One domain, separate office sites, or a hybrid for a multi-location dental group

Three architectures

A group this size usually inherits a mix: a corporate site, a few office domains from older brands, and a subdomain someone stood up for a campaign. The architecture choice is which of those hostnames stay indexed. It is not a template a vendor picks because folders are "stronger for SEO."

• •One domain, location folders. Every office patients can visit lives at a path on the group host, for example /locations/oak. The page for that path is the page you build in the location page guide.
• •Separate domain per office. oakdental.example stays the public site for that door. The group site may link to it. It does not replace it, and it does not canonical the office back to the group home page.
• •Hybrid after an acquisition. Doors that will share the group name move onto the group host. Doors that keep a distinct name on the sign keep their domain. The cutover steps for name, profile, and Ads access are in the post-acquisition transition.

A subdomain such as oak.group.example is not a folder. It is another hostname. Treat it with the separate-domain column for robots.txt and, often, for cookies, and with the one-domain column only when a Search Console domain property already covers it. The wider planning page for brand models is DSO and multi-location marketing. Which public name the sign will use, separate from the host choice, is in rebrand, co-brand, or keep the local name. The order for a group opening or buying its third office is in the emerging groups playbook.

Folders, subdomains, and separate domains

Google's URL structure guidance asks you to make the structure easy for people to read: descriptive words, hyphens between words, and fewer parameter copies of the same page. A path like /locations/oak fits that. A long id does not. The page does not say a subdirectory will outrank a different registered domain.

The practical split is the host. Google's robots.txt specification says the file applies only to the host, protocol, and port where it is hosted. A robots.txt on the group domain does not govern oakdental.example, and it does not govern a subdomain either. Each indexed host needs its own file, and a blocked path on one host says nothing about the others.

Search Console follows the same boundary in a different way. A domain property includes the subdomains and protocols of that one domain, and it is verified with a DNS record. A URL-prefix property includes only the prefix you enter, so https://group.example/locations/ is not the data for https://oakdental.example/. Two registered domains are two properties. You read them separately during a move.

Google's international site guide is about countries and languages, not dental offices. It still names the two shapes without a ranking order: a subdirectory is easier to keep on one host, and a subdomain is easier to put on another server. Use that as an operations note. Do not import it as a geotargeting setup for a city you do not have an office in. A subfolder and subdomain glossary entry states the same split in one place.

Canonicals

A canonical URL is the address Google selects as the representative copy among duplicates. Redirects, rel="canonical" annotations, and sitemap inclusion are signals. Google says the annotation is a hint, not a rule, and it may select a different URL than the one you prefer.

Use the hint when the same office page is reachable more than once: www and non-www, a trailing parameter from an ad, or an old builder URL that still returns the page. Google's consolidation guide puts redirects first among those signals, then rel="canonical", then the sitemap as a weaker hint. Combining them raises the chance your preferred URL is the one that shows. None of the methods is required for a site that does not have duplicates.

Do not use a canonical to glue different offices together. Oak and Pine are not duplicates because they share a header. Each office URL should canonical to itself. The home page canonicals to the home page. If a campaign domain is a copy of an office page and you do not want it indexed, redirect it. A canonical across hosts is still only a hint, and patients who book on the copy are on a different cookie than the site you report.

Redirect maps after an acquisition

When a hostname will stop being the indexed site, Google's site-move guide starts with a URL map: every current URL to its corresponding new URL. Build the list from the old sitemap, from Search Console links, and from pages that still get visits. Include PDFs and images. The redirects documentation names a website merger as a reason to send outdated URLs to the correct pages, not to a single dump URL.

