To prepare a B2B website sitemap, list every page the site needs before anyone designs a thing: one page for each service you sell, one for each industry or area you serve, the proof pages (projects, reviews, certifications), and the pages buyers use to contact you. Group them under five to seven menu headings. Once the site is built, publish an XML sitemap, which is a machine-readable list of those same pages, and submit it to Google. The first is a plan for people. The second is a file for search engines. You need both.
Most owners only hear about the second one, usually from a developer or an SEO report that flags it as missing, and never get asked to sit down and agree on the first. The planning sitemap is the one that decides whether a buyer finds the page they came for.
Start with what you sell, not with the menu
Write down every service a customer can buy from you, in the words they'd use on the phone, including the small jobs you'd happily take more of and the large ones that only come along a few times a year but pay for the slow months. A mechanical contractor might list chiller service, boiler replacement, preventive maintenance agreements and building automation. Each one gets a page. Every one. One "Services" page with six paragraphs on it can only rank for one idea, and a facility manager searching for chiller repair won't scroll past five other services to find it.
Next, who you serve. If you work in hospitals, schools and warehouses, each can carry its own page that speaks to the rules and schedules that buyer works under. If you serve several metro areas, decide whether each area gets a page. Build an area page only when you have something specific to say about working there, such as the permits, the buildings, the customers you've done work for or the crew that's based nearby. Otherwise skip it.
The pages almost every B2B site needs
| Section | Pages it usually holds | Why a buyer opens it |
|---|---|---|
| Services | One page per service you sell | To confirm you do the exact job they need |
| Industries or markets | One page per type of customer | To see you've worked in buildings or companies like theirs |
| Service areas | One page per region, where it adds real detail | To check you'll actually come to them |
| Proof | Projects, case studies, certifications, safety record | To defend the choice to an owner or a board |
| Company | About, team, careers | To see who they'd be dealing with |
| Resources | Blog, guides, FAQs | To answer questions before they call |
| Contact | Contact page, quote request | To reach a person quickly |
Keep it shallow
Two clicks. A buyer should reach any service page in two clicks from the homepage, three at most.
Deep nesting, such as Services, then Commercial, then Mechanical, then Chillers, then Repair, buries the page you most want found. Search engines find pages mainly by following links from one page to the next, so a page that's hard for a person to reach from the homepage is usually just as hard for a crawler to reach, and it may sit unseen for months. Link related pages to each other as well. The chiller repair page should point to the preventive maintenance page, and to the industries where you do the most chiller work.
Names matter too. Write them the way buyers search. "Commercial Roof Coatings" beats "Protective Solutions." You can be clever in the headline. Be plain in the menu.
Turn the plan into an XML sitemap
Once the pages exist, the XML sitemap tells search engines where they are. Google is candid here. Google says a site of about 500 pages or fewer that's well linked internally may not need one at all, though most sites still benefit. The same page notes that if you run WordPress, Wix or a similar system, it has probably made a sitemap for you already. Check first. It's often sitting at yoursite.com/sitemap.xml or /sitemap_index.xml.
A few rules from Google's guide to building a sitemap are worth knowing, because plenty of old advice gets them wrong:
- One sitemap file can hold up to 50,000 addresses or 50MB. Bigger sites split it into several files and list them in an index.
- Google ignores the priority and change-frequency values that many plugins still fill in. Tuning them is wasted time.
- The last-modified date only counts if it's accurate. Changing a copyright line isn't a real update, and Google stops trusting dates that move for no reason.
- Only list pages you want found in search: the final address of each page, with no duplicates, redirects or thank-you pages.
Submit it, then check that Google read it
Add a line pointing to the sitemap in your robots.txt file, and submit it in Google Search Console, the free tool Google gives site owners to see how their site performs in search. The Sitemaps report in Search Console shows whether the file loaded ("Success," "Has errors" or "Couldn't fetch") and how many pages Google found in it.
Look at that count. If your plan has 60 pages and Google discovered 14, something is missing from the file, so check whether a plugin setting is quietly leaving whole sections, such as service areas or projects, out of the sitemap by default. If Google discovered 400, the sitemap is probably full of tag pages, image pages or old test pages nobody meant to publish. Both are common.
A sitemap is a hint. Google says so plainly, and it won't get a thin page indexed. For a quick outside look at how your site shows up, our Free AI Visibility Check reviews your website and mobile speed, whether you come up in a local search, and what an AI assistant says when a buyer asks who to call. No email needed.
Where we come in
If you're planning a new site from scratch, the sitemap is the hardest part to get right, because it means mapping every service and area you sell into pages someone has to write. That's the first month of Inbound SDR. We plan and build a website of up to 100 pages around every service you sell and every area you serve, host it, and handle the technical side: sitemaps, crawl and indexing fixes, page speed and structured data. After launch, a new blog goes up every business day and is shared to up to 3 social platforms, so the sitemap keeps growing with real pages. Packages start at $1,000 per month on a 12-month term.
It's not the right fit if your site already has a page for everything you sell and someone in-house keeps it current. In that case, use the table above, check the Sitemaps report once a quarter, and keep going.
Short answers
Is a sitemap the same as site navigation?
No. Navigation is the menu people click. The sitemap is the full list of pages, and the menu is drawn from it.
Do I need an HTML sitemap page for visitors?
Rarely. A clear menu and good links between pages do the job better. On a very large site with hundreds of pages, an HTML sitemap can help people who get lost.
How often should the XML sitemap update?
Every time you publish or remove a page. Most site platforms do this automatically, which is one more reason to check the Search Console count now and then.
Get the next one in your inbox
New playbooks, benchmarks and guides from our sales floor, for owners and sales leaders who sell to businesses. One email a month. See past issues.

