Webkoding AgeWall – Age Verification and Age Gate
Age verification and age gate that withholds restricted content on the server — an unverified visitor never receives it.
Solid choice
Webkoding AgeWall is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 4 weeks ago, and scores 64/100 on our health check.
- Actively developed — last update 4 weeks ago
- Tested with the latest WordPress (7.1)
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Webkoding AgeWall stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| age gate | #29 |
| age restriction | #38 |
| age verification | #57 |
| compliance | >100 |
| restricted content | >100 |
About Webkoding AgeWall
From the official readme · v1.0.3Description
Webkoding AgeWall adds real, server-side age verification to WordPress. Unlike simple “click to confirm” overlays that only hide content with CSS or JavaScript, AgeWall withholds protected content on the server: an unverified visitor never receives the restricted markup in the HTTP response, so it cannot be revealed by disabling scripts or reading the page source.
Gate your whole site, or just the pages, posts and blocks that need it. Set the minimum age, choose how visitors prove it, and decide what happens when they have not — all from one settings screen.
Key features
- True server-side enforcement. Protected content, shortcodes and blocks are withheld before the response is sent. The gate requirement (minimum age and method) is signed and re-derived on the server, so it cannot be weakened by tampering with the request.
- Whole-site gate or per-content gates. Gate the entire site with an overlay or a dedicated page, or gate individual pieces of content with the
[agewall]shortcode and the AgeWall block. - Per-post and per-category restrictions. Mark any post, page, custom post type or term as age-restricted, with its own minimum age and method.
- Two verification methods.
- Confirmation (“I am over N”) — a lightweight self-declared check.
- Date of birth (DOB) — a self-declared date, validated on the server.
- Choose your enforcement. Withhold the content entirely (the default and the strictest), redirect to a gate page, or cover the page with an overlay when you need search engines to keep seeing it.
- Search-engine friendly. Optionally allow known search-engine bots to bypass the gate for SEO.
- Customizable gate appearance. Set the gate title, message and logo, and choose an overlay, modal or inline template.
- No accounts, no tracking, no third-party calls. AgeWall stores no personal data and contacts no external service.
- Translation ready. All strings use the
webkoding-agewalltext domain and alanguages/webkoding-agewall.pottemplate is included.
What the paid add-on adds
Everything above is the free plugin and none of it is stubbed, time-limited or waiting for
a key. If you need more than a self-declared age, there is a separate paid add-on,
AgeWall Pro, that installs beside this plugin through the hooks documented above:
- ID document upload with manual review, stored outside the web root
- Yoti and VerifyMyAge as verification providers
- Ordered, country-aware rules — a different minimum age per jurisdiction
- An audit log of every attempt, with a retention policy you set
- WooCommerce: the cart and the checkout guarded, not only the product page
A self-declared “I am over 18” satisfies nobody who is actually regulated. The free plugin
holds the line on the server, which is the hard part; what it cannot do is tell you who
passed, hold a Frenchman to a different age than an Australian, or show a regulator
anything. That is what the add-on is for.
Details and price: https://webkodingtheme.com/plugins/agewall-pro
Developers
AgeWall is built to be extended. Documented hooks let you add your own verification provider (agewall/register_providers), supply your own rule set (agewall/rules), resolve the visitor’s country (agewall/visitor_country), observe every verification attempt (agewall/verification_attempt), and add your own settings tabs and admin screens (agewall/settings_tabs, agewall/admin_menu).
Installation
- Upload the
webkoding-agewallfolder to the/wp-content/plugins/directory, or install the plugin through the WordPress Plugins screen. - Activate the plugin through the “Plugins” screen in WordPress.
- Go to AgeWall in the admin menu, set your minimum age, verification method and appearance.
- (Optional) Mark individual posts, pages or terms as age-restricted from the AgeWall box on their edit screen.
Frequently asked questions
Does AgeWall really hide content from unverified visitors, or is it just a visual overlay?
It genuinely withholds the content on the server. Restricted content is never placed in the HTTP response for an unverified visitor, so it cannot be exposed by disabling JavaScript, editing CSS, or viewing the page source. This depends on the rule’s action, and the difference is important: withhold and redirect are content-withholding — the protected page is never rendered or sent to an unverified visitor — and withhold is the default. Overlay is a soft/SEO mode: the page still renders and is sent in the response with the gate painted over it, so use it only when you want search engines and…
Which verification methods are included?
Confirmation (“I am over N”) and self-declared date of birth. Both are checked on the server, and a visitor verified by the stronger method also satisfies the weaker one.
What personal data does AgeWall store?
None. AgeWall stores no personal data about your visitors, creates no database tables, and makes no third-party requests. A visitor’s proof of age is held in a signed cookie that records only the scope, the minimum age and the method it was granted for — never a date of birth.
Can I enforce a different age for different countries?
No. Every visitor is held to the same rule, which you set once in Settings. The plugin does not geolocate visitors and does not vary the minimum age by country. Developers can hook agewall/rules and agewall/visitor_country to match on their own criteria.
Can I add my own verification method?
Yes. Implement Agewall\Providers\ProviderInterface and register it on the agewall/register_providers action. It will appear automatically everywhere a method can be chosen.
Is AgeWall translation ready?
Yes. Every user-facing string uses the webkoding-agewall text domain, and a languages/webkoding-agewall.pot template is bundled for translators.
Changelog
1.0.3
- The Methods list now says, at the end of the list, that document and database checks are a separate add-on — where an admin choosing verification methods is actually standing, rather than only in the card at the foot of the page.
- The add-on card at the foot of the settings screen no longer appears when the add-on is installed.
1.0.2
- Fixed: a WooCommerce product marked age restricted was still for sale. The gate covers
post content, which on a product page is the description and nothing else, so the price,
the quantity field and Add to cart were untouched and the order went through without
anyone being asked their age. The product is now taken out of sale until the visitor
verifies, and a request sent straight to the cart is refused as well. - Fixed: the short description of a restricted product showed the gate’s words with its
markup stripped, buttons fused into one line. It now shows a sentence. - Added: after activation the plugin says what is left to do instead of appearing to do
nothing, and one verification method is switched on so the Methods tab is not empty. - Added: links to the settings screen and to the paid add-on in the Plugins list.
1.0.1
- Renamed: the listing now says what the plugin does, not only what it is called. No functional change.
1.0.0
- Initial release.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Webkoding AgeWall alternatives
All age gate plugins →FAQ
Webkoding AgeWall: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Sep 30, 2026
Is Webkoding AgeWall free?
Yes. Webkoding AgeWall is free to download and use from the official WordPress.org plugin directory.
Is Webkoding AgeWall safe to use in 2026?
Webkoding AgeWall is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 4 weeks ago, and scores 64/100 on our health check.
How many websites use Webkoding AgeWall?
Webkoding AgeWall is active on <10 WordPress websites and has been downloaded 198 times since it launched in August 2026. It was downloaded 130 times in the last 30 days.
Does Webkoding AgeWall work with WordPress 7.1?
Yes. The developer has tested Webkoding AgeWall up to WordPress 7.1.2, the latest release. It requires WordPress 6.0 or newer.
What PHP version does Webkoding AgeWall need?
Webkoding AgeWall requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Webkoding AgeWall last updated?
The latest version, 1.0.3, was released on September 4, 2026 (4 weeks ago).
Who makes Webkoding AgeWall?
Webkoding AgeWall is developed and maintained by WebKoding.
What are the best alternatives to Webkoding AgeWall?
The most popular alternatives to Webkoding AgeWall are Age Gate (40K+ installs), Age Gate Lite (2K+ installs) and Easy Age Verify (1K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card