Here is how to make a sitemap in one line: generate an XML file that lists every important URL on your site, then submit that file to Google Search Console so crawlers can find your pages faster. The fastest way to make a sitemap is to let your CMS or an SEO plugin build it automatically, then submit the URL in Search Console once and let it update itself. Most sites never need to touch a line of code. This guide walks through what a sitemap is, why it matters, the types that exist, four ways to create one, and exactly how to submit and verify it.
A sitemap will not force Google to index a page or improve where it ranks. It tells search engines which URLs you consider important and when they last changed, which speeds up discovery on large, new, or poorly linked sites. Below you get a methods comparison table, copy-paste XML, and a verification checklist so you finish with a working file Google can read.
A sitemap is a file that lists the URLs on your site you want search engines to know about, along with optional metadata like when each page was last modified. Search engines read it as a roadmap, then decide what to crawl and when. The most common format is XML, written for machines rather than people.
Think of it as a table of contents you hand to a crawler. Instead of relying only on links, Googlebot can open one file and see your full list of important URLs in seconds. According to Google Search Central's sitemaps documentation, a sitemap helps Google find pages it might otherwise miss, especially on sites where pages are not well linked to each other.
A sitemap is a suggestion, not a command. Google's documentation is explicit that using one does not guarantee every listed URL gets crawled or indexed, and that a sitemap will not improve rankings on its own. It is a discovery tool, and discovery is where visibility starts.
A sitemap matters because a page Google has not discovered cannot rank, and most pages already lose the visibility race. Ahrefs studied roughly one billion pages and found that about 96% of them get zero organic search traffic from Google. A sitemap will not fix weak content, but it removes one common reason a page never gets seen: the crawler never found it.
That first step feeds your largest channel. BrightEdge reports that organic search drives roughly 53% of all website traffic, so anything that helps search engines find and crawl your pages protects the source of most of your visitors. On a large or fast-growing site, faster discovery means new pages start competing sooner instead of sitting in a queue.
The stakes are rising as AI answers reshape results. Google has confirmed that AI Overviews reached more than 1.5 billion users a month in 2025, which means fewer searches end in a click. When every visit is harder to win, making sure your important pages are discoverable is table stakes, not a nice-to-have.
Sitemaps matter most in four situations: your site is large (thousands of URLs), your site is brand new with few backlinks, your pages are not well linked internally, or your site uses rich media like video and images you want indexed. Small, well-linked sites benefit less, but a sitemap rarely hurts.
Before listing the types, settle a common mix-up. The phrase "sitemap" refers to two different things that share a name:
They serve different jobs. If your goal is faster indexing, you want the XML file. If your goal is planning information architecture for a redesign, you want a visual sitemap. Many sites build the visual version first to decide their page structure, then ship an auto-generated XML version once the site is live.
There is more than one kind of sitemap, and choosing the right one depends on what you are trying to help search engines find.
.txt file with one absolute URL per line, UTF-8 encoded. Easy to maintain for small sites, but it carries no metadata.For the vast majority of sites, a single auto-generated XML sitemap (or index file) is all you need. Add image or video sitemaps only if media is central to how you want to be found.
| Format | Read by | Carries metadata? | Best for |
|---|---|---|---|
| XML | Search engines | Yes (lastmod, media extensions) | Most sites; the default |
| RSS / Atom | Search engines | Limited; recent URLs only | Supplementing fresh content |
| Text (.txt) | Search engines | No | Tiny sites, URL-only lists |
| HTML | Human visitors | No | Navigation, internal links |
| Visual diagram | Your team | N/A | Planning site architecture |
There are four practical ways to make a sitemap. The right one depends on your platform and how many pages you have. Here is how they compare.
| Method | Best for | Effort | Auto-updates | Cost |
|---|---|---|---|---|
| CMS or SEO plugin | WordPress, Shopify, Wix, Squarespace sites | Very low | Yes | Free |
| Online generator | Small static sites, no CMS plugin available | Low | No | Free up to ~500 URLs |
| Manual XML | Tiny sites, custom edge cases, learning | High | No | Free |
| Framework or build tool | Next.js, Hugo, custom-coded sites | Medium | Yes | Free |
For most people the answer is the first row: use a plugin or your CMS and move on. The other methods exist for sites without that option or for developers who want control. Below is how each works.
Most modern platforms generate a sitemap for you, and SEO plugins make it better. On WordPress, Yoast SEO and Rank Math both create and maintain an XML sitemap automatically, updating it every time you publish or edit a page. You usually find the file at yourdomain.com/sitemap_index.xml or yourdomain.com/sitemap.xml.
To set it up:
Shopify, Wix, and Squarespace generate a sitemap automatically with no plugin needed, usually at /sitemap.xml. You cannot always edit these by hand, but you rarely need to.
If you run a small static site with no CMS plugin, a free online generator is the quickest route. Tools like XML-Sitemaps.com crawl your site and produce a downloadable sitemap.xml. Most free tiers cap out around 500 URLs, which is plenty for a brochure site or small blog.
The trade-off is that generators produce a static snapshot. They do not update when you add pages, so you re-crawl and re-upload whenever your content changes. Download the file, upload it to your site's root directory via FTP or your host's file manager, and confirm it loads at yourdomain.com/sitemap.xml.
For larger or custom sites, a desktop crawler like Screaming Frog gives you more control: it crawls your site, lets you exclude noindex and non-canonical URLs, and exports a clean sitemap.xml. You can also gather URLs from your CMS, Google Analytics, or a site:yourdomain.com search before building the file by hand.
For a handful of pages, you can write the XML by hand. The structure is simple: a
``xml ``
Save it as sitemap.xml, upload it to your site's root, and verify the URL loads. The /about), and special characters in URLs must be entity-escaped (an ampersand becomes &). Google adds that
If your site is custom-coded, generate the sitemap during your build. Next.js produces a sitemap from a sitemap.ts (or .js) file in the app directory. Static site generators like Hugo, Gatsby, and Astro ship sitemap support or plugins that build the file every time you deploy. This is the cleanest option for developers because the sitemap regenerates automatically on each build, so it never drifts out of sync with your content.
Whichever method you pick, the output is the same kind of file. The next step is telling Google it exists.
Submitting tells Google where your file lives and lets it report errors back to you. You need a verified Search Console property for your site first. Once that is done, the submission takes under two minutes.
sitemap.xml or sitemap_index.xml.You can also point search engines to your sitemap from your robots.txt file by adding a single line: Sitemap: https://yourdomain.com/sitemap.xml. This helps other crawlers find it without a separate submission. Do both for full coverage.
Do not forget Bing. Submit the same sitemap URL in Bing Webmaster Tools (Sitemaps > Submit sitemap) so Microsoft's crawler, which also feeds some AI assistants, discovers your pages. Google's documentation also notes you can submit large or multi-site setups programmatically through the Search Console API, and that RSS and Atom feeds can ping search engines via WebSub.
Submitting is only half the job. Use this checklist to confirm the sitemap actually works:
https://example.com/page, not /page).Sitemap: appears in your robots.txt.When we ran this discipline for Swordfish AI, tightening crawlability and discovery alongside their wider SEO program, Swordfish AI grew revenue by 400% from organic search with Rankite. A clean sitemap was one input among many, but it is the kind of foundational fix that lets everything downstream work. If you want that foundation checked end to end, our complete SEO site audit covers crawling, indexing, and sitemap health in one pass.
Most sitemap problems come from listing the wrong URLs, not from the file format itself. Watch for these:
noindex pages sends mixed signals.Fixing these is usually faster than building the sitemap in the first place. Once your file is clean and submitted, the work shifts to the pages themselves: see how to rank on Google and run through our SEO audit checklist to find what is holding individual pages back.
Do I need a sitemap for a small website? Not strictly. Google can usually crawl a small, well-linked site without one. But a sitemap rarely hurts, it takes minutes to set up through a plugin, and it gives you a Search Console report on how discovery is going. For most sites the small effort is worth it.
Where should my sitemap be located? The convention is your site root, at yourdomain.com/sitemap.xml or yourdomain.com/sitemap_index.xml. It can technically live elsewhere, but keeping it at the root is the clearest signal and the path most tools expect.
How often should I update my sitemap? If you use a CMS or plugin, it updates itself every time you publish, so you do nothing. For manual or generator-based sitemaps, regenerate the file whenever you add, remove, or significantly change pages so it stays accurate.
Does a sitemap improve my Google rankings? No. A sitemap helps search engines discover and crawl your pages, which is a prerequisite for ranking, but it does not boost rankings on its own. Google's documentation is clear that submitting a sitemap does not guarantee indexing or higher positions.
What is the difference between an XML and HTML sitemap? An XML sitemap is for search engines and lists URLs in a machine-readable format. An HTML sitemap is a page for human visitors that links to your main sections. You submit the XML version to Search Console; the HTML version aids navigation and internal linking.
How do I know if my sitemap is working? Check the Sitemaps report in Google Search Console. A "Success" status, a discovered URL count close to your real page count, and pages appearing in the coverage report over the following weeks all confirm it is working. You can also track movement with a Google ranking tracker.
What is the difference between a visual sitemap and an XML sitemap? A visual sitemap is a diagram of your page hierarchy built in tools like Miro, Figma, Slickplan, or FlowMapp to plan a site's structure before it is built. An XML sitemap is a file you submit to search engines so they can discover your URLs. The visual version is for your team; only the XML version goes to Google.
How do I make a sitemap if I have more than 50,000 URLs? Split your URLs across multiple XML files, each under 50,000 URLs and 50MB uncompressed, then list those files in a single sitemap index file and submit the index to Search Console. Most CMS platforms and SEO plugins do this automatically once you cross the limit.
Can I submit my sitemap to Bing as well as Google? Yes, and you should. Add the same sitemap URL in Bing Webmaster Tools under Sitemaps, and include a Sitemap: line in your robots.txt so other crawlers find it too. One file works for every search engine; you just submit it in more than one place.
Do I need a sitemap if I already have good internal linking? If your site is small and every page is reachable through internal links, Google can often crawl it without a sitemap. But a sitemap still gives you a Search Console discovery report and helps on larger or frequently updated sites, so it is usually worth the few minutes it takes.
Pick the method that matches your platform and create the file today. If you run WordPress, install Yoast or Rank Math, confirm the sitemap loads, and you are most of the way there. If you are on a custom stack, wire sitemap generation into your build so it never drifts.
Then submit it in Google Search Console, run the verify checklist above, and check back in a week to confirm pages are getting indexed. Once discovery is solid, the next gains come from the pages themselves. If you want an expert to pressure-test your crawlability, indexing, and on-page foundations in one go, start with a local SEO audit from Rankite.
Get a free, no-obligation SEO audit and a 30-minute strategy session. We'll show you exactly where the growth is hiding.
Fill out the form and we'll get back to you within one business day. Prefer email? Write to us directly at contact@rankite.com.