If we really need to, what we usually do to organize them is to play with the names of the files. For example, imagine that you have a sitemap for the blog of the Madrid store of the site. Since we don’t trust putting it in the “domainmadridblogsitemap.xml” folder because some URLs might not be in this structure, what we can do is emulate something similar with the name, putting for example: “sitemap-domain-com–madrid–blog.xml”.
Google not only supports sitemaps in
There are more formats. Sitemap.xml is just one of the supported formats (and the most complete and standard, of course) but there are others that can be very very useful in other cases. You can see them all in Google’s documentation on sitemap formats .
We can upload sitemap.txt files:
These are made up of a very simple file that simply contains all the URLs of the site, one after the other, each on a separate line. way and we can line data avoid technical complexities if we are in a hurry or working on the typical project with limited technical resources.
As a basic sitemap it will work
The same, but this system, of course, is not the most recommended for the simple reason that we lose many of the functionalities that we will see what is freelancing: how and where to start later (precisely because we only indicate URLs and nothing else with them).
We can also upload an RSS or Feed of the site:
This is another option, even less known. These are files used to syndicate content, that is, so that certain tools can see the latest posts from a platform and read them. They are XML files that only have content and no design. If you have never seen one, you can see the. A one for any blog in WordPress by adding “rss” to the end of its URL. For example, this is the Feed for this website . Uploading this type of file usually means an improvement in the speed of indexing new content. They are quite consulted sitemaps that generally only yeezys shoes contain 10 or 20 elements and, therefore. S Google can read them very quickly.