Field data outranks your Lighthouse score
A Lighthouse score is one synthetic run on one simulated device from one location. Google ranks on what real Chrome users experienced over the last 28 days, at the 75th percentile. The two disagree more often than people expect: a page can score 95 in the lab and fail Core Web Vitals in the field because real visitors arrive on slower phones over slower networks, or because an interaction the lab never triggers is the one that stalls. This audit shows both and tells you which one to believe when they differ.
Crawlability before performance
The most expensive technical SEO problems are the boring ones: a staging noindex that shipped to production, a robots.txt rule written for a subfolder that matches the whole site, a canonical pointing at a URL that redirects. None of them show up in a speed score, and any of them makes the speed score irrelevant. The rules engine checks these first and caps the grade when it finds one, whatever the rest of the report says.
What AI crawlers read
Assistants such as ChatGPT, Claude and Perplexity fetch pages with their own crawlers, each with its own user agent, and each respects robots.txt. Whether you allow them is a business decision, but it should be a decision. The report shows the verdict for each bot as robots.txt would give it, and whether an llms.txt file exists, so nobody is surprised later by what is or is not being cited.
What a single-page audit cannot tell you
One URL shows template-level and server-level problems, which is most of them. It does not show orphaned pages, duplicate titles across a category, faceted navigation creating thousands of crawlable URLs, or a sitemap listing pages that 404. Those need a full crawl and Search Console. Treat this report as the first backlog, not the complete one.
