Project image delivery
Evidence required: a crawl export, page templates, representative project galleries, and performance reports for important paving service pages. Pass condition: project images are appropriately sized, compressed, served in efficient formats where supported, and do not create avoidable layout or loading problems.
Fail condition: oversized originals, duplicated assets, or gallery behavior materially delays useful page rendering. Severity: high when affected pages are core lead or service pages. Owner: developer or site administrator.
Corrective action: resize source files, compress them, use efficient delivery formats, and remove unnecessary duplicate assets. Validation: rerun the same performance test and visually inspect the gallery on mobile and desktop.
Business and service structured data
Evidence required: rendered page content, deployed JSON-LD, and a structured data validation result. Pass condition: markup describes information that is also visible and accurate on the page, such as the business identity and genuinely offered paving services.
Fail condition: markup is missing where the implementation requires it, conflicts with visible content, or invents unsupported attributes. Severity: medium unless invalid markup is blocking a broader release.
Owner: SEO lead with developer support. Corrective action: align the markup with the real business information and remove unsupported properties. Validation: test the deployed page and compare the parsed values with the visible business details.
Structured data can help search engines understand page entities, but it is not a guaranteed ranking or rich-result mechanism.
Mobile usability
Evidence required: mobile screenshots, interaction testing, field or lab performance data, and a working quote or contact path. Pass condition: a user can understand the service, inspect proof, navigate, call, or submit an inquiry without blocked controls or unreadable content.
Fail condition: menus, forms, tap targets, project galleries, or text create material friction on common mobile viewports. Severity: critical when the defect blocks contact. Owner: developer and conversion owner.
Corrective action: fix responsive layout, navigation, forms, and heavy media. Validation: repeat the same task flow on representative mobile devices and confirm successful completion.
Service-area presentation
Evidence required: Google Business Profile settings, on-site service-area language, business contact details, and any embedded map implementation already used on the site. Pass condition: the website and profile describe the contractor's real operating area consistently without implying staffed locations that do not exist.
Fail condition: conflicting geography, unsupported location claims, or a map that suggests a false office location. Severity: high for materially inaccurate local information. Owner: local SEO manager or business owner.
Corrective action: reconcile the public business information and service-area wording. Validation: compare the live site and profile after publication. A map embed may help users orient themselves, but an embed is not an official ranking requirement.
HTTPS and security baseline
Evidence required: browser security status, certificate details, redirect behavior, crawl results, and form submission tests. Pass condition: important site URLs load securely, insecure duplicates redirect correctly, and contact paths do not expose obvious mixed-content problems.
Fail condition: certificate errors, mixed-content failures, or inconsistent secure canonical access remain on important pages. Severity: critical when users or crawlers cannot reliably access the site.
Owner: developer or hosting administrator. Corrective action: repair certificate, redirect, and mixed-content issues. Validation: crawl the secure site, test representative URLs, and submit a test inquiry through the live form.