| 开发者 | huloglobal |
|---|---|
| 更新时间 | 2026年11月13日 17:39 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wc-api), robots.txt and sitemaps are never blocked.noindex; closures (business hours, maintenance) send HTTP 503 with Retry-After so search engines treat them as temporary.CF-IPCountry (and cf-region-code), Akamai and Fastly country headers, once you tell the plugin the site is behind that CDN. Any visitor can send these headers, so they are honoured only for requests arriving from a trusted proxy: Cloudflare's published ranges (one tick) or the addresses you list (or the HULO_TRUSTED_PROXIES constant).GEOIP_COUNTRY_CODE, MM_COUNTRY_CODE).X-Forwarded-For the right-most address that is not one of your proxies is taken.no-store and DONOTCACHEPAGE, so no page cache stores a block page.GET /wp-json/hulo-geo-block/v1/check returns the current visitor's verdict (uncached). A server-side caller can pass the visitor's country signed with a secret.No. Administrators are never blocked, wp-admin and the login page are never blocked, and the plugin will not switch on rules that would allow no one.
No. Geo-block works on any WordPress site. If you do run it, Geo-block also guards add-to-cart and checkout and can use the shop's MaxMind geolocation.
They are allowed; allowlists, business hours and maintenance still work. Set up a country source (see Installation, step 2) so countries are known.
Yes. Block pages are never cached. If your cache serves HTML without running WordPress, turn on the page-cache helper on the Settings tab. Checkout and payments always re-check the visitor on the server.
Yes, by default search and link-preview crawlers are let through.
Country headers are only believed when the request comes from a proxy you trust, so a visitor cannot send their own. A crawler User-Agent only lets a visitor browse, never buy or pay, and with reverse-DNS verification on, a fake Googlebot or Bingbot is treated like any other visitor.
No. See "External services" below.
hulo_geo_block_rate_limit filter. The 429 answer's Retry-After now says when the window resets.wc-api and wc-ajax exemptions follow what WordPress actually routed; optional reverse-DNS verification of Googlebot and Bingbot.