Diagnose before you change

SEO Audit Checklist

An SEO audit checklist helps you diagnose why an existing website is losing visibility, missing useful search traffic or frustrating visitors. Start with Search Console, then inspect the pages behind the numbers: their indexing status, titles, content, links and mobile experience. Each check shows where to look, how to interpret a result and which fix to investigate. Notes are optional throughout.

Free to useNo account neededSaved in your browser
A magnifying glass reviewing evidence cards beside SEO audit findings arranged by priority.
An editorial illustration
Your working checklist

Work through the checklist

Click a square to mark a task as Pass. Click again to undo. Use the result menu for a problem, a blocker or a task that does not apply. You do not need to enter notes.

21 checks

Check Search Console and Your SEO Baseline

Search Console shows how Google finds and displays your website. Its clicks, impressions and alerts help you separate a search-visibility problem from a measurement problem. Check the correct property, meaning the verified website or address prefix, before comparing reports.

Choose important pages for the SEO audit

Include the page types that attract visitors or help them act.

Use this for: Every audit, including a small site checked in full.

Open your website navigation and the published-page list in your website editor. Include the homepage, important services or products, category pages, articles and the main contact or purchase path where these exist. Small sites can check every important page.

Add pages with reported traffic losses and recent changes. Compare a problem page with another using the same template, meaning the shared layout or publishing rule. This helps distinguish a local editing error from a repeated defect.

Example

Hypothetical example: a garden business’s homepage works, but all service pages share a broken enquiry link. Include those service pages and the enquiry path.

  1. Choose important page types and URLs.
  2. Include changed pages and known problems.
  3. Expand a repeated-problem sample.
More help and optional notesHigh · SEO lead
PassThe selected pages cover the audit scope, and any omissions are understood.
FailImportant page types are missing, or a homepage-only test is treated as sitewide.

If it fails: Add missing page types.

Retest: Confirm coverage of the scoped page types.

Not applicable: Usually applies; every audit needs a defined scope.

Keep in mind: A sample does not cover every URL.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Compare search clicks and impressions

Locate the dates and website areas where search performance changed.

Use this for: An existing site with search history or a reported performance change.

Open Search Console → Performance → Search results. Compare equal-length periods with the same search type and filters. For seasonal businesses, also compare the relevant season when history allows. Clicks count clicks from Google Search to your site; impressions count appearances in results.

Use Pages to find the URLs behind the change. Click an affected page, then open Queries to inspect its searches. Compare Devices and Countries if the decline may be limited to mobile or a market.

Example

Hypothetical example: service-page clicks fall while advice-page clicks stay steady. Inspect the affected services and queries before proposing a sitewide rewrite.

  1. Compare equivalent dates.
  2. Inspect affected pages and their queries.
  3. Compare device, country and season.
More help and optional notesHigh · SEO lead
PassYou can identify the dates, affected pages or searches, and what changed against the comparison period.
FailA decline is called a penalty or technical failure without checking the comparison.

If it fails: Test reporting, demand and site-change explanations.

Retest: Repeat with the same report filters.

Not applicable: A new site has no usable history. Missing access to an existing report is Blocked.

Keep in mind: Matching dates do not establish causation.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check which page appears for each important query

Find mismatches between searcher intent and the page receiving impressions.

Use this for: Existing pages with query-level search data.

In Search Console’s Search results report, select a relevant query from Queries, then open Pages. Read the pages shown for that query and compare their purpose with the search. A search for a repair service needs different information from a search for instructions to repair something yourself.

Compare the same query and page over equivalent dates. If a less suitable page receives impressions, inspect its title, main heading, content and incoming internal links alongside the intended page. Two pages appearing for one query is a clue to review their roles, not proof that they must be merged.

Example

Hypothetical example: “roof repair Leeds” shows an old advice post instead of the repair-service page. Check the service page’s indexability, answer and incoming links.

  1. Select a query, then Pages.
  2. Compare results with the searcher’s task.
  3. Investigate mismatched page choices.
More help and optional notesMedium · SEO lead
PassImportant query/page mismatches have been assessed and an appropriate next test or correction identified.
FailSearch terms are assigned to pages without examining the actual query/page relationship.

If it fails: Investigate eligibility, discovery or page-purpose mismatches.

Retest: Compare query/page results after data updates.

Not applicable: No usable query history exists; unavailable report access is Blocked.

Keep in mind: Search Console omits some queries; absence does not establish zero demand.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Test the analytics or lead event you rely on

Check whether a reported loss could involve measurement or a broken visitor action.

Use this for: An audit using existing analytics or recorded leads to assess performance.

