Website Audit Template: Complete SEO & Technical Checklist

A website audit template gives you a repeatable system for finding technical SEO problems, indexing errors, weak content, slow pages, broken links, missing metadata, poor user experience and other issues that may prevent a website from reaching its full potential.

Instead of randomly checking pages and writing problems in different documents, a good website audit template organizes every finding into a structured workflow.

At minimum, your audit should record:

The downloadable checklist included with this guide follows the same practical idea: find the issue, measure its importance, document the evidence, fix it and verify the result.

That last step matters.

A website audit is not finished when you discover 50 problems.

It is finished when the important problems have been corrected and tested again.

What Is a Website Audit?

A website audit is a systematic review of the technical, search, content, performance, usability and authority signals affecting a website.

Think of it like a health check for your site.

You inspect how search engines access the website, how users experience it and whether each important page is doing the job it was created to do.

A complete website audit normally examines areas such as:

Crawling → Indexing → Technical SEO → On-page SEO → Content → Internal Links → Images → Performance → Mobile → Security → Backlinks → Analytics → Conversions

The purpose is not to produce the longest possible list of errors.

The purpose is to identify which problems are actually preventing growth.

For example, fixing ten missing image alt attributes may be useful, but repairing an accidental noindex directive on your primary service page is usually far more urgent.

That is why every finding in this website audit template receives a priority.

Free Website Audit Template: How to Use It

The easiest way to use the template is to audit one category at a time.

Do not start changing things while you are still discovering problems.

First collect the evidence.

Then prioritize.

Then fix.

Then retest.

For every row, use one of these statuses:

For importance, use:

This simple distinction can prevent one of the biggest audit mistakes: treating every issue as equally important.

Website Audit Checklist Overview

A complete website audit can be divided into these major sections:

Now let us audit each category properly.

1. Website Analytics and Search Console Audit

Before analyzing rankings or traffic, make sure measurement works.

You need reliable data.

Check whether your analytics platform is correctly installed and whether important events are being tracked.

For most SEO projects, you should also have access to Google Search Console.

A simple website audit should answer:

Without reliable measurement, it becomes difficult to know whether the changes made after an audit actually improved anything.

2. Crawlability Audit

Search engines need to discover and access a URL before they can properly process it.

Start by crawling the website with a crawler or auditing your most important URLs manually.

Check the HTTP response.

A normal indexable page should generally return:

200 OK

You should investigate URLs returning:

3xx redirects
404 Not Found
410 Gone
5xx server errors

A redirect is not automatically bad.

The problem appears when redirects are unnecessary, broken or chained.

For example:

Page A → Page B → Page C → Final Page

is less efficient than:

Page A → Final Page

Your website audit template should therefore include checks for redirect chains and loops.

3. Indexing Audit

A page being crawlable does not automatically mean it is indexed.

Important URLs should be reviewed in Search Console or another reliable indexation workflow.

Start with pages that matter commercially:

homepage, service pages, product pages, category pages, important articles and high-traffic landing pages.

Check whether an important URL accidentally contains:

<meta name="robots" content="noindex">

You should also inspect HTTP headers when necessary because indexing instructions can be delivered with X-Robots-Tag.

One technical detail is especially important: if a URL is blocked through robots.txt, Google may not be able to crawl the page to discover a noindex directive placed inside it.

Your audit should therefore separate:

crawler blocking

from:

indexing control

They are not the same thing.

4. Robots.txt Audit

Open:

https://example.com/robots.txt

Look for accidental blocks.

For example:

User-agent: *
Disallow: /

would prevent compliant crawlers from accessing the entire site.

That may be intentional on a staging site.

It would be disastrous on most production websites.

Your robots.txt audit should verify that important sections are accessible while unnecessary or problematic crawler paths are controlled appropriately.

Also check whether the sitemap location is referenced when useful:

Sitemap: https://example.com/sitemap.xml

5. XML Sitemap Audit

A sitemap helps search engines discover the URLs that you consider important.

Your sitemap should generally contain canonical, indexable URLs that you actually want search engines to process.

Avoid filling it with:

redirected URLs, 404 pages, noindex pages, duplicate URLs or irrelevant parameter variations.

For large websites, remember that one sitemap file is limited to 50,000 URLs or 50 MB uncompressed, after which a sitemap index can be used.

Check:

6. Canonical Tag Audit