• •Permanent and server-side. A 301 or a 308 tells Google to show the target. The same page says server-side redirects are the ones it is most likely to interpret as you intend, and to use a permanent redirect only when you will not revert it. A 301 redirect is that status, not a plugin that runs after the HTML loads.
• •One destination per URL. The site-move guide says not to point many old URLs at one irrelevant address such as the new home page. That can confuse people and may be treated as a soft 404. If several old service URLs were truly combined into one new page, those older URLs may share that one new page. Everything else gets its own row.
• •Credit and calendar time. On link credit, the site-move guide says permanent redirects, 301 included, do not discard PageRank. It also describes the swap in search results as gradual: weeks or longer for a medium-sized site, and more time when the site is large. Leave hostname redirects up for a year or more, which is the window that guide gives for recrawls and for other sites' links to be reassigned. Update your own high-traffic links so visitors are not stuck on the hop.
• •Change of Address is a hostname tool. Submit it in Search Console when the domain or subdomain changes. Google says you do not need it for a path move on the same domain, for HTTP to HTTPS, or for www versus non-www. Those still need the redirects, the new sitemap, and a canonical on each surviving URL.

Hosts you are keeping do not go in the redirect map. A hybrid that 301s a still-public brand domain onto the group home page throws away the site patients typed and asks Google to drop that host. The name you will put on the sign decides which column a door is in. Profile edits that go with the name change are in the post-acquisition guide, not a second listing.

NAP and Dentist markup

Whatever host you keep, the page for an office shows that office's name, street address, and phone in the HTML, matching the profile. Google's local business documentation says to define each location as a LocalBusiness type and to use the most specific subtype you can. schema.org defines Dentist as that subtype of LocalBusiness. The url property is the fully qualified URL of that specific location, and it has to be a working link. The example in Google's doc is a location path, not the corporate home page.

parentOrganization is the schema.org property for the larger organization this one is a subOrganization of. On the office page, the Dentist entry can point at the group's Organization entry. It records the relationship. It does not merge the two addresses into one profile, and it is not a substitute for a separate page. Google's Organization documentation describes adding that markup on the home page so Google can read the organization's administrative details. How this site applies that to a group, including what to keep off the office URLs, is in AI search for multi-location groups.

Markup that names a street the page does not show, or a phone the profile does not use, fights the visible NAP. If two acquired brands share a building, you still have one location. A second Dentist block does not create a second door.

Business Profile website links

Google's guidelines for representing your business say to provide a phone number that connects to the individual location, or a website that represents that individual location. They also say not to provide a phone or a URL that redirects or refers people to a landing page or a number other than that location's. A group homepage can represent the group. It does not represent Oak if Pine, Cedar, and Oak are all on it and the link dumps every profile there.

Set the website field to the surviving URL for that door: the folder on the group host, or the separate domain you decided to keep. If the old domain 301s to that URL, the profile should be updated to the final URL so patients are not sent through the redirect. A URL that 301s to a different office fails the "actual location" line in the same guidelines.

Appointment buttons are a different slot. Business Profile links can include up to 10 links in a category such as booking, and you can mark one as the preferred link. The scheduler URL does not replace the website field. Who may edit those profiles, and how a group of ten or more keeps the fields aligned, is in profile governance.

Analytics and attribution

Google's account structure guide treats a property as the container for one logical user base. The practical test it poses is whether you want to share that whole body of data with the people and the linked products that can open the property. If yes, one property. If a region's staff must not see another region's reports, use a separate property, or a subproperty where you have Analytics 360. The guide's usual pattern is one web data stream for the website journey inside that property, plus app streams only if you have apps.

Folders on one hostname are one website journey. Separate registered domains are not, until you say so. Cross-domain measurement passes the same user and session ids in a _gl parameter when someone follows a link or submits a form to a domain you listed. Without that, each root domain sets new cookies and new ids, so a patient who reads the group site and books on the office domain looks like two people. Google also recommends the setup for subdomains that do not share a cookie domain, because those hops can show up as self-referrals. Configure it on the web stream, and list every domain that should count as one journey. The glossary entry is cross-domain measurement.

