Hreflang Tags Explained: How to Set Them Up Correctly to Avoid Duplicate Content Issues
2026-06-30
If you've ever Googled your own site and seen duplicate pages competing against each other in search results, hreflang tags are probably the fix you need. For SMB owners expanding into new markets, getting this right isn't optional — Google needs clear signals to serve the correct language version of your site to the right audience. The good news? Learning how to set up hreflang tags is simpler than most developers make it sound, and you don't need to hire an agency or buy expensive software to do it correctly.
What Are Hreflang Tags and Why Do They Matter?
Hreflang tags are small snippets of HTML that tell search engines like Google which version of a page to show based on a user's language and location. Without them, Google might serve your Spanish-speaking visitors your English homepage, or worse, treat your translated pages as duplicate content and penalize your rankings.
Here's what a basic hreflang tag looks like:
<link rel="alternate" hreflang="en" href="https://yoursite.com/en/" />
<link rel="alternate" hreflang="es" href="https://yoursite.com/es/" />
<link rel="alternate" hreflang="x-default" href="https://yoursite.com/" />
The x-default tag is important — it tells Google which page to show when no other language matches the visitor's region. Always include it.
Who Actually Needs Hreflang Tags?
If your site exists in only one language, you can skip this for now. But if you're running:
- An e-commerce store shipping to multiple countries
- A SaaS product with a translated landing page for European markets
- A service business serving both English and Spanish speakers in the US
…then you need hreflang tags. Without them, you're leaving both traffic and revenue on the table.
The Most Common Hreflang Mistakes (and How to Avoid Them)
Before covering how to set up hreflang tags correctly, it helps to know what goes wrong. These are the mistakes that cause duplicate content issues and tank rankings.
Mistake 1: One-Way References
Hreflang tags must be reciprocal. If your English page references your Spanish page, your Spanish page must reference your English page back. Google ignores one-sided implementations.
Wrong: Only adding hreflang tags to your English page.
Right: Every language version references every other language version, including itself.
Mistake 2: Wrong Language Codes
Use ISO 639-1 language codes (en, es, fr, de) and ISO 3166-1 alpha-2 country codes when targeting a specific region (en-US, en-GB, es-MX). A typo like eng instead of en means Google ignores the tag entirely.
Mistake 3: Forgetting Self-Referencing Tags
Each page should include an hreflang tag pointing to itself. It sounds redundant, but Google uses it to confirm the implementation is intentional.
Mistake 4: Inconsistent URLs
Use the full canonical URL, including https:// and trailing slashes if you use them elsewhere. Mixing https://yoursite.com/es and https://yoursite.com/es/ in the same implementation confuses crawlers.
How to Set Up Hreflang Tags: Three Methods
There are three ways to implement hreflang tags: in the HTML <head>, in your XML sitemap, or via HTTP headers (for non-HTML files like PDFs). For most SMB websites, the <head> method is the most practical.
Method 1: HTML Head Tags
Add the following block to the <head> section of every page in every language version:
<head>
<!-- Your other head tags -->
<link rel="alternate" hreflang="en" href="https://yoursite.com/en/" />
<link rel="alternate" hreflang="fr" href="https://yoursite.com/fr/" />
<link rel="alternate" hreflang="de" href="https://yoursite.com/de/" />
<link rel="alternate" hreflang="x-default" href="https://yoursite.com/" />
</head>
Remember: this block needs to appear on all three language pages, not just one.
Method 2: XML Sitemap
If you have a large site with many pages, managing hreflang tags in the HTML of every page becomes unwieldy. Adding them to your sitemap is cleaner at scale:
<url>
<loc>https://yoursite.com/en/</loc>
<xhtml:link rel="alternate" hreflang="en" href="https://yoursite.com/en/"/>
<xhtml:link rel="alternate" hreflang="fr" href="https://yoursite.com/fr/"/>
<xhtml:link rel="alternate" hreflang="x-default" href="https://yoursite.com/"/>
</url>
This approach keeps your HTML cleaner but requires your sitemap to be accurate and regularly updated.
Method 3: The Practical Reality for Most SMBs
Here's the honest truth: manually managing hreflang tags across dozens of pages is tedious and error-prone. One wrong URL, one missed reciprocal tag, and your SEO signals fall apart. This is exactly why many business owners either avoid international SEO altogether or overpay for tools that handle it automatically.
Why Most Translation Tools Overcomplicate This
If you've looked into multilingual website tools before, you've probably encountered Weglot. It's a capable tool, but at $15–$490/month depending on word count and languages, it's priced for enterprise budgets, not small businesses testing a new market.
Other solutions require developer time, plugin configurations, and ongoing maintenance just to keep hreflang tags accurate as your site changes.
The reality is that how to set up hreflang tags should not require a monthly enterprise subscription or a developer retainer.
The 90-Second Alternative
SiteDialect handles hreflang tag implementation automatically. You add one script tag to your site — that's it. No plugin configuration, no sitemap editing, no cross-referencing language codes.
<script src="https://cdn.sitedialect.com/loader.js" data-site-id="YOUR_SITE_ID"></script>
That single line generates correct, reciprocal hreflang tags across all your language versions, updates them automatically when you add new pages, and includes the x-default tag without you having to remember.
It also handles the actual translation, language detection, and switcher UI — everything a growing business needs to go multilingual without the overhead.
What You Get Versus Weglot
| Feature | Weglot | SiteDialect |
|---|---|---|
| Hreflang automation | ✅ | ✅ |
| Translation included | ✅ | ✅ |
| Starting price | $15/mo | $5.99/mo |
| Setup time | 10–30 min | 90 seconds |
| Developer needed | Sometimes | No |
Quick Hreflang Audit Checklist
Before you go live with any multilingual implementation, run through this checklist:
- [ ] Every language version references every other version
- [ ] Every page includes a self-referencing hreflang tag
- [ ] The
x-defaulttag is present on all pages - [ ] Language codes use correct ISO 639-1 format
- [ ] Country codes (if used) are correct ISO 3166-1 alpha-2
- [ ] All URLs are full canonical URLs with consistent formatting
- [ ] No hreflang tags are pointing to 301 redirects or 404 pages
You can also use Google Search Console's International Targeting report to catch errors after implementation.
The Bottom Line
Getting hreflang tags right is one of the highest-leverage things you can do for international SEO. Done correctly, they eliminate duplicate content issues and ensure Google serves the right page to the right audience. Done poorly — or skipped entirely — they cost you rankings in the markets you're trying to reach.
The manual approach works if you have time, developer resources, and a static site that rarely changes. For everyone else, automation is the smarter path.
Add multilingual support to your site in 90 seconds with SiteDialect. Starting at $5.99/mo.