Use a Verifiable SEO Checklist Before You Scale Work or Hire Support

This checklist is for business owners, marketing managers, and in-house teams that want a structured view of current SEO readiness before expanding work, evaluating a supplier, or reviewing what an existing supplier has delivered. It complements the existing SEO audit guide: the audit explains root causes, while this page helps you verify whether specific foundations and controls are present.

Use one consistent record for every applicable item. Evidence required: note the report, page, account, crawl result, screenshot, or configuration you inspected. Pass or fail: define what correct behavior looks like before checking the item. Severity: rate the business and search impact of a failure rather than relying on a tool label. Owner: assign the person or team that can make the change. Corrective action: state the smallest change that addresses the confirmed problem. Validation: specify the re-test that proves the condition changed.

If you are reviewing an agency, use the checklist as a validation tool rather than a scorecard for blame. A failed item can be a legitimate backlog decision if the evidence, impact, dependency, and owner are documented. A checked item should be supported by evidence you can inspect, not only by a status label in a report.

Skip items that do not apply. A business with no genuine local customer location does not need location-specific optimization simply to complete a checklist. A store with no editorial program does not need a publishing workflow invented for the sake of activity. The purpose is to verify the controls your site and business actually require.

Technical checks come first because they determine whether important pages can be discovered, fetched, rendered, indexed, and used as intended. Do not assume every warning is severe. The test is whether the condition affects valuable pages, templates, or user journeys.

Crawlability and indexing checks:

• Robots directives. Evidence required: robots.txt and page-level robots directives for important templates. Pass if required pages are crawlable and intentionally excluded pages are documented. Fail if valuable pages are blocked unintentionally. Severity: critical when broad sections are affected. Owner: technical SEO and engineering. Corrective action: change the blocking rule or page directive. Validation: fetch and re-crawl representative URLs after deployment.
• XML sitemap. Evidence required: current sitemap output and Search Console submission state. Pass if canonical, indexable URLs intended for search are represented and stale or redirected URLs are excluded. Fail if important URLs are missing or invalid URLs dominate the file. Severity: moderate to high depending on scope. Owner: platform or SEO. Corrective action: update sitemap generation logic. Validation: regenerate, re-submit, and compare the resulting URL set.
• Crawl errors and broken internal links. Evidence required: a fresh crawl and samples of affected pages. Pass if important paths resolve to intended destinations. Fail when users or crawlers repeatedly reach missing or unintended URLs. Severity: based on affected templates and traffic importance. Owner: engineering, content operations, or SEO. Corrective action: repair source links or intended destinations. Validation: repeat the same crawl scope and confirm the broken references are gone.
• HTTPS coverage. Evidence required: protocol checks across important templates and canonical destinations. Pass if intended pages load securely and internal references resolve consistently. Fail if mixed protocol behavior, insecure assets, or unintended protocol duplicates remain. Severity: high when security or canonical consistency is affected. Owner: engineering or infrastructure. Corrective action: enforce secure delivery and consistent internal references. Validation: re-test representative pages and redirects.
• Redirect paths. Evidence required: crawl exports and server responses for changed URLs. Pass if redirects serve a clear migration or consolidation purpose and land on the most relevant destination. Fail when chains, loops, or irrelevant targets create unnecessary hops or broken journeys. Severity: based on breadth and page value. Owner: engineering with SEO review. Corrective action: update redirect mappings. Validation: test old and current URLs directly after deployment.
• Mobile rendering. Evidence required: browser inspection, Search Console information where available, and representative device tests. Pass if primary content, navigation, forms, and calls to action remain usable. Fail if important content is hidden, inaccessible, or broken on mobile. Severity: high when core journeys are affected. Owner: front-end engineering or design. Corrective action: fix the responsive behavior. Validation: re-test the same templates and interactions.

Performance and page experience checks:

