Technical SEO
What is technical SEO?
Technical SEO is the work of making a website easy for search engines to crawl, render, understand and index. It covers site structure, robots.txt, XML sitemaps, redirects, canonical tags, HTTP status codes, page speed, mobile usability, HTTPS, structured data and JavaScript rendering. It is the foundation that on-page and off-page SEO depend on.
Think of it in the order a search engine works. First it must reach your pages: technical SEO removes crawling barriers such as broken links, server errors, robots.txt blocks and pages that no internal link points to. Then it must see the content: if you rely on JavaScript, the page has to render correctly. Then it must decide what to store: canonical tags, noindex rules, redirects and duplicate handling tell it which URLs matter. Finally, the page experience, speed, stability and mobile layout, feeds into how the page is treated in ranking.
Typical technical SEO tasks include fixing 404 errors and redirect chains, setting canonical tags on duplicate URLs, keeping a clean XML sitemap, controlling faceted navigation and parameters on big sites, adding hreflang for multi-language sites, adding structured data for rich results, and improving Core Web Vitals: LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less.
Site migrations, changing domain, platform or URL structure, are among the riskiest technical SEO projects. Without a careful redirect map, a site can lose much of its organic traffic.
Technical SEO doesn’t make a page rank by itself. A technically perfect page with weak content won’t win. But technical problems can stop excellent content from ranking at all, and on large sites a single template bug can affect thousands of URLs at once.
Why technical SEO matters
If search engines can’t crawl or index a page, nothing else you do for it counts. Technical issues are often invisible to visitors, a page looks fine in a browser but carries a noindex tag, so they can go unnoticed for months.
Technical SEO scales. Fixing a template, an internal linking pattern or a redirect rule can improve hundreds or thousands of pages in one change, which makes it high value on large sites.
It also improves the site for users. Faster pages, fewer broken links and a site that works on every phone help conversions as well as rankings.
How to do a technical SEO audit
- Crawl the whole site with an SEO crawler to collect status codes, titles, canonicals, directives and internal links for every URL.
- Check indexing in Search Console’s Page indexing report and compare with the crawl: are your important pages indexed, and are junk URLs being indexed?
- Review robots.txt and the XML sitemap. The sitemap should list only canonical, indexable 200 pages.
- Fix broken internal links, redirect chains and loops, and update links to point straight to the final URL.
- Check canonical tags and duplicates: each set of duplicate pages should point to one preferred URL.
- Test mobile usability and Core Web Vitals with Search Console’s Core Web Vitals report, PageSpeed Insights or Lighthouse.
- Check rendering for JavaScript-heavy templates with URL Inspection.
- Validate structured data with the Rich Results Test.
- Confirm the site is served over HTTPS with no mixed content and that HTTP redirects to HTTPS.
- Prioritise fixes by impact: problems on many pages or on your most valuable pages first.
Technical SEO FAQ
What is the difference between technical SEO and on-page SEO?
Technical SEO is about the site’s infrastructure: whether pages can be crawled, rendered and indexed, and how fast they are. On-page SEO is about each page’s content and HTML elements such as titles and headings.
Do I need to code to do technical SEO?
Not always. You can find most issues with crawlers and Search Console. Fixing them may need a developer or CMS settings, and understanding basic HTML helps a lot.
How often should I run a technical SEO audit?
Run a full audit at least a few times a year and after any major change such as a redesign or migration. Large sites benefit from scheduled weekly crawls.
Are Core Web Vitals part of technical SEO?
Yes. They measure loading (LCP), responsiveness (INP) and visual stability (CLS), and are part of Google’s page experience signals.
Related SEO terms
Crawling is how search engines discover pages: automated bots fetch URLs and follow the links on them to find more pages.
Indexing is when a search engine analyses a crawled page and stores it in its index, so it becomes eligible to appear in search results.
Rendering is when a search engine runs a page’s HTML, CSS and JavaScript to build the page as a browser would, so it can see the final content.
Site architecture is how a website’s pages are organised and linked together, which shapes how people and search engines find and value them.
Core Web Vitals are Google’s three metrics for real-world page experience: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
A canonical tag is a link element that tells search engines which URL is the main version of a page when duplicates exist.
An XML sitemap is a file that lists the URLs you want search engines to crawl and index, with optional last-modified dates.
An SEO audit is a review of a website’s technical health, content and links to find what holds it back in search and what to fix first.