A live ranking can have an old last-comment date. What should freshness mean?
I operate Rankiwiki, a public community ranking site. One small interface problem is making me rethink what a "live" page promises.
On our "What makes content feel credible?" page, the visible labels are PUBLISHED 01/23/2026 and LAST COMMENT 05/16/2026. The page also describes itself as a live ranking. Those dates are real labels I checked today, but neither tells a reader when the ranking order last changed. A recent page view is not fresh participation, and a recent comment would not necessarily change the order.
I am considering separating three events: topic created, latest contribution, and ranking last changed. For a small community, I would rather show an honest old date than make a quiet topic appear newly validated. I have not shipped that change or measured whether readers find it clearer.
My proposed first test is simple: show the existing page to a few readers and ask, "What do these dates tell you about the results?" before explaining them. Then test the separate labels on a mockup. That checks understanding rather than treating more clicks as proof of trust.
If you maintain a community product, would you show all three dates, or only the event that changes the result? I am particularly interested in cases where an extra freshness label made the interface worse.
Product limit: Rankiwiki is public and is not classroom-ready; this is not a proposal to rank identifiable children. Operator disclosure: I run the site. Written with AI assistance; the interface observations above were checked against the live page.
The three-date separation is the right instinct. Google faces the same problem — a page's "last modified" header can mean the ranking changed, someone left a comment, or someone fixed a typo, and the signal is useless if all three trigger it. That's why Google added "last reviewed" structured data for medical and YMYL content, separate from "last updated."
For your product, I'd show "ranking last changed" prominently and bury the other two in a detail view. Readers who see "live ranking" expect the ORDER to be current, not just the comment section. An old "last changed" date actually builds trust if the ranking genuinely hasn't moved — it says "this settled" rather than "this was abandoned."
We build SEO audit reports at UtilitySEO and ran into a parallel: when should we re-scan a page and call the score "current"? The answer wasn't a timer — it was whether the page's content hash changed.
Would the "ranking last changed" timestamp update only on vote-driven reorder, or also when someone adds a new item?
Good point. Did you test that with users before committing to it?
When you test this with readers, what response would convince you they understand ranking freshness correctly rather than simply preferring one date layout?
I would score an explanation of the events before asking which layout they prefer. For example: a topic was created in January, the order last changed in May, and someone added a comment yesterday without changing the order. Ask: "What changed yesterday? Can you tell when the order last changed? Does this prove the ranking is representative today?"
A useful answer would distinguish the recent contribution from the older ordering, and say that neither date establishes representativeness. "It looks up to date" would not pass that check, even if they prefer the layout. I would use the same scenarios for both versions, alternate which version people see first, and record their explanations and mistakes rather than a satisfaction score alone.
This is still a proposed small qualitative test, not a test I have run or a statistical success threshold. As the operator, I should first verify that each event can be recorded accurately; otherwise the extra precision would be misleading. AI-assisted reply.
Clear and practical, thanks. Did anything surprise you along the way?
Thanks for writing this up. Bookmarking it for later.
Love this angle. Building Xstream4K right now so this hits close to home — what made you look into it in the first place?
Separating latest contribution from ranking last changed makes sense; otherwise a recent comment can imply freshness that the result does not have. I’d show all three dates but give the result-changing event visual priority, with a short explanation for the other two. The reader test you propose should reveal whether people can map each date to a meaningful event before you optimize for clicks.
I'd show only the event that changes the result. Someone reading a ranking is asking whether the order is still true, and "last comment" answers a different question, so at best it's noise and at worst it looks like freshness that isn't there. The other two can live in the footer.
One pairing that tends to help: an old "ranking last changed" date next to a count, like "order unchanged since May, 14 contributions since". The date alone reads as abandoned, with the count it reads as settled.
Thanks for sharing the numbers, that makes it much easier to follow.
Thanks for sharing the numbers, that makes it much easier to follow.
Thanks for writing this up. Bookmarking it for later.
Interesting take. Would you still recommend this approach to someone starting today?
Thanks for sharing the numbers, that makes it much easier to follow.
Appreciate the honesty here, most people only share the wins.
Really relatable. How much time do you put into this each week?