The site map helps to provide the search engine with a list of relevant addresses. It should reflect the actual service, not collect all the options of links, errors and outdated subpages.
See what goes on the map
An overview of optimization is worth starting with a comparison of the map with the content actually available. Does it contain new guides and services? Did not there remain test addresses, redirects or pages removed long ago? The fact that the file exists does not confirm its usefulness.
With the service managed by CMS, specify which modules are collected from. Adding a new type of content may need to be included in the mapping mechanism.
Maintain Address Consistency
Google recommends giving full addresses and indicating the versions to appear in the results. The map should be consistent with the choice of canonical addresses. Reporting it is a guide, not a guarantee of processing all subpages. The rules are described. website map building guide.
Do not fix the conflict of addresses only by changing the map. Also check the links in the service and the existing redirections.
Specify the date of the actual changes
Field lastmod should correspond to a significant update of the website. Do not change it every day just because the file has been re-generated. Google documentation indicates that the credibility of these dates is relevant for their use.
- Compare date with published change of content.
- Check map behavior after editing a single article.
- Separate the page update from changing the whole service footer.
- Control the map also after migration.
Link the map to navigation
A useful subpage should also be available through logical links to readers. The XML map does not replace categories, menus or links between articles. We write about this complementary area in Internal Linking Review GuideBoth mechanisms should provide a coherent picture of the content of the site.
