SEO Audit Checklist: Fix P0 Blockers, Then Tackle P1 in 30 Days

An SEO audit is a structured checklist that converts site issues into a prioritised action list to restore and grow organic visibility. It covers technical health, on-page signals, content quality, links, schema and Core Web Vitals, then ranks what you find by impact. The first move is practical: run a URL Inspection check on your key pages to confirm Google can actually crawl and index them.

TL;DR:

• Fix crawl or indexing blockers immediately; address ranking and schema issues within 30 days, then handle lower impact content and image work within 60 days.
• At the 75th percentile, keep LCP within 2.5 seconds, INP within 200 milliseconds, and CLS at 0.1 or less on each device type.
• For large sites, sample representative pages instead of crawling everything, including the homepage, top categories, blog posts, and busiest landing pages.
• Request link removals first, and consider disavowing toxic links only after those efforts fail; preserve links that send referral traffic, even when authority is modest.
• After fixing a page, rerun URL Inspection’s live test and request indexing; use a sitewide crawl to catch template errors across the site.

Table of Contents

• How to run an SEO audit: framework, priorities and cadence
• Technical SEO audit checklist: crawlability, indexing and server health
• On-page SEO checklist: titles, headings, structure and internal links
• Content quality audit: thin pages, gaps and AI readiness
• Backlink profile audit: spotting toxic links and protecting authority
• Schema and structured data checks
• Core Web Vitals and UX: what to measure and how to act
• Tools and verification: running checks and confirming fixes
• Prioritising issues and building a clear audit report
• How Blindspot runs audits
• AI search readiness: beyond the basics
• Local SEO audit checks: Google Business Profile, citations and reviews
• Mobile usability and mobile-first indexing
• Competitor analysis within the audit
• Where audits usually go wrong
• Run a professional audit with Blindspot
• FAQ
• Sources

How to run an SEO audit: framework, priorities and cadence

A full audit works best when you split it into eight categories rather than trying to check everything at once. This keeps the process manageable and makes it easier to hand sections off to different people or tools.

The eight categories are:

• Technical SEO: crawlability, indexing, sitemaps, redirects, canonicalisation.
• On-page SEO: titles, meta descriptions, headings, content-to-intent match.
• Content quality: thin or duplicate pages, topical coverage, freshness.
• Backlink profile: referring domains, anchor text, toxic link patterns.
• Schema and structured data: present types, validation, rich-result eligibility.
• Core Web Vitals and UX: loading, interactivity, visual stability.
• Local signals: Google Business Profile, citations, NAP consistency.
• AI search readiness: structured answers, summary clarity, voice query alignment.

Once you have findings from each category, label every issue with a priority rather than leaving a flat list of problems. A simple three-tier system works well:

1. P0 (fix immediately): issues blocking indexing or crawling, such as an accidental noindex tag or a broken sitemap.
2. P1 (fix within 30 days): issues suppressing rankings or click-through, such as duplicate titles or missing schema on key pages.
3. P2 (fix within 60 days): issues with smaller, longer-term impact, such as thin content on low-traffic pages or minor image optimisation.

Scope depends on site size and resources. A full site-wide crawl suits smaller sites or a first-time audit, while a sample of representative pages (homepage, top category pages, a handful of blog posts and your highest-traffic landing pages) works for larger sites where a full crawl would take too long to action. Most businesses benefit from a full audit regularly, with occasional lighter checks focused on technical health and Core Web Vitals.

Pro Tip: Run your P0 checks first and in isolation. Fixing an indexing block before anything else means every other improvement you make actually has a chance to be seen by Google.

Technical SEO audit checklist: crawlability, indexing and server health

Technical issues sit at the top of the priority list because they can block everything else you do. A page with excellent content and strong backlinks is worthless if Google cannot crawl or index it.

Start with the basics, in this order:

