📌 Why the indexed count stays at zero
A healthy sitemap and a clean robots.txt only tell Google which pages exist and that crawling is allowed. They do not guarantee that pages are indexed. The indexed number in Google Search Console can stay at zero while Google is still discovering URLs, or when pages are crawled but excluded.
Search Atlas cannot force Google to index a site. You can confirm the setup, resubmit the sitemap, and request indexing for important URLs. Google decides what to crawl and when.
✅ Check the basics first
- Confirm the sitemap URL returns a valid XML file and lists the live page URLs you expect, including https and the correct domain.
- Open robots.txt and confirm it does not block those URLs or the sitemap itself.
- Spot-check a few listed URLs. Each should return a normal page, not a redirect loop, login wall, or error.
- On those pages, confirm there is no noindex tag and that the canonical URL matches the URL in the sitemap.
- In Search Atlas, open the correct site project and confirm Google Search Console is connected to the same property that owns the sitemap. A domain property and a URL-prefix property can show different data.
🔄 Resubmit the sitemap in Search Console
- In Google Search Console, select the property that matches the live site.
- Open Sitemaps in the left menu.
- If the sitemap is already listed, note the status. Success with zero indexed pages is common on new or recently changed sites.
- Enter the sitemap path, such as sitemap.xml, in the add field and choose Submit. Submitting again asks Google to read the file again. It is not an instant recrawl of every URL.
- Return to Search Atlas and refresh or re-sync Search Console data for that project so the platform shows the latest status.
🚀 Request indexing for key pages
- In Google Search Console, open URL inspection at the top of the page.
- Paste one important URL from the sitemap, such as the homepage or a priority service page, and press Enter.
- Review the result. Look for blocked by robots.txt, excluded by noindex, duplicate or alternate page, or crawled but not indexed.
- If the URL is eligible and the Request indexing button is available, select it. Use this for a small set of priority URLs, not every URL in the sitemap.
- Repeat for a few representative URLs. If those are excluded, fix the reported reason before requesting more.
🛠️ Use Search Atlas to find blockers
- Run or open the latest Site Audit for the project and filter for indexability issues, blocked pages, canonical conflicts, and redirect or status-code problems.
- Compare audit URLs with the sitemap. Pages missing from the audit, or listed with errors, will not move the indexed count.
- If OTTO recommendations are waiting, review indexation and technical items and apply only the fixes you intend to publish.
- After fixes go live, resubmit the sitemap and request indexing again for the corrected URLs.
⏳ What to expect after a recrawl request
Google may take days or longer to recrawl and update the indexed count. Zero does not always mean the sitemap was rejected. Check the Pages or indexing report for discovered, crawled, and excluded URLs. A rising discovered count with a low indexed count usually means quality, duplication, or canonical selection, not a broken sitemap.
If the sitemap status is an error, the property is wrong, or URL inspection shows a sitewide block after you have corrected the pages, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.