๐ฏ ๐ฃ๐ข๐ฆ๐ง-๐๐๐ฃ๐๐ข๐ฌ ๐๐๐๐๐๐ฆ ๐๐ข๐ฅ ๐๐๐ข๐จ๐๐๐๐๐ฅ๐ ๐ฃ๐๐๐๐ฆ
I spent two weeks fixing bugs in production. These issues only appeared after deployment. Now I run three fast checks to stop them.
I use Astro 5 and Cloudflare Pages. Here is the workflow.
Sitemap Health
- Check if sitemap-index.xml returns a 200 status.
- Check the URL count in your sub-sitemap.
- A low count means your data pipeline failed.
- Use curl to catch redirect errors.
Search Engine Sync
- Use a script to send URLs to IndexNow.
- This updates Bing and Yandex.
- A 403 error means your key file is wrong.
- Trigger this after your build is live.
Weekly Performance
- Run a Lighthouse audit every Monday.
- Test your homepage and one deep page.
- Watch for speed drops or layout shifts.
- Track trends instead of blocking deploys.
Static sites do not need complex tests. These checks cover the real failure points.
Source: https://dev.to/morinaga/three-post-deploy-checks-i-run-after-every-cloudflare-pages-build-4jnm