Picture this: a customer hits checkout with something age-restricted in the cart. Your theme asks for a birth year, they tap through, the order completes, and everyone in the room—including them—knows that was theatre, not proof. That gap is where chargebacks, brand damage, and awkward conversations with your counsel start. AgeOnce Verification is now on WordPress.org so you can close it properly: verify through AgeOnce before money changes hands on WooCommerce, gate posts and pages with taxonomy rules when the risk is access, not payment, and keep the same privacy-first OAuth model you already expect from the AgeOnce dashboard.

That is the shift people are searching for in 2026—not another “age gate” skin, but age assurance tied to policy: verifiable checks versus a cosmetic field, WooCommerce as the moment of truth for restricted goods, and content rules when you need to show you took real steps on sensitive categories. Search and AI overviews reward pages that say who something is for and what to do next; the regulatory backdrop everyone cites—the EU Digital Services Act, the UK Online Safety Act and Ofcom’s bar for “highly effective” age assurance, and the European Commission’s age-verification blueprint toward privacy-preserving proofs of age—is the same pressure shaping what buyers type into Google before they ever reach your site.

So what does the plugin actually do in plain language? It connects your WordPress site to AgeOnce using OAuth-style flows your team already knows from modern SaaS. For WooCommerce, you can require verification before an order is placed when the cart contains age-restricted products. For content, you can gate posts, pages, and custom post types using taxonomy rules (think categories and tags) with different minimum ages where your policy demands it, plus manual overrides when a single piece of content needs a stricter line than the rest of the site.

That combination is deliberate. Merchants rarely need “age verification in the abstract.” They need a gate at the moment money changes hands, and a lighter touch on editorial pages where the legal story is about access, not payment. Publishers and membership businesses need the opposite emphasis sometimes: protect the archive, keep the funnel human, and avoid turning every blog post into a paperwork wall. The plugin is written for both realities.

Who should reach for it first? If you run a WooCommerce store where age is part of the contract, wine, supplements, curated adult markets where permitted, collectibles, anything where “I clicked buy” is not enough for your risk team, you already know why you are reading this. Publishers, memberships, and communities that must show they took real steps on sensitive categories belong in the same bucket. So do agencies rolling one playbook across many client sites, course and LMS operators selling access to mature-audience material, events and ticketing sites with tiered access, and D2C brands expanding into the UK or EU and discovering that a checkbox does not match anyone’s definition of “highly effective” age assurance anymore.

The AgeOnce product family is bigger than WordPress: the same verification engine powers the REST API and SDKs for custom stacks, mobile apps, and headless storefronts. If your storefront is not WordPress, you are not left out—you integrate where your code lives, and you still get the same outcome-and-audit model. If WordPress *is* your stack, the plugin is the fastest way to align your storefront and your editorial site with how regulators and partners now talk about age checks in 2026.

None of this replaces legal advice. Jurisdictions differ, product categories differ, and your counsel still owns the final word on what “reasonable steps” means for you. What the plugin does replace is the fantasy that a static age checkbox still counts as innovation in 2026. Users have seen breaches in the headlines. Regulators have seen the same screenshots you have. A serious age assurance flow, one that separates verification from day-to-day storage of sensitive artefacts, is becoming table stakes for credible operators.

If you want to try it, the path is intentionally boring in a good way: install from the directory, paste credentials from your AgeOnce dashboard, configure rules, test on staging, ship. We keep the interesting cryptography and risk scoring on our side so your WordPress team can stay focused on merchandising, editorial calendars, and the hundred other fires that already own their calendar.

We are proud this is finally a one-click story for the world’s most popular CMS. If WordPress powers your revenue, your community, or your reputation, welcome aboard. We built this for you.