Netlify prerender cache

In February 2023 I discovered I had an issue with crawling a site after some changes. I like to fix things to make websites work properly so often go through several itterations of the code fixing things.

The same issue cropped up again in June 2023 so I thought I had better post a Short about it to remind myself rather than just moan about it on Mastodon! When running a crawler, such as Sitebulb, Screaming Frog or SEO PowerSuite, against a site on Netlify you could hit the prerender cache. The same happens when you test a page in Google Search Console but the real Google crawler is ok. To get the real results either wait 48 hours and crawl or change the crawler User Agent to something else, such as Safari, and rerun the crawl.

screenshot of Screaming Frog results showing 3 301 issues with a site after these issues had been fixed and deployed. Netlify is caching the pages and the crawls are given the old cached version.

There is a very good explanation of what's happening on the Netlify support pages.

By Simon Cox Published: Sun, Jun 4, 2023

Next short: 11ty image shortcode best practice

Previous short: Stanton Coach chassis progress

Latest Shorts

Or all the short articles

Latest articles

Or all the articles