Canonicalization tells search engines which URL you prefer when multiple URLs contain duplicate or very similar content.

An HTML canonical looks like:

<link rel="canonical" href="https://example.com/preferred-page/">

For an ordinary unique page, the canonical will often point to itself.

For example:

Current URL:
https://example.com/seo-guide/

Canonical:
https://example.com/seo-guide/

Audit for:

missing canonicals, canonicals pointing to 404 pages, canonicals pointing through redirects, conflicting canonicals, duplicate pages using different canonical targets and pages where Google chooses a different canonical than you expected.

Redirects and rel="canonical" are strong canonicalization signals, while sitemap inclusion provides an additional weaker signal.

Do not blindly add canonical tags everywhere without understanding the relationship between the URLs.

7. URL Structure Audit

A good URL should be understandable.

Compare:

example.com/page?id=9317&cat=11

with:

example.com/website-audit-template/

The second version gives users and search engines more context.

Audit URLs for unnecessary parameters, excessive folders, inconsistent capitalization, duplicate trailing-slash versions and meaningless IDs when cleaner URLs are practical.

Do not change existing URLs simply because they are not perfect.

Changing a ranking URL creates migration work.

Only change it when the benefit justifies the risk, and redirect the old URL properly.

8. Website Architecture Audit

Site architecture determines how easily users and crawlers can reach important content.

Your highest-value pages should not be hidden behind ten clicks.

A simple hierarchy might be:

Homepage
   ↓
Category
   ↓
Subcategory
   ↓
Article or Product

Inspect navigation menus, category structures, breadcrumbs, contextual internal links and orphan pages.

An orphan page is a URL with no meaningful internal links pointing to it.

It may exist in a sitemap but remain disconnected from the normal website structure.

Those URLs deserve investigation.

9. Title Tag Audit

Every important indexable page should have a useful <title>.

Example:

<title>Website Audit Template: Complete SEO Checklist</title>

Avoid generic titles such as:

<title>Home</title>

or:

<title>Page 1</title>

Also look for duplicate titles across many URLs.

There is no fixed Google rule requiring titles to stay under exactly 60 characters. Google recommends descriptive, concise titles and may truncate title links depending on the device and available display width.

So audit titles for clarity and uniqueness, not an arbitrary character counter alone.

10. Meta Description Audit

Every important landing page should ideally have a useful description that summarizes why someone should click.

For example:

<meta name="description"
content="Download our website audit template and check technical SEO, content, Core Web Vitals, links, indexing and more.">

Do not stuff keywords.

A meta description should function like SERP advertising copy.

There is also no fixed official maximum length that guarantees Google will display the complete description. Search snippets can be truncated based on available space, and Google may generate a snippet from page content when it better matches the query.

The important checks are:

unique, relevant, accurate and click-worthy.

11. Heading Structure Audit

Every page should have a clear visual and semantic structure.

A simple structure might look like:

H1: Website Audit Template
   H2: Technical SEO Audit
      H3: Canonical Tags
      H3: XML Sitemap
   H2: Content Audit
      H3: Search Intent
      H3: Duplicate Content

The goal is not to satisfy a robotic rule about the exact number of headings.

The goal is to make the document easy to understand.

Check for missing primary headings, confusing hierarchy, headings being used only for styling and pages where the main topic is unclear.

12. Keyword and Search Intent Audit

A page should have a clear reason to exist.

Ask:

What query or user problem is this page trying to satisfy?

Then analyze the search results for that topic.

Determine whether users expect an informational guide, commercial comparison, product, category, tool, service or local result.

For example, someone searching:

website audit template

likely wants something they can actually use.

An article that spends 4,000 words explaining audits but provides no usable template may satisfy the query poorly.

That is why this page combines the explanation with a practical audit framework.

When researching new SEO opportunities, you can also use our free KGR Checker to compare search demand with title-level competition.

13. Content Quality Audit

Do not judge content only by word count.

Ask whether the page actually solves the user's problem.

Check for:

outdated information, unsupported claims, duplicate paragraphs, thin pages, keyword cannibalization, generic AI-generated filler, inaccurate instructions and sections that add no value.

You should also evaluate whether an expert could improve the page with:

real examples, original screenshots, first-hand observations, data, comparison tables, calculations, demonstrations or unique experience.

A 1,200-word article that completely answers the query can outperform a useless 5,000-word article.

