Technical SEO Audits: Complete Website Audit Guide

Server error.

Repeated server errors can interfere with crawling and user access.

Do not automatically redirect every 404 to the homepage.

A relevant replacement is better when one exists.

Find Broken Internal Links

Broken internal links send users and crawlers to URLs that no longer work.

Check links pointing to:

• 404 pages

• 410 pages

• 5xx responses

• redirect loops

Fix them by:

• Updating the destination

• Restoring the missing page

• Removing the link

Important pages should not depend on broken navigation paths.

Audit Redirects and Redirect Chains

A redirect chain looks like:

URL A → URL B → URL C → URL D

Where practical, internal links should point directly to the final destination.

Google's current crawl-budget guidance specifically recommends avoiding long redirect chains because they can negatively affect crawling efficiency.

Also check for:

• Redirect loops

• HTTP → HTTPS chains

• WWW/non-WWW chains

• old migration redirects

• redirected sitemap URLs

Review Robots.txt

Robots.txt controls which URLs crawlers are allowed to request.

Audit:

• Important directories accidentally blocked

• CSS or JavaScript resources blocked

• outdated staging rules

• wildcard mistakes

• AI crawler directives

Do not use robots.txt as a substitute for noindex.

Google notes that a URL blocked by robots.txt can still potentially appear in search if Google discovers it through external links, even though Google cannot crawl the page's contents.

Audit Robots Meta Tags and X-Robots-Tag

Check for:

• noindex

• nofollow

• nosnippet

• max-snippet

• noarchive

• X-Robots-Tag headers

An accidental noindex on a valuable template can eliminate an entire page type from search.

Also remember that Google needs crawler access to read a robots meta tag.

Blocking a page in robots.txt while expecting Google to read its noindex instruction can therefore create conflicting behavior.

Audit XML Sitemaps

An XML sitemap helps search engines discover important URLs.

Audit whether URLs are:

• Canonical

• Indexable

• Returning 200

• Current

• Using correct HTTPS URLs

Remove:

• Redirected URLs

• 404s

• noindex URLs

• duplicate versions

Google recommends putting URLs you want to appear in search into the sitemap and notes that sitemap submission does not guarantee indexing.

Audit Indexation

Compare:

URLs that should be indexed

against:

URLs Google has indexed or excluded

Look for:

• Important pages excluded

• Low-value pages indexed

• Duplicate URLs

• Crawled – currently not indexed

• Discovered – currently not indexed

• Alternate pages with canonical

• Soft 404s

Do not attempt to maximize the total number of indexed URLs.

The objective is to index the right URLs.

Audit Canonicalization

A canonical URL tells search engines which page represents a group of duplicate or closely similar URLs.

Audit:

• Missing canonicals

• Multiple canonical tags

• canonical to redirect

• canonical to 404

• cross-domain canonicals

• incorrect self-canonicals

• JavaScript changing canonicals

Google currently treats redirects and rel="canonical" as strong canonical signals, while sitemap inclusion is weaker.

Google may still select a different canonical when it determines another page is more representative.

Find Duplicate and Parameter URLs

Common duplicate sources include:

• Tracking parameters

• Sorting

• filtering

• session IDs

• printer URLs

• pagination

• alternate category paths

• HTTP/HTTPS

• uppercase/lowercase variations

Determine whether each variant should be:

• Canonicalized

• redirected

• blocked from crawling

• allowed but not indexed

• preserved as a distinct indexable page

The correct response depends on the URL's purpose.

Audit Site Architecture

Website architecture determines how pages relate to one another.

Important pages should normally be accessible through logical navigation and contextual links.

A useful structure may resemble:

Homepage → Category → Subcategory → Product

or:

Homepage → Services → Individual Service

Avoid important pages buried six or seven clicks deep without a legitimate reason.

Find Orphan Pages

An orphan page has no crawlable internal link pointing to it.

Find these by comparing the crawler against:

• XML sitemap

• Analytics

• Search Console

• backlink data

• CMS exports

Then decide whether to:

