Optimization Cards: Your SEO To-Do List That Does Itself

If you've read the previous guide, you've already seen the word "card" a few times. Here's the full picture: a card is yeet's basic unit of work — one specific problem, the evidence behind it, and a ready-to-apply fix, bundled together so you're never staring at a vague warning wondering what it actually means or what to do about it.

A typical card isn't "your SEO could be better." It's something like: this page's title tag disappeared from search results, here's the crawl data showing when it changed, and here's the exact schema markup fix that would restore it. Specific problem, specific evidence, specific fix.

Where cards come from

Cards are found by watchers — background processes that keep an eye on things like rank drops, click-through rate problems, lost backlinks, and lost AI citations, among other signals. When a watcher notices something worth flagging, it doesn't just hand you a raw alert. An AI investigates it first: it scrapes your actual live page, checks real data, and only then writes up a recommendation. That investigation step matters — it's the difference between "something changed in a metric" and "here's specifically what's wrong and why."

The lifecycle of a card, in human terms

Every card moves through the same stages, whether it's a meta tag issue or an AI-citation drop:

• Found — a watcher spotted something worth looking into.
• Being fixed — the AI has investigated, confirmed the problem against your live site, and drafted (or applied) a specific fix.
• Checking it worked — yeet re-scrapes your live page to confirm the fix actually shipped, then checks real numbers (Search Console data, or AI citations, depending on the card) to see if it actually moved anything.
• Confirmed — verified, done, and added to your record of proven fixes.

Cards can also move backward. If a confirmed fix quietly disappears later — overwritten by a template change, a CMS update, or a redeploy — yeet notices and reopens it. Nothing stays "fixed forever" without yeet actually continuing to check.

What "Copy fix prompt" does

Not everyone wants yeet touching their codebase directly, and that's fine. Every card has a "Copy fix prompt" action, which generates the best-quality version of the fix and copies it in one step — ready to paste straight into whatever editor, AI coding tool, or ticket you actually work in. It's the same underlying fix quality as an auto-applied one; the difference is just who does the applying.

What auto-apply actually means

For fix categories yeet is confident handling directly, it can open a real GitHub pull request against your repository — not silently edit your live site, an actual PR you review and merge like any other change. The categories that support this today are meta tags, schema markup, technical issues like an accidental robots noindex, duplicate-page canonicals, and llms.txt.

Auto-apply isn't available on every plan the same way. On the free plan, the agent only proposes fixes — you approve everything by hand. On paid plans, auto-apply becomes available, and it costs credits accordingly: opening an auto-apply pull request costs 2 credits, while a fully hands-off fix — one where yeet applies it and completes the verification loop without you doing anything in between — costs 5 credits. See pricing for how those credit allowances compare across plans.

You can dismiss anything

Not every flagged issue is worth fixing for your specific site, and yeet doesn't assume it knows better than you about that. Every card can be dismissed, no explanation required and no penalty. Dismissing something doesn't cost credits, and it won't stop yeet from flagging genuinely new problems later — it just tells yeet you've seen this specific one and don't want to act on it.

If you haven't run a check yet to generate your first batch of cards, start with Run Your First SEO Check (and Actually Understand the Report). And if some of your cards are about AI assistants losing track of you rather than Google, Will ChatGPT Recommend Your Website? explains that side of things in full.

Quick FAQ

Does dismissing a card cost credits? No — dismissing is free. Credits are spent on checks, investigations, and applying fixes, not on deciding what to ignore.

What happens if I approve a fix and it doesn't actually help? yeet's verification step checks real data after applying a fix, not just whether it was technically applied. If the metrics don't move the way expected, that shows up honestly rather than being marked confirmed.

Can every kind of fix be auto-applied as a pull request? No — only specific categories currently support it (meta tags, schema markup, technical fixes like noindex issues, duplicate-page canonicals, and llms.txt). Other fixes are proposed for you to review and apply through "Copy fix prompt" instead.