# Static Publisher Targeted Content Sync

Targeted content sync publishes the public effects of WordPress content changes without crawling the complete site. It is available with an active Professional or Agency subscription, like incremental publishing, and is driven by a saved scheduler rule plus the external `@smart-cloud/publisher-exporter` queue runner.

A rule selects public post types and can reconcile their post URLs, post-type and taxonomy archives, the posts page, optional author and date archives, pagination, and the sitemap chain. Explicit site-relative listing routes cover Query Loop pages or other listing surfaces that WordPress cannot infer reliably. WordPress journals publish, update, taxonomy, sticky, unpublish, trash, delete, permalink, author, and publication-date effects for the selected scope.

A successful normal full or incremental publish must establish a verified baseline and trusted manifest first. Theme, plugin, permalink, sitemap, rewrite, scope, or deployment-target changes make that baseline stale and require another normal publish. Content sync stops safely when the baseline is missing or stale.

The runner claims a closed journal range. Demand is coalesced, later changes become trailing work, and retry checkpoints preserve the same range with bounded backoff. The committed cursor advances only after deploy, CloudFront invalidation, and public verification succeed. If an operator abandons a retry, its local plan is cleared but the journal range remains unacknowledged and discoverable by a later scheduler tick.

Trash, unpublish, delete, and permalink changes use the last exact public URL recorded before the transition. WordPress `__trashed` aliases are rejected. Remote tombstones are limited to paths already owned by the trusted manifest, so unrelated or remote-only S3 objects are preserved.

Multisite tracking is opt-in. By default, the rule covers only the site that owns the Publisher runtime. Full-network tracking requires WordPress multisite, network activation of SmartCloud Static Publisher, and same-origin path-based subsites that share the output namespace. Enabling it changes the scope and therefore requires a new normal publish. Domain-mapped or independently hosted subsites need separate Publisher targets.