# What is a sitemap? Purpose and an XML example

> Learn which URLs belong, how to read a sitemap and what to check when a page is not indexed.


An XML sitemap is a file that lists a site's URLs to help search engines discover and understand pages the owner considers important. It is not the menu a person uses to navigate; that visual map is a separate HTML page. Submitting a sitemap does not require Google to crawl or index every URL in it.

## A small example

Suppose a café publishes four canonical pages: home, menu, location, and reservations. A simplified XML file could look like this:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url><loc>https://www.example.com/</loc></url>
<url><loc>https://www.example.com/menu/</loc></url>
<url><loc>https://www.example.com/location/</loc></url>
<url><loc>https://www.example.com/reservations/</loc></url>
</urlset>
```

`example.com` is illustrative; replace it with the real domain. Each `<loc>` contains an absolute URL. On a real site, list URLs you want search engines to consider: public, preferably canonical, and accessible. Leave out drafts, redirected pages, URLs marked `noindex`, and duplicates that point to another canonical URL. [Google's sitemap overview](https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview) and [sitemap creation guide](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap) explain formats and limits.

## When does it help?

A sitemap can be useful when a site is large or new, has many isolated pages, or adds content frequently. Internal links still matter: a sitemap complements navigation and discovery; it does not replace a linked structure that lets people and crawlers reach pages.

You can submit the file in Search Console or declare its location in `robots.txt`. Submission provides a hint and lets you review processing in Search Console; it is not a guaranteed indexing request. If the report shows excluded URLs or errors, inspect a specific URL and check its status, response, canonical, indexing directive, and internal links. Being listed in the sitemap does not fix those issues.

## What to check before submitting

Make sure the XML is valid and available at the declared URL. Compare its entries with the pages you actually want to offer in search. If a path redirects, returns an error, or should not appear in results, fix the file and the underlying page. For a small site, a sitemap generated by its CMS is often enough; confirm it updates when content is published or removed.

Do not confuse “included in sitemap” with “indexed” or “ranking.” Google decides what to crawl and index based on its systems and available signals. The file organizes a list of preferred URLs; it does not create demand, links, or visibility by itself.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
