How isAccessibleForFree Paywall Schema Helps Google Handle Gated Documentation in Search and AI Answers
Published November 21, 2026 · Last reviewed November 21, 2026

High-intent B2B buyers frequently ask technical architecture questions directly in Google Gemini and AI Overviews before contacting sales. Companies selling complex software often place their best implementation guides, API references, and architectural benchmarks behind registration walls or subscription portals. When an engineering team shows the full documentation to search crawlers but gates it for visitors without paywall structured data, Google has a harder time telling that setup apart from cloaking, which violates its spam policies. If those pages are not indexed, searchers may get citations pointing to open-source alternatives or competitors with public guides instead.
The short answer
Google does not publish a rule that Gemini grounding drops gated pages that lack isAccessibleForFree markup, and it says no special schema.org structured data is needed to appear in AI Overviews or AI Mode. What Google does say is that paywall structured data helps it tell paywalled content apart from cloaking, and that a paywall or content gate is not considered cloaking if Google can see the full gated content, just like a person with access, and you follow its Flexible Sampling guidance. For gated documentation you want crawled and indexed, set isAccessibleForFree to false on the page and use hasPart to point at each gated section with a .class cssSelector. That keeps the setup in line with Google Search policies, and Grounding with Google Search finds its sources by running Google searches.
How Google Handles Gated Content Without Paywall Markup
Grounding with Google Search connects Gemini to real-time web content: the model generates one or more Google searches, processes the results, and returns an answer with citations to source URLs. Google does not document a separate paywall check inside grounding, so the practical question is whether your gated pages are crawled, indexed, and compliant with Google Search policies. When documentation is gated behind a lead capture modal or subscription paywall, a common setup delivers full HTML to Googlebot while client-side scripts blur or restrict the text for regular visitors.
Google's paywalled content structured data guide says the markup helps Google differentiate paywalled content from cloaking, which violates its spam policies. Its spam policies add that a paywall or content gate is not considered cloaking if Google can see the full content behind it, just like any person with access, and you follow its Flexible Sampling guidance. Google does not say what any grounding system does with a specific unmarked page, so treat the markup as policy hygiene, not a guaranteed citation.
| Document State | Structured Data Present | What Google Documents | Practical Result |
|---|---|---|---|
| Public Documentation | Article or TechArticle markup, or none | Eligible to be crawled and indexed like any public page | Can appear in Search and AI features, with no guarantee |
| Gated, full text shown to Googlebot, no paywall markup | Missing isAccessibleForFree |
Harder for Google to tell the gate apart from cloaking | Risk under Google's cloaking policy |
| Gated With Valid Schema | isAccessibleForFree: false + hasPart |
Markup helps Google differentiate paywalled content from cloaking | Can stay eligible for Search, with no guarantee of citation |
| Blocked in robots.txt or noindex | Not applicable | robots.txt stops crawling; noindex stops indexing | Content not used; a robots.txt-blocked URL can still be indexed without its content |
For more on how rendering affects what answer engine crawlers can read, see our analysis of client-side JavaScript rendering for answer engine crawlers.
Required JSON-LD Structure for Gated Documentation
For gated documentation you want crawled and indexed, Google's paywall markup uses schema.org/isAccessibleForFree with the schema.org/hasPart property. Together they tell Google which sections of the page are behind the gate.
Google supports this markup on CreativeWork or a more specific type such as Article, NewsArticle, Blog, HowTo, or WebPage, and TechArticle is a more specific type of Article in schema.org. Setting the root isAccessibleForFree property to false tells Google the page has paywalled or registration-gated content. hasPart then lists a WebPageElement for each gated section (as an array if there is more than one), each with isAccessibleForFree set to false and a cssSelector that uses a .class selector from the page markup.
{
"@context": "https://schema.org",
"@type": "TechArticle",
"headline": "Distributed Sharding Architecture and Failover Benchmarks",
"description": "Technical specifications and failover configurations for multi-region database clusters.",
"isAccessibleForFree": false,
"hasPart": [
{
"@type": "WebPageElement",
"isAccessibleForFree": false,
"cssSelector": ".gated-technical-body"
}
],
"author": {
"@type": "Organization",
"name": "Engineering Operations"
}
}
Google says to use only .class selectors for cssSelector and not to nest content sections. Each class must match the class actually used on the gated container. If the class name .gated-technical-body is misspelled or generated dynamically through CSS-in-JS hashing without updating the markup, the structured data no longer points at the gated section, so it cannot show Google where the paywall is.
Implementation Walkthrough: Configuring Paywalled Documentation
Fixing paywall metadata requires coordinated changes across the content management system, the front-end presentation layer, and the metadata generator. These five steps mark gated content the way Google's paywall guide describes.
- Segment the front-end template into explicit containers. Wrap introductory summaries, prerequisites, and table of contents in a container marked with a static class such as
entry-summary-public. Wrap detailed code snippets, benchmark results, and implementation guides in a separate container markedgated-spec-content. - Add the JSON-LD paywall markup to the page. Set the root
"isAccessibleForFree": false(a boolean, not a string) and point ahasPartWebPageElementwithisAccessibleForFreeset tofalseat.gated-spec-content. Google's examples list only the gated sections, so the public summary container does not need its own entry. - Configure indexing tags correctly. Do not use
noindexon pages you want in Search, and check thatnosnippetor a lowmax-snippetvalue is not blocking text you want shown. Google's robots meta tag documentation notes thatnoarchiveis no longer used by Google Search because the cached link feature no longer exists. - Keep gated sections separate. Google's guidelines say not to nest content sections, so do not put one gated container inside another. As shown in our guide on semantic HTML comparison tables in AI search, clean structural containers can also make tables and comparisons easier to extract.
- Validate the markup with the Google Rich Results Test, as Google's guide recommends, and fix any critical errors. Then use the URL Inspection tool in Search Console to see how Google crawls and renders the page, and confirm that the class in each
cssSelectoris on the gated container.
# Test server response to confirm JSON-LD schema renders in initial HTML
curl -s -A "Googlebot" https://docs.example.com/architecture/multi-region-failover | grep -A 20 "isAccessibleForFree"
What this means if you're running spend
Paid traffic teams and growth operators often treat technical documentation as bottom-funnel collateral rather than an acquisition asset. When performance marketing campaigns drive target accounts to gated whitepapers or technical portals, the ad spend covers direct clicks. However, buying committees may check vendor claims by asking Google Gemini, ChatGPT, and Perplexity technical questions before talking to a sales rep.
If the benchmarks and technical details in your gated resources are not crawled or indexed, answer engines can only build responses from sources they can reach, which may be competitors with public documentation. An account executive on your sales floor could then spend weeks trying to convince a prospect that your infrastructure supports active-active replication while an AI answer cites only a competitor's docs.
Correct paywall markup lets you keep the lead gate for human visitors while giving Google a clear, policy-compliant view of the gated content. It does not guarantee that any AI answer will cite your pages, but it removes a cloaking risk that could keep them out of Search.
To align performance ad spend with total market authority, marketing leaders should audit how technical assets are represented across both paid landing pages and organic answer engines. We handle this structural alignment through our growth marketing operations.
FAQ
Does adding isAccessibleForFree schema require removing registration forms for human visitors?
No. Google's spam policies say a paywall or content gate is not considered cloaking if Google can see the full content behind it, just like any person with access, and you follow its Flexible Sampling guidance. The paywall markup helps Google tell that setup apart from cloaking. It does not guarantee rankings or citations.
Can a page declare multiple gated sections under hasPart?
Yes. Google's guide says to list multiple paywalled sections as an array of WebPageElement entries under hasPart, each with its own .class selector. Google's examples mark only the gated sections, so introductory content outside those classes does not need its own entry.
What happens if the cssSelector in JSON-LD does not match the page HTML?
Then the markup no longer identifies the gated section, so it cannot help Google tell your gate apart from cloaking. Google does not document a specific penalty or grounding outcome for a mismatched selector, but the fix is simple: use a stable .class name on the gated container and keep the markup in sync with it.
Is isAccessibleForFree schema supported on single-page applications rendering client-side?
Yes. Google says it can understand and process structured data that is in the DOM when it renders the page, including JSON-LD added with JavaScript. Google also notes that rendering is not guaranteed, so including the JSON-LD in the server-rendered HTML is the safer choice.
How much of this applies to your operation?
The impact of missing structured data depends on how much revenue rides on technical validation, the depth of your documentation gate, and how prospects research your platform. If answer engines misquote your technical specifications or fail to cite your implementation docs, the friction shows up downstream as longer sales cycles and disputed product capabilities. If you want to review your technical search visibility, paid traffic funnels, and underlying lead operations, apply for a conversation at /apply.
Last reviewed November 21, 2026. Sources linked inline.
Speak directly with Jason, our Managing Director. No sales reps.
