What Is Technical SEO and How to Audit It

Technical SEO is the practice of making a website easy for search engines to crawl, index, render and understand. It is not about the words on the page or the links pointing to it — it is about the underlying mechanics: whether a search engine can discover your pages, access them, make sense of their code, and add them to its index. It spans crawlability, indexability, site architecture, page speed, mobile-friendliness, HTTPS, structured data, and the configuration of sitemaps and robots.txt. This guide explains what each piece means, why technical SEO is the foundation everything else sits on, and how to run a practical audit — with the specific tool for each check.

It connects tightly to the rest of on-page SEO, so it pairs well with how to write a title tag and meta description and the indexing concepts in what are canonical tags and how to use them.

What technical SEO actually is

It helps to picture how a search engine works. First it crawls — sends automated bots to follow links and discover pages. Then it renders — processes the page's HTML, CSS and JavaScript to see what a user would see. Then it indexes — stores and understands the page so it can be retrieved for relevant queries. Only pages that survive all three stages can rank. Technical SEO is the discipline of making sure your pages pass cleanly through every stage.

That makes it different from the other two pillars of SEO. Content is about relevance and quality — answering the query well. Off-page SEO (chiefly links and reputation) is about authority — being recognised by others. Technical SEO is about access and comprehension — making the content reachable and interpretable in the first place. You need all three, but technical SEO comes first in a logical sense, because the best content in the world cannot rank if the engine cannot crawl it, render it, or index it.

Why it matters: the silent ceiling

Technical problems rarely announce themselves. A page with a stray noindex tag does not throw an error — it just quietly never appears in search. A site that takes eight seconds to load does not break — it just loses rankings and users. A JavaScript-only page that a crawler cannot render looks fine to you in your browser but is blank to the engine. These issues form a silent ceiling on performance: you can pour effort into content and links, but if a technical fault is capping the page, that effort is wasted.

This is why a technical audit is so valuable. It surfaces the invisible obstacles — the blocked directories, the broken canonicals, the render failures, the crawl traps — that hold a site back without anyone noticing. Fixing them does not always feel glamorous, but it often unlocks the latent value of content and links you have already created.

The areas technical SEO covers

Before the audit checklist, here is the territory, area by area.

Crawlability is whether search engines can discover and access your pages. It is governed by internal linking (can bots reach every important page by following links?), robots.txt (which directories you allow or block), and the absence of crawl traps (infinite URL spaces that waste crawl budget).

Indexability is whether, having crawled a page, the engine is allowed and able to index it. It is governed by noindex tags, canonical tags, HTTP status codes, and duplicate-content handling.

Site architecture is how your pages are organised and linked. A shallow, logical structure — important pages a few clicks from the home page, related content interlinked — helps engines understand relationships and distribute authority.

Page speed and Core Web Vitals measure how fast and stable the page loads and responds. Google uses these as page-experience signals.

Mobile-friendliness matters because Google indexes the mobile version of your site first (mobile-first indexing). The page must work well on a phone.

HTTPS is secure, encrypted delivery. It is a baseline trust and ranking signal; modern sites should serve everything over HTTPS.

Structured data is machine-readable markup (schema) that helps engines understand and enrich your content.

Sitemaps and robots.txt are the explicit instructions you give crawlers about what to find and what to ignore.

How to audit each area, and with what tool

An audit is most efficient when you walk these areas in a logical order — from discovery through to meaning — and use the right tool for each. The table below is the backbone of a practical technical SEO audit.

