Fix library
Every problem we report has a page that fixes it.
Not advice. The lines to paste, the place to paste them, and the test that proves it worked, so you or your developer can close it today.
Start with whatever the check flagged
No machine-readable identity Common
The page never says, in a form a machine can read, who the business is. The single highest-value fix for a local business.
AI assistants blocked Costly
robots.txt refuses the crawlers that fetch pages for answers. Usually an accident, and usually confused with training crawlers.
Nothing quotable on the page Very common
No top-level heading, no description, the answer buried three paragraphs into brand prose.
Profiles that do not resolve Quiet
Structured data points at a social account that has moved or closed, weakening the corroboration it was added to provide. Repair page in preparation. The finding is still reported in full, with its evidence.
No sitemap Minor
Discovery of new and changed pages is slower and less complete than it needs to be. Repair page in preparation. The finding is still reported in full, with its evidence.
Content only after JavaScript Structural
The page looks fine to you and arrives nearly empty to a crawler that does not run scripts. Repair page in preparation. The finding is still reported in full, with its evidence.
How every fix page is laid out
- What we found — the finding as it appeared in your result, with its evidence reference.
- Why it matters — one paragraph, no scaremongering, and honest about how much it is worth.
- Before and after — your situation on the left, the corrected version on the right.
- Where it goes — the file, the place in it, and the common platforms named.
- Prove it worked — a test with an expected result, so nobody has to take our word for it.
- What it will not do — the honest ceiling on the change.
Fix pages are written for a competent web developer and a determined owner. Where a change needs care, the page says so rather than pretending everything is a five-minute job.