FeedFetcher-Google
FeedFetcher-Google fetches pages when a person using Google's assistant asks something that needs them, so a visit means someone is asking about the page right now.
Should you let it in?
Allow or block FeedFetcher-Google
Usually, yes. Each visit is a person asking Google's assistant something your page answers, right now. Blocking it means the answer is written without your page.
To ask it to stay out, add this to robots.txt. Whether it follows robots.txt is Google's call; its documentation says.
User-agent: FeedFetcher-Google
Disallow: /Is it really?
How to tell a real FeedFetcher-Google from an impostor
Anyone can put “FeedFetcher-Google” in a user agent. What can't be faked:
- Check the address. Google publishes the IP ranges FeedFetcher-Google uses: developers.google.com/static/crawling/ipranges/user-triggered-fetchers-google.json. A request whose user agent says FeedFetcher-Google from an address outside them is an impostor.
- Check reverse DNS. Look up the requesting IP's host name; it should end in
googlebot.comorgoogle.com. Then look that name up and make sure it resolves back to the same IP, since anyone can set a reverse DNS name on their own addresses.
In Punchline
How Punchline counts FeedFetcher-Google
Punchline labels a request that names FeedFetcher-Google with how sure it is: verified or declared when the evidence checks out, a lower tier when it can't be checked, and impostor when the evidence contradicts it. Each visit is counted under Google, with its purpose, so you can see whether FeedFetcher-Google is bringing people's questions to your pages and which pages it reads. How it works · Known agents