How does isAccessibleForFree=false affect Apple's AI context use?

Definition: isAccessibleForFree=false is a page-level Schema.org signal for restricted access. Apple's About Applebot documentation says that a marked page remains eligible for Apple search results, while Applebot will not use its content as additional context when AI models generate output for Apple products and services.

Key facts

• Apple's About Applebot documentation supports isAccessibleForFree for pages behind a paywall, metered access, or a subscription.
• The Apple signal belongs in page-level JSON-LD, and false marks the page as restricted.
• Apple says a page marked isAccessibleForFree: false can appear in search results, but its content is excluded from additional AI context for output displayed in Apple products and services.
• Apple documents this as a page-level signal. It says section-level markup using hasPart is unsupported.
• Schema.org defines isAccessibleForFree as a flag for free access and lists Boolean as its value type.
• Apple's Applebot-Extended control addresses use of crawled data for training foundation models, so it is a separate setting from the page-level paywall signal.

What does false change for Apple?

Apple's About Applebot documentation describes two relevant uses of crawled data. Applebot supports search features in products such as Spotlight, Siri, and Safari. It also says crawled data may provide additional context and current content when AI models generate output for Apple products and services.

The paywall signal changes that second use for the marked page. Apple states that pages marked isAccessibleForFree: false remain eligible to appear in search results, while Applebot will not use that content as additional context for AI-generated output displayed in Apple products and services. The documented scope is the whole page, because Apple says the signal applies at page level.

How should the page-level markup look?

Apple says to add the property to page-level structured data in JSON-LD. Its example is:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "isAccessibleForFree": false
}
</script>

The Schema.org definition describes the property as a flag that signals free access and gives Boolean as the expected value type. In this use, false communicates that access to the page requires a paywall, metered access, or a subscription, as listed in Apple's documentation.

Can hasPart mark only one restricted section for Apple?

No. Apple's documentation says that the signal applies at page level and that section-level markup using hasPart is unsupported. A page with mixed free and restricted sections therefore has no Apple-documented section selector in this control.

Google documents a different implementation for its own paywalled-content guidance. Its paywalled content documentation uses hasPart with WebPageElement and a CSS class selector to identify restricted sections. It says multiple restricted sections use an array, and its guidance requires isAccessibleForFree to be false for the restricted article or section. That Google pattern should not be read as Apple support for hasPart.

How does this differ from Applebot-Extended?

Apple describes Applebot-Extended as a separate user agent that controls how Apple may use data crawled by Applebot. Apple's documentation says Applebot-Extended does not crawl webpages, and that pages disallowing it can still be included in search results. The page-level paywall property therefore addresses AI context use for the marked page, while Applebot-Extended is the documented control for opting out of training Apple's foundation models.

Related terms

• Applebot
• Applebot-Extended
• Does Applebot support hasPart for section-level paywall exclusions?
• Subscription content markup

FAQ

Does false remove the page from Apple search?

No. Apple's documentation says pages marked isAccessibleForFree: false are eligible to appear in search results.

Does false opt the page out of training Apple's foundation models?

No. Apple documents Applebot-Extended as the control for opting out of that training use. The page-level property addresses additional context supplied to AI models for output in Apple products and services.

Can a publisher use Google's hasPart pattern for Apple?

Apple says section-level markup using hasPart is unsupported. Google's documentation describes hasPart for Google's paywalled-content implementation.

Sources

1. Apple, "About Applebot", 4 September 2026
2. Schema.org, "isAccessibleForFree", undated
3. Google Search Central, "Subscription and Paywalled Content Markup", 8 September 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer