Yahoo! Slurp

What Yahoo! Slurp does

Slurp was once one of the web's major crawlers, back when Yahoo ran its own search index. Yahoo's web results have been supplied by Bing since 2010, so Slurp's modern role is much narrower: Yahoo's own documentation describes it collecting content from partner sites and checking pages to improve personalized content across properties like Yahoo News, Finance, and Sports. It obeys the Robot Exclusion Standard and its crawl volume today is modest.

Why it visits your site

Content collection and verification for Yahoo's portal properties rather than for a standalone search index.

The bigger picture: search engine crawlers

Search crawlers remain the one category with a decades-old, well-understood bargain: they consume crawl budget and return ranked visibility. Everything about them is comparatively mature - published IP ranges, verification methods, granular directives, webmaster consoles. Blocking them is almost always self-harm, which is precisely why they need to be cleanly separated from AI crawlers in your data: a blanket bot block that catches Googlebot costs you your organic channel.

The complication the AI era added is that search indexes now feed AI features too - AI Overviews draw on Google's index, Copilot on Bing's. Operators have answered with control tokens that split AI use from search use of the same crawl. The practical upshot: your lever for AI concerns is usually a token, not a block on the search crawler itself.

Should you block it?

There is rarely a reason to. Its volume is low, it is well behaved, and blocking it mainly risks your content dropping out of Yahoo's content surfaces. If you are trimming every nonessential crawler, it is a safe cut - just do not expect a noticeable difference in server load.

Block via robots.txt

Add these lines to the robots.txt at your site root to ask Yahoo! Slurp to stay away:

User-agent: Slurp
Disallow: /

Remember that robots.txt is a request, not a lock - compliance is voluntary, and enforcement happens at the server. Viz's AI Control pairs robots.txt rules with server-level 403 responses and then probes your site to verify the block is actually holding.

How to see Yahoo! Slurp traffic on your site

You have three windows onto it, each with a catch. Raw hosting access logs contain every Yahoo! Slurp request, but many managed WordPress hosts don't expose them, and when they do you are grepping text files by hand. A CDN dashboard sees the traffic at the edge, but it lives outside WordPress and speaks in totals, not in your site's terms. And JavaScript analytics - GA4 and friends - will never show it at all, because Yahoo! Slurp doesn't run scripts.

Viz's answer is the request log: filter to Yahoo! Slurp and read exactly which URLs it fetched and when, right inside wp-admin - then watch the same filter after any blocking decision to see whether the visits stopped, slowed, or kept coming.