• Internally link the page

• redirect it

• remove it

• intentionally leave it outside search

Audit Internal Linking

Internal links communicate:

• Discovery

• hierarchy

• context

• importance

Audit:

• Broken links

• irrelevant links

• overly deep pages

• weak anchors

• excessive links

• important pages with very few links

A page can be crawlable and indexable yet still receive very little architectural support.

Review Crawl Depth

Crawl depth measures how many link steps separate a URL from the crawl starting point.

Important pages generally should not be buried unnecessarily.

But do not treat every page deeper than three clicks as an automatic error.

Large websites naturally develop deeper structures.

The key question is:

Does the architecture reflect the page's importance?

Audit Crawl Budget When Relevant

Crawl-budget analysis is primarily an advanced concern.

Google currently recommends focusing on it mainly for very large, frequently changing, or crawl-constrained websites.

Potential crawl waste includes:

• Infinite faceted navigation

• duplicate URLs

• search pages

• session parameters

• redirect chains

• low-value URLs

For smaller sites, normal sitemap management and indexation monitoring are usually sufficient.

Audit JavaScript Rendering

JavaScript can create major SEO differences between what users initially receive and what search engines eventually render.

Compare:

• Initial HTML

• Rendered DOM

• Google URL Inspection rendering

Check whether JavaScript controls:

• Main content

• Internal links

• headings

• canonical tags

• robots directives

• structured data

Google processes JavaScript through crawling, rendering, and indexing stages.

Server-side rendering or static rendering can sometimes simplify discovery, but implementation decisions should reflect the actual application.

Audit Core Web Vitals

Current Core Web Vitals are:

Largest Contentful Paint

Target: 2.5 seconds or less

Interaction to Next Paint

Target: under 200 milliseconds

Cumulative Layout Shift

Target: below 0.1

Use field data from actual users where available.

Lab tools are excellent for diagnosis, but they represent simulated conditions.

Audit Mobile Experience

Check:

• Responsive design

• viewport configuration

• mobile navigation

• content parity

• tap targets

• intrusive overlays

• forms

• font readability

Important desktop content should not disappear from the mobile version when search engines primarily evaluate the mobile experience.

Audit Structured Data

Identify schema types currently deployed.

Validate using:

• Rich Results Test

• Schema Markup Validator

Review:

• Syntax

• Required properties

• entity relationships

• accuracy

• visible-content alignment

Google explicitly requires structured data to accurately represent the content visible on the page.

Do not add irrelevant schema solely because a tool recommends it.

Audit Hreflang and International SEO

International sites should review:

• Language codes

• region codes

• reciprocal hreflang

• self-reference

• canonical relationships

• x-default

• redirects

Hreflang problems can cause search engines to surface the wrong regional or language version.

Audit Images and Media

Review:

• Image sizes

• lazy loading

• alt text

• broken images

• crawlable image URLs

• video embedding

• media sitemaps where appropriate

Optimize heavy assets without compromising necessary visual quality.

Audit HTTPS and Security Issues

Check:

• HTTP versions

• mixed content

• expired certificates

• HTTPS redirects

• internal HTTP links

Every canonical indexable page should normally resolve through the intended secure HTTPS version.

Audit AI Crawler Accessibility

This should now be documented explicitly.

Determine the company's intended policies for:

• Google crawlers

• search crawlers

• training crawlers

• AI search crawlers

• user-triggered agents

For example, OpenAI currently says websites seeking inclusion in ChatGPT Search summaries should allow OAI-SearchBot.

That is separate from decisions regarding crawlers used for other purposes.

Document intentional rules rather than allowing legacy robots.txt directives to determine policy accidentally.

Audit WAF, CDN and Bot Protection

Robots.txt is only one access layer.

Test whether important machine consumers are blocked by:

• Cloudflare

• Akamai

• firewalls

• rate limiting

• bot protection

• JavaScript challenges

• CAPTCHA

• authentication

A legitimate crawler that receives repeated 403 errors cannot access the content regardless of robots.txt permissions.

