Technical seo audit.
What Google can't crawl, index or trust — found, ranked and fixed
The detail
Most technical SEO audits arrive as a PDF: two hundred rows of red, half of them things your CMS already handles, and no answer to the only question that matters — which of these is actually costing you enquiries. I have watched clients pay for that report twice: once for the audit, then again for a developer to work out what it meant.
I audit as the person who implements the fix. I pull the crawl, the Search Console data and the code, explain in plain English what each problem breaks, rank the list by what it is costing you, and then make the changes myself on WordPress, WooCommerce, Next.js or the server — or hand your developer one ticket per issue with the exact change and how to verify it. The work ends with a re-crawl, not a recommendation.
At a glance
- Crawl & Indexation Diagnostics
- Core Web Vitals & Real Speed
- JavaScript Rendering
- Canonicals, Duplicates & Redirects
What's included
Everything in the scope.
Written into the proposal line by line, so there is nothing to argue about at invoice time.
Crawl & Indexation Diagnostics
What Google is finding, what it is choosing not to index, and why — thin pages, stray noindex rules, canonicals, robots.txt and crawl budget burned on parameter URLs.
Core Web Vitals & Real Speed
LCP, INP and CLS from field data, then the actual cause behind each one: render-blocking scripts, oversized images, plugin bloat, slow hosting or a heavy theme.
JavaScript Rendering
For React, Next.js and headless builds: what the crawler sees before hydration, whether the content survives with JavaScript off, and which routes are client-only.
Canonicals, Duplicates & Redirects
www vs non-www, trailing slashes, HTTP/HTTPS, pagination, and old migration redirect chains that still leak link equity into the wrong URL.
Structured Data & SERP Features
Organization, Service, Product, Article, FAQ and breadcrumb markup that is valid, matches the visible page, and earns the rich result instead of a manual action.
International & Local Signals
hreflang for US, UK, Germany and UAE targeting, currency and language variants, and Google Business Profile plus NAP consistency for city-level searches.
How it runs
From brief to
launch.
Four steps, each one ending in something you can open and review rather than a status update.
- 01Access & BaselineSearch Console and Analytics access, a fresh crawl of the site, and a before-snapshot of indexation, rankings and Core Web Vitals so the work can be measured afterwards.
- 02Ranked FindingsA short list grouped by what each issue breaks — crawling, indexation, rankings, revenue — with the evidence behind it: URLs, log lines, screenshots, the actual code.
- 03ImplementationI make the changes where I have access (WordPress, WooCommerce, Next.js, AWS/Hestia), or write one ticket per issue for your developer with the exact fix and acceptance check.
- 04Verification & HandoverA re-crawl and Search Console validation after the fixes, plus a plain-English record of what changed and what to watch, so nothing quietly reverts.
Before you ask
Questions about technical seo audit.
Both, where I have access. On WordPress, WooCommerce, Next.js and AWS/Hestia setups I implement the fixes myself, including redirect maps and structured data. If another developer owns the codebase, I hand over one ticket per issue with the exact change and a check they can run, then re-crawl after they ship to confirm it worked.
Search Console access (Full or Owner), read access to Analytics if you have it, and access to the code or hosting if you want the fixes applied rather than handed over. Without that access I can still audit from the outside, but anything that needs the codebase or server logs stays a recommendation.
Not on its own. A technical audit removes the reasons Google cannot crawl, index or trust the site; it does not create demand for what you sell. If the pages target keywords nobody searches, or the site has no authority yet, the audit will say so plainly instead of burying it under green ticks.
Let's work together
Ready to get started with Technical SEO Audit?
Tell me about your project and I'll come back with honest advice on the best way forward — including if the answer is that you don't need it yet.
United StatesUnited KingdomGermanyUnited Arab Emirates