Sam asked for a targeted live cleanup on https://aguiarinjurylawyers.com/abogado-lexington/: remove the Lexington eyebrow at the top of the page and avoid a double header. The page is a published WordPress page, ID 63356, slug abogado-lexington.
I authenticated to WordPress REST, read the live raw page content, and confirmed the issue was in the page body. The hero included <div class="hero-eyebrow">Lexington, Kentucky</div>, and the H1 was visually split as Abogado de Accidentes de Auto <em>en Lexington</em>. I backed up the raw content, removed the eyebrow, and changed the H1 to one source heading: Abogado de Accidentes de Auto en Lexington.
After checking the rendered page, I also confirmed the double-header issue came from an embedded page-level call-bar navigation block inside the content while the WordPress theme already renders the site header. I made a second REST-backed update to remove that embedded call-bar block. The page stayed published after both updates.
First backup before the eyebrow and H1 edit: /Users/samaguiar/Documents/Claude/wp-content-backups/abogado-lexington-2026-05-22-171104-pre-edit.html.
Second backup before embedded call-bar removal: /Users/samaguiar/Documents/Claude/wp-content-backups/abogado-lexington-2026-05-22-171446-pre-callbar-removal.html.
Rollback path: POST either backup file back to WordPress REST page 63356 as content, preserving the published status by omitting the status field.
Public plain URL and cache-busted fetches both returned HTTP 200 with x-cache: MISS and cf-cache-status: DYNAMIC. Both public HTML checks confirmed: no <div class="call-bar">, no hero-eyebrow">Lexington, Kentucky, no split H1, one H1, and the single H1 text present.
Browser QA confirmed: callBarCount: 0, heroEyebrowCount: 0, h1Count: 1, H1 text Abogado de Accidentes de Auto en Lexington, no old eyebrow text, no split hero H1, and no horizontal overflow.
Desktop and mobile screenshot QA artifacts are saved at /Users/samaguiar/Documents/Codex/qa-screenshots/abogado-lexington-2026-05-22-final/. Final screenshots: /Users/samaguiar/Documents/Codex/qa-screenshots/abogado-lexington-2026-05-22-final/abogado-lexington-desktop.png and /Users/samaguiar/Documents/Codex/qa-screenshots/abogado-lexington-2026-05-22-final/abogado-lexington-mobile.png. Final JSON QA: /Users/samaguiar/Documents/Codex/qa-screenshots/abogado-lexington-2026-05-22-final/qa-results.json.
The first edit attempt stopped before posting because the narrow replacement pattern expected a different indentation. No live write happened on that attempt. The Cloudways API purge path returned HTTP 403 during access-token creation. The public content was still verified fresh through both plain and cache-busted fetches, so the page cleanup was not blocked.
The live page is updated and verified. The remaining observations are improvement items, not blockers to the requested cleanup: Cloudways API purge credentials need reconciliation, the page logs a pre-existing zaraz is loaded twice console error, and the deploy workflow could benefit from a check that flags embedded page-level nav blocks on pages where the theme header already renders.
Context: this page had a standalone landing-page call-bar embedded inside WordPress, while the theme already rendered the top header.