Technical checks should follow the customer paths that matter most: finding a location, reading the menu, understanding membership options, and completing the next step. A tool score alone is not enough evidence.
Checkpoint: Verify crawl access, index intent, responses, and canonical signals. Evidence required: Live response codes, crawl directives, index directives, canonical tags, and rendered output for the homepage, genuine location pages, service pages, and membership page.
Pass/Fail condition: Pass when intended public pages return the expected successful response, are available for crawling and indexing, and identify the intended canonical page. Fail when important pages are blocked, redirected incorrectly, duplicated under competing indexable addresses, or assigned to an unrelated canonical.
Severity: Critical. Owner: Developer or technical SEO owner. Corrective action: Repair access rules, response handling, redirect chains, and canonical conflicts while keeping private account and checkout areas appropriately protected.
Validation step: Re-crawl the corrected pages, inspect the rendered HTML, and confirm the live response, directives, and canonical destination.
Checkpoint: Make CarWash structured data agree with visible facts. Evidence required: The JSON-LD, the visible business name, address, opening hours, price range, and membership information referenced by the markup.
Pass/Fail condition: Pass when the markup parses and every property is supported by content visible on the same page or clearly associated with it. Fail when markup contains hidden offers, stale prices, another location's details, unsupported availability, or syntax errors.
Severity: High. Owner: Developer with content and operations review. Corrective action: Remove unsupported properties, align the remaining values with approved public information, and avoid treating structured data as a guarantee of rankings or enhanced display.
Validation step: Run the live page through Schema.org guidance and Google Rich Results Test, then compare the parsed values with the rendered page.
Checkpoint: Test mobile performance on the real decision path. Evidence required: Mobile measurements for the location, wash-menu, and membership pages, plus a manual task test on a representative device and connection.
Pass/Fail condition: For this checklist, fail the task when key content or controls remain unusable beyond 3 seconds, the page shifts enough to cause errors, or a customer cannot reach directions, prices, or sign-up reliably.
Treat that threshold as an internal triage rule, not an official ranking cutoff. Severity: High. Owner: Front-end developer with the website owner. Corrective action: Reduce oversized media, defer nonessential scripts, stabilize layout, and repair third-party widgets that block the main task.
Validation step: Retest the same pages and actions with PageSpeed Insights and GTmetrix, then repeat the manual journey and preserve before-and-after evidence.
Checkpoint: Eliminate broken membership links and unsafe redirect paths. Evidence required: A crawl of internal links, redirect chains, final destinations, and manual tests from navigation, location pages, package cards, and calls to action.
Pass/Fail condition: Pass when every relevant link reaches the intended live destination for the correct location without a loop, error, or unexpected branch change. Fail when a link is broken, a redirect chain obscures the destination, or a membership action lands on the wrong offer.
Severity: Critical. Owner: Website owner with developer support. Corrective action: Update the source link, simplify redirects, and align destination ownership with the current membership flow. Validation step: Re-crawl with Screaming Frog or Ahrefs and manually complete each corrected path through the final pre-payment step.