SEO and Sitemap Settings
Overview
Marketplace SEO settings can be set at multiple levels. The system uses an inheritance chain, and the most specific setting wins.
Sitemap and robots settings are controlled per URL path.
SEO inheritance priority
From lowest priority (least specific) to highest priority (most specific):
- Project default SEO
- Location default SEO (for location-specific pages)
- Page SEO (only when the Page has SEO override enabled)
- Route SEO override (only when the Route has SEO override enabled)
- Path SEO override (only when the Path has SEO override enabled)
If a Path override is set, it will override Route and Page settings for that URL.
SEO fields you may see
SEO is defined through a shared seo object that can be used at multiple levels. Common fields include:
- metaTitle: The page title used for the HTML <title> tag
- metaDescription: The meta description shown in search results
- ogTitle and ogDescription: Open Graph values used when sharing links
- ogImage and ogAltImage: Social sharing image and its alt text
Some fields may be localized, which means you can provide different values per locale if your site uses multiple languages.
Sitemap settings
Sitemap inclusion is controlled per path with include_in_sitemap.
- When enabled, the URL can appear in /sitemap.xml.
- When disabled, the URL will be omitted from the sitemap.
Robots settings
Indexing rules are controlled per path with disallow_robots.
- When enabled, the path is added to robots.txt as a disallow rule.
- This signals search engines not to crawl or index the URL.
Recommended approach
- Use Project defaults for global SEO values.
- Use Page SEO when you want content-specific control that can be reused across URLs.
- Use Route or Path overrides when a specific URL needs unique SEO values.
- Use include_in_sitemap and disallow_robots to manage which URLs should be discovered and indexed.