Introduction
Choosing between a ccTLD vs subdomain vs subdirectory starts with a practical question: how will your business run its websites in different markets? A French site at example.fr has a clear country association. Using fr.example.com gives you a separate hostname, while example.com/fr/ keeps French pages within the main website. Each setup can work for international SEO. Think about who will manage the pages, how much the markets differ and whether your current website can support the structure you have in mind.
Table of Contents
ccTLD vs Subdomain vs Subdirectory: Which URL Structure Is Right for You?
Before choosing a structure, look at how much separation your international websites actually need. A business with one marketing team and a shared CMS has different requirements from a group whose regional teams manage their own platforms.
Key Differences Between the Three URL Structures
The URL patterns may look similar, but they organise a website in different ways.
Factor | ccTLD | Subdomain | Subdirectory |
Example | example.fr | fr.example.com | example.com/fr/ |
Country targeting | Strong country signal | Regional label in the hostname; needs wider context | Regional label in the URL path; needs wider context |
Site separation | Separate domain | Separate hostname | Section of the main website |
Technical setup | Can use separate infrastructure | Can use separate or shared infrastructure | Usually managed within the main site’s infrastructure |
Day-to-day management | May involve separate site administration | Depends on how independently it is run | Often centralised |
Typical trade-off | More domain and maintenance work | More configuration and coordination if managed separately | Less freedom to separate regional systems |
These are typical arrangements rather than technical rules. A subdomain can use the same CMS as the main site, and a large website can make subdirectories complicated to maintain.
Google’s guidance on multi-regional websites describes the trade-offs between country-specific domains, subdomains and subdirectories. It does not prescribe one structure for every business.
What Is a ccTLD?
Definition and URL Examples
A country-code top-level domain is associated with a country or territory. Examples include example.fr for France and example.de for Germany. A UK-focused site may use example.co.uk. A business can run separate sites for separate markets, each with its own local details, products or commercial terms.
Country-Specific SEO Signals
Google treats a ccTLD as a strong signal of the country a site targets. It can help make that association clear, but it does not guarantee rankings. The page still needs to answer local customers’ needs. A French domain with outdated prices or irrelevant offers will not become useful just because it ends in .fr.
There are exceptions to the country-code rule. Google treats some country-code domains, including .io and .ai, as generic top-level domains because of their wider use. Check the current rules and availability before building a strategy around a particular domain.
Costs and Operational Limitations
A separate domain brings more than a registration fee. Someone has to manage its renewal, technical setup, content updates and reporting. If a UK retailer changes its returns policy, the French site may need a different update rather than a direct copy. That work grows with each market, so clear ownership matters.
What Is a Subdomain?
Structure and URL Examples
A subdomain sits before the main domain, as in uk.example.com or fr.example.com. It gives a site its own hostname and can be used for a regional website, service or application.
Infrastructure and Operational Flexibility
Subdomains can use different hosting, CMS platforms or release processes. This helps when regional teams need their own systems. Separate infrastructure is not essential, though: one central team can manage several subdomains through the same CMS and templates.
Before choosing this route, decide what needs to be separate. If the French team uses a different platform, a subdomain may fit. If everyone publishes through one workflow, another hostname may add configuration without solving a real problem.
SEO and Indexing Considerations
A subdomain does not automatically rank worse than a subdirectory. Its pages still need relevant content, crawlable links and correct technical settings. Check that search engines can discover and index the pages, and review canonical tags and hreflang where relevant. If different teams manage different systems, include each hostname in routine audits rather than checking only the main site.
What Is a Subdirectory?
Structure and URL Examples
A subdirectory places a section after the domain, such as example.com/uk/ or example.com/fr/. A French service page could sit at example.com/fr/services/. Pick a naming pattern early and use it consistently; mixing /fr/, /france/ and language codes without a reason makes the site harder to manage.
Centralised Management and Maintenance
Subdirectories let regional pages sit within the same website and often the same CMS. A central team can maintain templates and navigation while local editors update prices, availability or delivery details. That can reduce repeated development work, but shared templates do not remove the need to review local content.
Technical Constraints and Limitations
A subdirectory can be awkward when regional teams need separate hosting, CMS platforms or release schedules. Site-wide changes may also affect every market folder. If a developer changes routing rules, test important URLs across the regional sections instead of assuming that the main homepage tells the whole story.
Country Targeting vs Language Targeting: What Does Your Website Need?
Multilingual vs Multi-Regional SEO
A multilingual site offers content in different languages. A multi-regional site targets users in different countries. A Canadian site with English and French pages is multilingual; a retailer serving the UK and US is multi-regional, even if both audiences use English. Some businesses need to handle both.
Google recommends distinct URLs for language versions rather than changing a page only through cookies or browser settings. Otherwise, search engines may not find every version. Read Google’s guidance on international websites before deciding how to organise the pages.
Examples of Country and Language Targeting
A UK retailer expanding to the US may keep English on both sites but change prices, delivery terms and product information. It could use example.com/uk/ and example.com/us/. A Canadian business serving English- and French-speaking customers might use example.com/en-ca/ and example.com/fr-ca/.
A business serving the UK, France and French-speaking Canada has both country and language needs. Its URLs should make those versions clear, and suitable hreflang annotations can tell Google how they relate. The exact path is a choice; consistency and useful local content matter more than a particular naming convention.
How to Choose an International Website Structure
Target Markets and Audience Requirements
List the countries and languages you plan to serve. Then identify what genuinely changes: prices, products, delivery, legal details, contact information or language. The structure should reflect those needs, not create separate URLs for markets the business is not ready to serve.
Technical Independence and Team Control
Think about who will publish and maintain each regional site. One team using one CMS may find subdirectories simplest. Regional teams with different platforms or release processes may need subdomains or separate country domains. Check the hosting and CMS constraints before committing; discovering a limitation after the pages are built can cause avoidable rework.
Long-Term Costs and Maintenance
Registration is only one cost. Consider translation, content updates, development and technical monitoring. Separate websites need clear ownership, while a central structure needs someone to check that local details remain accurate. The cheapest launch option is not always the easiest to run a year later.
URL Structure Selection by Business Scenario
Take a UK retailer expanding into Ireland. If the same team manages both markets, example.com/ie/ may be all it needs. A SaaS business selling in English, French and German could keep its language pages under one domain. Things change when regional teams run their own systems and manage their websites separately. In that case, subdomains or country domains may be more practical. Look at how each market will operate before settling on a URL structure.
International SEO Implementation Checklist
A technical SEO review can help identify crawlability issues, incorrect canonical tags and problems with regional URLs before launch.
URL Planning and Content Localisation
Map the URLs for every country and language before publishing. Note which pages are alternatives and keep the naming pattern consistent. A UK product page might use example.com/uk/product/, with its French counterpart at example.com/fr/product/.
Localisation means more than translating a heading. Check product availability, delivery terms, contact details and local wording. Ask someone who knows the market to review the page; a literal translation can miss details a local reader will spot immediately.
Hreflang Implementation and Validation
Use hreflang to identify alternate pages for different languages or regions. For a UK and French page, the HTML might include:
<link rel=”alternate” hreflang=”en-GB” href=”https://example.com/uk/” />
<link rel=”alternate” hreflang=”fr-FR” href=”https://example.com/fr/” />
Each page must reference itself and its alternate, and the references must be reciprocal. Use valid language-region codes: en-GB is correct for English intended for the UK; en-UK is not. Google explains the requirements in its hreflang guidance. The annotations can be provided in HTML, HTTP headers or XML sitemaps; choose a method the team can maintain.
Canonicalisation Across Regional Versions
A canonical tag signals which URL should be treated as the preferred version among duplicate or very similar pages. Distinct UK and French-language pages will often have their own self-referencing canonicals. Do not point every market page to the UK version by default. For similar pages in the same language, consider canonicalisation and hreflang together. Google’s canonicalisation documentation explains how it selects a representative URL.
Internal Linking and XML Sitemaps
Regional pages need links that users and search engines can follow. A country selector can help visitors find another version, but important pages should also be connected through the website’s normal navigation and relevant internal links.
Check that those links lead to the preferred URLs. Links to old paths or unnecessary redirects make the site harder to maintain.
Keep XML sitemaps consistent with the URLs intended for indexing. They can also carry alternate-language annotations, if that is the method chosen for hreflang. Google treats HTML, HTTP header and sitemap methods as supported options; the important thing is to implement one consistently rather than let several versions drift apart.
A sitemap helps Google discover URLs. It does not guarantee that every URL will be indexed.
Technical Validation Checklist
Before launch, check status codes, indexability, canonical tags, hreflang references, internal links and sitemap entries. Make sure the main content and links appear in rendered HTML. Google Search Console’s URL Inspection tool can help with individual pages; a crawl can reveal problems repeated across a whole regional folder.
How to Migrate an International URL Structure Safely
URL Mapping and Migration Planning
Export the current URLs and map each one to its intended destination. Include service pages, products, regional landing pages and URLs that receive traffic or backlinks. If example.com/fr/services/ moves to fr.example.com/services/, record that exact match. Sending every old URL to one general page can leave visitors without the information they expected.
Redirects and Technical Signal Updates
Use permanent redirects from old URLs to the closest relevant replacements. Update internal links, canonicals, hreflang and XML sitemaps at the same time. Avoid redirect chains where possible. Google’s site migration guidance recommends preparing URL mappings, testing the new site and monitoring both old and new URLs.
For a large website, moving a small, lower-risk section first can reveal problems with templates or redirects before the wider change. Avoid changing the URL structure, CMS and design all at once if possible; when several things change together, finding the cause of a traffic drop becomes much harder.
Performance Monitoring After Migration
Before the move, export your Google Search Console data so you have something to compare against later. Keep an eye on the pages that matter most, particularly those that bring in organic traffic from your target markets. Analytics can help you see whether visitors are still reaching key pages and completing enquiries or purchases.
Don’t panic if rankings shift in the first few weeks. Google needs to discover and process the new URLs, and there is no set date by which performance will settle.
If traffic starts to fall, check the affected pages individually. Does the old URL redirect to the right destination? Can Google index the new page? Has any content disappeared, or is a canonical tag pointing to the wrong URL? Check the hreflang references too, especially if the migration changed your regional URLs.
Leave the redirects in place after launch. Seeing the new URLs appear in search results isn’t a reason to remove them; users and other websites may still follow the old addresses.
Need Help Planning Your International SEO Structure?
Expanding into another country often means more than adding a new folder to your website. You may need different content, separate systems or a way for local teams to manage their own pages. The ccTLD vs subdomain vs subdirectory decision should start with those practical needs. Before making a change, check how the new URLs will work with your existing pages, internal links and international SEO setup. If you’re moving to an established site, plan the redirects and check indexing after launch rather than assuming everything will transfer cleanly.
Need help working out the right approach? Explore Midland Marketing’s international SEO services.
Frequently Asked Questions
Does a Subdomain Affect SEO Rankings?
A page on uk.example.com can rank just as well as one in a subdirectory. The URL format alone doesn’t decide that. What matters is whether the page serves its audience and Google can find and index it. A subdomain makes sense when a regional team needs its own website setup. When everyone uses the same CMS and publishing process, keeping the pages under example.com/uk/ may save some work.
Are Subdirectories Better Than Subdomains for SEO?
Not by default. Subdirectories are often easier to manage when one team handles the whole website. Subdomains give regional teams more room to use different systems or release schedules. Think about how the site is actually run before choosing. Moving pages into folders just because they sit closer to the root domain is unlikely to be a good reason for a migration.
Does Using a ccTLD Improve Local SEO?
A domain such as example.fr gives Google a strong signal that the website targets France. That can help clarify the intended market, but it won’t make a page rank well on its own. French customers still need relevant content, accurate local information and pages that meet their needs. A ccTLD is worth considering when a separate country website fits the business, rather than simply as an SEO tactic.
Is Hreflang Necessary for Every International Website?
No. Hreflang is useful when a website has pages serving different language or regional audiences. A UK page and its French counterpart, for instance, can use the attribute to identify each other as alternatives. Both pages need to reference themselves and the other version. Get those links wrong and Google may not interpret the relationship as intended. The tags also won’t fix a poor translation or content that doesn’t suit the local audience.
Can You Change from a Subdirectory to a ccTLD Without Losing Rankings?
You can move to a ccTLD, but don’t expect rankings to stay exactly as they are throughout the change. Start with a URL map so every old page has a suitable destination. Set up permanent redirects, update internal links and check canonical tags and hreflang before launch. After the move, watch Google Search Console for indexing errors and changes in organic traffic. If a page loses visibility, investigate its redirects, content and indexing status before assuming the new domain is to blame.
