Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Elenco dei fetcher attivati dall'utente di Google
I fetcher attivati dall'utente si avviano per eseguire un'azione di recupero all'interno di un prodotto Google. Ad esempio, Google Site Verifier agisce su richiesta di un utente, oppure un sito ospitato su Google Cloud (GCP) dispone di una funzionalità che consente agli utenti del sito di recuperare un feed RSS esterno. Poiché il recupero è stato richiesto da un utente, questi fetcher in genere ignorano le regole del file robots.txt. Le
proprietà tecniche
generali dei crawler di Google si applicano anche ai fetcher attivati dall'utente.
Gli intervalli di IP utilizzati dai fetcher attivati dall'utente sono pubblicati negli oggetti
user-triggered-fetchers.json e
user-triggered-fetchers-google.json. La maschera DNS inversa dei fetcher attivati dall'utente, a seconda che il fetcher sia di proprietà di Google o dell'utente, corrisponde rispettivamente a ***-***-***-***.gae.googleusercontent.com o google-proxy-***-***-***-***.google.com.
L'elenco seguente mostra i fetcher attivati dall'utente, le relative stringhe dello user agent così come appaiono nelle richieste HTTP e i prodotti a cui sono associati. L'elenco non è completo, si limita
solo ai richiedenti che hanno maggiori probabilità di apparire nei file di log e per cui abbiamo ricevuto domande.
-
| User-Agent nelle richieste HTTP |
FeedFetcher-Google; (+http://www.google.com/feedfetcher.html)
|
| Prodotti associati |
Feedfetcher viene utilizzato per eseguire la scansione di feed RSS o Atom per Google News e PubSubHubbub.
|
Google Publisher Center
-
| User-Agent nelle richieste HTTP |
GoogleProducer; (+https://developers.google.com/search/docs/crawling-indexing/google-producer)
|
| Prodotti associati |
Google Publisher Center recupera ed elabora i feed che gli editori hanno fornito esplicitamente per utilizzarli nelle pagine di destinazione di Google News.
|
-
| User-Agent nelle richieste HTTP |
| Agente mobile |
Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Mobile Safari/537.36 (compatible; Google-Read-Aloud; +https://support.google.com/webmasters/answer/1061943)
|
| Agente desktop |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36 (compatible; Google-Read-Aloud; +https://support.google.com/webmasters/answer/1061943)
|
| Agente precedente (deprecato) |
google-speakr
|
|
| Prodotti associati |
Su richiesta dell'utente, Google Read Aloud
recupera e legge le pagine web utilizzando la sintesi vocale (TTS).
|
-
| User-Agent nelle richieste HTTP |
Mozilla/5.0 (compatible; Google-Site-Verification/1.0)
|
| Prodotti associati |
Google Site Verifier recupera i token di verifica di Search Console.
|
Salvo quando diversamente specificato, i contenuti di questa pagina sono concessi in base alla licenza Creative Commons Attribution 4.0, mentre gli esempi di codice sono concessi in base alla licenza Apache 2.0. Per ulteriori dettagli, consulta le norme del sito di Google Developers. Java è un marchio registrato di Oracle e/o delle sue consociate.
Ultimo aggiornamento 2025-08-04 UTC.
[null,null,["Ultimo aggiornamento 2025-08-04 UTC."],[[["\u003cp\u003eUser-triggered fetchers are initiated by users within Google products and generally disregard robots.txt rules.\u003c/p\u003e\n"],["\u003cp\u003eThese fetchers utilize specific IP ranges and reverse DNS masks for identification, detailed in provided JSON files.\u003c/p\u003e\n"],["\u003cp\u003eGoogle products like Feedfetcher, Google Publisher Center, Google Read Aloud, and Google Site Verifier utilize user-triggered fetching for various purposes.\u003c/p\u003e\n"],["\u003cp\u003eA table lists these fetchers with their user agent strings and associated products for easier identification in log files, although user agent strings can be spoofed.\u003c/p\u003e\n"],["\u003cp\u003eVerifying the visitor's identity as a Google crawler is crucial and can be achieved using the provided verification guide.\u003c/p\u003e\n"]]],["User-triggered fetchers, initiated by user actions within Google products, ignore `robots.txt` rules. These fetchers' IP ranges are in `user-triggered-fetchers.json` and `user-triggered-fetchers-google.json`, with reverse DNS masks either `*.gae.googleusercontent.com` or `google-proxy-*.google.com`. Key fetchers include: Feedfetcher for RSS/Atom feeds; Google Publisher Center for publisher-supplied feeds; Google Read Aloud for text-to-speech; and Google Site Verifier for Search Console verification tokens. Each has distinct user-agent strings.\n"],null,["# Google User-Triggered Fetchers | Google Search Central\n\nList of Google user-triggered fetchers\n======================================\n\n\nUser-triggered fetchers are initiated by users to perform a fetching function within a Google\nproduct. For example,\n[Google Site Verifier](https://support.google.com/webmasters/answer/9008080)\nacts on a user's request, or a site hosted on Google Cloud (GCP) has a feature that allows the\nsite's users to retrieve an external RSS feed. Because the fetch was requested by a user, these\nfetchers generally ignore robots.txt rules. The general\n[technical properties](/search/docs/crawling-indexing/overview-google-crawlers#crawl-technical-props)\nof Google's crawlers also apply to the user-triggered fetchers.\n\n\nThe IP ranges the user-triggered fetchers use are\npublished in the\n[user-triggered-fetchers.json](/static/search/apis/ipranges/user-triggered-fetchers.json) and\n[user-triggered-fetchers-google.json](/static/search/apis/ipranges/user-triggered-fetchers-google.json)\nobjects. The user-triggered fetchers' reverse DNS mask, depending on whether the fetcher is Google\nor user owned, matches `***-***-***-***.gae.googleusercontent.com` or\n`google-proxy-***-***-***-***.google.com` respectively.\n\n\nThe following list shows the user-triggered fetchers, their user agent strings as they appear in\nthe HTTP requests, and the products they are associated with. The list is not exhaustive, it only\ncovers the requestors that are more likely to show up in log files and that we've received\nquestions about.\n| **Caution** : The user agent string can be spoofed. [Learn how to verify if a visitor is a Google crawler](/search/docs/crawling-indexing/verifying-googlebot).\n\n[Feedfetcher](/search/docs/crawling-indexing/feedfetcher)\n---------------------------------------------------------\n\n:\n\n |---------------------------------|--------------------------------------------------------------------------------------|\n | **User-Agent in HTTP requests** | ``` FeedFetcher-Google; (+http://www.google.com/feedfetcher.html) ``` |\n | **Associated products** | Feedfetcher is used for crawling RSS or Atom feeds for Google News and PubSubHubbub. |\n\n\nGoogle Publisher Center\n-----------------------\n\n:\n\n |---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n | **User-Agent in HTTP requests** | ``` GoogleProducer; (+https://developers.google.com/search/docs/crawling-indexing/google-producer) ``` |\n | **Associated products** | Google Publisher Center fetches and processes [feeds that publishers explicitly supplied](https://support.google.com/news/publisher-center/answer/9545414) for use in Google News landing pages. |\n\n\n[Google Read Aloud](/search/docs/crawling-indexing/read-aloud-user-agent)\n-------------------------------------------------------------------------\n\n:\n\n |---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n | **User-Agent in HTTP requests** | |---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Mobile agent | ``` Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Mobile Safari/537.36 (compatible; Google-Read-Aloud; +https://support.google.com/webmasters/answer/1061943) ``` | | Desktop agent | ``` Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36 (compatible; Google-Read-Aloud; +https://support.google.com/webmasters/answer/1061943) ``` | | Former agent (deprecated) | `google-speakr` | |\n | **Associated products** | Upon user request, Google Read Aloud [fetches and reads out web pages using text-to-speech (TTS)](/search/docs/crawling-indexing/read-aloud-user-agent). |\n\n\n[Google Site Verifier](https://support.google.com/webmasters/answer/9008080)\n----------------------------------------------------------------------------\n\n:\n\n |---------------------------------|------------------------------------------------------------------|\n | **User-Agent in HTTP requests** | ``` Mozilla/5.0 (compatible; Google-Site-Verification/1.0) ``` |\n | **Associated products** | Google Site Verifier fetches Search Console verification tokens. |"]]
