What to review
Client-rendered applications can delay important content and metadata or make route discovery difficult. Rendering support varies across crawlers, so inspect what each important URL actually returns.
Approach
- Compare the initial HTML, rendered DOM, response status and canonical URL on representative routes.
- Choose server-side rendering, static generation or prerendering according to the application and publishing workflow.
- If prerendering is used, maintain equivalent content for users and crawlers, cache invalidation and reliable error handling.
- Verify that titles, descriptions, canonical tags and structured data reflect each route rather than a shared application shell.
How to validate
Test important templates and status codes after release. Review rendered output and indexing in Search Console, and use logs and performance measurements to confirm that the change works as intended.