Run Your First SEO Check (and Actually Understand the Report)

You've connected Search Console, maybe gotten your first pages indexed. Now comes the button that actually matters: Run Check. It's the core loop of yeet — one click produces a report on your site's health, and understanding that report is the difference between it being useful and it being noise.

The report always has the same four sections, in this order: found, did, awaiting approval, and verified since last. Each one answers a different question. Here's what each actually means and what you should do with it.

Found: problems discovered

This section is the result of yeet's watchers scanning your site and your search data for anything that looks wrong — a ranking that dropped, a click-through rate that's underperforming, lost backlinks, pages losing AI citations, missing or broken meta tags, and similar issues. Nothing here has been touched yet; it's purely diagnostic, a list of "here's what we noticed."

What to do with it: Read through it, but don't panic at volume — a longer list often just means your check is thorough, not that your site is in worse shape than a competitor's. Each item found here becomes (or updates) an optimization card, which you can read more about in Optimization Cards: Your SEO To-Do List That Does Itself.

Did: actions already taken

This is everything yeet actually did on its own during this check — pages submitted for indexing, pull requests opened against your codebase for fixes, and similar completed actions. Nothing in this list is a suggestion; it already happened.

What to do with it: Mostly, just review it so you know what changed. If a pull request was opened, you'll still want to actually look at it and merge it yourself — "did" means yeet took the action of opening the fix, not that it silently rewrote your live site without a trace.

Awaiting approval: things that need a human yes

Not everything yeet finds gets applied automatically, and that's intentional. This section holds proposed fixes that are ready to go but are waiting on you to say yes — because they're higher-risk, because your plan doesn't include auto-apply for that fix category, or because the free tier's agent always proposes rather than acts on its own.

What to do with it: Read the proposed fix and the evidence behind it, then approve it, edit it, or dismiss it. Nothing in this section costs you anything until you approve it. If you'd rather apply a fix yourself in your own editor, this is also where the "Copy fix prompt" action lives — more on that in the cards guide linked above.

Verified since last: fixes proven to work

This is the section worth caring about most, because it's not a suggestion or a to-do — it's proof. For any fix that was applied since your last check, yeet re-scrapes your live page to confirm the change actually shipped, then checks real data — Search Console metrics, or AI citation tracking — to confirm the fix actually worked, not just that it exists.

What to do with it: Nothing, really — this is your receipts pile. It's useful for understanding what's actually driving improvement versus what's still pending. Worth knowing: verified fixes aren't permanent certificates. If a fix disappears later — say, a meta tag gets overwritten in a future deploy — yeet will catch that regression on a future check and it'll show back up in "found."

What a check costs

A standard check costs 1 credit. If you want yeet to go deeper on a specific issue — a full investigation rather than a routine scan — that costs 3 credits. Both draw from whatever credit balance your plan includes; see pricing for how the free, Pro, and Agent plans compare on credits and what a top-up costs if you run out.

If you haven't gotten your pages indexed yet, that's the right place to start before your first check will have much to report on — see How to Get Your Site on Google (the 10-Minute Version).

Quick FAQ

Do I need to run a check manually every time? You can run one anytime you want a fresh read, but yeet's watchers also run continuously in the background, so cards can appear between checks too.

Why did something show up in "found" that I thought was already fixed? That's a regression — the fix was verified before, but something changed since (a deploy, a template update, a CMS setting) and yeet caught it reverting.

What's the difference between a check and a deep investigation? A check (1 credit) is a routine scan across your site. A deep investigation (3 credits) digs specifically into one issue with more thorough evidence-gathering before recommending a fix.