1. Check robots.txt: confirm it is not accidentally blocking important sections of the site, and that your sitemap is referenced inside it.
2. Verify sitemap correctness: the sitemap should follow the XML sitemap protocol, contain only canonical, indexable URLs, and be submitted inside Search Console.
3. Run URL Inspection on priority pages: this live test shows whether a page is crawlable, whether indexing is allowed, which canonical Google has chosen, and whether structured data was found. According to Search Console’s own documentation, the tool reports one of three states: the URL is on Google, it is on Google but has issues, or it is not on Google at all, with details on the cause in each case.
4. Check for the robots.txt and noindex trap: a page blocked by robots.txt can still show “Indexing allowed? Yes” in URL Inspection, because Google cannot see a noindex tag it was never allowed to crawl in the first place. This is a common reason pages seem fine on paper but never appear in search, so always check robots.txt and any meta robots or X-Robots-Tag header together rather than relying on one signal alone.
5. Audit server responses: crawl the site and flag any 4xx or 5xx errors, along with redirect chains. A single 301 is harmless, but chains of three or more redirects waste crawl budget and slow page loading.
6. Confirm canonical tags are consistent: each indexable page should point to itself as canonical unless there is a deliberate reason (such as a filtered or paginated variant) to point elsewhere.
7. Check hreflang implementation: if you run multiple language or regional versions of a page, confirm hreflang tags are reciprocal and point to valid, indexable URLs.
8. Verify HTTPS and basic security headers: an expired certificate or mixed content warning can quietly suppress rankings and erode trust signals.

Server performance deserves its own pass too. Slow response times from the origin server compound with front-end performance issues, so check time-to-first-byte alongside your Core Web Vitals data rather than treating them as separate problems.

Pro Tip: When URL Inspection shows a discrepancy between the live test and the indexed version, trust the live test. It reflects what Google would see if it crawled the page right now, which is exactly what you are trying to diagnose.

Document every technical finding with a screenshot or exported report, because these checks tend to need re-verification once fixes go live, and having a before state makes it easy to confirm the fix actually worked.

On-page SEO checklist: titles, headings, structure and internal links

On-page elements are the signals closest to the content itself, and they are usually the fastest items to fix once identified. A single afternoon can often clear an entire backlog of these issues.

Work through the following:

• Title tags: check each one is unique, under roughly 60 characters, and reflects the actual search intent of the page rather than a generic label.
• Meta descriptions: these do not directly affect rankings but shape click-through from the results page, so write them to match what the searcher is trying to accomplish.
• Heading structure: confirm a single H1 per page, with H2s and H3s that follow a logical hierarchy rather than skipping levels or repeating the same phrase.
• Content-to-intent alignment: check that the page actually answers the query it is targeting in the first few hundred words, rather than opening with unrelated context.
• Canonical tags: verify these match the technical audit findings and that near-duplicate pages (such as printer-friendly or filtered versions) are canonicalised correctly.
• Duplicate content: search for repeated blocks of text across pages, particularly on ecommerce category pages or templated location pages, and consolidate or rewrite where found.
• Image optimisation: check alt text is descriptive and file sizes are compressed, since both affect accessibility and page speed.
• Internal linking: confirm your most important pages receive internal links from relevant, high-traffic pages, and that anchor text describes the destination rather than using generic phrases such as “click here”.

A quick way to spot on-page gaps at scale is to export your top organic landing pages from Search Console and check each one against this list in turn, rather than reviewing every page on the site with equal depth. Pages that already receive traffic are the ones where a small fix tends to produce the clearest lift, so they deserve the first pass.

Internal linking is worth a second look once the rest of the on-page checks are done, because it is the item most often skipped. A page with strong content but no internal links pointing to it is effectively invisible to both users browsing the site and to Google’s crawler discovering new pages.

Content quality audit: thin pages, gaps and AI readiness

Content quality issues are harder to spot than technical ones because they require judgement rather than a simple pass or fail test. The goal is to work out which pages are pulling their weight and which are diluting the site’s overall relevance.

Start by identifying problem pages:

