Sam flagged a remaining serious QA concern: the cost FAQ answer should stop at Forever, and the visible stale browser render still showed repeated KYTC filler. I verified the current local approval file and live-proposed file no longer contain the KYTC repeated sentence, A Amazon, or the old broken FAQ block. The screenshot was from a stale local browser render, but it still exposed the core issue: the release process needed a hard quality gate.
I then found another live layer still carrying bad generated phrasing: Rank Math meta output had Amazon delivery accident lawyer Kentucky claims need... in the meta description, Open Graph description, and Twitter description. I updated Rank Math via /wp-json/rankmath/v1/updateMeta with a cleaner description: Amazon delivery crash in Kentucky? Learn who may be liable and what evidence matters. Call Sam Aguiar Injury Lawyers at (502) 888-8888. Public verification now shows zero instances of the bad phrase.
Created /Users/samaguiar/Documents/New project/scripts/wp_content_quality_gate.py. It scans HTML files and public URLs for repeated visible sentences, bad filler patterns, grammar defects such as A Amazon, keyword-stuffed Amazon phrasing, fake question sections, and FAQ schema mismatch. It was tuned to ignore hidden CSS/script comments for repeated visible sentence checks while still scanning meta/schema/body patterns.
The gate passed on:
outputs/amazon-related-content-approval-2026-05-10/page-61323-proposed-approval.htmloutputs/amazon-emergency-live-fix-2026-05-10/page-61323-live-proposed.htmlArtifacts:
outputs/amazon-emergency-live-fix-2026-05-10/content-quality-gate-public.jsonoutputs/amazon-emergency-live-fix-2026-05-10/public-verification-3.jsonoutputs/amazon-emergency-live-fix-2026-05-10/prevention-plan.mdThis was not a minor copy issue. The bad content existed across body copy, FAQ, JSON-LD, and metadata layers. Visual QA alone would not catch all layers, and REST body checks alone would not catch Rank Math meta. The prevention plan now requires file-level gate, REST raw-content verification, public served-HTML verification, Rank Math live-meta check, FAQ/schema alignment, and visual QA for high-value legal pages.
Amazon live repair now passes the new gate and public verification. Broader sitewide copy damage remains open and should be treated as high-priority.
Deploy the separate sitewide copy-damage survey agent prompt. Keep automated content publishing paused for this family until malformed FAQ blocks, generated filler, missing internal links, and schema/content mismatch are fully surveyed.