No XML sitemap found
sitemap_missingShort answer
No sitemap returned 200 for this site: Glimana looked at the Sitemap: lines in robots.txt, /sitemap.xml, /sitemap_index.xml and the sitemaps registered in Search Console. This issue affects whether Google can find the page or add it to its index. Create sitemap.xml, declare it in robots.txt with a Sitemap: line and submit it in Search Console.
Why it matters
A sitemap is how you tell search engines which URLs exist and when they changed; without it, discovery depends entirely on links. For small, well-linked sites the impact is small; for large sites, new content and pages deep in the structure, the sitemap is the main discovery path. Glimana also uses the sitemap to seed the crawl and to report pages that are in the sitemap but not indexed.
How Glimana detects it
The rule fires when the site has no sitemap record with status 200.
How to fix it
WordPress core serves /wp-sitemap.xml since 5.5; SEO plugins replace it with /sitemap_index.xml (Yoast) or /sitemap_index.xml (Rank Math). Make sure the feature is enabled in the plugin, then add Sitemap: https://example.com/sitemap_index.xml to robots.txt (the plugin usually does this) and submit the URL in Search Console › Sitemaps.
Shopify generates /sitemap.xml automatically for every store. If it is missing, the store is password-protected or the domain is not the primary one. Submit https://yourdomain/sitemap.xml in Search Console.
Generate the sitemap from the database on a schedule or at build time (Laravel spatie/laravel-sitemap, Next.js sitemap.ts, Django sitemaps framework). Keep each file under 50,000 URLs / 50 MB and use a sitemap index for more. Add <lastmod> with real modification dates; Google uses it only when it is consistently accurate.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-10-01</lastmod>
</url>
</urlset>
How the fix is verified
Re-crawl; the task closes when a sitemap returns 200.