Notion CMS: publishing retail content from Notion

Assess Notion as an editing and publishing source for retail guides, checking permissions, supported delivery and how corrections reach the public page.

Notion CMS publishing works in two ways: publish a page with Notion Sites, or use the Notion API as the editing source for a separate website. Notion Sites suits simple public guides with direct editing. An API-delivered site gives you control over the storefront design and publishing process, with development and maintenance work attached.

Define the Notion publishing arrangement

Separate private workspace pages from public content and from the website that delivers it. Sharing an internal guide with your team doesn’t decide what a customer can read on an external site.

ArrangementWhat you editWhat the customer receivesWho owns delivery
Internal workspaceNotes and draft policiesAccess only through the page’s sharing permissionsWorkspace administrators
Notion SitesA page published from NotionThe public Notion SiteNotion hosts the site and your team controls publication
API-delivered websiteContent selected for a connection to readYour website’s rendered versionYour developer or site provider

Notion Sites publishes pages to the web and updates them automatically as you edit. Subpages are published by default too, so review the whole page tree before publication. Keep internal supplier notes and draft policy discussions outside that tree.

An external website can read selected Notion content through an application programming interface (API). Your site then chooses the layout and public address. Connecting Notion to that site requires a renderer and a delivery process. It doesn’t happen because an editor copies a workspace link into the store.

Keep live prices, stock and orders with the systems that own those records. Use Notion for editorial material such as product care advice and buying guides. If your requirements include account-specific content, define the customer sign-in and access rules separately when comparing content management systems.

Check editing and delivery support

Check how the chosen arrangement handles the content your editors actually publish, including corrections and media. A formatted Notion page and an external rendered page can behave differently.

For Notion Sites, inspect a private copy before placing approved content on the published page. Automatic updates mean that editing the live source changes what customers receive. If you need a separate approval step, keep draft writing separate and assign someone to transfer approved changes.

For API delivery, Notion’s page content guide describes content as typed blocks. The API supports a subset of block types. An external renderer needs a defined response when it encounters an unsupported block, such as stopping publication with an editor-facing error. Quietly omitting part of a policy can change its meaning.

The block retrieval endpoint returns one level of children at a time and uses pagination. Nested content needs additional requests. Include a nested list and a longer guide in the integration check so a successful first response doesn’t conceal missing content.

Give the publishing connection only the capabilities it needs, normally read access for an editorial source. Adding a connection to a parent gives it access to descendants within its capabilities. Select the parent carefully. A publishing filter in your website must decide which readable pages are approved for public delivery.

Treat media as part of the delivery design. Notion’s file retrieval documentation says uploaded-file URLs expire after one hour. An external site must refresh those links or deliberately copy approved public media to storage it controls. Otherwise an image or care PDF can work during preview and fail later. Apply the same publication and withdrawal rules to any copied file.

Define what starts a refresh and who notices a failed one. Notion webhooks notify your application about changes. The application still fetches the content and updates the website. Trigger publication only for approved content, and decide how to recover from a missed event or failed build. A scheduled refresh is another implementation choice.

Notion’s request limits depend on the workspace plan, with additional workspace and endpoint limits. Queue requests and honour Retry-After when requests are throttled. Fetching every guide for every shopper visit makes the publishing connection part of storefront availability. Serving a controlled published copy separates those jobs, but also creates a copy you must update or withdraw.

Compare the operating cost

Notion’s Sites feature table includes public Sites on the Free plan. Customisation requires a paid plan, and connecting an existing custom domain needs a paid plan plus a domain add-on. Include domain registration separately.

For an external site, budget for hosting and the renderer, plus refresh jobs, media storage and maintenance. Record who owns the integration if an editor changes a block type or Notion changes its API. Compare that total with the cost of editing directly in your existing website.

Verify access and a published change

Prove that a private draft stays private and an approved correction reaches the customer through the chosen publishing path. Use harmless test content and a non-production destination for this check.

For a hypothetical retailer, correct an appliance care guide that links to an outdated cleaning PDF. Give the draft a recognisable test sentence. Record the intended public page and the replacement file before starting.

  1. Save the draft without approving it. Open its direct link while signed out and check the external site, including its search results and any generated page data. The test sentence must remain private.
  2. Inspect the proposed page on a phone and a desktop. Follow every internal link and open the replacement PDF. For API delivery, include nested blocks and confirm that all approved text appears.
  3. Approve the correction. On Notion Sites, transfer it to the published source. On an external site, run the approved publishing process and wait for its refresh to complete.
  4. Reload the customer page in a fresh session. Confirm that the corrected advice and replacement PDF appear together. Recheck API-delivered media after the original one-hour file link has expired.
  5. Withdraw the test page and revoke its source access. Check the old public URL and direct file links, then clear or remove external copies through your site’s withdrawal process.

Notion warns that unpublishing a Site can leave the page accessible if general access still allows anyone with the link. Remove that public-sharing permission as well. For an external website, revoking the connection prevents future authorised reads, but your site must also stop serving previously copied content.

Choose Notion Sites when direct public editing meets your approval needs. Choose API delivery when your team can maintain the renderer and the complete correction and withdrawal process. Keep the arrangement only if a customer gets the approved guide and a private draft stays out of every public copy.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup