Small sites (usually with few development resources) and where we don’t see an obvious structural problem, we at IKAUE don’t usually ask for sitemaps.xml files. SEO should always play along the lines of profitability and without a doubt spending development time on something that contributes absolutely nothing makes no sense.
The solution is not to upload
A static sitemap.xml file that you create yourself with any program… What’s the point? Are you going to use a smaller crawler to help one that is much more powerful than the one you use? What do you expect to find that Google can’t find on its own?
On the downside
We also have all those people who, out of ignorance, upload a sitemap without having much idea of cause indexing problems that didn’t exist before. This happens more often than you might think in the sector. I’ll give you some examples of problems fantuan phone number that can be caus by poorly creat sitemaps.xml.
To start with, if you don’t do it right
you can give it a lot of URLs that you don’t really care about indexing in SEO terms. This happens when you generate them automatically. You tell it to index seo and, on top of that corporate pages that weren’t index before and things like that.
Also, when they are generat from
Development without anyone giving you instructions on what they should contain, you can find things like URLs from the user’s private environment or thank you pages in the sitemap… You don’t want to show that to Google, do you?
Another classic, similar to the first, is when we trust our CMS or a plugin that generates everything. In this case, WordPress, Drupal and others are experts yeezys shoes at indexing junk content. Taxonomies that you had not provid URLs for on your page, Author Pages, Monthly Archives, or even worse, daily ones… Not everything adds up. On the contrary, all of this subtracts.