Area	What to check	Tool
Crawlability	robots.txt rules, internal links reaching key pages, no crawl traps	Screaming Frog; robots.txt tester
Indexability	noindex tags, canonical tags, indexed-page count, coverage errors	Google Search Console (Pages report, URL Inspection)
Site architecture	click depth, orphan pages, internal-link distribution	Screaming Frog (crawl depth, inlinks)
Rendering / JavaScript	does content appear without JS; rendered vs raw HTML	GSC URL Inspection ("view rendered"); Screaming Frog rendering
Mobile-friendliness	responsive layout, tap targets, no horizontal scroll	GSC; manual device testing
Page speed / Core Web Vitals	LCP, INP, CLS; field and lab data	PageSpeed Insights; GSC Core Web Vitals report
HTTPS / security	HTTPS everywhere, valid certificate, no mixed content	Browser dev tools; SSL check
Structured data	valid schema, correct types, no errors	Rich Results Test; Schema validator
Sitemaps & robots	sitemap submitted, accurate, referenced in robots.txt	Google Search Console (Sitemaps)
Redirects & errors	404s, redirect chains, soft 404s, server errors	Screaming Frog; GSC Pages report

The pattern is clear: Google Search Console is your source of truth for how Google actually sees your site (indexing, Core Web Vitals, mobile usability), a crawler like Screaming Frog gives you a site-wide structural X-ray, and PageSpeed Insights drills into speed. With those three you can run a thorough audit for free.

Walking the audit in order

1. Discovery: robots.txt and the sitemap

Start at the front door. Open your robots.txt and confirm you are not accidentally blocking important sections — a misplaced Disallow: / is a catastrophe that hides the whole site. Confirm your XML sitemap exists, lists your canonical URLs, and is submitted in Search Console. The deeper treatment is in how to write a robots.txt file and how to create an XML sitemap and submit it. These two files are how you tell crawlers what to find and what to skip, so they are the right place to begin.

2. Indexing: coverage, canonicals and noindex

In Search Console, open the Pages report (formerly Coverage). It tells you which pages are indexed and, crucially, which are not and why — "excluded by noindex," "duplicate without canonical," "crawled but not indexed," and so on. Investigate anything important sitting in the not-indexed buckets. Check that key pages do not carry stray noindex tags, and that their canonicals point where you intend. Canonical mistakes are a frequent, quiet cause of lost indexing — see what are canonical tags and how to use them for the failure modes.

3. Rendering: does the page work without JavaScript?

Modern sites lean heavily on JavaScript, but not every crawler executes it reliably, and rendering costs the engine time. Use Search Console's URL Inspection to view the rendered HTML Google sees, and compare it to the raw source. If your main content only appears after JavaScript runs, you risk it being missed or delayed. Server-side rendering or static generation is the safest route. This matters doubly for AI engines, many of which fetch raw HTML.

4. Speed and Core Web Vitals

Run your key page types through PageSpeed Insights, and read the Core Web Vitals report in Search Console for field data across the site. The three metrics are Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). Each has its own deep guide: LCP, INP and CLS. Speed is both a ranking signal and a user-experience issue, and it overlaps with sustainability — a lighter page is faster and greener.

5. Mobile-friendliness

Because Google uses mobile-first indexing, the mobile version of your site is the version that counts. Confirm your pages are responsive, that tap targets are not cramped, that text is readable without zooming, and that there is no horizontal scrolling. Test on a real device, not just a desktop browser resized.

6. HTTPS and security

Confirm the whole site is served over HTTPS, that the certificate is valid and not near expiry, and that there is no "mixed content" (secure pages loading insecure resources, which browsers flag). HTTPS is a baseline expectation — see what is HTTPS and why your site needs it. It is a lightweight ranking signal and, more importantly, a trust signal users and engines both expect.

7. Structured data

Validate your schema with Google's Rich Results Test and a schema validator. Confirm the types are appropriate (Article, FAQPage, Organization, Product, and so on) and error-free. Structured data does not directly raise rankings, but it helps engines understand and enrich your content, and it can earn rich results. Start with the highest-leverage types — see what is schema markup and which types you need.

8. Errors and redirects

Finally, crawl the site to catch the housekeeping issues: broken links (404s), redirect chains (A redirects to B redirects to C, wasting crawl budget), soft 404s (pages that return 200 but say "not found"), and server errors (5xx). These degrade crawl efficiency and user experience. A crawler surfaces them at scale in a single pass.

Site architecture and internal linking

