You run the business, answer the phone, do the work, and send the invoices. Marketing is whatever hour you can find on a Sunday night. So here is the one hour that pays for itself. A sitemap is a plain list of every page on your website, written in a format Google reads. Getting one in place and handing it to Google is the difference between your pages showing up in search within days and drifting for weeks while Google finds them on its own, if it ever does. This is not deep technical work and it is not something you need to pay an agency for. You can do the whole thing yourself this week. Here is exactly how, in the order that matters, with the parts you can safely skip at your size clearly marked.
What a sitemap is, in one plain sentence
A sitemap is a file that lists every page on your site that you want Google to know about. Think of it as handing the delivery driver a printed list of every door on your street instead of hoping they wander down and find each one. The technical name is an XML sitemap, and it usually lives at an address like yoursite.com/sitemap.xml. You almost never have to write it by hand. The tool that built your site can make it for you, and most of them already do.
One thing to be clear about up front, because it saves you from wasting effort: a sitemap does not make your pages rank higher. It only helps Google find them and re-check them when they change. Ranking is a different job, about whether your page is genuinely the best answer to what someone typed. The sitemap just gets your page into the race. If your page is not indexed, it cannot rank at all, so this is step one, not the whole game. The full mechanics behind this pattern, written for developers, live in the sitemaps pattern if you ever want the deeper version.
Step one: find out if you already have a sitemap
Before you build anything, check whether one already exists. Most site builders create a sitemap automatically and you never knew it was there. Open a browser and type your site address followed by /sitemap.xml, like yoursite.com/sitemap.xml, and press enter. Try these in order:
- yoursite.com/sitemap.xml
- yoursite.com/sitemap_index.xml
- yoursite.com/wp-sitemap.xml (if you are on WordPress)
If any of those loads a page full of your website addresses, even if it looks like ugly raw code, congratulations, you already have a sitemap. You can skip straight to the part below about handing it to Google. If all three give you a page-not-found error, you need to turn one on, which is the next step and is usually a single setting, not a project.
Step two: turn on a sitemap for your specific tool
Almost every website tool can produce a sitemap, and on most of them it is already on or is one toggle away. You do not need to understand the file. You just need to know where the switch is. Here is where it lives on the tools most owner-operators are running:
- WordPress: install the free Yoast SEO or Rank Math plugin. Both generate a sitemap automatically the moment they are active. Yoast puts it at yoursite.com/sitemap_index.xml. That is the whole task.
- Squarespace: a sitemap is generated automatically for every site at yoursite.com/sitemap.xml. There is nothing to turn on. Just confirm it loads.
- Wix: automatic as well, at yoursite.com/sitemap.xml. Wix even submits it to Google for you in some cases, but you should still confirm it in the checking step below.
- Shopify: automatic, at yoursite.com/sitemap.xml, covering your products, collections, and pages. Nothing to enable.
- A custom-built or developer-built site: ask whoever built it whether a sitemap is generated, and if not, that is a small, cheap thing to request. The developer version of this is covered in the sitemaps pattern.
That is the entire build step for most people. If your tool is not on this list, search the phrase "[your tool name] sitemap" and you will find the setting in a minute. Do not spend money on a sitemap plugin or a paid service. This is free functionality that ships with your website software.
Step three: get Google Search Console, the free tool that shows you what Google sees
Google Search Console is a free tool from Google that shows you exactly which of your pages Google has found, which it has indexed, and which it is having trouble with. It is the single most useful free thing in this whole guide, and most owner-operators either have never set it up or set it up once and never opened it again. You need it for the next two steps, so set it up now. It takes about ten minutes.
- Go to search.google.com/search-console and sign in with the Google account you use for the business.
- Click Add Property and enter your website address.
- Google asks you to prove you own the site. The simplest route for most people is the URL prefix option, which lets you verify by adding a small snippet or a file, or automatically if you already use Google Analytics or a builder like Wix or Squarespace that connects for you.
- Follow the on-screen instructions for your tool. If you are on Squarespace, Wix, or Shopify, they each have a one-page help article titled "verify Google Search Console" that walks you through it in a few clicks.
If you get stuck on verification, Google's own help pages at support.google.com/webmasters cover every builder and every method. Once you are verified, you are inside the tool that tells you the truth about your site's presence in Google. Everything else in this guide runs from here.
Step four: hand your sitemap to Google
This is the payoff step and it takes about sixty seconds. Inside Search Console, look in the left menu for Sitemaps. Type in the address of your sitemap, which is usually just sitemap.xml or, on WordPress with Yoast, sitemap_index.xml. Click Submit.
Google will fetch it within an hour or so and start working through your pages. In the same panel you will see a status. Success means Google read it cleanly and knows about your pages. If instead you see "couldn't fetch," the address you typed is probably wrong or the sitemap is not actually live, so go back to step one, confirm the exact address that loads in your browser, and submit that. This one step is the whole reason for the guide. You have now told Google, in the format it prefers, about every page you want it to find.
Google's own overview of how sitemaps work and how to submit them is worth a five-minute read if you want the source of record: the Google sitemaps overview. It is written plainly and it confirms everything here.
Step five: check that your pages are actually getting indexed
Submitting the sitemap tells Google about your pages. It does not guarantee Google indexes every one of them, and this is where most owner-operators stop paying attention and lose the benefit. Come back to Search Console a week or two after you submit and look at two things.
First, in the Sitemaps panel, Google shows how many pages it discovered from your sitemap. That number should roughly match how many pages you actually have. Second, in the left menu under Indexing, open the Pages report. It splits your pages into two groups: indexed, meaning they are in Google and can appear in search, and not indexed, with a reason for each. Over the week or two after you submit, the indexed number should climb toward your total page count.
If the indexed count is well below your real page count, click into the not-indexed reasons. You do not need to fix all of them, and some are completely normal. Here are the ones you will actually see, in plain terms:
- "Discovered - currently not indexed": Google knows the page exists but has not gotten around to looking at it yet. Usually just needs time, or a link to it from a page Google already indexed, like adding it to your main menu.
- "Crawled - currently not indexed": Google looked at the page and decided it was too thin or too similar to another page to bother indexing. The fix is to make the page genuinely more useful and specific, not to resubmit it.
- "Page with redirect" or "Alternate page with proper canonical tag": these are almost always fine and mean the system is working as intended. You can ignore them.
- "Not found (404)" or "Server error": a page that should exist is broken. This one is worth fixing, because it means a real page is unreachable.
The handful of mistakes worth avoiding
You do not need to become an expert, but a few small errors quietly cost people their indexing, and all of them are easy to sidestep once you know they exist.
- Do not accidentally hide your site from Google. Most builders have a "discourage search engines" or "hide from search" checkbox, often left on from when the site was being built. Find it in your settings and make sure it is off before you do anything else. A single checked box can keep your entire site out of Google no matter how good your sitemap is.
- Do not submit a sitemap and then forget it after a redesign. If you rebuild or move your site, the old sitemap can go stale and point at pages that no longer exist. After any relaunch, re-check that the sitemap loads and resubmit it.
- Do not chase every not-indexed page. Some pages Google chooses not to index are pages that genuinely do not need to be there. Focus your energy on your money pages: your services, your main location pages, your contact page. If those are indexed, the tail can wait.
- Do not confuse indexing with ranking. Being in Google's index means you are eligible to appear. Appearing high means your page earned it. Get indexed first, then work on being the best answer.
What to do this week, and what to skip
Here is the honest priority list for someone with a couple of hours and no help. Do the first three. The rest are for later, or for never, at your size.
- Do now: check whether you already have a sitemap, turn one on if you do not, and set up Google Search Console. That is your one hour.
- Do now: submit the sitemap in Search Console and turn on email alerts. Sixty seconds and one setting.
- Do in two weeks: come back once, check the indexed count against your page count, and fix any of your main pages that are not indexed.
- Skip for now: paginated sitemaps, sitemap index files, splitting sitemaps by content type. These matter for sites with thousands of pages. You are nowhere near that, and reaching for them now is wasted effort.
- Skip for now: news sitemaps and video sitemaps. Unless you are running a news site or a video library, you do not need these, ever.
That is the whole 20 percent that gets you most of the benefit. Everything past it is for bigger operations, and the versions of this guide written for them cover exactly when it starts to matter. If you grow into a small team and start managing a real content library, the SME version walks through building a repeatable indexing routine. If you end up running dozens of client sites, the agency version covers doing this across a book of sites. And if you scale into a company with a real marketing team and hundreds of pages, the mid-market version handles index coverage at that scale. For now, you are the audience for exactly the steps above and nothing more.
A realistic picture of what this gets you
Let me be straight about the payoff so you can decide if the hour is worth it, because a guide that oversells wastes your time. Getting a sitemap in place and submitted does not flood your site with customers. What it does is close the gap between the pages you have published and the pages Google actually knows about. On a small site that has been quietly under-indexed, that gap is often the difference between a service page that has been invisible for months and one that starts showing up for the exact searches your customers make. It is the plumbing, not the water. But if the plumbing is broken, nothing else you build on top of it can flow.
For an owner-operator, the value is that you did it once, correctly, in an hour, and now it runs on its own with an email alert watching your back. You do not need to think about it again until you relaunch or add a big batch of pages. That is exactly the kind of one-and-done, high-return task worth spending a scarce evening on. Everything else in your marketing is ongoing effort. This one mostly is not.
When to stop doing it yourself
You can absolutely handle the sitemap-and-indexing basics yourself, and for most owner-operators that is the right call. The point where it makes sense to get help is not the sitemap. It is when your indexed count keeps falling short, when pages you know are good refuse to get indexed, or when the whole thing stops loading after a site change and you cannot figure out why. That is a real technical problem underneath, not a checkbox, and it is a fair thing to hand off.
If you hit that wall, or you would rather have the whole setup done right the first time and threaded into how you get found, that is the kind of foundational work we build into every site we ship. You can see how we approach it across our solution set, or, if you are a service business weighing whether to do this yourself versus have it handled, the way we work with professional services shows what that looks like. When you are ready, get in touch or run the estimator and we will tell you honestly whether you even need us for it yet. Half the time, for a business your size, you do not, and we would rather tell you that than sell you an hour you can do yourself.
