𝟯 𝗣𝗼𝘀𝘁-𝗗𝗲𝗽𝗹𝗼𝘆 𝗖𝗵𝗲𝗰𝗸𝘀 𝗔𝗳𝘁𝗲𝗿 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲 𝗣𝗮𝗴𝗲𝘀 𝗕𝘂𝗶𝗹𝗱𝘀
I spent two weeks fixing production issues.
One error involved a sitemap redirect rule. It blocked my sitemap file. Another error involved an image upload lag.
I do not use full end-to-end test suites. Instead, I use three specific checks. These checks target the exact ways my sites fail.
I run these on three Astro 5 SSG sites: aiappdex.com, findindiegame.com, and ossfind.com.
- Sitemap Validation
I verify that sitemap-index.xml returns a 200 status code. I do not follow redirects. This is important because a bad redirect rule can hide errors from browsers but show them to crawlers.
I also check sitemap-0.xml. I ensure it has a minimum number of URLs. If the URL count drops, my data pipeline likely failed.
- 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 breaking the path. Checking this immediately prevents indexing delays.
I run this manually after deployment. This ensures I submit live URLs rather than URLs still in the deployment process.
- Lighthouse Trend Monitoring
I run a Lighthouse check on a schedule every Monday. I check one homepage and one deep page per site.
I look for:
- Performance scores below 80
- CLS above 0.1
- Accessibility regressions
I do not block deployments if these scores drop. I use these scores to monitor trends. A drop might signal a layout change in my CSS or components.
Why these three?
I do not use uptime monitoring because I trust Cloudflare. I do not use API checks because my sites are static. For a static CDN deployment, these three checks cover my actual risks.
Source: https://dev.to/morinaga/three-post-deploy-checks-i-run-after-every-cloudflare-pages-build-f12