Check: Search engines can crawl and index the fencing pages that matter. Evidence required: Search Console coverage data, a crawl export, robots directives, sitemap entries, and a sample of indexed service pages.
Pass condition: important service and location pages are discoverable and indexable, while intentionally excluded pages are excluded for a documented reason. Severity: critical when revenue pages are blocked or missing.
Owner: developer or technical SEO owner. Corrective action: fix crawl barriers, accidental directives, broken internal paths, or sitemap errors. Validation: recrawl and confirm the affected pages can be requested and indexed.
Check: Structured data accurately describes the visible business and services. Evidence required: the rendered markup, the visible page content it describes, and a validation result. Pass condition: LocalBusiness or Service markup, if used, matches the real fencing company and does not claim unavailable services or fabricated service areas.
Severity: medium unless invalid markup is part of a broader implementation problem. Owner: developer or technical SEO owner. Corrective action: remove unsupported properties and align markup with visible content. Validation: rerun the validator and manually compare the markup with the page.
Check: Project galleries load efficiently on mobile devices. Evidence required: field or lab performance data, image dimensions, file sizes, and loading behavior on representative service pages. Pass condition: galleries remain usable without forcing oversized media to load before the customer can understand the page.
Severity: high when image delivery interferes with navigation or estimate requests. Owner: developer with the marketing owner selecting the images. Corrective action: resize, compress, use efficient formats where appropriate, and lazy-load media that is not needed immediately. Validation: rerun performance tests and check the live page on common mobile conditions.
Check: Security and form handling support customer trust. Evidence required: a valid HTTPS implementation, working forms, and a successful test submission. Pass condition: the customer can browse securely and submit an estimate request without certificate or form errors.
Severity: critical when forms fail or browsers show security warnings, especially for a project that could be valued at 10,000 dollars. Owner: developer or hosting owner. Corrective action: repair certificates, mixed content, or form delivery. Validation: complete a real test from the public page and confirm receipt.