An SEO audit checklist is a fixed order of checks that tells you why a site is or is not getting search traffic. Start with whether Google can crawl and index your important pages, then check site structure, on-page basics, content, speed and links, and finish by turning what you found into a short, prioritized fix list. The order matters: there is no point polishing title tags on pages Google has never indexed.
This guide walks through each step with what to check, which free tool to use, and what a real problem looks like. You can run it on a small business site in an afternoon.
You do not need an expensive tool stack to work through this SEO audit checklist. For most sites this is enough:
- Google Search Console, verified for the domain property so you see every subdomain and protocol.
- A crawler such as Screaming Frog SEO Spider. The free version handles small sites; check its current URL limit before you start.
- PageSpeed Insights for speed and Core Web Vitals.
- A spreadsheet with four columns: issue, affected URLs, impact (high, medium, low) and owner.
Write down the pages that matter most to the business before you crawl anything: the home page, service or product pages, and the posts that bring in leads. Every finding gets judged against that list.
Step 1: Check crawlability (robots.txt and server responses)
Open yourdomain.com/robots.txt in a browser. Read every Disallow line and ask whether it blocks anything you want in search. A leftover rule from a staging site, such as a blanket Disallow for the whole site, is one of the most damaging and easiest mistakes to find.
Next, run your crawler across the whole site and sort by status code:
- 4xx errors on pages that other pages still link to. Fix the link or redirect the URL to its closest replacement.
- 5xx errors, even occasional ones. These mean the server failed, and Google slows down crawling when it keeps seeing them.
- Redirect chains, where one URL redirects to another that redirects again. Point the first URL straight at the final one.
Do not assume a URL is fine because it works for you in a browser. On growthscribe.com we found that the XML post sitemap was returning a 500 error. PHP was running out of memory while building one very large sitemap page. Splitting it into smaller sitemap pages fixed it, but we only spotted it because we checked the sitemap response directly instead of trusting the plugin.
Step 2: Check indexing in Google Search Console
Open the Pages report under Indexing. It splits URLs into indexed and not indexed, with a reason for each group. Go through every reason and decide whether it is expected or a problem.
Many statuses are normal. “Alternate page with proper canonical tag” usually means things are working; we explain when it needs action in our guide to the alternate page with proper canonical tag status. Other statuses are worth a closer look:
- Excluded by noindex tag: check that none of your key pages are in this list. Page builders and SEO plugins sometimes set noindex on templates by accident.
- Crawled, currently not indexed: Google saw the page and chose not to index it. This often points to thin or near-duplicate content.
- Page with redirect: usually harmless, but look at the URL patterns. On our own site this group was mostly
?filter-parameter URLs, which we now block in robots.txt so Google stops spending time on them.
Then submit or check your XML sitemap in the Sitemaps report. It should list only indexable, canonical URLs that return a 200 status. A sitemap full of redirects or noindexed pages sends Google mixed signals.
Finally, use the URL Inspection tool on your top five pages. Confirm each one is indexed, and that the Google-selected canonical matches the URL you expect.
Step 3: Review site structure and internal links
Good structure means important pages are close to the home page and linked from relevant content. In your crawler, look at:
- Click depth: key pages should be reachable in a few clicks from the home page. Pages buried deep tend to be crawled less.
- Orphan pages: pages in your sitemap that no other page links to.
- Internal links to redirects or errors: update them to point at the final URL.
Also check that your URLs are readable and consistent. Pick one version of the site (https, with or without www) and make sure every other version redirects to it in a single hop.
Step 4: Audit on-page basics
Export titles, meta descriptions and H1s from your crawler and sort them. You are looking for patterns, not perfection:
- Missing or duplicate title tags across different pages.
- Titles that do not mention what the page is about.
- Pages with no H1, or several H1s competing with each other.
- Images on important pages with no alt text.
- Two or more pages targeting the same main keyword.
That last one matters more than people think. We use one main keyword per page so our own pages do not compete with each other. If two pages chase the same query, decide which one should rank, merge or differentiate the other, and link between them.
Step 5: Check content quality on the pages that matter
Take your list of important pages and read each one as a customer would. Ask:
- Does the page answer the question someone searching for it actually has?
- Is there a clear next step, such as a contact form, a price request or a product to buy?
- Is anything out of date: old offers, discontinued services, broken screenshots?
- Is there obvious duplication, such as dozens of near-identical location or tag pages?
Pull the Performance report in Search Console and filter by page. A page with many impressions and few clicks often has a weak title or a mismatch with search intent. A page with almost no impressions may not be targeting a query anyone searches for.
Step 6: Test speed and Core Web Vitals
Open the Core Web Vitals report in Search Console first. It uses real user data and groups URLs with similar problems, which is more useful than testing pages one at a time. Then run a few representative pages through PageSpeed Insights: the home page, a service or product page, and a blog post.
Note which metric fails on which template. A slow hero image, a layout that jumps while ads or fonts load, or a heavy script that delays clicks each needs a different fix. Our guide on how to improve Core Web Vitals covers those fixes in detail, so in the audit you only need to record what fails and where.
Check mobile too. Open your key pages on a phone and try to use them. Tiny tap targets, pop-ups that cover the content and text that needs zooming are all worth logging.
Step 7: Check structured data and links
Run key pages through Google’s Rich Results Test. Look for errors in any schema you already use, such as Organization, Product, Article or FAQ markup. If you run several sites or brands, make sure the same organization is described consistently. We link Organization and Person schema with @id references across our sites so search engines see one entity, not several.
For external links, you do not need a huge backlink report. Check that your most-linked pages still exist and return a 200 status. If an old page with good links now returns a 404, redirect it to the most relevant live page.
Step 8: Turn your SEO audit checklist into a fix list
An audit is only useful if someone acts on it. Score each issue in your spreadsheet on two things: how many important pages it affects, and how badly it blocks search visibility. Then sort.
- Blockers: anything stopping key pages from being crawled or indexed.
- High-value fixes: problems on pages that already get impressions, such as weak titles or slow templates.
- Structural work: internal linking, merging competing pages, fixing redirect chains.
- Clean-up: missing alt text, minor warnings, cosmetic issues.
Assign each item an owner and a date. Re-crawl after fixes go live and use the Validate Fix button in Search Console where it applies.
Common audit mistakes to avoid
- Treating every crawler warning as urgent. Tools flag hundreds of things. Most do not affect rankings.
- Auditing without business context. A problem on a page nobody visits matters less than a small issue on your best service page.
- Skipping the live check. Plugins and dashboards can say everything is fine while the actual URL returns an error, as our sitemap problem showed.
- Fixing and never re-checking. Re-crawl and confirm.
Keep a copy of this SEO audit checklist with your spreadsheet so the next audit follows the same order and you can compare results over time.
If the audit turns up server errors, indexing problems or template-level speed issues that you cannot fix in your CMS settings, that is usually the point to bring in a technical SEO team who can work at the server and code level.
FAQ
How often should I run an SEO audit?
Run a full audit once or twice a year and after any big change such as a redesign, migration or new CMS. Between full audits, check the Pages and Core Web Vitals reports in Google Search Console every month so problems do not pile up.
Can I do an SEO audit for free?
Yes. Google Search Console, the URL Inspection tool, PageSpeed Insights and the free tier of a crawler such as Screaming Frog cover most of this checklist for a small site. Paid tools mostly save time on large sites.
What should I fix first after an audit?
Fix anything that stops important pages from being crawled or indexed first, such as a wrong noindex tag, a robots.txt block or a broken sitemap. Then fix problems on pages that already get impressions, and leave cosmetic warnings for last.
Is an SEO audit the same as a technical SEO audit?
Not quite. A technical audit focuses on crawling, indexing, speed and site structure. A full SEO audit also looks at content, keyword targeting and links. This checklist covers both, starting with the technical layer because content cannot rank if Google cannot index it.
