Check: Crawl and index access for important divorce and family law pages
Evidence required: A current crawl, representative URL inspections, sitemap status, robots directives, canonical signals, and index coverage for the pages the firm expects searchers to find.
Pass/fail condition: Pass when important pages are reachable, indexable where intended, internally linked, and not blocked or canonicalized away by mistake. Fail when a technical directive or navigation defect prevents access to a page that should be discoverable.
Severity: Critical when a revenue-relevant section is broadly blocked; otherwise prioritize by affected page type and scope. Owner: SEO lead for requirements, developer for implementation. Corrective action: Remove unintended blocks, repair canonical or redirect logic, restore discoverable navigation, and resubmit only where appropriate.
Validation step: Re-crawl the affected templates and inspect representative URLs after deployment. Do not infer success only from a later ranking change.
Check: Structured data matches visible, accurate page information
Evidence required: The live JSON-LD, the visible attorney or organization information it describes, and validation output from Schema.org tooling or Google-supported testing where applicable.
Pass/fail condition: Pass when markup is syntactically valid, corresponds to visible content, and uses properties that truthfully describe the firm or attorney. Fail when markup invents credentials, services, locations, ratings, or relationships that the page does not support.
Severity: High when the markup misrepresents legal credentials or business identity; medium for non-material syntax defects. Owner: SEO lead and developer, with attorney review for professional credentials.
Corrective action: Remove unsupported fields, align entity details with the visible page, and use only schema types and properties that accurately represent the content. Structured data can help systems understand page information but should not be presented as a guaranteed ranking factor or rich-result trigger.
Validation step: Retest the rendered markup and manually compare each material field with the page and approved firm records.
Check: Mobile performance and interaction quality
Evidence required: Field or lab performance data where available, real-device testing, layout checks, and a manual walkthrough of navigation, forms, and click-to-call behavior.
Pass/fail condition: Pass when important templates load and remain usable on common mobile devices, controls are reachable, content is readable, and the contact path works. Fail when loading, layout movement, blocked resources, or interaction defects materially interfere with research or contact.
Severity: High on service and contact templates; otherwise based on user impact. Owner: Developer and design owner, with SEO input on crawl and rendering requirements. Corrective action: Reduce unnecessary payloads, size media appropriately, remove blocking defects, simplify interactions, and fix template-level problems before polishing isolated pages.
Validation step: Retest the same devices and templates after release and compare the evidence captured before the change.
Check: Broken links and error responses
Evidence required: A crawl report, analytics or server data where available, and a manual review of important internal navigation paths. Pass/fail condition: Pass when internal links resolve to the intended destination and intentionally removed pages have an appropriate handling strategy.
Fail when navigation or editorial links lead users or crawlers to unintended 404 responses. Severity: High for broken links in primary navigation, service pages, or contact flows; lower for isolated legacy references.
Owner: Content owner for editorial destinations, developer for routing defects. Corrective action: Update links to the correct existing destination, restore a page only when it should still exist, or use an appropriate redirect when a true replacement exists. Validation step: Re-crawl and manually test the corrected paths.
Check: HTTPS and inquiry-path security configuration
Evidence required: Browser checks, certificate status, mixed-content review, form transport inspection, and hosting configuration records. Pass/fail condition: Pass when public pages load over HTTPS without certificate warnings and inquiry forms transmit over the intended secure connection.
Fail when users encounter security warnings, mixed-content errors that break functionality, or insecure form submission paths. Severity: Critical for inquiry or authentication flows; high for sitewide certificate problems.
Owner: Developer or hosting administrator. Corrective action: Correct certificate, redirect, mixed-content, or form transport configuration and confirm that the fix does not create redirect loops or inaccessible assets. Validation step: Test representative pages and inquiry flows in a clean browser session after deployment.