Skip to content
Tutorials Center
My learning

Topics

Lesson 8 of 37 ยท Concepts and Setup

Site Structure, Pages and Navigation

Plan a sitemap, page hierarchy, URLs and menus before you build. Learn static versus template pages, navigation patterns, breadcrumbs, redirects and how structure affects users and SEO.

The most expensive mistakes in a website happen before you open the editor. If the structure is wrong (pages in the wrong places, a menu with fifteen items, URLs that change every month), you will redo work in every page. Good structure comes from a sitemap: a plan of which pages exist, how they group together and how visitors move between them. Both Wix and Webflow let you create and reorder pages visually, but neither one will plan for you.

This lesson shows how to plan a site, translate the plan into pages and menus in each tool, and avoid the structure problems that hurt both users and search rankings.

Start with the visitor's questions

List the questions a visitor has when they arrive, then give each question a page. A bakery's visitors ask: What do you sell? Where are you? When are you open? Can I order? Who are you? That already suggests Products, Location, Contact (with hours), Order and About.

Then group related pages. Groups become menu sections and URL folders.

flowchart TD
  H["Home"] --> P["Products"]
  H --> V["Visit us"]
  H --> A["About"]
  H --> B["Blog"]
  P --> P1["Breads"]
  P --> P2["Pastries"]
  P --> P3["Cakes"]
  V --> V1["Location and hours"]
  V --> V2["Contact"]
  B --> B1["Post template"]

A sitemap tree. The Blog post is a template page that will generate many pages.

Three kinds of pages

Kind What it is Examples
Static page Built once, same for everyone Home, About, Contact
Template page One design reused for many items from a CMS Blog post, product, team member, event
Utility page Supports the site's operation 404 page, search results, privacy policy, password-protected page

In Webflow, template pages belong to collections and are created with the CMS (chapter 4). In Wix, they are dynamic pages connected to a collection in the Content Manager. Utility pages deserve attention too: a helpful 404 page that offers navigation and search keeps lost visitors on your site.

URLs and slugs

A URL is part of your user interface. Good URLs are short, readable, lowercase and stable.

  • Good: /products/sourdough
  • Poor: /page2?id=48271&ref=x

Rules of thumb:

  1. Use hyphens, not underscores or spaces.
  2. Keep URLs short and meaningful.
  3. Do not change a published URL without a redirect from the old address. A changed URL without a redirect gives visitors an error and discards the ranking the old URL earned.
  4. Mirror your structure: a page under Products gets a path beginning with /products when the tool supports folders.

Webflow gives each static page a slug and (in CMS template pages) a folder prefix such as /blog/ set by the collection. Wix lets you edit a page's URL slug in its SEO settings and uses a pattern for dynamic pages.

Primary navigation is the main menu, usually 4 to 7 items, shown on every page. Fewer is better: each extra item reduces the click-through to the others.

Other patterns:

  • Dropdowns for grouped pages. Make sure they work with a keyboard and on touch screens.
  • Footer navigation for legal pages, contact details and secondary links.
  • Breadcrumbs showing the path (Home > Products > Breads) help orientation on deep sites.
  • A call-to-action button in the menu (Order now) separates the primary action from ordinary links.
  • Mobile menu: both tools collapse the menu into a button on small screens. Test that the tap targets are big enough.

Because both builders offer reusable header and footer areas, you edit the menu in one place and it updates across the site. That makes a clear structure worthwhile: the menu reflects the sitemap.

Checking your sitemap with code

A sitemap is a tree, so we can validate it automatically. The stand-in below checks depth (how many clicks from the home page), duplicate slugs and menu length for a plan. It is a planning aid, not a feature of either builder.

JS Stand-in: audit a sitemap

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The result flags the repeated contact last segment (the same word is used in two different folders) and the page that is four clicks away. Neither is an error in the tool, but both are structure smells worth fixing.

Redirects

When you rename or delete a page, tell the web where it went with a 301 redirect (permanent). Both tools have a redirect manager in site settings: you enter the old path and the new path. A redirect plan is just a map.

JS Stand-in: resolve a redirect map

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Redirect chains (A to B to C) slow things down and a loop breaks the page entirely. Always point old URLs directly at the final destination.

Planning checklist

  1. Write the visitor questions.
  2. Draw the sitemap, with at most three levels.
  3. Mark which pages are static and which are templates.
  4. Decide the URL pattern for each group.
  5. Keep the main menu under about seven items.
  6. Plan 404, privacy and contact pages.
  7. Keep a list of URLs so you can add redirects if they change.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a template page?

    Template pages generate one page per CMS item, such as every blog post.
  2. 2. What should you set up after changing a published page's URL?

    A 301 redirect keeps visitors and ranking signals flowing to the new address.
  3. 3. Why keep the primary menu short?

    A focused menu helps visitors decide quickly.
  4. 4. What is wrong with a redirect chain A to B to C?

    Each hop takes time, so point old URLs straight at the final destination.

Summary

  • Plan the sitemap from visitor questions before opening the editor.
  • Distinguish static pages, CMS template pages and utility pages.
  • Use short, lowercase, hyphenated, stable URLs and add 301 redirects when paths change.
  • Keep the main menu to roughly seven items and the depth to about three levels.
  • Both tools let you reuse headers and footers, so the menu is edited once.

Next: Brand Setup: Colors, Fonts and Assets