Description
Privacy-first age verification for WooCommerce and WordPress. WooCommerce has no built-in official age gate — AgeOnce adds real checks at checkout, optional customer signup on My Account, restricted content, and an optional full-page site entrance gate, without archiving customer IDs or face images on your server. Your site keeps the verification outcome and an Audit ID. Start free with 100 verifications per month, no credit card required.
Full setup guide (video, install, free plan): WordPress age verification on AgeOnce.com
See how it works
About 90 seconds: install, connect credentials, set product rules, verify at checkout, then review order status and the AgeOnce audit log.
Use it for alcohol, tobacco, vaping, cannabis, adult content, supplements, events, memberships, or any other WordPress content that should be shown only after age verification.
Instead of relying on a simple “Are you 18?” popup, AgeOnce sends the visitor through a dedicated verification flow and then returns them to your store. The plugin can block WooCommerce checkout until verification is complete, optionally require age verification before customers create a store account on My Account, protect selected posts or pages, optionally gate the whole site at the entrance, and record verification details on WooCommerce orders and new customer accounts.
Age assurance is now a legal requirement in many markets — the UK Online Safety Act, US state age-verification laws, the EU Digital Services Act, and FDA PACT rules for tobacco and vape all expect real checks rather than a self-declared age box. AgeOnce gives you a workflow you can show an auditor while keeping data collection to a minimum.
You can start with the AgeOnce free plan. No credit card is required for the free tier, so you can install the plugin, connect your site, and test the full WooCommerce checkout, optional signup gate, or content restriction flow before upgrading.
Why stores use AgeOnce
- Protect checkout for restricted products – Require age verification only when the cart contains products or categories that need it.
- Optional store signup age gate – Require age verification before guests can create a WooCommerce customer account on My Account (off by default; configurable 16+/18+/21+).
- Optional site entrance gate – Gate the whole site with a full-page screen until verification; keep Terms, Privacy, 2257, or Contact public.
- Avoid blanket age gates – Keep normal products and public content open while gating only the items that require verification.
- Support 16+, 18+, and 21+ rules – Configure different minimum ages for different product categories, tags, posts, pages, or custom post types.
- Brand the gates – Logo, colours, optional copy, and custom CSS for the entrance screen and inline banners.
- Keep proof on orders and accounts – Store verification status, transaction ID, and timestamp on WooCommerce orders (and on new customer accounts when signup verification is enabled).
- Start free – Use the free AgeOnce plan to test real verification before moving to a paid plan.
- Use one verification flow across your site – The same AgeOnce verification can unlock checkout, signup, protected content, and the entrance gate for guests and logged-in visitors.
- Respect privacy – The plugin only contacts AgeOnce when a visitor chooses to verify their age.
Features
- Site entrance gate – Optional full-page gate before browsing. Choose allowed pages, entrance links, editor preview, and optional search-bot bypass (SEO).
- Gate appearance – Logo, separate colour sets for entrance and inline banners, optional heading/message, custom CSS, and theme template overrides under
yourtheme/ageonce/. - WooCommerce checkout age gate – Disable checkout until the customer completes age verification for restricted cart items. Product pages stay visible unless you opt in to hiding descriptions.
- Optional WooCommerce customer signup age gate – On My Account registration, block create-account until AgeOnce verification (disabled by default; choose 16+, 18+, or 21+).
- Product-level control – Mark individual WooCommerce products as requiring age verification.
- Category and tag rules – Protect products, posts, pages, and custom post types by taxonomy.
- Manual content locking – Add an AgeOnce metabox to lock individual posts or pages regardless of taxonomy.
- Multiple age thresholds – Configure 16+, 18+, and 21+ rules from the same settings screen.
- Order and customer verification metadata – Save verification status, transaction ID, and verification time on WooCommerce orders; when signup gating is on, also save verification meta on the new customer.
- Configurable local pass – You set how long a visitor stays verified, separately for restricted content and for checkout and signup. The default is 24 hours. Guests are always asked again after 24 hours at most; logged-in accounts can keep a longer pass (up to 7 days for content, 30 days for checkout). Logout ends the pass immediately. The account still remembers the age that was passed, so 18+ does not unlock a 21+ rule. When the pass ends they click Verify Age again (AgeOnce SSO if they already have an AgeOnce account). Administrators can reset a customer’s verification from the user profile.
- Secure OAuth flow – Uses a one-time server-side state and server-to-server token exchange with AgeOnce.
- Content protection without WooCommerce – Gate posts, pages, and custom post types even if WooCommerce is not active.
Requirements
- WordPress 5.0 or higher
- WooCommerce 5.0 or higher (for checkout and customer signup protection)
- AgeOnce account with OAuth credentials (Client ID and Client Secret)
Getting Started
- Install and activate the plugin
- Open the AgeOnce WordPress setup guide (video + free plan)
- Create an account at AgeOnce and start with the free plan or choose a paid plan
- Go to AgeOnce Settings in the admin menu
- Copy the Redirect URL from WordPress into your AgeOnce dashboard
- Enter your Client ID and Client Secret in WordPress
- Click Test connection to confirm the OAuth setup
- Configure rules for WooCommerce products, categories, tags, posts, pages, or custom post types
- Optionally enable the Site entrance gate for whole-site protection, and adjust Appearance if you want branded gates
- Optionally enable WooCommerce customer signup if you want age verification before store account creation
- Save changes and run one entrance, checkout, signup, or restricted content test
Docs: WordPress plugin documentation. Plans: AgeOnce pricing. Product page: wordpress-age-verification.
Privacy
This plugin sends data to the AgeOnce service (app.ageonce.com, api.ageonce.com) only when a user explicitly starts age verification, such as clicking “Verify Age” at checkout, on the My Account registration form, or on restricted content. No tracking or data collection occurs without that user action.
The plugin does not send WordPress account passwords to AgeOnce. It may store a verification flag in the WooCommerce session or a cookie (24 hours at most), and it may store verification metadata on WooCommerce orders and on WordPress users (logged-in verification, and new customer accounts when signup verification is enabled). A logged-in pass lasts for the duration you choose in the settings, and also ends on logout; stored user meta keeps the age threshold that was passed and when each threshold was verified. See the AgeOnce service for privacy and terms.
External services
This plugin relies on third-party services operated by AgeOnce (the verification provider). They are required for OAuth login and token exchange so the site can confirm age verification.
-
AgeOnce web app (app.ageonce.com) — Used for the user-facing OAuth authorization screen when someone clicks “Verify Age”. The browser is redirected here with your site’s OAuth client ID, redirect URI, a state value, and required minimum age. The user completes verification on AgeOnce; no WordPress account password is sent to AgeOnce.
-
AgeOnce API (api.ageonce.com) — Used when the user returns to your site with an authorization code. The plugin sends a server-to-server request to exchange that code for an access token: it transmits the authorization code, redirect URI, OAuth state, and HTTP Basic authentication using your Client ID and Client Secret (stored in WordPress options). On success, the plugin may store a verification flag in the WooCommerce session or a cookie and optional transaction metadata for orders. This happens only during that callback after the user completes the flow.
-
Terms and privacy (AgeOnce) — Terms of service, Privacy policy.
Installation
- Install the plugin from WordPress.org or upload the
age-verification-with-ageoncefolder to/wp-content/plugins/ - Activate the plugin through the “Plugins” menu in WordPress
- Go to AgeOnce in the admin menu
- Create or open your AgeOnce account and add the WordPress Redirect URL to your AgeOnce OAuth settings
- Enter your AgeOnce Client ID and Client Secret in WordPress
- Configure content rules for WooCommerce products, categories, tags, posts, pages, or custom post types
- Enable AgeOnce verification and save changes
FAQ
Where do I find the full install guide and setup video?
On the AgeOnce WordPress age verification page: install steps, OAuth, content rules, free plan, and the 90-second WooCommerce walkthrough.
Does WooCommerce include an official built-in age gate?
No. WooCommerce does not ship a native age-requirement feature. Store owners must add their own checkout or content checks for restricted products. This plugin is one way to do that with privacy-first verification and order audit fields.
Is this just an age popup?
No. AgeOnce is designed for stores that need more than a basic self-declaration popup. The plugin starts a secure AgeOnce verification flow, returns the visitor to your site, and can store verification status for checkout and order records.
Do I need an AgeOnce account?
Yes. You need an AgeOnce account to obtain the Client ID and Client Secret used by the secure verification flow.
Can I use AgeOnce for free?
Yes. The free plan includes 100 verifications per month with no credit card. Install the plugin, connect your site, and test real checkout or content gating before upgrading. Details: WordPress age verification.
Can I protect only selected WooCommerce products?
Yes. You can require age verification for individual products, selected product categories, selected product tags, or other configured taxonomy rules.
Does AgeOnce block checkout automatically?
Yes. If the cart contains a restricted product and the customer is not verified, the plugin shows an age verification prompt and prevents checkout until verification is complete.
Does it hide WooCommerce product pages?
No. Product rules require Verify Age at checkout. Product descriptions stay visible. If the product page itself should be blocked, enable Also hide product descriptions until verified under Content Rules → Products.
Can I require age verification before customers create a store account?
Yes. In AgeOnce Settings, open WooCommerce customer signup and enable signup verification (off by default). Guests must complete AgeOnce verification on the My Account registration form before they can create a store account. You can choose a minimum age of 16+, 18+, or 21+.
Can I lock the whole site until visitors verify their age?
Yes. Open Entrance gate and enable Gate the whole site at the entrance. Unverified visitors see a plain AgeOnce entrance screen instead of your pages, menus, or theme chrome. Choose pages that stay public (for example Terms, Privacy, 2257, Contact), configure links on the entrance screen, and optionally let logged-in editors preview the site. Search-engine bot bypass is off by default.
Does the entrance gate work with page caching or Cloudflare?
Yes, with the right cache rules. The plugin already avoids caching the AgeOnce OAuth callback (admin-post.php) and sends no-cache headers on the entrance screen. If your CDN uses “Cache Everything”, add a rule that bypasses cache when the request includes the ageonce_verified cookie (and usually WooCommerce cart/session cookies). Also bypass or never cache cart, checkout, My Account, and admin-post.php. On the host, use a page cache that varies by cookie, or exclude HTML for unverified visitors. Full guide: Caching and CDNs.
Can I brand the age gates?
Yes. Under Appearance, set a logo, colours for the full-page entrance and for inline banners, optional heading/message text, and custom CSS. For full markup control, copy a template from the plugin templates/ folder into yourtheme/ageonce/.
Can I run my own code after a successful verification?
Yes, from plugin version 1.0.9. The ageonce_verification_completed action passes the WordPress user ID (0 if the visitor is not logged in), transaction ID, minimum age, and whether the check happened at checkout, signup, or on content. Use it for a custom role. Do not use it to unlock paid memberships; grant those after WooCommerce payment.
Does it save verification proof on orders?
Yes. When checkout is completed after verification, the plugin can save the AgeOnce verification status, transaction ID, and timestamp on the WooCommerce order.
Does it work without WooCommerce?
The plugin loads without WooCommerce, but checkout and customer signup protection require WooCommerce. Content protection (posts, pages) works independently.
Can I restrict content by category?
Yes. In Content Rules, expand a post type (e.g., Posts) and select categories/tags that require verification for each age group (16+, 18+, 21+).
What data is sent to AgeOnce?
When a visitor clicks “Verify Age”, the browser is redirected to AgeOnce with your OAuth client ID, redirect URI, state value, and required minimum age. After verification, the plugin exchanges the returned authorization code with AgeOnce through a server-to-server API request.
How long does a verification last?
You choose it under Settings, Verification duration, separately for restricted content and for checkout (store signup counts as checkout). The default is 24 hours for both. Restricted content can be set to the browser session (24 hours at most), 1 hour, 24 hours, or 7 days. Checkout and store signup can be set to 1 hour, 24 hours, 7 days, or 30 days. The time counts from the moment of verification.
Visitors who are not logged in are always asked again after 24 hours at most, because their pass is kept in a cookie or session. A longer duration only applies to logged-in WordPress accounts. Logout ends the local pass immediately (cookies, session, and the account’s pass times). After that they click Verify Age again. AgeOnce can complete that return visit with SSO when the customer already has an AgeOnce account. The plugin still remembers whether the account previously passed 18+ or 21+, so a lower age does not satisfy a higher rule.
You are responsible for choosing a duration that meets the requirements that apply to your business. AgeOnce does not provide legal advice.
Can I reset a customer’s verification?
Yes. Open the customer’s user profile in WordPress and tick “Reset this account’s age verification”, then save. The next restricted page or checkout asks that person to verify again on every device. Past orders keep their own verification records.
Does this replace legal advice?
No. AgeOnce helps enforce age verification rules on your WordPress or WooCommerce site, but requirements vary by country, state, product type, and business model. Review your local compliance requirements before selling age-restricted products.
Screenshots







