A real estate marketing manager and a developer in Kochi compare a printed listing brochure with a laptop.

Vercel · Security

Your listings show up on copycat sites before buyers see them. Challenge the scrapers and keep Google in.

Scripts pretend to be browsers, copy your pages and pad your analytics. AI crawlers take bandwidth you pay for. Vercel’s bot rules challenge traffic that is not a real browser and can log or deny known AI crawlers. Both are off until you switch them on, and Google and other verified bots get through on their own.

Salesforce consulting partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE, India and US desks

The problem

What bots cost you today.

What Bot Management is

Bot Management, in plain words.

Facts from Vercel’s own pages, checked on 16 October 2026. The sources are at the end of this page.

Layers
DDoS protection, the Web Application Firewall and bot protection rules, in that order.
Bot protection ruleset
Challenges non-browser traffic and catches requests that claim to be a browser, like a curl request posing as Chrome. Off by default.
AI bots ruleset
Logs or denies known AI crawlers. Vercel keeps the list of AI bots up to date. Off by default.
Good bots
Verified bots such as Google’s crawler are let through on their own, checked by IP ranges, reverse DNS and Web Bot Auth.
Where it works
Only when Vercel is the front door. It does not work with Cloudflare or another CDN placed in front of the site.
Plans
Both managed rulesets are available on all plans.

How it works

From bot traffic in the logs to rules that leave Google alone.

Five steps. Nothing is challenged until we have seen what the rule would catch.

Five steps: bot rules on in Log mode, review flagged traffic, switch to Challenge, choose AI crawler rules, let trusted tools through.

Infographic

The same steps are written out below.

Step by step

What happens at each step.

  1. Log

    Turn on bot rules in Log mode

    In Project, Firewall, the bot protection ruleset records what it would catch.

  2. Review

    Review the traffic it flags

    Check that monitoring tools and partner feeds are not in the list.

  3. Challenge

    Switch to Challenge

    Traffic that is not a real browser now has to prove it.

  4. AI

    Choose what AI crawlers get

    Log them, or deny them if you do not want your pages in AI tools.

  5. Allow

    Let trusted tools through

    WAF bypass rules for your uptime monitor and partner webhooks. BotID on the forms that matter.

How it fits together

Where bot rules sit between the open web and your site.

Scrapers, AI crawlers and real visitors all arrive at the same door. Bot rules sit at that door, in front of your site, Salesforce and your database. Verified bots like Google are let through. It only works when Vercel is the first stop, with no other proxy in front.

Scrapers, crawlers and visitors meet Vercel bot rules before the site, with verified bots allowed through.

Infographic

Where it sits next to the systems you run today.

Use cases · worked examples

One worked example in each industry.