• Thin content: pages with very little unique text, often old blog posts or auto-generated category pages, are candidates for consolidation or a full rewrite.
• Duplicate or near-duplicate pages: these split ranking signals between two URLs that should really be one, so merge them and redirect the weaker version.
• Cannibalisation: when two pages target the same query, decide which one should rank and adjust the other’s focus or merge the content.
• Coverage gaps: map your existing pages against the topics and intents your audience searches for, and note where a competitor page would answer a question you have not covered at all.
• Freshness: pages built around time-sensitive information or statistics need a review date, particularly where the facts or figures quoted have since changed.

E-E-A-T signals matter here too, though they are qualitative rather than something you tick off with a tool. Check that pages dealing with health, finance or safety topics cite credible sources, that author information is visible where relevant, and that the content reflects direct knowledge of the subject rather than generic paraphrasing.

Pro Tip: Before rewriting a thin page from scratch, check whether a near-duplicate already exists elsewhere on the site. Consolidating two weak pages into one strong one is usually faster and more effective than improving both separately.

AI readiness is an increasingly practical part of this audit. Pages that answer a question directly in the first two or three sentences, with a clear summary near the top, are easier for AI-driven search features to extract and cite. Our breakdown of practical steps for AI citations covers this in more depth if you want to go further than the basics. For older content, auditing existing posts for outdated links and claims is worth doing alongside a content freshness pass, since broken or stale references undermine both user trust and AI extraction.

Backlink profile audit: spotting toxic links and protecting authority

A backlink audit exists to answer one question: is your link profile helping or quietly holding you back? Most sites have a mix of genuinely valuable links and a smaller number worth investigating further.

Work through these steps:

• Export referring domains and anchor text: pull a full list from your preferred link data source and sort by domain authority, anchor text and link type.
• Filter for low-quality indicators: flag links from unrelated foreign-language sites, obvious link farms, or domains with no real traffic or content of their own.
• Watch for link velocity spikes: a sudden, unexplained jump in referring domains over a short period is a common sign of a negative SEO attempt or a leftover from an old, poorly executed campaign.
• Check anchor text distribution: a profile dominated by exact-match commercial anchors (“best security company Sussex”) rather than branded or natural anchors can look manipulative to Google.
• Decide on remediation: for a handful of toxic links, a removal request to the site owner is worth trying first; for links you cannot get removed, document them and consider a disavow file only once you have exhausted other options.
• Identify links worth protecting: some links send genuine referral traffic even if their domain authority is modest, so note these separately before any cleanup so they are not accidentally caught up in a disavow.

Keep a simple record of every decision, including links you chose to leave alone and why, since this becomes useful evidence if rankings shift later and you need to work out whether the link profile played a part.

Schema and structured data checks

Structured data does not directly move rankings on its own, but it controls whether your pages qualify for the enhanced result types that improve click-through, such as star ratings, FAQ dropdowns or business information panels.

Start by finding what is already there:

• Detect existing schema: crawl the site to see which pages carry structured data and which markup types are in use, such as Article, Product, FAQPage or LocalBusiness.
• Validate each type: check results in Search Console’s enhancement reports and cross-reference with Schema to confirm the properties used are valid for that type.
• Prioritise by SERP impact: fix errors on schema types that directly change how your listing appears, such as FAQ, Product or LocalBusiness markup, before spending time on types with no visible effect.
• Check for missing opportunities: if a page clearly matches a schema type (an FAQ section, a local business location page) but has no markup at all, add it rather than waiting for an error to force the issue.
• Watch for spammy markup: schema that misrepresents the page’s actual content, such as review markup not tied to genuine reviews, risks a manual action rather than a ranking boost.

Treat schema fixes as a P1 item in most cases: they rarely block indexing outright, but they directly affect how competitive your listing looks next to others on the same results page.

Core Web Vitals and UX: what to measure and how to act

Core Web Vitals measure how a page feels to use, not just how it is built. Google’s own guidance defines three metrics that matter for SEO: Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS).

