SEO and crawlers
Age gates have a reputation for hurting SEO. Optan is designed so yours doesn’t.
Why the gate is SEO-safe by construction
Section titled “Why the gate is SEO-safe by construction”- Your content stays in the page. The gate is an overlay on top of the normal page — the product content is still fully present in the HTML that search engines fetch. Nothing is hidden server-side, swapped, or cloaked.
- No redirect on arrival. Visitors land on the URL they requested; the gate appears over it. Crawlers following links reach real pages with real content and real status codes.
- Targeting shrinks the surface. With collection or tag targeting (Pro), unrestricted pages — usually most of your store — never show the gate at all.
- Featherweight embed. ~6 KB of JavaScript, ~2 KB of CSS, zero external requests, no fonts, no trackers. The impact on Core Web Vitals is negligible; there is no layout shift because the overlay paints above the page rather than pushing content.
Crawler bypass (Pro)
Section titled “Crawler bypass (Pro)”Let search engines through without the gate hides the overlay entirely for known search engine and preview bots — Googlebot, Bingbot, DuckDuckBot, Baiduspider, YandexBot, link-preview fetchers and similar crawlers, detected by their declared user agent.
With the bypass on, crawlers see the page exactly as an age-verified visitor would — no overlay in a rendered screenshot, no gate text mixed into snippets.
With the bypass off, crawlers still index your content (it’s in the HTML), but rendered snapshots may show the overlay, and snippet extraction can occasionally pick up gate text. If SEO matters to your store, turn the bypass on.
Practical checklist for restricted stores
Section titled “Practical checklist for restricted stores”- Use targeting so only restricted pages carry the gate.
- Enable the crawler bypass.
- Keep the remember duration at a comfortable value (default 30 days) so returning human visitors aren’t re-prompted on every visit — bounce rate stays healthy.