𝟯 𝗣𝗼𝘀𝘁-𝗗𝗲𝗽𝗹𝗼𝘆 𝗖𝗵𝗲𝗰𝗸𝘀 𝗜 𝗥𝘂𝗻 𝗔𝗳𝘁𝗲𝗿 𝗘𝘃𝗲𝗿𝘆 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲 𝗣𝗮𝗴𝗲𝘀 𝗕𝘂𝗶𝗹𝗱
I spent two weeks debugging issues that only appeared in production.
One rule blocked my sitemap. Another issue involved a race condition during image uploads. These mistakes cost time.
Now, I run three specific checks after every Cloudflare Pages deploy. I use Astro 5 SSG on three sites: aiappdex.com, findindiegame.com, and ossfind.com.
These checks focus on real failures I have faced.
- 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 aiappdex.com, that number is 1,000. If the count drops, my data pipeline failed.
A bad redirect rule once hid my sitemap from crawlers for five days. It looked fine in a browser but failed in a curl test. This check catches those errors immediately.
- IndexNow Submission
After the sitemap check, 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 broken. Catching this early prevents indexing delays.
I run this manually after deployment. This ensures I only submit URLs that are live and stable.
- Weekly Lighthouse Audits
I run a Lighthouse check every Monday at 04:30 UTC. I check one homepage and one deep page per site.
I monitor three metrics:
- Performance (Target: above 80)
- CLS (Target: below 0.1)
- Accessibility scores
I use Lighthouse as a trend monitor. I do not block builds if a score drops slightly. I use these results to spot regressions in my Tailwind configuration or layout components.
I do not use uptime monitoring or end-to-end tests. These sites are static. My entire runtime is pre-built HTML and CSS. These three checks cover my actual risks.
Source: https://dev.to/morinaga/three-post-deploy-checks-i-run-after-every-cloudflare-pages-build-3fi0