Hreflang Tags for SaaS Websites
Implement hreflang tags for your SaaS marketing site. Target international markets without cannibalizing your own pages in search.
You launched a French version of your marketing site. Translated homepage, pricing page, feature pages. You set up the subdirectory structure. You told everyone you're targeting France now.
Three months later, you check the rankings. Your English homepage is ranking for French-language searches. Your French homepage is ranking for nothing in particular. Your English and French pricing pages are both trying to rank for the same keywords in the same market.
You've invested in localization and it's actively working against you.
What's happening
When you create multiple versions of your marketing site for different languages, Google has to decide which version to show to which user. Without hreflang, it relies on content signals, backlink profiles, and guesswork. The result is almost always that your original-language pages dominate -- they have history, backlinks, and authority -- while your localized pages struggle to get any traction.
Worse, your language variants start competing with each other. Your English pricing page and your German pricing page are both optimized for "SaaS pricing" related queries. Without hreflang grouping them as intentional variants for different audiences, Google sees two competing pages and picks one. Usually the English one, for every market.
Hreflang fixes this by telling Google exactly which page is for which audience. Your French pricing page is for French-speaking users. Your English pricing page is for English-speaking users. They're not competing -- they're complementary.
SaaS-specific hreflang challenges
SaaS marketing sites have a few properties that make hreflang trickier than a typical brochure site.
You likely have a marketing site, a docs site, and possibly a separate app subdomain. These may or may not all have internationalized versions. The hreflang structure needs to reflect what actually exists -- you can't hreflang pages that don't have translations, and you shouldn't point hreflang tags at your app's dashboard just because it's on the same domain.
You also have high-value pages where getting this right actually matters: pricing, feature comparisons, landing pages for specific use cases. These are the pages where ranking in the right language market directly affects trial signups.
Generate hreflang for marketing site page sets
Map your homepage, pricing, features, and landing pages to their language variants. Generate the complete tag sets for each cluster. Clean output, no guessing.
Validate against cannibalization
The validator checks that your language variants are properly grouped, not competing. Missing hreflang is what causes English pages to rank everywhere and localized pages to rank nowhere.
Handle partial internationalization correctly
If your docs are only in English but your marketing site is multilingual, the generator helps you scope hreflang correctly -- only on pages that actually have language variants.
x-default for language selection flows
Many SaaS sites detect language from browser settings or ask users to choose. x-default tells Google which page to show before language preference is known. The generator includes it in every tag set.
Correct codes for every language market
ISO 639-1 language codes, ISO 3166-1 region codes, built-in validation. No pt-BR written as pt_BR. No zh-TW accidentally rendered as zh-tw. The codes are enforced.
Stop your language variants from competing with each other
Generate validated hreflang for your SaaS marketing site. Free.
The pages that matter most for SaaS
Not every page on your marketing site needs the same level of hreflang attention. But these do:
Pricing pages -- If you have region-specific pricing (EUR for Europe, GBP for UK, local currencies elsewhere), hreflang ensures the right pricing page appears in the right market's search results. This is directly tied to conversion.
High-intent landing pages -- Feature pages, use case pages, and comparison pages that you're actively trying to rank. These are the pages where language targeting matters most.
Homepage -- The canonical entry point to your brand in each market. Getting this one right influences how Google understands your entire site structure.
Blog and resource content -- Lower priority than the above, but if you're translating content for SEO purposes, it still needs hreflang to function correctly.
Implementation for SaaS sites
Audit what you actually have translated
List every page that has a translated version. Don't assume -- check the CMS or ask the team. Hreflang tags pointing to untranslated or placeholder pages cause more harm than having no hreflang at all.
Generate tag sets for high-value pages first
Start with pricing, homepage, and key feature pages. Generate the complete hreflang tag sets -- including self-references, all language variants, and x-default.
Implement in your CMS head template
Most SaaS marketing sites use a CMS (Webflow, WordPress, Contentful, custom Next.js). The hreflang tags go in the page <head>. If your CMS supports per-page head injection or a global template, that's where they go.
Validate the live implementation
After publishing, run the validator against your live pages. Confirm the tags are rendering in the HTML, the URLs return 200 status codes, and the return links are present on all language variants.
Approaches compared
| Approach | Setup effort | Risk of errors | Handles growth? |
|---|---|---|---|
| Write hreflang by hand | High | High | No |
| CMS plugin with auto-generation | Low | Medium -- hard to audit | Partial |
| Developer implements from spec | Medium | Medium -- one template error = all pages | Partial |
| Generate + validate with Hreflang Generator | Low | Low -- validated output | Yes |
The plugin route is tempting because it feels automatic. But automatic doesn't mean correct -- and plugins often generate subtly wrong hreflang (incorrect codes, missing return links on some page types) that you'd only catch with a proper validator.
Free
$0
- Up to 3 items
- Email alerts
- Basic support
Pro
$9/month
- Unlimited items
- Email + Slack alerts
- Priority support
- API access
Getting started
List your translated pages and their URLs
Collect the URL for each language variant of each page you've translated. This is your source data.
Generate hreflang tags for each page cluster
Enter the URL sets into the generator and produce the complete tag sets, ready to implement.
Implement in your marketing site head template
Place the tags in your CMS head template or have your developer add them to the page component.
Validate and monitor
Run the validator post-launch. Add hreflang validation to your QA checklist whenever you add new translated pages or restructure URLs.
Related Articles
Part of Boring Tools -- boring tools for boring jobs.
Generate perfect hreflang tags
Create and validate hreflang markup for your multilingual site. Free.