Sitemap.xml Example Download
Basemat Doolen
Referenced URLs' properties: Use fully-qualified, absolute URLs in your sitemaps. Google will crawl your URLs exactly as listed. For example, if your site is at , don't specify a URL such as /mypage.html (a relative URL), use the complete, absolute URL:
If your sitemap includes only web page URLs, you can provide Google with a simple text file that contains one URL per line. For example, if you have two pages on your site, you could add them to your sitemap as follows:
If you're using a CMS such as WordPress, Wix, or Blogger, it's likely that your CMS has already made a sitemap available to search engines. Try searching for information about how your CMS generates sitemaps, or how to create a sitemap if your CMS doesn't generate a sitemap automatically. For example, in case of Wix, search for "wix sitemap", or in case of Blogger, search for "Blogger RSS".
For sitemaps with more than a few dozen URLs, you will need to generate the sitemap. There are various tools that can generate a sitemap. However, the best way is to have your website software generate it for you. For example, you can extract your site's URLs from your website's database and then export the URLs to either the screen or actual file on your web server. Talk to your developers or server manager about this solution. If you need inspiration for the code, check out our old, unmaintained collection of third-party sitemap generators.
Note: A Sitemap index file can only specify Sitemaps that are found on the same site as the Sitemap index file. For example, _index.xml can include Sitemaps on but not on or As with Sitemaps, your Sitemap index file must be UTF-8 encoded.
Note that this means that all URLs listed in the Sitemap must use the same protocol (http, in this example) and reside on the same host as the Sitemap. For instance, if the Sitemap is located at , it can't include URLs from
URLs that are not considered valid are dropped from further consideration. It is strongly recommended that you place your Sitemap at the root directory of your web server. For example, if your web server is at example.com, then your Sitemap index file would be at In certain cases, you may need to produce different Sitemaps for different paths (e.g., if security permissions in your organization compartmentalize write access to different directories).
If you submit a Sitemap using a path with a port number, you must include that port number as part of the path in each URL listed in the Sitemap file. For instance, if your Sitemap is located at :100/sitemap.xml, then each URL listed in the Sitemap must begin with :100.
To submit Sitemaps for multiple hosts from a single host, you need to "prove" ownership of the host(s) for which URLs are being submitted in a Sitemap. Here's an example. Let's say that you want to submit Sitemaps for 3 hosts: www.host1.com with Sitemap file sitemap-host1.xmlwww.host2.com with Sitemap file sitemap-host2.xmlwww.host3.com with Sitemap file sitemap-host3.xml
In this example, the robots.txt file at would contain the line "Sitemap: -host1.xml". By modifying the robots.txt file on www.host1.com and having it point to the Sitemap on www.sitemaphost.com, you have implicitly proven that you own www.host1.com. In other words, whoever controls the robots.txt file on www.host1.com trusts the Sitemap at -host1.xml to contain URLs for www.host1.com. The same process can be repeated for the other two hosts.
If you 've got a geo-targeted international site, or a site that has the same page translated into multiple languages, you can use your XML sitemap to your advantage. As we showed in our example above, putting hreflang tags in your sitemap tells crawlers that you 've got multiple versions of your page. Search engines can use this information to make sure they 're serving the right version to users based on language and/or location.
So I got my robots.txt and sitemap.xml to work by putting them in my public folder. But I cant get old urls to be redirected properly. I was hoping to find a way to set all old urls to 404. I see in my deploy console that I have four redirect rule implemented, witch is in my Netlify.toml:
@Marcelo_da_Silva sounds like you need to upgrade your plan level, if you want to crawl two domains. You could do sub.example.com only, but you would not get the pages from just example.com. The other option would be to put your sitemap for example.com on example.com (but you still wouldn't get pages from sub.example.com).
XML Sitemaps are designed for search engines and not for users. If you're new to the idea, and want to know how a sitemap looks like, they're typically available to see as a file sitemap.xml on the site, for example and these may link to other sitemaps for different countries and content categories, for example, -uk-sitemap.xml.
In this simple way we can easily identify if companies have a sitemap.xml and if the values in the tags, for each page, are properly implemented. These are some important tips that you need to consider when deciding whether to use XML Sitemaps.
There are many online tools that can help you with the creation/generation of sitemap.xml. For this purpose, we are going to use this service : -sitemaps.com/. If you're running a WordPress blog or site, the Yoast SEO plugin includes a function for this.
For our case study, we have deliberately deleted a tag. In this case the final sitemap.xml will appear like this (please review the screenshot below) and we will probably need to review again the sitemap.xml until we spot the problem.
If we have more than one language versions of a website, it is important to create sitemap.xml for each language respectively. There are cases where you handle large sites. The case in point we can automate the process by using Notepad++, simply by going to: Search > Replace and then just fill in the respective fields and include the language version for your sitemap.xml.
After the editing of the sitemap.xml (you can see the final version of the sitemap.xml below), the next step is the implementation of the sitemap.xml in the source code. Depending on our coding skills we can either implement it ourselves or a developer can implement it instead.
35fe9a5643