Audit Machine-Readable Page Structure

Review whether important information is represented through semantic page structure.

Check:

• <main>

• headings

• lists

• tables

• navigation

• links

• buttons

• labels

Avoid constructing important interactions entirely from anonymous JavaScript elements when native semantic elements are available.

Audit Technical Entity Signals

Review the technical relationships between major entities.

Examples:

Organization → Website

Person → Organization

Product → Brand

Article → Author

Service → Provider

Check whether:

• Canonical entity pages exist

• internal links reinforce relationships

• schema matches visible content

• identifiers are consistent

• breadcrumb structure is logical

Structured data provides explicit clues about page meaning, but it should reinforce real page content rather than replace it.

Analyze Server Logs for Large Websites

Log analysis shows what crawlers actually request.

Evaluate:

• Frequently crawled URLs

• rarely crawled important pages

• wasted crawl activity

• status codes

• crawler types

• crawl frequency

This is particularly valuable for:

• Large ecommerce stores

• marketplaces

• publishers

• classified sites

Technical SEO Audits for Ecommerce

Pay additional attention to:

• Faceted navigation

• product variants

• out-of-stock pages

• filters

• sorting parameters

• pagination

• discontinued products

• category canonicals

Ecommerce sites can generate far more URLs than actual products.

Technical SEO Audits for JavaScript Websites

Pay special attention to:

• Client-side routing

• rendering

• history API

• internal anchors

• canonical generation

• lazy-loaded content

• metadata

• structured data

Always verify what crawlers actually receive and render.

Technical SEO Audits Before a Site Migration

Audit before launch:

• Current URL inventory

• redirects

• canonicals

• internal links

• metadata

• structured data

• robots directives

After launch:

• Crawl old URLs

• Crawl new site

• verify redirects

• monitor Search Console

• inspect indexation

• monitor traffic

Migration auditing is substantially easier when a baseline exists before changes occur.

How to Prioritize Technical SEO Issues

Do not hand stakeholders a list of 800 crawler warnings.

Use:

Impact × Confidence × Effort

Critical

Examples:

• Entire website noindexed

• Revenue pages blocked

• Broken migration redirects

High

Examples:

• Large canonical problems

• Important orphan pages

• indexation failures

Medium

Examples:

• long redirect chains

• substantial internal linking weakness

Low

Examples:

• isolated low-value errors

This turns an audit into a roadmap.

How to Build a Technical SEO Audit Report

For every major issue, include:

Issue

What is wrong?

Evidence

Which URLs are affected?

Impact

Why does it matter?

Recommendation

What should change?

Priority

Critical, high, medium, or low.

Owner

SEO, developer, content, infrastructure, or another team.

Validation

How will you confirm the fix worked?

A raw tool export should support the audit—not become the audit.

How Often Should You Run Technical SEO Audits?

There is no universal schedule.

A practical framework:

Small Stable Website

One or two comprehensive audits per year plus monitoring.

Growing Website

Quarterly audits.

Ecommerce or Publisher

Monthly automated monitoring plus deeper periodic audits.

Major Migration

Before and immediately after launch.

Technical monitoring should also alert teams to major unexpected changes between audits.

Common Technical SEO Audit Mistakes

Treating Every Tool Warning as Important

Tools cannot determine business priorities automatically.

Looking Only at Googlebot

Modern websites may need intentional policies for multiple machine consumers.

Checking Only Robots.txt

WAF and CDN restrictions can still block crawlers.

Confusing Crawling With Indexing

A crawlable page is not necessarily indexed.

Using Robots.txt for Noindex

Use appropriate indexing controls.

Treating Canonical Tags as Commands

They are signals.

Putting Every URL in the Sitemap

Only include URLs you actually want search engines to consider.

Obsessing Over Crawl Budget on Small Sites

Most small sites have more important problems.

Using Only Lighthouse

Use real-user performance data as well.

Auditing Source HTML Without Rendering

JavaScript sites require rendered testing.

Adding Schema Everywhere

Structured data should represent visible page content accurately.

