A 42-Point CPA SEO Checklist Built for Evidence, Ownership, and Verification

This checklist is designed for diagnosis and execution, not box-ticking. Begin with the highest-dependency issues, then move into local accuracy, on-page relevance, content depth, and authority. Every item should produce evidence that another person can inspect.

Evidence required: save the relevant report, page URL, screenshot, crawl result, profile field, or search-platform record. Pass/fail condition: define what observable state counts as complete before work begins. Severity: use critical when an issue blocks discovery or creates material factual risk, high when it limits an important page or location, and routine when it refines a functioning setup.

Owner: assign technical fixes to the developer or technical SEO owner, service-page and editorial fixes to marketing with subject-matter review, and local profile corrections to the practice administrator or designated local-search owner. Corrective action: fix the documented cause, not a symptom. Validation: repeat the original check after implementation.

The source previously framed the initial technical review as 4-8 hours and referenced a historical 60% observation about skipped basics. Those figures are retained because they are part of the source record, but no supporting source URL is present here. Treat them as historical context requiring reconciliation, not as verified benchmarks.

The source also described completion of priority work within 8-12 weeks. Use that only as a planning reference from the prior edition. Actual effort depends on site size, access, developer capacity, number of genuine locations, and the amount of corrective work uncovered.

Purpose: confirm that important accounting pages can be discovered, rendered, indexed, and used before spending heavily on expansion work. Treat technical findings as dependencies, not as a generic score.

• Secure delivery. Evidence required: browser and crawl checks showing important pages resolve securely. Pass if the preferred version loads without certificate or mixed-content problems. Severity: critical. Owner: developer. Corrective action: repair protocol, certificate, or redirect issues. Validation: recrawl and retest representative pages.
• Mobile usability. Evidence required: manual device review plus current search-platform or performance diagnostics. Pass if navigation, forms, text, and key service content work without avoidable mobile friction. Severity: high. Owner: developer. Corrective action: fix responsive layout and interaction defects. Validation: repeat the same device and diagnostic checks.
• Page performance. Evidence required: PageSpeed Insights or equivalent diagnostics on representative templates. The source carried a target score above 70; treat that as a historical operating threshold, not an official ranking guarantee. Pass when material performance problems identified in the audit are resolved or accepted with a documented reason. Severity: high. Owner: developer. Corrective action: address the specific bottlenecks reported. Validation: rerun the same tests.
• XML sitemap. Evidence required: current sitemap contents and Search Console submission status. Pass if canonical, indexable priority pages are represented and stale or blocked URLs are not being relied on as discovery paths. Severity: high. Owner: technical SEO owner. Corrective action: regenerate or correct the sitemap. Validation: inspect the live file and submission record.
• Robots directives. Evidence required: robots.txt and page-level directives for priority sections. Pass if important service, location, team, and resource pages are not unintentionally blocked. Severity: critical. Owner: developer or technical SEO owner. Corrective action: remove unintended restrictions. Validation: test the affected URLs again.
• Canonicalization. Evidence required: crawl exports and page source for duplicate or parameterized versions. Pass if each important page points consistently to the intended canonical version. Severity: high. Owner: developer. Corrective action: fix conflicting canonicals, redirects, or internal links. Validation: recrawl the affected templates.
• Google Search Console. Evidence required: verified property access and current indexing reports. Pass if the correct property is available to the team and significant coverage issues are triaged. Severity: high. Owner: marketing or technical SEO owner. Corrective action: resolve access and documented indexing problems. Validation: confirm ownership and recheck affected URL states.

The source estimated 6-10 hours for this technical pass. Retain that as prior planning context only. The actual workload depends on platform complexity, site history, and whether implementation requires development.

Goal: make each priority accounting page understandable to prospects and search systems without forcing keywords or relevance the page does not support.

• Primary heading. Evidence required: rendered page and source. Pass if there is one clear H1 that accurately names the page topic. Severity: high. Owner: marketing or developer. Corrective action: remove competing primary headings or rewrite the heading to match the actual service. Validation: inspect the rendered heading structure.
• Title tags. Evidence required: crawl export and search appearance review. The source carried 50-60 characters as an operating range. Use it as an editorial check, not a hard ranking rule. Pass if the title is unique, descriptive, and aligned with the page. Severity: high. Owner: marketing. Corrective action: rewrite duplicate, vague, or misleading titles. Validation: recrawl and inspect the live tag.
• Meta descriptions. Evidence required: crawl export and page intent review. The source carried 120-155 characters as a writing range. Pass if the description is unique, accurate, and useful to a searcher. Severity: routine. Owner: marketing. Corrective action: rewrite missing or duplicated descriptions. Validation: recrawl.
• Heading hierarchy. Evidence required: rendered heading outline. The source's H1 convention was one H1 per page, followed by H2 and H3 sections where the content hierarchy calls for them. Pass if headings follow information structure rather than styling needs. Severity: routine. Owner: content or developer. Corrective action: correct heading levels. Validation: inspect the page outline again.
• Opening relevance. Evidence required: the first 100 words and target-query map. Pass if the introduction clearly states the accounting service or topic without keyword stuffing. Severity: high. Owner: content lead. Corrective action: rewrite the opening for clarity and intent. Validation: compare copy against the page purpose and actual service scope.
• Natural keyword use. Evidence required: page copy and query map. The source referenced H1 placement and 1-2 body mentions as an editing convention. Treat that as prior editorial guidance, not a density requirement. Pass if terminology appears naturally where it helps understanding. Severity: routine. Owner: content lead. Corrective action: remove forced repetition or add missing service language where genuinely useful. Validation: human editorial review.
• Internal linking. Evidence required: crawl graph and rendered links. The source used 2-4 internal links per page as a working minimum. Pass when important pages are connected through relevant, descriptive links that help users move between related services and resources. Severity: high. Owner: content lead. Corrective action: add or repair contextually useful internal links. Validation: recrawl and click-test.
• Structured data. Evidence required: page source and validation output. Use only schema types that accurately describe visible content. Do not present FAQPage markup as a route to a Google FAQ rich result. Pass if markup is syntactically valid, truthful, and consistent with the page. Severity: routine. Owner: developer or technical SEO owner. Corrective action: remove unsupported properties and correct invalid markup. Validation: run the appropriate validator.

The source estimated 8-12 hours for a 20-page site and suggested beginning with the top 10 pages. Keep those figures as prior planning assumptions, not fixed production requirements. Prioritize pages by business importance, existing visibility, and dependency.

Scope: use this section only for genuine office locations and accurate service-area information. Do not create thin city pages simply because a market is desirable.

• Google Business Profile accuracy. Evidence required: live profile compared with current firm records. Pass if name, address, phone, hours, categories, website destination, and other core facts are accurate. Severity: critical for affected locations. Owner: practice administrator. Corrective action: correct factual fields and resolve ownership problems. Validation: compare the live profile with internal records.
• Profile imagery and updates. The source referenced 10+ photos and ongoing posts. Treat those as prior operating practices, not guaranteed ranking factors. Evidence required: current profile assets. Pass if photos are accurate, current, and useful to prospects. Severity: routine. Owner: local-search owner. Corrective action: replace misleading or outdated assets. Validation: manual profile review.
• Reviews. The source referenced 15+ reviews and response within 48 hours. Those are historical operational targets, not official ranking thresholds. Evidence required: review record and response process. Pass if eligible clients are asked consistently for honest feedback without incentives or review gating, and responses are handled according to firm policy. Severity: high. Owner: office manager or compliance-approved reviewer. Corrective action: establish a neutral request and response process. Validation: audit the process and sample recent interactions.
• Citation accuracy. Evidence required: major directory listings compared with the firm's official name, address, and phone. Pass if material discrepancies are corrected. Severity: high. Owner: local-search owner. Corrective action: update inaccurate listings. Validation: recheck live records after propagation.
• Location pages. Evidence required: proof of a genuine office plus unique, useful location-specific information. Pass if a dedicated page exists only where the location is real and the page helps prospects understand services, contact details, access, and local context. Severity: high where applicable. Owner: marketing with firm review. Corrective action: build or improve the page; do not publish doorway-style market pages. Validation: compare page content with the actual office.
• Local authority. Evidence required: relevant local or professional references. Pass if links or mentions are legitimate, editorially earned or appropriately listed, and relevant to the practice. Severity: routine. Owner: marketing or communications. Corrective action: pursue genuine community and professional opportunities rather than low-quality link schemes. Validation: manually review each acquired source.

The source estimated 4-6 hours for setup and 2-3 hours per month for ongoing work. Use those as prior planning assumptions only; workload varies by location count, review volume, citation problems, and approval requirements.

Objective: make the site useful for the accounting services and client questions the firm is actually qualified to address. Build depth where it helps a prospect decide whether the firm is a fit.

• Cornerstone service pages. Evidence required: inventory of the firm's 8-12 most important service pages, mapped to actual offerings and search intent. The source used 1,500+ words and a historical 70% ranking claim; the claim lacks a supporting source URL here, so treat it as source-carried context requiring reconciliation. Pass if each priority page is complete enough to explain scope, fit, process, limitations, and next steps without padding. Severity: high. Owner: marketing with CPA or subject-matter review. Corrective action: consolidate thin duplicates or deepen genuinely important pages. Validation: editorial and service-scope review.
• Industry-specific pages. Evidence required: proof that the firm actually serves the named industry and can provide distinct guidance. A prior example referenced real estate topics including 1031 exchanges. Pass if the page reflects real expertise and client needs rather than substituting industry labels into generic copy. Severity: high where the vertical is strategically important. Owner: content lead with subject-matter review. Corrective action: rewrite for actual industry issues or remove unsupported positioning. Validation: practitioner review.
• Guides and question-led resources. The source used 2,000+ words as a historical editorial benchmark. Pass if the resource answers the question completely and links naturally to relevant services. Severity: routine to high depending on intent. Owner: content lead. Corrective action: expand missing decision information or consolidate repetitive resources. Validation: compare against the intended query and user task.
• Editorial planning. The source referenced 2-4 posts per month. Treat cadence as an operating choice, not an official ranking factor. Pass if the firm publishes only when it has useful, accurate material and can maintain review quality. Severity: routine. Owner: marketing. Corrective action: replace quota-driven publishing with a prioritized topic queue. Validation: review usefulness, accuracy, and internal linking.
• Compliance review. Evidence required: documented review of testimonials, case studies, tax-related claims, and promotional language. The source references AICPA Section 1.600 and an unsourced example claim of save 30% on taxes. Do not treat that example as acceptable or verified. Pass if claims are accurate, supportable, and reviewed under applicable professional and advertising requirements. Severity: critical for risky claims. Owner: firm leadership or designated compliance reviewer. Corrective action: remove or qualify unsupported statements. Validation: final compliance review before publication.

The source estimated 20-30 hours for initial content setup and 8-12 hours per month thereafter. Use those figures as prior planning context only; actual effort depends on how much subject-matter review, rewriting, and consolidation the site requires.

Goal: verify that the firm is represented accurately by credible third parties and that professional expertise is clear on the site. Do not use authority metrics as substitutes for source quality.

