Website Audit Checklist: What to Check and Fix First

How to prioritize a website audit checklist

An audit is only useful if it tells you what to do next. Start with the pages that matter most, such as the home page, service or product pages and contact routes. Then widen the review to templates and the rest of the site.

Sort findings into four tiers and fix them in this order:

Blocks indexing. Important pages return errors, are blocked in robots.txt, carry a stray noindex or point their canonical tag at another URL.
Affects a whole template. A broken title pattern, faulty hreflang, mixed content or a slow layout repeats on every page that uses it.
Weakens key pages. Thin copy, duplicate titles or missing internal links on the pages that earn money.
Improves presentation. Structured data, images and speed on pages that already index well.

Within each tier, rank items by pages affected and effort. For each item, keep the URL, the evidence and how you will verify the fix. Our guide to reading a website audit report explains that record.

Technical SEO checklist: crawling and indexing

These checks decide whether search engines can find and keep your pages. Confirm what Google sees with the Page indexing report and URL Inspection tool in Google Search Console.

robots.txt. Confirm /robots.txt does not block pages, CSS or scripts you need. It controls crawling, not indexing; Google notes that a blocked URL can still appear in results without a description (Google Search Central).
XML sitemap. List only canonical, indexable URLs that return a 200 status, as full absolute addresses. One file holds up to 50,000 URLs or 50 MB uncompressed. Reference it in robots.txt and submit it in Search Console (building a sitemap).
noindex. Search your templates for a noindex left over from a development copy. Google sees noindex only on pages it is allowed to crawl, and noindex rules inside robots.txt are not supported (blocking indexing).
Canonical tags. Each page should name one absolute, indexable canonical URL that returns 200. Keep canonicals, sitemap entries and internal links on one address. Google treats a canonical as a strong signal, not a command (duplicate URLs).
Redirect chains. Use permanent redirects for pages that moved, and collapse chains into one hop. Googlebot generally follows up to 10 hops, but each one slows visitors, so link straight to the final URL (redirects).
4xx and 5xx errors. Google drops URLs that keep returning 4xx codes, and persistent 5xx errors slow crawling and can eventually remove pages. Also look for soft 404s: error pages served with a 200 status (HTTP status codes).

SEO audit checklist for titles, descriptions and headings

Google may rewrite a title or build a snippet from page text. So aim for accurate, distinct metadata rather than a perfect character count.

Give every indexable page a unique, clear title that names its topic early, without the same stock phrase on every page (title links).
Write a meta description that summarizes that specific page. Google uses it only some of the time, so treat it as a draft of the snippet, not a ranking lever (snippets).
Use one clear H1 that matches the page's purpose, then headings in a logical order. Google says there is no ideal number of headings, so this is about clarity for readers and screen readers (SEO Starter Guide).
Export titles and descriptions to a spreadsheet and sort them; duplicates usually mean a template problem or two pages competing for one topic.

Website audit checklist: content, duplicates and internal links

Content checks ask whether each page deserves a place in the index. Google's helpful, people-first content guidance is a useful test: does the page offer original information?

Thin pages. Flag pages with little unique text, empty tag or archive pages, and placeholders. Improve them, merge them into a stronger page with a redirect, or add noindex.
Duplicate content. The same text under several URLs is not a penalty, but it splits signals. Choose one version and consolidate the rest with canonicals or redirects.
Crawlable links. Use <a href> links with descriptive anchor text, not script-only click handlers (crawlable links).
Click depth. Keep key pages within a few clicks of the home page; three is a common rule of thumb. Compare your sitemap with the pages your navigation links to, so orphan pages stand out.
Broken internal links. Fix links to 404 pages at the source.

Structured data and international pages

Structured data can make a page eligible for rich results. Check one page from each template with the Rich Results Test and the Schema Markup Validator. Look for invalid JSON, placeholder values and missing required fields. Markup must describe content visitors can see, and valid markup does not guarantee a rich result (structured data guidelines).

For sites in more than one language, audit hreflang (localized versions):

Each page lists itself and every alternate version, using fully qualified URLs.
Every alternate links back. Without return links, Google ignores the annotations.
The self-reference is the clean canonical URL. A common mistake starts when a page is reached through a query string, such as a tracking or ?lang= parameter. The page then names that parameter version as its own alternate. Hreflang, canonical and sitemap should share one address.
Pair only true translations, add an x-default fallback where it helps, and keep each page's canonical in the same language.

Performance, mobile and HTTPS

Core Web Vitals measure loading, responsiveness and visual stability. Google sets a target for each one, measured at the 75th percentile of real visits. A page meets Google's targets when Largest Contentful Paint is 2.5 seconds or less and Interaction to Next Paint is 200 milliseconds or less. Cumulative Layout Shift must also be 0.1 or less (web.dev).

Read field data in Search Console's Core Web Vitals report and PageSpeed Insights, then use lab tools such as Lighthouse to find causes.
On the slowest templates, look for oversized images, render-blocking scripts, third-party tags and web fonts.
Google indexes the mobile version of your pages. That means the mobile view needs the same main content, headings, structured data and metadata as desktop (mobile-first indexing).
On a real phone, check text size, tap targets, menus, forms and any content hidden behind a tap.
Serve every page over HTTPS and redirect HTTP to HTTPS in one hop. Also remove mixed content: images, scripts or styles still loaded over HTTP. Browser developer tools list them.

