What do saves and shares tell you about an informational post?

As a tiering system, likes are lowest then saves and then shares. Sharing with another human is most skin-in-the-game (sharing a bad post is embarrassing) when saving is clearly them saying to themself "I want to remember this or I want to come back to it"

Your read on this is 100% accurate. When analyzing audience behavior and mapping out content strategies, I actually use saves and shares as my primary KPIs for informational posts. Likes are basically just vanity metrics at this point.

Here is exactly how I read them to judge if a post actually helped:

• Saves (The Utility Metric): A save represents information density. When someone hits save, they are saying, "This solves a problem for me, and I need to keep it as a reference tool." It’s the ultimate indicator that your content had practical, actionable value.
• Shares (The Social Capital Metric): A share means the content was so impactful or relatable that someone is willing to stake their own digital reputation on it by sending it to a friend. It tells me that the post didn't just help one person, it articulated a pain point or solution so well that they wanted their network to see it too.

So yes, I absolutely use both! High saves mean the post was highly educational. High shares mean it was highly relatable. If an informational post hits both, you've completely nailed it.

If this post doesn't follow the rules, please report it to the mods.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

I'd look at saves per thousand reached and compare that with your own past informational posts. Raw counts mostly follow reach, so a post that got pushed further looks helpful whether it was or not. For whether it actually helped, the cleaner signal sits outside the post. If it answers something your team keeps getting asked in DMs or support tickets, count how often that question comes in over the next few weeks. Slower to read than saves. In-house it's also the number a support lead or a VP will care about when you ask for more time on that kind of content.