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.
See these repairs in context on an example result, or run the free audit on your own site.
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.
- No profiles declared Very common
The page never tells a machine where else the business exists: no map listing, no social account, no register entry to corroborate it.
Structured data points at a social account that has moved or closed, weakening the corroboration it was added to provide.
- No sitemap Minor
Discovery of new and changed pages is slower and less complete than it needs to be.
- Content only after JavaScript Structural
The page looks fine to you and arrives nearly empty to a crawler that does not run scripts.
The crawler questions we are asked most
OpenAI runs three crawlers with three jobs. Which one to allow for citation, which one governs training, and the robots.txt lines.
ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot and Perplexity-User: which is which, and what robots.txt can and cannot do about each.
The checklist for owners: what to check yourself in an afternoon, and what you may still be sold that no longer works.
What the file is, what Google and the other providers say about it, and what to do with the hour instead.
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, without scaremongering, that says plainly how much the change is likely to be worth to this kind of business and when it is not worth the hour.
- 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 that nobody, including us, has to take our word for it.
- What it will not do. The ceiling.
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.