Add to Preferred Sources
A website sitemap planning guide addresses two separate structural documents: a visual sitemap, the hierarchy diagram your team builds before any design decision is made, and an XML sitemap, the machine-readable file that lists your live, canonical URLs for search engines to crawl and index. Effective web design in Johannesburg and across South Africa starts with these structural decisions — before colour palettes, fonts, or any layout work. Get the page architecture wrong first and you pay in expensive redesign hours or in a site that buries its own services from both users and Google.
The confusion between these two documents is the most common planning mistake we see. Many business owners arrive believing they need to "sort out their sitemap" for SEO when they actually need a visual sitemap as a strategic document before development begins — and sometimes both. This guide separates the two clearly, walks through both step by step, and gives you a decision table for choosing the right site structure based on your business type and page count. If you are also starting a full business website planning process, you will find this a useful companion to the broader planning framework.
Quick Answer
A website sitemap planning guide addresses two separate tools: a visual sitemap (a flowchart diagram of your page hierarchy used for planning and stakeholder alignment before development) and an XML sitemap (a machine-readable file submitted to search engines listing your canonical, indexable URLs). Build the visual sitemap before any design work; generate and submit the XML sitemap once your site is live. For most South African business sites under around 500 pages with solid internal linking, an XML sitemap is helpful but not critical — the visual sitemap earns its time on almost any multi-page build.
In This Guide
What Is a Website Sitemap? (Two Documents Explained)
Why Plan Your Sitemap Before Design Starts
Your Website Sitemap Planning Guide: Step by Step
Sitemap Structure by SA Business Type
Starting a New Site or Redesign?
Send us your current page list and we will map the right structure for your business before any design work starts.
Get a Free Structure ReviewWhat Is a Website Sitemap? The Two Documents Most Businesses Confuse
A website sitemap is not one thing — it is two documents that serve completely different audiences and purposes, and conflating them is what leads to the most common planning errors.
| Document | Audience | Format | When to Create | Purpose |
|---|---|---|---|---|
| Visual sitemap | Your team and stakeholders | Flowchart / diagram | Before any design begins | Plan page hierarchy, align stakeholders, catch gaps |
| XML sitemap | Search engines (Googlebot, Bingbot) | Machine-readable XML file | Once the site is live | Help search engines discover and index your URLs |
| HTML sitemap | Website visitors | Linked page on your site | Ongoing; useful for large sites | Navigation aid for users who cannot find a page |
The visual sitemap is the planning artifact. It shows your full page structure as a hierarchy of boxes and connecting lines — essentially a flowchart of your website before anyone opens a design tool. According to Nielsen Norman Group, a sitemap is "a tangible visual diagram that can be shared with stakeholders" and forms only part of the broader information architecture work that includes navigation naming, taxonomy, and content grouping decisions.
The XML sitemap is the technical file. According to Google Search Central, it is "a file where you provide information about the pages, videos, and other files on your site, and the relationships between them." Search engines use it to crawl more efficiently, particularly for new sites, large sites, or sites with substantial media content.
Key Distinction
Build the visual sitemap before a single design decision is made. Generate the XML sitemap after your site is live. These are sequential, not simultaneous, tasks.
Why Structural Planning Matters Before Design
Structural decisions made after visual design is locked in are one of the most common sources of rework on the South African website rescue projects we take on. Once a designer has created layouts for six service pages, discovering that two of them belong under one parent category — or that three were missing entirely — means scrapping paid work.
The SA context adds another dimension. With 98.3% of South African internet users accessing the web via a smartphone (DataReportal Digital 2026), navigation depth has a direct cost in mobile usability. A deeply nested page structure that forces four or five taps to reach a service is not a minor inconvenience — it is a conversion barrier on the device most of your visitors are using right now.
Building your visual sitemap first also forces you to confront a question that most business owners avoid: are you mapping your internal org chart, or mapping how customers think about your services? These are almost never the same thing. A logistics company might internally separate road freight, cross-border, and last-mile — but a customer searching for "courier services Johannesburg" does not care about that distinction until they are already in contact. The sitemap is where that mismatch gets resolved cheaply.
SA Mobile Navigation Benchmark
Navigation depth matters more in South Africa than in markets where desktop dominates. With the vast majority of local browsing happening on mobile — where thumb reach and screen space are limited — keep your most important service or product pages reachable within two taps from the homepage where possible. This is not a hard rule; it is a useful target to pressure-test against your visual sitemap.
Your Website Sitemap Planning Guide: Step by Step
A strong visual sitemap planning process follows five stages, and the order matters — skipping stage one to jump to drawing boxes is how you end up with a sitemap that looks organised but still buries your most important pages.
Step 1: Take Stock of Everything You Have
Before planning anything new, list every existing page. For a live site, export a crawl using a tool like Screaming Frog or pull your page list from Google Search Console. For a new site, list every page you know you will need. Include pages that exist but perform poorly — they are candidates for consolidation or removal, not automatic inclusion in the new structure.
Step 2: Identify What Your Visitors Actually Need
Group your pages by the question a visitor is trying to answer, not by your internal categories. A professional services firm might have partners, associates, and support staff internally — but visitors are asking "can you help me with X?" not "which department handles X?" Run a quick card-sorting exercise with three or four people from outside your business: give them the page names and ask them to group the ones that belong together. The groups they create are usually more useful than your org chart.
Step 3: Define Your Hierarchy
Establish your depth. Most business sites work across two levels: top-level navigation (Home, Services, About, Contact) and second-level pages beneath each (Services → Accounting, Tax Advisory, Payroll). A third level is warranted on large ecommerce sites or complex service businesses, but each additional level of depth is a tap a mobile visitor has to make. Use the decision table in the next section to match your structure to your site size.
Step 4: Draw the Sitemap
Use boxes for pages and lines for relationships. A free tool like Miro, Whimsical, or even Google Slides works for most SA business sites. Start with the homepage at the top. Branch down to your main navigation sections. Below each section, show the pages that belong there. Colour-code by status: existing pages you are keeping, pages you are creating, and pages you are retiring. This diagram becomes your shared reference for the web designer, the developer, and the content writer — everyone works from the same map.
Step 5: Validate Navigation Paths for Your Priority Actions
Identify the three most important actions a visitor should take on your site (enquire, buy, download). Trace the path from the homepage to each action on your sitemap. Count the steps. If a critical conversion path requires more than three navigation choices, restructure until it does not — not because the "three-click rule" is a hard law (Nielsen Norman Group research has found it is not) but because each decision point is a place where a distracted mobile visitor can drop.
Step-by-Step Summary
Inventory existing pages → group by visitor question → define depth → draw the hierarchy → trace conversion paths. Complete these five steps before any design file is opened. Changes cost hours at this stage; they cost days once layouts exist.
Sitemap Structure by SA Business Type
The right website sitemap structure depends on your page count and the nature of your business. Here is a practical decision table built for common South African business types.
| Business Type | Typical Page Count | Recommended Structure | Depth Limit | Key Consideration |
|---|---|---|---|---|
| Local service business (plumber, electrician, clinic) | 5–15 pages | Flat — every page one click from homepage | 1 level | Mobile speed; keep navigation short |
| Professional services (accountant, attorney, consultant) | 15–40 pages | Grouped — services clustered under 2–3 parent pages | 2 levels | Separate service pages from blog/resources to protect credibility |
| B2B or SaaS | 30–80 pages | Grouped with content hub — solutions / industry pages + resource cluster | 2–3 levels | Industry-specific landing pages often worth a third level |
| Ecommerce (retail, fashion, health) | 50–5,000+ pages | Full hierarchy — category → subcategory → product | 3–4 levels | Faceted navigation and filters need careful canonical planning; see below |
| Hospitality (guesthouse, restaurant, lodge) | 8–25 pages | Flat to grouped — rooms, menus, packages, gallery | 1–2 levels | Keep the booking path within one tap of the homepage on mobile |
Well-structured professional services sitemap: Home → Services (parent) → Accounting / Tax Advisory / Payroll (children) → Blog → Contact. Every service page is two clicks from home. Navigation contains five items. Visitors who land on any service page can reach the contact form in one click. The structure stays flat enough that an XML sitemap is straightforward to manage.
Poorly structured site (common pattern): A Johannesburg accounting firm with 12 service pages, all at the same navigation level with no parent grouping, a blog section buried three levels deep, and a Contact page not linked from the main navigation. Visitors searching for a specific service land on the homepage and leave because the structure reflects the firm's internal departments rather than what clients are looking for.
What to Include — and Exclude — From Your XML Sitemap
What belongs in an XML sitemap is decided by two properties of each individual URL — whether it is the canonical version and whether it is indexable — not by what type of page it is. Google's instruction is to include the URLs you want to see in Google's search results, so the URLs to leave out are the ones that fail that test: noindexed pages, non-canonical duplicates, URLs that redirect, 404 and 410 URLs, and pages behind a login. Page type is not the criterion, which is why blanket rules such as "strip out every paginated URL" get this wrong.
Include in Your XML Sitemap
- Canonical, indexable pages — only pages you genuinely want ranked
- Accurate
lastmoddates that reflect real content updates, not auto-generated timestamps - For ecommerce and media-heavy sites: image and video sitemap extensions where applicable
Exclude From Your XML Sitemap
- Pages tagged with a
noindexdirective — if you have told Google not to index a page, there is no reason to invite it to crawl it via the sitemap - Non-canonical duplicates — list the canonical version of the page instead
- Redirect URLs (3xx status codes) — list the final destination URL instead
- 404 or 410 error pages
- Paginated URLs (
/page/2/,/page/3/) only when you have noindexed them or canonicalised them to a view-all page — Google's guidance is that each page in a paginated sequence carries its own canonical URL, not page 1's, so a self-canonical, indexable/page/2/is a legitimate sitemap entry; Google no longer usesrel=next/rel=prevas an indexing signal - Thank-you pages, checkout steps, account pages — anything behind a login or session parameter
Technical Limits and Tags Worth Knowing
A single XML sitemap file is capped at 50,000 URLs or 50MB uncompressed — whichever limit is hit first — and beyond either limit you use a sitemap index file that references multiple sitemap files. Google Search Central documentation states that Google ignores priority and changefreq outright, and uses lastmod only where the value is consistently and verifiably accurate — so a plugin that stamps today's date on every URL gives Google nothing to act on. Listing a URL is a request, not an instruction: Google's own wording is that a sitemap "doesn't guarantee that all the items in your sitemap will be crawled and indexed".
Submission and Maintenance
Submit your sitemap URL to Google Search Console and Bing Webmaster Tools. Reference it in your robots.txt file using the full absolute URL. If you are running WordPress, WordPress SEO plugins like Yoast or Rank Math generate and update your XML sitemap automatically — review the output periodically to confirm it matches your intended page set rather than simply trusting the plugin output.
Google's Guidance on When You Need a Sitemap
According to Google Search Central, sites with around 500 pages or fewer that are comprehensively linked internally may not need a separate XML sitemap — good internal linking already lets Googlebot follow links to discover pages. For most South African small business sites, Google can discover pages by following links from the homepage — a clean internal link structure is the first priority; sitemap submission is a useful supplement, not the foundation.
Common Sitemap Planning Mistakes SA Businesses Make
Any solid website sitemap planning guide will identify these structural problems at the diagram stage, before they are built into the site. Most structural issues on South African business sites trace back to four recurring planning errors.
Mapping the org chart instead of the customer journey. Your internal departments and your visitors' questions are rarely aligned. A site structured around your departments forces visitors to understand your business before they can use it. Structure around the questions visitors arrive with instead.
Treating every page as equally important. Your XML sitemap should list the pages you want in search results. Many SA sites accumulate tag pages, thin category archives, and legacy content with no chance of ranking. Crawl budget is rarely the real cost at this size: Google scopes crawl budget management to sites above roughly 1 million pages, or 10,000+ pages with very rapidly changing content. The cost on a normal SA business site is that the sitemap stops describing the page set you actually care about.
Ignoring mobile navigation depth at the planning stage. A structure that feels manageable on a desktop dropdown becomes unwieldy on a mobile tap-through. With most SA visitors on smartphones, navigation depth is a usability decision, not just an architecture preference. Test your visual sitemap by tracing the path to your most important pages on a phone-sized sketch.
Setting up and forgetting the XML sitemap. A sitemap built at launch and never updated becomes a liability over time — it references old URLs, deleted pages, and redirects. Tie sitemap generation to your content workflow; check Search Console's Sitemaps report quarterly to confirm submitted URLs are being indexed without errors.
Is Your Current Site Structure Costing You Enquiries?
Share your site URL and we will audit your navigation depth, internal linking, and page hierarchy against what your target visitors are actually looking for.
Request a Free Site Structure AuditWhy South African Businesses Choose Growth Pulse Media for Web Design
Dirk van Greuning built and scaled a large South African ecommerce business before founding Growth Pulse Media — which means our web design engagements are led by a founder with direct, hands-on experience in SA digital operations, not someone who learned the field from theory. The visual sitemap is not a deliverable we hand off and move on from; it is the working document that drives every design, development, and content decision that follows.
We work with a deliberately limited client load so that every website project receives senior-level attention from the structure planning stage through to launch. No juniors handling your information architecture while someone senior approves it at the end. If your site needs a foundational rebuild of its page hierarchy alongside responsive web design for South African mobile users, that structural work is included in the engagement, not treated as a premium add-on.
We keep all execution in-house across design, development, and SEO — which matters for sitemap work because the visual planning, the URL structure, the internal linking logic, and the XML sitemap submission all need to be coherent. When those functions are split across different agencies or freelancers, the sitemap is usually the first thing that gets compromised.
Who This Guide Is NOT For
Businesses that already have a stable, well-structured site with under 20 pages. If your homepage, services, about, and contact pages are all interlinked and Google has indexed them without issues, this level of sitemap planning work is disproportionate. A quick audit is more useful than a full structural exercise.
One-page or portfolio sites. A single-page site with anchor links does not need a visual sitemap planning process. An XML sitemap for a one-page site adds little — Googlebot can reach a single URL from the domain and any external links pointing at it without one.
Teams that need a finished design by tomorrow. Good sitemap planning takes a few days of stakeholder input and iteration. If you are under a hard launch deadline with no room for structural review, this process will create more conflict than clarity in that specific sprint. Build a proper sitemap in the next cycle instead.
Operators who want to hand off all architecture decisions to a developer. A developer can build what you specify, but the decisions about which services deserve their own page, what the navigation labels should communicate, and which content to retire require input from someone who knows the business. The sitemap process only works if the business owner is a participant, not just an approver.
Frequently Asked Questions
What is the difference between a visual sitemap and an XML sitemap?
A visual sitemap is a flowchart diagram of your website's page hierarchy, used during the planning phase to align your team and identify structural gaps before any design work begins. An XML sitemap is a machine-readable file submitted to search engines like Google that lists your live, canonical URLs so they can be crawled and indexed efficiently. Most business owners need both, but at different stages — the visual sitemap comes first, the XML sitemap comes after the site is live.
Does every South African business website need an XML sitemap?
Not necessarily. Google states that sites with around 500 pages or fewer that are comprehensively linked internally may not benefit significantly from a sitemap, because search engines can discover pages by following links. For most South African business sites that fall within Google's documented threshold — around 500 pages or fewer, comprehensively linked internally — Googlebot can reach every page by following links from the homepage, and sitemap submission is a useful supplement rather than the foundation. That said, submitting a clean sitemap to Google Search Console and Bing Webmaster Tools is low-effort and provides useful discovery data, so it is worth doing regardless.
How many pages should a South African small business website have?
There is no single correct number — it depends on your services, your content strategy, and how your visitors search for you. A simple local service business (plumber, electrician, clinic) typically works well with 8–15 focused pages. A professional services firm (accountant, attorney) typically needs 20–40 pages once individual service pages and location or team pages are accounted for. More pages only help if each one answers a distinct question; thin, duplicated, or vague pages hurt both user experience and SEO.
What should I exclude from my XML sitemap?
Exclude any URL that is not the canonical, indexable version of a page you want ranked: pages carrying a noindex tag or directive, non-canonical duplicates, redirect URLs, 404 and 410 error pages, and pages behind a login or session parameter such as checkout steps or account pages. Page type is not the test — a paginated URL such as /page/2/ belongs in the sitemap when it is self-canonical and indexable, and should be left out only when you have noindexed it or canonicalised it to a view-all page. Review your sitemap output quarterly against the set of pages you actually want in search results.
How do I create a visual sitemap for my website?
Start by listing every existing page you have (or every page you plan to create for a new site). Group those pages by the question a visitor is trying to answer, not by your internal departments. Define your navigation depth (two levels is right for most SA business sites) and draw the hierarchy using boxes for pages and connecting lines in a free tool such as Miro, Whimsical, or Google Slides. Validate the result by tracing the path from homepage to your three most important conversion actions and confirming each path requires minimal navigation choices.
Ready to Plan a Website That Works for South African Visitors?
Growth Pulse Media handles website structure planning, responsive web design, and SEO-aligned URL architecture — all in-house, senior-led, and built for the way South African users actually browse. No obligation — we will get back to you within 24 hours.
Start the Conversation