Paywall and Login Detection

Paywall and login detection checks whether your page is openly reachable or sits behind a barrier no AI crawler can get past. friendly4AI reads the page HTML for login forms, CAPTCHA widgets, and paywall phrases, then scores the page pass (100), partial (50), or fail (0) based on how many access signals turn up. The higher the score, the more open the page. It does not reward restriction.

What signals does this parameter check?

The scan looks for two classes of access signal in the page HTML.

Strong signals (each adds one strong count):

• A login form containing a password field.
• A CAPTCHA widget — reCAPTCHA, hCaptcha, Cloudflare Turnstile, or a "verify you are human" challenge.
• A hard paywall phrase: paywall, subscribe to continue, premium content, members-only, sign in to continue, log in to continue, start your subscription, or already a subscriber.

Weak signals:

• Softer markers such as member access, plus an authentication entry point paired with registration-wall language.

Why does it matter for AI-readiness?

AI crawlers can't log in, and they can't solve challenges. Anthropic's system card says so directly: the Claude crawler cannot reach password-protected pages, sign-in pages, or CAPTCHA-protected content. ChatGPT, Perplexity, and Gemini crawlers hit the same wall. So if your main content lives behind a login, a hard paywall, or a CAPTCHA, no AI system will ever read it. Your most important pages go dark to every engine, no matter how well the rest of the page is built. This gate works alongside the other crawlability checks: HTTP reachability, robots.txt accessibility, and AI crawler access control.

How is the score calculated?

Under the v4.5 methodology, this Crawlability parameter scores in three tiers by counting access signals. A login form, a CAPTCHA, and every matched strong paywall phrase each add one strong signal.

| Score | Condition | | --- | --- | | Pass (100) | No strong signal and fewer than two weak signals. | | Partial (50) | Exactly one strong signal, OR two or more weak signals. | | Fail (0) | Two or more strong signals. |

Cookie-consent markers (say "cookie policy" or "accept all cookies") suppress one weak count. A cookie banner doesn't block AI crawlers, so the scan won't mistake one for a content wall.

How do I fix paywall and login barriers?

• Keep your primary content publicly readable. Your value proposition, key facts, and pricing should render without a login or a payment.
• Running a paywall? Use a metered model so the first view stays open, or push key landing pages above the wall.
• Pull CAPTCHA gates off public content pages. Save the challenges for suspicious traffic, not every visitor.
• Drop hard-gating phrases like "subscribe to continue", "members-only", or "sign in to continue" from any page you want AI systems to read.
• Cookie-consent banners on their own are fine. They don't block AI crawlers, and the scan discounts them. Re-scan after your changes to confirm the barriers are gone.