Sanity useCdn true vs false for a read-after-publish content page

Short answer

For a public article that is revalidated immediately after a publish, the only guarantee that the reader will never see the pre‑publish version is to read from the live origin. useCdn: false guarantees freshness, while useCdn: true can return a stale copy for an unpredictable propagation window.

What is documented

• useCdn: true uses apicdn.sanity.io, an eventually consistent edge cache.
• useCdn: false hits the Sanity API origin and always returns the most recent committed document.
• The Sanity client is instantiated per‑use, so you can mix modes inside one application.

Practical recommendation for your setup

1. Keep a default client with useCdn: true for lists, navigation, and other staleness‑tolerant reads.
2. Create a second client with useCdn: false and use it inside the article page’s data fetch (e.g. getStaticProps with ISR or a dedicated API route). Because Next.js revalidates on publish, the origin query happens once per revalidation, not once per reader.
3. Optionally, add a Sanity publish webhook that calls the CDN purge endpoint (https://www.sanity.io/docs/cdn-purge) or triggers your Next.js revalidation endpoint. This shrinks the stale window, but the guarantee remains only when you use the origin client.

import {createClient} from "@sanity/client";

const base = {
  projectId: process.env.SANITY_PROJECT_ID!,
  dataset: "production",
  apiVersion: "2024-01-01"
};

export const cdnClient = createClient({...base, useCdn: true});
export const originClient = createClient({...base, useCdn: false});

Can listen or webhooks replace the guesswork?

• Webhooks can trigger revalidation and purge, but they do not automatically bypass the CDN for a single request.
• client.listen notifies you of a mutation, but the subsequent query still uses whatever useCdn setting you give it. It is useful for preview UIs, not for guaranteeing freshness to anonymous readers.

Verification steps

1. Publish a change, then query the same document immediately with both clients and compare the _updatedAt timestamps.
2. With a purge webhook, measure how long after publish a CDN‑served query returns the new timestamp.
3. In Next.js, add revalidate: 1 to getStaticProps and confirm that a page refresh after publish shows the updated content without manual purging.