Indexed, not submitted in sitemap

We have been taunted with the sitemap recently, and we could not figure out what was causing issues with "indexed, not submitted on the sitemap." There is a simple way of fixing it when you feel that your page is on a sitemap and google is not considering it on the sitemap submitted.

This problem is very crucial and irritating. Guess what? It is helping you instead of solving the issue with the website architecture. We will explain the cause below, but in other words, when google bots are crawling, they are finding different URLs instead of the ones defined on the sitemaps. To fix this, you might need a developer to help.

However, you might have heard that this does not affect your ranking. Still, we feel this is the primary cause of the ranking because the webmaster brings out another error on your coverage: Duplicate without user-selected canonical.

Let us go through what google is doing now and how the error can resolve.

Sitemaps, How to Fix

Fixing indexed, not submitted in the sitemap, must consider many things while fixing this issue. Before fixing this issue, you need to understand that the crawler is eventually crawling your website, but the URL is not found on the sitemap. 

The problem can be an easy and tough one that might need a developer to fix the issue. 

The easy problem might be:

When the google bots are crawling your website, it might be crawling with one variant like https://webnetpk.com instead of https://www..webnetpk.com, which your sitemap might have all URLs based on that. The simple solution is to put 301 redirects on one URL you prefer; www or without www will resolve the issue.

The problem might be complicated if you have everything set up correctly. You might need a developer to fix the issue. 

What we have done is customizable and will not be available with sitemaps free plugin, but you can eventually get that help from a web developer to make changes accordingly. 

We have made the crawler define our website architecture with "/" at the end of the root URL to make it easy for the crawler to understand that the URL with "/" at the end may have more URLs. It is not essential in the case of fixing the issue if you are looking at our sitemaps, but we believe helping the crawler can give you some extra points. :)  

Now let us come to the central issue of fixing the complex problem you might have but needs attention because it may cause your website ranking to vary around on SERPs. 

Good practice needs to be implemented while doing SEO, and most of the platform for building your website uses good practice. You might see something like this on your sitemap when you install it.

https://webnetpk.com/ 
https://webnetpk.com/slug/
https://webnetpk.com/slug1/

Now when google is crawling, it is crawling your URL like this

https://webnetpk.com
https://webnetpk.com/slug
https://webnetpk.com/slug2

Notice that there is no "/" at the end, which is one reason why you are getting this error.

Below are the results from doing this, which gave an instant change one week after submitting the sitemap.



We have solved all your significant issues, and hopefully, you will have a great way of doing and fixing all your problems by yourself. You could contact us to solve this issue for you.

Our central objective is to understand the main problem that many SEO companies have faced. We can identify them while implementing another module because we continuously improve our CMS SOLUTIONS.

The queries on the Search Console were updated. 

Remember, if you have developed your website custom on custom cms, please note that your issue can be different and more complicated depending on how experienced as your developer. Remember, developers, are not keen in SEO issues while developing the applications or websites for you. So please, you need to tell them. 

Guys, you are connecting with us regarding this same issue, and you need to understand that the same problem has been on your sitemaps. After analyzing everyone's query, we felt you are having trouble with the SEO plugin. Let me tell you, to resolve this issue in the plugin, you would need to modify it and would require a developer to solve this sitemap issue in WordPress or any other. Major platform. The top queries we have faced are from WordPress plugins. 

It is straightforward. If you remove "/" from the slug, which has no additional URL to solve the indexed, not submitted in the sitemap as google takes the extra "/" in the URL as a new one. Please get this done, and please don't forget to comment and let others know it works. We are working to help you all.