Changelog
1.0.16
- New: Site entrance gate. Require age verification before any visitor can browse the site. Unverified visitors see a plain entrance screen instead of your pages, menus, or previews — built for adult and other strictly age-restricted sites.
- New: Allowed pages, entrance-screen links, optional editor preview, and optional search-engine bot bypass (SEO). The gate stays off automatically when API credentials are missing.
- New: Gate appearance — logo, separate colour sets for entrance and inline banners, optional heading/message, custom CSS, and theme template overrides under yourtheme/ageonce/.
- New: “Secured with AgeOnce” trust mark on inline banners (content, checkout, signup).
- Docs: page-cache and Cloudflare guidance for the entrance gate (bypass cache when the ageonce_verified cookie is present).
1.0.15
- New: Verification duration setting. Choose how long a visitor stays verified, separately for restricted content (browser session, 1 hour, 24 hours, 7 days) and for checkout and store signup (1 hour, 24 hours, 7 days, 30 days). The default stays 24 hours.
- Guests are still limited to 24 hours; a longer pass only applies to logged-in accounts. Logout ends any pass.
- New: Administrators can reset a customer’s age verification from the WordPress user profile.
- Orders now store the transaction ID and time of the check that allowed the purchase.
- Fix: Stored verification times are read in the site timezone, so a pass no longer shifts by the timezone offset on WordPress 5.3 and later.
1.0.14
- Fix: OAuth return no longer fails when the server-side state key is lowercased (LiteSpeed/Redis object cache). New states are HMAC-signed so the callback does not depend on the transient.
1.0.13
- Fix: Verify Age now starts through a cache-safe local URL and stores OAuth state on the server. Cached checkout pages and lost guest cookies can no longer fail the return from AgeOnce with a CSRF/session error.
1.0.12
- WooCommerce product pages no longer replace the description with an age gate. Product rules still require Verify Age at checkout. Optional setting: Also hide product descriptions until verified.
1.0.11
- WooCommerce Checkout Block: show the age gate above Place order, keep the button locked until verification, and reject unverified Store API checkout requests.
- Logged-in verification now expires after 24 hours, same as the guest cookie, on checkout, signup, and restricted content. Logout clears the local pass timestamp. User meta still stores the age that was passed so 18+ does not satisfy 21+.
1.0.10
- Return AgeOnce visitors to admin-post.php instead of the homepage, so a full-page cache cannot skip the code exchange. Visitors who already verified are not served that cached page. The previous homepage callback still completes links that were already opened.
1.0.9
- Add the
ageonce_verification_completedaction after a successful verification, including the WordPress user ID when the visitor is logged in. - Store verification on the logged-in WordPress user so a later checkout, signup, or content view for the same age does not require another check.
- Remember the age threshold that was passed, so an 18+ verification does not satisfy a 21+ rule.
1.0.8
- Optional WooCommerce customer signup age gate (disabled by default): block store account creation on My Account until AgeOnce verification, with a configurable minimum age (16+/18+/21+).
- Fix: keep age verification for guest visitors after OAuth return (always set verification cookie, start WooCommerce customer session when needed, and check session or cookie everywhere).
- Readme: document checkout, optional signup gate, guest verification, and related FAQ.
1.0.7
- Readme: primary CTA to AgeOnce.com WordPress landing (setup video + free plan); clarify WooCommerce has no native age gate; FAQ for install guide; screenshots stay in the Screenshots section only. No code changes.
1.0.6
- Readme: shorten short description to WordPress.org 150-character limit; add setup demo YouTube video and screenshots near the top of the Description section. No code changes.
1.0.5
- Readme: reduce Tags to 5 (WordPress.org limit). Same description as 1.0.4.
1.0.4
- Readme: clearer WooCommerce and privacy-first summary, free-tier hook (100 verifications/month, no card), expanded plugin tags, and added compliance context (UK Online Safety Act, US state laws, EU DSA, FDA PACT). No code changes.
1.0.3
- Category rules now match descendant terms (e.g. a parent category in Content Rules applies to products assigned only to a child category, including checkout).
1.0.2
- Improved the first-run admin experience with a setup checklist, connection testing, automatic credential saving after a successful test, and clearer toast notifications.
- Redesigned Content Rules with a quick-start guide, recommended versus advanced taxonomy groups, selected-item counters, and clearer control explanations.
- Updated WordPress.org screenshots and plugin copy to better explain setup, free plans, documentation, and WooCommerce/content restriction flows.
1.0.1
- WordPress.org review: document external services in readme; sanitize nested content rules; align text domain with plugin slug; validate OAuth state (nonce) and redirect URL on callback; harden metabox saves with capability checks.
1.0.0
- Initial release for WordPress.org
- WooCommerce checkout protection
- Content rules by post type and taxonomy
- Manual locking via metabox
- Product-level age verification
