Academy › Publish › Get found on Google
The map you hand over, not the one it has to guess
Find out whether your sitemap.xml tells the truth about your site, how to fix it if you manage it yourself, and how to check in Search Console that Google has it.
By Yodai · Published September 6, 2026 · Updated October 12, 2026
Maybe the pages you want showing up no longer carry the noindex tag, maybe you can read the reason Search Console gives you when something fails, and yet the indexing report still won't budge: some pages are indexed and others, which look the same to you, haven't even been crawled.
There can be many reasons, and one worth checking lives in a file you may have never opened: the sitemap.xml. It's the list you hand Google with the pages you want it to find. It doesn't guarantee it will crawl and index all of them, but it helps Google discover them, and a list full of errors only helps halfway. And if your site lives at an address borrowed from the platform you built it with, check first that Google can index its inner pages, not just the homepage: if it can't, no sitemap will fix that.
What a sitemap is and what Google uses it for
A sitemap.xml is a list of your site's addresses, written in a format Google knows how to read. The file is usually at yoursite.com/sitemap.xml, and Google uses it to discover your pages and crawl your site better. What it doesn't do is follow priorities: if the file includes priority or change-frequency fields, Google ignores them.
Having a sitemap isn't required. Many small sites work fine without one because Google finds the pages through internal links. If you do have one, make sure it's not lying: it shouldn't list pages that no longer exist, pages with a noindex tag, or the same page repeated with a different color or size filter. Google asks you to include only the pages you want to show up in its results. The extra ones don't break the rest of the file, Google still reads through it, but Search Console flags them as problems, and they don't do you any good.
the rest of the file still gets read; what you lose is a clean list where you can spot at a glance what's actually wrong
Where yours comes from: generated by your platform, or uploaded by you
Before you fix anything, figure out where your sitemap comes from. There are two situations, and how you fix it depends on which one you're in.
- The sitemap regenerates itself every time you publish or delete a page
- You never touch the XML file directly
- Your job is to check what it lists, not to write it
- The sitemap doesn't update itself: you have to regenerate it by hand every time you change pages
- You need a tool to write it, a sitemap generator or your own editor
- If you delete a page, the sitemap keeps listing it until you regenerate it
Which one do I pick: If your platform generates it automatically, don't start editing the XML by hand: check what it lists and trust that it updates itself. If you uploaded it yourself, treat it as a task that repeats every time you touch the site, not something you do once and forget.
What goes on the list, and what doesn't
Don't put every URL on your domain into the sitemap. It's the list of what you want Google to index, not a dump of everything sitting on the server.
Fix it and send it in
- 1Open the current file
Type yoursite.com/sitemap.xml into your browser. If a list of URLs loads, you already have one. If it errors out, open yoursite.com/robots.txt: if there's a line starting with Sitemap:, that's where your address is. If it's not there either, chances are you don't have one and need to generate it. - 2Compare it with your actual site
Go through every URL on the list, one by one. Cross out the ones that no longer exist, the cart or checkout pages, and anything with noindex. - 3Add what's missing
If you launched a new page or service area and it's not there, it needs to be added. On a platform that generates the sitemap for you, publishing the page takes care of it; if you're doing it by hand, you add the line yourself. - 4Generate it if it doesn't exist
Without your own sitemap, use a sitemap generator with your site's address, or whatever your builder provides. Upload the result to the root of your domain, as sitemap.xml, if your site lets you upload files; if not, ask whoever manages it for you. - 5Submit it in Search Console
In the left-hand menu, go to Sitemaps. Type sitemap.xml in the field and hit Submit. If your platform already sends it for you, here you're just confirming it's there and error-free. Once Google processes it, you'll see how many URLs it detected and whether any caused problems.
With the sitemap fixed and submitted, you're making it easy for Google to find your site: you've handed it over yourself, with the pages you want found and none of the ones you don't. It doesn't guarantee it'll index all of them, but it removes one reason for doubt.
- Your sitemap.xml lists only real pages, no noindex pages and no duplicates
- You know whether you're the one who has to check it by hand, or your platform keeps it updated on its own
- It's submitted in Search Console, under Sitemaps, either by you or by your platform
- You can check right there how many URLs it detected, compared to what's on your list
Test yourself
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. You closed your online store a month ago and kept only the contact page, but the sitemap still lists the old product pages, which now show an error when opened.
The sitemap gets fixed now, not at the next update: those listings aren't going to show up on Google anymore, and as long as they stay on the list, Search Console flags them as errors and you're asking Google to crawl dead pages instead of paying attention to the ones you actually want indexed, starting with your contact page.
2. Your platform generates the sitemap on its own, but a new page you published three days ago still isn't showing up on it.
Don't edit the XML by hand. Check whether the page is truly published and not still a draft, because on a platform that generates the sitemap for you, the list follows the published pages, not the other way around.
3. You have an FAQ page linked from your site's footer, but you don't want it showing up in a Google search.
It doesn't go in the sitemap. If it already carries noindex, adding it to the list would be telling Google to index it and not index it at the same time: Search Console would flag that as a problem, and it wouldn't get you anything.
Your sitemap now tells the truth and doesn't contradict any tag. But indexing the right page won't do you any good if you bet on the keyword that just sounds right to you: it's time to pick, with data instead of guesswork, the three searches you're going to compete for.
In Yodai every site goes live with its padlock, its sitemap and its titles, with nothing to buy or set up. See what the hosting included with your website covers.
NextThe three phrases people actually type, not the ones you assume