Sitemap Submitted Successfully but Pages St...

Direct Answer

A sitemap can say “submitted successfully” while Google still leaves pages undiscovered because the sitemap is only a hint, not a crawl command. In my experience, the first things to check are robots.txt, weak internal links, and canonical tags that point Google away from the page you want indexed. If those three areas are clean, then check page quality, redirects, noindex tags, and server response issues.

Explanation

This problem usually starts with a confusing Google Search Console message. You submit your XML sitemap, Google accepts it, and the status looks healthy. Then you open the Pages report and see URLs listed under Crawled - currently not indexed, Discovered - currently not indexed, or Excluded by ‘noindex’ tag.

The sitemap is doing one job. It is telling Google, “These URLs exist, and here is how often they change.” It is not forcing Google to crawl them, index them, or rank them. Google Search Central explains that sitemaps help Google discover URLs, but they do not guarantee crawling or indexing. You can read more in Google’s official sitemap documentation: Sitemaps overview.

The page may stay undiscovered for a few common reasons. Google may find the URL in the sitemap, then hit robots.txt and back away. The page may have no internal links from other pages, so Google sees it as isolated. A canonical tag may point to another URL, telling Google that this page is not the main version.

I’ve seen this happen often with new blog posts, product pages, category pages, and landing pages. The sitemap looks fine, but the page has no strong path from the homepage, no links from related posts, or a canonical tag copied from a template. That is why I always treat sitemap status as the starting point, not the finish line.

When This Fix Works

This fix works when Google can technically access the page but does not crawl it because your site is sending mixed signals. For example, your sitemap includes /services/web-design/, but the robots.txt file blocks /services/. Google sees the URL, checks the rules, and excludes it from crawling.

It also works when pages are missing from the internal link structure. A new page in your sitemap but not linked from your homepage, menu, footer, sitemap page, or related posts can sit in a weak discovery state. In my experience, adding 2 to 4 contextual links from relevant pages often helps Google understand that the page is part of the site, not an orphan.

This approach also works when canonical tags are wrong. A common WordPress issue is a page canonical pointing to the homepage, a category page, or the wrong language version. If the canonical points away from the URL you want indexed, Google may respect that signal and ignore the page in the sitemap.

When This Does NOT Work

This does not work if the page is thin, duplicated, auto-generated, or not useful enough for Google to index. A sitemap cannot make a low-value page worth crawling. If the page has 80 words copied from another page, Google may ignore it even when all technical signals are clean.

It also does not work if the URL returns a 404, 410, 500 error, or a soft 404. In that case, the sitemap is pointing Google to a page that does not properly exist. Fix the page status first.

This fix also will not solve ranking problems. A page can be indexed and still rank poorly because the content is weak, the search intent is wrong, or stronger pages already cover the topic. For that, you need content and SEO work, not just sitemap repair.

If your site is brand new, it may simply need time. Google often crawls new sites slowly at first. I usually give a new site 2 to 6 weeks before judging crawl behavior, as long as the technical setup is correct.

Step-by-Step Instructions

1. Open Google Search Console and select your website property on the left side of the screen.

2. Click Sitemaps under the Indexing section. Check the submitted sitemap URL, such as https://example.com/sitemap_index.xml. If the sitemap URL is wrong, remove it and submit the correct one.

3. Open the Pages report under Indexing. Look for the affected URL in Discovered - currently not indexed, Crawled - currently not indexed, or Not found (404). If the page is not listed at all, paste the exact URL into the top inspection field and press Enter.

4. Run the URL Inspection test for the affected page. Check whether Google says the URL is available to Google. If it says blocked by robots.txt, move to the robots.txt check.

5. Test robots.txt with Google’s official tool. Go to the robots.txt testing tool and enter your URL. If the tool says blocked, open your robots.txt file at https://example.com/robots.txt.

6. Remove any rule that blocks the page or section you want indexed. For example, change Disallow: /blog/ to a narrower rule, or remove it if you want all blog posts crawled. Do not block pages that you want Google to index.

7. Check the live page for a noindex tag. In your browser, open the page, right-click, and select View Page Source. Search for noindex. If you see <meta name="robots" content="noindex">, remove it from the page settings, SEO plugin, or template.

8. Check the canonical tag in the page source. Search for canonical. The URL inside the tag should match the page you want indexed. For example, if the page is https://example.com/services/web-design/, the canonical should point to that same URL unless you have a clear reason to use another URL.

9. Fix wrong canonicals in your CMS. In WordPress, check the SEO plugin settings for the affected post or page. In Shopify, check theme SEO settings. In custom sites, ask your developer to update the canonical template for that page type.

10. Add internal links from strong pages. Put one link on the homepage, one from a related blog post, one from a service page, and one from a relevant category page. Use natural anchor text, such as “web design services” or “local SEO checklist.”

