Crawl and index controls
Evidence required: Search Console indexing information, current robots directives, canonical tags, redirect behavior, and a crawl export covering the main service and genuine location pages.
Pass: each important public page is crawlable, indexable where intended, resolves cleanly, and points to the preferred canonical destination. Fail: a priority page is blocked, noindexed unintentionally, duplicated, trapped behind a conflicting canonical, or routed through an unnecessary redirect chain.
Severity: critical. Owner: technical SEO or developer. Corrective action: repair the directive, redirect, canonical, duplication, or template rule causing the conflict while preserving accurate business information.
Validation: recrawl the affected URLs and confirm the intended indexing state in Search Console. Tools: Google Search Console, Screaming Frog
Mobile enquiry path and page performance
Evidence required: mobile screenshots, field or lab performance evidence, tap-through tests, and completed form or call-action tests on priority service and contact pages.
Pass: navigation, calls to action, forms, service details, media, and contact controls remain readable and usable on common mobile layouts. Fail: shifting layouts, blocked form controls, hidden service information, delayed actions, oversized media, or tap targets interfere with evaluation or contact.
Severity: high. Owner: developer. Corrective action: remove avoidable front-end weight, fix layout and interaction problems, and repair any broken step in the enquiry path. Validation: rerun PageSpeed Insights and manually complete the main mobile enquiry flow. Tools: Google PageSpeed Insights, Search Console
Structured data consistency
Evidence required: the rendered page, current JSON-LD, and validation output for pages where markup is used. Pass: LocalBusiness or Service markup accurately reflects visible content and does not add unsupported prices, ratings, locations, services, credentials, or other claims.
Fail: markup conflicts with the page, contains stale or unsupported properties, or is maintained mainly because someone expects guaranteed enhanced presentation. Severity: medium. Owner: technical SEO.
Corrective action: remove inaccurate fields and retain only relevant markup that matches the visible page. Validation: test the final markup, then compare every material property with the rendered content. Tools: Schema.org, JSON-LD Generator
Service and location URL structure
Evidence required: crawlable URL inventory, navigation paths, canonical targets, and a verified list of real services, genuine locations, and legitimate service areas.
Pass: each important service uses a stable descriptive URL, while any dedicated location page is backed by a real location or useful service-area information that is meaningfully specific to that area.
Fail: query-string duplicates, near-identical market pages, orphaned services, or nominal location pages create ambiguity without serving a real client decision. Severity: high. Owner: SEO strategist and developer.
Corrective action: consolidate duplicate intent, use descriptive paths, and keep dedicated location pages only where the business can support genuinely useful location-specific content. Validation: crawl the site and confirm unique canonicals, working internal links, and differentiated page purposes. Tools: Screaming Frog
HTTPS and form integrity
Evidence required: browser security checks, certificate status, mixed-content reports, redirect behavior, and successful form-submission tests. Pass: public pages, media, and contact flows load securely without certificate warnings, insecure asset requests, or broken submission steps.
Fail: mixed content, expired certificates, redirect loops, insecure assets, or broken secure forms interrupt access or enquiries. Severity: critical. Owner: developer or hosting administrator. Corrective action: renew certificates when needed, repair HTTPS redirects, replace insecure asset references, and fix affected forms. Validation: retest representative pages, forms, and contact actions after deployment. Tools: SSL Labs