Yesterday I audited all twelve app pages on my website against the apps they are supposed to describe. One of the Sortes gallery images had a UnitFlip back indicator in it. I was looking at a decision app and seeing another app's screen. That is a hard bug to spot when you treat marketing images as decoration.
The image made the problem obvious. Other drift showed up right behind it. UnitFlip still had a stale locale capture showing 150.000. QRift was missing its successful-scan and History states. ReceiptCrate's page still described its first iPhone release even though 1.2 was live with encrypted backup and App Lock.
I went back to each app's owner sources: the current repository, the public store version, the screenshot set, and the claims the site was making. Scope Binder's replacement set grew from three images to six. It now covers quote comparison, missing terms, follow-ups, files, a decision packet, and privacy. The captions say when the screens use fictional demo data. SwipeClean got the same disclosure on its demo screens.
I also removed claims I could not prove. Sortes had copy about saved presets that were not in the shipped build, so I removed it and kept the gallery to the three states the app publishes. The public page now describes the shipped app and stops there.
The code changes were small. Checking them took the day. I compared the copy and images with current app truth, ran the full site gate, and checked the production pages after deployment. The corrected assets and claims are live.
I am treating website screenshots, icons, and feature copy as release artifacts now. Before I publish one, I need to know which app version it represents, where the image came from, what the reader should learn from it, and whether the claim still exists in the shipped build. If I cannot answer those questions, the page is not ready.