When the bot version and the user version slowly drifted apart

When the bot version and the user version slowly drifted apart

A travel-deals site ran dynamic rendering — a prerender path for bots, the live app for users. It worked for two years. Then rankings on its money pages eroded 30% over a quarter with no obvious cause.

The symptom: gradual, not sudden. Each individual page looked fine. The decline was diffuse, spread across the catalog.

The investigation diffed the bot-served HTML against the live user DOM, page by page. They'd drifted. A dozen front-end features had shipped over the year — new schema, updated internal links, fresh content blocks — all to the live app. The prerender service ran an older render path nobody had updated. Bots were reading a year-old version of the site while users got the current one.

Turns out dynamic rendering isn't 'set and forget.' It's a parallel copy of your site that silently rots unless every front-end change is verified on the bot path too.

The fix: add an automated diff that flags any meaningful gap between bot-rendered and live HTML, and run it in the deploy pipeline.

Result: after re-syncing the render path, the eroded -30% recovered to +5% over 12 weeks. The long-term fix was the monitoring, not the one-time patch.