If your business manages more than one Search Console property, the default answer is usually to let child properties inherit the parent Search generative AI control. Override a child property only when that URL set has a materially different risk, licensing, or monetization posture—and only after you document why the parent setting is wrong for that branch.
This decision is different from whether to include or exclude your site overall. The inclusion choice is covered in our guide on keeping or opting out of Google generative AI Search features. This article focuses on the inheritance model that now matters for every verified domain, subdomain, and URL-prefix property after Google rolled the control out worldwide.
Key takeaways
-
As of August 31, 2026, Google states that Search generative AI control is available to websites worldwide in Search Console under Settings > Search generative AI.
-
The control governs inclusion in AI Overviews, AI Mode, and generative AI features in Discover. Google says it is not used as a ranking or inclusion signal for other parts of Search.
-
Child properties inherit from the closest parent that stopped inheriting. If no parent manually stopped inheriting, they inherit the top-level domain property setting.
-
Default to inheritance for operational consistency. Override only when a Property Override Scorecard shows a durable, branch-specific reason.
-
Do not use inheritance changes as a substitute for Google-Extended, nosnippet controls, or noindex. Each tool solves a different problem.
What inheritance actually controls
According to Search Console Help, owners can choose one of three states for a property:
-
Include the site’s links and content in Search generative AI features (default for properties that are not inheriting a different choice).
-
Exclude the site’s links and content from those features, including being linked within them and helping ground AI responses there.
-
Inherit the control from the parent property. Google says this is the default when a property has a parent.
Google’s inheritance rules are hierarchical. A child property inherits from the closest parent that manually stopped inheriting. When no parent has done that, the child inherits the top-level domain property. For example, a URL-prefix property such as https://example.com/business/cats would inherit from example.com by default, unless a closer parent such as https://example.com/business/ or https://example.com/ was manually configured to stop inheriting.
That matters because many businesses accidentally “set policy” for dozens of child properties by changing only the domain property—or they create conflicting exceptions on blog, help, staging-adjacent, or regional prefixes without realizing parent owners receive override notifications.
When inheritance is the right default
Inheritance is usually the correct operating mode when:
-
The same brand, legal entity, and content licensing rules apply across the domain and its verified children.
-
You want one reversible policy change to propagate cleanly instead of hunting through subdomain and path properties.
-
Your Generative AI performance report—and classic Web performance—do not show a child property with a uniquely harmful or uniquely valuable pattern that requires a separate rule.
-
You have already decided the parent should remain included, which is the sensible default for most commercial sites seeking discovery in AI Overviews and AI Mode.
Google’s AI features documentation also reiterates that eligibility for supporting links still depends on ordinary Search requirements: the page must be indexed and eligible to appear with a snippet. Inheritance configuration does not replace crawlability, indexability, or content quality work. For page-level eligibility issues after Google expanded links in AI answers, start with the fixes in what to fix first after Google put more links in AI answers.
The Inheritance Decision Ladder
Use this five-level ladder before changing any child property. Complete each level before moving down.
-
L0 — Inventory properties. List every verified domain, subdomain, and URL-prefix property. Mark which ones are parents of others. Note owners and who can change Settings > Search generative AI.
-
L1 — Confirm the effective parent setting. Open the top-level domain property and each intermediate parent. Record whether each is set to include, exclude, or inherit. Identify the closest configured parent for every child.
-
L2 — Score override need. Run the Property Override Scorecard below for each child that feels “different.” If the score stays low, keep inheritance.
-
L3 — Configure the minimum override. Change only the child property that needs a different rule. Prefer the narrowest URL-prefix or subdomain property that covers the exception. Write the hypothesis, owner, and review date.
-
L4 — Monitor propagation and notifications. Google says exclusion generally takes a few days after a control change, with some content taking longer because of caching and propagation. Confirm parent owners see override notifications when a child stops inheriting, and re-check Generative AI impressions for both parent and child scopes.
Property Override Scorecard
Score each factor from 0 to 2. Total possible: 12. Higher scores favor a manual override on that child property.
|
Factor |
0 |
1 |
2 |
|
Policy divergence |
Same legal and brand rules as parent |
Soft preference differs; no hard constraint |
Contract, counsel, or partner license requires a different generative-AI appearance rule |
|
Content ownership |
First-party marketing content only |
Mixed first-party and lightly licensed material |
Third-party, UGC, or co-branded library with reuse restrictions |
|
Monetization mismatch |
Child supports the same conversion model as parent |
Child is mostly educational; conversion still brand-level |
Child’s business model is damaged by generative summaries in a way the parent is not |
|
Measurement evidence |
No child-specific generative AI impression pattern |
Weak or mixed child-level signal |
Clear, durable child-level pattern in Search Console that supports a different rule |
|
Operational ownership |
Same team owns parent and child |
Separate editors; shared SEO lead |
Separate business unit with authority to set its own Search AI appearance policy |
|
Reversibility plan |
No written review date |
Informal reminder to revisit |
Named owner, metric threshold, and calendar review before the override becomes permanent by inertia |
How to read the total
-
0–4: Keep inheritance. Fix content, measurement, or page eligibility instead of forking policy.
-
5–8: Stay inherited for now. Gather 28–45 days of child-scoped evidence, then rescore.
-
9–12: A narrow override can be justified. Configure the child, notify parent owners, and schedule the review.
Worked example: publisher brand with a help subdomain (hypothetical)
Consider a hypothetical B2B software company with three verified properties:
-
example.com (top-level domain) — product and marketing site, set to Include
-
blog.example.com — thought leadership, currently inheriting
-
help.example.com — documentation that includes partner-licensed screenshots and restricted API reference text
Marketing wants one global include policy. Legal flags that a partner agreement limits generative reuse of certain help articles. The team scores blog.example.com at 2 (no durable reason to fork) and help.example.com at 10: policy divergence 2, content ownership 2, monetization mismatch 1, measurement evidence 1, operational ownership 2, reversibility plan 2.
Decision: keep the domain and blog inheriting Include. Manually configure help.example.com to Exclude, document the partner clause, and set a 60-day review. Parent owners should expect the Search Console notification that a child overrode the parent setting. The team does not block Googlebot on help pages, does not apply sitewide nosnippet, and does not treat this as a Google-Extended decision—those are separate controls with different effects.
Common failure patterns
-
Changing every child “just in case.” Manual overrides multiply audit debt. Prefer inheritance until the scorecard clears the bar.
-
Assuming a URL-prefix change covers the whole brand. Google’s parent/child examples show that protocol, www, subdomain, and path boundaries matter. https://www.example.com/ is not the same parent tree as example.com or http://example.com/.
-
Using inheritance as a ranking tactic. Google states the Search generative AI control is not a ranking signal for other parts of Search. If classic rankings slipped, fix relevance and technical eligibility.
-
Confusing this control with Google-Extended. Search Console Help notes that the generative AI control does not affect AI training; Google points publishers to Google-Extended to limit certain Gemini training and grounding uses outside Search generative AI features. Google-Extended also does not impact inclusion or ranking in Google Search, according to Google’s crawler documentation.
-
Excluding a child and expecting the AI answer panel to go blank. Google is explicit that other sites can still appear—and may look similar to yours—if you exclude.
Limitations and exceptions
Inheritance management helps only after you know whether inclusion or exclusion is the right parent policy. If that strategic choice is still unresolved, finish the inclusion scorecard first. Page-level preview controls such as nosnippet can still limit how content appears even when a property is included; those are not substitutes for property inheritance decisions, and overly restrictive preview controls can affect eligibility for AI features.
Also remember Google’s broader AI optimization guidance: special AI text files such as llms.txt are not required for Google Search generative AI features, and Google Search ignores them for ranking and visibility. Do not spend override-planning energy on file formats that do not change this control.
What to do next
-
Inventory every Search Console property and map parent/child relationships.
-
Confirm the effective include/exclude setting on the top-level domain and each intermediate parent.
-
Score only the children that appear operationally different; keep low-scoring children on inheritance.
-
If you override, use the narrowest property, wait through Google’s multi-day propagation window, and review Generative AI impressions plus business outcomes before making the exception permanent.
If you need help turning Search Console property structure into a durable AI-search visibility plan—across Google AI features and the broader answer ecosystem—Oasbit’s generative engine optimization services are built for that measurement-first approach.
If you want a working session on your property map, inheritance defaults, and which child exceptions are actually justified, book a growth strategy session.
