Wordfence Integration
Tier: Basic — Plugin-based toggle integration. Keeps Wordfence's REST namespace available when SyteOps' REST API Restriction is on, and asks search engines not to crawl Wordfence's self-check URLs.
The Wordfence integration in SyteOps is a compatibility toggle. When you enable REST API Restriction, it blocks anonymous REST traffic by default. Wordfence uses its own REST namespace for authentication, configuration, and security operations that need to remain reachable — this toggle ensures that.
What the toggle does
- Adds the Wordfence REST namespace to the allowlist when REST API Restriction is enabled.
- Lets Wordfence continue to receive its own security-related requests without being blocked by SyteOps' restriction.
- Has no effect when REST API Restriction is off — Wordfence works either way, the toggle just preserves Wordfence's access when everything else is locked down.
Keeping Wordfence's self-check URLs out of search results
Wordfence checks your site by requesting an address that looks like yoursite.com/?wordfence_lh=1&hid=.... The page already tells search engines not to index itself, but Google can still crawl those addresses and list them in Search Console as "Crawled - currently not indexed". With the toggle on and Wordfence active, SyteOps adds two lines to your site's robots.txt file so crawlers skip them:
Disallow: /*?wordfence_lh=
Disallow: /*&wordfence_lh=
- No extra plugin or code snippet is needed. If you added these lines by hand, or with a small custom plugin, SyteOps recognizes them and does not add them twice. On Squirrly SEO, a line you added yourself that is exactly the same as one SyteOps adds is treated as SyteOps's own and is removed along with the feature; any line that differs is never changed. A line with a note after it, or any other difference, counts as different.
- It works with whichever SEO plugin writes your robots.txt. With Yoast SEO and Rank Math the lines appear in the file they generate. With Squirrly SEO's Robots File turned on, SyteOps adds the lines to the list you see under the Robots File settings, in the "all crawlers" section, and puts them back if a settings save removes them. Older Squirrly releases (14.2.7 and earlier) rewrite the
&character in that list, so SyteOps adds only the first line (?wordfence_lh=) there on every version; it covers the addresses Wordfence actually uses and is safe everywhere. - Turning the toggle off, or deactivating Wordfence, takes back only the lines SyteOps added or took over.
- A change can take a while to show up if your host or Cloudflare caches robots.txt. Whenever the lines are added or removed, SyteOps asks your cache layers to refresh the file in the background, but it can still take a short time for crawlers to see the new version.
- If your site has a real robots.txt file in its main folder, the web server serves that file and WordPress never gets a say, so SyteOps cannot add the lines. Add them to that file yourself, or delete it so your SEO plugin or WordPress can serve one.
Setup
- Install and activate the Wordfence plugin from WordPress → Plugins.
- Navigate to SyteOps → Integrations.
- Find Wordfence in the Security category.
- Toggle it ON and click Save Changes.
If Wordfence isn't installed, SyteOps disables the toggle and shows "Not Installed".
What endpoints become reachable
When this toggle is on and REST API Restriction is enabled, Wordfence's entire v1 REST namespace is allowed through:
| Path | Purpose |
|---|---|
/wp-json/wordfence/v1/* | Wordfence authentication, configuration, and security endpoints |
Wordfence verifies its own requests against these endpoints — SyteOps isn't weakening Wordfence's security, just keeping Wordfence's namespace open while everything else stays restricted.
Review Portal sign-in
This works whether or not the toggle is on. When Wordfence's login reCAPTCHA is turned on, the Review Portal's sign-in card passes Wordfence's security check the same way the WordPress login screen does, so reviewers are not sent a "Login Verification Required" email every time they sign in, and Wordfence still counts wrong passwords toward its lockout. When Wordfence does send a verification email, its link brings the reviewer back to the portal after they sign in. Reviewers who sign in from their own private review page, with their own username or email, are not asked by Wordfence to confirm by email at all: the private link sent to them already shows the sign-in is theirs. Anyone holding that link can still only try passwords for that one reviewer, and Wordfence's lockout, two-factor and passkey rules all still apply, so treat the link like the private link it is. After three wrong passwords in an hour, the private-page shortcut pauses for a day. Reviewers who use Wordfence two-factor codes or passkeys are pointed to the standard sign-in page to finish. While the check is running, the sign-in button shows as busy, and Google's reCAPTCHA notice appears under it instead of Google's floating badge in the corner of the page.
Common use-cases
- Sites running both Wordfence and SyteOps REST API Restriction.
- Sites where Search Console reports Wordfence self-check addresses as "Crawled - currently not indexed".
- Security-heavy configurations where you want the REST API locked down but Wordfence's paid features (like Country Blocking or Real-Time IP List) still functioning.
Related
- REST API Restriction
- Integrations Overview
- Cloudflare Setup Guide — if you stack Cloudflare in front of Wordfence