Technical SEO audit: what Google actually receives from your site
Most audits are a dashboard export with a cover page. This one starts from the other end.
Every finding is checked against what your site serves a crawler, and every claim ships with the command that reproduces it.
Free check and full audit
The free check covers the errors that keep pages out of the index. Public data only, no access required, delivered in writing.
The full audit is the paid deliverable: the whole site, finding by finding, each with its impact, its fix and its proof. [Pricing and turnaround: Carlos decides.]
The failure modes I look for
The crawler gets a different page than you do
The most common failure on a React, Vue or AI-built site, and the one that makes everything else irrelevant. I request the same URL as a crawler and as a browser, and compare what comes back.
Pages that exist for you and not for the index
Sitemap entries that disagree with what the site serves, accidental noindex, canonicals pointing elsewhere, and routes returning 200 for URLs that were never meant to exist.
Markup that claims more than the page shows
Structured data declaring questions, reviews or prices that are not on screen. Search engines treat that as hidden content, and it is the fastest way to lose a rich result you already had.
Numbers that do not survive a second run
A single performance score is a coin flip. I run it repeatedly and report the median with its spread, because a decision made on one run is a decision made on noise.
Pages held up by the menu and nothing else
Navigation links every page, so navigation tells you nothing. What matters is which pages earn links from inside the content.
Responses that leak
Security headers do not move rankings, but a site without them fails any vendor review — and most sites that set them send them on pages only, not on the sitemap or the static assets.
How it is delivered
Finding, impact, fix, and the command to verify it afterwards. Written so a developer turns it into a ticket without a follow-up question.
The instruments behind each check are listed in my technical SEO toolkit.
Single page applications
If your site is a React, Vue or AI-built SPA, the first question is whether the crawler gets HTML at all. That is a different failure from "we need more content", and it is the one I see most.
The long version: the single page application SEO guide.
Want to know what Google receives from your site?
The free check is public data only, no access required, and you get it in writing.
Get a free diagnosis