Start with conditions that determine whether search systems and customers can reach, understand, and use the site.
Crawl and index access
Evidence required: current robots directives, sitemap status, canonical signals, status codes for priority service pages, and Search Console coverage for pages the company expects to appear in search.
Pass condition: important remediation and location pages intended for search are accessible, return the expected status, use consistent canonical targets, and are not accidentally blocked. Severity: Critical when a revenue-relevant page cannot be crawled or indexed; otherwise High for broad architecture problems.
Owner: Web developer or technical SEO owner. Corrective action: remove accidental blocks, repair broken status behavior, consolidate conflicting canonicals, and update the sitemap to reflect the actual indexable site.
Validation step: recrawl the affected templates and confirm the live response, canonical, internal links, and indexability before requesting any further search processing.
Structured data accuracy
Evidence required: the markup already present on service and business pages, plus the visible business facts those fields describe. Pass condition: structured data matches visible, supportable facts and does not claim services, certifications, locations, ratings, or relationships the business cannot verify.
Severity: High when markup materially contradicts the page; Medium when optional descriptive fields are incomplete. Owner: Web developer with business or compliance review. Corrective action: remove unsupported fields, align remaining markup with visible content, and use the Google Rich Results Test only for syntax or eligibility checks where applicable, not as proof of ranking impact.
Validation step: test the published markup and manually compare each business claim against the page and current source records.
Core mobile usability
Evidence required: mobile testing on priority pages, PageSpeed Insights or equivalent diagnostics, and direct observation of contact, navigation, and form behavior. Pass condition: a visitor can identify the service, understand the service area, and contact the company without obstructive layout or avoidable delay.
A historical 5-second load observation should be treated as a diagnostic data point, not a universal conversion threshold. Severity: High for broken contact paths or unusable mobile layouts; Medium for performance issues that do not block completion.
Owner: Web developer and conversion owner. Corrective action: reduce unnecessary script and image weight, fix layout instability, simplify urgent contact paths, and preserve essential content. Validation step: retest on real mobile devices and slower connections, then compare diagnostics with the observed customer journey.
Site hierarchy and internal navigation
Evidence required: crawl data, menu structure, breadcrumbs if used, internal links, and the set of active remediation services. Pass condition: every important service can be reached through a logical path, related informational pages link to relevant services naturally, and no orphaned priority page depends on search engines alone for discovery.
Severity: High for orphaned or unreachable service pages; Medium for confusing hierarchy. Owner: SEO or information architecture owner with operations review. Corrective action: group content around real service categories, remove duplicate pathways, and add contextual internal links where they help a reader move to the next decision.
Validation step: crawl the site again and trace each priority service from the main navigation or a clearly related hub.