One domain or several: site architecture for two markets
For most Quebec businesses opening a second market, a subdirectory under the existing domain is the default choice. It inherits the authority already accumulated and costs little to maintain. A subdomain or a separate domain detaches more easily when the day comes, and each stays justified in four specific cases.
- Three structures are open to you: the subdirectory, the subdomain and the separate domain. Google documents the pros and cons of each one without preferring any.
- Pooled authority is the decisive argument. A version housed under the existing domain inherits what has been built, a new domain starts from zero.
- Ongoing upkeep is the most forgotten line item. A second domain duplicates deployments, measurement, security and shared content.
- Reversibility runs the other way: the structure that shares authority best is the one that separates with the most difficulty.
- Google does not vary the origin of its crawler to discover the regional versions of a site. You have to declare them yourself.
On this page
What is authority pooling
Authority pooling is the fact that the trust signals a domain accumulates benefit every page it hosts. A second site version placed under the same domain inherits that standing the day it goes live. A separate domain starts from zero and has to rebuild that reputation on its own, year after year. It is the main economic argument for the subdirectory, and the main hidden cost of a separate domain.
The three possible structures
The question comes up late and gets settled fast. The second market is validated, and someone asks where the new version of the site will live. The answer takes ten minutes, for a choice that commits you for five years.
Statistics Canada counted 48,036 goods exporters in 2024, down 1.4% year over year. Among them, 65.9% sold to the United States only. Many serve two markets with a single site.
Google Search Central sets out the options in its documentation on multi-regional sites. It recommends no structure, and lists for each one what it gives you and what it takes away.
The subdirectory
The subdirectory, also called a subfolder, is a path added to the existing domain, of the form yourdomain.com/en/. Google credits it with two advantages: it is easy to set up and it takes low maintenance. The documentation also names its limits: geographic intent is barely visible, the server location is single, and separating the sites is more complex.
The subdomain
The subdomain places the new version in front of the name, of the form en.yourdomain.com. Google credits it with being easy to set up, allowing several server locations and separating easily. Its limit fits on one line: geographic intent cannot be read from the URL alone.
The separate domain
The separate domain is a domain name of its own, often a country-code top-level domain tied to one country. Google credits it with clear geotargeting, a server location that does not matter and easy separation. Against that, the documentation lists four drawbacks: it is expensive, its availability is limited, its registration requirements are strict, and it targets a single country.
The documentation covers a fourth possibility, URL parameters, in order to advise against it.
One passage deserves a second read. Google does not vary the origin of its crawler to discover the regional versions of a site. Declaring them is on you, whatever the structure.
Four axes to settle it
The choice plays out on four axes. Three can be observed today, the fourth has to be anticipated.
The geographic signal you send
A country-code top-level domain sends the clearest signal. It is tied to its country and Google reads it that way, with the server location playing no part. The subdomain and the subdirectory do not carry that signal in their address. The weakness is corrected by declaring the versions, which you owe in any case.
Authority shared or split
This is the axis technical comparisons forget, and the one that costs the most. A domain accumulates trust signals over the years, through the links it receives and the history it carries. An English version dropped into a subdirectory inherits them the day it goes live. Placed on a new domain, it starts from zero, and the rebuild is counted in years.
The cost of ongoing upkeep
A second domain is not a second site, it is a second permanent worksite. Every change has to be deployed there, security certificates renewed there, measurement watched there and shared content maintained twice. One revised return policy becomes two edits. The subdirectory duplicates nothing on that list, and that is what Google sums up as low maintenance.
How reversible the choice is
The ranking flips here, and the decision turns out less simple than it looks. The separate domain separates easily, and so does the subdomain. The subdirectory is the one that separates with more difficulty. A business that runs it for three years, then wants to move its English version elsewhere, is running a full migration.
The default choice
For a Quebec small or mid-sized business opening a second market, the subdirectory wins most of the time, for an economic reason before a technical one.
Pooled authority is an asset you have already paid for. The subdirectory lets you cash it in the day the new version goes live. The separate domain makes you buy it back, with time nobody writes into the plan.
Lower upkeep is the second argument. A team that runs one domain runs one set of deployments and one measurement chain. With two, it spends part of its time synchronizing the identical.
What you give up is the geographic readability of the address, replaced by a declaration you had to produce anyway. One condition remains: your platform has to serve both versions under a single domain, with stable addresses.
A separate domain is decided in one meeting and paid for over five years. What it costs appears on no invoice: authority that has to be rebuilt, and upkeep that has to be done twice.
Falia analysis frameworkWhen it does not hold
The default recommendation gives way in four situations, all of them recognizable before a line of code is written.
The first is a legal obligation to host locally. Some countries require data to stay on a server located inside the territory. The subdirectory cannot do that, since it has a single server location.
The second is a distinct brand. If you sell in the other market under another name, the domain follows the brand. Housing one brand in the subdirectory of another creates a confusion nobody untangles.
The third is the planned sale of one of the two entities. If the business plan considers selling one of the two activities, the separate domain transfers with it. A subdirectory cannot be handed over as is: it has to be detached and migrated at the worst possible moment, the transaction itself.
The fourth is a platform that imposes its structure. Several online retail platforms create one store per market, with its own domain or its own subdomain. The question becomes the cost of working around the platform, against the cost of accepting it. The second wins almost every time.
One worry comes back without being an exception: the fear that the English version will hurt the French one. That risk comes from a missing declaration, not from the structure.
The cost of each option can be worked out before it is debated. A separate domain adds a hosting budget, a content production budget and maintenance that comes back every year, while the subfolder reuses authority you have already paid for.
The decision therefore rests on three numbers: the annual cost of the second site, the margin expected from the target market, and the risk that revenue from the home market drops during the migration. A leadership team without those three numbers is not making a trade-off, it is picking a technical preference and discovering the price afterward.
What to settle before registering a second domain
No structure is better in itself. The question is which one costs the least in your business, once authority and upkeep are counted.
- How much authority has our current domain accumulated, and do we accept depriving the new version of it?
- How many hours a month would duplicated deployments and measurement cost us?
- Does a legal obligation force us to host inside the target territory?
- Do we expect to sell one of the two activities within the next five years?
- Does our platform serve both versions under a single domain, with stable addresses?
The good signal: upkeep of the second domain priced in hours per month, and the authority rebuild priced in years. The bad signal: future flexibility invoked without saying what it costs in the meantime.
Comparing the three structures against your real constraints, before you register anything, is part of what we cover in a paid audit.
The record that settles the question fits on one page. List what exists today in a single copy and would exist in two: the site template, the return policy, the security certificate, the measurement property, the search console access. Next to each line, write the number of times you touched it in the last twelve months, then double the total. You get the annual upkeep cost of the separate domain, counted in actions. The decision meeting never has that number in front of it.
Before you choose your architecture
Declaring the versions is covered in what happens when two versions compete for the same page, and the effect of a .ca address outside Canada in this note on the country-code domain. The traps of a store in two languages are detailed in what breaks between the translation and the addresses. The case of a platform that imposes its structure is treated in opening a market without duplicating your store, and the logic of paths for a large catalog in the URL architecture of a large catalog. The day a separation becomes necessary, the method is set out in changing address without losing your traffic. The blockers that cancel out everything else are listed in what stops a site from being crawled. How links move between your pages is explained in the lever you control entirely, and the neighbouring English market in what translation does not settle.
What you will publish on those addresses is framed in generating leads in a market that does not know you, and price display by market in tariffs and price display.
Opening a market is at the heart of the Develop a new market goal.
The lever involved in this decision is search engine optimization.
Frequently asked questions about two-market architecture
Subdirectory or subdomain: which one should you choose?
The subdirectory suits most businesses, because it inherits the authority of the domain and takes little upkeep. The subdomain becomes preferable when a technical or legal constraint requires a separate server, or when the separation is already planned.
Does a separate domain per country help local search?
Google documents that a country-code top-level domain gives clear geotargeting, with the server location playing no part. The same documentation cites its cost, its limited availability, its strict requirements and the fact that it targets a single country. The signal you gain is paid for with authority you have to rebuild.
What is expensive about a second domain?
Two things, and neither shows up on an invoice. Authority starts from zero and gets rebuilt over years. Upkeep is duplicated: deployments, measurement, security and shared content. The price of the domain name is the only visible line, and the least important one.
Can you change structure later?
Yes, but the price depends on where you start. A separate domain or a subdomain detaches easily, and Google documents it. A subdirectory separates with more difficulty and calls for a full migration, with its redirect plan and its risk of losing traffic.
Does Google find our regional versions on its own?
No. The documentation is explicit: Google does not vary the origin of its crawler to discover the regional versions of a site. Those versions have to be declared, and that obligation applies to all three structures.
- Google Search Central, Managing multi-regional and multilingual sites, official documentation, accessed August 2026. Pros and cons of the country-code top-level domain, the subdomain and the subdirectory, and the absence of variation in the crawler origin.
- Statistics Canada, Trade in goods by exporter characteristics, 2024, The Daily, May 16, 2025, accessed August 2026. Number of exporting businesses and concentration on the United States market.
Geneviève puts the strategy for your engagement into action. She leads all our web development projects: Shopify, WordPress and the new ways of building a site with AI. She manages our team of developers and translates your business needs into technical language. She runs your organic search (SEO), your visibility in AI answers (GEO) and your site's conversion rate optimization (CRO). Her work is at the heart of three goals: Attract customers with SEO and AI, Improve your site's conversion, and Strengthen your visibility in AI answers. With Gabriel, she also builds the landing pages for your advertising campaigns. She writes mainly about SEO, AI visibility and web design.
About Falia →
SEO
Paid advertising
Conversion
AI visibility
Web design