Airbnb Superhost and 30+ Day Stays: Why the Math Works Against Long Bookings

Consider a host who ran four stays last year, each a corporate placement of about 90 days. Three guests left five stars. The fourth left three stars after a water heater failed in week seven and took two days to replace under warranty. The host answered within minutes, arranged a hotel for the night, and paid for it.

That host loses Superhost status at the next assessment.

Nothing about the hosting got worse. What changed was the denominator. This is a structural feature of how the rating system counts, and it lands on every host running stays of a month or longer. Below is the arithmetic, what Airbnb actually publishes about losing and keeping status, and what to do about it.

All Airbnb criteria described here are quoted from Airbnb's published Help Center, re-verified August 2026. Programs and thresholds change; verify current terms before acting on them.

Why is Superhost status harder to keep on 30+ day stays?

Because your rating is an average, and long stays give you very few numbers to average. Airbnb evaluates hosts on a rolling 12-month window and requires a 4.8 overall rating. A host with 100 short stays a year can absorb about ten 3-star reviews and still qualify. A host running four 90-day stays can absorb none.

The 4.8 threshold is arithmetic, not judgment

Airbnb's published Superhost criteria are specific. To qualify, a host must have hosted at least 10 reservations, or 3 reservations totaling at least 100 nights; responded to 90% of new messages within 24 hours; maintained a cancellation rate under 1%; and "maintained a 4.8 or higher overall rating." Assessment happens four times a year, and the measurement window is stated plainly: "Every 3 months, we evaluate your performance as a host over the past 12 months for all listings on your account."

That 12-month window is where long-stay hosting runs into trouble. Two hosts, same standard, same single bad review:

The threshold treats both hosts identically. The exposure is not: ten bad reviews absorbed versus zero, against the same standard.

Recovery works against long-stay hosts the same way. The host above sits at 4.50 with four reviews. To average back above 4.8 by adding perfect stays, they need six more of them. Six stays of 90 nights is roughly 18 months of hosting, and the assessment window is only 12 months long. They cannot out-book the problem, because they cannot generate reviews faster than the calendar moves. The arithmetic leaves one option: wait for the review to age out of the window. That can take a year.

Airbnb has already solved this problem in the other half of the criteria. The volume requirement carries an explicit alternative for exactly this host: "3 reservations that total at least 100 nights." Counting stays instead of nights would have locked long-stay hosts out entirely, and the published rule accounts for it. The rating gate was left alone. The volume math was adjusted for long stays. The rating math was not.

Long stays generate maintenance events by definition

A property in use wears down. Appliances fail, HVAC systems need service, the yard grows, a fixture leaks. None of that is a hosting failure. It is what happens when a building is occupied, and it is one of the ways a 30+ day stay differs from a weekend booking in kind rather than degree.

The variable that matters is exposure. A two-night guest is present for two nights of possible incidents. A 90-day guest is present for 90 of them, and is also living in the unit rather than sleeping in it: cooking daily, running laundry weekly, using the dishwasher, filling the trash, noticing the drip under the sink that a weekend guest would never find. As stays lengthen, the probability that some maintenance event happens during the stay stops being a risk and starts being a certainty.

Airbnb's own rating categories are where this collides. Guests rate seven things: overall, cleanliness, accuracy, check-in, communication, location, and value. The published definition of accuracy asks whether the listing "was accurately represented with up-to-date photos and info," and then adds: "Was everything in good working condition?"

For a two-night stay that is a reasonable question with a stable answer. For a 90-day stay, the honest answer eventually becomes no, for every host, regardless of how well they run the business. The category has no place to record that the dishwasher failed on day 54 and was replaced on day 55. A host who responds in four hours and a host who ignores the message for a week both end up describing the same underlying fact: at some point during the stay, something was not in good working condition.

We are not claiming Airbnb designed this to punish anyone. We are pointing out that a rating vocabulary built around a stay short enough for nothing to break behaves differently when applied to a stay long enough that something will.

Airbnb added a layer on top of this in May 2026. The 2026 Summer Release introduced AI review highlights, which Airbnb describes as models that "synthesize reviews for each listing and highlight things you care about the most including location, amenities, family-friendliness, and more." Synthesis across three hundred reviews smooths out the one stay where the dishwasher failed. Synthesis across four has less to work with. Airbnb does not publish how the models treat a small review set, and we are not going to guess at it. The arithmetic point holds without that: the fewer reviews a listing carries, the larger the share of any summary that a single review represents.

What happens when you lose Superhost status?

Airbnb reassesses every three months, and the badge is removed from your listing and profile if you no longer meet the criteria. Airbnb states that hosts can regain it: "If you miss a requirement, you can always become a Superhost again once you meet the requirements." Because assessments run quarterly, on January 1, April 1, July 1, and October 1, the soonest possible return is the next assessment date, and only if every requirement is met by then.

On the visibility question, Airbnb is less specific, and we are going to be equally unspecific rather than guess. Airbnb's published guidance on search says results are influenced by quality, popularity, price, and location, and states that "higher quality listings with better ratings and reviews tend to rank higher in search." Airbnb does not publish how much weight the Superhost badge itself carries, or what a rating drop from 4.9 to 4.5 does to placement. Anyone who tells you the exact number is guessing. What Airbnb does publish is enough for the point: ratings and search position are connected, and yours just fell.

Lower placement means fewer bookings, and that is where it compounds. For a nightly host, fewer bookings still means a steady stream of new reviews diluting the bad one, and the situation self-corrects within weeks. For a 30+ day host, fewer bookings means fewer of the four annual reviews that constitute the entire denominator. The same feedback loop that repairs a short-stay listing tightens around a long-stay one.

What do you actually get for Superhost status?

Airbnb describes the benefits as "more visibility, earning potential, and access to exclusive rewards," plus the badge that appears on your listing and profile. Guests use the badge as a trust signal, which matters more, not less, for a stay someone is committing three months of their life to.

Guest Favorite is a separate program, and long-stay hosts should understand the difference. Guest Favorites are rated above 4.9 on average, and a listing needs at least five reviews in the last four years, with one in the last two years, to be eligible. The review-count bar is achievable on long stays. The 4.9 average, on a base of four or five reviews, means a single 4-star review can put it out of reach.

How do you go from a 4-star to a 5-star rating on a long stay?

The advice written for nightly hosting mostly does not transfer. Welcome baskets and fast check-in matter less over 90 days than how you behave in week seven. Five things actually move ratings on long stays:

Set expectations in writing before arrival: tell the guest directly that over a stay this long something will likely need service, that you will handle it, and how to reach you. A guest who was told in advance reads a broken dishwasher as a normal event that got handled. A guest who was not reads it as a surprise. Same dishwasher, different review.

Make reporting frictionless: one channel, stated once, no forms. Every hour a guest spends deciding whether an issue is worth bothering you about is an hour it sits unreported and turns into resentment.

Reply fast, then commit to a date: speed of acknowledgment and certainty of resolution are separate things, and guests need both. "I've seen this, the tech comes Thursday between 9 and 12" resolves the anxiety even though the problem is still there. Silence for a day does more damage than the failure did.

Check in around day 21, not day 85: ask a specific, open question. Is there anything that would keep this from being a great stay? Problems surfaced at day 21 get fixed and forgotten. The same problem discovered at checkout goes straight into the review, because you never gave the guest a way to tell you.

Over-document the listing: accuracy is where long stays bleed, because a guest has 90 days to notice every gap between the photos and the unit. Photograph the actual appliances, note the quirks, state what is not included, and update the listing whenever something changes. Nightly guests never get far enough into a unit to find the discrepancy. Long-stay guests find all of them.

One thing not to do: never ask a guest for five stars, offer anything in exchange for a review, or condition your review of them on theirs. Airbnb's review policy prohibits review manipulation, and the downside is losing the listing. The day-21 question is the legitimate version of the same instinct, and it works better anyway, because it fixes the problem instead of managing the score.

What should actually be measured

A host running 30+ day stays should be measured on three things: how well they communicate, how quickly they resolve issues, and whether the listing was accurate. Those are the things a host controls, and they are what actually determines whether a long stay goes well.

Whether anything broke is not one of them. Over 90 days, something breaking is a property of the calendar. A rating system that cannot distinguish between a host who fixed the water heater in four hours and a host who never answered is not measuring hosting. It is measuring luck, and then treating the result as a performance score.

Radius runs this as the review system rather than as a position. Guests rate the same standard categories, and an overall number still exists. What changed is what the system collects around it.

On stays of 28 nights or more, the guest gets a check-in around day 21. Anything they mark as needing attention reaches the host immediately, so a fixable problem gets fixed while the guest is still in the unit. The rating and comments stay sealed until the post-checkout reveal, which means the guest can be candid without living under a review the host has already read. When the checkout rating differs from the day-21 rating, the published review shows both: Day 21: 3 stars, checkout: 5 stars. A host who fixed the water heater in four hours and a host who never answered no longer produce the same record.

The denominator gets addressed directly too. A host joining Radius can import reviews from a connected Airbnb or PMS account, labelled by source, so a long-stay operator does not restart at zero on a count that takes years to rebuild. Ratings also run at the company level, averaged across every listing an operator runs, so a well-run operator is not judged on whichever listing happens to have the fewest reviews. And there is no status tier: no badge held behind a rating threshold, and no quarterly assessment that takes one away.

The full mechanics are documented in How reviews work on Radius.

This is one of several reasons we built Radius. It is not the whole reason, and it is not the largest one. It is a specific instance of a general problem: a platform built for two-night stays makes assumptions everywhere, and long-stay hosts absorb the cost of every one of them.

The same short-stay assumption shows up everywhere else

Ratings are the visible version. The structural version shows up in the paperwork.

Rental agreements: Airbnb permits hosts to ask guests to sign a contract, with conditions: the terms must be disclosed in the listing and in the message thread, and Airbnb states that "guests are not obliged to sign anything." A guest who declines can cancel within 48 hours for a full refund. And on enforcement, Airbnb is direct: "Airbnb can't help enforce any special policies in your contract."

That is a coherent design for a two-night booking, where an agreement would be overhead nobody needs. For a 90-day stay it inverts the relationship. The agreement is not paperwork attached to the stay. It is the stay. Occupancy rules, guest limits, utility responsibility, damage terms, renewal, and notice all live in it, and it sits outside the platform, unenforceable by the platform, and optional for the guest to sign.

Tenancy: Airbnb notes that at around 30 days, local landlord-tenant law may attach to the stay. The exact threshold varies by jurisdiction, and this is a question for a lawyer in your market rather than a platform help article. The relevant point is that the 30-day mark is precisely where midterm hosting begins, and it is where the platform's own guidance starts pointing hosts elsewhere.

Payments and cancellation: Airbnb has built for this one. Stays of 28 nights or more use long-term cancellation policies and monthly installment payments, which accommodates how longer stays actually work. It also shows the pattern. Where a long-stay problem was framed as a long-stay problem, it got solved. The rating system and the agreement layer were never framed that way.

What Airbnb gets right, what it does not, and where Radius fits

More of this comparison, including how the models differ on inventory and demand, is on our comparison page.

So should you leave Airbnb?

Probably not, and we are not going to pretend otherwise.

Airbnb's distribution is enormous, and for a host with an empty calendar, demand beats a better-designed system with less of it. Plenty of midterm hosts run profitably on Airbnb and will keep doing it.

The argument is narrower than "leave." It is that a rating system tuned for two-night stays should not be the thing that determines whether your business is visible, and that a host whose entire annual review count is four is carrying a risk that no amount of good hosting removes. One water heater is enough. That is a bad foundation to build a business on, regardless of how good the demand is on top of it.

The practical response is to stop depending on a single channel. Run the Airbnb listing for what it is good at, and build a second demand channel where the stay length is the assumption rather than the exception. Hosts who do that stop treating the quarterly Superhost assessment as an event that decides their year.

Frequently asked questions

Does a 30-day stay count toward Superhost status?Yes. Airbnb's published criteria require at least 10 reservations "or 3 reservations that total at least 100 nights," which is designed to let long stays qualify. The volume requirement accommodates long stays. The 4.8 rating requirement is the same for everyone.

What happens when you lose Superhost status?The badge is removed from your listing and profile at the quarterly assessment. Airbnb states you can regain it once you meet the requirements again, but assessments only run on January 1, April 1, July 1, and October 1, so the soonest return is the next one. Airbnb's published search guidance says listings with better ratings and reviews tend to rank higher, though Airbnb does not publish how much weight the badge itself carries.

How many reviews do you need to hold a 4.8 rating?There is no minimum, but the count determines how much one bad review costs you. At 100 reviews, ten 3-star ratings still average exactly 4.80. At four reviews, a single 3-star drops you to 4.50. Airbnb evaluates the past 12 months, so a long-stay host cannot dilute a bad review faster than it ages out.

Can you require a lease or rental agreement on Airbnb?You can ask. Airbnb permits hosts to request that guests sign a contract if the terms are disclosed in the listing and the message thread, but states that guests are not obliged to sign, that a guest who declines can cancel within 48 hours for a full refund, and that "Airbnb can't help enforce any special policies in your contract."

How does Radius rate hosts differently?Guests rate the same standard categories, but the system collects more around them. On stays of 28 nights or more, a check-in around day 21 lets the guest flag anything needing attention, and that note reaches the host immediately while the rating stays sealed until after checkout. Published reviews show how the rating moved between day 21 and checkout. Radius has no status tier, so there is no badge to lose at a quarterly assessment. The mechanics are documented in How reviews work on Radius.

Is Airbnb good for midterm rentals?It is good for demand and weak on structure. The audience is unmatched, and the 28+ night cancellation and installment payment policies do accommodate longer stays. The rating system, the Superhost threshold, and the agreement layer all still assume a short stay. Most midterm hosts get the best result by keeping the Airbnb listing and adding a channel built for 30+ day stays.