Bots read fast pages too: what we reprioritised after an AI-crawler audit
An audit was conducted to assess how AI crawlers interact with a client's website. The findings revealed significant discrepancies between monitored URLs and those actually accessed by bots, highlighting issues with crawlability. As a result, the team adjusted their monitoring priorities to better accommodate AI crawler performance and improve overall site responsiveness.
- ▪The audit focused on understanding how GPTBot and other AI crawlers accessed the website's content.
- ▪It was discovered that many URLs being monitored did not align with those frequently requested by bots.
- ▪Crawlability issues included timeouts, JavaScript shells, and accidental blocks that hindered bot access.
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 === 3769723) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Apogee Watcher Posted on May 30 • Originally published at apogeewatcher.hashnode.dev Bots read fast pages too: what we reprioritised after an AI-crawler audit #webdev #seo #ai #webperf We ran a small audit last winter because a client asked whether GPTBot could "see" their new help centre. Search Console looked fine. PageSpeed Insights on the homepage looked fine.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
