Objective: check aguiarinjurylawyers.com for structured-data regressions and repair any real source issue.

What happened:

• Homepage root organization graph stayed valid.
• Representative article page still had one valid root organization node with Louisville PostalAddress.
• A separate inline Article JSON-LD block on post 12390 failed to parse.
• Root cause: the post content contained a hand-authored Article schema block with a phone number in the description. On render, the phone auto-linker converted that phone number into an anchor tag inside the JSON string, breaking the JSON-LD. The post content also had an unnecessary stray closing script tag immediately before the Article schema block.

Work completed:

• Backed up the current published post content to /Users/samaguiar/Documents/Codex/wp-content-backups/10-mistakes-to-avoid-after-an-accident-2026-05-18-090000-pre-edit.html
• Patched only the malformed article schema segment in a working copy.
• Updated post 12390 via WordPress REST while keeping status publish.
• Flushed WordPress object cache, ran rocket_clean_domain, and cleared wp-content/cache/wp-rocket.

Verification:

• Homepage normal and cache-busted: one root #organization, Louisville PostalAddress present, zero parse errors.
• Article normal and cache-busted: one root #organization, Louisville PostalAddress present, zero parse errors.
• The Article JSON-LD now renders with a plain-text description and parses cleanly.

Reason session ended: regression fixed and live verification clean.

Handoff: if similar parse errors recur on article pages, inspect inline JSON-LD blocks stored in post content before touching the sitewide WPCode schema snippet 43605.