How to stop spam and unwanted bookings on your booking page
On this page
Start by distinguishing repeated nuisance requests from ordinary mistakes or a legitimate guest using an unexpected address. You'll need the host settings, the affected event and a test address you control.
Which control should I use to stop spam bookings?
Use an email block for a known sender, a domain block for a whole unwanted domain, and approval when the request needs human review. Blocking a broad email provider can exclude legitimate clients, so don't widen the rule merely because several nuisance requests happen to look similar. Be precise.
| Problem | First control to try | What it won't establish |
|---|---|---|
| Repeated requests from one known address | Block that email | The person's other addresses |
| Unwanted requests from one organization | Block that domain | Who operates unrelated domains |
| Public offer needs screening | Requires approval | Automatic qualification from answers |
| Link should reach selected invitees | Secret event or limited-use link | Identity verification of its holder |
These controls solve different problems. A booked time you later regret isn't always spam, and a guest using a personal address isn't automatically a fake booking.
The request approval guide covers review before acceptance. Use it when judgement is needed instead of assuming an email-domain rule can make that decision for you.
Where do I block an email or domain?
Open Settings, choose "Blocked" and add the address under "Blocked emails" or the domain under "Blocked domains". We check those host-level lists during booking submission, so an event link being public doesn't override an explicit block. Save a narrow rule.
The checked code inspects the main guest address and extra guest addresses. If an extra guest matches a block, the request can be rejected even when the main booker's address is allowed; that matters when diagnosing a legitimate booking that can't proceed.
For a domain entry, use the domain you intend to restrict, such as the organization's domain from the unwanted address. Don't claim a parent-domain entry automatically covers every subdomain: the checked implementation compares the supplied email domain against the stored list.
We also expose a business-email restriction, but it isn't proof of identity. Use it only if personal-email exclusion matches your actual invitation policy; many real guests have good reasons to use personal accounts.
Will Requires approval prevent an unwanted meeting being confirmed?
"Requires approval" lets you review a request before accepting it as a confirmed appointment. A person can still submit an unwanted request, and the host still has to inspect it and act on the decision instead of treating the toggle as a spam classifier. It adds judgement, not certainty.
Open the event's "Booking page" section to enable it. We place approval there, apart from the host's blocked-address settings, because reviewing an individual offer and rejecting an address across the account are different actions.
Suppose two public events receive unwanted requests, but a third is shared only with existing clients. You might require approval on the two public offers while leaving the established-client event unchanged, with the blocklist still applying at host level.
The approvals and booking-limit controls describe those restrictions. If requests consume attention even before confirmation, reduce exposure as well; approval alone doesn't make the public link undiscoverable.
Are secret and single-use links enough to prevent fake bookings?
Secret events and limited-use links reduce where and how an offer is shared, but possession of a link isn't identity verification. A forwarded private link can still reach someone you didn't intend, and a single-use link can be consumed by an unwanted request. Keep that distinction clear.
We support secret events, one-off links and single-use links. The one-off link guide explains offering selected times; use a restricted invitation when there isn't a reason to leave the same public offer available indefinitely.
As a planning example, sharing one single-use invitation with one intended guest limits the invitation's reuse, while a public event link remains an ongoing offer. That difference is about access to an opportunity, not a verified claim about the holder's identity.
Don't put a supposedly private link in a public footer and expect the label to protect it. Share it through the channel you've agreed with the guest, and handle mistaken or unwanted existing appointments through their management process.
How do I test a blocking rule without excluding real guests?
Submit a trial request using an address you control that matches the new rule, then repeat with an allowed address. A rejection test alone can show that something is blocked while missing the fact that the rule also prevents the guests you wanted to invite. Check both outcomes.
| Symptom | Likely cause | Next action |
|---|---|---|
| Legitimate company address is rejected | Its domain is on the blocklist | Review the stored domain |
| Main guest is allowed but submission fails | An extra guest matches a block | Check every submitted address |
| Another address still gets through | Email block matches only the listed address | Review approval or a justified domain rule |
| Private offer attracts strangers | The link was forwarded or published | Revisit sharing and review requests |
We validate the lists at submission, not by trusting whether the guest could open the booking page. A visible event doesn't establish that the final booking will pass the account's restrictions.
No combination here guarantees zero spam, and changing a blocklist isn't a cancellation of all earlier bookings. Inspect existing appointments deliberately, keep exceptions narrow and restore your test addresses after verification.
There isn't a paid anti-spam tier in Barq Meet; generous fair-use controls apply to everyone. Review current account features and restrictions, then set up a booking page with the review you need.
Steps
Identify the unwanted request pattern
Distinguish one repeated address, one domain and requests needing manual review. Choose the narrowest rule that addresses the actual problem.
Add a targeted rule under Blocked
In Settings, use Blocked emails or Blocked domains. Check the exact entry and save it.
Enable Requires approval when needed
Open Booking page on the affected event. Use approval when you need to inspect requests before accepting them.
Restrict how the offer is shared
Use a secret event or limited-use invitation for selected guests. Treat possession of the URL as access to the offer, not proof of identity.
Test blocked and allowed addresses
Submit controlled requests on both paths, including extra guests when enabled. Remove test entries and inspect existing bookings independently.
Frequently asked questions
Will blocking a domain cancel appointments already on my calendar?
Treat the block as a rule for future submissions, not an instruction to cancel existing appointments. Review unwanted bookings through their management process and contact legitimate guests when a previously agreed appointment needs to change. Review existing reservations through their own management controls and contact affected guests deliberately, instead of assuming a new access rule withdraws appointments that were already accepted before the block was added.
Why can someone open my page even though their email is blocked?
The address restriction is checked when the request is submitted. Opening a public booking page doesn't prove the visitor is allowed to complete a booking, and hiding the page is a different concern from validating a submitted address. Inspect the restriction at the point where booking details are submitted, keeping access to the public URL separate from whether a particular email address is permitted to finish a reservation through it.
Should I block every personal email provider?
Only if that exclusion matches your real invitation policy. Personal addresses can belong to legitimate clients or candidates, and a company-domain address isn't identity verification; targeted blocks and review are often more precise than a broad exclusion. Use the narrowest rule that handles the unwanted inquiries and combine it with request review when necessary, so legitimate clients using ordinary personal addresses aren't rejected solely because of their email provider.
Related pages
- How to approve meeting requests before booking
Review meeting requests with Booking page > Requires approval. Set the 1,440-minute timeout and understand pending holds before Google invites.
- How to create a private booking link for specific clients
Hide an event from your public profile with Secret event. Compare reusable, one-off and single-use links, then test access before sending it.
- Booking approvals: hold a time before you say yes
Turn on Requires approval under Booking page. Requests hold time; Google invites wait for approval. The default timeout is 1,440 minutes.
- How to create a custom times link
Offer three hand-picked meeting times with a custom times link. Choose real availability or manual times, set an expiry and close after one booking.
- What is a booking page?
A booking page displays available appointments and collects guest details. See its six parts, a 30-minute example and what stays private.
Create your free booking link
Sign in with Google, create an event and share your link.
Create your free link