For a general WordPress site that needs an age gate on the whole site or selected content, start by evaluating Age Gate. For a WooCommerce store, choose based on where the check must happen and how much assurance it needs: WooCommerce Age Verification Manager documents configurable store triggers and remembered verification state, while AgeOnce, Token of Trust, and OneGuard describe hosted verification flows with differing product rules, identity checks, and order handling.
A yes/no popup or date-of-birth form is a self-declaration, not an identity-backed check. Neither type of plugin should be treated as a universal legal-compliance solution. The right fit depends on your products, customer journey, privacy obligations, and applicable rules.
Which WordPress age verification plugin should you choose?
Choose by the job the plugin must do, not by its name or installation count. A content gate that asks visitors to confirm their age solves a different problem from a store workflow that blocks a product, checks a customer at checkout, or sends information to an external identity service.
| Option | Best fit | Documented approach and scope |
|---|---|---|
| Age Gate | General WordPress sites and content publishers | Self-declaration or date entry; whole-site or selected-content rules with per-content age thresholds, styling controls, and cache-related options. |
| WooCommerce Age Verification Manager | Stores that want configurable checks across the shopping journey | Self-confirmation or date-of-birth checks at entry, restricted product or taxonomy views, add-to-cart, and checkout; signed-cookie storage and user metadata are documented. |
| AgeOnce | Stores or publishers considering an external verification service | Hosted service account; rules for products, categories, tags, posts, pages, and custom post types, with WooCommerce checkout and optional signup gating. |
| Token of Trust | Merchants considering ID-backed verification or broader identity workflows | Government-ID-backed checks, configurable WooCommerce checkout or selected-product checks, and WordPress page checks; a separate self-declaration gate is optional. |
| OneGuard | Stores that want product-scoped checks linked to order handling | Hosted phone-based check after checkout; restricted orders can be held pending verification and automatically updated after success. |
These are feature descriptions, not results from a head-to-head performance test. Compare the exact verification method, challenge point, data flow, service terms, and customer experience against your own requirements.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute#1 Best Overall
How do the verification methods differ?
Self-declaration
A yes/no prompt asks a visitor to state that they meet an age threshold. A date-of-birth form asks for a stated birth date. These methods can put a visible gate in front of content or a store journey, but they do not establish identity. Age Gate and WooCommerce Age Verification Manager document these kinds of checks; Token of Trust also offers a separate optional self-declaration gate.
Hosted or identity-backed verification
A hosted flow involves an external service. Token of Trust describes government-ID-backed checks; AgeOnce describes a service-account-based verification flow; OneGuard describes a phone-based check after checkout. Those descriptions are not interchangeable: confirm the exact check offered for your use case, the information transmitted, the service’s terms, and what happens if a customer cannot or does not complete it.
An age prompt and an identity-backed check provide different levels of assurance. Do not describe either as legally sufficient without confirming the applicable rules for the product, location, and sales journey. Token of Trust says its software alone cannot guarantee compliance with every applicable law or regulation, and OneGuard likewise says its tools do not guarantee legal compliance.
What each plugin documents
Age Gate: a flexible gate for WordPress content
The WordPress.org listing describes whole-site and selected-content rules, per-content age thresholds, yes/no or date-entry choices, customizable date order, a remember-me option, branding and styling controls, optional legal notes, redirect behavior, and bot exclusions. It also identifies the plugin as open-source software.
Recommended Free Tools
Age Gate’s directory listing documents a non-caching mode and warns that caching can make the gate appear stuck; it points to JavaScript mode or the cache-bypass option as possible approaches. Test the chosen behavior with your site’s actual caching setup, theme, language configuration, and excluded post types.
The WordPress.org Plugin Directory’s 2026 snapshot reported 40,000+ active installations for Age Gate. That is a dated adoption indicator, not a quality score or evidence that it fits a particular site.
WooCommerce Age Verification Manager: configurable store checkpoints
WooCommerce’s documentation describes checks at site entry, restricted product or taxonomy views, add-to-cart, and checkout. Merchants can use self-confirmation or date-of-birth checks and apply rules globally or to specific objects. The documented operational features include signed-cookie storage, user metadata for logged-in customers, a consent-aware mode, logs, and WP-CLI utilities.
This is a candidate when you need to decide where a store challenges customers and how remembered state interacts with consent and administration. Test the complete journey alongside your checkout, cookie-consent setup, cache, and any relevant extensions; the documentation does not establish which legal standard applies to your business.
AgeOnce: an external service for content and WooCommerce
The WordPress.org listing describes rules for products, categories, tags, posts, pages, and custom post types, plus WooCommerce checkout and optional signup gating. It says an AgeOnce account is required. Its 2026 listing states that the free plan includes 100 verifications per month; confirm current quotas and service terms before relying on that limit.
The listing also says, “No. WooCommerce does not ship a native age-requirement feature.” That is AgeOnce’s statement about WooCommerce, not a conclusion about what any merchant is legally required to implement.
Token of Trust: identity checks and optional self-declaration
The plugin listing describes government-ID-backed verification, checks at WooCommerce checkout or for selected products and WordPress pages, and an optional self-declaration gate. It is positioned for merchants considering more assurance than a simple popup, as well as businesses with broader identity or KYC workflows.
The listing currently describes a free verification quota but does not establish an amount or commercial terms that should be relied on here. Confirm current limits and terms directly. The publisher also states: “No software by itself can determine or guarantee a business’s compliance with every applicable law or regulation.”
Free tools Windows power users keep installed
One-click scans. No signup required.
OneGuard: product checks tied to order workflow
The WordPress.org listing describes selecting restricted products and setting age thresholds, with the customer completing a check on a phone after checkout. Orders can be held pending the check and automatically updated after success.
OneGuard’s privacy section identifies its hosted service and documents site and order/customer information sent for checks. Review the current data flow and service terms against your privacy obligations. Its publisher states: “No. Oneguard provides age-verification tools, but requirements vary by product, country, and business.”
How to evaluate an age verification plugin for your site
- Map the required scope. Decide whether the gate must cover the whole site, selected pages or posts, selected products or taxonomies, or a particular commerce checkpoint. Do not assume a content gate protects every stage of a store purchase.
- Choose the assurance method. Determine whether self-confirmation, date entry, or a hosted identity-backed check is appropriate for the use case. Treat them as distinct approaches rather than equivalent features.
- Trace the customer path. For a store, identify whether the customer is challenged at entry, product view, add-to-cart, checkout, or after checkout as part of order review. Check what happens when verification is incomplete or unsuccessful.
- Review information handling and consent. Find out whether remembered state is kept in a cookie or user metadata, whether an external provider receives customer or order details, and what consent controls or logs are available.
- Test site operations. Check compatibility with the real theme, checkout, cache, multilingual configuration, and relevant extensions. Confirm that the prompt is usable and that customers can complete the required flow.
- Verify service dependencies. For hosted services, check account requirements, current quotas and pricing, terms, support, and the data sent to the provider before enabling the flow.
- Confirm the applicable rules. Requirements can depend on jurisdiction, product, customer journey, and enforcement rules. Check with qualified counsel or the relevant regulator rather than assuming a plugin supplies a legal determination.
Is an 18+ popup enough?
A popup can present a self-declaration gate, but its presence does not turn a visitor’s answer into an identity-backed check or prove that a particular legal requirement has been met. Whether any control is sufficient depends on the rules that apply to the business, its products, and the customer’s location and journey. The plugin listings describe capabilities; they are not jurisdiction-by-jurisdiction legal guidance.
For that reason, treat “age verification” as a broad product label, then check what the selected tool actually does: what it asks, where it blocks access or purchase, whether it verifies identity, and what data leaves your site.
How does WooCommerce age restriction work?
WooCommerce stores can use a plugin to put a check at one or more stages of the shopping process. WooCommerce Age Verification Manager documents configurable checks at entry, restricted product or taxonomy views, add-to-cart, and checkout. OneGuard documents a different flow in which the customer completes a phone check after checkout and an order can remain on hold until verification succeeds.
AgeOnce’s listing says WooCommerce does not include a native age-requirement feature. That statement does not mean every store needs the same plugin or checkpoint: determine the right product rules and verification method for the store’s own requirements.
Frequently asked questions
Can I restrict specific WooCommerce products?
Yes. WooCommerce Age Verification Manager documents object-level rules, and the AgeOnce, Token of Trust, and OneGuard listings describe selected-product rules or thresholds. Their verification methods and customer flows differ, so check each plugin’s current documentation before choosing.
Does an age verification plugin guarantee compliance?
No universal guarantee is established. Token of Trust and OneGuard explicitly state that their software or tools do not guarantee compliance with every applicable requirement. A merchant needs to identify and confirm the rules relevant to its own products and customers.
Which plugin has the most active installations?
The WordPress.org Plugin Directory’s 2026 snapshot lists Age Gate at 40,000+ active installations and Easy Age Verify at 1,000+. These dated directory counts indicate adoption only; they do not establish quality, suitability, or comparative performance.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
