Service structured data matches visible content
Evidence required: the rendered service page, its JSON-LD, and the current business service list. Pass/fail condition: Pass when markup describes information that is visible, accurate, eligible, and consistent with the page.
Fail when markup invents services, locations, ratings, credentials, or other facts. Severity: High. Owner: Technical SEO or developer, with business facts verified by operations. Corrective action: Remove unsupported properties and align structured data with the actual basement waterproofing or foundation repair service described on the page.
Do not treat schema as a guaranteed ranking factor. Validation step: Test syntax, compare the markup with the rendered page, and confirm the business data with the responsible owner.
Mobile pages remain usable under constrained conditions
Evidence required: representative mobile tests, field or lab performance data, and a completed contact-flow test. Pass/fail condition: Pass when important pages and forms remain usable and core content is available without blocking errors.
The source previously used 2.5 seconds on 4G connections as a performance target, but no supporting source URL is present, so treat it as a historical operating target rather than a verified universal threshold.
Severity: High for pages used during urgent waterproofing inquiries. Owner: Developer or performance engineer. Corrective action: Reduce avoidable script and image weight, reserve space for media, and fix form or navigation problems that interrupt mobile use.
Validation step: Retest representative pages on actual mobile devices and repeat the quote or contact action end to end.
Old service URLs do not strand users or crawlers
Evidence required: crawl export, server response codes, internal-link report, and redirect map. Pass/fail condition: Pass when obsolete service URLs have an intentional destination or a justified terminal response.
Fail when important internal links lead to 404 errors or irrelevant destinations. Severity: Medium to High depending on the affected page. Owner: Technical SEO or developer. Corrective action: Update internal links first, then apply appropriate redirects only where a real replacement exists.
Where the broader topic is relevant, use the basement waterproofing resource as the preserved destination from the source. Validation step: Re-crawl the changed URLs and confirm final status codes, canonical targets, and internal links.
HTTPS and security configuration do not interrupt access
Evidence required: browser tests, certificate status, redirect behavior, and hosting or security configuration. Pass/fail condition: Pass when users reach the intended secure URL without certificate warnings or redirect loops.
Severity: Critical when a security warning blocks trust or form completion. Owner: Hosting administrator or developer. Corrective action: Repair certificate, protocol, mixed-content, or redirect issues according to the site's actual hosting configuration. Validation step: Test key landing pages and forms in multiple current browsers and verify the final secure URL.