ccTLD vs Subfolder for International SEO: A Keyword Planning Framework
Compare country domains and subfolders through your keyword-to-page plan. Use a workbook to record ownership, prerequisites, and planned URL changes.
Choose a country domain or subfolder by asking which structure your team can maintain for the pages a market actually needs. Keep the keyword research scoped to country and language in either case. Then compare domain control, publishing support, content ownership, reporting, and the work required to preserve existing URLs. The result should be a documented architecture decision, with a separate migration plan if live addresses will change.
This framework is for an in-house SEO preparing that recommendation. It uses Google documentation checked on October 26, 2026, and an original planning workbook. It does not report a ranking experiment or predict a traffic gain from changing domains.
What changes between a ccTLD and a subfolder?
A country-code top-level domain, or ccTLD, places content on a country-specific domain such as example.de. A subfolder places a section beneath a domain, such as example.com/de/. These examples describe addresses, not a completed targeting or content strategy.
- Country domain: Google's regional-site guidance describes country-specific domains as a clear country signal and an option for separating sites, with additional infrastructure and availability considerations.
- Subfolder on a generic domain: the same guidance describes lower same-host maintenance, with harder separation of sites. A folder name alone may not make its targeting clear to users.
- Check the suffix: Google treats some country-code endings as generic. Check its documented classification before assuming that every two-letter ending behaves like a country-targeted domain.
The practical question is what the structure lets your team publish and maintain. Can a shared platform support different catalogs? Who approves each section? Can a country team keep its domain and templates working? Those are project questions to answer with evidence. This article does not assign either structure an automatic ranking advantage.
Build a keyword record that survives either structure
Before drawing the URL tree, identify the content tasks the new market needs. If the country itself is still undecided, complete international SEO market selection first. A structure discussion is easier to resolve when it has a defined launch scope.
- Country and language: store these in separate fields. A language section might serve more than one country, while one country might require more than one language. Record the intended audience explicitly.
- Page task: state the job the page must complete, such as explaining a process, comparing options, or presenting an available product category.
- Keyword evidence: retain the exact approved query, source, country settings, check date, and a reference to the wording and result-page review. Keep estimates and unresolved questions identifiable.
- Existing and proposed URL: record both without replacing the original evidence. An empty proposed URL can be appropriate while the architecture decision is open.
- Content owner and next action: name who can maintain the page and what remains to be checked. A proposed path with no responsible owner is an unfinished plan.
Give the record a stable task ID. In an illustrative planning record, a task such as explaining delivery options could eventually live on a country domain or in a folder. Changing its address should not erase the query evidence or the reason that page was commissioned. The multilingual keyword mapping method covers how to assign accepted clusters to pages.
Compare prerequisites before choosing an option
The workbook compares three options: keep the current structure, assess a subfolder, and assess a country domain. Its five prerequisite fields are operational checks. They are not SEO ranking factors or a points system for declaring a winner.
- Domain access: can the team control the required domain and DNS? For a proposed country domain, verify availability and any registration requirements with the appropriate registry or registrar. The workbook supplies no legal or eligibility conclusion.
- Routing: can the platform publish the intended pages and handle the necessary links and locale navigation? Ask the implementation owner to demonstrate a representative URL.
- Owners: are publishing, review, and continuing maintenance assigned? A separate domain does not by itself create an independent operating team.
- Reporting: can the team identify the intended section and country in its reporting process? Name the reports and the person responsible, rather than assuming a URL label will make measurement complete.
- URL continuity: will existing addresses remain, or is there a reviewed mapping for the pages that move? For a new launch, explain why no existing URL move is required.
Use Yes, No, Unknown, or Not needed for each field, with supporting evidence. Explain every Not needed entry. An unanswered or unrecognized entry keeps the option on hold. A No removes it from the current comparison until the failed prerequisite is resolved. When all fields are Yes or justified Not needed and the evidence field is populated, the workbook marks the option Ready for comparison. It does not select the architecture or authorize a launch.
Write the final choice, reason, and decision owner in the separate editable decision fields. If multiple options remain viable, compare their actual implementation and continuing maintenance work. Keep a named constraint or estimate behind each conclusion. Do not substitute a generic claim that folders always inherit all authority or that country domains always win local searches.
Two hypothetical planning decisions
A new market on a shared platform. Suppose a team has approved page tasks for German-language content serving Germany and Austria. The platform can support separate sections, and one team owns both. A subfolder option is worth evaluating if its routing and maintenance checks pass. Keep the country records separate even if some pages are reused. Whether the project needs one shared German page or country-specific pages remains a content decision supported by the evidence; a folder label does not settle it.
An established country site with its own team. Suppose a business already has maintained pages on a country domain and proposes moving them under the main domain for simpler governance. Keep the current structure in the comparison. Ask which concrete problem the move solves and whether the team can preserve useful page tasks, map addresses, and monitor the transition. If the proposed benefit has no supporting evidence, holding the migration is a reasonable decision.
These are hypothetical project conditions, not observed market results. They illustrate why the same comparison can lead to different decisions. Neither contains a search-volume claim, a language preference, or a measured performance advantage.
Treat a change to live URLs as a migration
A new section with new pages and a move of existing pages are different projects. If the recommendation changes live addresses, use Google's site-move guidance to prepare an old-to-new URL map, plan redirects, update internal links and relevant canonical or localized-version annotations, and monitor the transition. Google notes that search visibility can fluctuate during a move; do not promise a fixed recovery date.
Keep each task ID attached to its old and proposed URL in Page plan. When a page is consolidated or retired, record that decision and its reason instead of forcing every row into a one-to-one relocation. Have the implementation owner validate the resulting handling before the move. This workbook is the planning handoff, not a redirect generator or complete migration specification.
Check tool scope as well. Google's Change of Address documentation covers moves between domains or subdomains and excludes path-only moves within a domain. A new folder does not automatically mean that this tool applies. Follow the current instructions for the particular move rather than treating every architecture change as the same operation.
Connect equivalent pages after the page jobs are clear
Google's localized-version guidance allows alternate URLs to be on different domains and describes hreflang as a way to identify language or regional variations. That supports documenting relationships across either structure. It does not establish that every page must have an equivalent in every market.
Record which pages serve equivalent tasks and which need a different brief. If the wording or result-page evidence is unresolved, return that record to the SERP validation workflow. Keep the address proposal separate from the content decision so a neat URL tree cannot hide missing research.
Finish with a short recommendation: keep the existing structure, assess a subfolder, assess a country domain, or hold. Name the market scope, the pages affected, the operational reason, the decision owner, and the next review point. If live URLs will change, attach the migration handoff. That gives the team a structure it can explain and a keyword plan it can continue to use.