Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Info

Wordfence Rate Limiting Settings Explained: What Each Option Does

Wordfence Rate Limiting Settings Explained: What Each Option Does

Short answer

Wordfence rate limiting caps how many requests, page views and 404 errors a visitor or crawler can make per minute, then throttles or blocks them. Let verified Google crawlers through, use high throttle limits for humans, a low block limit for crawler 404s, and fairly short block times.

Key takeaways

  • Rate limiting lives in Wordfence firewall options.
  • Give only verified Google crawlers unlimited access.
  • The anyone's requests limit counts every request, so keep it high.
  • A low crawler 404 limit stops vulnerability scanners quickly.
  • Throttle real people and block clearly abusive bots.
  • Tune limits by reviewing Live Traffic for a week.

What are Wordfence rate limiting settings?

Wordfence rate limiting settings cap how many requests a visitor, crawler or bot can make per minute, and throttle or block anyone who goes over the limit, to stop scrapers, brute force tools and aggressive bots from overloading your site.

You find them in Wordfence > All Options > Firewall Options > Rate Limiting. Wordfence documents each one on its rate limiting help page.

Rate limiting works at the firewall level. Wordfence counts requests by IP address and decides whether each visitor looks human or like a crawler. It then applies the matching rule.

Here is a quick map of the main settings:

SettingWhat it limitsTypical action
Rate limiting on/offThe whole featureOn for most sites
How should we treat Google's crawlersWhether Google is exemptVerified Google crawlers unlimited
If anyone's requests exceedTotal requests from any visitorThrottle at a high number
If a crawler's page views exceedPage views from botsThrottle
If a crawler's pages not found (404s) exceed404s from botsBlock
If a human's page views exceedPage views from peopleThrottle at a high number
If a human's pages not found (404s) exceed404s from peopleThrottle
How long is an IP address blockedBlock durationMinutes to hours
Allowlisted 404 URLsPaths ignored for 404 countingCommon missing files

Option labels can change between versions, so check the help page if yours look slightly different.

Should I turn rate limiting on?

Yes, most sites benefit from rate limiting with moderate values, because it stops scrapers and vulnerability scanners early, but set the limits high enough that real visitors and good crawlers are never caught.

Wordfence's default values are conservative and suit many sites. Problems usually come from setting numbers too low, not from enabling the feature.

Turn it on, keep defaults for a week, then review Wordfence > Tools > Live Traffic to see who is being throttled. Adjust from there.

For the wider firewall setup, see how to set up the Wordfence firewall.

How should Wordfence treat Google's crawlers?

Choose Verified Google crawlers have unlimited access to this site, which exempts real Googlebot after Wordfence checks its identity, while fake bots claiming to be Google still face normal limits.

The three choices are roughly:

  • Verified Google crawlers have unlimited access. Wordfence confirms the crawler is really Google. Recommended.
  • Anyone claiming to be Google has unlimited access. Trusts the user agent string, which any bot can fake. Not recommended.
  • Treat Google like any other crawler. Applies normal limits to Google. This risks slowing indexing.

Many bad bots pretend to be Googlebot. Google explains how verification works in its guide on verifying Googlebot, which uses reverse DNS lookups.

What does the anyone's requests limit do?

This setting caps the total requests per minute from any single IP, counting pages, images, scripts and AJAX calls together, and throttles or blocks that IP when it goes over.

It is a catch-all limit. Because it counts every request, it should be the highest of your limits.

A modern page can make dozens of requests on load. A visitor who opens several tabs quickly can reach a low limit without doing anything wrong.

Keep this high, often in the hundreds per minute, and choose throttle rather than block. That leaves room for busy pages, logged-in editors and shared office networks.

What do the crawler page view and 404 limits do?

Crawler limits apply to visitors Wordfence identifies as bots, capping their page views and their 404 errors per minute, because bots that hit many missing pages are often scanning for vulnerabilities.

If a crawler's page views exceed controls how fast a bot can fetch pages. Good bots like Bingbot usually crawl politely. Aggressive scrapers do not.

If a crawler's pages not found (404s) exceed is one of the most useful rules. Vulnerability scanners request lists of paths like old plugin files and backup archives. Almost all of them return 404.

A low limit with block stops these scans fast.

These settings also help with AI crawlers that fetch many pages quickly. For more control, see how to block AI crawlers in WordPress.

What do the human page view and 404 limits do?

Human limits apply to visitors Wordfence thinks are people, capping their page views and 404 errors per minute, and they should be generous because real users browse in bursts and sometimes hit broken links.

