45. A Sitemap You Can Explain to a Non-Designer

A sitemap, for a small business, is not a secret file for search engines. It is a list of the pages you have decided to maintain. You should be able to explain it to someone who has never opened a design tool. If you cannot, the site is probably bigger than your team, or the names of the pages are private jokes. The explanation sounds like this. These are the pages a customer can open. This is why each one exists. This is who updates it. Anything that fails that explanation should not be built yet.

Draw it before you argue about colours. A single sheet of paper is enough for most SMEs. Boxes for pages, lines for how you reach them from the menu. You are not drawing the layout of buttons inside a page. You are deciding the inventory. Inventory is a founder topic. It decides what you must keep true when prices, hours, or staff change.

<>

Start with the pages a sale actually needs

Almost every local service business needs a homepage, a way to see the offer, a way to make contact or book, and a footer identity that can live on all of them. Many need a separate page per major service if the buyers differ. A cafe may need a page for the menu and a page for catering, because a lunch customer and a wedding planner should not read the same essay. A contractor may need residential and commercial split for the same reason. Add a page when the audience or the offer splits, not when a template has an empty slot.

About is optional. Use it when trust needs a story, a face, or a registration that does not fit the footer. A blog is optional. Use it when you will truly publish, not when someone said you should have content. A page you will not update is a page that will lie. Leave it off the sheet. You can add it later in a calmer month, which is a better plan than launching a diary nobody writes.

Name each box in customer language

Write the page name as the menu will show it, plus one sentence about what the page must answer. Servicing: what we service, where, and how to book. Prices: the packages and what is not included. Projects: eight examples with permission. If you cannot write the sentence, you do not need the page. You need a paragraph on an existing page. This is how a sitemap protects you from a twenty-page site that says less than a four-page site.

• Homepage with the offer in the first screen.
• One page for each offer that has its own buyer.
• Contact or booking, with the real hours.
• Any legal or privacy page your forms require.
• Optional proof, such as projects, only if you can maintain it.

Mark the languages on the same sheet if you publish more than one. A box that exists only in English should look different from a box that has a Malay twin. Otherwise you will promise a toggle you cannot feed. Mark who owns the box. The founder owns prices. The branch manager owns hours. A vendor owns nothing unless the retainer says so. Ownership is part of the map, because a page without an owner decays.

<>

Use the sheet when someone suggests a new idea

A new idea is not a new page until it fails to fit an existing box. A festival promotion usually fits a temporary landing page that is not in the main menu, and it leaves the sheet when the festival ends. A new permanent service gets a box and a name. Write it in pencil first. Live with it for a week. If you still need it, build it. This pause is not bureaucracy. It is how a non-designer stays in charge of scope when a meeting gets excited.

If you cannot point to a box and say why it exists, do not pay anyone to design it.

Bring the sheet to design meetings. When a proposal adds pages, ask which box they belong to. When a proposal removes the price page because the layout looked cleaner, ask where the price sentence went. Visual taste does not get to delete a business decision quietly. The sitemap is the agenda. The design is the rendering of the agenda.

<>

Keep the sheet next to the site after launch

Store a photo of the paper or a simple text list in the handover folder. Update it when a page is added or retired. Once a quarter, open every box and ask whether the page still matches the sentence. Retire pages that no longer do. A sitemap you explain to a new staff member in five minutes is a healthy one. If the explanation needs a whiteboard and a history lesson, the site has grown branches nobody pruned.

You can show this sheet to a developer without apology. Professionals prefer a founder who knows the inventory. It makes their quote shorter and their work cleaner. The sitemap is not a design skill. It is a list of promises your business is willing to keep in public. Keep the list short enough to say out loud.