• Review process. The source referenced response within 48 hours. Treat that as a prior service standard, not an official ranking factor. Evidence required: current review workflow. Pass if all eligible clients are treated consistently, honest feedback is welcomed without incentives or gating, and responses follow the firm's privacy and compliance rules. Severity: high. Owner: office manager or designated reviewer. Corrective action: standardize the process. Validation: sample recent requests and responses.
• Professional credentials. Evidence required: current licenses, memberships, and other credentials shown on the site. Pass if every displayed credential is accurate, current, and relevant. Severity: high. Owner: firm administrator. Corrective action: remove stale or ambiguous credentials and update verified information. Validation: compare against current firm records and relevant issuing bodies.
• Team biographies. Evidence required: practitioner bios and approved professional information. Pass if bios accurately identify role, qualifications, experience, and areas of practice without unsupported superlatives. Severity: high. Owner: marketing with practitioner review. Corrective action: complete or correct bios. Validation: practitioner sign-off.
• Third-party mentions. Evidence required: live references from relevant publications, associations, directories, or community organizations. Pass if the source is legitimate and the reference is accurate. Severity: routine. Owner: communications or marketing. Corrective action: pursue appropriate editorial and professional opportunities. Validation: manual source review.
• Earned links. Evidence required: backlink review showing context and destination. Pass if links are relevant and editorially defensible rather than purchased, spun, or unrelated. Severity: high when risky links dominate the profile. Owner: SEO or communications lead. Corrective action: stop manipulative acquisition and focus on useful resources, professional participation, and legitimate citations. Validation: review new referring sources.

The source estimated 4-6 hours for setup and 3-5 hours per month for monitoring and relationship work. Use those numbers only as prior planning context; actual effort varies with firm size and opportunity volume.

Use quick wins only after blockers are understood. The source labeled some tasks as taking 1-3 hours and producing immediate improvements. Treat that timing and outcome language as prior operating context, not a guarantee.

• Search-platform coverage. Evidence required: current sitemap and verified webmaster-tool properties. Pass if the XML sitemap is submitted where the firm actively monitors search performance and the submitted URLs are the intended canonical pages. Severity: routine. Owner: technical SEO owner. Corrective action: correct submission or sitemap contents. Validation: inspect status after processing.
• Structured data hygiene. Evidence required: page source and validator output. Pass if markup reflects visible content and is free of material errors. Do not present FAQPage markup as a guaranteed route to a rich result. Severity: routine. Owner: developer. Corrective action: remove unsupported or misleading properties. Validation: rerun the validator.
• Image accessibility. Evidence required: representative service and team images. Pass if meaningful images use descriptive alt text and decorative images are handled appropriately. Do not stuff keywords or use filename-like text such as image1.jpg as a substitute for a description. Severity: routine. Owner: content or developer. Corrective action: revise alt text where it helps accessibility. Validation: inspect the rendered page and source.
• Analytics configuration. Evidence required: Google Analytics 4 property and Search Console connection where the firm uses them. Pass if the configuration captures agreed page and inquiry events consistently enough for decision-making. Severity: high. Owner: analytics or marketing lead. Corrective action: repair missing or duplicate tracking. Validation: test live events and reporting.
• Migration redirects. Evidence required: old-to-new URL mapping and crawl results. If the firm migrated, verify permanent 301 redirects from retired URLs to the closest relevant destinations. Pass if priority legacy URLs resolve correctly without chains. Severity: critical after a migration. Owner: developer. Corrective action: repair redirects and internal links. Validation: recrawl legacy URL samples.
• Breadcrumb implementation. Evidence required: rendered breadcrumbs and source markup. Pass if breadcrumbs help users understand hierarchy and any structured data matches visible navigation. Severity: routine. Owner: developer. Corrective action: align visible and structured breadcrumb data. Validation: manual review plus validator.

Ongoing review: the source referenced 2-3 hours per month, publication of 1-2 new pieces, and review of the top 10 pages. Keep those figures as historical operating assumptions, not required cadences or guaranteed thresholds. Use Search Console, crawl data, inquiry quality, and content accuracy to decide what actually needs attention.

Quarterly interpretation: the source referenced pages ranking #3-#10 and a push into the top 3. Treat those positions as examples from the prior edition, not promises. Revisit pages when query relevance, search appearance, or user behavior shows a clear opportunity, then validate whether the change improved the intended signal.