Checklist item: Match structured data to visible business facts
Evidence required: The rendered page, deployed JSON-LD or other structured data, the selected Schema.org type, and the business records supporting each property.
Pass/fail condition: Pass when FinancialService, ProfessionalService, or another supported type accurately describes the visible entity and every material property agrees with on-page information. Fail when markup adds credentials, ratings, locations, services, or other facts that the user cannot verify on the page or through the business record.
Severity: Medium
Owner: Technical SEO owner with business-data review. Corrective action: Remove unsupported properties, align markup with visible facts, and use the most accurate supported type instead of stacking types to imply extra relevance.
Validation step: Parse the deployed markup, compare values with the page and source-of-truth records, and use structured-data testing tools for syntax or eligibility diagnostics without assuming enhanced presentation in search.
Checklist item: Verify secure delivery for public pages and lead forms
Evidence required: A production crawl, certificate checks, form-action destinations, mixed-content findings, and the approved data-handling architecture.
Pass/fail condition: Pass when the intended public site and tested form path use 100% HTTPS coverage and no required page exposes insecure active content or an insecure submission endpoint. Fail when a required page, asset, or form destination falls back to an insecure connection.
Severity: Critical
Owner: Web engineering and security owner. Corrective action: Fix certificate, redirect, mixed-content, and endpoint defects, and separately review whether the marketing site should collect any sensitive taxpayer information.
Validation step: Re-crawl production, submit non-sensitive test data through the intended form path, and confirm the final transport behavior with the responsible security reviewer.
Checklist item: Diagnose performance from field and functional evidence
Evidence required: Core Web Vitals data when available, laboratory tests, representative device checks, and a comparison of important service, article, and contact templates.
Pass/fail condition: Pass when no confirmed performance issue materially prevents reading, navigation, or intended form use, and each material defect has an assigned owner. Fail when slow loading, unstable layout, or delayed interaction obstructs a key user task.
Severity: Medium
Owner: Web performance or engineering owner. Corrective action: Address the confirmed bottleneck, such as oversized media, render-blocking scripts, unstable components, or inefficient templates, rather than chasing a score without diagnosing the cause.
Validation step: Repeat the same test on the corrected template and compare like-for-like evidence from representative devices.
Checklist item: Confirm a crawlable service-page hierarchy
Evidence required: A site crawl, navigation map, canonical tags, internal-link graph, and the approved inventory of tax service pages. Pass/fail condition: Pass when important service pages are reachable through logical navigation or relevant content paths and duplicate or competing URLs are intentionally controlled.
Fail when a service page is orphaned, hidden behind fragile scripting, duplicated without purpose, or mapped ambiguously to the same search task. Severity: High
Owner: SEO information-architecture owner with web implementation support.
Corrective action: Simplify page relationships, consolidate duplicates where appropriate, correct canonicals, and rebuild internal links around the client decision path. Validation step: Re-crawl after deployment and confirm the intended pages are reachable, indexable as planned, canonically consistent, and returning the expected status.
Checklist item: Align sitemap and robots controls with publishing intent
Evidence required: The live XML sitemap, robots.txt, page-level robots directives, canonical tags, and Google Search Console observations for representative URLs.
Pass/fail condition: Pass when the sitemap lists intended canonical pages, disallowed paths are intentional, and robots directives do not contradict the approved indexation plan. Fail when valuable pages are blocked, non-canonical variants are promoted, or utility and private URLs are unnecessarily submitted.
Severity: High
Owner: Technical SEO owner. Corrective action: Reconcile sitemap membership, robots rules, canonicalization, and index directives with the approved page inventory. Validation step: Fetch the deployed files, inspect representative URLs, and confirm that observed indexing signals move toward the intended state without promising a particular indexing timetable.