Route-Level Layouts (Search, Product, etc.)
Overview
The layout field on a Route selects the frontend template used to render a URL. The layout determines what modules are shown on the page and how content is sourced.
Choosing the right layout is one of the most important Route decisions because it defines the structure of the rendered experience.
Layout options
Default content layout (contentBlockDefault)
Use for general content pages.
How it behaves:
- The page renders a standard structure (header, main content, footer).
- The main content area renders the Page content blocks in order.
Use cases:
- Homepages
- About pages
- Landing pages
- Campaign pages
Location Details
Use for dealership location detail pages.
How it behaves:
- Renders a predefined module structure sourced from Location data.
- Does not rely on Page content blocks for the main layout.
Use cases:
- Location pages with hours, address, and location-specific modules
Product layouts
Use for vehicle detail page experiences.
How they behave:
- Render a predefined vehicle detail structure.
- Use inventory and product data as the primary source.
Use cases:
- Vehicle detail pages
Search layouts
Use for inventory search and listing pages.
How they behave:
- Render an inventory results experience.
- Search with side filter includes a persistent filter panel on larger screens.
Use cases:
- Search results pages
- Inventory listing pages
Content blocks and layouts
Only the default content layout renders author-managed Page content blocks as the primary page content. Specialized layouts typically render a predefined structure, even if a Page is referenced.
Practical guidance
- Choose the default content layout for pages where your team will author and reorder content blocks.
- Choose specialized layouts for experiences that depend on structured data, such as inventory search, product detail pages, and location pages.
- If you change a Route layout after launch, review the rendered URL carefully, because the entire page structure may change.