04 / 04

Fix what is worth the most first.

Every scan turns your crawl, Search Console and Analytics data into one ranked list. Each item says why it matters, which pages it touches and what it could be worth, with steps, a definition of done and a brief you can hand off.

In numbers

26 kinds of fix

From search, Analytics traffic, the crawl and page speed.

0–100 score

Estimated clicks or reach, plus severity, weighed by confidence.

1 click to verify

We fetch the pages from your live site and run the same checks again.

1 Markdown task

Any fix, copied as a self-contained task for a person or a coding agent.

Fig. 01 — Improvements · open. A sample list of five open improvements ranked by score: server errors at 70, a striking-distance query worth about 240 extra clicks a month at 58, down to thin pages at 20.Sample data

[01]Ranking

One list, in order.

Each fix gets a score from 0 to 100. The list is sorted by it, and ties go to the fix with more estimated clicks.

  1. 01

    What it is worth

    Up to 65 points for estimated clicks, measured against your own traffic: a fix worth 8% of your monthly clicks gets the full 65, so a 50-click win ranks high on a small site and lower on a big one. Without click data, up to 40 points for the share of pages it affects.

  2. 02

    How bad it is

    Up to 35 more points for severity. Critical issues, like server errors or a robots.txt that blocks everything, never score below 70.

  3. 03

    How sure it is

    Each kind of fix carries a confidence between 0.55 and 0.9, and the total is multiplied by it: a broken link is near certain, the clicks a query with none yet might win much less so.

Severity points

Critical
35
High
25
Medium
15
Low
6
Fig. 02 — One score, taken apart. A sample score of 58: 58 of 65 points for estimated clicks plus 25 of 35 for high severity, multiplied by a confidence of 0.7.Sample data

[02]Each fix

Why, where, and when it is done.

Open any item for the full picture. Nothing is a vague warning: each one names its pages, its numbers and its finish line.

  • 01With evidence

    Why this matters

    A plain explanation of the problem and the numbers behind it: positions, impressions, CTR against the benchmark, word counts or status codes.

  • 02Or one target

    Affected pages

    Every URL the fix touches, or the single page and query it is about.

  • 03Tick them off

    Steps

    Concrete actions in the order to do them. Your ticks are kept in this browser while you work.

  • 04Acceptance criteria

    Done when

    How to check the fix worked, measurable where it can be, such as “average position at 8 or better within 6 weeks”.

  • 05Last 28 days

    In Google now

    The target page's clicks, impressions, CTR and position from Search Console, next to the fix.

  • 06Per month

    Estimated clicks

    With Search Console connected, the clicks a month the fix could add or win back, worked out from your own impressions, CTR and clicks.

[03]Verification

Checked on your live site.

A fix counts as done once we can see it, not when someone says so. Fixes keep the same identity from scan to scan, so done means something.

  1. 01

    Verify the fix

    We fetch the affected pages from your live site and run the scan's checks on them again. Only a passing check moves the fix to Done. If the issue is still there, it stays open and shows the pages where we found it.

  2. 02

    Every scan checks again

    If a later scan finds the issue again it reads Still detected, so you know to look again.

  3. 03

    Data takes weeks

    Fixes for issues found in Search Console, Analytics or speed data can't be seen on a page. Mark them done and they read Tracking results while the 28-day data catches up.

  4. 04

    See what moved

    When the fix is about a page or query in Search Console, its clicks and position before and after sit next to the badge.

  5. 05

    Dismiss what doesn't apply

    Dismissed items stay out of the open list, even after rescans. Reopen them any time.

Fig. 03 — Improvements · done. Two sample fixes marked done: one verified fixed with clicks up from 12 to 30 and position from 14.2 to 9.1, and one verified on the live site two hours ago.Sample data

[04]Briefs

A brief you can hand off.

Each fix can come with a brief: a headline, a summary, paste-ready deliverables, the steps and the checks. Copy one piece at a time, or copy the whole fix as a Markdown task.

Written by Claude

Title options, 30–60 characters, with counts
3
Meta descriptions, 120–155 characters
2
H2/H3 outline and FAQ questions, from your queries
Content fixes
Exact markup, config or code, and the URLs to change
Technical fixes
Internal links: source, target and anchor text
Up to 5 sources

On Pro and Agency, briefs are written by Claude; on Base, they are built from a template. Each brief is labelled with which one wrote it. Either way the input is your own data: up to 15 affected pages, up to 15 of the queries the page ranks for, and your strongest pages that don't link to it yet. Claude is told not to invent metrics, rankings or competitors. Not happy with it? Rewrite.

Fig. 04 — Brief · title options. A sample brief for a striking-distance query: three title options with character counts, a meta description, and a Copy as task button.Sample data

[05]How it fits

Four views, one list.

Each view feeds the next. Search Console clicks decide which crawl and speed issues rank first, and every finding ends up in the same ranked list of improvements.

[06] Start now

Get your list of fixes.

From $9 a month. First 3 days free.