Use this check only when existing analytics or recorded enquiries inform the audit. Confirm the report’s website, dates and filters. Compare its trend with Search Console clicks; the systems measure different things and their totals need not match.

Try the affected action in test mode or with approval for a live test. For existing GA4, ask the measurement owner to enable test-device debug mode and open Admin → Data display → DebugView. Compare expected and received events. Respect consent: denied analytics consent or privacy controls can suppress debug events.

Example

Hypothetical example: clicks stay steady but recorded enquiries disappear after a form redesign. Test both enquiry delivery and its event before recommending copy changes.

  1. Check property, dates and filters.
  2. Test the approved action and event.
  3. Investigate mismatches and recent changes.
More help and optional notesHigh · Analytics owner

Before you begin: Known expected event and approved test method.

PassThe test records the expected action correctly under the agreed conditions, without unexplained missing or duplicate events.
FailA missing, duplicate or incorrect event or reporting setup is reproduced. Missing access or test permission is Blocked.

If it fails: Correct reproduced faults without bypassing consent.

Retest: Repeat the approved action; inspect its event.

Not applicable: No existing analytics or recorded-action data is used in this audit; installation is not required.

Keep in mind: One test does not validate historical data or every consent state.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check manual actions and security alerts

Find explicit Google reports that require a specific response.

Use this for: A website reviewed for its current Google Search status.

Open Search Console’s Manual actions and Security issues reports separately. Read current findings, affected examples and recommended responses. A manual action is a reported policy action; a security issue may concern hacked content. A traffic drop establishes neither.

Escalate unresolved findings to the site owner and relevant specialist. Follow the report’s remediation and review process. Do not visit a suspected hacked page merely to inspect it, or clear the finding while review is pending.

Example

Hypothetical example: the report identifies hacked pages in an unfamiliar directory. Escalate for safe investigation before editing page titles.

  1. Read both reports.
  2. Escalate unresolved findings.
  3. Verify remediation and the report outcome.
More help and optional notesCritical · Site owner

Before you begin: Correct Search Console property access.

PassBoth reports have been checked and show no unresolved reported issues.
FailEither report contains an unresolved issue. Missing report access is Blocked.

If it fails: Follow issue-specific remediation with a qualified owner.

Retest: Verify remediation and the report outcome.

Not applicable: Only when Google Search status is outside the agreed audit scope; lack of access is Blocked.

Keep in mind: Clear reports do not establish complete security or quality.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Find Indexing, Sitemap and Internal Link Problems

Indexing means Google has processed a page so it can be eligible to appear in search. Audit important public pages first. Duplicate addresses, private pages and deliberately removed content can be excluded correctly; an exclusion becomes a problem when it conflicts with what the page is meant to do.

Find important pages missing from Google’s index

Separate expected exclusions from important pages that need investigation.

Use this for: Public pages expected to appear in search, plus known intentional exclusions.

Open Search Console → Indexing → Pages. Review Why pages aren’t indexed and compare examples with the pages you want people to find. Prioritize an excluded main service page over a deliberately duplicated filter address.

Paste an unexplained URL into URL Inspection. Check its reason, last crawl and available canonical information. Indexed data describes Google’s last observed version; Test live URL checks current access and indexability, not whether Google already indexed the change.

Example

Hypothetical example: a public service page is excluded by noindex. Investigate that setting; the same instruction on an intentionally excluded thank-you page may be correct. Genuinely private pages need access controls.

  1. Review indexing exclusions.
  2. Inspect important unexpected examples.
  3. Compare intended status and current output.
More help and optional notesHigh · SEO lead
PassImportant exceptions are explained with page-level evidence.
FailImportant search pages have unexplained exclusions or misleading status assumptions.

If it fails: Investigate unexplained important exclusions.

Retest: Compare live output and fresh indexed information.

Not applicable: Only when search indexing is outside scope; unavailable reports are Blocked.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Verify the suspected technical SEO blocker

Test the page-level cause before recommending a technical change.

Use this for: A suspected technical problem from the report or page checks.

Match the inspection to the warning. For missing pages, ask the developer to check the response status, the server’s result code. For indexing exclusions, compare robots instructions and the preferred address. For missing text, compare the visible page with URL Inspection’s rendered output.

Compare a working page using the same layout. One wrong page setting needs a different correction from a shared template fault. Hand the exact difference to the technical owner.

Example

Hypothetical example: a guide looks normal but returns 404, meaning not found. Compare a working guide and ask the developer to investigate the response.

  1. Repeat the relevant inspection.
  2. Compare a working equivalent.
  3. Confirm or rule out the blocker.
More help and optional notesHigh · Developer
PassThe suspected issue has been reproduced or ruled out by the relevant test; any finding identifies the mismatch.
FailA warning is treated as a confirmed issue without checking an example.

If it fails: Isolate the responsible setting or template.

Retest: Repeat the original test after deployment.

Not applicable: No suspected technical blockers were found within the reviewed scope.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check the sitemap against published search pages

Find stale or conflicting addresses in the site’s discovery list.

Use this for: A website with an existing sitemap or a discovery issue being investigated.

Open Search Console’s Sitemaps report and inspect the submitted sitemap, if one exists. A sitemap is a list of addresses you want search engines to discover. Compare a few important entries with their final published addresses and compare recently published search pages with the sitemap.

Flag entries that point to removed content, redirect elsewhere or deliberately exclude indexing. If the sitemap cannot be read, give its reported error to the platform owner. Recommend changes to the system generating the file; manually editing an automatically rebuilt file may not last.

Example

Hypothetical example: the sitemap still lists a service’s old redirecting address. Ask the platform owner to publish its final preferred address.

  1. Read the sitemap and reported status.
  2. Test priority entries.
  3. Flag stale addresses or generation errors.
More help and optional notesMedium · Developer
PassInspected sitemap entries agree with intended preferred public pages, with no unresolved relevant errors.
FailImportant entries are stale, inaccessible or conflict with their intended indexable state.

If it fails: Correct the generator and conflicting entries.

Retest: Test entries in the regenerated sitemap.

Not applicable: No sitemap is used and no sitemap-related discovery issue is in scope.

Keep in mind: Sitemaps do not guarantee indexing.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Compare declared and Google-selected canonical URLs

Check whether duplicate addresses point toward the intended version.

Use this for: Important duplicate or alternate URLs with a canonical question.

For an important URL with a duplicate-related exclusion, use URL Inspection’s indexed information to compare the user-declared canonical with Google’s selected canonical, when available. A canonical is the preferred address for substantially equivalent content. Open both pages and ask whether they really serve the same purpose.

If Google selects a different address, ask the technical owner to compare page content, canonical declarations, redirects, internal links and sitemap entries. Do not use canonical tags to join unrelated pages or remove useful distinct content. The live test does not predict Google’s final canonical choice.

Example

Hypothetical example: campaign-tagged and main product addresses show identical content. Check why internal links favor the tagged version and whether signals consistently prefer the main address.

  1. Compare declared and selected canonicals.
  2. Confirm the pages’ relationship.
  3. Investigate conflicting signals.
More help and optional notesMedium · Developer
PassThe intended preferred page is supported by the inspected signals, or a specific mismatch has a scoped technical investigation.
FailA duplicate warning is resolved by guessing a destination or conflating distinct pages.

If it fails: Align reviewed duplicate signals with the preferred URL.

Retest: Check deployed signals, then fresh indexed data.

Not applicable: No duplicate-URL or canonical question was identified.

Keep in mind: Google may select another canonical.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Find important pages without useful internal links

Check whether visitors and crawlers can reach priority pages from related content.

Use this for: Priority public pages that visitors should reach from elsewhere on the site.

Start at the homepage, a category or a relevant guide and follow links to each priority page. Compare reachable pages with the editor’s page list and sitemap. A published page without useful incoming links is often called an orphan page.

Check link text and destination together. “Garden maintenance services” sets a clearer expectation than an unexplained “click here.” For script-driven controls, ask the developer whether an ordinary crawlable link also exists. Recommend relevant paths without a fixed link count.

Example

Hypothetical example: a lawn-care guide never links to the existing lawn-maintenance service. Recommend a link where the guide explains work that service genuinely covers.

  1. Follow links to priority pages.
  2. Find missing incoming paths.
  3. Check link text and destination.
More help and optional notesHigh · SEO lead
PassImportant pages have useful incoming links and working destinations.
FailA priority page is isolated or linked only through a broken route.

If it fails: Add useful contextual links.

Retest: Follow corrected paths; repeat affected crawl samples.

Not applicable: Only for pages deliberately outside public navigation, such as private utility pages.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check broken links and unexpected redirects

Find link destinations that no longer satisfy the visitor’s task.

Use this for: Sampled links and reported broken-link or redirect problems.

Follow important navigation, in-content and download links on the sampled pages. If a crawler has found broken links, open its source-page examples and repeat those clicks. Check the final page and address, not just whether something loads. A redirect sends the visitor to another address and can be valid after a real move.

Ask a developer to inspect uncertain responses or redirect paths in the browser’s Network panel. An internal link to an old address can usually be updated to the correct final destination. A removed page with no suitable replacement may correctly return not found; an unrelated homepage redirect is not an automatic repair.

Example

Hypothetical example: “Download the pruning calendar” redirects to a general resources page. Find the calendar or correct the promise; loading any page is insufficient.

  1. Follow flagged source links.
  2. Check final destinations.
  3. Recommend the appropriate correction.
More help and optional notesHigh · Editor
PassInspected links reach the intended resource, or any deliberate removal is handled accurately.
FailA broken link, loop or irrelevant destination prevents the advertised task.

If it fails: Correct links or appropriate redirects.

Retest: Follow the source link to its resource.

Not applicable: No links or navigation paths are included in the agreed scope.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Audit SEO Titles, Content and Mobile Experience

An on-page SEO audit compares what each page promises with what it actually delivers. Read the title, description, headings and main content together. Use search queries to understand the questions visitors bring, then inspect whether the page answers them and works on a phone.

Check whether the page answers its target search

Find missing answers, unsupported promises or broken next steps.

Use this for: Priority pages with a visitor question or action to satisfy.

Read the SEO title, main heading and opening. Identify the task: choose a product, compare options, understand a problem or request a service. Use Search Console queries as clues, then compare the promise with the actual offering.

Find the information needed: service scope and coverage, important exclusions, product differences or ordered tutorial steps. Try the next action using test mode or approval for consequential submissions. Specify the missing answer rather than requesting “more content.”

Example

Hypothetical example: a page promises a maintenance-checklist download but only describes one. The gap remains until the download works or the promise is corrected.

  1. Identify the promised task.
  2. Find the required answers.
  3. Try the next step.
More help and optional notesHigh · Editor
PassThe page delivers its promised answer or action without an unresolved gap that prevents the visitor’s task.
FailA missing answer, false promise or broken action leaves the visitor’s task unresolved, even if the gap is noted.

If it fails: Specify the missing answer or action.

Retest: Retry the original visitor task.

Not applicable: Only for a utility page with no visitor-facing content or action in scope.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Find missing, duplicate or misleading SEO titles

Check whether each priority page has a specific title that matches its subject.

Use this for: Priority public pages with an SEO title to review.

Open the page’s SEO title field in the website editor and check the published browser-tab title or title element. If a crawler lists missing or duplicate titles, inspect examples alongside their headings and content. Compare the wording with the main search topic and distinguish pages that serve different purposes.

Flag generic labels, outdated dates, repeated keywords or a service or location the page does not support. A length warning is a cue to preview clarity, not an automatic failure. Google may use other page signals to display a different title link.

Example

Hypothetical example: replace the vague “Services” with a recommendation such as “Boiler Repair in Bristol | Example Heating” only when those details are true.

  1. Inspect the published title.
  2. Compare its topic and distinguishing details.
  3. Flag missing or misleading wording.
More help and optional notesMedium · Editor
PassSampled titles accurately distinguish their pages without an unresolved missing or misleading title.
FailA missing, duplicated or misleading title obscures the page’s actual subject.

If it fails: Correct the title or shared template.

Retest: Inspect the published title against the page.

Not applicable: Only when this page type or issue is outside the audit scope.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check meta descriptions against the actual page

Find search summaries that are missing, generic or make unsupported promises.

Use this for: Priority public pages whose search summaries are being reviewed.

In the website editor’s SEO settings or the published page source, inspect the meta description. Compare it with the page’s main answer and next step. A useful description briefly explains what this particular page offers; copied company boilerplate does little to distinguish services or products.

If clicks fell while comparable impressions remained steady, review the query, title and description together. A weak summary is one possible explanation, not a proven cause. Search snippets can come from the page itself, so a rewritten snippet does not automatically mean the meta description is defective.

Example

Hypothetical example: “Download the free checklist” describes a page with no download. Correct the false promise before testing wording for click-through rate.

  1. Inspect the published description.
  2. Compare its promise with the page.
  3. Flag inaccurate or generic summaries.
More help and optional notesMedium · Editor
PassThe description accurately summarizes the specific page, or an intentional omission is understood.
FailA misleading, generic or unintentionally missing description remains on an important reviewed page.

If it fails: Recommend an accurate page-specific summary.

Retest: Inspect published wording; assess search data separately.

Not applicable: Only when this page type or issue is outside the audit scope.

Keep in mind: Description changes do not guarantee display or more clicks.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check the H1 and section headings

Find page structure that hides the topic or makes answers difficult to scan.

Use this for: Content pages with a main subject and subsections.

