Page Not Showing

Overview

If a page is not showing, Marketplace resolves the URL through a fixed sequence. The fastest way to troubleshoot is to walk that sequence in order.

How Marketplace resolves a page

Marketplace resolves an incoming URL in this order:

1. Redirect check
2. Route resolution
3. Page data fetch
4. Layout rendering

1) Redirect check

The incoming URL is checked against the Redirects document in Sanity.

If a redirect rule matches, the visitor is sent to the redirect destination and no page renders at the original URL.

2) Route resolution

If no redirect matches, the URL is matched against Route documents in Sanity.

If no Route path matches the URL, the result is a 404.

3) Page data fetch

If a Route matches, Marketplace fetches the route’s configured data from Sanity, including:

• Layout type
• Linked Page document
• Content blocks
• SEO configuration
• Navigation references

4) Layout rendering

The layout engine renders HTML for the selected layout using the fetched data.

Causes and fixes

The route does not exist in Sanity

A URL only resolves if there is a Route document with a path entry for that exact URL.

What to check:

• In Sanity Studio, open Routes and search for the path.

Fix:

• Create a Route with the correct path.
• Set the correct Layout type.
• Link the Route to the correct Page document.

The path is malformed

Paths must:

• Start with a leading slash
• Contain no spaces

Examples that do not resolve:

• about-us
• /about us

Fix:

• Edit the path field on the Route document so it starts with / and contains no spaces.

The Page is not published

Routes reference Page documents.

If the linked Page is a draft, it will not render on the live site.

Fix:

• Open the Page document in Sanity Studio.
• Click Publish.

A redirect is intercepting the URL

A redirect rule that matches the path takes precedence over route resolution.

Fix:

• Open the Redirects document in Sanity Studio.
• Remove or correct the conflicting redirect entry.

Cache invalidation has not completed yet

Publishing a new route or path triggers cache invalidation with a built-in delay.

What to expect:

• A route created moments ago can still return a 404 while cache invalidation is in progress.

Fix:

• Wait 2 to 3 minutes and try again.