Check: LegalService structured data and page semantics
Evidence required: representative service-page markup, validation output, visible page content, attorney and organization details, and the current documented requirements used for implementation.
Pass/fail: Pass if the markup accurately reflects visible content and validates for the properties the firm actually uses. Fail if it invents credentials, services, locations, ratings, or other facts, or if the implementation relies on markup alone to claim search visibility.
Severity: Medium unless inaccurate markup creates a material legal or factual misstatement. Owner: Technical SEO owner with attorney or compliance review for legal claims. Corrective action: Remove unsupported properties, align markup with the visible page, and keep Schema.org terminology consistent with the content.
Use Google Rich Results Test only for the features it actually supports. Validation step: Revalidate the rendered page and compare each material property with the public content. Do not treat structured data as a guaranteed ranking or rich-result mechanism.
Check: Core Web Vitals and mobile usability
Evidence required: Google PageSpeed Insights, Search Console field data where available, device testing, and a list of templates affecting key wills, trusts, probate, attorney, and contact pages.
Pass/fail: Pass if critical pages are usable on mobile and material performance issues have an owner and remediation plan. Fail if layout movement, blocking scripts, slow interactions, or broken mobile controls materially impede users.
Severity: High when usability or intake paths are impaired; otherwise Medium. Owner: Web development owner. Corrective action: Fix the root cause at the template or component level before applying page-by-page patches. Validation step: Retest representative templates and confirm that corrections persist after deployment.
Check: Security and contact-form data handling
Evidence required: SSL configuration, privacy disclosures, form fields, data destinations, access controls, retention practices, and the legal or regulatory basis the firm actually relies on.
HIPAA-compliant form providers should be evaluated only if HIPAA is genuinely applicable to the firm's handling of protected information. Pass/fail: Pass if transmission is secure, data collection is proportionate, access is controlled, and applicable privacy or professional obligations have been reviewed.
Fail if sensitive information is collected without a documented handling process. Severity: Critical for material security or confidentiality exposure. Owner: IT or security owner with responsible legal review.
Corrective action: Minimize requested data, secure transmission and storage, restrict access, and update notices or workflows as required. Validation step: Test submission, storage, access, and deletion workflows rather than assuming an SSL Certificate alone resolves the issue.
Check: Practice-area hierarchy and crawl paths
Evidence required: crawl export, navigation map, indexable URL list, orphan-page report, and the firm's actual service taxonomy. Pass/fail: Pass if users and crawlers can reach important estate planning pages through descriptive navigation and internal links.
Fail if key pages are orphaned, duplicated, buried, or mapped to services the firm does not actually offer. Severity: High for inaccessible core service pages; otherwise Medium. Owner: SEO and web architecture owners.
Corrective action: Simplify hierarchy around real services, consolidate duplicates, and repair broken or misleading paths. Screaming Frog and Lucidchart can support the audit, but the pass condition comes from the site's actual architecture. Validation step: Re-crawl after deployment and manually test representative user paths.