Read the main heading and the H2/H3 section headings in order. In the website editor or browser inspection, confirm that headings use heading elements rather than only large bold text. The H1 should identify the main page subject; lower-level headings should describe the sections beneath it.

Compare the main topic with relevant search language and the actual content. A heading such as “Benefits” may need a more specific label when readers cannot tell what it refers to. One clear H1 is a practical convention, not a universal ranking requirement. Do not add repetitive keywords to every heading.

Example

Hypothetical example: a roof-repair page says “Welcome” and “More information.” Recommend headings naming roof repair and the specific repair types discussed.

  1. Read the heading outline.
  2. Check topic and section labels.
  3. Inspect semantic heading levels.
More help and optional notesMedium · Editor
PassThe heading structure communicates the main topic and logical sections.
FailVague, misleading or structurally incorrect headings make the reviewed content difficult to understand or navigate.

If it fails: Correct unclear labels or heading levels.

Retest: Inspect the revised heading outline and structure.

Not applicable: Only when this page type or issue is outside the audit scope.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Compare overlapping or duplicate content

Decide whether similar pages serve distinct needs or compete to explain the same thing.

Use this for: Similar pages or duplicate-content warnings identified during the audit.

Open candidate pages side by side. Compare their titles, main answers, examples, intended audience and next steps. Use Search Console’s query and page filters to see how the pages appear for relevant searches. Similar words alone are not enough to establish an unnecessary duplicate.

Choose a specific recommendation: keep distinct pages and clarify their roles; update an outdated page; investigate technical duplicates; or propose a merge when both pages serve the same task. Before a merge, check useful content, incoming links and the correct replacement. Keep implementation subject to review rather than automatically deleting short pages.

Example

Hypothetical example: a pruning tutorial and seasonal calendar serve different tasks. Two near-identical calendars may instead justify a reviewed consolidation.

  1. Compare answers and visitor tasks.
  2. Check search data and incoming links.
  3. Choose a justified recommendation.
More help and optional notesMedium · Editor
PassCandidate overlap has a justified recommendation based on page purpose and useful content.
FailPages are selected for deletion or consolidation solely by word count, shared terms or a similarity score.

If it fails: Clarify roles or propose reviewed consolidation.

Retest: Confirm retained pages satisfy their intended tasks.

Not applicable: No meaningful overlap or duplicate-content candidates were found.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Compare repeated problems across page templates

Determine whether a title, heading or content defect is shared or page-specific.

Use this for: Groups of pages sharing a layout or publishing rule.

Compare several pages using the same layout, including a normal example. Inspect published titles, descriptions, headings, repeated copy and links against the website editor’s fields.

Ask which shared rule produces a repeated mistake. A missing service-name field may explain identical titles; one blank record needs a local edit. Bound the correction to the affected group and test another page type before a broad change.

Example

Hypothetical example: three services share “Services | Example Company.” Check whether the title template ignores the service-name field before assigning separate rewrites.

  1. Compare equivalent pages.
  2. Identify repeated field or template problems.
  3. Separate shared and individual fixes.
More help and optional notesMedium · Developer
PassRepeated problems have inspected examples and a bounded affected group, or the sample shows no repeated defect.
FailTool counts are reported as verified sitewide defects without checking examples.

If it fails: Correct shared causes; preserve page-specific details.

Retest: Test affected and unaffected templates.

Not applicable: The site has no repeated page types within the audit scope.

Keep in mind: Completed diagnosis does not resolve identified website defects.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Compare mobile usability and page speed

Find mobile task failures and measured loading or interaction problems.

Use this for: Important pages and visitor actions used on mobile.

Compare the main answer, headings, images and links on phone and desktop. Try menus, forms and primary buttons in test mode, or stop before an unintended submission. Look for cut-off text, obstructive overlays and unusable controls. A narrow desktop preview helps, but use a real phone where possible.

Run the public URL in PageSpeed Insights and compare Mobile with Desktop. Separate real-user field data from the simulated laboratory run. Check whether field data covers this URL or the wider origin, meaning scheme, hostname and port. Investigate the named bottleneck rather than only the score.

Example

Hypothetical example: mobile hides service-area information, and the lab run flags a large banner. Request those specific checks instead of relying on the desktop score.

  1. Try phone and desktop tasks.
  2. Compare PageSpeed Insights results.
  3. Investigate the specific obstacle.
More help and optional notesMedium · Developer
PassThe review identifies affected tasks and measurement conditions, including tests with no observed obstacle.
FailA lab score is presented as proof that all users have the same experience.

If it fails: Address reproduced obstacles and measured bottlenecks.

Retest: Repeat tasks under comparable measurement conditions.

