Two hosts or folders already confuse Google
The UK page appears for US queries, or the US page appears in the UK. Tags in a spreadsheet did not fix it. The pair is incomplete, the codes are wrong, or the documents are still clones.
International SEO
International SEO: Hosts, Hreflang, and Language versus Country
International SEO at SEOConsultants.ai is how the site is versioned across locales you will actually maintain. We choose the host model, write hreflang as a return-tag contract, and keep language targeting separate from country targeting. This is not a country essay, not a translation product, and not a promise that tags raise rankings.
- Hosts
- Contract
- Distinguish
- Validate
Position
We version the site across locales you can keep
Most teams do not need another country blog. They need a .com that must not be the UK result while a .co.uk exists, or a folder that must not be a noun-swap of the US page. International SEO exists for that split. Which host you will maintain. How locale URLs claim each other. Whether you are targeting a language, a country, or both.
One market
USA, UK, Singapore, Dubai, and Sydney own how those markets search. International SEO owns how the site is split so they do not share one URL.
Open locationsLive-market operations
Global SEO runs a shared backlog after the properties already exist. If hosts and return tags are still undecided, start here. If the sites are live and teams are cloning, open global SEO.
Open global SEOThe large-company program
Enterprise SEO is the program when many sites and teams have to stay honest. It can require that a locale not ship without return tags. Writing those tags and choosing the host stays here.
Open enterprise SEOA door or a listing
A storefront in one city is local SEO. The Maps product is Google Business Profile. A .com and a .co.uk that must not cannibalize each other is this page.
Open local SEOHow searchers behave in one market still lives on a location page. Operations across live markets still live on global SEO. Search work across many brands and launches still lives on enterprise SEO. A crawl that cannot fetch a locale still lives on technical SEO. This page does not reprint those jobs. It makes the site versioned so they have something honest to run.
We will not staff native-speaking specialists as a claim. Query research in Arabic or Chinese lives on the market page that owns those searches. We will not print a traffic-by-country forecast. We will not add hreflang in a plugin and call the architecture done. If you have one country and one language, you may not need this page yet.
When to buy
When a second locale can steal the first result
Buy international SEO when more than one locale must share a site system. One country and one language is usually a market page, not this build.
You have not chosen the host you can keep
IT wants subdomains. Brand wants ccTLDs. Content wants folders. Nobody has written which model you can re-deploy after a design-system change. That choice is this page.
Language and country are being treated as the same thing
Someone wants to 'cover Spanish' and 'cover Mexico' with one set of tags. en is not en-GB. A language target is not a United Kingdom market page. We write the decision before we write the codes.
A plugin looks green and the crawler disagrees
The CMS shows hreflang. View source does not. The sitemap lists a pair the HTML does not. Validation is a crawl of both ends, not a settings screen.
Process
How we work
Four steps: Hosts, Contract, Distinguish, and Validate. Each step has a named outcome. We do not run a global content calendar inside step two. The process exists to make locale versions true.
-
Hosts
We name the object you will maintain: ccTLD, subdomain, folder, or one host. A ccTLD is a separate property. A folder shares equity and demands real documents. We pick the model you can re-ship after a template change, not the one that looks elegant in a slide.
Outcome A written host choice you can actually keep.
-
Contract
We write hreflang as a return-tag contract. If A claims B, B must claim A. We name x-default, the codes, and one source of truth: HTML, headers, or sitemap. A mix that disagrees is how validation fails. Canonicals that point at another locale fight the pair.
Outcome Pairs that return, including x-default.
-
Distinguish
We separate language from country. Query research stays on the market page. Architecture stays here. Spanish across several countries is not the same decision as Mexico as a country. We will not invent ISO codes Google does not use.
Outcome A targeting decision the codes can match.
-
Validate
We crawl both ends. We check the chosen source of truth. Search Console is an input, not a strategy. If the pages are clones, tags will not invent two intents. Access bugs go to technical SEO. Duplicate work on live markets goes to global SEO.
Outcome A sample of live pairs that actually return.
Outcomes
Expected outcomes
International SEO produces a versioned site you can keep shipping. It does not produce a ranking in every country overnight, and it does not replace a market page or a global ops cadence.
Host decision
ccTLD, subdomain, folder, or one host, with why you can maintain it after the next template change. Named people, not a department.
Return-tag contract
The pair list, codes, x-default, and one source of truth. Reciprocity or it is not a contract. A plugin screenshot is not the contract.
Language versus country note
What you are targeting, in one page. Query research stays on the market page. This note only says how those documents are versioned.
Validation sample
A crawl of both ends for a set of money URLs. Named coverage issues only when Search Console can support them.
Handoff note
Which service owns what is left: technical SEO for fetch, global SEO for live-market ops, enterprise SEO for launches across many brands, locations for one market.
Benefits
Key benefits
The intended locale can be selected
Pairs return. Codes match the decision. Canonicals do not fight the contract.
A host model you can re-ship
The next design-system change does not orphan a ccTLD nobody staffs. Folders are allowed when that is the honest operations choice.
Language and country stop being mixed
Market research stays on market pages. Architecture stays here. Thin locale folders are refused.
The right door after the site is versioned
Ops, launches, crawl, and one-country work each have a page. You are not asked to buy all four because the proposal needed length.
Operating model
The versioning we actually ship
International SEO only works when both ends of a pair can be fetched. If nobody can change the template, we are configuring a plugin, not building a contract.
Every international SEO engagement starts from four facts: the locales that must not steal each other, the host you can maintain, the person who can change annotations, and the market page that should own query research. If any of those four is missing, we spend the first week naming it. We do not fill the week with a tour of countries you might enter.
We test the documents, not the CMS. Does this locale URL match search intent in that market's HTML? Does coverage have topical relevance, or is it the US draft with a folder swapped? Keyword density is not an international SEO metric. If two locale URLs are the same document, the decision is to stop one of them or write a second page, not to sprinkle more tags.
The roles below are the default. You may change them. You may not leave host ownership implied. Implied ownership is how two CMS emit two graphs for one pair.
- International SEO lead SEOConsultants.ai writes the host choice, the contract, and the validation sample. We do not silently become your global ops manager or your market copywriter.
- Engineering or CMS Owns the renderer and the chosen source of truth. A dropped link tag after a header redesign is a failed validation, not a surprise next quarter.
- In-house SEO Names which locales are in force and whether a pair is already supposed to exist. They are not asked to invent ISO codes.
- Content Writes a real document for each locale that deserves one. They may refuse a folder that would only be a noun-swap.
- Leadership Funds or refuses the host model. An unread pair list is not an international SEO failure. A ranking promise from tags would be.
On the pair
What we inspect first
The first session is for two live URLs that should be a pair, not a tour of countries on a slide.
We ask which locales already take traffic, or which second locale would steal the first if you launched it tomorrow. A US .com and a UK folder is a valid set. 'We want to be global' is not. If the set cannot be named, international SEO stops at that sentence.
We then fetch both ends. View source, the chosen annotation source, canonicals, and whether the body matches search intent in that locale. A preview that looks complete in a logged-in CMS is not evidence. A one-way tag is the first finding.
The last part of the session is the host choice or the stop. A choice names the model, the first pairs, and the person who can ship them. A stop names what is missing: a second document, fetch access, or a job that is actually one market. Both are international SEO outcomes. A plugin install is not.
AI search and LLMs
How AI search questions get handled across locales
International SEO can make the intended locale document eligible. It cannot become the AI SEO program or a citation product for every country.
Leadership now asks whether each country will appear in Google AI Overviews (AIO) or in a chatbot answer. Those questions are real. They are not all this page. If the UK URL still canonicalizes to the US page, extractors have one document. That is a contract finding. If the pages are already distinct and models still mix the UK offer into a US answer, that is LLM SEO or an AI search audit.
The right document first
If the pair is broken, generative search has no honest locale page to quote. International SEO fixes the versioning. It does not sell Overview presence per country.
Entity names on the locale page
We check whether the organization, product, or place is named the way that market speaks. That is entity optimization as a test of the document, not a Knowledge Graph program we sell from this build.
Route the rest
How models describe the brand across countries belongs on LLM SEO. Ops across live markets belong on global SEO. Query research in Arabic or Chinese belongs on the market page.
Schema
Structured data on locale URLs
JSON-LD can help extractors read a page that already tells the truth in that locale. On an international build, invalid markup is often a US graph pasted onto a UK URL.
HTML first
We will not add Organization or Product markup to a clone and call the locale done. Schema that disagrees with the local HTML is a validation failure.
One source of truth
The contract names which system emits hreflang and which system emits JSON-LD. Two apps injecting two graphs for one path is how errors start. Technical SEO can own fetch once the owner is named.
No citation shortcut
Extra fields will not force generative search to cite every locale. International SEO can stop a schema project that is being used instead of writing a second document. Eligibility is not a purchased mention.
Teams
Working with engineering, in-house SEO, and market teams
International SEO assumes someone can change the template on each locale. We plug into that path. We do not replace it with another hreflang plugin.
Engineering
Usually the people who can keep link tags through a header redesign. Our job is a contract they can fail in review. We do not file fifty crawl tickets that belong on technical SEO after the pair exists.
In-house SEO
Chooses which locales are in force and defends a real document when a campaign wants a folder of swapped adjectives. They are not asked to become linguists for every market.
A market team or agency
Can keep writing once the host and contract are honest. If they are paid to publish a private clone of the US site, two jobs collide. We will say that in the first pair list. Live-market ops then belong on global SEO.
Questions
Frequently asked questions
Is this SEO for the UK, USA, Singapore, Dubai, or Sydney?
No. Those are market pages. They own how searchers behave in that country or city. International SEO owns how the site is split so those markets do not share one undifferentiated URL: which host you will maintain, how locale pages annotate each other, and whether you are targeting a language or a country. Open the locations hub when the job is one market.
Does hreflang improve rankings?
We do not sell that claim. Hreflang declares which URL is for which locale so the intended version can be selected. Ranking still depends on the document and competition in that locale. A one-way tag is not a contract. If A points at B, B must point at A.
Should we use a ccTLD or a folder?
That is an identity and operations choice, not a ranking law. A ccTLD is a separate property you must keep. A folder shares one host and needs a real document in each locale. We pick the model you can re-ship after a template change. An elegant ccTLD map that nobody can maintain is worse than folders with an honest contract.
How is this different from global SEO?
International SEO is architecture: hosts, return tags, language versus country. Global SEO is operations after those properties already exist: one backlog, who ships which market, and a stop on duplicate work. If the hosts and pairs are not decided, start here. If US, UK, and AE sites are already live and two teams are cloning pages, open global SEO.
Will international SEO put every locale into Google AI Overviews?
No. A correct pair can stop the wrong country showing in classic results, which also helps extractors pick the right document. That can support AI search and generative search. It does not buy a citation in Google AI Overviews (AIO) for each locale. If the HTML still names the US company on the UK URL, models will mix them up. That finding stays on the document, not on a citation product.
Second locale
Do you need a second locale that must not steal the first?
Tell us which hosts and folders already exist. We will say whether international SEO is the architecture, or whether a market page or global operations should go first.
- Host model first
- Return-tag contract
- Locales that must not collide
- No cloned city pack
Hosts, contract, distinguish, validate. Not a city pack.