If a human's page views exceed should be high enough that fast readers, shoppers comparing products and people opening many tabs never reach it.

If a human's pages not found (404s) exceed catches people, or bots that look human, guessing URLs. Real visitors rarely hit many 404s in one minute unless your site has broken images or links.

If you have many broken links, fix them first. Otherwise this rule can throttle real users. Choose throttle for both human rules on most sites.

What is the difference between throttle and block?

Throttle temporarily slows the visitor by returning a 503 Service Unavailable response until their request rate drops, while block bans the IP for the duration you set in the block time setting.

Throttling is forgiving. A real person who trips a limit waits briefly and then continues. MDN describes how browsers handle a 503 Service Unavailable response.

Blocking is strict. It suits clear abuse, such as a crawler hitting dozens of 404s per minute.

A practical rule: throttle humans, block obviously bad crawlers.

How long should an IP be blocked?

Set the block duration between a few minutes and a few hours for most sites, long enough to stop a scan but short enough that a shared IP or mistaken block clears on its own.

Many attackers rotate IPs, so very long blocks add little protection. They mainly risk locking out innocent visitors on shared networks, such as offices, schools and mobile carriers.

If you lock yourself out, see how to fix Wordfence blocking the admin. Adding your own IP to the allowlist in Firewall Options prevents that.

What are allowlisted 404 URLs?

Allowlisted 404 URLs are paths Wordfence ignores when counting 404 errors, such as common missing files like favicon or apple-touch-icon images that browsers request automatically.

Without this list, a visitor's browser asking for a missing icon could count toward their 404 limit. That adds up when browsing several pages.

Add paths here if Live Traffic shows real users being throttled for the same missing file. Better still, add the missing file, which removes the 404 for everyone.

How do I tune rate limits without blocking real visitors?

Start with Wordfence defaults, watch Live Traffic for throttled and blocked entries for a week, raise any limit that catches real users, and tighten only the crawler 404 rule if scanners keep getting through.

A good tuning routine:

  1. Leave the defaults on for several days.
  2. Filter Live Traffic for throttled or blocked visitors.
  3. Check whether they are real users, good bots or attackers.
  4. Raise limits that catch real users or services you rely on.
  5. Add your monitoring and uptime services to the allowlist.

High server load from bots may need extra layers. Our guide on Wordfence high CPU usage covers performance.

Edge rules such as Cloudflare WAF rules can stop bots before they reach WordPress.

What rate limiting values make sense for most sites?

Keep Google verified and unlimited, set high throttle limits for general and human page views, use a low block limit for crawler 404s, and keep blocks fairly short.

Treat these as starting points, not rules:

SettingStarting point
Google's crawlersVerified crawlers unlimited
Anyone's requestsHigh, throttle
Crawler page viewsModerate, throttle
Crawler 404sLow, block
Human page viewsHigh, throttle
Human 404sModerate, throttle
Block durationMinutes to a few hours

Busy shops, membership sites and sites with heavy AJAX need higher limits. For the rest of the plugin, read Wordfence settings explained. The free plugin is on the WordPress.org plugin directory.

Frequently asked questions

Where are rate limiting settings in Wordfence?

Go to Wordfence, then All Options, and open the Firewall Options section. The Rate Limiting area lists the Google crawler option, request and page view limits for humans and crawlers, the 404 limits, block duration and allowlisted 404 paths.

Can Wordfence rate limiting block Googlebot?

It can if you set Google to be treated like any other crawler or set very low limits. Choose the option that gives verified Google crawlers unlimited access. Wordfence then checks that the crawler is genuine before exempting it from limits.

What does throttle mean in Wordfence?

Throttling temporarily returns a service unavailable response to a visitor making too many requests until their rate drops. It does not ban them. It suits real people who browse quickly, while blocking is better for clearly abusive crawlers and scanners.

Why is Wordfence throttling real visitors?

The limits are probably too low for your pages, or visitors share one IP address, such as an office network. Missing files can also push up 404 counts. Raise the limits, fix broken links and add common missing paths to the allowlist.

Does rate limiting reduce server load?

Yes, partly. It stops aggressive bots and scanners from making thousands of requests. However, each request still reaches WordPress before Wordfence acts, so very heavy bot traffic may also need edge protection from a CDN or web application firewall.

Sources

  1. Rate limiting Wordfence Help
  2. Firewall options Wordfence Help
  3. Verifying Googlebot and other Google crawlers Google Search Central
  4. 503 Service Unavailable MDN Web Docs
  5. Wordfence Security WordPress.org Plugins

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.