SEODrafts

Cloudflare caching for SEO content publishing

Keep public pages fast without serving an old article after deployment. The safe sequence is deploy, verify, purge affected URLs, and warm them again.

Keep API, dashboard, login, preview, and personalized hosts outside the public HTML cache rule. SEODrafts can use Cloudflare OAuth for limited zone access; copied long-lived global API keys are not required.

The publishing sequence

01

Publish

Write the approved content and record the affected URL manifest.

02

Verify deployment

Use a cache-busted request to confirm that the new public route exists at origin.

03

Purge and warm

Invalidate only the article, relevant index pages, sitemap, robots.txt, and llms.txt, then request them again.

Scoped CI fallback

CLOUDFLARE_API_TOKEN=${{ secrets.CLOUDFLARE_API_TOKEN }}
CLOUDFLARE_ZONE_ID=${{ secrets.CLOUDFLARE_ZONE_ID }}
npx --yes @wotaso/seo-blog-admin-cli cache-revalidate --if-configured

Use a zone-scoped token with cache-purge permission only. Never use the Global API Key, never print credentials, and never run “purge everything” for a single article update.

Publish through the stack you control.

Keep review in SEODrafts and infrastructure ownership in your website.

Add my website