Delivering a Crawl Export as the Final Audit

Prioritization is where the audit becomes useful.

Technical SEO Audit Checklist

Before completing the audit, confirm:

• The website has been fully crawled.

• Important status-code problems are documented.

• Broken internal links are identified.

• Redirect chains and loops are reviewed.

• Robots.txt is intentional.

• Robots meta directives are reviewed.

• XML sitemaps contain appropriate URLs.

• Important pages are indexable.

• Low-value indexed URLs are identified.

• Canonical signals are consistent.

• Duplicate and parameter URLs are controlled.

• Important pages have internal links.

• Orphan pages have been reviewed.

• Crawl depth reflects page importance.

• Crawl-budget analysis has been performed when relevant.

• JavaScript rendering has been tested.

• Core Web Vitals have been reviewed.

• Mobile rendering has been tested.

• Structured data has been validated.

• Hreflang has been reviewed when applicable.

• HTTPS and mixed-content issues are resolved.

• AI crawler policies are documented.

• CDN and firewall access has been tested where relevant.

• Important pages use clear machine-readable structure.

• Major entity relationships are technically reinforced.

• Log analysis has been considered for large websites.

• Audit issues have been prioritized.

• Owners have been assigned.

• Validation steps have been documented.

Frequently Asked Questions

What Is a Technical SEO Audit?

A technical SEO audit examines whether search engines can efficiently crawl, render, understand, and index a website and identifies technical problems that may limit organic visibility.

What Does a Technical SEO Audit Include?

It typically covers crawling, indexation, robots directives, sitemaps, canonicals, redirects, internal links, Core Web Vitals, JavaScript rendering, structured data, and website architecture.

How Do You Perform a Technical SEO Audit?

Crawl the website, compare the results with Search Console and analytics data, evaluate crawling and indexing controls, inspect architecture and rendering, test performance, and prioritize discovered problems.

What Tools Are Used for Technical SEO Audits?

Common tools include Google Search Console, Screaming Frog, Sitebulb, Ahrefs, Semrush, PageSpeed Insights, Chrome DevTools, and structured-data validation tools.

How Long Does a Technical SEO Audit Take?

A small website may be reviewed relatively quickly, while ecommerce, international, JavaScript-heavy, or enterprise websites can require substantially more analysis.

How Often Should a Technical SEO Audit Be Done?

Stable small websites may need one or two comprehensive audits annually, while frequently changing or large websites benefit from continuous monitoring and more frequent technical reviews.

Does a Technical SEO Audit Improve Rankings?

An audit itself does not improve rankings. It identifies technical problems and opportunities. Search performance may improve after meaningful problems are correctly resolved.

What Is the Most Important Part of a Technical SEO Audit?

Ensuring important pages can be discovered, crawled, rendered, and indexed correctly is foundational. The most important issue varies by website.

Do Technical SEO Audits Include Core Web Vitals?

Yes. Modern audits should evaluate LCP, INP, and CLS using real-user field data when available, along with laboratory tools for diagnosing performance problems.

Should Technical SEO Audits Check AI Crawlers?

Yes, when AI-search visibility matters to the organization. A modern audit should document which AI crawlers and agents should have access and verify that robots.txt, firewalls, CDNs, and bot protections match that policy.

Final Thoughts

Technical SEO audits are no longer simply crawler checklists.

The traditional questions still matter:

Can Google crawl the page?

Can Google render it?

Can Google index it?

Is the correct URL canonical?

But a modern technical audit should go further:

Does the architecture reinforce important pages?

Can JavaScript-dependent content be interpreted correctly?

Do structured data and visible content agree?

Are performance problems affecting real users?

Do the company's crawler policies reflect how search and AI discovery work today?

The biggest mistake is treating every technical warning equally.

A good technical SEO audit does not produce the largest spreadsheet.

It identifies the handful of technical issues that create the greatest risk or opportunity, explains exactly why they matter, and gives developers a clear path to fixing and validating them.

That is the difference between a technical SEO audit and a crawler export.