Skip to content

How to get sitemap approval from a website client

By The Onbo team · Updated

Short answer

Draft the sitemap from the client's questionnaire answers, walk the decision maker through it, and get written approval of a specific version before design starts. Record who approved it and when, link it to the agreement, and treat any page added afterwards as a change request with its own price and date.

The sitemap decides how big a website project really is: how many pages are designed, built, filled with content and tested. When it changes after design starts, every later phase moves with it. A sitemap that’s clearly approved at the start gives you and the client a shared reference point, so a new page request becomes a simple conversation about scope instead of a source of tension.

Why does sitemap approval matter?

Without an approved sitemap, the project’s scope is whatever the client last remembered. Pages appear during design reviews (“we’ll need a careers page too”), content plans go out of date, and the timeline slips without anyone deciding it should. With an approved sitemap, both sides know what’s included. Additional pages are still welcome, but they’re quoted and scheduled like any other change, and nobody is surprised by the cost.

How do you prepare a sitemap clients can approve?

Build the first draft from the client’s questionnaire answers, so it reflects their goals rather than a generic template. Keep it readable for a non-designer: a simple list or tree of pages, each with a one-line purpose and, where useful, the main sections it will contain. Mark which pages are new, kept from an existing site or merged. And note who will supply each page’s content, because a page without an owner is a page that will be late. The web design client questionnaire collects the answers you need for this draft.

Page Purpose Main sections Content owner
Home Explain the offer and route visitors Hero, services, proof, contact Studio drafts, client approves
Services Describe each service One section per service Client
About Build trust Story, team, values Client
Contact Make enquiries easy Form, details, map Studio

How do you get it approved?

Walk the client’s decision maker through the sitemap on a short call or a recorded walkthrough, explaining why each page exists. Invite changes then, while changes cost nothing. Once agreed, send the final version and ask for written approval of that specific version. A reply such as “Approved, version 2” from the right person is enough; what matters is that the version, date and approver are recorded. Attach it to the agreement or project record so it’s easy to find later.

For example, a two-person web studio might draft a nine-page sitemap from a client’s answers, review it on a twenty-minute call with the client’s managing director, and receive written approval the same day. When the marketing manager asks for a separate events page during design, the studio points to the approved version, quotes the extra page, and the client approves the change in one reply.

How do you handle pages added later?

Treat every new page the same way: confirm what it’s for, check whether it replaces or adds to an approved page, quote the extra design, build and content work, and update the timeline. Start only once the change is accepted in writing, and add it to the sitemap as a new version. Clients rarely object to this when the original approval was clear; they object when scope rules appear for the first time mid-project.

Keep every approved version, not just the latest. When a question about scope comes up months later, being able to show what was agreed and when settles it quickly and fairly.

A sitemap approval checklist

  • Draft built from the client’s questionnaire answers
  • Each page has a one-line purpose
  • Main sections listed where helpful
  • New, kept and merged pages marked
  • Content owner named for every page
  • Reviewed with the final decision maker
  • Written approval of a specific version
  • Approval date and approver recorded
  • Linked to the agreement or project record
  • Later pages handled as change requests

Sitemap sign-off is part of the website project kickoff, and the dates that follow from it belong in a website project timeline.

Once the sitemap is approved, handle new pages with a website change request form.

Where Onbo fits

Onbo collects what you need before drafting the sitemap. After the client accepts your agreement and pays the deposit, they answer your website questionnaire with autosave and upload existing content and brand files into your Google Drive. You get a Markdown hand-off brief to draft the sitemap from. Try it free for 30 days; see pricing.

Questions

How do I get a client to sign off a sitemap?

Show a clear page list with a one-line purpose for each page, review it with the person who has final say, and ask for written approval of that version before design begins.

What if the client adds pages later?

Treat new pages as change requests: confirm what's being added, quote the extra design, build and content work, and update the timeline before starting.

Who should approve the sitemap?

The client's final decision maker. Feedback can come from several people, but approval should come from the person who can't later overrule it.

Start your next client relationship with everything in place.

Collect the first steps in one link. Try Onbo free for 30 days, no card required.

Start free