Indexed, not submitted in sitemap

There is a simple solution if you are having trouble with pages not being indexed even though they are on your sitemap. We have recently received questions about sitemap-related issues and understand the frustration. If you're reading this, you may be experiencing problems with pages that are "indexed, not submitted on the sitemap." The good news is that there is a straightforward way to fix this problem and get your pages indexed properly.

This issue is of utmost importance and can be pretty frustrating. However, it's interesting to note that it is helping you instead of fixing the problem with the website's architecture. Allow us to explain the cause of the issue. It simply means that Google bots found the website page, but they could not locate it on the sitemap because the URLs are different from those defined on the sitemaps. To resolve this, you may require the assistance of a developer.

Although you may have heard otherwise, duplicate content is the primary cause of ranking issues. This is due to an error in your coverage where there is duplicate content without a user-selected canonical link.

Let's review what Google is doing now and how the error can be resolved.

Sitemaps, How to Fix

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

The problem might be easy, and a developer might need to fix it. 

The easy problem might be:

When Google bots crawl your website, they might use a different URL variant, such as https://webnetpk.com, instead of the one in your sitemap, like https://www.webnetpk.com. This can cause issues, but the solution is simple: set up 301 redirects for your preferred URL (with or without the "www"). 

However, if the problem persists even after setting up the redirects, it might be more complicated and require the assistance of a developer to fix the issue.

What we have done is customizable and will not be available with the sitemaps free plugin. Still, 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, which needs attention because it may cause your website ranking to vary around on SERPs. 

While doing SEO, it's crucial to implement best practices. Most website-building platforms utilize these practices, often reflected in the sitemap upon installation.

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

It's important to note that there is no "/" at the end of the URL, which is causing the error message to appear.

After submitting the sitemap, we saw an instant change one week later.



We have resolved all of your significant issues and hope you can now address and fix any future problems on your own. However, please do not hesitate to contact us if you require assistance. 

Our primary objective is to understand the most common issues SEO companies face. By continuously improving our CMS solutions, we can identify and address these issues as they arise. 

If you have developed a custom website on a custom CMS, your issue may be more complex depending on the developer's experience level. Developers may not always be aware of SEO issues when building applications or websites, so it is vital to communicate any concerns. 

Many of you have contacted us regarding the same issue, which we have found to be related to sitemaps. After analyzing your queries, we determined that the problem lies with the SEO plugin. To resolve this issue in the plugin, you must modify it, which will require a developer's expertise. The most common queries we have received are related to WordPress plugins. 

The solution is simple. By removing the "/" from the slug that does not have an additional URL to index, you can prevent Google from treating it as a new URL. Please try this solution and share your feedback with others. We are here to assist you in any way we can.