Use this section to verify whether search engines and users can reach the pages that matter and whether the site architecture reflects the way the installer actually sells and delivers services.
Crawl access and indexation
Evidence required: Search Console coverage data, robots directives, canonical tags, sitemap entries, and a crawl of the main service, product, project, and genuine location pages.
Pass condition: Important pages are crawlable, return the intended status, use self-consistent canonical signals, and are discoverable through internal links or the sitemap where appropriate. Fail condition: Important pages are blocked, orphaned, duplicated unintentionally, canonicalized elsewhere without reason, or omitted from discoverable navigation.
Severity: critical when commercially important pages cannot be crawled or indexed; high when duplication or orphaning creates ambiguity. Owner: developer or technical SEO owner. Corrective action: remove unintended blocks, repair canonical logic, restore internal links, and update sitemap coverage where necessary.
Validation: recrawl the affected templates and inspect Search Console after deployment to confirm the intended state is being seen.
Broken URLs and internal links
Evidence required: a site crawl, Search Console error reports, and manual checks of navigation, service links, project links, and calls to action. Pass condition: important internal links resolve to live, relevant destinations without avoidable redirect chains.
Fail condition: users or crawlers encounter 404 responses, broken navigation, or links that point to outdated destinations. Severity: high when a broken path interrupts a lead journey or isolates an important page; medium for isolated editorial defects.
Owner: developer for template issues and content owner for editorial links. Corrective action: update the source link, restore a genuinely needed page, or redirect only when a relevant replacement exists. Validation: rerun the crawl and manually test representative user journeys from landing page to inquiry.
Mobile usability and page delivery
Evidence required: mobile testing on representative templates, performance diagnostics, real-user data where available, and direct inspection of galleries, forms, menus, and calls to action.
Pass condition: core content, navigation, project media, and inquiry paths remain usable on common mobile devices and do not depend on unnecessarily heavy assets. Fail condition: content shifts, controls are hard to use, images block meaningful content, forms malfunction, or critical text and links are delayed by avoidable front-end work.
Severity: high when usability blocks contact or core content; medium when the issue degrades browsing without breaking it. Owner: developer with design or content support as needed. Corrective action: optimize media delivery, reduce unnecessary scripts, repair layout issues, and prioritize critical content.
Validation: retest affected templates on mobile and compare representative real-user signals before and after the change where data is available.
Site architecture for products, materials, and services
Evidence required: current URL inventory, navigation, internal links, sales catalogue, and service-area definitions. Pass condition: pages map to real offerings and distinct homeowner intents, with clear parent-child relationships where those relationships help users understand products or services.
Fail condition: one generic page tries to represent unrelated intents, or many thin pages exist without enough distinct information to justify separate URLs. Severity: high when architecture obscures key services or creates widespread duplication.
Owner: SEO strategist with installer or product specialist review. Corrective action: consolidate overlapping pages, create distinct pages only where there is enough unique value, and improve internal links between related topics.
Validation: verify that each retained page has a clear search and user purpose, receives relevant internal links, and does not compete heavily with a near-duplicate page.
Structured data accuracy
Evidence required: rendered page content, structured data output, validation tools, and the business records that support the marked-up facts. Pass condition: markup accurately represents visible content and uses types appropriate to what the page actually contains.
Fail condition: markup contains claims, ratings, products, locations, or services that are not visible or supportable on the page. Severity: medium, rising when inaccurate markup creates misleading public claims.
Owner: developer or technical SEO owner, with business review for factual claims. Corrective action: remove unsupported properties and align markup with visible, current content. Validation: retest rendered markup and compare it against the live page. Do not treat passing validation as evidence that rankings or enhanced search displays will follow.