𝟯 𝗣𝗼𝘀𝘁-𝗗𝗲𝗽𝗹𝗼𝘆 𝗖𝗵𝗲𝗰𝗸𝘀 𝗜 𝗥𝘂𝗻 𝗔𝗳𝘁𝗲𝗿 𝗘𝘃𝗲𝗿𝘆 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲 𝗣𝗮𝗴𝗲𝘀 𝗕𝘂𝗶𝗹𝗱
I spent two weeks debugging production issues.
One error was a sitemap rule that blocked my sitemap index. Another was an image upload lag. These issues only appeared after deployment.
I do not use full end-to-end test suites. Instead, I use three specific checks to catch common failures. I run these on three sites built with Astro 5.
- Sitemap Verification
I check if sitemap-index.xml returns a 200 status code on all domains. I use curl to verify this.
I also check the sub-sitemap, sitemap-0.xml. I ensure it has a minimum number of URLs. If the count drops, my data pipeline likely failed.
I learned this the hard way. A redirect rule once broke my sitemap for five days. It worked in a browser but failed for web crawlers.
- IndexNow Submission
After the sitemap check, I run a node script. This script collects URLs and sends them to the IndexNow endpoint for Bing, Yandex, Naver, and Seznam.
I run this manually after a deploy. This ensures I submit URLs that are live.
If IndexNow returns a 403 error, my key verification file is missing or a redirect rule is broken. Catching this early prevents delays in search engine indexing.
- Lighthouse Trend Monitoring
I run this check on a schedule every Monday. I use lighthouse-ci to check performance, layout stability, and accessibility.
I monitor three sites with one homepage and one deep page each.
I do not use these scores to block deployments. I use them to track trends. If scores drop, I know a recent change in my CSS or components caused a layout shift.
These checks cover my actual failure points. Since my sites are static, I do not need uptime monitoring or API checks. I focus only on what can break in a static CDN deployment.
Source: https://dev.to/morinaga/three-post-deploy-checks-i-run-after-every-cloudflare-pages-build-4704