Managing URLs (Paths)
Overview
A path object defines how a specific URL behaves. Paths live inside a Route under paths[].
A Route can have one path or multiple paths. Each path can have its own page assignment, sitemap and robots settings, and optional SEO overrides.
Path fields
value (required)
The URL path string, such as:
- /vehicles/search
- /contact-us
- /locations/downtown
Rules:
- Must start with /
- Cannot contain spaces
pages[]
The Page or Pages to render for this URL.
In most implementations today, a path has a single page entry. The array structure supports future scenarios where multiple Pages could be selected based on conditions.
include_in_sitemap
Controls whether this URL is included in /sitemap.xml.
Common reasons to disable:
- Utility pages
- Thank-you pages
- Internal or admin flows
disallow_robots
Controls whether search engines should be told not to index this path.
Common reasons to enable:
- Staging or private pages
- Duplicate content paths
- URLs that should exist for users but not appear in search results
overrideSEO and seo
When overrideSEO is enabled, you can set SEO fields specifically for this path. This is the most granular SEO override level in the system.
query_string
Adds a query string to the URL for tracking or parameter passing (for example, UTM tracking).
variables[]
Key/value pairs that can be passed as path variables. These are used for template-level configuration at the path level.
Multiple paths on one Route
When a Route contains multiple paths:
- All paths share the same Route layout selection.
- Each path can have its own page assignment.
- Each path can control its own sitemap and robots settings.
- Each path can have its own path-level SEO override and variables.
This allows one logical Route to serve multiple URLs with slightly different configuration.