AgeOnce Docs
WordPress

Settings

AgeOnce WordPress plugin configuration

Plugin Settings

After installing the plugin, go to AgeOnce in the WordPress admin sidebar to configure.

If you are evaluating AgeOnce, start with the free plan and use a staging site or a test product category first.

API Credentials

Status

Enable or disable the plugin.

  • Enabled — Age verification is active
  • Disabled — Plugin does not intercept content or checkout

Client ID

Unique identifier of your client in AgeOnce.

Client Secret

Secret key for API request authentication.

Never publish the Client Secret! It must remain confidential.

Redirect URI

The plugin automatically uses this callback URL (format ?ageonce_callback=1):

https://yoursite.com/?ageonce_callback=1

The exact URL for your site is shown in the plugin settings — copy it and add to allowed Redirect URIs in your Dashboard Settings.

For WordPress, always copy the exact URL shown by the plugin. This avoids problems with www vs non-www, HTTPS, subdirectories, or staging domains.

Content Rules

Content restriction is configured per post type (Pages, Posts, Products, etc.).

For each post type you can:

  1. Enable/disable — Turn age verification on or off for that content type
  2. Allow Manual Locking via Metabox — When enabled, you can protect individual pages, posts, or products. An AgeOnce Protection metabox will appear in the sidebar on the edit screen for each post/page/product. There you can enable protection separately for that specific item, regardless of its category.
  3. Active Age Groups — Choose which age thresholds apply: 16+, 18+, 21+
  4. Per-age rules — For each enabled age group (e.g. 18+ Rules), select taxonomy terms (Categories, Product Categories, etc.). Content in those terms will require verification for that age

Example

  • Enable Products
  • Check 18+ as active age group
  • In 18+ Rules, select "Alcohol" in Product Categories
  • All products in the Alcohol category will require 18+ verification

After Configuration

  1. Save changes
  2. Add the Redirect URI to Dashboard Settings
  3. Test by opening a restricted page or adding an age-restricted product to cart and going to checkout

On this page