The recommended thresholds, measured at the 75th percentile of visits, are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less, and a CLS score of 0.1 or less, each segmented by device type since mobile and desktop performance often differ significantly.

Data for these metrics comes from three main sources:

• Chrome UX Report: real-world field data collected from actual Chrome users visiting your pages.
• PageSpeed Insights: combines field data with a live lab test of the page you enter.
• Search Console’s Core Web Vitals report: groups your pages by status (good, needs improvement, poor) at a site-wide level.

Common fixes include compressing and lazy-loading images to improve LCP, deferring non-critical JavaScript to improve INP, and reserving space for images and ads before they load to prevent CLS. When a fix requires changes to the site’s underlying code or hosting infrastructure rather than content or image adjustments, it is usually time to bring in a developer rather than trying to patch it through a plugin alone.

Tools and verification: running checks and confirming fixes

An audit is only useful once you have verified that a fix actually worked, not just that you made a change. A simple run, fix, re-test loop keeps this honest.

A practical workflow looks like this:

1. Run URL Inspection on the affected page inside Search Console to see its current crawl and index status, then note any blocking reasons shown.
2. Make the fix, whether that is removing a noindex tag, correcting a robots.txt rule, or adjusting a canonical reference.
3. Re-run the live test inside URL Inspection and, once it passes, request indexing so Google recrawls the page sooner rather than waiting for its next scheduled crawl.
4. Diagnose Core Web Vitals issues with PageSpeed Insights or Lighthouse, both of which break down exactly which elements are slowing LCP or contributing to layout shift.
5. Run a full crawl with a dedicated crawling tool to catch site-wide issues that a page-by-page check would miss, such as a broken template affecting hundreds of pages at once.
6. Check basic accessibility with a tool such as WAVE, which flags missing alt text, poor colour contrast and structural issues that affect both usability and, indirectly, engagement metrics.

Pro Tip: Always request indexing after a fix rather than waiting. It costs nothing and can shave days off the time it takes Google to notice the change.

For WordPress sites, a plugin such as Yoast SEO can handle much of the on-page and schema management day to day, reducing how often you need to return to these checks manually.

Prioritising issues and building a clear audit report

Once every category has been checked, the real work is turning a long list of findings into something a stakeholder can actually act on. A report with fifty bullet points and no order of operations tends to get filed away and forgotten.

Score each issue by impact against effort, then assign it a priority tier:

• High impact, low effort: fix immediately, regardless of category, since these are the quickest wins available.
• High impact, high effort: schedule as P1 and break into smaller milestones so progress is visible before the whole fix is complete.
• Low impact, low effort: batch these together as P2 and clear them in a single pass.
• Low impact, high effort: deprioritise unless it supports a separate business goal, such as accessibility compliance.

A sample 30/90-day structure keeps this concrete. Our 90-day plan for service-area businesses shows one version of this in practice: the first 30 days clear P0 technical blockers and quick on-page wins, and the following 60 days work through content consolidation, schema additions and link remediation.

A concise report, paired with a defined 30 to 90 day execution window, gives stakeholders something they can approve and track rather than a static document that sits unread.

How Blindspot runs audits

Our audits follow the same prioritised structure outlined above, because a list of fifty unranked issues rarely leads to action. We start every engagement with the P0 technical and indexing checks, since fixing a blocked page is wasted effort if it happens after weeks spent on content or link work.

Our process typically includes:

• A full technical and on-page crawl, cross-checked against Search Console data rather than crawler output alone.
• A prioritised action list split into P0, P1 and P2 fixes with suggested timelines.
• A sample 90-day execution plan, similar in structure to our service-area business SEO plan, adapted to the client’s priorities and resources.
• Local-specific checks for Google Business Profile, citations and NAP consistency where the business depends on local search.

Realistic timelines matter here. Our own benchmark guidance on how long SEO takes to show results puts most meaningful ranking movement at 6 to 12 months from a fixed baseline, which is why we frame audit outcomes against that window rather than promising faster results than the work supports.

