What is a sitemap?

Two things a sitemap is not: a guarantee of indexing and a cure for weak internal linking. What it is, is the inventory list a website hands to search engines — a file, usually at /sitemap.xml, enumerating the pages you want found, each with the date it last changed, submitted once through Google Search Console. Understood correctly, its role is discovery assistance. Crawlers find pages on their own by following links, but the sitemap hands them the complete map: new pages appear on the radar sooner, pages with weak internal linking such as products deep in a catalogue or older articles do not stay undiscovered, and on large sites and during migrations a fresh map noticeably shortens the transition. What it does not do is force indexing — a file listing ten thousand thin pages remains a catalogue of intentions — nor compensate for structural problems, because a page nothing links to is already telling the engine that the site itself does not consider it important. Healthy practice for a company website: automatic generation, since any decent platform maintains the file at every publish while a hand-written one is dead by its second week; content hygiene, meaning only canonical, indexable pages belong in it; registration in Search Console once, after which the engine re-reads it by itself; and above all reading the report, because the gap between pages submitted and pages actually indexed is one of the most honest free diagnostics available anywhere in search.