Never Guess Whether It's Working: Live Capture-Health Status, Plus a Public Changelog

A live status indicator that confirms capture is healthy right now, and a public changelog that shows exactly what shipped and when, so you're never left guessing.

The problem

PostSnag lives downstream of a platform that changes without warning. Facebook redesigns a layout or shifts how a stat displays, and a tool reading that page can quietly break with no error message, just an export that looks normal until the numbers are a little too low. A tool that fails loudly gets fixed the same day; one that keeps running on incomplete data can stay broken for a week, and by then you may have already handed a client a report built on numbers that were never right. A tool that goes quiet with no visible updates starts to feel abandoned even when it isn't, which is often enough to make people stop trusting it.

What we're building

Two always-visible signals: a live capture-health indicator confirming PostSnag's capture is working right now, so a quiet Facebook change shows up as a clear status change instead of silently corrupted data, and a public, dated changelog logging exactly what shipped and when. Neither promises perfection, no tool reading a platform client-side can, but you'll never be left to find out the hard way.

• Live capture-health indicator, visible anytime, confirming capture is working the way it should.

• A clear flag the moment something shifts, instead of a quiet discovery weeks later.

• A public, dated changelog: every shipped fix and feature logged in one place.

How it works for you

Check the status before you lean on a scan for something that matters: a clean read means the data reflects what's actually on the page. Whenever something in the dashboard looks different, the changelog has a plain, dated answer for whether it's a bug or a shipped change.

What you get

• Confidence that the data you're capturing today is actually accurate, confirmed rather than assumed.

• An early warning the moment a Facebook change affects capture, instead of a silent gap discovered weeks later.

• Visible proof that PostSnag is actively maintained, not a tool you're just hoping still works.

For example

Facebook quietly changes how it displays reaction counts on a post layout. The capture-health indicator flags the shift before you've pulled a single affected scan into a client deck, and the changelog already shows the fix logged with a date and a plain description.

What it unlocks

Trust in the underlying capture is what every other PostSnag feature depends on: the overperformance score, snapshot history, and AI breakdowns are only as good as the data feeding them. The changelog does the same job for the product as a whole, turning "is this still being worked on" into something you can just go look at.

Who it's for

Anyone using PostSnag for something that actually matters, a client report, a real business decision, a pitch, and anyone who's been burned before by a tool that quietly stopped working.