A sitemap is a file that presents a list of a website's pages in a standardized format to search engines. Its purpose is not to "improve rankings," but to make it easier for search engines to understand what content a website has and which parts are new. Because it is inconspicuous, many new sites only discover problems with it long after they occur.
Put It in the Right Place and Write the Right Paths
A sitemap needs to be placed in the conventional location, or explicitly pointed out in the crawl rules file; otherwise, search engines may not read it at all. The addresses listed in it must be complete, accessible canonical addresses, not test domains or temporary links with parameters. If one character in an address is wrong, the corresponding page is effectively not submitted.
Only Include Pages That Should Be Indexed
A common mistake is to put admin pages, search result pages, and temporary campaign pages all into it at once. These pages either require login or contain duplicate content; after search engines crawl them, they will mostly be judged invalid, and this may also affect the assessment of the entire site's quality. A sitemap should list only public content pages with independent value.
Updates and Time Annotations
A sitemap needs to be updated along with content. After new pages are published, old pages are taken offline, or sections are adjusted, the file must be synchronized. The file can usually annotate the last modified time of each page, and this time should match the page's actual changes. If the time annotations are inaccurate for a long time, search engines will gradually lower their trust in this signal.
Coordinate with Crawl Rules
A sitemap is responsible for "please come and look," while the crawl rules file is responsible for "don't look here." The two need to work together: content blocked by the rules should not appear in the sitemap again; and pages listed in the sitemap should not be mistakenly blocked by the rules. New sites are most prone to problems here when setting access restrictions—for example, using an overly broad wildcard rule to prevent search engines from crawling a certain type of page, only to block public pages as well.
Don't Treat Submission as a Cure-All
Proactive submission can speed up discovery, but what determines whether a page is indexed is still the content itself. A site that has not been updated for a long time and has duplicate content will find it difficult to obtain stable indexing even if submitted every day. Treating the sitemap as foundational work to get right and leaving energy for content is the more practical order.
The technical barrier to sitemaps is not high; what is difficult is maintaining consistency over the long term. Checking it casually after every launch or redesign is much less troublesome than looking back for causes after problems arise.