𝟯 𝗣𝗼𝘀𝘁-𝗗𝗲𝗽𝗹𝗼𝘆 𝗖𝗵𝗲𝗰𝗸𝘀 𝗜 𝗥𝘂𝗻 𝗔𝗳𝘁𝗲𝗿 𝗘𝘃𝗲𝗿𝘆 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲 𝗣𝗮𝗴𝗲𝘀 𝗕𝘂𝗶𝗹𝗱
I spent two weeks debugging issues that only appeared in production.
One sitemap rule blocked my sitemap index. Another issue involved image upload delays.
I do not use a full end-to-end test suite. Instead, I use three specific checks to catch the errors I actually face.
I run these on three sites built with Astro 5 SSG on Cloudflare Pages.
- Sitemap Verification
I check if sitemap-index.xml returns a 200 status code on all domains.
I also check sitemap-0.xml. I ensure it contains a minimum number of URLs. For one site, that number is 1,000. If the count drops, my data pipeline failed.
I learned this the hard way. A redirect rule once broke my sitemap for five days. It looked fine in a browser but failed for crawlers. Using curl helped me find this error immediately.
- IndexNow Submission
After sitemap checks pass, I run a script to submit URLs to IndexNow. This sends my URLs to Bing, Yandex, Naver, and Seznam.
If IndexNow returns a 403 error, my key verification file is missing or a redirect rule is broken. Catching this right after deployment prevents indexing delays.
I run this manually after a deploy rather than inside GitHub Actions. This ensures I submit URLs that are live and stable.
- Weekly Lighthouse Audits
I run a Lighthouse check every Monday at 04:30 UTC.
I monitor performance, layout shifts, and accessibility scores. Since these sites use Astro SSG with no client-side JS, scores should stay steady. A drop tells me a CSS or component change broke the layout.
I do not use these scores to block deploys. I use them to monitor trends.
Why these three?
I do not use uptime monitoring or API checks. My sites are static. Cloudflare handles the infrastructure. The database is only queried at build time.
For static CDN deployments, these three checks cover my actual risks.
Source: https://dev.to/morinaga/three-post-deploy-checks-i-run-after-every-cloudflare-pages-build-2862