A technical SEO audit that reads the code.
Crawler reports list thousands of symptoms. I find the few problems that actually cost you traffic, trace each one to the template or setting behind it, and rank the fixes by impact. Then your developer makes them, or I do.
- Price
- Fixed fee, quoted on a call
- Platforms
- Next.js, React, WordPress, Shopify
- Data
- Search Console, Semrush, your analytics
(01)What gets checked
| Area | What I look at |
|---|---|
| Crawling and indexing | Pages Google can’t reach or chooses not to index, noindex and robots.txt mistakes, redirect chains, soft 404s, and what Search Console’s page indexing report says. |
| Canonicals and duplicates | Canonical tags, trailing-slash and www variants, parameter URLs, and near-duplicate pages competing for the same search. |
| Rendering | Whether content and links are in the HTML or only appear after JavaScript runs, and how the framework (Next.js, React, WordPress, Shopify) is set up to render them. |
| Site structure and internal links | How pages link to each other, orphaned pages, and whether the pages that should rank get the links. |
| Structured data | Organization, product, article, FAQ and breadcrumb markup: valid, accurate, and matching what’s on the page. |
| Sitemaps | Whether the sitemap lists the right URLs, with honest last-modified dates, and matches what’s indexed. |
| Speed and Core Web Vitals | Field data from Search Console and PageSpeed Insights, and the templates, images and scripts behind slow pages. |
| AI search access | Crawler access for AI assistants in robots.txt, an llms.txt guide, and whether key facts are readable without JavaScript. |
| Titles and search demand | Titles and headings compared with the queries Search Console shows you appear for, and pages on page two that a better title could lift. |
(02)What you get
- 01A written report in plain language, every finding ranked by impact and effort
- 02The exact template, file or setting behind each issue, not just the URL it shows up on
- 03A fix list your developer can work from, or I make the fixes
- 04A walkthrough call to go through the findings
(03)Why not just a tool
Different from a crawler report
| Usual approach | What you get | This audit |
|---|---|---|
| Crawler tools (Screaming Frog, Semrush Site Audit) | List symptoms per URL: thousands of rows, many harmless. | I use them too, then trace each real problem to the template or code that causes it. |
| Agency SEO audits | Often a long PDF someone else has to implement. | Written for your developer, or I implement it myself. |
(04)Related
(05)Questions
What is a technical SEO audit?
A review of how search engines crawl, render and index a site: the parts of SEO that live in the code and configuration rather than in the writing. It finds problems such as pages Google can’t index, duplicate URLs, slow templates and broken structured data, and says how to fix them.
How is this different from running Semrush or Screaming Frog myself?
Those tools are a good start and I use them. They report symptoms URL by URL, many of which don’t matter. The audit decides which problems actually cost you traffic, finds the template or setting that causes each one, and orders the fixes by impact.
What do you need from me?
Read access to Google Search Console and your analytics, and access to the codebase or CMS. Read-only access is enough for the audit.
Which platforms do you audit?
Next.js and React sites, WordPress, Shopify and Webflow. On Next.js and React I can make the fixes directly in the code; on hosted platforms I make the changes the platform allows.
Will the audit improve my rankings?
The audit itself changes nothing; the fixes do. Technical fixes remove what holds pages back, and results show up as Google recrawls the site, usually over weeks. Nobody can guarantee positions in Google.
Find out what’s holding the site back.
A 20-minute call to look at your Search Console together and decide whether an audit is worth it.