Say a company buys a technical SEO audit. Eighty pages, two hundred findings, a developer spends six weeks closing them. Page speed goes green, the duplicate URLs are gone, the sitemap is clean. Three months later organic traffic is where it was. Nobody did anything wrong. The audit did what an audit does: it removed what was stopping Google from reading the site. It did not give anyone a reason to search for the site, and it did not make a single page better at answering. The ceiling moved up. The room under it was empty.
Technical SEO removes what stops Google from reading a site. It gives nobody a reason to search for it.
What technical SEO is
Google’s description of how Search works has three stages: crawling, indexing and serving. Google downloads the page, works out what is on it, and decides whether to show it for a query. The same page says not all pages make it through each stage, and that Google does not guarantee any of the three.
Technical SEO is everything that decides whether a page gets through the first two stages and is eligible for the third. Can Google reach the URL. Does it load fast enough to be worth crawling. Is there one version of it or five. Does the HTML say what the page is about, with one heading and readable text, or is it a wall of scripts. Does the site tell Google which language each page is in and which pages are the same page in another language.
That is the whole job. It is a gate, and it is binary at each stage: the page is reachable or it is not, indexed or not, eligible or not. Once it is through, technical work has nothing more to say about where it ranks.
What it is not
A page that passes every technical check still has to be something people search for, and it still has to be the best answer among the pages that also passed. Technical work does neither.
It does not create demand. If 40 people a month search for what the site sells, the cleanest site in the category gets a share of 40. The audit cannot change the 40. Choosing which queries the site should be found for, and whether those queries exist at all, happens before any technical work and decides more than all of it.
It does not write the answer. Google’s documentation on AI features says there are no additional technical requirements to appear in AI Overviews or AI Mode. What those features need is a page that answers the question in its first sentence, from a source the engine can identify. Both of those are content decisions. A technically perfect page that opens with a paragraph about the company’s vision is a technically perfect page nobody quotes.
It does not move a page from position 8 to position 3. Once two pages are both crawlable, indexed and fast, the difference between them is what they say, who says it and who else points to it. The audit has already done its part for both.
When technical is the whole problem
There are sites where the ceiling is so low that nothing else matters until it moves, and the audit is the right first purchase.
Large sites. Tens of thousands of URLs, faceted navigation, filters that generate pages nobody asked for. Half the crawl goes to pages that should not exist and the pages that should are crawled once a month. That is a crawl budget problem and it is technical from start to finish.
Migrations. A new domain, a new CMS, a new URL structure. If the redirect map is wrong, years of accumulated signals point at pages that return 404. Nothing content-side can recover that. Site migrations are the case where technical work is the whole project.
Broken indexing. A noindex tag left from staging, a canonical pointing at the wrong language, a robots.txt that blocks the CSS so Google renders the page as empty. These are one-line problems with site-wide consequences, and a site with one of them is invisible regardless of how good the pages are.
Agents that cannot fetch. The newest version of the same gate. If the crawlers behind ChatGPT and Perplexity are blocked at the firewall or in robots.txt, every content decision made for AI search is made for nobody. Which AI crawlers to allow is the first check, before any page is rewritten.
In all four, the site is below the ceiling. Moving it changes everything.
This site, measured logged out after launch: 74 to 85 milliseconds to first byte, 111 to 132KB of HTML per page. Green on every technical check. It also had zero rankings on launch day, because the old site had none to inherit and no page had yet answered a question anyone asked. The ceiling was high. The room was empty.
When technical is the alibi
The other pattern is a mid-sized site with 200 pages, a decent CMS and traffic that has been flat for two years. It has had three audits. Each one found things. Each one was closed. Traffic did not move, because the site was never below the ceiling. It was in the room, with nothing to say.
Three ways to tell you are in this pattern:
- The findings are small and many. Image alt text, meta descriptions over 155 characters, a handful of redirect chains. Two hundred of these are not a ceiling. They are a to-do list that keeps a developer busy while the content question goes unasked.
- The queries the site ranks for are not the queries that buy. Open Search Console and read the top twenty queries. If they are definitions and how-tos, the site has a demand problem and an answer problem, and no audit addresses either. The pages AI answers took from you is what happens to that pattern next.
- The drop has a date. A site that was fine and then was not has a ranking event or an AI answer event, and the diagnosis is core update or AI answer, not a crawl report. The audit will find things, because it always does, and none of them will be the cause.
Audits are popular in this pattern for a reason that has nothing to do with search. They produce a document, the document has numbers, and closing the numbers feels like progress. Deciding what the site should be found for produces an argument, and arguments are harder to invoice.
What to buy instead, and in what order
- A demand check before an audit. Which queries, with what volume, from which buyers. If the answer is “none with volume”, the next purchase is not technical and it is not content either. It is positioning.
- Then the gate. One pass on crawl, index and speed, sized to the site. A 200-page site needs an afternoon, not an 80-page document.
- Then the answers. The pages that serve the buying queries, rewritten so the first sentence answers and the entity is clear. This is where rank moves.
- Then the audit again, only if something breaks. Technical SEO after launch is maintenance: a check when the CMS updates, when pages move, when traffic steps down with a date. It is not a quarterly growth lever.
Where this sits
In SEO consulting the technical pass is the first week, and it is a week because the point is to clear the gate and get to the questions that move rank. If you have an audit on your desk and the site has had two already, tell me what the audit found and I will tell you which findings are a ceiling and which are a to-do list.