Summary of work done

• Ran scripts/audit_recent_wp_content.py from the configured project workspace using /Users/samaguiar/Documents/Projects/.credentials/vault.env.
• Wrote outputs to outputs/recent-wp-content-audit-2026-05-19/.
• Audit completed with 0 pass, 12 warn, 67 fail, 79 items audited, and 86 media URLs checked.
• The script explicitly caught the requested drift classes: section 12B banned FAQ patterns, TOC structure drift, snippet/internal-phrase drift, FAQ visible/schema mismatch, and sidebar CTA plus visible-phone drift.

Main failures found

• Missing TOC was the most common failure class.
• Missing snippet or missing .sa-snippet before long-form content was common on newer draft and preview pages.
• FAQ visible/schema mismatch appeared on multiple pages where the schema had extra questions or the visible FAQ set drifted.
• Sidebar CTA drift showed up as visible phone numbers in CTA blocks, label drift away from the expected Call Now pattern, and a few missing .sa-sidebar-cta blocks.
• Section 12B banned FAQ patterns were still present on at least the motorcycle page, including comparative fault and statute-of-limitations phrasing.

Output artifacts

• outputs/recent-wp-content-audit-2026-05-19/recent-wp-content-audit.json
• outputs/recent-wp-content-audit-2026-05-19/recent-wp-content-audit.csv
• outputs/recent-wp-content-audit-2026-05-19/recent-wp-content-audit.md

Safest next repair path

• Keep this run read-only unless a target is clearly reversible and already covered by existing repair rules.
• The safest follow-on is a focused content repair queue for the highest-risk pages first: the pages with section 12B FAQ hits, sidebar visible-phone drift, and FAQ visible/schema mismatch.
• After those, fill missing TOC and snippet structure on the pages that are clearly missing the canonical long-form scaffolding.

Handoff notes