Secure transport and form handling
Evidence required: browser security status, certificate configuration, form destinations, and a record of what information each public form collects. Pass condition: public pages load over HTTPS without mixed-content warnings, contact forms submit to the intended controlled destination, and unnecessary sensitive-data requests are removed.
Fail condition: insecure resources, broken certificate behavior, unexplained form routing, or collection that the firm cannot justify. Severity: critical when confidentiality, form delivery, or user trust is affected.
Owner: web engineering with firm operations. Corrective action: repair transport, form routing, and data-minimization issues. Validation: retest representative pages and submissions on desktop and mobile.
Crawl and index controls
Evidence required: robots directives, XML sitemap output, canonical tags, redirect behavior, and Search Console coverage data. Pass condition: pages the firm intends search engines to discover are crawlable and internally reachable, while duplicate or nonpublic utility URLs are controlled intentionally.
Fail condition: important pages are blocked, duplicate URLs compete without a clear canonical choice, or stale URLs remain discoverable without purpose. Severity: high. Owner: technical SEO and engineering.
Corrective action: align crawl, canonical, redirect, and sitemap rules with the current information architecture. Validation: recrawl the site and confirm the intended URLs are discoverable without relying on assumptions about ranking.
Broken-page and internal-link integrity
Evidence required: a site crawl, server logs where available, and a list of internal links resolving to error responses. Pass condition: navigation and contextual links resolve to live, relevant destinations, and any intentional 404 response is appropriate for a removed resource.
Fail condition: important client paths terminate at errors, loops, or irrelevant redirects. Severity: high for intake and core practice pages, medium for peripheral resources. Owner: content operations and engineering.
Corrective action: repair destinations, update links, or retire obsolete references. Validation: rerun the crawl and manually test high-intent paths from entry page to contact action.
Mobile rendering and interaction quality
Evidence required: device testing, performance diagnostics, layout checks, and recordings or screenshots of key pages. Pass condition: content remains readable, controls are usable, phone and form actions work, and important legal context is not hidden behind intrusive overlays.
Fail condition: clipped text, blocked controls, unstable layouts, or interaction failures. Severity: high. Owner: design and engineering. Corrective action: simplify responsive layouts, reduce blocking assets, and fix touch targets or overlays. Validation: repeat tests on representative mobile devices and network conditions.
Structured data accuracy
Evidence required: rendered JSON-LD, validation output, and a comparison between markup and visible page content. Pass condition: structured data describes the real firm, attorneys, services, and locations shown to users and contains no invented credentials, ratings, or service details.
Fail condition: markup contradicts the page, identifies the wrong entity, or includes unsupported properties. Severity: medium to high depending on the inaccurate claim. Owner: technical SEO with attorney or compliance review for legal facts.
Corrective action: remove unsupported properties and align markup with visible, reviewed content. Validation: rerun schema validation and manually compare each material property with the page.