𝟯 𝗣𝗼𝘀𝘁-𝗗𝗲𝗽𝗹𝗼𝘆 𝗖𝗵𝗲𝗰𝗸𝘀 𝗜 𝗥𝘂𝗻 𝗔𝗳𝘁𝗲𝗿 𝗘𝘃𝗲𝗿𝘆 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲 𝗣𝗮𝗴𝗲𝘀 𝗕𝘂𝗶𝗹𝗱
I spent two weeks debugging production issues. One sitemap redirect rule blocked my sitemap index. Another issue involved image upload lag.
I do not use full end-to-end test suites. Instead, I use three specific checks. These focus on the failure modes I actually face.
I run these on three Astro 5 sites: aiappdex.com, findindiegame.com, and ossfind.com.
𝟭. 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.
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 helps catch this 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 a site returns a 403 error, my verification file is missing or a redirect rule is broken. I catch this right after deployment to avoid indexing delays.
I run this manually after deployment. This ensures I submit URLs that are live on the CDN.
𝟯. Weekly Lighthouse Audits
I run a scheduled audit every Monday. This check takes a few minutes per site.
I monitor three metrics:
- Performance scores below 80
- CLS above 0.1
- Accessibility score regressions
I use these results to watch trends. I do not block deployments if a score drops slightly. For a static site, these three checks cover my main risks.
I do not use uptime monitoring or API checks. My sites are static. Everything is pre-built. These checks protect the parts of my stack that actually change.
Source: https://dev.to/morinaga/three-post-deploy-checks-i-run-after-every-cloudflare-pages-build-408k