Publishing Pipeline Scheduled vs Immediate

Description and use

A centralized content routing system assigns a single canonical URL to all content, whether published immediately or scheduled, eliminating duplicate URLs and broken links.

Problem

Managing consistent canonical URLs for content published both immediately and via scheduled posts across multiple platforms.

Outcome

Consistent canonical URLs across immediate and scheduled content, reducing duplicate content issues and improving SEO and user experience.

Workflow

• 1. Receive publish request (immediate or scheduled).
• 2. Generate unique content_id and canonical URL (https://apexgrid.dev/content/{content_id}).
• 3. Store content metadata (title, body, scheduled_time, canonical_url) in in‑memory content_store.
• 4. Return canonical URL to caller.
• 5. Scheduled jobs or immediate triggers fetch content via /content/{content_id} endpoint.
• 6. Ensure versioning and caching to prevent overwrites of already‑published posts.

Evidence

We’ve implemented a centralized content routing system that assigns a single, stable canonical URL to every piece of content, regardless of when or where it’s published.

Source

Managing a centralized content store adds complexity to our system.

Source