Free + Pro · Coverage
Check your forms and checkout
Separate the forms Gate House supports, the checks you enabled and the successful submissions observed on your site. Use that information alongside your own visitor-journey tests.
In version 1.21.0 and later, open Gate House directly in the WordPress sidebar, then choose the tab named in this guide. Version 1.20.1 and earlier use Settings → Gate House.
In WordPress: Gate House → Coverage
Find the forms your visitors use
Compare the page with your actual login, registration, reset, comment, review and checkout forms. Forms detected on this site can list installed form plugins and stored forms. Detection does not prove that a form is published, enabled or supported. Reading Coverage does not change settings or submit forms.
Free: read Native form coverage
The Visitor check column shows Off, Invisible or Human check. The Evidence column separately reports what has been observed:
- Not enforcing
- This form does not currently require a visitor check.
- Successful protected submission observed on this site
- A successful submission was observed with the current recorded setup. This does not test every rejection path or custom behavior.
- No current successful-use observation; test this form
- A check is enabled, but there is no current successful submission to show. Try the actual form.
- Configuration needs attention
- Review Provider and Diagnostics, correct the setup and try the form again.
Overview also shows enabled form types, successful-use observations and blocked attempts for the last 30 calendar days, including today, in UTC. Blocks can include configuration failures; a total is not proof that every blocked submission was spam.
Test complete journeys on staging
Keep your administrator session open and use a separate private browser window. Test successful and rejected submissions for each form you protect. For payments, use your gateway’s sandbox and test guest checkout, signed-in checkout, account creation during checkout and existing-order payment links where offered. Enable the intended checkout checks on staging before testing them.
Pro: review the status and its evidence
With Pro, expand See the evidence on a coverage row. Successful use observed on your site and matching release tests are separate evidence sources. The read-only compatibility assessment describes your setup; it does not run a checkout test.
- Working
- A successful protected submission was observed on this site, or matching release-test evidence is available. Read the evidence source; neither proves every journey on your site.
- Awaiting first use
- Verification is required, but no current successful use or matching release test is recorded.
- Attention / Needs configuration
- Review the row’s setup issue, Provider and Pro Activity.
- Observe only
- The visitor check is not required. Pro attempt limits or other abuse controls may still be enabled; review Rules separately.
- Unsupported / Not applicable
- There is no supported integration for that route, or its required plugin is inactive.
Pro’s Diagnostics → Run Protection Test runs labeled probes against supported guards, page rendering and counters. A rejected probe does not count as a successful visitor submission or make a coverage row Working.
Which integrations are included?
Free and Pro: native WordPress login, registration, password-reset requests and comments; WooCommerce My Account forms, product reviews, classic checkout, Checkout Blocks and native order-payment forms.
Pro: Contact Form 7 and WPForms submissions when those plugins are active, plus advanced controls for WooCommerce checkout page loads and authenticated legacy REST order creation. These last two do not use browser challenges.
Gate House requires WordPress 7.1+ and PHP 8.1+. WooCommerce integrations require 11.1.2+. Custom forms, headless clients, express wallets, saved-card setup, subscription renewals and gateway-specific payment routes need separate assessment. One successful checkout does not prove every payment method works.
Using Free and seeing a problem? Start with provider and configuration troubleshooting. Individual event history is a Pro feature.