Can my content appear in AI summaries in Google Discover?

Your content can appear in generative AI features in Google Discover without you doing anything. Google's Search Console help documentation describes inclusion as "the default control for all properties." No toggle needs flipping and no form needs filling in.

The control that matters works the other way. Search Console's AI features control lets a property owner opt out. When they do, the property is excluded from the generative AI surfaces the control covers, and Discover is one of them.

So the real question for most teams isn't "how do I get in?" It's "has anyone, on purpose or by inheritance, taken us out?" If you want the full walkthrough of the control itself, read our guide to Google's AI features control in Search Console.

As of October 2026, Google lists three surfaces under the control:

• AI Overviews
• AI Mode
• Generative AI features in Google Discover

Google adds that it expects to update this list over time. Treat the setting as a switch for Google's generative display surfaces in general, not as a Discover-only switch. A choice you make today may apply to surfaces that don't exist yet.

Three boundaries are worth knowing:

• It is not a training control. Training and Gemini grounding are governed separately by Google-Extended, a robots.txt token that Google says does not affect inclusion in Google Search.
• It is not a ranking signal. Google states the control isn't used as a ranking or inclusion signal for other parts of Search. Our page on whether opting out hurts your rankings covers this in more detail.
• It does not stop all use. Opting out of display does not stop Google using content to power Search as a whole, for example to understand the language of queries. See what Google can still do with your content after opting out.

The control has three properties that make silent exclusion possible.

Inheritance

For child properties, the default is "Inherit control from parent." If someone opts out a domain property, every child property that inherits follows. A marketing team managing a subfolder property may never see the decision that removed it.

Invisibility

The setting lives inside Search Console. It is not in your HTML, your headers or your robots.txt. No crawler can detect it, and Google offers no API that reports it. A competitor, an agency or a visibility tool looking from outside cannot tell you whether you're opted out. Only someone with access to the property can.

Partial rollout

Google's documentation has described the control as rolling out to a subset of website owners. Some properties may have no visible toggle yet. That doesn't mean the property is excluded: inclusion remains the default where the toggle is absent.

The practical risk is multi-property setups. If your organisation has several Search Console properties, audit them together. Our playbook on auditing inherited AI controls across properties gives the steps.

The evidence is clear about the control. It is much thinner about Discover's AI summaries themselves.

What holds up:

• Inclusion is the default, and the opt-out is real.
• For AI Overviews and AI Mode, Google says a page must be indexed and eligible to be shown in Search with a snippet, and that there are "no additional technical requirements."
• Google says AI Overviews and AI Mode "may use different models and techniques," so behaviour on one Google AI surface tells you little about another.

What nobody has published:

• Google has not documented eligibility rules specific to Discover's generative AI features beyond the control.
• No study we've reviewed measures how often Discover AI summaries use a given site, or what makes one source more likely than another.
• Search Console's generative AI performance report covers AI Overviews and AI Mode impressions. The documentation we reviewed does not describe Discover AI reporting.

That means no one can honestly promise you a place in Discover AI summaries. What you control is whether you are blocked. Everything after that is Google's decision.

Work through these in order. Each one removes a possible block.

1. Open Search Console for every property you own. Find the AI features control and record its state for each one. Note which properties inherit and from where.
2. Confirm the decision was deliberate. If a property is opted out, find out who chose that and why. If nobody knows, it may have been inherited from a parent setting made for another reason.
3. Check index and snippet eligibility. For Google's AI surfaces in Search, a page needs to be indexed and eligible for a snippet. Look for stray noindex, nosnippet or max-snippet:0 directives, often inherited from a template.
4. Separate training from display. If you want to limit Gemini training but stay in Google's AI surfaces, handle that with Google-Extended, not the Search Console control.
5. Decide what you want kept out. If the goal is to exclude specific content rather than a whole property, page-level and section-level controls are more precise. See how to keep specific content out of AI answers.

If you're worried the same setting is affecting AI Overviews, read whether a Search Console setting could be hiding your site.