robots.txt pointed at a stale, misspelled sitemavp.xml; added the live AIOSEO blog sitemap and a clean 500-URL sitemap.xmlwp_blog_defaults.pyThe post was already in the live AIOSEO sitemap and linked from several pages. The break was one line in robots.txt pointing only at a stale static sitemavp.xml (77 old URLs, latest Apr 2026). The canonically named sitemap.xml was a junk file of 452 raw .php source filenames. All four were corrected and cache-busted past a stale CDN edge.
The post was authored by user 3 and used a 736×736 square banner while every other recent post is 16:9. Author was moved to a shared editorial account and the banner rebuilt from the native 5001×2800 render to 1600×900 (1.778), with featured media, in-content figure, og:image and twitter:image all repointed.
The hero video’s poster attribute still held the old pre-video banner, so mobile painted it for seconds while the 4 MB video loaded. The poster is now frame 0 of each video (extracted with OpenCV — ffmpeg not installed), removing both the old banner and the blank white gap.
Two rounds of client JSON edits were deployed. The cta field is dead data — index.php hardcodes the button label — so 3 Bed Large and Duplex still disagree with the JSON and were flagged for client sign-off. The site’s thin-client firewall had also blacklisted our IP (HTTP 200 “Access Denied”) due to a malformed whitelist entry.
data.json for stale configuration strings and drafted the sitemap + robots fixes