Google Docs

Google Docs may fetch an external page or image after a user inserts that resource into a document. Google makes the request so the Docs feature can use the referenced content. The visit follows a user action and is not an autonomous crawl looking for new URLs.

The request should be read as a fetch of the supplied resource, not as a normal reader session. It may arrive without the surrounding navigation that a person would generate in a browser. There is no documented basis for treating it as a crawl through the rest of the site.

Google does not include a dedicated Docs token in its current published fetcher list, which it says is not exhaustive. Its general policy also says user-triggered fetchers usually ignore robots.txt. Without a Docs-specific compliance statement or supported token, a crawler group cannot be treated as reliable control.

This fetch is separate from Googlebot and Google-Extended. No available operator documentation assigns it a role in search indexing, AI answer retrieval, or model training. It indicates that a Google Docs feature requested a public resource, nothing more.