What is technical SEO?
Technical SEO is the work that makes a website easy for search engines to crawl, render, index, and understand. It covers site architecture, page speed, mobile rendering, canonical tags, redirects, structured data, and security. Good content cannot rank if Google cannot reach it. In 2026, the same foundations also decide whether AI Overviews and AI assistants can read and cite your pages.
Think of it as the plumbing under your content. On-page SEO decides what a page says. Off-page SEO decides who vouches for it. Technical SEO decides whether a search engine can get to the page at all, and whether the version it sees is the one you intended.
This guide walks through every core element, in the order you should fix them. It ends with a checklist and answers to the questions site owners ask most.
Why does technical SEO still matter in the age of AI search?
Technical SEO matters more in 2026, not less, because AI search features are built on the same index as classic search. Google states there are no additional requirements to appear in AI Overviews or AI Mode. A page must simply be indexed and eligible to show a snippet.
That sentence carries a hidden demand. If a page is blocked by robots.txt, stuck behind broken JavaScript, or canonicalised to the wrong URL, it cannot be cited anywhere in Google. The same logic applies to other engines. ChatGPT Search and Perplexity fetch pages live and read the visible HTML.
Google also notes that AI features use "query fan-out", running many related searches across subtopics to build one answer. That rewards sites where every useful page is crawlable and clearly linked, not just the homepage.
So the job has not changed. What changed is the cost of getting it wrong. A technical fault now hides you from both the blue links and the AI answer above them.
How do crawling and indexing work?
Crawling is when Googlebot discovers and downloads a URL; indexing is when Google processes that page and stores it so it can appear in results. Google explains the full pipeline in How Search works: crawl, index, then serve.
Three files and tags control this pipeline:
- robots.txt tells crawlers which paths they may request. It controls crawling, not indexing. Google's robots.txt introduction warns it is not a way to hide pages from results.
- The robots meta tag (noindex, nosnippet, max-image-preview) controls indexing and snippets on a page-by-page basis.
- XML sitemaps list the URLs you want found. They help most on large, new, or poorly linked sites, per Google's sitemaps overview.
A common mistake is blocking a page in robots.txt and adding noindex to it. Google cannot see the noindex on a page it is not allowed to crawl. Use one or the other, based on your goal.
How should you structure a site for SEO?
A good site structure keeps every important page within a few clicks of the homepage and groups related pages together. Flat, logical architecture helps crawlers find content and helps users understand where they are.
Follow these rules:
- Use clean, readable URLs. Google's URL structure guidance recommends simple, descriptive words and hyphens.
- Group pages into topic hubs. A hub page links to its supporting articles, and each article links back.
- Add breadcrumbs. They show hierarchy to users and can appear in results with breadcrumb structured data.
- Use standard HTML anchor links with an href. Google can only follow crawlable links, not click handlers.
Orphan pages, with no internal links pointing at them, are the usual casualty of poor structure. They may sit in the sitemap for months without ranking. A crawl tool that compares linked URLs against sitemap URLs will surface them quickly.
How fast does a website need to be?
A website should pass all three Core Web Vitals at the 75th percentile of real visits. The thresholds, set out on web.dev, are:
| Metric | What it measures | Good score |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading speed of the main content | 2.5 seconds or less |
| Interaction to Next Paint (INP) | Responsiveness to taps and clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Visual stability | 0.1 or less |
INP replaced First Input Delay as a Core Web Vital in March 2024. Many older guides still cite FID, so treat them as out of date.
Google describes Core Web Vitals as part of its page experience signals. They rarely beat relevance on their own. They do act as a tie-breaker, and slow pages lose users before they convert. Speed also matters for AI crawlers that fetch pages live under tight timeouts. The fastest wins usually come from compressed images, fewer third-party scripts, and server-side rendering.
Is mobile-first indexing still relevant?
Yes. Google now uses the mobile version of a page for indexing and ranking, so whatever your phone visitors cannot see, Google may not see either. The mobile-first indexing guide lists what must match between mobile and desktop.
Check these points:
- The same main content appears on mobile and desktop.
- Headings, structured data, and meta robots tags are identical.
- Images on mobile have the same alt text and are crawlable.
- Lazy-loaded content loads without a user action such as a swipe or click.
Responsive design, where one URL serves every device, is the simplest way to meet all four. Separate m. subdomains still work but double the maintenance and the chances of drift.
Test on a real mid-range phone, not only a desktop emulator. Tap targets, pop-ups, and layout shifts look very different on a small screen with a slow connection.
How do you fix duplicate content and canonical issues?
You fix duplicate content by choosing one preferred URL for each piece of content and signalling it consistently. Google explains the options in its guide to consolidating duplicate URLs.
Duplicates appear more often than people expect. Common sources include:
- http and https versions both resolving
- www and non-www versions both resolving
- trailing slash and non-slash URLs
- tracking parameters such as ?utm_source=
- filtered or sorted category pages on ecommerce sites
The fixes, from strongest to weakest signal, are 301 redirects, rel="canonical" tags, and consistent internal links plus sitemap entries. Use 301 redirects when the duplicate should never be visited. Use canonical tags when the variant must stay live for users.
One rule matters above all. When you move or retire content, redirect each old URL to its closest relevant replacement. Redirecting everything to the homepage or a hub page is treated much like a soft 404, and rankings do not transfer.
What role does structured data play?
Structured data is code, usually JSON-LD, that describes a page's content in a standard vocabulary so search engines can understand entities and show rich results. Google's introduction to structured data lists the supported types.
The most useful types for most businesses are:
- Organization and LocalBusiness for brand and contact details
- Article for blog posts and guides
- Product and Review for ecommerce
- BreadcrumbList for site hierarchy
Keep expectations realistic. Structured data makes pages eligible for rich results and helps Google's own systems understand entities. It does not guarantee a rich result, and several types, such as HowTo, no longer produce one. External AI assistants mostly read the visible page text, so every important fact should also appear in the body copy.
You can draft valid JSON-LD quickly with our free schema generator, then test it before publishing.
How do HTTPS, JavaScript, and international setups affect SEO?
These three areas cause the most hidden technical failures, because the site can look fine to a visitor while search engines see something different.
HTTPS. Every page should load over HTTPS with a valid certificate, and every http URL should 301 to its https twin. Mixed content warnings can break images and scripts.
JavaScript. Google can render JavaScript, but rendering is a separate step that can lag behind crawling. Google's JavaScript SEO basics recommend server-side or static rendering for important content. Many AI crawlers do not run JavaScript at all, so content that only appears after scripts run may be invisible to them.
International SEO. Sites serving several languages or countries need hreflang annotations that point each version to its alternates. Google's localized versions guide covers the syntax. Each language version should also have its own URL, not rely on cookies or IP detection.
What should a technical SEO audit checklist include?
A technical SEO audit should confirm, in order, that pages can be crawled, indexed, rendered, and served fast. Work through this checklist each quarter:
- Crawl the whole site and list 4xx errors, 5xx errors, and redirect chains.
- Review the Page indexing report in Google Search Console for excluded URLs.
- Confirm robots.txt is not blocking important sections or resources.
- Check that the XML sitemap only lists live, indexable, canonical URLs.
- Verify one preferred version of every URL and consistent canonical tags.
- Measure Core Web Vitals with field data, not only lab tests.
- Validate structured data and fix errors.
- Find orphan pages and thin or duplicate pages.
- Confirm title tags and meta descriptions are unique; our meta analyzer checks a page in seconds.
- Fetch key pages without JavaScript to see what AI crawlers see.
If the list surfaces more than your team can fix, a specialist technical SEO service can prioritise the issues by traffic impact.
Frequently asked questions
What is the difference between technical SEO and on-page SEO?
Technical SEO makes pages crawlable, indexable, fast, and correctly configured, covering robots.txt, sitemaps, canonicals, redirects, and Core Web Vitals. On-page SEO improves the content itself, including titles, headings, copy, and internal links. Both are needed. Technical SEO gets the page into the index, and on-page SEO helps it rank for the right queries.
How often should I run a technical SEO audit?
Run a full technical audit at least once a quarter, and always after a redesign, CMS migration, or URL change. Large ecommerce sites benefit from monthly crawls because new filters and products create fresh duplicate URLs. Check the Page indexing report in Google Search Console weekly so sudden drops are caught early.
Does technical SEO help with AI Overviews and ChatGPT?
Yes. Google says AI Overviews and AI Mode have no extra requirements beyond normal indexing and snippet eligibility, so technical health is the entry ticket. Other AI assistants fetch pages live and read visible HTML. Fast, server-rendered pages with clear headings are easier for every engine to retrieve, understand, and quote accurately.
Is Core Web Vitals a major ranking factor?
Core Web Vitals are a confirmed part of Google's page experience signals, but relevance and content quality matter more. A fast page with weak content will not outrank a helpful, slower one. Treat good vitals as a tie-breaker and a conversion booster. Aim for LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1.
What is the most common technical SEO mistake?
The most common mistake is redirecting old URLs to the homepage or a generic hub during a migration. Google treats these much like soft 404s, so the old rankings are lost. Each retired URL should redirect to its closest matching new page. Blocking CSS or JavaScript in robots.txt and leaving staging noindex tags live are close runners-up.
Can I do technical SEO myself?
You can handle the basics yourself with Google Search Console, a site crawler, and PageSpeed Insights. Fix broken links, submit a clean sitemap, and set one canonical version of each URL. Complex work, such as JavaScript rendering, large-scale migrations, and international hreflang, usually benefits from a specialist who has handled similar sites before.