SPMEDIA AGE VERIFICATION
SPMedia Age Verification compatibility with REEID Translate
SPMedia Age Verification compatibility with REEID Translate is being evaluated from available plugin evidence. WooCommerce age-gate full-screen popup with a visitor “Are you {age}?“ Yes/No choice that blocks access to age-restricted content until verified No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for SPMedia Age Verification.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
SPMedia Age Verification is documented in the Security category with 6 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How SPMedia Age Verification compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- WooCommerce age-gate full-screen popup with a visitor “Are you {age}?“ Yes/No choice that blocks access to age-restricted content until verified
- Configurable minimum age threshold (default 18) and configurable deny behavior including a deny message and redirect URL after a short delay
- Session-based remembering on the free plan so verified visitors are not re-prompted within the same browser session
- Pro option for persistent consent remembering via a configurable-duration cookie (default 30 days)
- Pro option to bypass the age gate for search-engine crawlers (e.g., Googlebot and Bingbot) so pages can remain indexable
- Pro options to scope the age gate to specific WooCommerce categories and/or individual products rather than applying site-wide
CONTENT BOUNDARY
SPMedia Age Verification capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
SPMedia Age Verification and REEID Translate FAQ.
What does SPMedia Age Verification do according to the available plugin evidence?
SPMedia Age Verification has 6 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for SPMedia Age Verification?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for SPMedia Age Verification?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate SPMedia Age Verification in a multilingual WordPress workflow.
REEID documents SPMedia Age Verification functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.