The short answer
Keep one public name for the group and one public name for each office, and use those same strings on the sign, the location page, and the Google Business Profile. Give every eligible office its own profile, and point that profile at the matching location page. On the site, describe the group once with Organization markup, and describe each office with Dentist markup that names the group through parentOrganization. Put sameAs only on profiles that actually belong to that entity. An llms.txt file is optional for other tools. Google's own guide says Google Search does not use it. Measure by location URL in Search Console and by profile in Business Profile performance. How to write a page that can be cited is a different job, covered in earning AI Overview citations.
This page is the group view: who the brand is, who each office is, and how those facts stay the same anywhere Google reads them. It is not a writing tutorial and not a single-office crawl checklist. Page-level citation habits are in earning citations in Google AI Overviews. Crawl, robots, and non-Google assistants are in optimizing a dental website for AI search. What belongs on an office URL is in location pages for a multi-office site. Access, chain verification, and the organic UTM pattern are in Business Profile governance.
Brand names and office names
Google's Business Profile guidelines say the profile name is the real-world name on the storefront, the website, and the stationery. Do not add a tagline, a store code, a phone number, a URL, or a location phrase such as a city the sign does not use. For a chain in one country, locations use that same name when they present themselves the same way, and the same primary category when they offer the same services. Two exceptions are documented: a consistent sub-brand, and a location that already uses a different name on the sign, the site, and stationery together.
That is an identity rule, not a slogan. A marketing team that prints "North Park" on the ads and "Oak Street" on the profile has created two entities for one door. Write the strings down before anyone edits a page.
Parent brand
Public name
Corporate site, letterhead, and the one page that describes the group.
Profile
Not a stand-in for office profiles. Offices the public can visit still get their own profiles.
Markup
Organization on the home page or that one about page. Name matches the site name.
Office using the brand name
Public name
The same name string on the sign, the location page, and stationery.
Profile
One profile for that door, website link set to that location page.
Markup
Dentist on the location page, with parentOrganization pointing at the group.
Office with its own public name
Public name
Only when the sign, the site, and stationery already use that different name the same way.
Profile
The profile uses that real-world name. Do not bolt a city onto the brand as a keyword.
Markup
Dentist uses the name patients see on that page, not a private internal code.
Unit inside one office
Public name
A department with its own hours or phone, at the same street address.
Profile
A separate practitioner or department profile only when Google's guidelines allow that unit its own page.
Markup
Nest it with department. Do not use department to fake a second street address.
| Who | Public name | Profile | Markup |
|---|---|---|---|
| Parent brand | Corporate site, letterhead, and the one page that describes the group. | Not a stand-in for office profiles. Offices the public can visit still get their own profiles. | Organization on the home page or that one about page. Name matches the site name. |
| Office using the brand name | The same name string on the sign, the location page, and stationery. | One profile for that door, website link set to that location page. | Dentist on the location page, with parentOrganization pointing at the group. |
| Office with its own public name | Only when the sign, the site, and stationery already use that different name the same way. | The profile uses that real-world name. Do not bolt a city onto the brand as a keyword. | Dentist uses the name patients see on that page, not a private internal code. |
| Unit inside one office | A department with its own hours or phone, at the same street address. | A separate practitioner or department profile only when Google's guidelines allow that unit its own page. | Nest it with department. Do not use department to fake a second street address. |
Two brands that share a door stay separate if they operate independently. Do not merge their names into one profile title. A practitioner who sees patients at a branded office can have a practitioner profile titled with that person's name, in addition to the organization's profile for the location. A solo practitioner at a branded organization may share one profile that shows the brand and the practitioner. This page does not add Person markup for clinicians. Name choices here follow Google's public representation rules. They are not legal advice about corporate structure. Ask your own counsel for that.
Where location pages fit
Google's AI features documentation says pages need to be indexed and eligible to show a snippet. There is no separate submission path for a multi-location brand. The architecture that makes an office eligible is ordinary: one indexable URL per office, with that office's name, address, and phone visible, matching the profile. Town URLs with no office of their own are a different problem, covered as doorway risk in the location page guide. Do not clone the corporate about page once per city and call that a location.
The same documentation says structured data should agree with the text on the page, and that Business Profile information should be kept up to date. Those two sentences are the whole "AI" requirement Google states for local facts. The writing habits that make a passage easy to cite, including a direct answer near the top of a service page, stay on the citation guide so this page does not repeat them.
Business Profile alignment
One profile per eligible location. Google's guidelines say not to create more than one page for the same location, in one account or across accounts. The phone should connect to that individual location, or the website should represent that location. A local number the business controls is preferred over a central switchboard. Do not use a number or a URL that redirects somewhere other than the actual business, including a social page.
- •Website field: the location page for that door, not the home page and not a sibling office.
- •Name field: the string from the name sheet, with no city stuffed in to "help" AI.
- •Closed or moved offices: update the profile and the page together so an old address does not keep circulating.
Who may edit those fields, how a chain of ten or more locations requests bulk verification, and how organic links carry a shared UTM pattern are already written up in profile governance for dental groups. Paid location assets that read this same profile data are covered in Google Ads budget allocation and call attribution.
Organization, Dentist, and sameAs
Google's Organization documentation says to add that markup on the home page or on one page that describes the organization, not on every URL. For a local business, use the most specific local-business subtype and include the organization fields you need. The name in the markup should match the site name. Local business documentation says to define each location as its own local business, with address and name, and it points the URL property at the fully qualified URL of that location. Google's examples of subtypes do not list a dental type. schema.org defines Dentist as a dentist and places it under LocalBusiness, which is why a dental office page can use Dentist as that more specific type.
- •parentOrganization. schema.org defines parentOrganization as the larger organization this one is a subOrganization of. On an office page, that pointer connects the Dentist entry to the group's Organization entry. Google's Organization rich-result properties do not list parentOrganization. Use it as a clear relationship, not as a promise of a special search feature.
- •department. department relates an organization to a department that is itself an organization, such as a unit with its own hours or phone. Google's local business page describes the same idea and suggests naming a department with the store name plus the department name unless that unit is branded on its own. A department is not a second street address and not a substitute for a location page.
- •sameAs. sameAs is a URL of a reference page that unambiguously indicates the item's identity. Google's Organization page describes it as another site with more information about that organization, such as a social profile, and allows more than one. Put the group's real profiles on the Organization entry. Put an office sameAs only when the URL is about that office. Copying the brand's Facebook URL onto every location says those doors are the same entity.
Do not add review or aggregate rating markup to these blocks. Markup that visitors cannot see on the page disagrees with both the local business guide and the AI features guide. The field-by-field office checklist, including hours and the page URL, stays in the location page guide so the two pages do not duplicate each other.
llms.txt is optional
Some groups publish a plain-text file, often at /llms.txt, that lists pages an outside assistant might fetch. Google's generative AI optimization guide is direct about this class of file: Google Search, including generative AI features on Google Search, does not use llms.txt or similar AI text files. You do not need one to appear in Google Search. Google notes it may still crawl many kinds of files, but Search does not use this one for ranking or for its AI features. Other products may read it.
If you publish one, list real URLs: the page about the group, and each location page, with the same names you use everywhere else. Do not stuff keywords or patient information into it. Do not tell an agency that the file is why Google showed an office. This site publishes its own llms.txt as that kind of convenience for agents. It is not a claim that Google reads it. The broader single-site notes on robots and assistants are in the AI search guide for a practice website.
Measurement by office
Two Google reports cover this, and neither one is a new-patient count.
- •Search Console, generative AI. The Generative AI performance report shows impressions of links in AI Overviews and AI Mode. You can group by page, country, device, and date. Group by page and look for location URLs. The report's dates use Pacific Time. Google's AI features page also says appearances in AI Overviews and AI Mode are included in the Performance report's Web search type. A page with no row may simply have no impressions yet.
- •Inclusion control. The Search generative AI control defaults to include, which allows links and grounding. Exclude stops impressions and traffic from AI Overviews, AI Mode, and Discover generative features. A group that turned exclude on should not expect those reports to fill in.
- •Business Profile performance. Performance data is available to owners and managers of verified profiles. It includes interactions, searches, views, direction requests, calls from the call button, website clicks, messages, and bookings when a booking provider is connected. For many profiles, Business Profile Manager can download a spreadsheet so offices can be compared. A call click is not proof of a booked visit.
Read the generative report by URL, then the profile sheet by office, then your own front-desk log for appointments. Keep patient names, phone numbers, and chart ids out of Search Console, the profile, and any export you hand to a vendor. How a single practice reads the generative report is also summarized in the citation guide. This page adds the group cut: one row per location URL, one row per profile, and a note when a door is missing from either.
Red flags
- •Office pages titled with the brand while the signs use a different name, or the reverse, with no written rule for which string is public.
- •One Business Profile for several doors, or a second profile created for the same door.
- •Every profile website link pointed at the home page.
- •The brand's social URL pasted into sameAs on every office.
- •department markup used instead of a location page for a real second address.
- •An llms.txt file described as the way Google finds the offices.
- •City names added to profile titles to chase "near me" queries the sign does not show.
Governance checklist
Tick these for the group you are reviewing. The ticks stay in this browser only. Nothing is sent to DDS Web Solutions.
Group AI search checklist
12 items
The planning page for brand models and reporting is DSO and multi-location marketing. Questions to ask a vendor about this work are in how to choose a DSO dental marketing company.
FAQ
Does a dental group need a special schema type to appear in AI Overviews?
No. Google's AI features documentation says there are no extra technical requirements beyond being indexed and eligible for a snippet, and no special markup is required for those features. Structured data still has a job: it should match the visible page and can support the rich results Google documents for businesses. parentOrganization is a schema.org relationship. It is not listed as an Organization rich-result property on Google's Organization page.
Should every location page repeat the parent Organization block?
Google says to put Organization markup on the home page or on one page that describes the organization, not on every page. Each location page should describe that office, using the most specific local-business type that fits, with the address and name of that door. Point parentOrganization at the group entry instead of pasting the whole corporate block onto every office.
Can one Business Profile represent the whole group?
Google's guidelines say not to create more than one profile for each location, and a place the public can visit is represented by that location's profile. A brand overview on the website does not replace those profiles. Chains in one country use the same name at each office unless the sign, the site, and stationery consistently show a different name.
Will an llms.txt file get our offices into AI Overviews?
Google's optimization guide says Google Search, including its generative AI features, does not use llms.txt or similar AI text files. You do not need one to appear in Google Search, including AI Overviews. You can still publish the file as a convenience for other systems. Do not treat it as a substitute for indexed location pages.
How do we see which office showed up in AI features?
In Search Console, open the generative AI performance report and group by page so each location URL is its own row. That report counts link appearances in AI Overviews and AI Mode. It is not a booking report. For the profiles, owners and managers can download performance for multiple locations and compare calls, website clicks, and direction requests. Ask the front desk which of those visits became appointments. Do not send patient details to Search Console or the profile.
Sources
Google and schema.org pages opened November 6, 2026 and returned HTTP 200. Wording changes, so confirm the live page. This is marketing operations guidance, not legal advice about entity names or corporate structure. DDS Web Solutions has offices in Sacramento and San Mateo. Our team has been building websites since 2014 and has served 100+ practices. SmileTrak is the analytics platform included with client work. ToothRank is a curated directory for DDS clients and is not a public listings site. Smyly is a consult preview and is separate from this entity work.
- •Google Search Central: AI features and your website
- •Google Search Central: Optimizing for generative AI features on Google Search
- •Search Console Help: Generative AI performance report
- •Search Console Help: Search generative AI control
- •Google Search Central: Organization structured data
- •Google Search Central: Local business structured data
- •schema.org: Dentist
- •schema.org: parentOrganization
- •schema.org: department
- •schema.org: sameAs
- •Google Business Profile Help: Guidelines for representing your business on Google
- •Google Business Profile Help: Performance data