Do Old Reviews Really Fade? What Airbnb Actually Confirms
There is a story hosts tell each other, usually late at night after a rough stay finally rolls off the calendar: give it time, the review will sink, the algorithm will bury it, the newer ones will carry more weight and the old one will fade into the background like a stain that eventually stops being visible from across the room. It is a comforting story. It is also, as far as the publicly available documentation from Airbnb goes, not a story anyone at Airbnb has actually confirmed. That gap — between what hosts widely believe about review recency and what the platform has actually put in writing — is the entire subject of this piece, and it deserves to be walked through slowly rather than waved away with a shrug.
This is not a post about search algorithms in the broad sense, and it is not a post about the dilution math of getting more five-star reviews to outnumber a bad one, though it touches both, because this site already has essays dedicated to each of those questions and there is no reason to retread that ground here. This is narrower and, I think, more useful: a plain accounting of what Airbnb's own Help Center says about how reviews are ordered and averaged, an honest admission of what remains unconfirmed for Vrbo and Google, and a clear-eyed argument for why the practical response to all of this uncertainty is the same regardless of which platform you host on — keep the reviews coming, steadily, because the math rewards volume whether or not recency ever gets its own multiplier.
This is not legal advice, and none of the marketing guidance on this page replaces reading your own contracts or confirming local rules with the relevant office.
What Airbnb Actually Documents About Review Order
Start with the one thing that is genuinely, unambiguously documented: Airbnb's default sort order for the reviews a guest sees on a listing page is relevance, not chronology. This comes directly from Airbnb's own Help Center material on how reviews are sorted and displayed, and it is worth sitting with because it contradicts the mental model a lot of hosts carry around. Many of us assume, without ever checking, that the newest review sits at the top the way a fresh comment sits at the top of a social feed. That is not what Airbnb says happens by default. Relevance sorting means Airbnb's own systems are making a judgment about which reviews a given viewer is likeliest to find useful, and recency may be one signal folded into that judgment, but it is described as relevance, full stop — not 'newest first,' not 'most recent first,' and not any term that would let a host confidently say the freshest praise is guaranteed prime real estate.
Guests can typically change the sort order themselves, and most listing pages let a browsing guest choose to view reviews by criteria including recency if they want to. But the operative word there is choose — that is a guest-initiated action layered on top of a default that is not chronological. If a host is building a strategy around the assumption that the newest reviews are automatically what every visitor sees first, that assumption is standing on documentation that does not exist. It may happen to work out that way for some visitors who flip the sort toggle. It is not the platform's baseline behavior.
The Assumption Hosts Make — And Why It's Understandable
None of this is a knock on hosts for believing the recency-weighting story. It is an intuitive belief, and it is reinforced by adjacent, half-remembered facts that are individually true but get fused into a claim that goes further than any of them actually supports. Hosts know that removed reviews get excluded from the public average — that part is documented, in Airbnb's Help Center material on how the overall rating is calculated. Hosts know that a bad review from three years ago feels less relevant than one from last month — which is a human, common-sense reaction, not a statement about platform mechanics. And hosts know that competitors with fresher review activity tend to look more vibrant on the search results page, which is true but is a different phenomenon than the star average itself decaying.
Fuse those three true-but-separate observations together and you get a fourth claim — 'the star average down-weights old reviews over time' — that feels like it should be true and yet is not something Airbnb's current public documentation states. This piece is not arguing the fused claim is false in some absolute cosmic sense; it is arguing that no host should build a strategy on it as though it were confirmed, because it isn't, and strategies built on unconfirmed mechanics tend to produce disappointment when the mechanics don't behave the way the story predicted.
Two Separate Rating Systems: What Article 1257 and Article 13 Actually Say
Here is where the documentation gets genuinely specific, and where it is worth being precise rather than approximate, because precision is the whole point of this essay. Airbnb's Help Center distinguishes between the overall rating a guest leaves and the six subcategory ratings — things like cleanliness, communication, check-in, accuracy, location, and value. According to Airbnb's own material on this (Help article 1257), the overall rating is not a computed average of those six subcategories. It is its own separate number that the guest assigns directly. A guest could, in theory, leave five stars across every subcategory and still give a lower overall rating, or the reverse, because the overall score is asking a different question than the subcategory scores are asking.
Then there is the public-facing number — the star average a browsing traveler actually sees on your listing card and your listing page. Airbnb's Help Center material on how the overall rating is calculated (Help article 13) describes this as a straightforward average of the overall-rating scores left across all of a listing's reviews, with removed reviews excluded from that average. Straightforward average. Not a weighted average. Not a time-decayed average. Not an average where a review from six months ago counts for sixty cents on the dollar compared to one from last week. The documentation describes simple arithmetic: sum the overall scores that remain after any removals, divide by the count. That is the mechanism as Airbnb has published it, and it is the mechanism this piece is going to keep returning to, because it is the load-bearing fact underneath everything else.
Why does this distinction between article 1257 and article 13 matter to a host trying to figure out what to do on a Tuesday? Because it tells you exactly where the dilution math lives and exactly where it does not. If the star average is a simple average with no time-based weighting, then the only documented lever a host has for improving that number is changing the composition of the pool being averaged — either by disputing and removing reviews that violate Airbnb's content policies, or by adding more high scores to the denominator. There is no third documented lever where waiting quietly for six more months causes an old low score to matter less on its own. Time, by itself, is not described anywhere in this documentation as doing that work.
The 14-Day Review Window and What It Actually Controls
Both host and guest have a 14-day window after checkout to submit a review, and once that window closes, no further review can be added for that stay. This window is worth mentioning here not because it has anything to do with recency-weighting of the display — it doesn't, based on the documentation — but because it is frequently misunderstood as part of the same system, and it's worth separating cleanly. The 14-day window controls whether a review gets submitted at all. It has no documented bearing on how that review, once submitted, gets weighted against older reviews in the public average years down the line. Keeping these two mechanics distinct in your head is part of the discipline this whole essay is asking for: know which documented rule governs which behavior, and resist the urge to let one rule's existence imply a second rule that hasn't actually been published anywhere.
The practical host takeaway from the 14-day window is entirely about timing your own communication — prompting a happy guest to leave a review before the window closes, rather than assuming there's flexibility to circle back a month later. That is a real, actionable, documented constraint. It simply isn't evidence of anything about how reviews decay once they're in the system, and the two shouldn't be treated as part of the same mechanism just because they both involve the passage of time.
Vrbo and Google: What This Research Could Not Confirm
Now the harder, more honest section, because a host reading this deserves candor rather than a confident-sounding paragraph built on guesswork. This piece cannot tell you, with documentation-backed certainty, what Vrbo's default review sort order is, or whether Vrbo's displayed rating is a simple average or something else. It cannot tell you the same about Google's review display on a Business Profile or a Maps listing. The research behind this essay was scoped to what Airbnb has published in its own Help Center, and extending confident claims to other platforms without equivalent documentation in hand would be exactly the kind of unearned certainty this piece is trying to push back against everywhere else.
What that means practically: if you host on Vrbo, or if your listing shows up with reviews aggregated through a Google Business Profile, treat any claim about those platforms' specific sort defaults or rating-weighting mechanics — including claims in this paragraph, because there are none being made here — as something to verify directly against each platform's current help documentation before you make a decision based on it. Platforms update their help articles, their sort defaults, and their display logic without necessarily announcing it widely, so a claim that was accurate eighteen months ago on a forum thread may not be accurate today. The responsible move, and the one this piece is modeling rather than just recommending, is to check the platform's own current documentation at the point you actually need the answer, rather than carrying around a secondhand belief about how Vrbo or Google 'must' work because it resembles how Airbnb works. Resist the temptation to assume symmetry across platforms just because it would be tidier.
A Search-Visibility Question Worth Naming, Not Answering Here
There is a second, genuinely interesting question tangled up in all of this, and it deserves to be named clearly even though this essay is not the place to chase it down: separate from whatever happens to the displayed star average, does a steady flow of recent reviews do anything for a listing's visibility in search results? It is entirely plausible that Airbnb's search ranking systems treat review recency, review velocity, or recent guest engagement as a freshness signal that helps a listing surface more often — independent of whether that recency ever touches the star average itself. Plausible is the right word and the only word this piece is going to use for it, because this site has other content specifically dedicated to search-ranking mechanics, and duplicating or half-explaining that material here would do a disservice to both pieces.
The reason it's worth naming at all, even briefly, is that it explains why 'get more recent reviews' can be sound advice even in a world where the displayed rating truly is just a simple, non-decaying average. Two entirely separate systems could both reward review velocity — one because dilution math genuinely lowers the weight of old scores in a simple average as new ones join the pool, and the other, unconfirmed but plausible, because search ranking might favor freshness signals on top of that. A host doesn't need the second mechanism to be true in order for the advice to hold. That's the quiet strength of this argument: it survives even if the search-visibility piece turns out to be smaller than hosts hope, because the first mechanism, the arithmetic one, is already documented and already sufficient on its own.
Why Review Velocity Is the Provable Strategy
Set the unconfirmed pieces aside for a moment and look only at what article 13 actually tells you: the public rating is a straightforward average of all remaining overall-rating scores. If that's true, then getting more positive reviews into that pool has a direct, provable, arithmetic effect on the average — not because the new reviews push the old ones down or make them count for less, but because they change the denominator. A listing sitting at a 4.6 average built from twenty reviews moves meaningfully with the addition of ten more strong ones; the same listing sitting on two hundred reviews barely moves at all from ten more, good or bad. This is not a mysterious algorithmic favor Airbnb is doing for active hosts. It's the same arithmetic that governs any average of anything, and it happens to reward hosts who keep the review count climbing.
This is the honest version of the recency story, and it's worth saying plainly because it changes what a host should actually do with their energy. You are not trying to make an old bad review 'age out' or 'fall off' — nothing in Airbnb's documentation describes reviews aging out of the average on their own. You are trying to make that old review count for a smaller and smaller share of an ever-larger total, by adding more scores to the pool it sits inside of. The practical difference matters because it points toward action rather than waiting. A host who believes in silent time-based decay might reasonably decide the smart move is to do nothing and let the calendar handle it. A host who understands the actual documented mechanism knows that nothing happens on its own — the average only shifts because new, real stays generate new, real reviews, which means the entire strategy comes down to hosting well and asking consistently, stay after stay, rather than hoping distance does the work for you.
Building a Steady Review Habit Without Gaming Anything
None of this is a call to manufacture reviews or pressure guests into leaving five stars they don't mean — that would violate the spirit of the review system and, more importantly, would produce a public rating that misrepresents the actual guest experience, which eventually catches up with any listing regardless of the math behind it. What this argument actually supports is something much simpler and more sustainable: making it a habit, for every single stay, to give a guest an easy, low-friction reason to leave the review they were already inclined to leave. A warm checkout message that mentions the review window closes after fourteen days. A genuine thank-you that doesn't beg, but does remind. Consistency in how the property is presented and maintained, so that most stays naturally earn the kind of review that helps the average rather than hurts it.
The velocity strategy works precisely because it doesn't depend on any unconfirmed mechanism to be true. It works if the star average is a simple, undecaying arithmetic mean exactly as article 13 describes, and it may work even better if there turns out to be a freshness component to search visibility on top of that, once that question gets properly documented somewhere. Either way, the host who treats every completed stay as one more opportunity to add a solid score to the pool is playing the version of this game that the published rules actually support — not the version built on a comforting rumor about old reviews quietly fading from view.
Related Reading
These neighboring Crest & Cove Creative posts stay on the same marketing desk for independent hosts - listing clarity, owned search, and direct-booking choices without mixing in finance or legal work.
Frequently Asked Questions
Does Airbnb reduce the weight of old reviews as new ones come in?
Airbnb's Help Center describes the public star average as a straightforward average of overall-rating scores across all remaining reviews, with removed reviews excluded. There is no documented mechanism stating that older reviews carry less weight or decay over time in that average. Hosts commonly assume time-based weighting exists; based on current public documentation, it is not confirmed. What is documented is that adding more reviews changes the pool the average is drawn from, which does shift the number arithmetically.
What is Airbnb's default sort order for guest reviews on a listing page?
Airbnb's default sort order for reviews is relevance, not strictly newest-first chronological order, according to Airbnb's own Help Center documentation on review display. Guests can typically choose to re-sort by other criteria including recency, but that is a guest-initiated action layered on a default that isn't chronological. Hosts who assume the newest review is automatically what most visitors see first are relying on an assumption the documentation doesn't support as the baseline behavior.
Is the overall rating just an average of the subcategory scores like cleanliness and communication?
No. According to Airbnb's Help Center material on this, the overall rating is its own separate score that a guest assigns directly, not a computed average of the six subcategory ratings such as cleanliness, communication, check-in, accuracy, location, and value. A guest could rate subcategories highly and still leave a different overall score, or vice versa. This distinction matters because it clarifies which number actually feeds the public-facing average hosts see on their listing.
How long do guests and hosts have to leave a review after checkout?
Both the host and the guest have a fourteen-day window after checkout to submit a review for that stay. Once that window closes, no further review can be submitted for it. This window governs whether a review gets created at all — it has no documented connection to how that review, once submitted, is weighted against older reviews in the public average later on. Use it as a prompt-timing deadline, not as evidence of any decay mechanism.
Does Vrbo weight recent reviews differently than older ones?
This has not been confirmed through Airbnb-equivalent public documentation, and it should not be treated as settled fact either way. Vrbo's specific sort defaults and rating-calculation mechanics were outside the confirmed scope of the research behind this piece. If this matters to a decision you're making, check Vrbo's current help documentation directly at that time, since platform mechanics and displayed defaults can change without wide announcement between when an article is written and when you read it.
Does Google weight recent reviews more heavily on a Business Profile?
That is not confirmed here either. Google's specific review sort defaults and any recency-related weighting on a Business Profile or Maps listing fell outside what this research could verify against current published documentation. Rather than repeat a secondhand assumption about how Google 'probably' handles this, the honest position is to verify directly against Google's own current help resources before building a strategy around a specific claim about how its review display works.
If old reviews don't fade, why do hosts with frequent recent reviews seem to recover faster from a bad one?
Because of simple arithmetic, not decay. A straightforward average is far more sensitive to new entries when the total review count is small, and far less sensitive once the count is large. A host who adds many new positive reviews is diluting the mathematical share that one old low score occupies in the overall average — not making the old review count less, but making the total pool larger around it. The visible 'recovery' is the denominator changing, not the old review aging out.
Is there a search-ranking benefit to getting reviews frequently, separate from the star rating itself?
It's plausible that review recency or velocity acts as a freshness signal in Airbnb's search ranking, independent of the displayed star average, but this has not been confirmed through public documentation and is not something this piece can assert as fact. It's worth naming as an open question rather than ignoring, but a full treatment of search-ranking mechanics belongs to dedicated search-algorithm content elsewhere, not to a review-averaging piece like this one.
Should hosts stop worrying about a single bad review if it happened a long time ago?
Worrying less is fine emotionally, but assuming the platform is quietly reducing its impact isn't supported by current documentation. The documented path to reducing a bad review's practical effect is adding more reviews to the pool it sits in, since the public rating is described as a simple average across remaining scores. Time alone, absent new reviews, isn't described anywhere as doing that work on its own — so the constructive response is to keep hosting well and keep the review flow steady, not to wait.
What's the most reliable strategy given how much about recency weighting remains unconfirmed?
Build a consistent habit of prompting genuine reviews after every stay, inside the fourteen-day window, without pressuring guests toward a score they don't believe. This works under the documented mechanism, since a simple average shifts with the composition of its pool, and it may work even better if a freshness-related search benefit turns out to be real once that's properly confirmed. It's the one approach that doesn't depend on an unproven decay mechanism to pay off.
Work with Crest & Cove Creative
You already suspect the old review isn't really fading — here's what Airbnb's own documentation actually says, and the one strategy that works whether or not it does. Ask for a marketing-only read of the listing.
Ready to make your review habit the thing that actually moves your rating? Build a simple after-stay prompt into your guest communication and let a steady stream of genuine reviews do the documented work. We stay on listing clarity, photos, SEO, and channel mix for independent hosts, not finance or legal work.
Reach out at crestcove.co or (256) 998-7502.
Comments