,

[Fixed] Indexed, Not Submitted In Sitemap In Google Search Console

Google Search Console is a great tool for webmasters to monitor and enhance their search rankings on Google. However, it behaves weirdly at times and reports some errors on our websites even when they do not actually exist. Two of those most common errors are the mobile usability error and the “Indexed, Not Submitted In Sitemap” error.

In this guide, we are going to learn how to resolve the “Indexed, Not Submitted In Sitemap” issue which Google Search Console shows us, every time we try to submit a new article to search console.

The message looks like this-

Google Search Console Indexed, Not submitted in sitemap

Tired of slow indexing of your blog posts by Google? Check Out: How To Get Your Blog Posts Indexed By Google Instantly [2 Minutes]




What Does “Indexed, Not Submitted In Sitemap” Exactly Mean?

This means that after Google bot crawled the page after receiving your request, it realised that it hasn’t seen that URL ever before in your sitemap. But that does not necessarily mean the URL was not updated in your sitemap at the time of checking.

If you use Google’s Blogger to host your website, then you can be 100% sure that the URL gets added into your sitemap as soon as you publish the post. This is because Blogger automatically generates the sitemap, which is available at (your domain name).com/sitemap.xml.

If you use WordPress or any other self-hosted platform, then you have two options, either you can manually create a sitemap for your site and update it each time you publish a new post or take the help of automatic SEO plugins such as Yoast SEO or Rank Math to create the sitemap and keep it updated automatically.

So as we can see, in both cases, the URL is properly being added to the Sitemap. But even then, Google shows us that error message.

Now let’s learn, why does Google show that message.

Why Does Google Show That Message Even When The URL Is Present In The Sitemap?

This is because Google doesn’t crawl your sitemap as soon as it is updated. Thus, when it finds a new URL related to your site, it tries to find it in the older version of your sitemap that’s stored in its memory, and thus, fails to find it.

Now, this entirely depends on the crawling frequency that Google has set for your site. The higher the crawling frequency, the sooner your sitemap is expected to get crawled by Google.

You can learn how Google sets the crawling frequency for domains, from here: https://www.searchenginejournal.com/google-crawl-indexing/274141/ (opens in a new tab)




Now let’s learn, how to fix this issue.

How To Fix “Indexed, Not Submitted In Sitemap” In Google Search Console?

After publishing a page or a post, first, we need to make sure that it gets successfully added to the sitemap first. For that, we need to visit our sitemap and search for the URL of the article that we just published.

If you do not know what’s the URL of your sitemap, you may visit your SEO plugin’s website and look it up or ask your site’s developer about it.

In this example, we’re gonna work with the URL: https://www.techrbun.com/fast-google-post-indexing/, which is the URL of a post on this site.

So first, we head up to our sitemap.

Now by performing a simple search (CTRL+F), we can confirm that the URL is present in the sitemap.

xml sitemap

Now we need to refresh the sitemap in Google’s memory. To do that, simply go to Google Search Console -> Sitemaps

You will see that the sitemap is already there but the “last read” date is old. So, simply submit the same sitemap again.

old sitemap in Google's memory

After hitting the SUBMIT button, you will see that the sitemap’s “last read” date has changed to the current date. Which means that the latest updated sitemap is now stored in Google’s memory.

updated sitemap in Google's memory.

Note: Even though the sitemap in Google Search Console’s memory should contain the URL to your latest post now, still it is recommended that you wait 10 minutes before proceeding to the next step. This is because the GSC (Google Search Console) sometimes is under development, which causes a delay in its processing.

Now, we will use the URL inspection tool again, to see what result it gives.

indexed, not submitted in sitemap Issue Fixed In GSC (Google Search Console)

As you can see, the the “Indexed, Not Submitted In Sitemap” issue in Google Search Console (GSC) has been fixed successfully.




Also Check Out: 8 Dangerous Blogging Mistakes That Beginners Must Avoid [Motivation]

If this article has helped you, don’t forget to share it on your favourite social media sites and online forums so that it can reach all the people who are suffering from the same problem, and resolve their issue with the help of this guide.

If you have any questions, feel free to comment down below. I’ll help you out!

Have a great day ahead!

Frequently Asked Questions

Will My Site Rank At The Top After Solving The Issue?

Nope. Ranking and indexing are two different things. Indexing only submits your content to Google. Google decides through its secret algorithm to decide which rank your post belongs to in the SERP (Search Engine Results Page).

Why Does It Show “Sitemaps: N\A”?

It means that the post’s/page’s URL wasn’t found in your sitemap by Google. It has been solved in this article.

What Does “Referring Page: None Detected” Mean?

It means that no page is being redirected to the current page through a permanent (301) or temporary (302) redirection.

About Anirban Roy

Anirban Roy is the founder of TechRBun. He is a Computer Geek. He likes to share his knowledge about PC, Mobiles and Blogging. He studies in class XII and when he is not studying, he can always be found tweaking his PC or surfing the web on his mobile phone. He loves music and literature too!

5 thoughts on “[Fixed] Indexed, Not Submitted In Sitemap In Google Search Console”

  1. Bhai, I saw your website. You are a legend . You just solved too many problems in less time.
    THANK YOU SO MUCH ❤️

    Reply
    • Then most probably GSC was going through an update while you were trying to do it. These days it’s going through a lot of updates. However, there can be some other issue with your site as well. You can provide the link to your site and I will check it for you. 🙂

      Reply
  2. Thank you very much! I was really struggling before I found your post. I am a newbie at all of this, but followed your steps and got things working again.
    I had to cleared the cache in WP Rocket. Then I did a test cache in the Cloudflare plugin and got a message stating it wasn’t caching. I disabled WP Rocket temporarily. Then ran the test cache in Cloudflare again. This time there were no errors. Then I enabled WP Rocket. All I had to do after that was refresh the sitemaps in the console.

    Reply

Leave a Comment