Not applicable: Only when mobile experience is excluded from the agreed assignment.

Keep in mind: Missing field data is unknown, not a Core Web Vitals pass. Review completion does not resolve measured problems.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Choose SEO Fixes and Check the Results

Turn a diagnosis into a specific correction: restore an important page’s access, repair a broken link, clarify a misleading title or fill a missing answer. Give shared technical problems to the platform owner and page-specific writing problems to the editor. A completed audit does not mean every repair is already finished.

Choose the most important confirmed SEO fixes

Put consequential, well-supported problems ahead of cosmetic warnings.

Use this for: Confirmed findings, unresolved hypotheses or access blockers needing action.

Start with active security issues, widespread loading failures and unintended exclusions on important public pages. Next consider broken visitor tasks, missing useful links and misleading content. Compare the affected pages and the risk of the change; a large tool count may describe harmless duplicate variants. Separate missing access from a confirmed website fault.

Example

Hypothetical example: restore an accidentally excluded service page before shortening a clear title. A broken enquiry path may be even more urgent.

  1. Separate defects from open investigations.
  2. Rank actual consequences.
  3. Check dependencies and change risk.
More help and optional notesHigh · SEO lead
PassEach priority explains affected scope, evidence confidence and why the fix comes next.
FailPriority is based only on a tool label or a promised traffic gain.

If it fails: Reorder by impact and implementation constraints.

Retest: Reassess when evidence or importance changes.

Not applicable: No findings or blockers need action after the review.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Give the editor or developer a specific fix

Make the next action clear enough to implement and verify.

Use this for: Findings requiring a fix or another person’s help.

For each important finding, identify the URL, current result and intended result. Ask the editor to correct a named title, heading or missing answer. Ask the developer to inspect the exact response, directive, sitemap rule or template behind a technical mismatch. Include one reproducible example and the check that will demonstrate the correction; a formal report is optional.

Example

Hypothetical handoff: “Replace the service page’s missing maintenance PDF with the approved current file, then open it from that page on a phone.”

  1. Choose the responsible editor or developer.
  2. Name the mismatch and correction.
  3. Agree the retest.
More help and optional notesHigh · SEO lead
PassThe owner, next action and acceptance test are clear enough to reproduce the issue.
FailThe next person cannot identify the issue, responsibility or test needed to close it.

If it fails: Clarify responsibility, correction and closure test.

Retest: Have the implementer reproduce the original test.

Not applicable: No findings require implementation or a handoff.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Retest the affected page after each fix

Confirm the original fault is gone before evaluating later search changes.

Use this for: An audit finding with an implemented fix.

Repeat the same test on the published page: follow the repaired link, inspect the corrected title, retry the mobile control or check the changed indexing instruction. For a shared-template fix, include another affected page and a different template. Later Search Console updates may lag the live repair, so keep crawl, indexing and traffic observations separate from the implementation result.

Example

Hypothetical example: noindex removal is visible today, but Search Console still shows the earlier crawl. Verify the live repair and check indexing separately.

  1. Repeat the original live test.
  2. Sample shared changes.
  3. Review fresh search data separately.
More help and optional notesHigh · SEO lead
PassThe original mismatch is resolved, and any separate search follow-up is understood.
FailA ticket closes because code shipped, without checking the affected URL.

If it fails: Reopen unresolved defects or dependencies.

Retest: Review fresh crawl or report data.

Not applicable: No fixes have been implemented yet; an unresolved dependency is Blocked.

Optional: URL, observed result and next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Reset this checklist?

This removes saved statuses, evidence and result dates for the checks on this page. Other checklists keep their records. Export a CSV first if you need a copy.

Quick reference

SEO Audit Checklist infographic

Keep these eight selected actions handy. The complete checklist above includes the steps, conditions and follow-up checks.

SEO Audit Checklist infographic summarizing audit scope, search evidence, indexing, content review and prioritized repairs. Text version below.
Eight selected actions from SEO Audit Checklist. Use the complete checklist for steps, conditions and retests.
Read the infographic as text
  1. Choose important pages to audit
  2. Compare clicks and impressions over time
  3. Check manual actions and security alerts
  4. Investigate important unindexed pages
  5. Compare declared and selected canonicals
  6. Check whether each page answers its search
  7. Prioritize confirmed problems by impact
  8. Retest the affected page after each fix

Choose an action to open its full instructions above.

A useful result, every time

Check a task. Choose a result.