Content depth should follow the complexity of the problem.

14. Duplicate Content Audit

Duplicate content becomes problematic when multiple URLs compete to represent the same information.

Common causes include:

parameter URLs, HTTP and HTTPS variants, www and non-www versions, printer pages, tag archives, filtered ecommerce URLs and copied product descriptions.

Do not simply delete every duplicate URL.

First determine why it exists.

Then decide whether the correct solution is a canonical, redirect, noindex, consolidation or simply leaving the URL alone.

15. Internal Link Audit

Internal links help users move between related pages and help crawlers understand your website structure.

Audit:

anchor text, broken internal links, orphan pages, unnecessary redirecting links, pages receiving almost no internal links and important pages buried deep in the architecture.

Compare:

click here

with:

technical SEO audit checklist

The second anchor provides more context.

However, do not force exact-match keywords into every link.

Internal linking should remain natural.

If you publish SEO content with AI-assisted workflows, our detailed Agility Writer review also demonstrates how content planning, internal linking and optimization can fit into a larger publishing process.

16. Broken Link Audit

Broken links hurt usability and can waste crawling.

Look for links returning:

404
410
5xx

For every broken link decide whether you should update the destination, remove the link or redirect the old target.

Do not create a redirect simply because a 404 exists.

A 404 is perfectly valid when a resource has genuinely disappeared and no useful replacement exists.

17. External Link Audit

External links should support the user's experience.

Review whether linked resources still exist and whether your page is pointing users to unreliable or irrelevant destinations.

Also audit appropriate link attributes.

Examples include:

rel="nofollow"
rel="sponsored"
rel="ugc"

Use them according to the nature of the relationship rather than automatically adding nofollow to every external link.

18. Structured Data Audit

Structured data can help search engines understand specific entities and content types.

Common examples include:

Article
Product
Organization
LocalBusiness
BreadcrumbList
WebApplication
Recipe
Event

Use schema only when it accurately describes visible page content.

Do not create fake ratings or misleading markup simply because you want a richer search result.

Google currently recommends JSON-LD when practical and requires structured data to represent the actual visible content of the page. Correct markup can make a page eligible for certain search features, but does not guarantee they will appear.

Validate important markup after implementation.

19. Image SEO Audit

Images should be treated as part of website performance and search visibility.

Check image filenames, dimensions, compression, loading behavior and alternative text.

Instead of:

IMG_82919.jpg

use something meaningful when appropriate:

website-audit-template-dashboard.webp

Alt text should describe the purpose or content of an image when alternative text is useful.

Do not keyword-stuff it.

You should also define image dimensions whenever practical because reserving layout space can reduce unexpected movement while the page loads.

20. Core Web Vitals Audit

Performance should be evaluated with real metrics rather than a vague statement such as:

“The website feels fast.”

The current Core Web Vitals are:

These thresholds are evaluated using real-world user experience, with the 75th percentile being important when assessing performance at scale.

LCP

Largest Contentful Paint measures how quickly the main visible content appears.

Typical LCP problems include oversized hero images, slow server response, render-blocking resources and heavy JavaScript.

INP

Interaction to Next Paint measures responsiveness when users interact with the page.

Heavy JavaScript, long main-thread tasks and inefficient event handling can hurt INP.

CLS

Cumulative Layout Shift measures unexpected visual movement.

Common causes include images without defined dimensions, ads loading into unreserved space and elements inserted above existing content.

21. Page Speed Audit

Do not optimize speed simply to turn a performance score from 98 to 100.

Prioritize improvements users can actually feel.

Common areas to inspect include server response, caching, JavaScript execution, CSS delivery, image formats, lazy loading, fonts, third-party scripts and CDN configuration.

Compare laboratory results with real-user data whenever possible.

A synthetic test represents a controlled environment.

Real-user performance tells you what visitors are actually experiencing.

22. Mobile Website Audit

Mobile auditing remains essential, but old checklists often mention Google's discontinued Mobile-Friendly Test.

That particular test was retired in December 2023.

Today, inspect mobile behavior using responsive browser testing, Lighthouse, Chrome DevTools and actual devices when possible.

Check viewport configuration, navigation, buttons, font readability, horizontal scrolling, popups, form fields, sticky elements and content parity.

Do not assume responsive design automatically means good mobile UX.

A site can technically respond to screen width while still being painful to use.

