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 inclusion, and variables. Use Page or Route SEO for ordinary content pages.
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
Do not rely on this flag to control crawling or search indexing. Contact Auto Genius Support for indexing changes and verify the public result.
Contact Support when you need help with:
Staging or private pages
Duplicate content paths
URLs that should exist for users but not appear in search results
overrideSEO and seo
Path-level SEO fields are present in Studio, but they are not applied to ordinary content pages. Use Page SEO or an enabled Route SEO override. Use separate Routes when URLs need different SEO.
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 inclusion.
Each path can have its own variables. Configure ordinary content SEO on the Page or Route.
This allows one logical Route to serve multiple URLs with slightly different configuration.