This is a manual SEO workflow. It helps you decide what to investigate and keep a usable record. It does not crawl your website or verify your answers automatically.

  1. Choose your scope. Pick the relevant task group and representative pages you are authorized to inspect.
  2. Run the stated check. Follow the steps, then choose your result. Click the square for Pass, or use the result menu for another status. You do not need to type anything.
  3. Assign the next action. Fix a problem when you can, or ask the right person for help. Optional notes can remind you what to do next. Check the result again after a fix.

What your progress means

Review progress counts passes and failures against applicable checks. Failed work still counts as reviewed. Blocked and untested checks remain unfinished. This is not an SEO score.

Untested
You have not checked this yet.
Pass
You checked it and it works as described.
Fail
You checked it and found something to fix.
Blocked
You need access, information or someone’s help.
Not applicable
This task does not apply to your website.

Export CSV downloads the checks currently shown and any optional notes. Print expands the instructions for that view. Saved results stay in this browser; there is no account sync.

A visual working guide

Move from an observation to a supported action

An audit decision sequence separating an observation, a hypothesis, a confirming check, and an action with a retest.
This is an illustrative audit method. Keep possible explanations separate from confirmed causes, and retain the evidence behind each decision. Original instructional illustration.
Apply the workflow

Understand the SEO Problems You Find

Use these answers to interpret indexing exclusions, falling search clicks, duplicate pages, redirect mistakes and performance warnings. They help you choose the right correction without turning every tool alert into a website change.

Why Is a Page Crawled but Not Indexed?

“Crawled, currently not indexed” means Google fetched the page but has not indexed it. That label does not identify one universal content defect. In URL Inspection, compare the crawl date with your latest publication, then inspect whether the page contains the intended answer and duplicates another useful page.

“Discovered, currently not indexed” means Google knows the address but has not yet crawled it. Check useful internal links and ask the technical owner about access or server issues when the pattern warrants it. For either status, repeated indexing requests or extra filler text are not a substitute for diagnosing the page.

Which SEO Problems Should You Fix First?

Fix a confirmed failure according to what it prevents. An accidentally inaccessible service page, an active security issue or a broken main enquiry route deserves attention before a minor snippet improvement. These are practical audit priorities, not a universal Google severity score.

  • Act urgently on active security issues and widespread failures affecting important pages.
  • Correct unintended indexing blocks and broken visitor tasks on priority pages.
  • Then schedule specific title, content, internal-link and performance improvements.

Which Checklist Helps You Implement an SEO Audit Fix?

Use the technical checklist for response codes, indexing instructions, canonicals and performance investigations. Use the on-page checklist to edit titles, headings, copy and images. Start with the diagnosed problem, then repeat its original test after publication. Checklist notes remain optional.

What Are the Steps in an SEO Audit?

Check search alerts and performance first, then inspect important indexing exclusions. Review titles, descriptions, headings and content on the affected pages. Follow their links and try their main actions on mobile. Finish with a small set of specific fixes and the tests that will confirm them. Skip checks that genuinely do not apply; unavailable required access is a blocker.

How Do You Audit a Small-Business Website?

For a small business, start with the pages that describe what you sell and how customers contact you. Compare each service page with the actual service and area covered. Check that the title and main heading identify that offering, then follow the enquiry link from a phone.

Hypothetical example: a landscaping company’s patio page appears for patio-repair queries but describes only new installations. Verify whether repairs are actually offered. If not, correct the misleading promise rather than adding invented repair claims to attract those searches.

What Determines the Cost of an SEO Audit?

Compare quotes by the actual checks included: Search Console analysis, inspected page types, a crawl where needed, content review, mobile testing and technical investigation. Ask whether the price also covers implementation and retesting. A title export and a hands-on investigation of a lost service page are different assignments; this checklist does not supply a market price.

Which Tools Do You Need for an SEO Audit?

Start with Search Console, your website editor and a browser. Search Console supplies search and indexing reports; the editor shows page fields and publishing settings; the browser lets you inspect the published result. PageSpeed Insights adds loading and interaction diagnostics.

A crawler can help collect titles, links and response codes across a larger site. It is optional for a small manual audit. Whatever tool you use, open a flagged example before accepting its diagnosis.

How Do You Sample Pages on a Larger Website?

Group pages by shared layout and meaningful variations: available versus discontinued products, articles with versus without downloads, or real language versions. Inspect important URLs and examples of each variation. If a fault appears, check another page with the same layout before treating it as widespread.

A sample can uncover a pattern, but it cannot prove that every uninspected page is affected. Expand the check where results conflict or a proposed shared fix has a broader impact.

Why Did Search Clicks Fall?