The linker does not decide credit by itself, and it does not put a patient name in the hit. Event names, office slugs, and what must stay out of the payload are in GA4 calls, forms, and bookings. Read Search Console on each property you verified. Analytics will not fill a hole where the old host was never verified.

Domains, DNS, and access

Write down, per hostname, the registrar login, the DNS host, and the Search Console owners. A domain property is verified with a DNS record, unless the site is on a Google product such as Blogger or Google Sites. Verification help covers the methods for other property types. The people who can edit DNS can prove a domain property. The people who cannot edit DNS cannot.

Google's verification page says more than one person can verify the same property, and that if every verified owner loses access, the other users lose access too. Keep at least two group-controlled owners. An agency login can be a user. It should not be the only owner and the only registrar admin. This is an access list, not a legal opinion about who owns the practice entity.

Acquired domains need the same row before anyone points DNS at a new host. "We will transfer it later" is how a group discovers that the previous vendor is the only admin, after the old site has already started 301ing. Questions to put in a vendor review are in how to choose a DSO dental marketing company.

AI search and one set of facts

Google's AI features documentation ties those appearances to ordinary indexed pages that can show a snippet. There is no separate domain type that makes a group eligible. A location URL that is indexed, that shows that door's name and address, and that matches the profile is the URL an overview can cite. A second domain that copies the same page and canonicals elsewhere is a duplicate, not an extra entity.

Keep one public string for the group and one public string for each office, on the sign, the page, and the profile. parentOrganization connects the Dentist entry to the group. It does not rename the office. Google's generative AI optimization guide says Google Search does not use llms.txt or similar AI text files, so publishing one file per domain does not create consistency. The file neither helps nor hurts Google Search. Other tools may read it. Consistency is the visible facts and the markup that matches them.

The Generative AI performance report groups impressions by page. On a single domain you filter to location paths. On separate domains you open each property. The group worksheet for that reading is in the AI search guide linked above.

Decision matrix

Use the row that matches the names and the hosts you will actually keep. None of the three is a ranking winner. A group of three offices and a group of fifty use the same test per door.

Office URL and redirect planner

List the offices and any hosts you plan to retire. The table drafts one URL per office, the Business Profile website field for that URL, and a 301 row when a legacy host matches that office's slug.

Draft an office URL map and the redirects it needs.

Labels stay in this browser. Nothing here is sent to a server. A leading "Office in" is dropped from the slug, then the rest is lowercased, turned into ASCII, and joined with hyphens.

Office labels

One office per line, up to 60. Repeated lines are combined.

Main domain

Hostname only. No https:// and no path.

Architecture

One domain with office subfolders Each office is a /locations/ path on the main domain. Office subdomains Each office is a subdomain of the main domain. Separate office domains Each office gets a draft host ending in .example. Replace it with the domain you will use. Hybrid: keep listed legacy domains, new offices in subfolders A listed host whose name matches an office slug stays that office's URL. Other offices use a subfolder.

Legacy office domains being retired

Optional. One hostname per line, such as old-office.com. On the hybrid choice, a listed host that matches an office slug is kept as that office URL. The other choices draft a 301 away from each listed host.

Summary

Worked example. 3 offices. Architecture: One domain with office subfolders. Main domain: example-dental-group.com. 2 legacy hosts: 1 with a 301 to a matching office, 1 needs a target.

Worked example

Three generic offices on example-dental-group.com, with location subfolders. With JavaScript, your labels replace this example.

Worked example of a proposed URL and Business Profile website field for three offices

Office	Slug	Proposed URL	Business Profile website field	Note
Office in Folsom	folsom	https://example-dental-group.com/locations/folsom/	https://example-dental-group.com/locations/folsom/	-
Office in Roseville	roseville	https://example-dental-group.com/locations/roseville/	https://example-dental-group.com/locations/roseville/	-
Office in Elk Grove	elk-grove	https://example-dental-group.com/locations/elk-grove/	https://example-dental-group.com/locations/elk-grove/	-

