Critical content accessible to Googlebot; no cloaking between bot and users
Why it matters
Client-only rendering of product descriptions, article bodies, and pricing leaves Googlebot with empty shells — the rendering budget times out before your JavaScript finishes, so the page gets indexed with zero substantive content. User-agent-based cloaking goes further and earns manual action penalties under Google's Spam Policies, which can deindex the entire domain. Either failure mode silently collapses organic traffic on your highest-value commerce and content routes.
Severity rationale
Critical because cloaking triggers manual penalties that deindex entire domains and tank organic revenue.
Remediation
Move critical content into Server Components or static generation so it exists in the HTML source before hydration. Never branch rendering on req.headers['user-agent']. Use app/products/[slug]/page.tsx as a server component:
export default async function ProductPage({ params }) {
const product = await fetchProduct(params.slug)
return <article><h1>{product.name}</h1><p>{product.description}</p></article>
}
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Advanced SEO Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from seo-advanced·automated