Technical SEO

Technical SEO is everything that decides whether search engines can find, crawl, render and correctly index your pages. It covers crawl budget and robots directives, the XML sitemap, canonical tags, redirects, hreflang for multilingual sites, site architecture and internal linking, rendering, and page speed.

It is invisible when done well and total when done badly. Content quality is irrelevant on a page a crawler cannot reach, and no amount of link building fixes a canonical pointing at the wrong URL.

It is also the part with the highest ratio of quick wins, because most sites have accumulated years of small errors nobody has looked at: orphaned pages, redirect chains, duplicate titles, parameters generating infinite URLs.

The line between them is blurry: internal linking and structured data belong to both. On a CMS like WordPress the useful distinction is where the fix lives. A technical fix usually goes into a template and repeats across every page that uses it, while an on-page fix improves one page at a time.

We run this sequence at the start of every engagement and again after each release. It works the same on a 20-page site and on a 2,000-page one; what changes is the time each step takes.

• Start in Google Search Console: the Pages report for indexing status and the reasons pages are excluded, Crawl stats for errors, and Core Web Vitals for real user data.
• Crawl the whole site with Screaming Frog, with JavaScript rendering turned on if the site depends on it, and export status codes, redirect chains, canonicals, hreflang and directives.
• Compare the crawl with the XML sitemap. Sitemap URLs that are noindex, redirected or broken need fixing, and so do indexable pages missing from the sitemap.
• Review robots.txt and meta robots together, so nothing you want indexed is blocked and nothing blocked is expected to carry a noindex.
• Test the key templates in PageSpeed Insights on mobile and note which issues repeat across them.
• Validate structured data on one URL per template with the Rich Results Test.
• Group the findings by template, fix the template instead of individual pages wherever possible, and crawl again to confirm.

• Full crawl for status codes, redirect chains, orphaned pages and 4xx links.
• Robots.txt, meta robots and XML sitemaps saying the same thing about which pages count.
• Canonical tags pointing to the indexable version of each page.
• Hreflang pairs that are reciprocal and point only to indexable pages.
• Internal links that stay inside the right language and section.
• Rendering and Core Web Vitals on mobile.

AI systems can only cite pages they can retrieve. Google’s AI Overviews and AI Mode draw on Google’s index, so a page that is not indexed cannot appear there. ChatGPT and Perplexity use their own crawlers (OAI-SearchBot for OpenAI search, PerplexityBot for Perplexity), which follow robots.txt like Googlebot does. Blocking them by accident, or showing key content only through JavaScript that a simpler crawler may not execute, keeps those pages out of their answers.

For local businesses, technical SEO means location pages that load fast on mobile, consistent name, address and phone in the markup, and a structure where every area page is linked from the rest of the site. A location page that exists only in the sitemap, with no internal links pointing to it, sends a weak signal about how much it matters.

1. Small business.A site with 20 pages can still have a wrong canonical or a blocked folder. One careful audit usually finds the issues that matter, and they are often quick to fix.
2. E-commerce.Filters, sorting parameters, out-of-stock products and pagination generate huge numbers of URLs. Technical SEO decides which of them get crawled and indexed.
3. Multilingual site like ours.Hreflang, language-specific internal links and translated slugs add a layer of errors that single-language sites never face, as our own audit showed.
4. Local service business.Location pages built from one template share every template error, so a single fix improves all of them at once.

If you are unsure where to start, the Pages report in Search Console is the quickest signal. A growing list of excluded pages, with reasons you did not expect, usually means something technical changed.

• Setting pages to noindex without updating the hreflang and sitemap entries that reference them.
• Hardcoding buttons and template links to one language on a multilingual site.
• Linking to scheduled content before it goes live.
• Running one audit at launch and never again, while every theme and plugin update adds new issues.

A technical audit is the first step of our traditional SEO work. If you want technical, content and AI visibility handled together, see our SEO 360 service.