Based on this, we decided to work with different

rigite2542@artg

This information must be provided for each individual URL of the website. It will look like that: Sitemaps in multiple languages Sitemaps can be stored in several languages. As you can see, the whole thing gets very extensive very quickly. Therefore, be sure to check your sitemap for errors before submitting it to Google. You can find more information about the hreflang attribute directly on Google's support page . Practical example 1: Incorrect URLs in the sitemap One of my customers has an outdated sitemap that contains URLs that shouldn't end up in the index.


These included a 404 error page, a 403 error page, and automatically generated URLs: Sitemap Special Data excerpt 404 and 403 error pages These errors crept into a customer's sitemap. During an SEO audit, we found these errors in the sitemap and recommended that the customer remove these URLs from the sitemap. The sitemaps are stored in the Google Search Console and can be read successfully: Redesigned sitemaps in Google Search Console The revised sitemaps were stored and read out in the Google Search Console. Practical example 2: Many products and only one sitemap? A customer of mine in the e-commerce sector has a lot of products from different categories.




If you add all the products together, you get over 1 million products. As you already know, over 1 million URLs don't fit into a single sitemap. This is what we did together with the customer: We thought about which products have priority and what similarities the respective product groups have. sitemaps: We divided the products into several groups and included the most important ones in the sitemap. This way, the most relevant URLs are present in the respective sitemaps and can be submitted. In addition, the customer has a current overview of the most important products.