Default vs Override SEO

Overview

Marketplace supports SEO at multiple levels so you can balance consistency with flexibility.

Most sites should rely on a strong default SEO baseline, then use overrides only where a page or URL needs a distinct search identity.

The SEO inheritance chain

SEO is resolved through a priority chain. The most specific override wins.

A common chain (least specific to most specific) is:

1. Project default SEO
2. Location SEO (for location pages)
3. Page SEO
4. Route SEO override
5. Path SEO override

Not every site uses every level every day, but understanding the hierarchy helps you avoid conflicting settings.

Default SEO

Default SEO is your brand-level baseline.

Use default SEO for:

• Consistent brand name and positioning
• A fallback title and description for pages you have not customized
• A default Open Graph image that represents your dealership or dealer group

If default SEO is missing or weak, many pages will inherit low-quality titles and descriptions.

When to override

Page override

Use page override for named content pages where you want unique titles and descriptions.

Route override

Use route override when the same Page content is served at multiple URLs and you want different SEO per URL.

Path override

Use path override when a route has multiple paths and each path should target different keywords.

This is common for vanity URLs that point to inventory or search experiences.

Recommended approach

• Start with strong default SEO.
• Add page-level SEO for your most important content pages.
• Use route and path overrides when URL-specific targeting is required.
• Keep overrides intentional. Too many overrides can make SEO harder to maintain over time.