technical seo audit — finished as fixes
Technical SEO audit finished as fixes.
An audit is usually a list of things someone else now has to do. Mine comes with the doing. I read the site the way the machines read it — logs, crawl, rendering, response times, the structured graph — name the root causes, ship the corrections in your stack, and show the readouts afterwards.
in practice since 2007 · uk & us · one operator · no forms, no funnels
who this is for — three situations
01
Rankings slid and the last audit changed nothing.
The three fixes a popular tool prescribed for Small Business Coach Associates would have changed nothing; the real fault was the apex host, which had no server-level redirect at all. Audits that start from the evidence find that kind of thing.
02
You're about to migrate, redesign or replatform.
The audit becomes the freeze: every URL inventoried, every redirect mapped and tested before cutover, rankings watched through the flip. Trade2Sync's 1,687 URLs were mapped and fetched single-hop through the tested config.
03
Pages are slow and Core Web Vitals are red.
Speed is found at the root. A UK tile retailer's server response went from 2.2 seconds to 47 milliseconds once the real causes were found — among them an error log of 113 MB, growing daily.
how the work runs — four stations
01
Instrument
Server logs, Search Console exports, a full crawl, rendered-against-raw comparisons, origin timing, and the AI crawlers' view. Nothing is diagnosed from a tool's score alone.
02
Diagnose
Each finding carries its evidence and its consequence: what it costs in crawl, index or rank. Severity follows impact, never the number of pages a crawler flagged.
03
Fix
Shipped in your stack, each change reversible and recorded. Where a platform can't be changed, the workaround is documented with its limits stated.
04
Read out
The after-state from the same instruments: response times, index coverage, crawl stats, field Core Web Vitals when they land. Plain words, numbers attached.
what lands — the receipt
- 01Crawl, render and log-file analysis across the whole site
- 02Indexation and canonical audit with the exact URLs listed
- 03Core Web Vitals root causes found and the fixes shipped
- 04Structured-data graph review with validator output
- 05AI-search readiness: crawler access, extractability, llms.txt
- 06Redirect inventory and tests whenever URLs are changing
- 07A written report with the evidence beside every finding
signed — one operator, no handoffs
07 items
proof — on the record
sealed file · UK tile retailer
2.2 s → 47 ms
server response, before and after
source — server timing, verified
case file · Small Business Coach Associates
3 / 3
prescribed fixes that would have changed nothing
source — the tool's report, checked line by line
case file · Trade2Sync
1,687
URLs mapped, every one fetched single-hop through the tested config
source — nginx config test + fetch sweep
asked straight — answered straight
01How long does a technical SEO audit take?
It scales with the site and with what the logs show. A brochure site and a catalogue of a hundred thousand URLs are different jobs. The reply to your brief gives you a scoped answer, and the audit opens against a frozen inventory so you see progress from the first day.
02What's the difference between this and a free SEO audit tool?
Tools count symptoms; an audit explains them. The tool report on one recent engagement prescribed three fixes that would have done nothing while the real fault sat in the server config. You can run a free instrument on this site right now — the Agent-Ready Grader on the lab page — and it will tell you plainly what it can and cannot see.
03Do you fix what you find, or hand over a report?
Both, in that order of importance. The fixes ship in your codebase or platform; the report records what was found, what changed and what the readouts showed afterwards.
04Which platforms do you audit?
WordPress and WooCommerce, Shopify, ShopWired, Magento, headless and Next.js builds, custom stacks on nginx or Apache. The method is the same on all of them; the fix changes shape.
05Will the audit cover AI search as well as Google?
Yes. The same read covers the AI crawlers' access, content extractability and the structured graph — the inputs ChatGPT, Perplexity and Google's AI features depend on. The grader on the lab page scores exactly those.
start — the brief
A few lines about the site, the problem and the evidence you have.
The reply is a straight read on fit and shape, from the person who does the work. If what you need is small, it says so. If it is not a fit, it points somewhere better.
other doors