Use this section to verify whether search systems and users can reliably reach, load, and understand the site.
Search monitoring setup
Evidence required: verified access to the firm's search performance and indexing tools, plus a documented owner. Pass condition: the firm can review indexing status, crawl issues, search queries, and affected pages from an authorized account.
Fail condition: no verified property exists, access belongs only to a former vendor, or the team cannot trace an alert to a page. Severity: high when the gap prevents diagnosis. Owner: marketing operations or the person responsible for web measurement.
Corrective action: verify the correct site properties, document access, and connect the records to the firm's reporting process. Validation: confirm that current pages and indexing information are visible to the responsible team.
Secure connection and transport settings
Evidence required: a valid secure connection, consistent secure URLs, and a review of redirect and security-header behavior. Pass condition: visitors reach the intended secure version without mixed-content or redirect problems.
Fail condition: certificate errors, insecure assets, redirect loops, or inconsistent secure and insecure versions are present. Severity: critical when users cannot safely access forms or content. Owner: web development or infrastructure.
Corrective action: repair certificate, redirect, or configuration issues and retest affected templates. Validation: crawl representative pages and complete the same checks from a browser and technical test.
Structured data accuracy
Evidence required: the structured data currently published, the visible page content it describes, and validation output. Pass condition: markup describes the actual firm, location, service, or person shown on the page and contains no unsupported claims.
Fail condition: markup conflicts with visible content, identifies the wrong entity, or is added only in an attempt to force a search feature. Severity: medium unless the markup contains materially misleading information.
Owner: SEO lead with development review. Corrective action: simplify or correct the markup so it mirrors the page. Validation: run a structured-data validation check and compare the output with the live page. Do not treat valid markup as a ranking guarantee.
Page experience and performance
Evidence required: field or lab performance evidence for representative service, article, location, and contact templates. Pass condition: pages are usable on common devices, important content appears without disruptive failures, and no major performance issue blocks the user journey.
Fail condition: slow rendering, layout instability, unusable controls, or heavy scripts materially interfere with access or conversion. Severity: high on lead-generating templates. Owner: development.
Corrective action: address the largest user-facing bottlenecks first, then retest the affected template. Validation: compare before and after measurements and verify the real page journey. The source version used a Largest Contentful Paint target under 2.5 seconds; treat that value as a technical checkpoint, not a guarantee of search performance.
URL structure and canonical consistency
Evidence required: a crawl of indexable URLs, canonical tags, redirects, and internal links. Pass condition: important service and location pages have stable descriptive URLs, self-consistent canonicalization, and no avoidable duplicate paths.
Fail condition: parameter duplicates, redirect chains, conflicting canonicals, or multiple URLs serving substantially the same intended page are found. Severity: medium to high depending on scale. Owner: SEO lead and development.
Corrective action: define the preferred URL, update internal links, and redirect or consolidate duplicate paths where appropriate. Validation: recrawl and confirm that indexable and canonical URLs match the intended information architecture.