Worked example redirect map

Worked example of 301 rows for two legacy hosts, including one that needs a target

Legacy host	Old home	Path pattern	Target	Status	Note
folsom.example	https://folsom.example/	https://folsom.example/*	https://example-dental-group.com/locations/folsom/	301	301 from the old home. The /* row is a pattern note for other paths on that host.
old-office.com	https://old-office.com/	https://old-office.com/*	needs a target	needs a target	No office label slug matches this host.

Before you launch the map

• The canonical on each office URL points at that same URL.
• The name, street address, and phone on the page match that office's Business Profile.
• The office page has one Dentist or LocalBusiness block for that door.

Put the office URL in the Business Profile website field. Add the UTM pattern from the profile governance guide only if the group already uses it: utm_source=google, utm_medium=organic, utm_campaign=gbp, and utm_content set to the office slug. Skip those parameters when the group does not already use them.

Copy URL table and redirect map as CSV Clear

Pause motion

Questions for an agency

Ask these in a proposal review. They are procurement questions. They do not name or rank any firm, and they are not a contract.

1. 1. Which Search Central page says a folder outranks a separate domain?

   URL guidance asks for simple, readable addresses. It does not score folders above hostnames. A vendor who leads with a ranking bonus is skipping the operating choice.

2. 2. Show the redirect map. How many old URLs land on the home page?

   Google's site-move guide says not to send many old URLs to one irrelevant destination such as the new home page. That pattern can be treated as a soft 404. A merger redirects each outdated URL to the correct page.

3. 3. What does the canonical on a location URL point at?

   A canonical is a hint about duplicates, and Google may choose a different URL than the one you name. Pointing every office at the home page asks Google to treat different doors as copies of one page.

4. 4. What is pasted in each Business Profile website field, and does that URL redirect?

   Google asks for a website that represents that location, and it says not to use a URL that redirects people to a landing page other than the actual location.

5. 5. Who can sign in to the registrar and the DNS host after the contract ends?

   A Search Console domain property is verified with a DNS record. If only the agency can edit DNS, the group cannot prove that property or move it.

6. 6. Is cross-domain measurement on, and which domains are listed?

   Without it, each root domain mints new cookies and new ids. Folders on one host do not need the linker. Separate live domains do, if one property should show one journey.

7. 7. Will anyone open a second Business Profile for a door that already has one?

   Google's representation guidelines say not to create more than one profile per location. An acquisition edits the profile patients already review.

Checklist

Twelve checks before you move DNS or change a profile website field. Ticks stay in this browser only.

What DDS Web Solutions builds

DDS Web Solutions builds practice websites. Our team has been building websites since 2014, and we have served 100+ practices. Offices are in Sacramento and San Mateo. The products are Smyly, SmileTrak, and ToothRank. The planning page for groups is DSO and multi-location marketing.

Sources

Wording on these pages can change, so confirm the live page. This is marketing guidance, not legal advice.

• •Google Search Central: URL structure
• •Google Search Central: What is URL canonicalization
• •Google Search Central: How to specify a canonical URL
• •Google Search Central: Redirects and Google Search
• •Google Search Central: Site moves with URL changes
• •Google Search Central: Robots.txt specifications
• •Google Search Central: Managing multi-regional and multilingual sites
• •Google Search Central: Local business structured data
• •Google Search Central: Organization structured data
• •Google Search Central: AI features and your website
• •Google Search Central: Optimizing for generative AI features
• •Search Console Help: Generative AI performance report
• •Google Business Profile Help: Guidelines for representing your business on Google
• •Google Business Profile Help: Manage your local business links
• •Search Console Help: Add a website property
• •Search Console Help: Verify your site ownership
• •Analytics Help: Google Analytics account structure
• •Analytics Help: Set up cross-domain measurement
• •schema.org: Dentist
• •schema.org: LocalBusiness
• •schema.org: parentOrganization