In one sentence: An XML sitemap is a machine readable file listing the pages on a site that you want search engines to know about, each one recorded with the date it last changed.
Despite the name, no customer ever reads it. It is a file written for crawlers, kept at a predictable address like /sitemap.xml, and it holds a plain list of page addresses with a note of when each was last updated. It is not the friendly site map page some sites link in the footer for people who are lost.
The file is a suggestion, not an order. Listing a page does not force a search engine to file it, and leaving a page off does not hide it. What the list does well is tell a crawler that a set of pages exists and which of them changed recently, so it does not have to find everything by wandering from link to link.
There is less in the file than people assume. No keywords, no descriptions, nothing you can write to argue a page deserves better treatment. The format does carry optional fields for how often a page changes and how important you consider it, and search engines have long treated both as noise. The last changed date is the field that carries weight, and only while it stays honest. Stamping today's date on every page every night teaches the engine to stop reading the dates.
Say you publish a page on Tuesday and the only thing pointing at it is one old post. A crawler might work its way there eventually. Listed in your sitemap with Tuesday's date on it, that page stands a better chance of being looked at while it is still new.
A six page brochure site barely needs one. The value climbs with size. On a storefront with over 1,400 products and live Stripe checkout, built for a Virginia retailer, no crawler is going to stumble across every product page by wandering the category links, and the sitemap is what says the rest of the catalog is there.
The other case is the orphan page, the page nothing on your site links to. Most sites have a few, usually left over from an old campaign. Listing them keeps them from vanishing altogether, though fixing the missing link is the better repair.
Then the honest tradeoff. A stale sitemap does damage. A file still listing pages that now return errors or bounce through redirects wastes the attention you wanted and teaches the engine your list is not worth trusting. So the file has to be regenerated whenever pages are added, renamed, or retired, which makes it one of the unglamorous jobs inside website maintenance.
Three files get mixed up constantly, and they do different jobs. Robots.txt says where a crawler may go. The sitemap says which pages you would like it to consider. A canonical URL settles which address counts when one page has several. None of the three decide indexing. The search engine still makes that call on its own.
Submitting the file in Google Search Console is worth the two minutes, because that is where you find out how many of the pages you listed were actually filed. The gap between listed and filed is one of the more useful things a small site owner can watch.
Keeping it at a predictable address and naming it in your robots.txt file is usually enough for crawlers to find it. Submitting it in Search Console is still worth doing, because that is where the reporting on those pages shows up.
Only the pages you want people finding through search. Thank you pages, internal search results, and near duplicates do not belong there. A sitemap stuffed with pages you would not want a customer landing on tells the engine the list was never thought about.
Website maintenance · Indexing · Robots.txt · Orphan page · Google Search Console · All glossary terms · Plain-English answers · AI search optimization services
Free consultation, plain-English advice. If you don't need us, we'll say so.
Book a free consultation → Or call/text directly: (407) 694-2055Tell us a little about the business and we will come back with an honest read: what we would fix first, what it costs, and whether you need us at all. Prefer to see work before you talk numbers? Get a free homepage mockup, built for your business, yours to keep either way.
Brandon reads every one of these himself. You will hear back shortly with an honest read on what we would do first, what it costs, and whether it is worth it for you.