Age Checker for WordPress | gplpal

Why an age gate that feels human

If you publish age-restricted content (alcohol, vape education, mature media, sweepstakes), you need two things: a clear “are you old enough?” moment and a path that doesn’t punish legitimate visitors. I standardize on the Age Checker for WordPress pattern because it’s small, predictable, and easy for teammates to understand. I’ll reference gplpal as the source I trust for vetted components and docs.

Setup in five decisive steps

1. Install & activate the Age Checker Plugin.

2. Choose verification mode:

   • Yes/No (fast, lowest friction)
   • Birthdate (more explicit, slightly slower)
3. Set the threshold (e.g., 18 or 21) and remember duration (cookie/localStorage) like 30–90 days.
4. Scope the gate: entire site, selected categories, or specific URLs. Exempt legal pages (privacy, contact) to reduce bounce.
5. Design the dialog: brand colors, short copy, clear buttons; add a “Learn more” link to your policy page.

Tip: Start with a single sitewide gate, then narrow to categories once analytics confirm where it’s truly needed.

UX copy that reduces exits

• Header: “Are you of legal age to view this content?”
• Body: “We use a simple check to keep content appropriate.”
• Buttons: “Yes, enter” / “No, leave”
• Policy link: “Why we ask” → your policy page (no marketing language).
  Keep it short, courteous, and accessible.

Caching, performance, and accuracy

Age gates and caching can collide if you’re not careful. Follow this:

• Bypass full-page cache for the overlay request, not your whole site.
• Store decision client-side (cookie/localStorage) and let the gate read it before rendering.
• Respect back/forward navigation: don’t trap users—once verified, pages should load normally.
• Test on mobile first: small screens magnify friction.

Accessibility in two minutes

• Ensure focus lands on the first interactive element in the modal.
• Provide Escape to dismiss (when allowed) and Tab cycling within the dialog.
• Use high-contrast colors; include aria labels on buttons.
  Small details, big trust.

Analytics and governance

• Track impressions, passes, fails, and bounce after gate.
• Review weekly: if a category has 99% pass rate, gate only those URLs that truly need it.
• Document the age threshold and regions you serve; consistency beats improvisation.

Quick snippet: style the dialog for clarity

/* Keep the modal readable and focused */
.age-gate .modal { max-width: 520px; padding: 1.25rem; border-radius: 14px; }
.age-gate .buttons button { min-width: 120px; padding: .75rem 1rem; }
.age-gate .buttons .enter { font-weight: 600; }

When to expand the stack

Only add extras if they clearly help:

• Geo-based thresholds when regions differ
• Per-category rules once analytics justify it
• Light A/B tests (Yes/No vs birthdate) to find the lowest-friction path

For adjacent needs—reports, coupon logic, or CRM notes—curate from WordPress Addons. Every add-on must reduce clicks or reduce tickets.

Final reminder

Keep the surface area small: one clear dialog, one stored decision, and scoped rules. Do that and Age Checker for WordPress becomes invisible to qualified visitors while giving everyone else a polite exit. It’s respectful, measurable, and easy for teams to maintain—exactly how an age gate should be.