23. HTTPS and Security Audit

Every production website should use HTTPS.

Audit whether HTTP versions redirect correctly to HTTPS.

For example:

http://example.com/

should normally resolve to the preferred secure version.

Also investigate mixed content, expired certificates, insecure resources and exposed sensitive information.

For a full website audit, security can also include software/plugin updates, backups, admin access, security headers and recovery processes.

However, an SEO audit is not a substitute for a professional penetration test or security assessment.

24. Accessibility Audit

A website should remain usable for as many visitors as practical.

An initial audit can check:

form labels, keyboard navigation, focus states, text contrast, semantic HTML, alt text and understandable error messages.

Automated tools can find some accessibility problems.

They cannot prove complete accessibility compliance.

Manual testing remains important.

25. Backlink Audit

Backlinks are not simply a quantity competition.

Do not write an audit recommendation such as:

“Build 200 backlinks.”

That tells you nothing about quality.

Instead examine relevance, authority, anchor distribution, suspicious patterns and whether important pages have earned legitimate references.

A single highly relevant editorial link can be more meaningful than hundreds of automated directory links.

Avoid creating backlinks merely to manipulate rankings.

The objective should be to earn authority through genuinely useful resources, relationships, digital PR, tools, research and content that deserves to be referenced.

26. Website Conversion Audit

Traffic is not the final objective for most websites.

A website can rank well and still perform poorly as a business asset.

Audit the primary conversion path.

For a service business that might be:

Google → Service Page → Contact Form → Lead

For an ecommerce store:

Google → Product → Add to Cart → Checkout → Purchase

Check whether the call to action is obvious, forms work, contact information is accessible, trust signals are visible and important pages clearly explain what the visitor should do next.

27. Tracking and Attribution Audit

After checking conversions manually, verify that analytics records them.

Test important actions such as:

form submissions, purchases, phone-click events, email clicks, account registrations, downloads and other business-critical interactions.

A conversion that happens but is not measured makes future SEO decisions harder.

Record each broken tracking event as a separate audit item.

28. Search and AI Visibility Audit

Modern discovery goes beyond traditional blue-link search results.

Your audit can now include whether your important pages clearly identify:

the business, author, products, services, expertise and relationships between entities.

Use descriptive content, strong site architecture and accurate structured data.

Businesses targeting broader AI-driven discovery can also review our guide on getting a business recommended by ChatGPT and Google AI.

Do not create a completely separate website for “AI SEO.”

Most of the foundations remain the same: crawlable pages, strong entities, useful content, accurate information and clear relationships.

How to Prioritize Website Audit Issues

Finding an issue does not automatically make it urgent.

Use a simple formula:

Priority = Impact × Reach × Confidence

You can then consider implementation effort separately.

Imagine these findings:

This gives developers and content teams an actual roadmap.

P0 — Critical

Fix immediately.

Examples include accidental sitewide noindex, broken production website, severe security incident or incorrect redirects removing important pages.

P1 — High

Fix next.

These issues can significantly affect traffic, crawling, performance or conversions.

P2 — Medium

Important improvements that should follow critical work.

P3 — Low

Cleanup and optimization.

These tasks matter, but delaying them temporarily is unlikely to cause serious damage.

The Website Audit Template Structure I Recommend

The original five-column structure works well:

Issue
Importance
Pass / Fail
Notes
Action Items

For a professional audit, I recommend expanding it to:

This makes the spreadsheet useful for both the SEO specialist who discovers the issue and the developer or content editor responsible for fixing it.

Example of a Completed Website Audit Finding

Suppose your crawler discovers that:

https://example.com/service/

contains:

<link rel="canonical" href="http://example.com/service/">

Your audit row could look like this:

That is a real actionable finding.

Compare it with writing only:

Canonical: Fail

The second version tells your team almost nothing.

Tools You Can Use During a Website Audit

You do not need one tool that claims to do everything.

A strong audit usually combines crawler data, search data, performance testing and manual inspection.

Typical categories include:

The tool matters less than understanding the evidence it gives you.

A crawler can tell you that 500 titles are duplicated.

It cannot automatically decide whether those URLs should exist.

That still requires analysis.

How Often Should You Audit a Website?

There is no universal schedule.

A small brochure website may need fewer deep audits than a large ecommerce platform publishing and changing thousands of URLs.

A practical strategy is to perform a comprehensive audit after major events such as:

website launch, redesign, CMS migration, domain migration, large content migration, significant traffic decline or major template changes.

For ongoing SEO, automated monitoring can run much more frequently.

The goal is to find serious regressions quickly rather than discovering them six months later.

Website Audit vs SEO Audit

These terms are often used interchangeably, but there is a difference.

A website audit is broader.

An SEO audit focuses primarily on organic search performance.

The template in this guide intentionally covers both because website problems rarely exist in isolated departments.

A slow checkout page is a performance issue.

It is also a UX issue.

And potentially a revenue issue.

Common Website Audit Mistakes

The most common mistake is generating a massive list of errors without deciding what should be fixed first.

The second is trusting automated tools without verifying the problem manually.

The third is treating best-practice warnings as ranking factors.

For example, a missing meta description should be reviewed.

But that does not necessarily deserve higher priority than broken indexing on your main revenue page.

Another common mistake is recommending a CMS migration as an automatic SEO solution.

WordPress, Wix, Shopify, custom frameworks and other platforms can all perform well when configured correctly.

Changing platforms should solve a real technical, operational or business limitation.

It should not be prescribed simply because one CMS is assumed to “rank better.”

Finally, avoid backlink recommendations based solely on quantity.

“Build 200 backlinks” is not an SEO strategy.

Website Audit Final Checklist

Before marking the project complete, verify one final time that the website can be crawled, important pages are indexable, canonicals are correct, sitemaps contain the intended URLs, metadata is useful, content matches intent, internal links work, Core Web Vitals have been reviewed, mobile usability is acceptable, HTTPS works, structured data is valid where applicable, analytics is collecting data and priority fixes have been retested.

The most important word in that paragraph is:

retested.

Without verification, an audit only documents problems.

With implementation and retesting, it becomes an optimization process.

Frequently Asked Questions About Website Audit Templates

What is a website audit template?

A website audit template is a structured checklist or spreadsheet used to evaluate technical SEO, indexing, content, performance, usability, security, links and other website factors. It provides a repeatable way to record issues and track fixes.

What should a website audit template include?

At minimum, include the audit item, priority, status, notes and recommended action. A professional template should also include the affected URL, supporting evidence, issue owner, due date and retest status.

How do I audit a website?

Start by defining the audit scope and collecting baseline data. Then evaluate crawling, indexing, status codes, canonicalization, sitemaps, robots rules, site architecture, on-page SEO, content, internal links, performance, mobile usability, security, backlinks, analytics and conversions. Prioritize issues before implementing fixes.

Is a website audit the same as an SEO audit?

Not exactly. An SEO audit focuses primarily on organic search performance. A full website audit can also examine accessibility, security, conversion rate, analytics, functionality and user experience.

Can I perform a website audit for free?

Yes. Many important checks can be completed with free search-engine tools, browser developer tools, performance testing tools and manual inspection. Paid crawlers and SEO platforms become more useful when auditing large websites or automating repetitive analysis.

How long does a website audit take?

It depends on the size and complexity of the site. A small website can be reviewed relatively quickly, while an ecommerce or publishing site with thousands or millions of URLs may require sampling, crawling, log analysis and template-level investigation.

What is the most important part of a website audit?

Crawling and indexing are usually among the first areas to investigate because a beautifully optimized page provides little organic value if search engines cannot properly access or index it.

How often should a website be audited?

Run a full audit after major site changes and periodically based on the size and importance of the site. Critical SEO, uptime and performance problems can also be monitored continuously instead of waiting for the next manual audit.

What Core Web Vitals should I check?

The current Core Web Vitals are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. A good result targets LCP at 2.5 seconds or less, INP at 200 milliseconds or less and CLS at 0.1 or less.

Should every audit issue be fixed?

No. Some warnings have little practical impact. Prioritize problems based on their effect on crawling, indexing, traffic, user experience, conversions and business goals.

Final Thoughts

The best website audit template is not the spreadsheet with the most rows.

It is the template that helps you answer four questions:

What is wrong?

How important is it?

Who will fix it?

Did the fix actually work?

Use the checklist in this guide to inspect the website systematically instead of guessing.

Start with crawling and indexing.

Then review technical SEO, content, internal links, page experience, security and authority.

Finally, convert every meaningful problem into an action with a priority, owner and retest.

That turns a website audit from a document into a real growth system.