Read it, then pass the check at the end to open the final check.
What to do next week, and the live test
Updated
Next week, in order, and nothing else:
- Run the index read. One call per sitemap URL, one CSV.
- Sort the CSV by verdict. Read the canonical columns first.
- Fix one class of failure, the biggest row count, in one commit.
- Request only the URLs that changed. One at a time. Write down the time.
- Read again a week later, and before you publish anything about it, check the live status of every URL you claim moved.
The live test on my side: five English service pages on clevrstart, crawled and not indexed since 2026-08-28, linked from every footer since 2026-10-15, request not yet made. Their dates fill in as they land, and if they do not land in the 48 hours I expect, that goes in too.
For a business rather than a developer, the same loop has an owner’s version. local seo mistakes shows what we would not do again and what we do instead, with the Business Profile as the entity; how to get clients with seo shows one page per service and one booking as the action, with our own starting numbers; and the local seo plan page shows what the mapped-and-built version looks like for a business that wants it done.
The traffic that comes after indexing, and what I do with it on platforms I rent versus pages I own, is What I do now for traffic, with the same 74 impressions and 1 click as the starting line.
One line on AI visibility, because someone will ask: whether your pages get cited by an AI answer is a separate question with its own cluster, and this workshop stops at indexing. A page that is not indexed is cited by nothing.
Check what you read in “What to do next week, and the live test”
Three questions drawn from a larger pool, so no two papers are quite the same. Two right passes it and opens the next step. The questions are public; scoring them needs an account, and the key never leaves the server.
Loading the check…