An SEO audit can uncover a problem that blocks thousands of useful pages from search. The hard part is knowing what to fix first. Use this SEO audit checklist in order, record the evidence, then rank each fix by its effect on leads, sales, or revenue. If you want to compare your own scope with what our SEO audit covers, keep that page open as a reference while you work. Below, the Kadima team shows how it connects audit findings to business goals, with results from three published case studies.
Step 1: How do you establish an SEO audit baseline and check indexation?
Start by saving a clear picture of the site before you change anything. Record organic clicks, impressions, indexed pages, key landing pages, and conversions from search. Use the same date range each time you check results. A baseline helps you tell whether a later change lines up with a change in performance.
In Google Search Console, review the Pages report and note which pages are indexed, excluded, or still waiting to be crawled. Compare those groups with a list of pages your business needs people to find. A product page marked noindex or a service page missing from the index deserves attention before a minor title edit.
Next, inspect robots.txt and your XML sitemap. Confirm that important pages and the resources needed to render them are accessible. A sitemap should point search engines toward your preferred, indexable URLs. Google explains that robots.txt controls crawling, while a noindex rule is used to keep a page out of search results. Check Google’s guidance on crawling and indexing before changing these rules.
Then check canonical tags and dead internal URLs. A canonical should point to the version you want search engines to treat as primary. Internal links should lead to working pages, not to a dead URL or a chain of redirects. For a large site, track the affected URL count and page type, not just the error total.
Here’s what that looks like at scale. On a technology ecommerce retailer with 71,000+ URLs, the audit found 50,700+ internal no-response URLs and 23,000+ missing or conflicting canonicals. After the cleanup, the site earned $599.56K in organic revenue in 6 months. The full breakdown is in our enterprise ecommerce crawl optimization case study.
Step 2: How do you audit site speed, mobile usability, and technical health?
Test the pages people use to buy, inquire, or learn. Don’t run one test on the homepage and assume the rest of the site works the same way. Check a key service page, a product or category page, and a high-traffic article. Note the device type and the page template for each result.
Use the Core Web Vitals report in Search Console to spot patterns across URLs. Then test individual pages with PageSpeed Insights. A single test can help diagnose a page, but it doesn’t stand in for how visitors experience it over time.
Check the three Core Web Vitals: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Google’s Core Web Vitals documentation describes them as measures of loading, response to interaction, and visual stability. When a page performs poorly, find the cause before asking a developer to make broad changes. A large hero image, a heavy script, or a layout shift each needs a different fix.
Test mobile pages on an actual phone as well as in a browser preview. Open the menu, tap the main call to action, and try a form. Look for text that’s hard to read, controls that are hard to tap, or content hidden under a menu.
Check HTTPS and make sure important pages load without browser security warnings. Then look at redirects, server errors, and pages that return an error while showing a normal-looking page.
Speed work pays off when it’s tied to the template behind the problem. For a paint and plaster company, speed and on-page fixes took its GTmetrix grade from C to A in 3 months, and in 6 months organic clicks rose 40% and average position improved 10.1 places. See the paint and plaster company technical and on-page SEO case study for the steps.
For a deeper look at the technical work involved, our technical SEO overview explains the types of issues an audit can uncover.
Step 3: How do you audit on-page SEO, content quality, and structured data?
Review pages against their purpose. A service page should answer a buyer’s questions and make the next step clear. A help article should solve the query it targets. If a page attracts visits but doesn’t support a useful business action, check its intent and content before you add more keywords.
For each important page, check that its title tag describes the page and stands apart from other titles. Make the meta description useful to a searcher, even though Google may choose a different snippet. Use one clear main heading, then organize subheadings so they match the page’s sections. If you’re editing snippets, preview how your title and description show in Google before you publish.
Now compare pages that target similar searches. If two pages answer the same question for the same audience, they may compete for attention and split internal links. Decide which page should own that topic. Then merge useful information, redirect an obsolete page where appropriate, or give each page a distinct purpose.
Look for thin pages that add little beyond a product name or a short sales claim. Check whether older content still answers the query and whether key facts match what the business does now. Don’t update a date alone and call the page refreshed. Add information that helps a reader make a decision, or remove the page from the plan if it no longer has a clear job.
Validate structured data against visible page content. A product page shouldn’t contain markup for details a visitor can’t see. A blog post’s structured data should describe the article on that page. Fix errors and remove duplicate markup that describes the same item in conflicting ways. Google’s introduction to structured data says markup can help it understand a page and may make it eligible for certain search features, but valid markup doesn’t guarantee a special result.
Technical and on-page fixes work best alongside new content. For a SaaS video redaction platform, a technical audit, on-page fixes and new content led to 261% more organic clicks and 268% more impressions in 6 months, as shown in the video redaction SaaS SEO case study. For teams that need a repeatable content review, our content optimization approach ties page improvements to buyer questions and useful inquiries.
Step 4: How do you review backlinks and find competitor content gaps?
Review the sites and pages that link to your domain. Look at the linking page, its topic, the anchor text, and the destination URL. A link from a relevant page can help people discover your content. A sudden group of odd links or a manual action needs a closer review, not an automatic rejection of every unfamiliar domain.
Use Search Console’s Links report to check which pages receive links and what sites link to you. Compare that list with your important pages. If a core service page has few internal or external paths leading to it, note that as a discovery issue. Treat anchor text as context, not a quota to hit.
Don’t disavow links just because a report labels them as low quality. First check for a manual action and review whether there’s a clear pattern of manipulative links. A rushed disavow can remove signals you didn’t mean to reject. If the issue is real, document the links and the reason for each action.
For competitor gaps, compare the pages that rank for searches tied to your products or services. Note topics competitors answer that your site doesn’t, then judge whether those topics match your audience and offer. A gap is a research lead, not a reason to copy a rival’s page. Prioritize gaps that can support a meaningful customer decision.
Use a short record for every finding: the affected URL, what you observed, the business impact you expect, and the person who can act on it. That record makes it easier to hand technical issues to a developer and content changes to an editor without losing the reason behind the task.
While you’re here, look for orphan pages: priority URLs that no other page on your site links to. The audit question applies on any platform. Can a user or crawler reach every priority page through useful links?
Step 5: How do you check user experience, schema, and AI search visibility?
Watch how visitors move through key pages. In Google Analytics, check organic landing pages alongside engaged sessions and the actions that matter to your business, such as a qualified form submission or a purchase. A high exit rate alone doesn’t prove a page is broken.
Test the journey yourself. Start at a search landing page, then try to reach the next step without using the site search or browser back button. Check navigation labels, internal links, forms, and error messages. If a page gets visits but few leads, compare the promise in the search result with what the page asks a visitor to do.
Recheck structured data while you’re on the page. Confirm that it matches what a visitor sees and that a theme or plugin hasn’t added a second version. If the page has an FAQ section, prepare FAQ markup that matches the visible questions word for word, then verify the result against the live page before release.
For AEO, check whether AI crawlers can access the pages you want them to read. Review robots.txt rules, then check whether your site has a useful llms.txt file and whether its contents match the site’s current structure. Don’t treat a file as proof of visibility. Check whether ChatGPT or Google AI Overviews cite your brand for questions your customers ask.
Use the same prompt and date when you check again, and record the answer, source links, and competing brands that appear. This makes changes easier to compare. AEO builds on the technical base of SEO with clear entities, answer-ready content, and citation tracking. See what an AEO audit checks if you want a structured review of brand visibility in AI answers.
Step 6: How do you prioritize fixes, measure impact, and schedule the next audit?
Turn findings into a ranked work list. Score each issue by likely impact and effort. Impact means the possible effect on valuable pages, qualified leads, or revenue. Effort means the time, people, and development work needed to resolve it. Add confidence too: a clear indexing block is easier to act on than a hunch about a competitor’s link profile.
Fix access problems first. A page blocked from crawling or marked noindex can’t earn search visibility in the usual way. Next, tackle errors that affect many high-value URLs, such as broken internal paths or conflicting canonicals. Then move to page-level updates, content gaps, and tests that need more evidence.
Give each task an owner and a way to check completion. For example, a developer can fix a template issue, while the SEO lead verifies the affected URLs in Search Console. A content editor can update a page, then the team can compare its clicks, impressions, and conversions with the baseline. If your team juggles a long fix list, Aboah Reviews compares SEO project management software for assigning and tracking this kind of work. Don’t promise that a fix will cause a set ranking change.
Measure the outcome with the metric tied to the original issue. Track indexation after a crawl problem, leads after a service-page change, and revenue after ecommerce improvements. The Kadima team uses this kind of evidence to connect audit work to business results, and our SEO consulting plan covers setting a baseline and building the action plan around it.
Recheck core technical items after major site releases, migrations, or template changes. Set a recurring review for the rest of the site based on how often pages change. A store adding products every week needs more frequent checks than a small site with stable pages. Keep a change log so future audits can separate new problems from old ones.
SEO audit checklist FAQ
How often should I run an SEO audit?
Run a focused check after a site migration, a major template change, or a large content release. For a stable site, set a regular review schedule that fits how often pages change. Keep monitoring Search Console between audits so indexing issues don’t wait for the next full review.
What should an SEO audit report include?
An SEO audit report should list the affected page or template, the evidence behind each finding, its likely business impact, and the next action. Add an owner and a way to measure completion. That turns the report into a working plan instead of a long list of tool warnings.
Can I do an SEO audit myself?
Yes, you can review Search Console, test key pages, and compare content with your business goals. Start with pages that drive sales or inquiries, then expand the review. Ask a developer for help when a fix involves site code, redirects, canonical rules, or server behavior.
What is the first thing to check in an SEO audit?
Check whether important pages can be crawled and indexed. A strong title or new article won’t help a page that search engines can’t access. Use Search Console’s Pages report, then inspect robots.txt, sitemaps, canonicals, and internal links for the URLs that matter most.
How do I know which SEO audit issues to fix first?
Fix issues with clear evidence that affect important pages or many URLs before small cosmetic edits. Compare likely impact with the effort and risk of each fix. Then name an owner and choose a metric that can show whether the change worked.
Turn Your Audit Findings Into a Prioritized Growth Plan
Keep the audit tied to business outcomes. Start with indexation and crawl access, then work through page quality, links, user experience, and AEO. Choose one high-impact finding, assign it to an owner, and record the result after the fix. If you want help turning findings into a plan, send Kadima Digital your website, marketing budget, and 90-day goal through the contact page.