We have worked across more than ten industries, with a particular focus on security companies, builders, trades and other service businesses that depend on consistent local visibility to generate enquiries.

AI search readiness: beyond the basics

AI-generated search results and voice assistants pull from pages that answer a question clearly and quickly, which means the structure of your content matters as much as its depth.

A few practical adjustments help:

• Lead with a direct answer: the first sentence after a heading should answer the question it poses, with supporting detail following rather than preceding it.
• Use clear, complete sentences: voice assistants and AI summaries tend to extract whole sentences rather than fragments, so avoid relying on bullet fragments or incomplete phrases for your core claims.
• Match natural phrasing: voice queries tend to be longer and more conversational than typed searches, so headings phrased as full questions (“How long does an SEO audit take?”) tend to match these queries more closely than a short noun phrase.
• Keep summaries concise: a two to three sentence summary near the top of a page gives an AI system a ready-made answer to extract, rather than forcing it to infer one from scattered paragraphs.
• Maintain structured data: FAQPage and HowTo schema, where genuinely applicable, give AI systems an additional structured signal to draw from.

This is an extension of good on-page writing rather than a separate discipline, and most of the groundwork overlaps directly with the content and on-page checks covered earlier in this audit.

Local SEO audit checks: Google Business Profile, citations and reviews

For any business relying on local customers, the audit is incomplete without checking signals outside the website itself. Search Engine Journal’s local SEO audit checklist frames this as its own distinct stage, covering Google Business Profile, citations, reviews and backlinks alongside the standard technical and content checks.

Key checks include:

• Google Business Profile completeness: confirm categories, business description, service areas, hours and photos are current and accurately reflect the business.
• NAP consistency: verify your business name, address and phone number match exactly across your website, Google Business Profile and major directories. Our NAP consistency workflow walks through how to catch and fix mismatches systematically.
• Citation accuracy: check listings on major directories for outdated information, duplicate entries, or missing categories.
• Review profile health: assess review volume, recency and response rate, since all three feed into how Google Business Profile ranks locally.
• Location page quality: for multi-location businesses, confirm each location page carries genuine local detail rather than templated text copied across every city. Our guide on publishing location pages with real local evidence covers what that detail should look like in practice.

These checks sit alongside, not instead of, the technical and content audit, since local pages still need to pass the same crawlability and quality checks as any other page on the site.

Mobile usability and mobile-first indexing

Google indexes and ranks the mobile version of your pages by default, which means a desktop-only audit misses the version of the site that actually determines your rankings.

Check the following on mobile specifically, not just desktop with a narrower browser window:

• Content parity: confirm the mobile page shows the same content, headings and structured data as the desktop version, since hidden or stripped-down mobile content can quietly suppress rankings.
• Tap target sizing: buttons and links should be spaced far enough apart that users do not tap the wrong element on a smaller screen.
• Viewport configuration: confirm the page sets a proper viewport meta tag so content scales correctly rather than forcing horizontal scrolling.
• Core Web Vitals on mobile: check LCP, INP and CLS separately for mobile, since mobile devices and connections typically perform worse than desktop and often fail thresholds that desktop passes comfortably.
• Intrusive interstitials: pop-ups that cover the main content on page load can affect both user experience and how Google evaluates the page.

Running URL Inspection in Search Console shows exactly how Googlebot Smartphone renders and crawls a given page, which is the most direct way to confirm mobile indexing issues rather than guessing from a browser preview.

Competitor analysis within the audit

An audit tells you what is wrong with your own site, but it does not tell you how that compares to what is actually ranking. A short competitor benchmark closes that gap.

Useful comparisons include:

