How Routes Connect to Pages

Overview

Routes connect URLs to the content and templates that render your site. The connection is intentionally multi-step so that URLs, templates, and content can be managed independently.

The connection chain

The full chain is:

Route → paths[] → path.pages[] → pathPage.page → Page → contentBlocks[]

Step-by-step

1) Route to Path

A Route includes one or more path objects under paths[]. Each path represents a URL entry point (for example, /about-us). Most Routes have a single path, but a Route can support multiple paths when multiple URLs should render the same experience.

2) Path to PathPage

Each path includes a pages[] list of pathPage objects. Today, most implementations use a single pathPage at 100% of traffic.

This structure exists to support conditional page selection in the future (for example, A/B testing). You may see fields that reflect this design, even if they are not currently configurable in your Studio UI.

3) PathPage to Page

Each pathPage references a Page document. The Page is where the actual content is authored.

Because a Page document is a reusable piece of content, the same Page can be referenced by multiple Routes or multiple paths. This allows one set of content to be used for more than one URL.

4) Page to Content Blocks

A Page typically contains an ordered list of contentBlocks[]. These blocks are what get rendered when the Route layout is set to the default content-block layout.

If a Route uses a specialized layout (such as search, product, or location layouts), the page content blocks may not be used because those layouts render a predefined module structure.

What to remember

• The Route defines the URL behavior and layout choice.
• The Page defines the content.
• Paths let one Route support one or more URLs.
• The pages[] array exists for future flexibility, even if you only use one Page per path today.