Content Dependencies (Pages, Routes, Locations)

Marketplace content is made of connected documents. Understanding these dependencies helps you publish changes in the right order.

Why dependencies matter

Routes reference Pages.

Pages contain Sections.

Many Sections reference Locations.

If you publish only one piece, the live site may still use the last published version of the other pieces.

Route and Page

A Route controls the URL and layout.

A Route references one or more Pages.

If you publish a Route but the connected Page is still only updated in draft, visitors will see the last published version of that Page.

Practical rule:

• Publish the Page first, then publish the Route (or publish both)

Page and Sections

Sections are stored inside the Page.

When you publish a Page, all of its Sections publish together.

Navigation

Some Routes can override navigation.

If a Route uses a specific Navigation document and that Navigation has draft changes, the live site will continue using the last published navigation.

Practical rule:

• Publish navigation changes before you publish the Route that depends on them

Locations

Locations can affect multiple parts of the site:

• Location detail pages
• Locations and Reviews Sections
• Inventory context for some experiences

When you publish a Location update, any pages that use that Location data can refresh.

Redirects and site-wide configuration

Redirects and site-wide configuration documents often affect many pages.

Best practice:

• Batch related changes and publish once, instead of publishing many small updates

Recommended publish order (when multiple items changed)

1. Supporting documents (Navigation, Location, SEO settings)
2. Page
3. Route
4. Site-wide configuration

For a simple text change on a Page, publishing the Page is usually enough.

Helpful reference

• Sanity references (how documents connect): https://www.sanity.io/docs/reference-type