Three post-deploy checks I run after every Cloudflare Pages build
The article discusses three post-deploy checks implemented after Cloudflare Pages builds to ensure site functionality. These checks focus on sitemap reachability, IndexNow batch submission, and weekly Lighthouse spot-checks. The author emphasizes the importance of these checks in preventing issues that may arise after deployment.
- ▪The first check verifies that the sitemap-index.xml is reachable and returns a 200 status code for all three domains.
- ▪The second check involves submitting URLs to the IndexNow endpoint for search engines after confirming the sitemap is correct.
- ▪The third check is a weekly Lighthouse performance assessment to monitor site performance and accessibility.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3907455) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } MORINAGA Posted on May 16 Three post-deploy checks I run after every Cloudflare Pages build #webdev #githubactions #astro #tutorial After spending two weeks debugging issues that only showed up in production — a sitemap _redirects rule that was blocking my own sitemap-index.xml and a Bluesky image upload race against Cloudflare Pages deploy lag — I added three post-deploy checks to my workflow.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
