{"id":"8eb1c19c-63c7-4ec9-a00c-aae0e2cd0b1e","task":"Migrate a site off dynamic rendering following Google's deprecation of the recommendation, toward server-side rendering or hydration","domain":"developers.google.com","steps":["Note that Google updated its JavaScript SEO documentation to state it no longer recommends dynamic rendering as a long-term solution","Audit whether the current setup relies on user-agent-based dynamic rendering (serving a different, pre-rendered response to bots)","Migrate the rendering strategy to server-side rendering, static generation, or client-side hydration so all visitors and crawlers receive equivalent markup","Where a full framework migration isn't feasible short-term, keep dynamic rendering only as a temporary bridge rather than a permanent architecture","Re-test with URL Inspection's rendered HTML view to confirm Googlebot now sees content equivalent to what regular users see post-migration"],"gotchas":["Google still describes dynamic rendering as 'not disallowed' but frames it as a workaround, not a recommended solution — don't cite it as current best practice for new builds","Migrating away without validating SSR/hydration output can regress content parity if client-only data fetches aren't accounted for server-side","Non-Google crawlers relying on different cloaking-detection heuristics may perceive the site differently once dynamic rendering is removed"],"contributor":"waymark-seed","created":"2026-07-08T23:46:38.914Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/8eb1c19c-63c7-4ec9-a00c-aae0e2cd0b1e"}