Entity and Semantic SEO
Multilingual and hreflang
Within Entity and Semantic SEO, this is the piece that serve several markets without the versions cannibalising each other.
What is meant by multilingual and hreflang?
Serve several markets without the versions cannibalising each other. In practice that means auditing current language and region targeting for conflicts and gaps, and then the harder half: implementing hreflang with correct reciprocal annotation and a self-reference.
Why this work exists
It is the first thing a competent competitor will have done, and the last thing most briefs mention.
Within Entity and Semantic SEO this is the item with the clearest cause and effect, which is why it is scoped on its own.
The nearest piece of work to it is making the service list the same on the site, the listings and the invoices. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
It is right when the exceptions are written down rather than remembered.
The gap between that and where most accounts start is why this is scoped as multilingual and hreflang rather than as a line inside something larger. Finding the gaps where the site asserts expertise it never demonstrates is the usual second step once it is in place.
When this is the right work
The diagnostic signs:
- The wrong country’s version ranks in a market you target
- Translated pages are canonicalised to the English original
- Hreflang exists but is missing return links
If none of those is true, something else is probably the constraint, and the Entity and Semantic SEO overview maps the alternatives. The usual neighbours are connecting case studies to the services they actually evidence and writing the definitional page the whole cluster can point at.
What the work covers
The work itself:
- Auditing current language and region targeting for conflicts and gaps. Straightforward in principle; the detail is where it stops being quick.
- Implementing hreflang with correct reciprocal annotation and a self-reference. Usually scoped at half the size it turns out to be.
- Deciding structure by market, then keeping canonical and hreflang consistent. Slow, unglamorous, and the reason the rest holds up.
- Testing which version each market is actually served, which clients tend to want evidence for, so it is documented as it goes.
How it runs
It runs in three passes. The order is not interchangeable.
Agreeing the measure
The number this will be judged on is fixed before the work starts. Agreeing it afterwards is how both sides end up disappointed.
Finding the constraint
Most of the available gain sits in one or two places. The first job is working out which, rather than improving everything by a little.
Working in public
Decisions get written down where the client can see them as they are made, so nothing arrives as a surprise in a monthly report.
What each part runs into
Each part meets a different obstacle depending on the market it is done in:
- Auditing current language and region targeting for conflicts and gaps, where a Chandigarh engagement contends with a measurement baseline that was never taken
- Implementing hreflang with correct reciprocal annotation and a self-reference – working in Manchester this means accounting for a language mix the content has to match rather than assume
- Deciding structure by market, then keeping canonical and hreflang consistent, and in Chicago the constraint on it is an enquiry path that runs through a messaging app rather than a form
- Testing which version each market is actually served, harder in Vancouver because of a catchment smaller than the ambition on the website
The avoidable version of this
Canonicalising a translation to the source-language page. It tells the system the translation is a duplicate and should not be indexed, which is the opposite of what was intended.
The reason it matters is that the failure is invisible from the report: the activity happened, the number did not move, and the conclusion drawn is usually the wrong one.
How it is measured
Correct version served per target market, and indexation of each language version. That is what gets reported, and it is deliberately narrow enough to move within the engagement.
Where the figure is estimated rather than counted, it says so on the report.
What you end up with
The concrete artefact is valid reciprocal hreflang across all versions, with structure and canonical decisions documented per market.
Handed over with the working, not only the conclusion.
How it differs by sector
The brief changes with the sector, not just the emphasis:
- Home and trade services brings its own limit: emergency intent, service-area geography, and a phone that has to be answered.
- B2B services, constrained by the fact that a buying committee, a long cycle, and attribution that has to survive both.
- SaaS and technology: Product-led companies where the buyer self-educates and the trial is the sales call. so this work has to account for that before anything else.
The industry pages carry the rest of that detail. Home and trade services and B2B services are the two where this piece of work most often decides the outcome.
Common questions
Does hreflang need to be reciprocal?
Yes. Every page in a set must reference every other page in the set, including itself, and the references must agree. A one-way annotation is ignored, which is the most common reason a correctly-intentioned implementation does nothing at all.
Should translated content be on a subdomain, subdirectory or separate domain?
Subdirectories are the usual answer, because they inherit the domain’s existing authority and are simplest to maintain. Separate country domains make sense where there is a genuine local entity, local hosting requirements or a brand that differs by market. Subdomains sit awkwardly between the two and are rarely the best of either.
What if this is not our problem?
Then we say so. The signals on this page are the honest filter, and work sold against the wrong diagnosis wastes a quarter. How much should SEO cost? is the part that scales. How do we rank in the map pack? is the part that never will.
What could go wrong with this work?
The usual risk is acting on a finding before it is solid. The diagnostic phase exists to avoid that, and where the data is too thin to be conclusive we will say so rather than proceed. If this is the part you came for, International SEO goes further into it, and Keyword cannibalisation covers what sits either side.
Will we speak to the person doing the work?
Yes. The person who diagnoses multilingual and hreflang is the person who does it and the person on the review call. Handing a finding to somebody else to execute is where most of the value leaks. If this is already in place, Marketplace Marketing for B2B services and Paid Social and Meta Ads for B2B services are the next two things to fix.
Ask about multilingual and hreflang
Say what the current setup looks like. We will say what we would change first and what we would leave alone.
Get a view you can act on this month
Give us the context and we will give you the order of work, including the parts you can do yourself.