Technical SEO is the work of ensuring a search engine can crawl, render, index and understand a website. It covers crawlability, indexation, rendering, site speed, site architecture, structured data, redirects and international targeting.
It sits beneath everything else, and it is not optional. Content and links cannot rescue a page a search engine cannot reach or read. A site with a rendering problem can have the best content in its market and rank for nothing, and no amount of content investment will fix it.
Crawl, render, index, rank
Four stages. Fail at any one and everything downstream is irrelevant.
Crawl. Can the search engine reach the page? Is it linked from anywhere? Is it blocked in robots.txt? Is the server returning it?
Render. Can it see the content once it gets there? This is where JavaScript sites die. If the content only appears after client-side hydration, it may never be seen.
Index. Is it eligible to be stored? Is it noindex? Is it thin enough that Google chose not to bother?
Rank. Only now do content and links matter.
Almost every agency starts at stage four. They write content and build links for a page that is failing at stage two, and then they cannot understand why nothing is happening.
The failures we actually find, in order of frequency
One. Content that only exists in JavaScript. A React or Vue marketing site, client-side rendered. view-source shows an empty root div. Google can sometimes render it, eventually. Bing is worse. AI crawlers are worse still. The fix is server-side rendering or static generation — an architecture decision, not an SEO tweak.
Two. Content hidden in accordions and tabs. It is in the HTML, so people assume it is fine. It frequently is not extracted, which means the page can rank and never appear in an AI Overview. This is now a much more expensive mistake than it was two years ago.
Three. Staging environments indexed. Search site:staging.clientdomain.com right now. You will find one eventually.
Four. Disallow: / left in robots.txt after a launch. The single most catastrophic and most common launch failure in this industry. It is one line and it makes the entire site invisible.
Five. noindex left on after a launch. The second most common.
Six. Faceted navigation generating tens of thousands of junk URLs. Crawl budget burned, index bloated, signals split. → Ecommerce SEO
Seven. Redirect chains and loops accumulated across years of site changes. → 301 redirects
Eight. AI crawlers blocked. GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot. A developer "tightening security" deletes a client's entire AI presence and nobody notices for a quarter. Check this monthly.
Nine. Not in Bing's index at all. ChatGPT search is Bing-backed. A client absent from Bing is invisible to ChatGPT, and most agencies have never opened Bing Webmaster Tools. → The agency guide to AI search
The technical SEO audit
And the reason most of them are worthless.
Most technical audits are a 60-page PDF listing problems, delivered to a client whose developer has no time and no context.
It is homework. It is not a service. Twelve months later, the client has paid for an audit and nothing has changed.
A technical audit is only worth anything if somebody implements it. Ask every provider before the price: do you fix it, or do you tell me about it?
→ White-label technical SEO · How much does SEO cost
The audit, properly
Crawl the site twice — once as raw HTML and once with JavaScript rendering enabled — and compare. The difference between those two crawls is the rendering problem.
Then check, in this order:
Indexation
site:count against actual page count- GSC Coverage report — every excluded reason, understood
- Anything
noindexed that should not be - Anything indexed that should not be (staging, app URLs, filter junk)
Crawlability
robots.txt, read line by line- AI crawlers explicitly permitted
- XML sitemap present, accurate, submitted to Google and Bing
- No orphan pages
- Crawl depth reasonable
Rendering
view-sourceon key pages — is the content actually there?- Compare the raw HTML crawl against the rendered crawl
- Is critical content in accordions or tabs?
Redirects
- No chains, no loops
- Internal links point at final destinations
- Nothing important 404ing that has backlinks
Speed
- Core Web Vitals, field data not lab data
- LCP element identified
Structured data
- Present, valid, on a live page not in a settings screen
- No duplicate or conflicting schema from two sources
Architecture
- URL structure logical and stable
- Internal linking coherent
- No cannibalisation
The tools
Screaming Frog. The default crawler. Sitebulb. Better visualisation for non-technical clients. Google Search Console. Free, first-party, irreplaceable. The Coverage report is the most under-read document in SEO. Bing Webmaster Tools. Free. Gates ChatGPT. Since 16 June 2026 it also provides four AI-visibility metrics, free in preview. PageSpeed Insights. Field data, not lab. Rich Results Test. Validate schema on a live page.
What is technical SEO?
The work of ensuring a search engine can crawl, render, index and understand a website. It sits beneath everything else — content and links cannot rescue a page a search engine cannot reach or read.
Why does technical SEO matter more than content?
It does not matter more, it matters *first*. A site with a rendering problem can have the best content in its market and rank for nothing.
What is the most common technical SEO problem?
Content that only exists after JavaScript runs. Check `view-source` on a key page. If you see an empty root div, that is the problem.
Why do technical SEO audits fail?
Because most are a 60-page PDF of problems handed to a client whose developer has no time. Ask whether the provider fixes issues or only reports them, before asking the price.
Should I allow AI crawlers?
Yes. `GPTBot`, `OAI-SearchBot`, `PerplexityBot` and `ClaudeBot` must be permitted in `robots.txt`, and it should be checked monthly.
Do I need to be in Bing?
Yes. ChatGPT search retrieves from Bing's index. A site not in Bing is invisible to ChatGPT regardless of how it ranks in Google, and submitting takes twenty minutes.
Still Have Questions on Your Mind?
Contact our support team and we’ll guide you every step of the way.