In Search Console, compare the same page or query across equivalent periods. CTR means click-through rate: clicks divided by impressions. Interpret it alongside impressions and position rather than using a fixed “good CTR” target.

  • Fewer impressions: inspect affected queries, indexing changes and seasonal demand. Check whether the loss is localized before choosing a technical or content explanation.
  • Similar impressions but fewer clicks: compare query mix, average position, title and page promise. Search-result competition may also differ.
  • Search clicks steady but recorded leads down: test the visitor action and analytics event.
  • Only mobile declines: compare mobile queries and pages, then reproduce the affected phone task.

How Do You Diagnose a Redirect That Sends Visitors to the Wrong Page?

Start from the actual link that a visitor uses. Watch the address change and read the final page. If the destination is wrong or the page never finishes loading, ask the developer to inspect the redirect responses and final status in Chrome’s Network panel; Preserve log keeps requests visible across navigation.

Hypothetical example: an old installation guide redirects to the homepage even though its replacement guide exists. Recommend reviewing the old-to-new mapping and updating internal links to the replacement, rather than adding another redirect without checking the chain.

Is Duplicate Content Always an SEO Problem?

No. A campaign parameter can produce another address for the same page without creating a second editorial resource. That needs a preferred-URL review. Two guides that answer different questions can also share terminology without being unnecessary duplicates.

When both pages answer the same question, compare useful details and query/page performance before proposing consolidation. Preserve the strongest relevant material and plan the replacement address and links. Short length alone is not a reason to delete a page.

How Should You Review Backlinks During an SEO Audit?

If backlinks relate to the audit question, inspect examples from an existing link report and compare the source page, destination and known campaign context. Ask who arranged paid placements or partnerships. An unfamiliar link or a tool’s toxicity label does not establish a Google policy action.

Check Search Console’s Manual actions report separately. Review suspected manipulative campaigns against the spam guidance with a qualified owner. Do not use a toxicity score as an automatic instruction to remove or disavow links.

What Should a Technical SEO Handoff Include?

Give the technical owner a URL and the exact contradiction: “The approved public guide is listed in the sitemap, but its current response includes noindex.” Ask which page setting or shared rule creates it. Confirm the intended change before removing any restriction. Retest the affected page and a deliberately excluded page after a shared change.

Why Do Sitemap and Indexed Page Counts Differ?

The website editor lists managed content, a sitemap lists discovery addresses, a crawler lists the pages it reached and Search Console reports Google’s observed URLs. These inventories have different purposes and dates. Their totals need not match.

Compare exceptions instead: an important published page missing from useful links, an old address still in the sitemap, or a preferred public page unexpectedly excluded from the index. Investigate the specific address rather than trying to make every count identical.

Why Does the Live Test Disagree with Search Console?

Compare the exact address and time represented by each result. URL Inspection’s indexed data may describe the last crawl before your repair; the live test checks the current page. Inspect the crawl date and deployment date before treating this as a new failure.

A successful live test does not guarantee indexing, predict the selected canonical or establish a ranking. Verify the changed output now and check later indexed information separately. Missing report access leaves the report-dependent conclusion untested.

Which SEO Audit Warnings Need a Manual Check?

Title-length warnings need a readability check, not automatic trimming. A removed page returning not found can be correct. An excluded duplicate may correctly point to another preferred address. Review the page’s purpose before applying the tool’s suggested fix.

For structured-data warnings, compare the detected markup with visible page facts and the requirements of the relevant search feature. Do not invent reviews, prices or author credentials to clear a warning. Correct markup cannot guarantee a rich result.

How Do You Interpret Core Web Vitals in an SEO Audit?

Core Web Vitals describe loading, responsiveness and visual stability. In PageSpeed Insights, LCP concerns when the largest visible content appears, INP concerns interaction response and CLS measures unexpected layout movement. Investigate the metric and affected experience, not only the overall score.

Good field targets are LCP at most 2.5 seconds, INP at most 200 milliseconds and CLS at most 0.1, assessed at the 75th percentile. Field data can be missing or cover the wider origin. A laboratory run helps diagnose bottlenecks but does not replace unavailable real-user measurements.

What Should You Keep from the SEO Audit?

Keep the small set of findings someone can act on: an unintended indexing block, a wrong search promise, missing answers, a broken link or a measured mobile obstacle. For each, retain the affected example, chosen correction and retest if useful. A long report is optional.

After fixes, compare fresh Search Console data with the original dates, pages and filters. A working repair establishes that the defect was corrected; a later traffic change still needs interpretation alongside demand and other site changes.

A clear process, with honest limits.

Follow the steps, choose the result that matches what you found, and check again after changes. Notes are optional. A completed check does not guarantee indexing, traffic or rankings. How the checklists work.