Architecture deserves a closer look because it influences both crawlability and how authority flows. A good structure is shallow and logical: your most important pages should be reachable within a few clicks of the home page, and related pages should link to each other. Bots discover pages by following links, so an orphan page (one nothing links to) may never be crawled. Internal linking also distributes ranking signals — linking from strong pages to important ones passes authority. When you audit, look for excessive click depth, orphan pages, and important pages with too few internal links pointing at them. A clean architecture is one of the most underrated technical SEO assets.

Crawl budget: when it matters

For most small and medium sites, crawl budget — the amount of crawling Google allocates to your site — is not a constraint; Google will happily crawl a few hundred or few thousand pages. It becomes a real concern for large sites (tens of thousands of URLs or more), where crawl traps, infinite parameter spaces, and masses of low-value pages can waste the budget on junk and starve your important pages of crawling. If you run a large site, watch the Crawl Stats report in Search Console, block low-value URL patterns, fix redirect chains, and keep your sitemap clean so crawlers spend their budget where it counts.

The technical SEO and GEO overlap

Here is the strategic bonus that mirrors the rest of modern SEO: the technical health that helps Google also helps AI answer engines. ChatGPT, Perplexity, Google AI Overviews and Copilot must crawl and render your pages before they can cite them. If a page is blocked in robots.txt, returns errors, or hides its content behind JavaScript an engine does not execute, it cannot be cited — exactly as it cannot be ranked. So crawlability, clean rendering, speed and valid structured data are the shared foundation beneath both classic search and AI visibility. If AI citations are a goal, start by confirming the technical basics, then layer on the GEO-specific work in how to check if your site is ready for AI search.

Common technical SEO mistakes

A handful of errors recur across audits. Accidentally blocking pages in robots.txt or with noindex, hiding content from search entirely. Canonical mistakes — pointing canonicals at the wrong URL, or at the homepage site-wide. Render-blocking JavaScript that leaves crawlers seeing a blank page. Redirect chains and broken links that waste crawl budget and frustrate users. Ignoring mobile when mobile is the indexed version. Slow Core Web Vitals treated as a "later" problem. And sitemap/robots/canonical signals that disagree with each other, confusing engines about which version of a page to trust. Most of these are invisible in a browser and only surface in an audit — which is precisely why the audit matters.

A technical SEO audit checklist

• Confirm robots.txt does not block important sections.
• Confirm an accurate XML sitemap is submitted in Search Console.
• Review the Pages report for not-indexed pages and fix the important ones.
• Check canonicals point to the right, live, indexable URLs.
• Verify key content renders without JavaScript; compare rendered vs raw HTML.
• Confirm the site is mobile-friendly (mobile-first indexing).
• Measure Core Web Vitals (LCP, INP, CLS) and fix failing pages.
• Serve everything over HTTPS with a valid certificate and no mixed content.
• Validate structured data with the Rich Results Test.
• Crawl for 404s, redirect chains, soft 404s and server errors.
• Audit site architecture: click depth, orphan pages, internal links.
• Confirm AI crawlers can also reach and render your pages.

Where to start if you only do a few things

If a full audit feels daunting, start where the silent ceilings hide. First, open Search Console's Pages report and the URL Inspection tool, and confirm your important pages are actually indexed and that Google sees the content you expect — this catches the most damaging issues (blocked, noindexed, mis-canonicalised, or unrendered pages) fastest. Second, run your main page types through PageSpeed Insights and fix the worst Core Web Vitals failures, since speed touches rankings, users and AI alike. Third, crawl the site with Screaming Frog to sweep up broken links, redirect chains and orphan pages. Those three passes — verify indexing, fix speed, sweep structural errors — resolve the majority of technical SEO problems for most sites, and they are exactly the foundation that makes your content and links able to perform.

Go deeper

• Control crawling: how to write a robots.txt file.
• Get pages discovered: how to create an XML sitemap and submit it.
• Avoid indexing traps: what are canonical tags and how to use them.
• Speed it up: Core Web Vitals explained.

Want crawlability, speed, HTTPS and structured-data issues flagged in one pass? Analyse any URL with StackOptic — one report covering technical SEO, performance, security and AI-readiness, free, no sign-up.