An XML sitemap lists the URLs you want search engines to discover on your website. It can be useful for large sites, recently launched projects, and sites with complex navigation. But adding an address to a sitemap does not guarantee indexing. Search engines still assess accessibility, content, canonicalization and other signals.
Which URLs belong in a sitemap?
Prioritize the preferred, accessible URLs that you genuinely want in search results. Good candidates generally return HTTP 200, contain useful content, and are not mistakenly marked noindex. Avoid listing old redirecting addresses alongside their final destinations or providing both parameter-heavy duplicates and their clean canonical equivalents without good reason.
A simple XML sitemap example
A basic file contains a <urlset> root and one <url> per entry. Within each entry, <loc>https://example.com/services/</loc> provides the absolute URL. Use valid XML and UTF-8 encoding. Seeing a plain browser XML tree rather than a styled page is normal.
Google documents a maximum of 50,000 URLs or 50 MB uncompressed for one standard sitemap. Larger websites can split files and submit a sitemap index.
Worked example: 73 URLs, 33 passing checks
Imagine a sitemap with 73 addresses. Some redirect, a few carry noindex, and others do not appear in a limited site crawl. Resist reducing this immediately to one score. Classify problems by cause: unavailable destination, redirection, indexing directive, canonical conflict, or crawl coverage. Each category has a different remedy.
Weak decision: Call every sitemap URL missing from a crawl an orphan. Better decision: Compare crawl depth, page limits, incoming links and final URLs before assigning an orphan label. A limited crawler cannot prove that a page has no incoming link anywhere on the web or the site.
Common sitemap problems
- Including URLs that permanently redirect.
- Listing duplicate variants instead of their preferred canonical versions.
- Keeping noindex pages in a list intended for indexable content.
- Mixing HTTP and HTTPS addresses unnecessarily.
- Listing 404, 5xx or login-protected destinations.
- Failing to refresh the sitemap after a migration.
A problematic URL does not mean every entry is invalid. Identify and repair the relevant group.
How to submit a sitemap in Search Console
- Generate the file and test its URLs.
- Publish it at a public path such as
/sitemap.xml. - Open the appropriate Search Console property.
- Submit the sitemap location in the Sitemaps report.
- Monitor discovery and inspect important URLs separately.
Use Sitemap Checker to inspect a file, XML Sitemap Generator for small lists, and Site Crawler to compare the sitemap with actual navigable pages.
Multilingual sitemaps require consistent URLs
English and Turkish content typically has distinct addresses. Mixing canonical URLs between languages or linking both language versions to a single primary URL can complicate discovery. Correct hreflang relationships can describe alternatives, and Google also supports language annotations in sitemap formats. The important part is a consistent map of real, accessible language URLs.
Frequently asked questions
Will a submitted page be indexed right away?
No. Submitting a URL helps discovery but is not an indexing promise.
Do changefreq and priority guarantee better rankings?
No. Treat the file as discovery information, not a ranking lever.
Is a sitemap necessary for every small website?
A small, well-linked site can be discovered without one, though maintaining a sitemap may still help site owners track intended URLs.
Reference: Google sitemap documentation. For duplicate URL problems, continue with our canonical tag guide.
Join the discussion
Share your experience or ask a question about this guide.