Before a site is built, there's no live URL structure to crawl — an XML sitemap generator has nothing to work with yet. Planning a new site's architecture is a design exercise, not a crawling one. Here's a practical workflow for that phase, and what to hand off once the site actually launches.
Start With the Pages You Know You Need
List every page you already know the site needs — homepage, core product or service pages, an about page, contact. Don't worry about hierarchy yet. Getting the full page list down first prevents you from designing a beautiful tree structure around an incomplete set of pages.
Group Pages Into a Hierarchy
Organize the page list into parent-and-child relationships — which pages are top-level navigation items, and which sit underneath them. Two rules keep this manageable:
- Keep top-level navigation narrow. More than seven or eight top-level items usually means the grouping needs another pass, not a wider menu.
- Avoid unnecessary depth. A page buried four or five clicks from the homepage is a page most visitors will never find. Flatten where you can.
Use a Visual Canvas, Not a Spreadsheet
A hierarchy is much easier to evaluate — and to get stakeholder sign-off on — as a diagram than as an indented list in a document. A dedicated visual planning tool lets you drag pages into place, see the whole structure at once, and share a link for feedback without anyone needing to install anything. For a full comparison of the visual planning tools built for exactly this, see how sitemapgenerator.ai compares to Lucidchart for site-planning diagrams.
Get Sign-Off Before Development Starts
Structure changes are cheap on a diagram and expensive once templates, navigation, and content are built. Share the visual sitemap with stakeholders and get explicit agreement on the hierarchy before development begins — moving a page in a diagram takes seconds; restructuring a built site touches navigation, internal links, and URLs all at once.
Handing Off to Development
The approved visual sitemap becomes the reference document for developers building out navigation and routing — it's the source of truth for what pages exist and how they nest, independent of final URL slugs or CMS structure.
After Launch: Switch to a Crawl-Based Sitemap
Once the site is live, the planning diagram has done its job. From here, what you need is an XML sitemap generated from the real, live URL structure — not the plan, but what actually got built — plus ongoing monitoring as pages get added or removed. See how to create an XML sitemap for that next step, or what a visual sitemap is for the fuller picture of planning vs. live-site visualization.