Urgent.News

What's breaking now, across thousands of outlets.

Tech

I Analyzed 2,849 Crawler Requests. Here's What Search Bots Actually Do on New Sites.

I Analyzed 2,849 Crawler Requests. Here's What Search Bots Actually Do on New Sites. I run k1r4.space — a site with 30 HTML tools, a 31-post blog, and 4 SEO tutorials. I logged every single request for a full day. Here's what 321 crawler requests from 12 different bots told me about SEO for new sites. The Setup My site runs on a single VPS (Debian 13, AMD Ryzen 5 3600, 62GB RAM, no GPU) behind…

An SEO analyst examined 2,849 crawler requests to a single website over the course of one day. The results suggest that more than half of the bot traffic comes from AI companies training models, rather than search engines indexing pages. The top content visited included tutorial pages, which received 50 combined crawler visits, compared to blog posts with ~18 and individual tools with ~20 visits.

This is likely because tutorials are text-heavy, semantically dense, and link-rich, making them easy for bots to parse and index. Googlebot, the most aggressive crawler, made 80 requests, which included checking the robots.txt file, loading the sitemap, following links to tutorials, visiting blog posts, and sporadically checking tool pages.

The findings highlight the importance of having a properly configured robots.txt file, submitting sitemaps, writing tutorials instead of just tools, internal linking between tutorials and tools, and utilizing IndexNow for Bing verification. Additionally, AI bots are actively crawling sites, ingesting content for the next generation of AI models.

Googlebot's aggressive crawling demonstrates that indexing is separate from merely visiting a site, with new sites typically experiencing a 1-4 week lag before their content is indexed.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Taming the Exchange API: Handling -4509 Errors and the F-065 Retry Mechanism in Quant Systems

Taming the Exchange API: Handling -4509 Errors and the F-065 Retry Mechanism in Quant Systems Tags: #algotrading #crypto #ai #buildinpublic The Incident: When Local Truth Meets Exchange Reality It was…

  • -4509 error occurs when GTE order lacks anchored open position
  • F-065 Retry Mechanism handles transient API rejection errors
  • Three failed stop-loss adjustments before successful F-065 retry

More from Wednesday 7 October →