Can you do SEO in languages your team does not speak?

The technical layer — hreflang, canonicals, routing, structured data, indexing — is language-independent and we handle it in any language. Content is different. We work natively in English, Italian and Albanian; beyond those we use native reviewers before anything publishes, and we insist on it, because we have seen first-hand what unreviewed machine-drafted copy looks like in a language nobody on the team reads.

Do you do local SEO — getting us into the map pack?

That is not our strength and we would rather say so. Local pack rankings are driven by a verified Google Business Profile, proximity and review volume, none of which we can engineer for you. Our advantage is the opposite case: international and multilingual search, where there is no local pack and the ranking factors are technical.

Do you also run paid advertising?

No. We run organic only — search and content. If you need paid media, keep your existing agency; we will build the attribution that finally tells you what they are producing. Paid traffic stops the day the budget stops, and running it well is a different discipline from ours.

How long before we see results?

Technical remediation is usually weeks and its effect can appear quickly, because fixing a broken hreflang cluster can release pages that were already written. New content in a new market compounds over months — early signals in one to three, meaningful movement after that. Anyone giving you a date for a ranking is guessing.

Can you fix our existing site or do we need a rebuild?

Almost always we fix what is there. Most international SEO defects are configuration and routing problems rather than architectural ones. If your platform genuinely cannot express correct hreflang or translated URLs we will tell you that plainly, along with what it would take to change — but we will not sell you a rebuild you do not need.

International & Multilingual SEO

Most multilingual SEO fails in the code, not the copy — duplicate canonicals, hreflang that does not reciprocate, translated pages sitting on English URLs. We are a software house that runs its own six-language programme, so we fix the layer that agencies can only file a ticket about.

Last updated: August 14, 2026

Start your project Get a free estimate

Where international SEO actually breaks

Almost every multilingual site we look at has the same handful of defects, and none of them are content problems. They are implementation problems that a content team cannot reach, which is why they survive years of SEO retainers.

Hreflang that does not reciprocate: page A points to B, B never points back, so Google discards the whole cluster
Every locale canonicalising to the English URL, which tells Google the translations are duplicates and should not rank
Translated content served on English slugs, so the URL itself carries no signal in the target language
One locale silently falling back to English mid-page — a server component that forgot which language it was rendering
A sitemap that lists locales the site does not actually serve, or omits the ones it does

Translation is not localisation

A translated page competes in a market where the phrasing, the buying question and the competitor set are all different. The keyword that carries the volume in one language frequently has no counterpart in another — sometimes the demand is real but phrased unrecognisably, and sometimes it genuinely does not exist and the honest answer is not to build the page.

Query research done per market, in-language, rather than translating an English keyword list
Pages aimed at how buyers in that market actually phrase the problem, which is rarely a literal translation
Markets where the demand is not there get told so — we would rather lose the page than sell you a translation with no audience
Native review before anything ships, because machine-drafted copy in a language nobody on the team reads is a liability
Per-market internal linking, so each language cluster supports itself instead of leaking authority to the English tree

What the programme covers

Run as an ongoing engagement rather than an audit you file and forget. The technical foundation comes first, because content published onto a broken hreflang implementation is money spent on pages Google will collapse into each other.

Technical foundation: hreflang, canonicals, translated URL routing, per-locale sitemaps, crawlability and Core Web Vitals
Query research per market against real volume and difficulty data, not a translated keyword list
Content clusters built to own a specific question, with the internal linking that makes them indexable
Structured data and AI-answer readiness, so pages are quotable by AI search as well as rankable
Automated index submission (IndexNow plus the Google Indexing API) and reporting from Search Console

Why a software house rather than an agency

The recurring pattern in multilingual SEO is a competent agency producing a correct audit that nobody can implement, because every finding lands in an engineering backlog behind the roadmap. We are the engineering team. The hreflang fix, the routing change, the canonical logic and the sitemap rewrite are our work, not a recommendation we hand you.

Findings get implemented, not filed — the same team writes the recommendation and the code
We work inside your codebase and your deployment process rather than through a plugin
Comfortable in Next.js, React and server-rendered stacks, where most i18n SEO bugs actually live
No dependency on an SEO plugin that a framework upgrade will break
If the honest answer is that your platform cannot do correct hreflang, we will tell you that too

The programme runs on this domain first

You do not have to take the methodology on trust — you are reading a page produced by it. This site serves six languages with reciprocal hreflang and translated URLs across roughly 380 indexed pages, carries structured data and AI-answer markup, and submits its own URLs to the search indexes automatically. All of it is inspectable from outside, and we will walk you through the parts that have not worked as well as the parts that have.

Six locales with reciprocal hreflang and genuinely translated URLs, not English slugs with a language prefix
Structured data across the money pages, with freshness signals carried in the markup
Automated submission to IndexNow and the Google Indexing API on a daily schedule
Reported on impressions, positions and enquiries from Search Console — first-party data, not an agency dashboard
What we will not do is show you someone else's case study: this is our own property, and we say so

How we work and what it costs

The technical remediation is a software engagement, priced from our EUR 35-55/hour band with a written estimate before anything starts. The ongoing programme is quoted separately and scoped to your markets and language count, because those are what actually drive the work. We will not put a monthly retainer number on a web page when we do not yet know how many languages you need.

Written estimate first, with the range and the assumptions stated
Technical remediation usually lands in weeks; it is bounded work with a definable end
Organic results compound over months, not weeks — anyone dating a ranking is guessing
Full CET overlap from Tirana, with engineers who work in English and Italian
You own everything we produce, and we can hand the programme to your team whenever you want it back

FAQ

Frequently Asked Questions

Can you do SEO in languages your team does not speak?
The technical layer — hreflang, canonicals, routing, structured data, indexing — is language-independent and we handle it in any language. Content is different. We work natively in English, Italian and Albanian; beyond those we use native reviewers before anything publishes, and we insist on it, because we have seen first-hand what unreviewed machine-drafted copy looks like in a language nobody on the team reads.
Do you do local SEO — getting us into the map pack?
That is not our strength and we would rather say so. Local pack rankings are driven by a verified Google Business Profile, proximity and review volume, none of which we can engineer for you. Our advantage is the opposite case: international and multilingual search, where there is no local pack and the ranking factors are technical.
Do you also run paid advertising?
No. We run organic only — search and content. If you need paid media, keep your existing agency; we will build the attribution that finally tells you what they are producing. Paid traffic stops the day the budget stops, and running it well is a different discipline from ours.
How much does it cost?
The technical remediation is sized from our EUR 35-55/hour band against your scope, with a written estimate and a clear range before anything starts. The ongoing programme is quoted separately, because its cost depends on how many markets and languages you are actually targeting. Neither has a list price we could honestly publish.
How long before we see results?
Technical remediation is usually weeks and its effect can appear quickly, because fixing a broken hreflang cluster can release pages that were already written. New content in a new market compounds over months — early signals in one to three, meaningful movement after that. Anyone giving you a date for a ranking is guessing.
Can you fix our existing site or do we need a rebuild?
Almost always we fix what is there. Most international SEO defects are configuration and routing problems rather than architectural ones. If your platform genuinely cannot express correct hreflang or translated URLs we will tell you that plainly, along with what it would take to change — but we will not sell you a rebuild you do not need.