Nobody has adopted WhatsApp yet. Adopt WhatsApp: your name goes on a plaque on this page for a year.
WhatsApp's food bowl
the bowl, as bots see itThe bowl is empty.
Identification
Its full user-agent string, exactly as it arrives at the gate:
Meta does not publish a way to verify WhatsApp's traffic. Treat its user agent as a claim, not proof: anyone can send it.
Meta publishes no way to check it, so every visit filed here is taken at its word.
How to block WhatsApp
Add these two lines to the robots.txt file at the root of your site. Well-behaved crawlers read it before they crawl, so the change applies from WhatsApp's next visit. Nothing else on your site needs to change.
# Block WhatsApp from the whole site User-agent: WhatsApp Disallow: /
Or let it visit but keep it away from part of the site:
# Let it in, but keep it out of one room User-agent: WhatsApp Allow: / Disallow: /members/
Observed behaviour
Most active around 08:00. Before the coffee is made.
Requested 36 disallowed pages out of 1,619 requests. Never read robots.txt.
Walked through the hidden /trap/ door. Last caught 14 days ago.
Where it comes from
The networks WhatsApp's visits came from:
Networks and countries come from the visitor's IP address, looked up in a local copy of the DB-IP database. The addresses themselves are never stored.
Keeper's field notes
Questions site owners ask
Does WhatsApp respect robots.txt?
No. It has never requested robots.txt here, and it has fetched disallowed pages 36 times.
Will blocking WhatsApp hurt my search rankings?
No. But links to your site will be shared without a title or preview image, which tends to get fewer clicks.
How often does WhatsApp visit?
Here, about 3 requests a day over the last week. Visits to your site depend on its size, how often it changes, and how many links point to it.