Website blocking
Website blocking can deny eligible requests from blocked visitors when enabled. Automatic blocks for paid-click behavior allow a later direct, organic or referral arrival; confirmed bots, manual blocks and explicit geographic policies can still be denied. A false-positive denial can turn away a real customer.
On this page
Ad-platform exclusion limits future paid targeting. Website blocking can also deny an eligible blocked arrival before the page loads. The decision depends on the block reason, how the visitor arrives and the site’s enforcement and recovery settings.
What it stops
- Fake form submissions and bogus enquiries reaching your sales team.
- Fraudulent phone-number clicks that generate real call costs.
- Scrapers and abusive automation consuming your bandwidth and skewing your analytics.
A false positive is visible here
A wrongly excluded visitor never knows they were excluded from an audience. A wrongly blocked one sees an error page instead of your website. Be more conservative with your threshold when website blocking is on.
Enabling it
Turn it on in Settings → Protection. Existing block reasons and enforcement safeguards determine whether a request is denied. Paid-click rules do not automatically deny a later free arrival; confirmed automation, manual blocks and explicit location policies have different treatment.
Conversion threats
The dashboard distinguishes blocked sessions and known interaction attempts. A denied page cannot report an action that never happened, so a block count is not proof of a prevented form submission, phone call or sale.
Frequently asked questions
Does this affect my SEO?
Recognized legitimate crawlers have safeguards, but classification is not infallible. Inspect unexpected blocks and adjust or whitelist where appropriate.
Can I unblock someone who was wrongly blocked?
You can use the relevant unblock and whitelist controls. Website access and external audience or IP exclusion removal may take different paths; verify the outcome.