𝟯 𝗣𝗼𝘀𝘁-𝗗𝗲𝗽𝗹𝗼𝘆 𝗖𝗵𝗲𝗰𝗸𝘀 𝗜 𝗥𝘂𝗻 𝗔𝗳𝘁𝗲𝗿 𝗘𝘃𝗲𝗿𝘆 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲 𝗣𝗮𝗴𝗲𝘀 𝗕𝘂𝗶𝗹𝗱
I spent two weeks debugging production issues.
A sitemap rule blocked my index file. A race condition caused image upload failures. These problems only appeared after deployment.
Now, I run three specific checks after every build. I do not use a full test suite. I use fast checks that target my actual failure points.
I run these on three sites built with Astro 5 SSG: aiappdex.com, findindiegame.com, and ossfind.com.
𝟭. Sitemap Availability and Integrity
I verify that sitemap-index.xml returns a 200 status code on all domains.
I also check sitemap-0.xml. I ensure the URL count meets a minimum threshold. For aiappdex.com, that threshold is 1,000. If it drops below that, my data pipeline failed.
I learned this the hard way. A bad redirect rule worked in my browser but blocked crawlers. Using curl to check the status code caught the error immediately.
𝟮. IndexNow Submission
After sitemap checks pass, I run a script to submit URLs to IndexNow. This notifies Bing, Yandex, Naver, and Seznam about new content.
If IndexNow returns a 403 error, my key verification file is missing or a redirect rule is breaking the path. Catching this early prevents indexing delays.
I run this manually after deployment. This ensures I submit URLs that are live and stable.
𝟯. Lighthouse Trend Monitoring
I run a Lighthouse check on a schedule every Monday. This check looks at performance, layout shifts, and accessibility.
I watch for trends rather than hard failures. If a score drops slightly, I do not block the deploy. I use these results to spot regressions in my Tailwind config or layout components.
Why these three?
I do not use uptime monitoring because I trust Cloudflare. I do not use end-to-end tests because my sites are static. For a static CDN deployment, these three checks cover my main risks.
Source: https://dev.to/morinaga/three-post-deploy-checks-i-run-after-every-cloudflare-pages-build-3a61