Another day, another peek into the digital trenches! Today, we observed a total of 612 visits, with 8 active bots crawling our site. The usual suspects were out in force, diligently indexing and, hopefully, appreciating the insights we offer.
Here’s a quick snapshot of the top 5 bots by visit count:
| Bot Name | Visits |
| Bingbot | 515 |
| Bytespider | 43 |
| ClaudeBot | 27 |
| AhrefsBot | 11 |
| YandexBot | 8 |
It's clear that Bingbot remains the dominant force, accounting for a whopping 515 visits. That's a significant portion of our traffic! Bytespider, while a distant second, still managed a respectable 43 visits. We also saw some activity from ClaudeBot, AhrefsBot, and YandexBot, all contributing to the overall crawl activity. The top paths accessed across all bots were mostly the usual suspects: /robots.txt, sitemap files, and the home page. The /robots.txt file had 19 visits from 7 bots. That's a clear indicator that many bots are respecting (or at least checking) our crawl directives. The sitemap files are also getting a lot of attention, which is good to see as they help bots discover new content.
An interesting pattern today is the activity around /sitemap-news.xml. ClaudeBot hit this path with 12 visits, and AhrefsBot with 2 visits. This suggests a strong interest in our news-related content. Also, the presence of 3 visits to /sitemap-hosted-llms-2.xml from Bingbot tells us they are starting to look at our hosted LLM data. We also saw some activity on older blog posts. Specifically, there were 3 visits to the 2026-05-10 diary post.
Unfortunately, we also observed some errors. Both Bytespider and Bingbot encountered 503 errors (service unavailable) when trying to access /aeo/shops/flexoplate-com-tw/llms.txt, and /aeo/shops/hongyuan-hy-com/llms.txt and /aeo/shops/titanwire-com-tw/llms.txt respectively. This could indicate temporary server issues or some blocking going on. We need to investigate these errors, especially as they're affecting Bingbot, and a service with the potential to generate 2 visits. This could point to issues with those specific shop pages, particularly related to the LLM content we're serving. Let's make sure our shop pages are returning the correct status codes and that we are not unintentionally blocking any bots or pages.
Now, for a concrete AEO tip: Given the high volume of Bingbot traffic and the errors experienced, check the internal linking on the affected shop pages. Make sure that they are correctly linked from the main navigation or content, so that Bingbot can easily find and index them, fixing the 503 errors on the shop pages to make sure their LLM data is accessible, and also review the robots.txt file to ensure there are no unintended directives blocking Bingbot from essential content.
That's all for today! Remember to keep an eye on your own site's AI traffic patterns. Use AEO Scanner to gain these insights and stay ahead in the ever-evolving world of AI and SEO!