Images, accessibility, analytics and Search Console

Images. Give informative images short, specific alt text, and leave decorative images with empty alt. Use descriptive file names and sizes that match the layout, without keyword stuffing (image SEO).
Accessibility basics. Check color contrast, form labels, keyboard navigation, visible focus, the page language attribute and link text against WCAG. Automated checks catch only part of the picture, so also try key pages with a keyboard and a screen reader (web.dev).
Search Console. Verify the site, submit the sitemap, and review the Page indexing, Core Web Vitals and Performance reports. Inspect key URLs to see which canonical Google chose. If Bing traffic matters, add Bing Webmaster Tools too.
Analytics. Confirm the tag fires once on every template and conversions are recorded. Also check that any consent banner matches the privacy rules that apply to you, which vary by state and country.

Speed, security and accessibility checks

These checks affect every visitor, not only the search engines that send organic traffic. Google's ranking systems use Core Web Vitals, but Google says there is no single page experience signal and that it always seeks to show the most relevant content (page experience). A slow, broken or insecure landing page can also lose people before they act. Google's web.dev site collects case studies in which faster load times raised conversion rates (why speed matters).

Page speed in Google PageSpeed Insights. Test your home page and top landing pages, on mobile first. Field data shows real Chrome users over the previous 28 days. Lab data comes from one simulated Lighthouse load and helps you find causes, so the two can differ. The tool rates LCP over 4 seconds, INP over 500 milliseconds and CLS over 0.25 as poor (about PageSpeed Insights).
SSL certificate. Check when your SSL certificate expires and that it renews automatically. If it lapses, browsers warn visitors instead of showing your page. Certificates are also getting shorter lives: the CA/Browser Forum voted to cut the maximum for public certificates from 398 days to 47 days, in steps between March 2026 and March 2029 (ballot SC-081).
Broken links. Many SEO tools include a crawler that reports broken links, and the free W3C Link Checker covers a page or a small site. Search Console's Page indexing report lists URLs that returned Not found (404). Fix the links that point to them and redirect pages that moved. Google notes that a 404 is not necessarily a problem when a page was removed with no replacement (Page indexing report).
Accessibility audit. Run a basic accessibility audit against WCAG 2.2, a W3C Recommendation since October 2023. One of its new Level AA criteria asks for pointer targets of at least 24 by 24 CSS pixels, with some exceptions. Start with the W3C's Easy Checks, then try a tool from its evaluation tools list. The W3C warns that a page can pass quick checks and still have serious barriers.

Where SiteFit fits

SiteFit is our website audit tool. It produces a scored, read-only review and a report you can hand to a client, as PDF, Word or Markdown. It reads only what any visitor can request, so there is no login, add-on or script. Each audit scores fourteen areas, plus two more when your site publishes a sitemap. Its checks include robots.txt and sitemap presence, titles, descriptions, headings, structured data and image alt text, and the report adds Core Web Vitals measured the way a phone sees your site.

It is delivered as a service: we run the audit and send you the report. Know its limits. It cannot see pages behind a login, and content that appears only after JavaScript runs may not show up. Link health samples up to fifteen sitemap addresses, so it is not a full crawl. Analytics, review markup and local business markup are always scored, so a site can score low there with nothing wrong. A score orders the work; it is not a certification and does not promise rankings.

To see real output, read the SiteFit snapshot example.

Frequently asked questions

What should a website audit checklist include?

At minimum, cover crawling and indexing: robots.txt, XML sitemap, noindex, canonical tags, redirects and status codes. Then add metadata, content quality and duplicates, internal links and structured data. Include hreflang for multilingual sites, Core Web Vitals, mobile usability, HTTPS, images, accessibility basics, analytics and Search Console.

What is the difference between an SEO audit checklist and a technical SEO checklist?

A technical SEO checklist covers how search engines crawl, render and index the site: status codes, robots rules, canonicals, sitemaps, speed and HTTPS. An SEO audit checklist also covers content quality, metadata, internal linking and measurement. Most audits need both, with technical blockers fixed first.

Which website audit issues should I fix first?

Anything that stops important pages from being crawled or indexed: server errors, an accidental noindex, robots.txt blocks, wrong canonicals and broken redirects. Then template-wide problems, then content and metadata on key pages, then enhancements.

How often should I audit my website?

A full review once or twice a year suits most small sites, plus one after any redesign, platform move or URL change. Check Search Console's indexing and Core Web Vitals reports monthly; a stray noindex or a run of server errors can appear without warning.

Which free SEO tools help with a website audit?

Google Search Console covers indexing, and PageSpeed Insights covers page speed. The Rich Results Test and the Schema Markup Validator check structured data. The W3C Link Checker finds broken links, and the W3C's Easy Checks give a first accessibility review. Paid SEO tools can help on large sites, but these free ones cover the basics.

Will fixing every item on the checklist improve my rankings?

Not necessarily. Fixes remove obstacles, but rankings also depend on competition, content quality and demand. Compare the same pages over the same time windows before and after a change, and expect search data to lag.

Related guides

Explore the complete product

Read features, current access and limitations

Website Audit Checklist: What to Check and What to Fix First