{
  "$type": "site.standard.document",
  "canonicalUrl": "https://www.simoncox.com/short-articles/2023-06-04-netlify-prerender-cache/",
  "description": "Crawling a newly changed website on Netlify can bring you incorrect cached results!",
  "path": "/short-articles/2023-06-04-netlify-prerender-cache/",
  "publishedAt": "2023-06-04T12:14:13.978Z",
  "site": "at://did:plc:tki7vwlanxbwrz2er67eaeqa/site.standard.publication/3mp4h4md7zv2y",
  "tags": [
    "Web",
    "SEO"
  ],
  "textContent": "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. \\\n\\\nThe 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.\n\nThere is a very good explanation of what's happening on the Netlify support pages.",
  "title": "Netlify prerender cache"
}