Check crawlability and indexability
Evidence required: Search Console coverage data, a representative crawl, robots directives, canonical targets, and rendered page checks for the main service templates.
Pass condition: Important installation, renovation, repair, maintenance, and genuine location pages are crawlable, return the intended status, resolve to the correct canonical target, and can be rendered with their primary content.
Fail condition: Important pages are blocked, duplicated unintentionally, canonicalized to the wrong destination, orphaned, or dependent on rendering that does not expose essential content. Severity: Critical when discovery is blocked; otherwise High.
Owner: Developer or technical SEO owner. Corrective action: Remove accidental crawl barriers, repair canonical and redirect logic, restore broken internal paths, and keep low-value utility pages out of primary navigation where appropriate.
Validation: Re-crawl the affected templates and confirm the intended pages are discoverable and represented correctly in Search Console.
Check mobile performance and page stability
Evidence required: Field or lab performance data for representative gallery, service, and location templates plus image payload review. Pass condition: The pages are usable on common mobile connections, large images are delivered at sensible dimensions, and layout movement does not interfere with reading or contact actions.
Fail condition: Oversized media, blocking scripts, unstable layouts, or template defects materially slow or obstruct the page. Severity: High for lead-generating templates; Medium for secondary resources.
Owner: Developer with design support. Corrective action: Resize and compress images, improve responsive delivery, defer nonessential resources, and reserve layout space for media and interface elements. Validation: Re-test the same templates under comparable conditions and confirm the measured issue improved.
Check internal links to core service pages
Evidence required: Crawl exports showing inlinks, navigation paths, anchor context, and orphan-page reports. Pass condition: Every important service page can be reached through relevant site navigation or contextual links, and related content points to the page that best matches the user's service intent.
Fail condition: Core pages are orphaned, linked only from utility areas, or repeatedly pointed to with ambiguous context. Severity: High. Owner: SEO or content lead, implemented by the web owner. Corrective action: Add useful contextual links from related pages, simplify competing destinations, and remove links that send users to a less relevant page.
Validation: Re-crawl the site and confirm each core service page has intentional internal entry points from relevant sections.
Check structured data for accuracy and eligibility
Evidence required: Rendered JSON-LD, visible page content, current business facts, and validation results. Pass condition: Markup accurately reflects visible information and uses supported properties for the page type.
Fail condition: Markup contains unsupported claims, stale contact details, mismatched service information, or properties added only to influence rankings. Severity: Medium unless incorrect business data creates a broader consistency problem.
Owner: Developer, reviewed by SEO and operations. Corrective action: Remove unsupported properties, synchronize facts with the page, and follow current documentation for eligible markup. Validation: Re-run validation and compare the structured data against the visible source of truth.