• Core Web Vitals evidence. Evidence required: field data where available plus representative page diagnostics. Pass when important templates do not show a persistent user-experience problem requiring action. Fail when a repeatable performance issue affects meaningful page groups. Severity: based on scope and user impact. Owner: engineering or performance specialists. Corrective action: address the measured bottleneck rather than chasing a generic score. Validation: compare the same templates using the same evidence source.
• Page resource review. Evidence required: waterfall, browser, or page-speed diagnostics. Pass when oversized images, blocking resources, scripts, and server delays are understood and proportionate to the experience. Fail when a specific resource pattern repeatedly slows important pages. Severity: based on repeatability and page value. Owner: engineering. Corrective action: optimize the identified bottleneck. Validation: re-run the same test under comparable conditions.
• Hosting and server behavior. Evidence required: server responses, uptime history, caching behavior, and representative request timing. Pass when the platform serves stable responses without obvious infrastructure bottlenecks. Fail when outages, timeouts, or consistently slow origin responses affect important pages. Severity: high for broad reliability problems. Owner: infrastructure or platform engineering. Corrective action: resolve the confirmed capacity, caching, application, or hosting issue. Validation: repeat the request tests and monitor the affected templates.

Site structure checks:

• Hierarchy and navigation. Evidence required: crawl depth, navigation paths, and representative user journeys. Pass if important content sits in a logical structure and can be reached without obscure paths. Fail if priority pages are effectively isolated or hidden behind inconsistent navigation. Severity: based on the business value of affected pages. Owner: information architecture, SEO, or product. Corrective action: simplify and clarify navigation. Validation: re-crawl and manually test the intended paths.
• Internal linking. Evidence required: inlink reports and source-page review. Pass if important pages receive relevant internal support from pages where the link helps users. Fail if important pages are orphaned, linked only from irrelevant contexts, or repeatedly pointed to with broken destinations. Severity: moderate to high by page importance. Owner: content operations or SEO. Corrective action: add, repair, or remove links based on context. Validation: re-crawl and confirm the intended links exist.
• URL consistency. Evidence required: crawl exports and routing rules. Pass if URLs are stable, readable, and consistently canonicalized. Fail if unnecessary parameters, duplicate routes, or session-dependent URLs create conflicting versions. Severity: based on duplication and crawl impact. Owner: engineering and technical SEO. Corrective action: normalize routing and canonical behavior. Validation: re-crawl variants and verify the intended canonical state.

Most content problems are easier to solve when every page has a documented purpose. Use the existing SEO mistakes guide for common failure patterns, but validate each checklist item against your own page set and search evidence.

Content inventory and ownership:

• Page inventory. Evidence required: a complete crawl or CMS export matched to analytics and Search Console where available. Pass if every important indexable page has a clear purpose, owner, and status. Fail if large groups have no identifiable role or overlap materially. Severity: based on the importance and scale of affected pages. Owner: SEO and content operations. Corrective action: classify, consolidate, improve, redirect, or retire pages according to evidence. Validation: re-run the inventory and confirm each changed URL has the intended state.
• Thin or low-value pages. Evidence required: page purpose, query data, conversions, internal links, and manual content review. A previously published threshold of under 300 words can flag pages for inspection, but it is not a pass or fail rule. Pass if the page satisfies its intended user need regardless of length. Fail if it lacks the information necessary for that purpose. Severity: based on intent value and duplication. Owner: editorial and SEO. Corrective action: expand, merge, rewrite, or remove based on the diagnosed gap. Validation: review the revised page against the original user need and query set.
• Duplicate and near-duplicate content. Evidence required: crawl similarity reports and manual comparison. Pass if similar pages have distinct, useful purposes or are intentionally consolidated. Fail if several pages compete for the same intent without a clear reason. Severity: high when valuable queries or large template sets are affected. Owner: SEO, editorial, or product. Corrective action: differentiate, consolidate, redirect, or adjust canonical handling where appropriate. Validation: re-crawl and confirm the competing set now has clear ownership.
• Orphaned content. Evidence required: crawl plus sitemap, CMS, or analytics comparison. Pass if important pages have discoverable internal paths. Fail if valuable pages exist without relevant internal links. Severity: based on page importance. Owner: content operations or SEO. Corrective action: add contextual or navigational links where useful. Validation: re-crawl and confirm discovery paths.

Keyword and intent checks:

• Current query map. Evidence required: Search Console query-to-page data and page purpose. Pass if important queries consistently map to the intended page. Fail if the wrong page ranks or several pages compete for the same intent. Severity: based on commercial importance. Owner: SEO. Corrective action: clarify page purpose, content, internal anchors, consolidation, or routing. Validation: re-check query-to-page associations after processing.
• Opportunity gaps. Evidence required: customer questions, search data, competitor result review, and business priorities. Pass if meaningful demand is intentionally covered or deliberately excluded. Fail if high-relevance customer needs have no suitable page. Severity: based on opportunity and business fit. Owner: SEO, marketing, or product. Corrective action: create or improve the most appropriate page only when the demand is supported. Validation: confirm the page answers the intended need and is discoverable internally.

On-page checks:

• Title accuracy. Evidence required: crawl export plus manual review of representative pages. A previously published review point used 60 characters, but display behavior varies. Pass if the title accurately distinguishes the page and matches its intent. Fail if it is duplicated, misleading, or disconnected from the content. Severity: moderate unless applied incorrectly at scale. Owner: SEO or editorial. Corrective action: rewrite the title. Validation: re-crawl and inspect rendered search snippets over time without treating display format as guaranteed.
• Meta description quality. Evidence required: crawl export and manual review. A previously published review point used 155 characters, but that is not a guaranteed display limit. Pass if the description accurately summarizes the page and supports the intended user decision. Fail if it is duplicated, misleading, or irrelevant. Severity: usually low to moderate. Owner: editorial or SEO. Corrective action: rewrite where useful. Validation: re-crawl and confirm the correct text is deployed.
• Primary visible heading. Evidence required: rendered page inspection and crawl extraction. Pass if the page has a clear H1 that describes the content without forced repetition. Fail if the heading is missing, misleading, or structurally confused. Severity: based on scale and clarity impact. Owner: editorial, design, or engineering. Corrective action: correct the page template or content. Validation: re-render and crawl the affected pages.
• Internal anchor relevance. Evidence required: inlink export and manual source-page review. Pass if anchor text helps users understand the destination in context. Fail if anchors are misleading, generic where specificity is needed, or systematically over-optimized. Severity: based on scale. Owner: content operations or SEO. Corrective action: revise anchors naturally. Validation: re-crawl and inspect representative source pages.

A backlink review should identify useful references, broken destinations, suspicious patterns, and realistic authority gaps. Do not treat a third-party toxicity score as proof of a penalty. Evidence, context, and pattern matter.

Current link profile checks:

• Referring-source quality. Evidence required: backlink export plus manual review of representative domains and linked pages. Pass if relevant editorial, partner, industry, or customer-facing references make sense in context. Fail if a material pattern appears manipulative, compromised, or unrelated to the business. Severity: based on pattern strength and affected pages. Owner: SEO or digital PR. Corrective action: investigate the source pattern, recover legitimate references, or stop risky acquisition practices. Validation: re-check the relevant referring sources and linked pages.
• Anchor-pattern review. Evidence required: anchor export and source context. A previously published warning example used the same optimized phrase 20 or more times; treat that only as a prompt for investigation, not a penalty threshold. Pass if anchors are naturally varied and contextually plausible. Fail if there is credible evidence of coordinated manipulative placement. Severity: based on pattern and intent. Owner: SEO. Corrective action: stop or unwind the identified practice where possible. Validation: document changed or removed placements and reassess the pattern.
• Broken backlink recovery. Evidence required: links pointing to missing or retired URLs and the historic purpose of each destination. Pass if valuable old references resolve to relevant current content or an intentional terminal state. Fail when valuable links land on missing pages without a reason. Severity: based on link relevance and page importance. Owner: SEO and engineering. Corrective action: use a relevant 301 redirect when a true replacement exists, or restore suitable content where justified. Validation: request the old URL and confirm the intended destination and status.

Manual actions and security checks:

• Search Console status. Evidence required: manual-actions and security-issues reports. Pass if no active issue is reported or an existing issue has an owned remediation plan. Fail if an active issue is ignored or ownership is unclear. Severity: critical for active confirmed issues. Owner: senior SEO, engineering, or security depending on the cause. Corrective action: remediate the documented issue according to Google's process. Validation: confirm the affected condition is resolved in the relevant report.
• Domain-history review. Evidence required: available historic pages, ownership records, backlink history, and current site behavior. Pass if no material historic pattern conflicts with the current site's purpose or any legacy problem has been addressed. Fail if spam, compromise, or unrelated legacy use appears to affect current search or security conditions. Severity: evidence-dependent. Owner: SEO and security. Corrective action: investigate the specific legacy problem rather than assuming age alone is harmful. Validation: document the remediation and re-check current behavior.

Authority opportunity checks:

• Link-worthy assets. Evidence required: existing research, tools, original resources, expert material, or genuinely useful references. Pass if the site has something relevant audiences may reasonably cite. Fail if outreach depends only on asking for links to ordinary commercial pages without a clear reason. Severity: strategic rather than technical. Owner: content, PR, or SEO. Corrective action: improve the asset or create a useful resource tied to real audience needs. Validation: review outreach response quality and any earned relevant references.
• Unlinked coverage. Evidence required: verified brand or expert mentions and their source context. Pass if important mentions already link where appropriate or have no reasonable need to link. Fail when a relevant publisher has referenced the business and a useful destination is clearly missing. Severity: low to moderate. Owner: PR or outreach. Corrective action: request attribution politely when appropriate. Validation: confirm the publisher's final page state.
• Competitor reference gap. Evidence required: a set of 10-15 genuinely comparable competitor domains and the sites that cite them. Pass if your authority plan reflects relevant opportunities rather than raw volume. Fail if competitors consistently earn useful references from sources your business could credibly serve but has never evaluated. Severity: based on relevance to target search areas. Owner: SEO and digital PR. Corrective action: identify the underlying asset or relationship that made the competitor reference possible. Validation: track whether comparable relevant references are earned, not whether a quota is filled.

Competitive review tells you what searchers are currently being shown; conversion review tells you whether your own site records useful business actions. Neither should be reduced to copying competitors or celebrating traffic without measurement.

Competitive benchmarking:

• Comparable search competitors. Evidence required: the top 5 domains that repeatedly appear for the query groups tied to your business, not merely companies you compete with offline. Pass if the set is genuinely relevant to the same search intents. Fail if the comparison uses unrelated publishers, marketplaces, or national brands that do not compete for the same user need. Severity: strategic. Owner: SEO. Corrective action: rebuild the competitor set by query group. Validation: manually confirm the domains in current search results.
• Winning-page analysis. Evidence required: the pages competitors rank with, the query intent they satisfy, their content format, internal support, and relevant external references. Pass if your analysis identifies why a format may fit the intent without assuming that copying it will rank. Fail if the output is only a list of competitor metrics. Severity: strategic. Owner: SEO and content. Corrective action: convert observations into hypotheses about user needs and page requirements. Validation: review whether resulting page decisions are differentiated and evidence-based.
• Visibility gaps. Evidence required: query sets where relevant competitors appear and your site does not. Pass if each gap is either intentionally outside scope or mapped to a suitable existing or planned page. Fail if important demand is unowned and no decision has been made. Severity: based on business relevance. Owner: SEO and marketing. Corrective action: improve or create the appropriate page when justified. Validation: confirm the new or revised page is internally discoverable and aligned to the intended query.

Conversion setup:

• Analytics implementation. Evidence required: Google Analytics 4 configuration, live-event tests, tag inspection, and data ownership. Pass if important page views and business actions are recorded once, with understandable naming and no obvious duplication. Fail if events are missing, duplicated, or controlled in an account the business cannot access. Severity: high when reporting or investment decisions depend on the data. Owner: analytics or marketing operations. Corrective action: fix tagging and ownership. Validation: perform controlled test actions and confirm the expected records.
• Conversion definitions. Evidence required: an agreed list of meaningful actions such as purchases, qualified forms, calls, bookings, or other business-specific outcomes. Pass if primary and secondary actions are clearly distinguished. Fail if every interaction is treated as equivalent or important outcomes are not tracked. Severity: high for decision-making. Owner: marketing, analytics, and commercial stakeholders. Corrective action: define and configure the event hierarchy. Validation: test each action and confirm it appears in reporting as intended.
• Search Console connection. Evidence required: verified property access and the intended analytics linkage where used. Pass if the business can inspect search performance and ownership is retained internally. Fail if access is missing or controlled only by an external supplier. Severity: moderate to high. Owner: SEO or analytics. Corrective action: verify ownership and access. Validation: confirm the property and data are visible to the correct internal users.
• Cross-channel consistency. Evidence required: definitions used in organic, paid, email, and other campaign reporting. Pass if the same business action is interpreted consistently across channels. Fail if incompatible definitions make channel comparisons misleading. Severity: based on reporting dependence. Owner: analytics. Corrective action: align naming and attribution rules. Validation: compare controlled test events across reporting systems.
• Call-to-action usability. Evidence required: page review, device testing, and conversion-path inspection. Pass if users can identify and complete the intended next step without hidden or broken controls. Fail if priority pages have unclear, inaccessible, or non-functioning calls to action. Severity: based on page traffic and commercial role. Owner: design, product, or marketing. Corrective action: improve visibility, clarity, or functionality. Validation: test the journey on representative devices.

Attribution controls:

• Phone and offline outcomes. Evidence required: the business's actual lead flow and any call or CRM tracking in use. Pass if important offline actions can be connected to the appropriate source without collecting unnecessary data. Fail if major lead types disappear from performance reporting. Severity: based on revenue importance. Owner: analytics and sales operations. Corrective action: implement an appropriate compliant measurement method. Validation: run controlled test leads through the process.
• Value assignment. Evidence required: business-approved definitions for the relative value of different actions. Pass if reported values reflect a documented commercial assumption. Fail if arbitrary values create false precision. Severity: strategic. Owner: finance, marketing, or analytics. Corrective action: document and apply agreed values. Validation: reconcile reporting with the approved definitions.
• Campaign parameters. Evidence required: current campaign links and naming conventions. Pass if parameters are consistent enough to support reliable source reporting. Fail if inconsistent naming fragments the same campaign into multiple labels. Severity: moderate. Owner: marketing operations. Corrective action: standardize the naming convention. Validation: test new campaign links and confirm reporting classification.

Do not prioritize checklist items by how easy they are to mark complete. Prioritize by evidence strength, severity, dependency, implementation risk, and the time required to validate the changed condition.

Short implementation stage, often framed as 1-2 weeks:

• Priority-page metadata review. Evidence required: crawl export and manual review of the top 20 business-critical pages. Pass if titles and descriptions are accurate and distinct. Fail if they are duplicated, misleading, or disconnected from page purpose. Severity: usually moderate. Owner: SEO or editorial. Corrective action: rewrite only affected fields. Validation: re-crawl after deployment.
• Image and caching corrections. Evidence required: page diagnostics showing oversized assets or caching gaps. Pass if the identified bottleneck is resolved. Fail if the same issue persists. Severity: based on user impact. Owner: engineering. Corrective action: optimize the confirmed resource or caching behavior. Validation: repeat the original diagnostic.
• Broken internal destinations. Evidence required: crawl list and source pages. Pass if links resolve to intended relevant destinations. Fail if users or crawlers hit missing or incorrect URLs. Severity: based on scale and page value. Owner: content operations or engineering. Corrective action: update source links or restore the correct destination. Validation: re-crawl.
• Sitemap and ownership checks. Evidence required: current sitemap, Search Console access, and submission state. Pass if intended indexable URLs are represented and the business controls access. Fail if stale URLs dominate or ownership is missing. Severity: moderate to high. Owner: SEO or platform. Corrective action: fix generation and access. Validation: regenerate and confirm the submitted state.
• Google Business Profile eligibility check. Evidence required: whether the business has a genuine eligible location or service-area presence. Pass if the profile reflects a real eligible business and accurate information. Fail if the business is ineligible, misrepresented, or the profile is unnecessary. Severity: high when misrepresentation creates policy risk. Owner: local marketing or operations. Corrective action: correct the profile or remove unsupported assumptions. Validation: review the final profile state and business information.
• Conversion measurement verification. Evidence required: controlled test actions. Pass if important outcomes are recorded correctly. Fail if events are missing or duplicated. Severity: high for reporting. Owner: analytics. Corrective action: repair tagging. Validation: repeat test conversions.

