# Google-Pinpoint

Google says the Google-Pinpoint fetcher requests individual URLs that Pinpoint users specified as sources for their personal collections of documents. The user-triggered fetchers section says these fetchers generally ignore robots.txt rules because a user requested the fetch. The page does not print a separate robots.txt User-agent line. This check matches the whole token and still reports the RFC 9309 decision.

- Operator: Google
- Kind: user_fetch
- robots.txt: generally_ignores. The vendor says this fetcher generally ignores robots.txt, because a person requested the fetch.
- HTTP user-agent: Google-Pinpoint The page prints this string as the HTTP user agent and does not print a separate robots.txt User-agent line.
- IP list: none on the cited page
- Source: https://developers.google.com/crawling/docs/crawlers-fetchers/google-user-triggered-fetchers (retrieved 2026-10-18)

## JSON

`curl -s https://whosthatbot.com/v1/crawlers/google-pinpoint`

## Check this token

tools/call with name check_robots is the same check at https://whosthatbot.com/mcp. Send `Content-Type: application/json` and `Accept: application/json, text/event-stream`. The pasted file disallows Google-Pinpoint on `/docs` and allows `*`. The call does not fetch a host.

```
curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: Google-Pinpoint\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["google-pinpoint"]}}}'
```

That call returns fetched_target false. This row is disallow via group Google-Pinpoint, rule Disallow: /.

Each card paraphrases the linked vendor page and was checked on source.retrieved. This is not legal advice. robots.txt is a request from the site owner. Botcard does not fetch third-party sites and does not suggest ways around a disallow rule.