Encuentra y valida todos los sitemaps de cualquier sitio web al instante. Descubre sitemaps ocultos, verifica validez y extrae recuentos totales de URLs.
Ingresa cualquier URL de sitio web para descubrir todos los sitemaps disponibles. La herramienta verificará robots.txt y escaneará ubicaciones comunes de sitemaps.
Ingresa el dominio principal (ej., example.com). La herramienta verificará sitemaps automáticamente.
El Buscador y Verificador de Sitemaps es una herramienta poderosa que descubre automáticamente todos los sitemaps en cualquier sitio web. Realiza análisis exhaustivos verificando el archivo robots.txt y probando ubicaciones comunes.
A diferencia de la búsqueda manual, esta herramienta automatiza todo el proceso de descubrimiento. Verifica más de 20 ubicaciones comunes incluyendo /sitemap.xml, /wp-sitemap.xml para WordPress, y sitemaps específicos de contenido.
Para cada sitemap encontrado, la herramienta valida su accesibilidad, verifica códigos de estado HTTP, extrae metadatos y cuenta el número total de URLs.
/sitemap.xml/sitemap_index.xml/sitemap-index.xml/sitemaps.xml/post-sitemap.xml/page-sitemap.xml/product-sitemap.xml/category-sitemap.xml/wp-sitemap.xml/blog/sitemap.xml/sitemap/sitemap.xml/news-sitemap.xml/video-sitemap.xml/image-sitemap.xmlreferencias robots.txtMost crawlers look at /sitemap.xml and a short list of common variants. A sitemap at an unusual path, such as /wp-sitemap-posts-post-1.xml or a CDN subdomain, is invisible unless something points to it. The fix is to declare it in robots.txt, which is the one place every crawler checks.
A Sitemap: line in robots.txt is how you tell crawlers where to look without relying on guesswork. It costs one line, works for every search engine, and is the single most common thing missing when a site has a sitemap that nothing can find.
Large sites split their sitemap into an index file that links to child sitemaps. If a tool reports one sitemap containing almost no URLs, you are probably looking at the index rather than the children. Open it and follow the nested entries.
A sitemap that answers with 404, 403 or 500 does not exist as far as any crawler is concerned. Firewalls and bot protection are frequent culprits, and they often block automated tools while still serving the file to you in a browser.
Disallowing the directory a sitemap lives in prevents crawlers from fetching it, even though the URL resolves. Check that no Disallow rule covers the sitemap path itself.
Common on hand-built sites and on CMS installs where the feature was never switched on. A sitemap is not mandatory and a small, well-linked site can be crawled without one, but it is cheap insurance on anything larger than a few dozen pages.
/sitemap.xml at the root of the domain is the convention, and there is no benefit to using anything else. What matters more is that robots.txt points to it and that Search Console knows about it.
It is not mandatory, but it is the most reliable way to be discovered. Add a line reading Sitemap: https://example.com/sitemap.xml and every crawler that reads robots.txt will find it.
No, and this is the most common misunderstanding about sitemaps. A sitemap helps Google discover URLs. Whether it indexes them is a separate judgement based on the quality of each page. A page can sit in your sitemap for months and never be indexed.
50,000 URLs, or 50MB uncompressed, whichever comes first. Beyond that you split into multiple files and list them in a sitemap index. Most CMS plugins handle the split automatically.
No. A sitemap should list canonical URLs that return 200 and that you want indexed. Including noindex pages, redirects or 404s sends conflicting signals and wastes crawl attention on URLs you have already told Google to ignore.
Submit it in Search Console, or reference it in robots.txt and let Google recrawl. The old sitemap ping endpoint was retired by Google in 2024, so tools and plugins that still ping it are doing nothing useful.