Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Lista de recuperadores generados por el usuario de Google
Los usuarios inician los recuperadores activado por el usuario para ejecutar una función de recuperación en un
producto de Google. Por ejemplo,
Google Site Verifier actúa a pedido de un usuario, o un sitio alojado en Google Cloud (GCP) tiene una función que permite
a sus usuarios recuperar una cuenta Feed RSS Debido a que un usuario solicitó la recuperación, estas recuperaciones suelen ignorar las reglas de robots.txt. En general,
propiedades técnicas
de los rastreadores de Google también se aplican a los recuperadores activados por el usuario.
Los rangos de IP que usan los recuperadores activados por el usuario
se publican en los objetos
user-triggered-fetchers.json y
user-triggered-fetchers-google.json. La máscara DNS inversa de los recuperadores activados por el usuario, en función de si el recuperador es Google
o propiedad del usuario, coincide con ***-***-***-***.gae.googleusercontent.com o
google-proxy-***-***-***-***.google.com respectivamente.
En la siguiente lista, se muestran los buscadores activados por el usuario, sus cadenas de usuario-agente tal como aparecen en
las solicitudes HTTP y los productos con los que están asociados. La lista no es exhaustiva; solo
abarca los solicitantes que tienen más probabilidades de aparecer en los archivos de registro y sobre los que
recibimos preguntas.
-
| Usuario-agente en solicitudes HTTP |
FeedFetcher-Google; (+http://www.google.com/feedfetcher.html)
|
| Productos asociados |
Feedfetcher se usa para rastrear feeds RSS o Atom de Google Noticias y PubSubHubbub.
|
Centro para editores de Google
-
| Usuario-agente en solicitudes HTTP |
GoogleProducer; (+https://developers.google.com/search/docs/crawling-indexing/google-producer)
|
| Productos asociados |
Recuperaciones y procesos de Publisher Center de Google
que los publicadores proporcionaron de forma explícita
para usarlos en las páginas de destino de Google Noticias.
|
-
| Usuario-agente en solicitudes HTTP |
| Agente para dispositivos móviles |
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 para computadoras de escritorio |
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 anterior (obsoleto) |
google-speakr
|
|
| Productos asociados |
A pedido del usuario, Google Read Aloud recupera y lee páginas web con la función de texto a voz (TTS). |
-
| Usuario-agente en solicitudes HTTP |
Mozilla/5.0 (compatible; Google-Site-Verification/1.0)
|
| Productos asociados |
Google Site Verifier recupera los tokens de verificación de Search Console.
|
Salvo que se indique lo contrario, el contenido de esta página está sujeto a la licencia Atribución 4.0 de Creative Commons, y los ejemplos de código están sujetos a la licencia Apache 2.0. Para obtener más información, consulta las políticas del sitio de Google Developers. Java es una marca registrada de Oracle o sus afiliados.
Última actualización: 2025-08-04 (UTC)
[null,null,["Última actualización: 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. |"]]
