Organízate con las colecciones
Guarda y clasifica el contenido según tus preferencias.
Reducir la frecuencia de rastreo de Google
La infraestructura de rastreo de Google cuenta con algoritmos sofisticados para determinar la frecuencia óptima de rastreo de un sitio. En cada visita, se intentan rastrear tantas páginas de tu sitio como sea posible sin sobrecargar el servidor. En algunos casos, el rastreo que hace Google de tu sitio web puede llegar a imponer una carga excesiva en tu infraestructura o generar costes no deseados por una interrupción del servicio. Para solucionar este problema, puedes reducir el número de solicitudes de los rastreadores de Google.
Identificar la causa de un aumento brusco del rastreo
Se puede producir un aumento considerable del rastreo si hay deficiencias en la estructura de tu sitio o problemas con tu sitio. Según los informes que hemos recibido en el pasado, las causas más habituales son las siguientes:
Una configuración ineficiente de las URLs del sitio, que suele deberse a una funcionalidad específica del sitio:
La navegación por facetas u otras funciones de ordenación y filtrado del sitio
Un calendario con muchas URLs para fechas específicas
Te recomendamos que te pongas en contacto con tu empresa de alojamiento y consultes los registros de acceso recientes de tu servidor para saber cuál es la fuente del tráfico y comprobar si se ajusta a las causas habituales de este aumento tan brusco en el rastreo. Después, consulta nuestras guías sobre cómo gestionar el rastreo de URLs de navegación por facetas y optimizar la eficiencia del rastreo.
Reducir urgentemente el tráfico del rastreador (en caso de emergencia)
Si necesitas reducir urgentemente la frecuencia de rastreo durante un periodo breve (por ejemplo, un par de horas o 1 o 2 días), devuelve un código de respuesta HTTP 500, 503 o 429 en lugar de 200 a las solicitudes de rastreo. La infraestructura de rastreo de Google reduce la frecuencia de rastreo de tu sitio cuando detecta un número significativo de URLs con códigos de estado de respuesta HTTP 500, 503 o 429; por ejemplo, si has inhabilitado tu sitio web.
La reducción de la frecuencia de rastreo afecta a todo el nombre de host de tu sitio (por ejemplo, subdomain.example.com), tanto al rastreo de las URLs que devuelven errores como al de las URLs que devuelven contenido. Una vez que se haya reducido el número de estos errores, la frecuencia de rastreo empezará a aumentar automáticamente.
Solicitudes excepcionales para reducir la frecuencia de rastreo
Si no es posible enviar errores a los rastreadores de Google en tu infraestructura, presenta una solicitud especial para informar de un problema con una frecuencia de rastreo inusualmente alta, indicando la frecuencia óptima para tu sitio. No puedes solicitar un aumento de la frecuencia de rastreo, y la solicitud puede tardar varios días en evaluarse y aprobarse.
[null,null,["Última actualización: 2025-09-01 (UTC)."],[[["\u003cp\u003eGoogle automatically adjusts crawl rate to avoid overloading your server, but you can reduce it further if needed.\u003c/p\u003e\n"],["\u003cp\u003eTemporarily reducing crawl rate can be achieved by returning 500, 503, or 429 HTTP response codes, but this impacts content freshness and discovery.\u003c/p\u003e\n"],["\u003cp\u003eFor longer-term crawl rate reduction, file a special request with Google; however, increasing the rate isn't possible.\u003c/p\u003e\n"],["\u003cp\u003eBefore reducing crawl rate, consider optimizing your website structure for better crawling efficiency as this might resolve the issue.\u003c/p\u003e\n"],["\u003cp\u003eExtended use of error codes to control crawling may lead to URLs being dropped from Google's index, so it's crucial to use this method cautiously.\u003c/p\u003e\n"]]],["Google's crawlers may need to be slowed if they overload a site. Common causes for increased crawling include inefficient site structure, like faceted navigation. For urgent reductions, return `500`, `503`, or `429` HTTP status codes to crawler requests; this will lower the crawl rate, but can negatively affect site indexing if done for too long. Alternatively, if returning errors isn't viable, submit a special request specifying an optimal crawl rate. Note: reducing the crawl rate will result in slower updates of existing pages.\n"],null,["# Reduce Google Crawl Rate | Google Search Central\n\nReduce the Google crawl rate\n============================\n\n\nGoogle's crawler infrastructure has sophisticated algorithms to determine the optimal crawl rate\nfor a site. Our goal is to crawl as many pages from your site as we can on each visit without\noverwhelming your server. In some cases, Google's crawling of your site might be causing a\ncritical load on your infrastructure, or cause unwanted costs during an outage. To alleviate this,\nyou may decide to reduce the number of requests made by Google's crawlers.\n\nUnderstand the cause of the sharp increase in crawling\n------------------------------------------------------\n\n\nSharp increase in crawling may be caused by inefficiencies in your site's structure or issues with\nyour site otherwise. Based on the reports we've received in the past, the most common causes are:\n\n- Inefficient configuration of URLs on the site, which is typically casued by a specific functionality of the site:\n - Faceted navigation or other sorting and filtering functionality of the site\n - A calendar with a lot of URLs for specific dates\n- [A Dynamic Search Ad target](/search/docs/crawling-indexing/large-site-managing-crawl-budget#adsbot)\n\n\nWe strongly recommend that you check with your hosting company and look at recent access logs of\nyour server to understand the source of the traffic, and see if it fits in the aformentioned\ncommon causes of the sharp increase in crawling. Then, check our guides about\n[managing crawling of faceted navigation URLs](/search/docs/crawling-indexing/crawling-managing-faceted-navigation)\nand\n[optimizing crawling efficiency](/search/docs/crawling-indexing/large-site-managing-crawl-budget#improve_crawl_efficiency).\n\nUrgently reduce crawler traffic (for emergencies)\n-------------------------------------------------\n\n| **Warning**: When considering reducing the Google's crawl rate, keep in mind that this will have broad effects. For Search, Googlebot will discover fewer new pages, and existing pages will be refreshed less frequently (for example, prices and product availability may take longer to be reflected in Search), and removed pages may stay in the index longer. For Google Ads, your campaigns may be cancelled or paused, and your ads may not serve.\n\n\nIf you need to urgently reduce the crawl rate for short period of time (for example, a couple\nof hours, or 1-2 days), then return `500`, `503`, or `429` HTTP\nresponse status code instead of `200` to the crawl requests. Google's crawling\ninfrastructure reduces your site's crawling rate when it encounters a significant number of URLs\nwith `500`, `503`, or `429` HTTP response status codes (for\nexample, if you\n[disabled your website](/search/docs/crawling-indexing/pause-online-business)).\nThe reduced crawl rate affects the whole hostname of your site (for example,\n`subdomain.example.com`), both the crawling of the URLs that return errors, as well as\nthe URLs that return content. Once the number of these errors is reduced, the crawl rate will\nautomatically start increasing again.\n| **Warning**: We don't recommend that you do this for a long period of time (meaning, longer than 1-2 days) as it may have a negative effect on how your site appears in Google products. For example, in case of Search, if Googlebot observes these status codes on the same URL for multiple days, the URL may be dropped from Google's index.\n\nExceptional requests to reduce crawl rate\n-----------------------------------------\n\n\nIf serving errors to Google's crawlers is not feasible on your infrastructure,\n[file a special request](https://search.google.com/search-console/googlebot-report)\nto report a problem with unusually high crawl rate, mentioning the optimal rate for your site in\nyour request. You cannot request an increase in crawl rate, and it may take several days for the\nrequest to be evaluated and fulfilled."]]
