Skip to content

Mass Batch Deploys

Status: Ongoing (several major pushes complete) Project: Website · SEO

What this is

Large-scale content rewrite + deployment campaigns that hit hundreds of pages at once via the WordPress REST API. Distinct from daily or small-batch work. These are the heavy pushes that rewrote significant fractions of the site in single sessions or short runs.

Major pushes

Fix-Batch Deployment: 50 Broken Pages Rewritten and Pushed Live (March 1, 2026) — 50 broken pages rewritten and deployed in a single pass. First large-scale fix batch.

52-Page Gap Deployment: Content Rewrite Push (March 2, 2026) — Filled a 52-page content gap identified in the audit.

100-Page Rewrite Deployment: Full Site Content Push (March 2, 2026) — The biggest push: 100 pages rewritten and deployed in one session.

Trust Bar Full Rollout: .sa-trust-strip to .sa-trust-bar (316 Pages) — CSS class migration from .sa-trust-strip to .sa-trust-bar across 316 pages, driven by a WPCode + REST API combination.

Sitewide Compliance Enforcement: 459 Pages/Posts Fixed + CTA Banner Removal (April 2026) — covered separately in Sitewide Compliance Enforcement.

Emergency Site Restoration: Rogue Agent Cleanup + Car Accident Page Upgrade — not a planned push but an emergency one, fixing damage from a rogue agent session that had modified many pages.

How these run

  • Pre-deploy diff against the existing live content
  • Batch upload via REST API, chunked by ~10 pages per API batch
  • Cloudflare bypass via Chrome User-Agent header
  • Post-deploy QA: visual spot-check, schema validation, 500-error watch
  • Rollback plan: git history of the rendered HTML snapshots before any deploy

Pain points

  • Rate limiting from Cloudways/WordPress on large batches
  • wpautop bug breaking blocks on some pages mid-batch
  • Protected pages (post SA Template v3.1) need to be filtered out or the deploy overwrites Sam's manual edits

Sources

See also