Use this section to verify that access controls, performance, structured data, transport security, and crawl directives work as intended without turning a legal requirement into an SEO assumption.
Age-verification and access controls
Evidence required: live browser behavior, rendered crawler output, server responses, and the documented reason the control exists. Pass/fail condition: Pass when the required user control functions, public content remains available to search systems as intended, and implementation does not rely on deceptive cloaking; fail when the gate replaces or blocks the primary document, loops, or serves materially inconsistent content.
Severity: Critical when indexable content is inaccessible; otherwise High. Owner: Web engineering with SEO QA and the responsible legal or regulatory reviewer for the access requirement. Corrective action: Rework the implementation so it satisfies the reviewed access requirement while preserving stable URLs, accessible interaction, and crawlable public HTML where appropriate.
Validation step: Re-test representative templates in a browser, a rendered crawler, and Google Search Console, then document the result. Tools: AgeChecker.net, Google Search Console
Core Web Vitals and mobile usability
Evidence required: field or lab performance data, template-level testing, and a sample of real mobile journeys. Pass/fail condition: Pass when major templates meet the team's documented performance targets and remain usable on common mobile devices; fail when slow or unstable rendering materially obstructs reading, navigation, or checkout.
Do not treat bounce rate as a documented ranking signal. Severity: High for purchase or information templates with persistent usability failures; Medium for isolated defects. Owner: Front-end engineering and technical SEO.
Corrective action: Address the measured bottleneck, such as image weight, render-blocking resources, script cost, layout instability, or server latency, rather than optimizing a score in isolation. Validation step: Re-run PageSpeed Insights and Chrome DevTools tests on the same templates after deployment and compare the underlying measurements. Tools: PageSpeed Insights, Chrome DevTools
Product and FAQ structured data
Evidence required: visible page content, the implemented Schema.org properties, eligibility documentation, and validation output. Pass/fail condition: Pass when markup accurately describes content users can see and validates for the intended type; fail when properties are misleading, unsupported, hidden, or added only to chase a rich result.
FAQ content can be useful to readers, but do not treat FAQ markup as a current Google FAQ rich-result tactic. Severity: Medium, or High when misleading markup misrepresents products or claims. Owner: Technical SEO with engineering and content review.
Corrective action: Remove unsupported properties, align markup with visible content, and keep product details consistent with the canonical page. Validation step: Test the deployed output with Schema.org validation and inspect rendered source. Tools: Schema.org, Validator.schema.org
HTTPS coverage
Evidence required: crawl results, certificate status, mixed-content checks, redirects, and subdomain inventory. Pass/fail condition: Pass when intended public pages and transactional paths use valid HTTPS without mixed-content or redirect defects; fail when users or crawlers can reach insecure or broken variants.
Severity: Critical for checkout or account flows; High for public pages with certificate or redirect failures. Owner: Platform or infrastructure engineering. Corrective action: Correct certificate, redirect, canonical, and mixed-content issues across affected hosts.
Validation step: Re-crawl all relevant subdomains and verify representative browser sessions. Tools: SSL Labs, Screaming Frog
Robots.txt and XML sitemap controls
Evidence required: robots directives, sitemap files, indexability reports, canonical tags, and examples of filter or faceted URLs. Pass/fail condition: Pass when directives reflect the intended crawl and index strategy, priority URLs are discoverable, and low-value parameter combinations are handled deliberately; fail when important pages are blocked or large URL sets are generated without a clear purpose.
Severity: High when important pages are blocked or duplicate URL expansion is substantial; Medium otherwise. Owner: Technical SEO with engineering. Corrective action: Align crawl directives, sitemap inclusion, canonicalization, and internal links with the approved indexable URL set.
Validation step: Re-crawl the site and compare sitemap, indexability, and canonical reports before and after the change. Tools: Screaming Frog, GSC