𝟯 𝗣𝗼𝘀𝘁-𝗗𝗲𝗽𝗹𝗼𝘆 𝗖𝗵𝗲𝗰𝗸𝘀 𝗜 𝗥𝘂𝗻 𝗔𝗳𝘁𝗲𝗿 𝗘𝘃𝗲𝗿𝘆 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲 𝗣𝗮𝗴𝗲𝘀 𝗕𝘂𝗶𝗹𝗱
I spent two weeks debugging production errors.
One error was a sitemap rule that blocked my sitemap index. Another was an image upload race condition. These issues only appeared after deployment.
I now run three specific checks after every Cloudflare Pages build. I do not use a full test suite. I use these fast checks to catch actual failures.
I run these on three sites using Astro 5 SSG: aiappdex.com, findindiegame.com, and ossfind.com.
𝟭. 𝗦𝗶𝘁𝗲𝗺𝗮𝗽 𝗩𝗲𝗿𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻
I check if sitemap-index.xml returns a 200 status code on all domains. I use curl to verify this. I do not follow redirects.
This caught a mistake I made previously. I had a rule that redirected my sitemap index to a sub-sitemap. It looked fine in a browser, but it blocked search crawlers.
I also check sitemap-0.xml. I ensure the URL count meets a minimum threshold. If the count drops, my data pipeline likely failed.
𝟮. 𝗜𝗻𝗱𝗲𝘅𝗡𝗼𝘄 𝗦𝘂𝗯𝗺𝗶𝘀𝘀𝗶𝗼𝗻
After the sitemap check, I run a node script. This script reads the live sitemap and sends the URLs to the IndexNow endpoint. This notifies Bing, Yandex, Naver, and Seznam.
If IndexNow returns a 403 error, my key verification file is missing or a redirect is breaking the path. Catching this immediately prevents indexing delays.
I run this manually after deployment succeeds. This ensures I submit URLs that are actually live on the CDN.
𝟯. 𝗟𝗶𝗴𝗵𝘁𝗵𝗼𝘂𝘀𝗲 𝗧𝗿𝗲𝗻𝗱 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴
I run this on a cron job every Monday. It is too slow to run after every deploy.
I check performance, layout shifts, and accessibility. I look for regressions in my Astro SSG sites. If scores drop, I check my Tailwind configuration or component changes.
I do not use these scores to block builds. I use them to track trends.
These three checks cover my actual failure points. I do not use uptime monitoring or end-to-end tests. For static sites on a CDN, these specific checks provide the most value.
Source: https://dev.to/morinaga/three-post-deploy-checks-i-run-after-every-cloudflare-pages-build-2eg1