Medium implementation stage, often framed as 4-8 weeks:

• Content consolidation. Evidence required: overlapping page sets, query mapping, and performance history. Pass if each important intent has a clear owner. Fail if several pages compete without distinct purpose. Severity: high for affected query groups. Owner: SEO and editorial. Corrective action: merge, differentiate, redirect, or rewrite according to the evidence. Validation: re-crawl and review the query-to-page map.
• Internal-link improvement. Evidence required: orphan and inlink reports plus page context. Pass if priority pages have useful, relevant internal paths. Fail if they remain isolated or supported by misleading anchors. Severity: based on page value. Owner: content operations. Corrective action: add or revise contextual links. Validation: re-crawl.
• Core service content improvement. Evidence required: customer questions, query intent, conversion needs, and existing page gaps. Pass if pages answer the real decision need without unnecessary duplication. Fail if important information remains absent. Severity: commercial. Owner: subject matter experts, content, and SEO. Corrective action: improve the appropriate existing page or create one only where a distinct need exists. Validation: editorial review plus search and conversion monitoring.
• Performance engineering. Evidence required: repeatable template-level bottlenecks. Pass if the measured issue is materially improved without regression. Fail if work changes unrelated assets but leaves the bottleneck untouched. Severity: based on scope. Owner: engineering. Corrective action: resolve the confirmed cause. Validation: repeat the original tests.
• Structured data review. Evidence required: visible page content, supported schema type documentation, and rendered markup. Pass if markup accurately represents the page and contains no unsupported claims. Fail if it misrepresents content, is invalid, or is added solely as a ranking tactic. Severity: policy and quality dependent. Owner: SEO and engineering. Corrective action: correct or remove unsupported markup. Validation: test the rendered markup and confirm it matches visible content.

Longer iteration stage, often framed as 3 months or more:

• Editorial production. Evidence required: a documented demand map, business priorities, available expertise, and quality review capacity. A previously published planning example used 2-4 new pieces monthly; treat that only as historical operating context, not as a required search cadence. Pass if new work serves distinct user needs and can be maintained. Fail if publishing continues without evidence of purpose. Severity: strategic. Owner: content leadership. Corrective action: adjust topics, formats, or production volume according to evidence. Validation: review whether the intended pages earn relevant impressions, engagement, or conversions without assuming a fixed publishing cadence is required.
• Authority development. Evidence required: useful assets, relevant publications, existing relationships, and competitor reference patterns. Pass if outreach is based on real relevance and editorial value. Fail if the plan depends on manufactured links or arbitrary quotas. Severity: high when risky tactics are involved. Owner: digital PR or SEO. Corrective action: replace manipulative tactics with legitimate relationship and asset-based outreach. Validation: verify earned references and source quality.
• Manual-action or spam remediation. Evidence required: confirmed Search Console notices, documented link or content patterns, and a remediation log. Pass when the documented issue has been addressed according to the applicable process. Fail when remediation is incomplete or unsupported. Severity: critical when an active confirmed issue exists. Owner: senior SEO with engineering or security support. Corrective action: complete the documented cleanup and request review where appropriate. Validation: confirm the relevant status after processing.
• Site-wide technical rollout. Evidence required: a validated fix on representative templates and a deployment plan. Pass if the correction works at scale without creating new conflicts. Fail if rollout produces regressions or unresolved variants. Severity: based on affected site scope. Owner: engineering. Corrective action: stage and deploy the validated change. Validation: re-crawl and monitor the affected templates after release.