Sam approved Option A, so I continued the Cloudways/Cloudflare Enterprise edge path for the two remaining Screaming Frog issues.
I ran the Cloudways API app cache purge for production server 1615235, app 6360875. The purge returned operation flex-87202333, and the operation status later showed completed.
I confirmed the production Cloudways cloudflare-helper plugin is configured with its Cloudways FPC environment and ran URL-level Cloudflare helper purges for:
https://aguiarinjurylawyers.com/about-us/bigger-share-guarantee/https://aguiarinjurylawyers.com/contact-us/Both returned success.
I retested Bigger Share Guarantee through direct origin and public edge. Direct origin remains clean: the URL returns HTTP 200 and resolves to WordPress page ID 9286. WordPress source also remains clean: wp post url 9286 is the correct URL, and url_to_postid returns 9286.
Public Cloudways/Cloudflare edge still returns a fresh cf-cache-status: MISS 301 from /about-us/bigger-share-guarantee/ to /about-us/bigger-share-guarantee-kentucky/, and that target returns 404.
I also tested a narrow reversible Rank Math hypothesis: row 315 was backed up, temporarily disabled with its cache/meta entry cleared, purged, retested, and then rolled back when it did not change the public edge behavior. Rollback verified row 315 active, page meta restored, and cache entry restored.
For Contact Us, WordPress still resolves /contact-us/ to page ID 56, but public curl/Screaming-Frog-style requests still receive HTTP 403 with cf-mitigated: challenge. The Cloudways/Cloudflare helper purge does not affect that challenge.
QA note: /Users/samaguiar/Documents/Projects/admin/_qa-queue/2026-05-12.md
Support packet: /Users/samaguiar/Documents/Projects/admin/support-packets/cloudways-bsg-contact-edge-2026-05-12.md
Rank Math test backup: /Users/samaguiar/Documents/Projects/admin/backups/bsg-rankmath-redirect-20260512_134421
Fresh crawl: /Users/samaguiar/Documents/Codex/screaming-frog/2026-05-12
Ingest report: /Users/samaguiar/Documents/Codex/screaming-frog-ingest/2026-05-12.md
The remaining failures are not resolved by WordPress cache, Cloudways app cache purge, Cloudways Cloudflare helper URL purge, or a reversible Rank Math auto-redirect test. The best current diagnosis is managed Cloudways Autonomous / Cloudflare Enterprise edge behavior: