Airbnb guest screening: how to vet guests before you accept

A two-unit host in Split accepts a same-day request at 11pm because the calendar had a gap and the money looked good. Six guests show up to a listing that sleeps four. The party runs till 3am, a neighbor calls the police, and the checkout photos show a cracked coffee table. The booking paid €140. The cleanup, the noise complaint, and the dented review cost far more. None of it was bad luck. The warning signs were all on the guest's profile — a brand-new account, zero reviews, a one-line message that said "need a place tonight." He just didn't slow down to read them.

Screening isn't about being suspicious of everyone. It's a thirty-second habit that filters out the small share of guests who turn a good week into a bad one. Do it before you hit accept, because after that your options shrink to damage claims and a mutual review neither of you enjoys.

Why screen guests when Airbnb already verifies IDs?

Airbnb's identity check confirms a guest is a real person, not that they'll be a good one for your unit. Verification and screening solve two different problems, and you need both.

A verified ID stops obvious fraud. It does nothing about the guest who books a quiet two-bedroom for a bachelor party, or the one who'll cram eight people into a four-person listing to split the cost. Airbnb sits in the middle of the transaction, so its incentives lean toward accepting bookings and keeping the marketplace liquid. Yours lean toward protecting a specific property, a specific set of neighbors, and a rating you spent months building. That gap is exactly where screening lives.

The good news: almost everything you need to make a decision is already visible before you accept. You just have to know where to look and what a real red flag looks like versus a harmless quirk.

What can you see on a guest's profile before you accept?

Open the profile and read it like a landlord, not a scroller. Three things carry most of the signal: review count, what past hosts wrote, and how the guest talks to you in the request.

Start with reviews. A guest with 20-plus host reviews and no negatives is about as safe a bet as this platform offers — they've been through the check-in-to-checkout cycle two dozen times and nobody flagged them. A guest with zero reviews isn't automatically a problem; everyone starts somewhere. It just means you have less to go on, so you lean harder on the message and the requirements you've set.

Read the actual review text, not just the star average. Hosts write in code to stay polite. "Communication could have been better" often means the guest went dark for two days. "Left the place as found" is neutral-to-good. "Would host again with clear house rules" is a soft warning that someone had to be managed. One lukewarm review in a wall of glowing ones is noise. A pattern of hedged language is a signal.

Then read the request message. A guest who writes "Traveling with my partner for a wedding nearby, we'll be out most of the day, checkout Sunday" is telling you who they are and why they're coming. A guest who writes nothing, or "is it available?" after the calendar already says yes, hasn't given you anything to screen on — and the absence of information is itself information.

What guest requirements can you set on Airbnb?

Airbnb lets you require verified ID, a clean trip-review history, and a profile photo before a guest can book — set these once and they screen every booking automatically. This is the highest-leverage move most hosts skip.

In your account settings, under guest requirements, you can gate bookings on government-ID verification and on the guest having no negative reviews from past hosts — Airbnb documents both controls in its host help center. Turning them on doesn't reject anyone by name — it just means the guests who reach your calendar have already cleared a baseline. For a whole-home listing where you're not on site, that baseline matters more than any single message.

You can also add a required booking message and house rules that guests must acknowledge. Spell out the things that actually cause problems: no parties, no unregistered guests, quiet hours, maximum occupancy as a hard number. A guest who agrees to "maximum 4 guests, no exceptions" and then asks about bringing two more has told you everything you need to decline. And if a stay does go sideways despite the rules, clear written limits are what make a security-deposit or damage claim defensible rather than a he-said-she-said.

Asking pre-booking questions is fine, and often smart — "How many guests total?" and "What brings you to town?" are reasonable. What you can't do is screen on protected characteristics or push the booking off-platform. Keep questions tied to the stay, not the person.

What are the red flags that predict a problem stay?

The reliable warning signs cluster around three things: a mismatch between the guest and the trip, vagueness where there should be detail, and pressure to move fast. Any one alone is weak. Two or three together is a decline.

Watch for the local booking with no clear reason — someone booking a place ten minutes from their own address is a classic party or "staycation" pattern worth a direct question. Watch for guest count that keeps creeping: "just me" becomes "me and a friend" becomes "actually a few of us." Watch for a brand-new account paired with a same-night request and a one-word message. And watch for anyone who tries to negotiate around your rules before they've even booked — the person who asks to "maybe have a few people over" is telling you their plan.

None of these is proof. Plenty of local bookings are legitimate, plenty of new accounts belong to lovely first-time travelers. The point isn't to reject the flag — it's to ask one clarifying question and read the answer. A guest with an innocent explanation gives you a straight, specific reply. A guest with a plan gets defensive or vague. That single exchange resolves most cases. When it doesn't, and a difficult guest does slip through, your recovery playbook lives in handling difficult guests — but screening is what keeps you from needing it.

Instant Book with requirements, or request-to-book for screening?

Instant Book with tight guest requirements gives you speed and search-ranking benefits while still filtering; request-to-book gives you a manual look at every guest but costs response effort and ranking. Neither is universally right — it depends on how much your listing can absorb a bad stay.

Instant Book isn't the screening-free free-for-all hosts assume. You can require verified ID, a history of positive reviews, and acknowledgment of your rules, and Airbnb still blocks guests who don't clear them. You keep the ranking lift Airbnb gives instant-bookable listings and you skip the back-and-forth. The trade is that you're trusting your requirements to do the filtering rather than your own eyes. Request-to-book flips that: every guest waits for your yes, so you read each profile, but you owe fast replies to protect your response rate and you give up some visibility.

For a mid-range whole-home unit with solid requirements, Instant Book usually wins on volume without much added risk. For a high-value property, a shared space, or a building with strict neighbors, request-to-book buys you a human check that's worth the ranking cost. The deeper trade-off between the two modes is worth its own read: see Instant Book pros and cons before you flip the switch either way.

Your pre-booking screening checklist

Run this before you accept any booking. It takes under a minute once it's a habit.

• Guest has a verified government ID on file.
• Review count and text checked — read the words, not just the stars.
• Request message names who's coming and why.
• Stated guest count matches your listing's maximum.
• No same-night-plus-new-account-plus-blank-message combo.
• No local booking without a clear, specific reason.
• Guest acknowledged house rules and occupancy limit.
• Any vague answer got one clarifying question — and a straight reply.

If a booking clears all eight, accept it and move on. If it trips two or more, ask a question or decline. You won't get it right every single time, but you'll catch the stays that actually hurt.

Frequently asked questions

Can you reject Airbnb guests without penalty?

Yes. Declining a request-to-book carries no penalty as long as you're not discriminating on protected characteristics. Airbnb tracks your acceptance rate loosely, but a reasoned decline — occupancy mismatch, no reviews plus a vague message, a rule the guest won't agree to — is entirely within your rights. What you can't do is decline based on race, religion, national origin, gender, or the other categories Airbnb's nondiscrimination policy protects.

What guest requirements can you set on Airbnb?

You can require a verified government ID, a profile with no negative reviews from previous hosts, agreement to your house rules, and for some listings a profile photo. These live in your account's guest-requirements settings and apply to every booking automatically, including Instant Book. They're the closest thing Airbnb offers to a standing screen.

How do you check if a guest has bad reviews?

Open the guest's profile and read the reviews left by past hosts, not just the star count. Watch for hedged phrasing — "communication could improve," "would host again with clear rules" — which experienced hosts use to flag a problem politely. Zero reviews means no history to check, so lean on your requirements and the booking message instead.

Is request-to-book better than Instant Book for screening?

Request-to-book gives you a manual look at every guest, which is better for high-value or on-site listings where one bad stay hurts a lot. But Instant Book with strict guest requirements screens automatically and keeps Airbnb's ranking boost, which usually wins for resilient whole-home units. Match the mode to how much your property can absorb a mistake.