𝟯 𝗣𝗼𝘀𝘁-𝗗𝗲𝗽𝗹𝗼𝘆 𝗖𝗵𝗲𝗰𝗸𝘀 𝗜 𝗥𝘂𝗻 𝗔𝗳𝘁𝗲𝗿 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲 𝗣𝗮𝗴𝗲𝘀 𝗕𝘂𝗶𝗹𝗱𝘀
I spent two weeks debugging production issues.
A sitemap redirect rule blocked my sitemap files. An image upload failed because of deployment lag. These mistakes cost time.
Now, I use three specific checks after every Cloudflare Pages deploy. I do not use a full test suite. I use these three fast checks to catch the errors I actually face.
I run these on three sites built with Astro 5 SSG.
- Sitemap Verification
I check if sitemap-index.xml returns a 200 status code on all domains. I also check sitemap-0.xml.
I verify that the URL count meets a minimum threshold. For example, aiappdex.com must have at least 1,000 URLs. If the count drops, my data pipeline failed.
I use curl without following redirects. This helps me catch broken redirect rules that hide errors from browsers.
- IndexNow Submission
After the sitemap check, I run a script to submit URLs to IndexNow for Bing, Yandex, Naver, and Seznam.
The script reads the live sitemap and posts the URLs. If IndexNow returns a 403 error, it means my key verification file is missing or a redirect rule is broken.
I run this manually after deployment. This ensures I submit URLs that are live and stable.
- Lighthouse Performance Monitoring
I run this check on a weekly cron job rather than every deploy. It tracks performance trends.
I watch for:
- Performance scores below 80
- CLS above 0.1
- Accessibility regressions
Since my sites use Astro SSG with no client-side JS, these scores should stay steady. If they drop, a CSS change likely broke the layout. I treat these scores as a trend monitor, not a way to block deployments.
Summary
I do not use uptime monitoring or end-to-end user tests. For a static CDN deployment, these three checks cover my main risks. They protect my SEO and my layout integrity without adding unnecessary complexity.
Source: https://dev.to/morinaga/three-post-deploy-checks-i-run-after-every-cloudflare-pages-build-48b4