What does technical SEO cover?

Everything that determines whether machines can fetch, render, and understand your site: crawl access, site architecture, rendering strategy, sitemaps, canonicals, structured data, page speed, and HTTPS. Content quality is out of scope — this layer is pure infrastructure.

What changes in technical SEO for AI search?

The crawler population changed. GPTBot, ClaudeBot, and PerplexityBot generally don't execute JavaScript, so client-rendered content is invisible to them. AI-era technical SEO adds bot access policy, server-side rendering, and optionally llms.txt to the classic checklist.

What Is Technical SEO?

Last updated: July 5, 2026 · Menra Team

Technical SEO is the infrastructure layer of search optimization: the work that ensures crawlers can fetch a site, renderers can see its content, and indexes can store it correctly. It spans crawl management, information architecture, rendering, canonicalization, sitemaps, structured data, and performance — everything except the content itself.

The classic checklist

The foundation hasn't changed: a clean robots.txt, XML sitemaps with accurate lastmod values, canonical tags that consolidate duplicates, sane URL structure, HTTPS, and Core Web Vitals within Google's thresholds (LCP under 2.5s, INP under 200ms since INP replaced FID in March 2024). Sites failing these basics leak crawl budget and index coverage before content quality ever gets evaluated.

What the AI era adds

A new class of consumers now fetches your pages, and they behave differently from Googlebot:

Bot access policy. Decide explicitly which AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot) may access what, and encode it in robots.txt rather than letting CDN bot protection block them accidentally.
Server-side rendering. Most AI crawlers do not execute JavaScript. Content that only exists after client-side hydration is invisible to them, which makes SSR or static generation a hard requirement for AI visibility, not a performance nicety.
llms.txt. The llmstxt.org proposal (Jeremy Howard, September 2024) offers a curated Markdown map of your most important content for LLM consumption — low effort, uncertain but nonzero payoff.
Log-file analysis for AI crawlers. Verifying that GPTBot and friends actually fetch your key pages closes the loop; a crawl-to-citation funnel starts with confirmed crawls.

Example

A React SPA documentation site showed near-zero ChatGPT citations despite strong Google rankings — Googlebot renders JavaScript, GPTBot doesn't, so ChatGPT's retrieval saw empty shells. Moving docs to static generation made the full text fetchable, and AI crawler hits in the logs converted into citations over the following weeks.

Related terms

See crawlability, server-side rendering, robots.txt, llms.txt, and Core Web Vitals.

Frequently asked questions

What does technical SEO cover?: Everything that determines whether machines can fetch, render, and understand your site: crawl access, site architecture, rendering strategy, sitemaps, canonicals, structured data, page speed, and HTTPS. Content quality is out of scope — this layer is pure infrastructure.
What changes in technical SEO for AI search?: The crawler population changed. GPTBot, ClaudeBot, and PerplexityBot generally don't execute JavaScript, so client-rendered content is invisible to them. AI-era technical SEO adds bot access policy, server-side rendering, and optionally llms.txt to the classic checklist.

Keep exploring

See how AI engines talk about your brand — track mentions across ChatGPT, Perplexity, Claude, Gemini and 5 more. Start with Menra