11. Add the page to your HTML sitemap if you use one. This is different from an XML sitemap. An HTML sitemap is a visible page that helps visitors and search engines move through important sections.

12. Update your XML sitemap after fixing the page. If you use WordPress, use your SEO plugin’s sitemap refresh option. If your sitemap is static, regenerate it and upload it again.

13. Resubmit the sitemap in Google Search Console. Go to Sitemaps, enter the sitemap URL again, and click Submit. This tells Google to check the latest version.

14. Use Request Indexing only after the page is clean. In the URL Inspection result, click Request Indexing. I use this after robots.txt, noindex, canonical, and internal link fixes are done.

15. Wait and recheck the URL after 7 to 14 days. Open URL Inspection again. If Google still lists the page as not indexed, check content quality, redirects, server logs, and duplicate pages.

Alternatives / Related Fixes

1. Fix weak internal linking first. If a page has no links from other pages, Google may treat it as less important. In my experience, orphan pages are one of the most common reasons a sitemap looks healthy but pages stay undiscovered. Add links from pages that already get crawled often.

2. Correct duplicate or near-duplicate pages. If you have /service, /services, and /services/service, Google may choose one and ignore the others. Use one clean URL, redirect the duplicates, and update internal links.

3. Review crawl budget and site size. Small sites usually do not have crawl budget problems. Large sites with thousands of low-value URLs can waste crawl activity on filter pages, tag pages, or old archives. Block or noindex low-value sections only after you understand the impact.

4. Check server responses and redirects. A page that redirects from HTTP to HTTPS, non-www to www, or old slug to new slug can confuse your internal link map. Use a crawler or server log check to confirm the final URL returns 200 OK.

5. Reset or rebuild the sitemap as a last resort. If your sitemap plugin is corrupt, showing deleted URLs, or mixing old URLs with new ones, rebuild the sitemap and resubmit it. I do this after checking robots.txt, internal links, canonicals, noindex tags, and redirects, because a sitemap reset alone rarely fixes discovery issues.

For more setup help, see the Website Setup & Indexing guide which covers sitemaps, WordPress configuration, 404 fixes, and canonical tags.

Decision Summary

If Google says the page is blocked by robots.txt, fix robots.txt before touching the sitemap.

If the page has no internal links, add links from relevant pages that Google already crawls.

If the canonical tag points to another URL, correct the canonical to the page you want indexed.

If the page has a noindex tag, remove the noindex rule and then request indexing.

If the page returns 404, 410, 500, or soft 404, fix the page status before resubmitting the sitemap.

If the page is thin or duplicated, improve the content or merge it with a stronger page instead of forcing indexing.

FAQ

Q: Why does Google Search Console say my sitemap was submitted successfully, but pages are still not indexed?

A: Because sitemap submission only means Google received the file. It does not mean Google will crawl or index every URL inside it. Google may skip pages due to robots.txt, noindex tags, weak internal links, canonical tags, redirects, server errors, or low content value.

Q: Should I resubmit my sitemap every day until Google indexes my pages?

A: No. Repeated resubmission usually does not help if the page has a technical or quality issue. Submit the sitemap after you fix the problem, then wait 7 to 14 days. If nothing changes, inspect the URL and check robots.txt, canonicals, internal links, and page quality.

Q: Can robots.txt block a page even if it is in the sitemap?

A: Yes. Google can discover a URL from the sitemap, then check robots.txt and decide not to crawl it. If you want the page crawled, remove the blocking rule for that URL or section. You can test this with Google’s robots.txt testing tool.

Q: What is the difference between “Discovered - currently not indexed” and “Crawled - currently not indexed”?

A: “Discovered - currently not indexed” means Google found the URL but has not crawled it yet. “Crawled - currently not indexed” means Google crawled the page but chose not to index it. The first often points to crawl priority, internal links, or sitemap timing. The second often points to content quality, duplication, or indexing rules.

Q: What should I check first when sitemap pages stay undiscovered?

A: Check the URL in Google Search Console’s URL Inspection tool first. Then check robots.txt, noindex tags, canonical tags, redirects, and internal links. In my experience, those five checks solve most sitemap discovery problems before you need to rebuild the sitemap.

Related Guides

• — Browse all guides in this category
• GA4 Shows Realtime Users but Standard Repor… — If GA4 Realtime shows users but standard reports are blank, the tag is probably firing, but GA4 has
• GA4 Traffic Looks Wrong After Website Setup? Check Consent M — If GA4 traffic looks wrong after website setup, check three things first: Consent Mode, GA4 data fil
• Understanding Sitemap & Indexing: How to Fix Crawling Issues — Direct Answer: Understanding Sitemap & Indexing is crucial for fixing crawling issues and boosting y