𝟯 𝗣𝗼𝘀𝘁-𝗗𝗲𝗽𝗹𝗼𝘆 𝗖𝗵𝗲𝗰𝗸𝘀 𝗜 𝗥𝘂𝗻 𝗔𝗳𝘁𝗲𝗿 𝗘𝘃𝗲𝗿𝘆 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲 𝗣𝗮𝗴𝗲𝘀 𝗕𝘂𝗶𝗹𝗱

I spent two weeks fixing production bugs. A bad redirect rule blocked my sitemap. An image upload failed due to deployment lag.

I now run three specific checks after every Cloudflare Pages build. I do not use a full test suite. I use fast checks that target my actual failure points.

I use Astro 5 SSG on three sites: aiappdex.com, findindiegame.com, and ossfind.com.

Here are the three checks:

  1. Sitemap Verification I verify that sitemap-index.xml returns a 200 status on all domains. I also check sitemap-0.xml. I ensure the URL count stays above a set threshold. For aiappdex.com, I expect at least 1,000 URLs. If the count drops, my data pipeline broke.

I use curl without redirect following. This catches errors where a redirect rule makes a sitemap look fine in a browser but breaks it for crawlers.

  1. 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.

I run this manually after deployment. This ensures I submit URLs that are actually live. If IndexNow returns a 403 error, I know my key verification file is missing or a redirect rule is broken. Catching this early prevents indexing delays.

  1. 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 watch for these metrics:

  • Performance below 80
  • CLS above 0.1
  • Accessibility score drops

Since my sites use static HTML and CSS, scores should stay steady. If they drop, a recent change in Tailwind or a component likely broke the layout. I use these results to monitor trends rather than to block builds.

I do not monitor uptime or API availability. My sites are static. The database only runs at build time. 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-39h6