Technical SEO Audit
Crawl issues, render problems, indexing weirdness. The kind of things that don't show up in dashboards until your traffic disappears. This audit finds them and gives you a fix list your dev team can actually use.
Why this matters
Google can't rank what it can't crawl, render, or trust. Plenty of "SEO problems" turn out to be technical problems wearing a content costume. A page is hidden behind a JS bug, or a stray noindex tag from a staging environment, or a redirect chain that sheds 80% of the link equity along the way.
You won't see any of that in Analytics. You see a flat line and start blaming the algorithm.
What's included
Everything that affects how Google reaches and reads your site
Crawl analysis
Full Screaming Frog crawl (or whatever your site needs), cross-checked against your sitemap, GSC, and log files. Every URL Google reaches, every URL it doesn't, and the wasted hops in between.
Indexability review
Noindex tags, canonical chains, robots.txt rules, sitemap mismatches, and parameter handling. Where you're telling Google to ignore pages you actually want indexed.
Rendering check
JS-dependent content, hydration failures, what Googlebot actually sees vs what your users see. If your site is React, Vue, Next, or any framework that ships content client-side, this is where the bodies usually are.
Site architecture
Click depth, internal linking, orphan pages, and how link equity flows from your homepage down to the pages you want ranking. Most sites underrate how much this matters.
Core Web Vitals
Real-user CrUX data plus lab tests in Lighthouse. LCP, INP, CLS, the actual page templates that fail, and what to fix first. Not just a screenshot of a green dial.
Log file analysis
What Googlebot actually requests, how often, and where it gives up. Crawl waste on parameter URLs, paginated junk, and dead redirects. The single most underused source of truth in technical SEO.
What you get
A document with the issues sorted by traffic impact, not by what's easiest to find. Each issue has the evidence (the URL, the screenshot, the log line), the fix, and an estimate of how hard it is for a developer to ship.
A 30-minute call to walk through it together so nothing gets lost in translation. Then I'm available for follow-up questions for two weeks.
Common questions
How long does the audit take?
Usually 5 to 10 working days, depending on site size. Bigger sites with millions of URLs take longer because the crawl alone takes longer.
Do I need to give you GSC and log file access?
GSC is helpful but not required. Log files are where about half the real findings come from, so I strongly recommend including them. Read-only access works fine.
Is this audit useful for small sites?
Honestly, not always. If you have under 100 pages and modest traffic, a technical audit usually isn't where the problem is. I'll tell you that on the intro call rather than take the money.
Will you fix the issues for me?
The audit is the diagnosis. Implementation is either done by your dev team (with me on hand for questions) or under a separate ongoing engagement. I don't bundle the two by default because most teams prefer to keep deploys in-house.
Think your site has hidden technical issues?
Send me the URL and a quick description of what you're seeing. I'll let you know whether an audit is the right call before scoping anything.