How Bot Management fits into the work of the industries we serve, one step at a time.

  1. Listings copied by scrapers are protected by bot rules that challenge fake browsers while search engines still index.

    Example 1 · Real estate, Bengaluru · Infographic

    Marketing manager at a Bengaluru residential developer

    Today: Our new listings and floor plans show up on aggregator sites within a day, sometimes with the wrong price. Buyers call about numbers we never published.

    After: The bot protection ruleset challenges scripts posing as browsers. Search engines still index the listings, and enquiries keep landing in Salesforce.

    Worked example, step by step

    1. Mon 10:00Marketing manager. Finds this week’s listings on two aggregator sites.
    2. Mon 11:00Mindcat. Turns on the bot protection ruleset in Log mode.
    3. Tue 11:00Mindcat. Reviews a day of flagged traffic: scripts posing as Chrome, plus Google’s crawler passing as verified.
    4. Tue 11:30Mindcat. Switches the ruleset to Challenge.
    5. ThuMarketing manager. Posts the next launch. Buyers see it on the developer’s own site first.

    Search still finds the listings, and enquiries go to the developer’s Salesforce, not a copycat’s inbox.

    Real estate CRM
  2. Odd traffic on a launch page is flagged by bot rules, challenged, and the agency report shows real visitors.

    Example 2 · Marketing agencies, Austin · Infographic

    Account director at an Austin performance marketing agency

    Today: A client’s launch page showed a spike in visits and no extra leads. The client asked if we were padding the report.

    After: Bot rules in Log mode show how much of the spike was scripts. Once they are challenged, the monthly report counts people.

    Worked example, step by step

    1. Day 1Account director. Sees visits triple on the launch page with flat leads.
    2. Day 1Mindcat. Turns on bot protection and AI bots rulesets in Log mode.
    3. Day 3Mindcat. Shows the director which visits were non-browser traffic.
    4. Day 3Mindcat. Switches bot protection to Challenge and AI bots to Deny, as the client asked.
    5. Day 30Account director. Sends a report where visits and leads move together.

    The client trusts the numbers again, because the agency can show where the fake visits went.

    Marketing agencies
  3. Scripts on a tracking page are challenged by bot rules while a merchant feed is allowed through.

    Example 3 · Couriers, Jeddah · Infographic

    Operations manager at a Jeddah courier company

    Today: Scripts check thousands of tracking numbers on our public page every hour. Customers say tracking is slow, and our merchant partners’ feeds time out.

    After: Bot rules challenge the scripts. A WAF bypass rule keeps the merchants’ integration flowing, so partners keep their feed.

    Worked example, step by step

    1. 09:00Ops manager. Hears from customer service that tracking is slow again.
    2. 09:30Mindcat. Turns on bot protection in Log mode and lists the merchant feeds it would flag.
    3. 11:00Mindcat. Adds a WAF bypass rule for the merchants’ integration.
    4. 11:15Mindcat. Switches bot protection to Challenge.
    5. 12:00Customers. Track parcels at normal speed.

    Merchants keep their feed, customers get fast tracking, and the scrapers have to prove they are browsers.

    Couriers and delivery
Examples of the work, not client stories. Times in each example show the order of events, not a measured result.

Is it for you

When Bot Management fits, and when it doesn’t.

Good fit

Not for you yet

Your content gets copied or your reports show fake visits
Cloudflare or another CDN sits in front of the site
You want a say in whether AI crawlers read your pages
You expect it to stop every bot
Vercel is the first thing visitors reach
Your bot problem is fake form sends: that is BotID
You still need Google to index everything
The site is not hosted on Vercel

What Mindcat does

We build it, then we run it.

The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days. After go-live, we keep it patched, watched and changing every month.

FAQ

What teams ask about Bot Management.

Will this hurt our Google ranking?
Vercel lets verified bots such as Google’s crawler through on their own, using IP ranges, reverse DNS and Web Bot Auth. We still check the logs after go-live to confirm search crawlers are passing.
Is it on already?
No. The bot protection and AI bots rulesets are both off by default. Someone has to switch them on per project, and we do it in Log mode first.
We use Cloudflare in front of the site. Does this work?
No. Vercel says bot protection does not work when a reverse proxy such as Cloudflare or another CDN sits in front of the deployment. You would pick one front door, and we help you decide which.
Can we block AI crawlers but keep Google?
Yes. The AI bots ruleset logs or denies known AI crawlers from a list Vercel maintains, and it is separate from verified search bots.
Does it stop fake form sends?
It catches simple scripts. For contact, sign-up and checkout forms we add BotID, which checks each send on the server before it reaches Salesforce.

Sources

Where these facts come from.

Checked against Vercel’s own pages on 16 October 2026. Vercel changes fast, so we check again before any plan we write for you.

Vercel is a product of Vercel Inc. Mindcat builds and runs work on it for clients; we are not affiliated with or endorsed by Vercel.

Start here

Tell us what you want built, and where it runs today.

One or two lines is enough. You hear back within 24 hours from the person who signs the work.

Salesforce consulting partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE, India and US desks