Use this section to verify whether search engines and families can access accurate assisted living information without treating technical SEO as a substitute for privacy, accessibility, security, legal, or regulatory review. Each item should end with retained evidence of the final state.
Crawl, index, and canonical alignment
Evidence required: a current crawl, index coverage evidence, rendered page output, canonical tags, robots directives, sitemap entries, and the intended index status for important facility, care, pricing, contact, and resource pages.
Pass/fail condition: Pass when each reviewed page is reachable as intended, has a consistent canonical destination, and does not carry contradictory index directives. Fail when blocked resources, accidental noindex directives, redirect loops, duplicate canonicals, or template defects prevent the intended page from being discovered or interpreted.
Severity: High. Owner: Technical SEO with engineering. Corrective action: repair conflicting directives, broken routes, redirects, canonicals, or sitemap entries and document why the chosen index state matches the page purpose.
Validation step: rerun the crawl and inspect the rendered live response for representative page templates after deployment.
Mobile performance and Core Web Vitals
Evidence required: field and lab performance evidence for major templates, a mobile task walk-through, rendered screenshots, and a record of scripts, images, fonts, or layout shifts that materially obstruct reading or contact actions.
Pass/fail condition: Pass when important pages remain usable on common mobile conditions and their core information and controls are accessible. Fail when performance or rendering defects materially block a family from reading facility information or contacting the community.
Severity: High. Owner: Engineering or web performance lead with technical SEO. Corrective action: reduce avoidable script work, optimize media delivery, stabilize layout, and fix broken or obstructive interactions.
Validation step: repeat the same measurements and mobile tasks after the change and retain before-and-after evidence without presenting the result as a ranking guarantee.
Structured-data factual alignment
Evidence required: rendered structured data, the visible content it describes, current facility records, and syntax validation against the relevant Schema.org vocabulary and Google documentation when applicable.
Pass/fail condition: Pass when markup accurately describes the page and genuine facility facts that can be substantiated. Fail when properties are stale, unsupported, misleading, or presented as if structured data alone guarantees a rich result or search position.
Severity: High. Owner: Technical SEO with engineering and content review. Corrective action: remove unsupported properties, correct entity facts, and use only markup that accurately reflects the page and organization.
Validation step: inspect rendered source after deployment, rerun syntax checks, and compare material properties with the live page and facility records.
Lead-form data handling and security path
Evidence required: every field collected on inquiry, tour, pricing, contact, or care-needs forms; submission routes; storage destinations; access controls; encryption settings; vendor terms; retention practices; and the approvals required by responsible privacy, security, legal, or regulatory reviewers.
Pass/fail condition: Pass when the actual data path is documented and each destination is approved for the information it receives. Fail when sensitive information reaches unknown systems, unnecessary fields are collected, or access and retention are not documented.
Severity: Critical. Owner: Privacy and security leads with intake operations and engineering. Corrective action: minimize fields, remove unapproved destinations, correct access and storage controls, and align the workflow with the reviewed handling model.
Validation step: submit controlled test data, trace every destination and access path, and retain the responsible reviewers' sign-off.
Accessibility evidence against WCAG 2.1
Evidence required: automated scan results, keyboard-only navigation checks, screen-reader spot checks, text alternatives for meaningful media, focus behavior, form labels, error messaging, contrast review, and the accessibility standard or policy actually adopted by the organization.
Pass/fail condition: Pass when the reviewed templates meet the organization's documented acceptance criteria and material barriers found during testing are resolved or formally tracked. Fail when users with visual, motor, hearing, or cognitive access needs encounter unresolved blockers or when the site claims conformance without supporting evidence.
Severity: High. Owner: Accessibility or product lead with engineering and content support. Corrective action: fix identified barriers, correct unsupported conformance language, and route policy or legal questions to the responsible reviewers.
Validation step: repeat the same manual and automated checks on repaired templates and retain the evidence used for acceptance.