Skip to main content

Publishing and Content Updates

TurboCache connects normal WordPress publishing activity to a targeted page refresh. Editors do not need to clear the cache after routine content changes.

Publishing a new page or post​

After you publish new content:

  1. WordPress records the change and notifies TurboCache.
  2. TurboCache schedules the new URL and related listing pages for refresh.
  3. The frontend generates the page and TurboCache stores a durable copy.
  4. The updated copies become available through the CDN.

A brand-new URL can be served by the frontend before its durable copy has been created. TurboCache then adds it to the managed page snapshot in the background.

Updating existing content​

An edit can affect more than the page being edited. For example, changing an article's headline, section, tags, author, or publication date can also affect:

  • the homepage;
  • category, tag, author, and date archives;
  • paginated listing pages;
  • feeds; and
  • other pages that display related or recommended content.

TurboCache uses the dependencies declared by each rendered page to determine which copies need to be replaced. It refreshes the affected pages before retiring their previous cached versions.

Updates are intentionally gradual

Visitors may briefly see the previous published version while replacement pages are generated. The site remains available during this period, and different related pages may update at slightly different times.

Previewing drafts​

WordPress previews bypass the public cache. An authenticated editor should see the latest draft even while public pages still show the currently published version.

If a preview appears stale, first confirm that you are using the WordPress preview link and are still signed in. A normal public URL is expected to show only published content.

Unpublishing or deleting content​

Normal unpublish and delete actions notify TurboCache so obsolete page copies and related listings can be processed. If content must be removed immediately for legal, privacy, or security reasons, do not rely on a routine update: contact Organic Support and identify the exact URLs that must become unavailable.

Changes that may need additional setup​

TurboCache automatically understands the standard relationships configured for your site. Contact Organic before introducing:

  • a new public custom post type or taxonomy;
  • a new archive or listing route;
  • a module that places the same content on many unrelated pages;
  • URL behavior controlled by new query-string parameters; or
  • a publishing process that bypasses standard WordPress lifecycle events.

Organic can verify that the new pages declare the correct dependencies and are included in the site's page inventory.