Objective

Run the daily schema check on aguiarinjurylawyers.com, distinguish source regressions from stale cached HTML, and repair the likely source if needed.

What changed

• Confirmed a real source regression on May 21, 2026: the homepage and article page had lost the richer sitewide schema graph.
• Verified the WPCode snippet 43605 still existed and found a real code defect inside it: malformed regex patterns in the video-detection block.
• Backed up the snippet content locally before editing:
  • /Users/samaguiar/Documents/Codex/wpcode-backups/sitewide-custom-seo-schema-43605-2026-05-21-170110-pre-fix.php
  • /Users/samaguiar/Documents/Codex/wpcode-backups/sitewide-custom-seo-schema-43605-2026-05-21-170110-fixed.php
• Repaired the malformed regexes in snippet 43605.
• Determined that the frontend was still not restoring the full graph through WPCode quickly enough, so deployed a narrow MU-plugin repair that patches Rank Math JSON-LD directly:
  • /Users/samaguiar/Documents/Codex/wpcode-backups/sal-rankmath-schema-repair-20260521.php
  • remote live file: wp-content/mu-plugins/sal-rankmath-schema-repair-20260521.php
• The repair consolidates duplicate #organization nodes, restores the canonical Louisville PostalAddress, restores the Louisville and Lexington office refs, and restores the four contact points.
• Cleared WordPress object cache and removed the WP Rocket page-cache tree for the production domain so plain URLs stopped serving stale schema.

Verification

• Before purge, cache-busted URLs were clean while plain URLs still served stale HTML. That confirmed source fixed, cache stale.
• After WP Rocket cache removal and cache flush, both plain URLs were clean.
• Final public checks on the homepage and 10-mistakes-to-avoid-after-an-accident showed:
  • parseable JSON-LD
  • one canonical root #organization
  • valid Louisville PostalAddress
  • two office refs
  • four contact points
  • no new parse errors

Reason for ending

The regression is repaired and the public plain URLs now match the cache-busted output, so the daily check is back to a clean state.

Suggested next steps

• If we want to reduce recurrence risk, the next useful pass is to either fully restore the sitewide custom schema through WPCode or migrate that logic into a versioned code surface intentionally, rather than leaving a mixed WPCode plus MU-plugin recovery path indefinitely.
• A narrower follow-up would be to inspect why WPCode did not restore the frontend graph even after the snippet code defect was fixed.

Handoff