A bilingual website isn't a translated website: a technical guide
December 2022, the last few days before Christmas. In my studio in Santa Maria Capua Vetere there was that typical buzz of the season: a festive mood that creeps into offices too at that time of year.
On my screen was Pasquale, a friend from Portici who'd moved to London a few years before. He was helping me weigh up the best options for setting up the new British company. Two shores in a single video-call window.
On 22 December 2022, Insight Adv Ltd was born.
Until a moment earlier, Insight was an Italian agency talking to Italy. From that moment it had to talk to the United Kingdom too, and to anyone arriving from abroad. A bilingual site was no longer an option. It was a necessity.
You don't build a bridge by hanging a "Welcome" sign above a "Benvenuti" sign. You dig foundations on both banks.
It wasn't the first time. In 2006 InsightAgency, the Italian creative agency where it all started, already had a site in four languages: Italian, English, French and Russian. HTML, Flash and CSS. A deliberate choice, for the time. Sixteen years later the technology under the bonnet was different, and the lesson stayed exactly the same: translating the text is the easy part.
The real work is done in the dark. Right-click, "Inspect", open the <head> of the page and read what's actually written there. There, where the reader never looks and Google spends its nights, it's decided whether your site speaks two languages or stammers in two.
In short. Six decisions separate a bilingual site that works from one that only seems to:
- the URL structure;
- hreflang, that is, the reciprocity pact between pages;
- the transcreation of the content;
- the design of the language selector;
- how you handle video;
- cookies, which in Italy and the UK follow different rules.
First, the right words: multilingual, multiregional, local
Google draws a precise distinction. A multilingual site offers content in more than one language. A multiregional site explicitly targets users in different countries. Mine is both: Italian for Italy, English for the United Kingdom and for anyone arriving from abroad.
In code, this distinction runs through language tags. My Italian pages declare <html lang="it-it" dir="ltr">, the English ones <html lang="en-gb" dir="ltr">. That's the right foundation. Language tags are case-insensitive: I write it-IT and en-GB purely out of convention.
The classic mistake is en-UK. The code for the United Kingdom in the international ISO standard is GB, and UK isn't the correct value. A tiny detail, but it's the giveaway that tells you whether whoever's had their hands on the code knows what they're doing.
The code, though, is only the container. The content has to reflect the market.
Take Berto. He's got a metalworking shop on the industrial estate between Santa Maria Capua Vetere and Capua, knocks back his short coffee in three sips and asks for a preventivo. Then take Bobby. He's got a craft brewery in Salford, orders his pint after five and asks for a quote. Same person, same need. Different words.
| Berto says | Bobby says | Why it isn't a translation |
|---|---|---|
| preventivo | quote (or estimate) | In the UK a "quote" is the document that commits you to a price |
| PMI (small and medium-sized enterprise) | SME or small business | "Small business" is the phrase used by the people who actually run one |
| P.IVA | VAT number | Same tax function, different system and different format |
| CAP and provincia | postcode and county | A postcode like EC1V 2NX pinpoints almost a single building |
That isn't translating. It's choosing.
Four languages in 2006, two in 2022
Let's get the facts straight. In 2006 InsightAgency launched with a static site in HTML, Flash and CSS, in Italian, English, French and Russian. It was the main site. Alongside it, a dynamic PHP site was growing, in Italian only: a side project, still evolving.
Then Flash was retired. Adobe ended support on 31 December 2020. I updated the site in HTML so it would work without Flash, but the energy went into the PHP site, which picked up speed until it was finished. At that point multilingual wasn't a priority. It got left behind, and in 2022 the bill arrived.
Russian, meanwhile, had never given me any trouble with characters. On a static site I could choose the encoding page by page. On a dynamic site with a single database, there's one choice for everything, and today it's called UTF-8: the encoding that represents every alphabet.
The point isn't nostalgia. It's the difference between a site you publish and one you maintain. On a static site, languages are pages that stay put. On a site that lives on articles, every extra language is a commitment that renews with every update.
I've written about how a brand learns to speak two languages in From the Caserta greenhouse to London. Here it's about technique, which is a different trade.
The architecture: where the two languages live
The three options (and one to avoid)
Where, physically, do the Italian and English versions live? Google Search Central's documentation sets out three options.
| Option | Example | What it offers | What it costs |
|---|---|---|---|
| Country-code top-level domain (ccTLD) | esempio.it and esempio.co.uk | Clear geographic signal, clean separation of the two sites | Double the cost and admin, domain requirements |
| Subdomain | it.esempio.com | Easy to separate | The URL alone doesn't tell you whether "it" is the language or the country |
| Subdirectory | esempio.com/it/ | One domain, simple to set up and maintain | Harder to keep the sites separate |
The fourth option, URL parameters such as ?lang=en, I mention only to dismiss it: Google doesn't recommend it.
My choice
The site lives on a single domain, .it, with /it/ and /en/ subdirectories. I also own .uk, .ltd.uk and .eu, which serve the same site, each at its own address, and .co.uk, which forwards to the .uk. To search engines they're copies: the canonical should keep them in check, and the clean fix would be a 301 redirect to the main domain.
The drawback is obvious: .it is a strong geographic signal for Italy, and the English-language audience is in the UK. I've got numbers to measure it. Since January, the UK has been the eleventh country by users: 470, or 1.74% of the total. The engagement rate is 9.38%, the average engagement time 2 seconds, and no conversions recorded. Those are warning numbers, not market numbers. The explanation is simpler than the domain: the site grows organically only, and the one bit of promotion goes through social channels, where the followers are mostly Italian, mostly on my own profiles. I'm not reaching the UK yet.
My position is this: the right structure is the one you can keep in order for years. A neglected national domain does more damage than a well-kept subdirectory.
The site root and the IP address trap
For years there was a fashionable practice: you read the IP address of whoever turns up and send them automatically to their language. Google advises against it. The reason is technical: its crawler mostly crawls from US addresses and doesn't set a preferred browser language. If you redirect based on location, Googlebot may never see one of the two versions.
The rule is simple: let the user choose, or show a selector page.
If I request insightadv.it/ without declaring any language, I land on /it: for anyone who doesn't state a preference, the site starts in Italian.
In the next few days I'll be working on a system that steers visitors according to their language, and now's the right time to write the rules before writing the code:
- Suggest, don't force. A discreet notice ("Would you like to read this page in English?") that readers can dismiss, not an automatic jump.
- Act on the root only. Anyone opening an explicit address,
/it/or/en/, stays put: if they clicked or pasted that link, they wanted that page. - Look at the browser language, not the IP address. An Italian in London reads in Italian. The language declared by the browser tells you more about the reader than the country they're connecting from.
- Remember the choice. If someone picks a language, the site doesn't ask again on every visit. How that choice is stored, and whether it needs consent, I'll check with a privacy consultant.
- Leave both routes open to search engines. The addresses for both languages stay reachable through plain links, without depending on any browser header.
When it's in production, I'll write about it here.
One URL, one language
Every version has its own stable address. No mixed pages, and slugs (the final part of the address) need translating: /it/blog/sito-bilingue and /en/blog/bilingual-website, not two pages sharing the same Italian slug. As you'll see in the post-mortem, my site doesn't manage this everywhere.
hreflang: the reciprocity pact
Let's try an experiment. Two phones. Berto, sitting at a little table in Piazza Adriano in Santa Maria Capua Vetere, is searching for an "agenzia creativa". Bobby, outside a pub in Salford, is searching for a creative agency. Without any declaration, Google has to guess which page to show to whom. Sometimes it guesses right. hreflang stops it guessing blindly.
hreflang is an annotation, invisible to readers, that tells search engines: this Italian address and this English address are the same page in different languages or regions.
The rules, from Google's documentation, are few and non-negotiable:
- each version lists itself and all the others;
- the set of links is identical on every version;
- the links go in the
<head>, or in the HTTP headers, or in the sitemap: pick just one and don't mix them.
An illustrative example, with made-up slugs:
<link rel="alternate" hreflang="it-IT" href="https://insightadv.it/it/blog/slug-italiano" />
<link rel="alternate" hreflang="en-GB" href="https://insightadv.it/en/blog/slug-inglese" />
<link rel="alternate" hreflang="x-default" href="https://insightadv.it/it/blog/slug-italiano" />
It's a dovetail joint. If one side doesn't hold, neither does the other.
What x-default really is
x-default is the value for all the languages you haven't listed, or for the selector page. It doesn't decide by country: it decides by what's missing. It's a signal, not an order, and it's recommended rather than mandatory.
My x-default points to the Italian page, the same URL as the it. The site was born in Italian and English was added later: it's a choice of history, not of strategy, and I'll be changing it shortly.
The rule I'd apply: the fallback should speak the language of the audience you want to reach outside your two main markets. For a site that also addresses Poland, Bulgaria, Romania and Ukraine, the natural fallback is English, or a selector.
The classic mistakes
- The non-reciprocal link. The Italian page points to the English one and the English doesn't answer back: Google ignores the pair.
en-UKinstead ofen-GB.- hreflang on pages excluded by the canonical. The canonical is the tag that says which URL is the "official" one.
- Mixed methods. A bit in the head and a bit in the sitemap.
- The lone missing self-reference. Every version must list itself too.
On the canonical, a blunt rule: every language version has its own canonical pointing to itself. The English page must never point to the Italian one.
lang isn't hreflang
The lang attribute you've seen in the <html> isn't used by Google to decide who to show the page to: the documentation is clear on this. It's for people reading with a screen reader, for automatic hyphenation, for spellcheckers. It's a piece of accessibility, and I've written about it in Web accessibility 2026.
How to check
Right-click, "View source". Or, from the terminal:
curl -s https://tuosito.it/it/pagina | grep -i hreflang
Never trust a plugin that tells you "all OK". Read the code.
Joomla and Falang: what the CMS does and what it doesn't
The CMS (the system that manages the content) behind insightadv.it is Joomla, with EasyBlog for the blog. Joomla has a native multilingual system, built from plugins and associations between content items, but many sites rely on a third-party component. I use Falang: the source says so, where the language selector is the mod_falang module. Falang translates content in the database and handles language switching.
Anyone using the native system will find two known pitfalls on Joomla's public tracker: the canonical that vanishes when alternate meta tags are enabled (issue 42128) and the hreflang that goes missing if the associated item is in the bin (issue 13359). With Falang the behaviour may differ, and I haven't checked.
I have checked my own, though. I opened the source of an Italian page, the Corso di fotografia category, and then its English twin.
What works:
- three hreflang tags (
it,x-default,en) and the page declaring itself; - a canonical pointing at the page itself, in both the Italian and the English version;
- the addresses of translated posts, such as
/en/blog/the-different-typologies-of-digital-cameras-and-not-only.
The disappearing-canonical bug isn't present here.
What doesn't add up:
- The English hreflang is
en, noten-GB. It's valid and applies to anyone reading English, and for a site that also speaks to Poland, Bulgaria, Romania and Ukraine it's even coherent. But the site declaresen-gbin thehtmlandenin the hreflang: two levels of precision, and a choice I'd have to explain. - The English slugs of categories and pages have stayed Italian. The category's twin is
/en/blog/categories/corso-di-fotografia, and the menu has/en/servizi/advertisingand/en/l-agenzia/the-our-method. Posts are translated, categories aren't: in this article I say slugs should be translated, and for half the site I haven't done it. - Strings in the wrong language. On the Italian page, the social preview (
og:description) says "There is no description for this category.". On the English page, the meta description and the title suffix ("Il blog della Insight Adv Ltd") are in Italian, and the forms still say "Nome utente", "Password", "Ricordami" and "voti". - The selector uses flags. Two little flags with the codes IT and EN beside them: the opposite of what I argue for in the section on the selector.
- The logo and the breadcrumb "Home" point to the root, not to
/en/: from an English page, one click on the logo goes throughinsightadv.it/, which, with no preferences, leads to Italian.
These are shortcomings I'm aware of, and I'm getting ready to fix them. I'm writing them down here because an article that preaches rigour can't hide its own flaws.
The six checks I run:
- the source of the home page;
- the source of a blog post;
- the language selector: does it generate clean URLs?
- the canonical: does it point to itself?
- the
langattribute in the<html>; - how the site behaves if a translation is missing.
The language selector
The selector isn't decoration. It's the light switch.
I'm taking an editorial position, not citing a rule of law: no flags. Flags represent countries, not languages. The English you're reading doesn't belong to a single country, and a Swiss from the canton of Ticino speaks Italian without flying the tricolour. My selector, as you saw in the post-mortem, still uses flags: that's a debt I'm declaring.
The model is the GOV.UK design system. The Language navigation component writes the name of the language in the language itself ("Cymraeg", not "Welsh"), with lang and hreflang attributes, and makes clear it translates nothing: content has to be created and maintained for every language. The pattern for switching to Welsh in the DWP design system adds another rule: whoever changes language stays on the same page of the service, and doesn't start again from the beginning.
And if the page has no twin? The selector takes you to the home page of the other language. Never to a 404. With a site that's 100% translated the case is rare, but it does exist, for instance when a translation is still in draft.
Transcreate, don't translate

My site isn't translated word for word. Every piece of content, blog included, exists in Italian and in English, with the copy in natural British English. Videos are the exception.
The method is this. I write the article in Italian, because it's the language that comes naturally to me. The article is then translated with AI, and I check the translation myself. If I've got a doubt, I pass the text to my collaborators in London and to other language tools to make sure it's all correct. In each language I'm after naturalness.
Three pairs from the blog, with what changes:
| Italian | Published English | What changes |
|---|---|---|
| Le foto di tua nonna si stanno cancellando | Your Grandmother's photos are fading away | "Cancellando" doesn't become being deleted: it becomes fading away, which is what really happens to prints |
| Il rientro si vince ad agosto | You win your return in August | The passive gives way to an active sentence, addressed to the reader |
| La storia d'amore che non fa vergogna | The love story that doesn't embarrass anyone | The subject of the embarrassment, which stays implicit in Italian, becomes explicit |
It hasn't always gone this way. In the English title of the article on the neighbourhood influencer, from 22 September 2026, it says neighborhood, American-style. On a site declaring en-gb it should be neighbourhood. And in the menu there's "Write us", a calque of "Scrivici": a Brit would write "Contact us" or "Get in touch". The recent blog texts have been rewritten. The older interface strings haven't.
A word of caution. London slang makes the tone feel natural to an audience in Shoreditch or Hackney. A client in Manchester or Salford might hear it as a parody. It needs deciding on purpose, not by reflex.
It's like parmigiana in London. You don't carry the recipe in your suitcase and repeat it identically. You remake it with the ingredients you find at Borough Market, and it still has to be parmigiana.
Numbers and currencies
In Italy you write 1.234,56, in the UK 1,234.56. The euro often goes after the figure (100 €), the pound always goes before (£100).
In the price table in How much does a website really cost, the Italian version writes £3.000, with a full stop, and the English version £3,000, with a comma. The cell changes along with the language. Nobody notices while it's right, and everybody notices when it's wrong.
Dates, spelling, forms
Italy and the UK share day-before-month, unlike the United States. The difference lies in the month names and in the risk of slipping into American English (colour and color, organisation and organization): you've seen it with neighborhood. An Italian form asks for provincia and CAP, an English one for county and postcode. The dialling code goes from +39 to +44. If I clone a form without transcreating it, the customer gives up at the moment of filling it in.
Typography
Fonts need to have all the glyphs: à, è, é, ì, ò, ù for Italian, the £ symbol for British English. In my <head> the fonts I load today (Bricolage Grotesque and Merriweather) are declared by character subsets: Italian accents, £ and € sit in the latin subset, so the check passed. I've written about fonts in Web Typography and in variable fonts. Quotation marks change too: «guillemets» in Italian, “double quotes” in English. CSS automatic hyphenation (hyphens: auto) works according to the declared language, so without a correct lang it doesn't hyphenate.
Then there's space. Italian headlines tend to be longer than their English equivalents. A hero section that holds with three words in English can spill onto two lines in Italian. I've written about the structure of the first screen in The first screen always lies.
Images and social
Text inside images has to be duplicated, and alt attributes translated and thought through for each language's search. For social, the Open Graph declaration og:locale has to switch from it_IT to en_GB.
Video isn't bilingual: how to declare it
Video content is the only part of the site that doesn't exist in both languages, so here the job is to declare it and make it accessible. I've written about the method for reusing one video across several pieces of content in One video, ten pieces of content.
On the technical side you need subtitles in the HTML5 player, with the <track kind="subtitles" srclang="en"> element. On the structured-data side, schema.org provides the inLanguage property to declare the language of the audio.
On the accessibility side, subtitles for pre-recorded video are a Level A requirement of the WCAG (Web Content Accessibility Guidelines, the international accessibility guidelines), success criterion 1.2.2. And if you embed an Italian video in an English page, the language of that part has to be declared with lang (criterion 3.1.2).
An Italian video doesn't break the hreflang pair: the pages are equivalent. But you need a clear line to warn English readers: Video in Italian, with English subtitles. A video's language is a fact. The flaw is not declaring it.
Cookies and privacy: two laws, one site
This is where the code ends and the law begins. Caveat: I'm not a lawyer, and this section needs checking with a privacy consultant.
The data controller is Insight Adv Ltd, a British company registered with the ICO, the UK data protection authority, as the footer states. Two regimes on the same site.
In Italy what matters is the Garante per la protezione dei dati personali, the Italian data protection authority. Its cookie guidelines (decision no. 231 of 10 June 2021, Official Gazette of 9 July 2021, in force from January 2022) set four points. Scrolling the page isn't consent. The cookie wall, meaning "accept or you can't come in", isn't allowed. The closing "X" on the banner counts as a refusal. After a refusal the banner mustn't be shown again for six months, with some exceptions. For analytics, the same guidelines allow, under precise conditions, statistical cookies without consent: the exact conditions need reading in the text.
In the UK cookies are governed by PECR (Privacy and Electronic Communications Regulations) and the UK version of GDPR, the data protection regulation. The Data (Use and Access) Act 2025 changed PECR, and according to the sources I've consulted the changes have been in force since 5 February 2026. The novelty is an exception for statistics, but it's a narrow one: the data has to be aggregated and used only to improve the service, the provider has to act on your behalf without using the data for its own purposes, and you need clear information and a simple way to object. Advertising, profiling and cross-site tracking still require consent. The analyses I've read suggest that tools like Google Analytics are unlikely to fall within the exception. The ICO published its definitive guidance in May 2026: the source to read is ico.org.uk.
The comparison is this. Italy and the UK both allow statistical cookies without consent, on different and restrictive conditions. Neither is a free pass for third-party analytics.
The banner has to speak the language of the page. As for behaviour, you've got two routes: a single standard, the strictest, for everyone, or different behaviour per country. Mind the distinction: varying the banner by country is one thing, redirecting by IP is another. The first doesn't stop Google seeing either version. The second does.
For the newsletter, the form and the privacy notice have to be in the subscriber's language. My newsletter form is run by SendFox, an external service: the language and the form of the consent depend on what the service lets me write. Double consent is good practice, not a legal obligation. On banners and design traps, I've written in The trick that's now a crime, in The cookie is dead and, on the 2021 rules, in New cookie guidelines.
How to keep a fully translated site on its feet
Translating everything has an advantage. For Google, localised versions only count as duplicates if the main content stays in the original language, so if you translate the lot you don't run that risk. And the documentation advises blocking automatically translated, uncurated pages with robots.txt: a bad translation is a debt.
The cost is something else. Every article has two versions to write, link and publish. Publishing, at my end, is almost instant: once the Italian article and the translation are done, I upload them to the site. The hard case is a different one: correcting an article that's already out. If you're not careful, that's where one of the two versions gets left behind.
Even the people who do it best don't translate everything. The Government Digital Service at GOV.UK prioritises Welsh translations according to user needs. I choose to translate everything, and I know that means paying for every update twice.
My yardstick is this: a bilingual site isn't measured by how many pages it has on launch day, but by how many are still aligned a year later.
Two examples from the wider world
The model: GOV.UK. I've already cited it for the selector, but the point here is a different one. The Government Digital Service didn't build a translated site: it built a site designed for all its users, and Welsh is part of that. The guidance refers to WCAG criteria 3.1.1 and 3.1.2 on the language attribute and prioritises translations according to the real needs of readers. That's the difference between translating and localising.
The warning: Italia.it, 2007. The portal that was meant to present Italy to the world was launched in February 2007. €45 million had been allocated, and the actual spend is disputed in the sources, somewhere between roughly one and roughly seven million. It was shut down in January 2008. According to accounts at the time, it didn't comply with the Stanca Law, the Italian rule on the accessibility of public websites. AIAP, the association of Italian graphic designers, launched a petition against the logo and pointed out that the slogan "L'Italia lascia il segno" closely copied those of Spanish and Portuguese campaigns. Speaking to the world doesn't mean copying the way the world presents itself. And a public site that can't be read with a screen reader doesn't speak to everyone.
The checklist
Before you say a bilingual project is finished:
- URL. One language per address, translated slugs, no IP redirects.
- hreflang. Present on every version, reciprocal, identical, with self-reference.
- x-default. Chosen on purpose, not out of inertia.
- Canonical. Every version points to itself.
lang. Correct on the page and on any parts in another language.- Selector. Language names, no flags, never a 404.
- Copy. Transcreated, not literal, with the same register in every version.
- Strings. Meta description, title, forms and social previews, all in the page's language.
- Numbers, currencies, forms. Local formats, postcode and county included.
- Typography. Glyphs, quotation marks, headlines that don't spill over.
- Video and cookies. Language declared, subtitles, banner in the page's language.
- Source. Opened and properly read, at least once a month.
Conclusion
Back to that December: the studio in Santa Maria Capua Vetere, the video call with Pasquale, the 22nd of December when Insight Adv Ltd was born. A bilingual site had become a necessity, and a bridge isn't built with a sign, but with foundations on both banks. Today I know something else too: foundations aren't dug once, they're checked every week. And they're checked from the source, not the browser.
The shortcomings I've listed are these, in order: the English hreflang without a region and the x-default on Italian; Italian slugs in the English categories and menu; strings in the wrong language; the selector with flags; the aliases that duplicate the site; the logo that points to the root; the missing og:locale; an American-style title and a calque in the menu. These are shortcomings I'm aware of, and I'm getting ready to fix them. When I have, I'll write about it here.
A translated site speaks two languages with one voice. A localised site speaks to two different people. The first costs less, and loses in both markets.
I build websites for a living, which is why I know what an error nobody sees costs. If you've got a site in two languages, open the source tonight. If something doesn't add up, drop me a line.
Sources
- Google Search Central, Tell Google about localized versions of your page
- Google Search Central, Managing multi-regional and multilingual sites
- GOV.UK Design System, Language navigation
- DWP Design System, Toggle to Welsh
- GOV.UK, Welsh language on GOV.UK
- W3C, WCAG 2.2
- Adobe, announcement of the end of support for Flash Player (31 December 2020)
- Garante per la protezione dei dati personali, Guidelines on cookies and other tracking tools, decision no. 231 of 10 June 2021 (Official Gazette no. 163 of 9 July 2021)
- Information Commissioner's Office (ICO), guidance on storage and access technologies, 2026, ico.org.uk
- PMI.it, The Italia.it portal is reborn
- 01net, The great Italia.it flop
Frequently asked questions
What is hreflang and what's it for?
hreflang is an annotation that tells search engines that two or more addresses are the same page in different languages or regions, for example it-IT and en-GB. It's there so each reader is shown the right version. It only works if it's reciprocal: each version lists itself and all the others, with the same set of links on every page.
What's the difference between hreflang and the lang attribute?
The lang attribute declares the language of a page or part of one, and it's used by screen readers, automatic hyphenation and spellcheckers. According to its documentation, Google doesn't use it to decide who to show the page to. hreflang, on the other hand, links equivalent versions together and guides search engines. A well-built bilingual site uses both.
Subdirectories, subdomains or separate domains per country?
It depends on how much you can maintain. A country domain (for example .co.uk) gives the clearest geographic signal but costs more to manage. A subdomain separates the versions well. The subdirectory (/it/, /en/) is the simplest to set up and keep tidy, but separates the versions less. URL parameters, like ?lang=en, aren't recommended by Google.
Should I redirect visitors based on country or browser language?
No. Google advises against automatically redirecting from one language version to another based on perceived language or location, because it can stop search engines from seeing one of the versions. It's better to let the user choose with a selector, or to show a choice page.
How do I design a language selector that works on smartphones too?
Write the name of each language in the language itself (Italiano, English), with no flags, because flags represent countries, not languages. Keep it visible and within thumb's reach, and declare lang and hreflang on every entry. Anyone switching language should stay on the same page, not be sent back to the home page. If the twin page doesn't exist, the selector takes you to the home page of the other language, never to a 404 error.
When is a bilingual site NOT worth having?
When you can't maintain it. Every extra language means translating, reviewing, linking and updating every piece of content twice, for ever. A site with half its pages translated, or machine-translated without review, does more harm than a well-made single-language site. Before you start, ask yourself who'll be updating the English version in a year's time.
What tools can I use to check that hreflang and canonical are correct?
The most reliable check is reading the code: right-click, "View source", and look for the hreflang and canonical tags in the <head>. From the terminal you can use curl -s URL | grep -i hreflang. For checking lots of pages at once, there are SEO crawlers. Don't trust a plugin that just says "all OK": check that the links are reciprocal and that each version has its own canonical pointing to itself.
By accepting you will be accessing a service provided by a third-party external to https://insightadv.it/
IT
EN 



















































Comments