• Content depth and structure: check whether competitors ranking above you cover subtopics or questions your page is missing entirely.
• Technical baseline: run the same Core Web Vitals and indexing checks on top-ranking competitor pages to see whether they are winning on speed and crawlability, or in spite of weaker technical performance.
• Backlink gap: compare referring domains to spot sites that link to multiple competitors but not to you, since these are often realistic, relevant outreach targets.
• Schema and SERP features: note which rich result types competitors have earned, such as FAQ dropdowns or review stars, and treat any gap as a prioritised schema fix on your own pages.
• Local pack presence: for local queries, check which businesses appear in the map pack and review their Google Business Profile completeness against your own.

This comparison does not need its own separate report. Folding competitor findings into the relevant category, technical, content, schema, as you go keeps the whole audit focused on action rather than observation.

Where audits usually go wrong

The biggest mistake I see is treating an audit as a document rather than a decision tool. A fifty-page PDF listing every missing alt tag on a 200-page site looks thorough, but it gives a stakeholder nothing to act on by Monday morning.

Start with crawl and index issues every time, even when content or links feel more urgent. Fixing a cannibalisation issue on a page Google cannot index yet is wasted effort, and I have seen teams spend weeks on content work before realising a sitewide noindex tag was quietly undoing all of it.

Aim for a measurable win inside the first 30 to 90 days rather than promising a complete transformation. A clear before-and-after on even two or three metrics, indexed pages, Core Web Vitals pass rate, organic clicks to a priority page, builds far more trust than a long list of fixes with no way to tell whether any of them worked.

— Harry

Run a professional audit with Blindspot

Working through this checklist on your own takes time most business owners do not have alongside actually running their business. Our SEO & GEO service turns this process into a prioritised action list and a working 90-day plan, built around what will move the needle for your specific site rather than a generic template.

This approach works particularly well for:

• Local service businesses competing for enquiries in a specific area, including security companies, builders and trades.
• Multi-location businesses that need consistent technical health and local signals across every site and profile.
• Teams that want clear priorities and timelines rather than a long list of unranked issues to work through themselves.

We offer this as part of our Essential, Grow and Transform plans, structured around how much ongoing support a business needs beyond the initial audit, available on our services page. If you would rather have a prioritised, actionable audit in hand than spend a weekend running one yourself, get in touch through our SEO & GEO page to find out what we would prioritise first for your site.

FAQ

What is included in an SEO audit?

A complete SEO audit covers technical health (crawlability, indexing, sitemaps), on-page elements (titles, headings, content), content quality, backlink profile, schema and structured data, and Core Web Vitals. A thorough audit also checks local signals such as Google Business Profile and citations where the business depends on local search, as outlined in Search Engine Journal’s local audit checklist.

What are the top SEO audit tools?

Google Search Console is the primary free tool, offering URL Inspection, Core Web Vitals reports and indexing data directly from Google. PageSpeed Insights and Lighthouse diagnose performance issues, while a dedicated site crawler catches sitewide technical problems and WAVE flags basic accessibility issues.

What is an SEO checklist?

An SEO checklist is a structured list of technical, on-page, content and off-page items to review on a website, used to find issues that may be limiting organic visibility. It typically groups items by category, such as crawlability, metadata and backlinks, and often assigns a priority level to each finding.

How do I prepare an SEO audit report?

A clear audit report leads with an executive summary of the top findings, followed by a prioritised issue list tagged by urgency (commonly P0, P1, P2) with suggested fix timelines. It should also assign ownership for each fix and define how success will be measured, rather than listing every issue with no order of action.

How often should I run an SEO audit?

Most sites benefit from a full audit annually, with a lighter quarterly check focused on technical health and Core Web Vitals in between. A business making frequent site changes or launching new pages regularly may benefit from more frequent spot checks on the technical and on-page categories.

Sources

• How to use Google Search Console (Semrush summary of Search Console guidance)
• URL Inspection tool - Search Console Help — Google

Recommended

• 90 Day Plan for Service Area SEO: Audit, One City Page
• 6 to 12 Months to ROI? SEO Timeline and Blindspot Benchmarks to Check
• 90 Day SEO That Gets Calls for Plumbers via Google Business Profile
• 3 SEO Moves That Drive Leads for U.S. Home Builders