Sitemap not found
What it is
Asky could not load a sitemap. It appears in two forms: No sitemap found, filed on your robots.txt, when no sitemap could be found for the site at all, and Missing sitemap, filed on one sitemap URL that answers 404, 410 or another client error. An XML sitemap is the file that lists the pages you want search engines and other crawlers to find.
Why it matters
Without a sitemap, crawlers find pages only by following links, so new, deep or poorly linked pages are found late or not at all. Google recommends one for large sites and new sites with few links, and Bing calls sitemaps foundational to URL coverage for search and Copilot. Asky also finds your pages through your sitemap, so with none it has no pages to crawl, audit or monitor.
How Asky checks it
Asky judges this for each of your domains, daily and at each audit. A domain has a sitemap when one listed in robots.txt or added in Asky loads on it, or its pages are listed in any sitemap. Otherwise Asky tries /sitemap.xml, /sitemap_index.xml and /sitemap1.xml on it and its www twin. No sitemap found is filed on its robots.txt only when each answer is a 404 or 410; a subdomain without a sitemap is not reported. A domain redirecting elsewhere is skipped. Missing sitemap is filed on a listed sitemap, or an index’s child, answering a 4xx other than 401, 403 and 429. Both clear once a sitemap loads.
Reported as a warning with medium severity.
How to fix it
- Open the sitemap URL in the issue’s details. For No sitemap found, start with
https://example.com/sitemap.xml. - If the site has no sitemap, turn one on. Webflow generates one in the site’s SEO settings, WordPress serves
/wp-sitemap.xmlor your SEO plugin’s index, and a headless site, such as one built on Sanity, generates it in the front-end app. - If your sitemap lives at another path, add a
Sitemap:line with its full URL to robots.txt, or add it in Asky. Asky only tries the three standard paths. - For Missing sitemap, update the robots.txt line or the URL in Asky to the working sitemap. While a listed URL exists, Asky does not look anywhere else. For a child of an index, fix the index entry or restore the file.
- Check the URL answers 200 with XML that starts a
<urlset>or<sitemapindex>. A web page served there is reported as invalid XML instead.
Example
The robots.txt on https://example.com still points at a sitemap from the previous platform, which now answers 404:
# Before
Sitemap: https://example.com/sitemap.xml
# After: the address the current sitemap answers on
Sitemap: https://example.com/sitemap_index.xml