Summary

Deployed the standard On This Page batch for pages/posts with sidebars on aguiarinjurylawyers.com. The target list was 130 records after excluding the FAQ hub that is documented to skip TOC. Across the first pass and cleanup passes, 123 unique pages/posts received or retained the canonical On This Page dropdown. Seven add candidates were intentionally skipped because the maintained renderer found fewer than three eligible body H2s after excluding snippets, CTAs, sidebar, FAQ, and related sections.

No homepage changes were made. Specialty/location/no-sidebar exclusions were preserved.

What Shipped

• Applied canonical sa-toc-start standard-batch-2026-05-19 blocks with label On This Page, dropdown chevron, no visible Show copy.
• Removed remaining legacy TABLE OF CONTENTS markup on kentucky-hands-free-law.
• Removed stale legacy TOC CSS from targeted pages where it could override the canonical block styling.
• Flushed WordPress cache and purged Cloudways application cache after each live apply phase.

QA Evidence

• Raw-source verification: qa/final-source-check-clean.json reports target_count: 130, ok: 130, failed: 0, canonical_present: 123, expected_skipped: 7.
• Playwright rendered QA: qa/playwright-final.json reports totalChecks: 12, passed: 12, failed: 0 across desktop 1440x1000 and mobile 390x844.
• Playwright pages covered: property damage reference form, truck accident add page, Kentucky accident replace page, hands-free legacy cleanup page, Amazon delivery CSS cleanup page, and homepage scope guard.
• Checks included: no horizontal scroll, no console errors, one visible TOC where expected, On This Page label, no Show copy, chevron present, summary focusable, TOC open/close interaction, no detected TOC overflow, homepage unchanged with no new TOC. Property damage reference form retained custom intake endpoint compatibility, hidden tracking fields, honeypot company field, and consent room.

Rollback

Rollback is available via the restore script and backups left on Cloudways and copied locally.

Remote restore command shape, dry run first:

cd /home/master/applications/fctbkwwahp/public_html && wp eval-file /home/master/restore-standard-on-this-page-2026-05-19.php mode=dry-run backup=/home/master/on-this-page-standard-batch-backup-2026-05-19.json

Original restore dry-run result: dry_run_restore_needed: 123, unchanged: 7, confirming the restore script can parse the original backup and identify the changed records.

Local artifact root:

/Users/samaguiar/Documents/Projects/admin/session_logs/on-this-page-standard-batch-2026-05-19/