International SEO checklist: do you need hreflang? (2026)

You need hreflang only when you publish two or more versions of the same page for different languages or countries. The classic case: Australian and US pages in English. If you run one English site for both markets, you don't need hreflang, and adding it won't help. Hreflang is a tag that tells Google which version of a page to show in which language or country. It sorts versions you already have. It won't make one page rank in a new market.

I'm Brenden House. I run Searchmaxxed, an SEO and AI SEO agency, and international SEO is one of the services we sell.

In summary

Most companies selling into Australia and the US need hreflang only once they split their site by market.

• Hreflang only works in pairs. Each version has to list itself and every other version, or Google can ignore the tags.
• Google treats .io and .ai as generic domains, so a SaaS company on either can't rely on its domain to target a country.
• Large sites get hreflang wrong in predictable ways, from wrong country codes to market versions that never name each other.
• Hreflang fixes which version shows, while ranking in each market still takes its own pages, proof and links.

Do I need hreflang on my website?

You need hreflang if the same page exists in more than one version, split by language, country or both. Google's own guide lists three cases: a translated template around one-language content, small regional variations in one language, and fully translated content. If none of those fit your site, skip it.

Google's guide to localised versions of a page is direct. "If you have multiple versions of a page for different languages or regions, tell Google about these different variations". The same guide adds that Google "might still find alternate language versions of your page" without tags. It still calls explicit tags "usually best".

Here's the decision:

We don't run hreflang on searchmaxxed.com. It's one English site for every market. Our own technical audit in August 2026 listed it as "absent and probably correct for a single-language site". Most single-market companies are in the same spot.

What is hreflang, in plain words?

Hreflang is a line of code that tells Google "this page has versions for other languages or countries, and here they are". Google uses it to swap in the right version for the searcher. It won't detect the page's language from it, or rank the page higher.

The terms you'll meet:

• Hreflang is an attribute that maps a page to its language and country versions.
• Language code is the first part of the value, in ISO 639-1 format, such as en for English.
• Region code is the optional second part, in ISO 3166-1 Alpha 2 format, such as AU or US.
• x-default is the fallback version for searchers whose language or country you don't serve.
• Return link means every version points back to every other version. Google calls these bidirectional links.
• Canonical tag names the preferred URL of a page. On a market page, it should point to that page itself.
• ccTLD is a country domain, such as .com.au. gTLD is a generic one, such as .com.
• Multilingual means more than one language, and multi-regional means separate versions for separate countries, such as a US and an Australian site.

Google is clear about language detection. Its guide says it doesn't use hreflang or the HTML lang attribute to detect a page's language; "we use algorithms to determine the language". So the words on the page decide the language. Hreflang decides which version gets swapped in.

What happens if you don't use hreflang?

Without hreflang, Google picks which version to show on its own. Sometimes it picks well. Often an Australian searcher sees the US page with US dollar prices, or the two English pages take turns ranking and neither settles.

Worried about duplicate content? Google's guide says localised pages "are only considered duplicates if the main content of the page remains untranslated". For two English pages, the risk is choice rather than a penalty. When the AU and US pages say almost the same thing, Google may fold them together and show one in both countries.

Google's multi-regional guide gives the fix for same-language versions. Pick a preferred version, then use rel="canonical" and hreflang so searchers get "the correct language or regional URL". Our international SEO service starts there, giving each market one page Google can crawl and making the canonicals, hreflang and sitemaps agree on it.

What hreflang mistakes do large international sites make?

Big sites get hreflang wrong in a few predictable ways, and each one quietly breaks the link between market versions. Check for these on your own site:

1. Codes that point at the wrong country. Country codes are ISO 3166 codes, and the obvious guess is often wrong. en-SV is El Salvador, not Sweden (SE), and en-SL is Sierra Leone, not Slovenia (SI).
2. Unsupported codes. Google's guide lists codes it doesn't support, such as es-419 for Latin American Spanish, so a tag that uses one does nothing.
3. Pages in separate sets. An Australian page lists only itself, the US page lists only the US and Mexico, and neither names the other. Google then has no link between the two versions.
4. English missing from its own set. A site lists every translation on its English page but not the English page itself, so the set never closes.
5. A market folder with no tags at all. A new /au/ or /us/ folder goes live with no hreflang, and Google has to guess which version to show.

Teams of every size miss pieces of this. That's why I'd check the tags with a crawler after every release, rather than once at launch.

What's on the international SEO checklist?

An international SEO checklist runs in six stages. Choose the markets, pick the URL structure and set up hreflang and canonicals. Then localise the pages, build authority in each market and measure each country on its own. Hreflang is one stage of six.

1. Choose the markets

• [ ] Confirm you can sell, invoice, support and stay compliant in a market before you build a single page for it.
• [ ] Research keywords per market. Australians and Americans often call the same product different things.
• [ ] Check each country's Google results. Your US competitors may be strangers.

2. Pick the URL structure

• [ ] Choose a country domain, subdomain or subfolder (see the table below).
• [ ] Use one pattern everywhere: /au/, /us/.
• [ ] Skip URL parameters like ?loc=au, which Google marks "Not recommended" in its multi-regional guide for international sites.

3. Set up hreflang and canonicals

• [ ] Give every version a set that lists itself and every other version.
• [ ] Use valid codes: language first, then country.
• [ ] Add an x-default.
• [ ] Point each market page's canonical tag at itself, and never at the page another market owns, or the hreflang set stops making sense.
• [ ] Write full URLs, with https://.

4. Localise the pages

• [ ] Show local currency, tax terms, phone numbers and addresses.
• [ ] Spell it their way.
• [ ] Add local proof: customers, case studies, certifications and the regulations that apply in that market, written for a buyer who lives there.
• [ ] Translate titles, meta descriptions and slugs when the language changes.

5. Build authority in each market

• [ ] Earn links and mentions from sites in each country.
• [ ] Appear where local buyers compare: the review sites, lists and trade press they already read before they shortlist a supplier.

6. Measure each country on its own

• [ ] Filter Search Console by country.
• [ ] Track rankings from inside each market.
• [ ] Report enquiries and revenue by market, so one healthy total can't hide a country that's quietly failing.
• [ ] Recrawl the hreflang sets after every release.

For the crawl, rendering and indexing checks underneath all of this, use our technical SEO checklist.

Should you use a country domain, subdomain or subfolder?

For most B2B SaaS and venture-backed companies, subfolders such as example.com/au/ are the simplest choice. Google lists them as "Easy to set up" and "Low maintenance", and in my experience every market builds on the main domain's existing links. Country domains give the clearest signal, at a higher cost.

Source: Google, read 27 October 2026.

One detail matters for SaaS. Google treats some country domains as generic, .io and .ai included. Its reason: "users and website owners frequently see these as being more generic than country-targeted". On a .io or .ai domain, your folders and hreflang carry the country signal, so they have to be right.

Moving to a new structure is a site migration, because redirects, canonicals and hreflang all change at once. Our site migration SEO checklist covers that move.

How do you add hreflang tags?

Add hreflang in one of three places: link tags in the page's <head>, an HTTP header, or your XML sitemap. Google says the three are "equivalent". Pick one. Google warns it may be "much harder to manage three implementations instead of just picking one".

For a company with a US homepage, an Australian folder and a fallback, every version carries the same set in its <head>:

``html <link rel="alternate" hreflang="en-US" href="https://www.example.com/" /> <link rel="alternate" hreflang="en-AU" href="https://www.example.com/au/" /> <link rel="alternate" hreflang="x-default" href="https://www.example.com/" /> ``

The US page and the Australian page both carry all three lines. Each one names itself and the other, and that's the return link Google checks for.

Which method suits you?

What are the most common hreflang mistakes?

The most common hreflang mistakes are missing return links, invalid codes and canonicals that point at another market. Google's guide names missing return links and wrong codes as the most common, and warns that missing return links can get the tags ignored.

The IP redirect deserves a second look. Google's guide warns: "Most, but not all, Google crawls originate from the US". Auto-redirect Australian visitors from an IP check and Google may struggle to reach your Australian pages at all.

Does hreflang help in ChatGPT and AI Overviews?

Hreflang is a Google Search signal for choosing between versions. Google says its AI features have "no additional requirements" beyond normal SEO, so the same setup serves AI Overviews and AI Mode.

For AI answers, I'd rely on the page. An Australian page should state Australian prices, Australian customers and Australian compliance in plain sentences. Then an engine answering an Australian buyer has Australian facts to quote. A copied US page with a currency swap doesn't.

That's the line between hreflang and international SEO. Hreflang points engines at the right version, and the content on that version is what makes it worth showing to anyone.

A worked example: an Australian payroll SaaS launching in the US

Take a B2B SaaS company selling payroll software in Australia, on example.com. It's raising money to enter the US. Here's how I'd set it up, and why each step matters.

1. Keep one domain. The site has links and history, so the US version goes in a /us/ folder rather than a new .com domain.
2. Build US pages, not copies. The Australian product page talks about Single Touch Payroll and superannuation. The US page needs W-2s, state payroll tax and 401(k) integrations, which means different main content written for a buyer with different worries. New copy.
3. Add hreflang only where pages pair up. The product, pricing and integration pages exist in both markets, so they get en-AU and en-US sets, while an Australia-only page about STP gets none.
4. Set x-default. It points at the US homepage, the version most English searchers elsewhere will find useful.
5. Fix the canonicals. Each /us/ page points at itself. Watch for a template that points every canonical at the original Australian page, because that cancels the hreflang.
6. Build US authority. US review sites, US integration partners and US press, because Australian links do less for US rankings.
7. Measure the US on its own. A Search Console filter for the United States on the /us/ folder, and US rankings tracked from the US.

Steps 3 to 5 are template work. Step 2 is the real writing, and steps 6 and 7 never stop. That's the honest shape of international SEO, and it's why hreflang alone rarely moves revenue.

Where does Searchmaxxed fit?

Searchmaxxed is an SEO and AI SEO agency for enterprise, B2B SaaS, venture-backed, manufacturing and public-sector companies. For international growth, we choose the market and site structure, implement hreflang and canonicals, localise the pages and measure demand and revenue by country.

Our packages:

A page release is an approved new page or a substantial rebuild of one. In a market launch, that means your US product, pricing, integration and comparison pages, each written for that market. Hreflang and sitemaps don't eat into the count. Our international SEO service sets out the market, structure, localisation and measurement work in detail.

Here's how we do it. We build on a website you own, our Agentic Website. AI agents pull your Search Console and GA4 data by country, read each market's Google results and check what AI answers say about you there. That feeds the Managed Search Loop, which shows which page, fix or link should bring in the most enquiries next, in which market. We build it, check the live page and its hreflang set, then measure what changed. Off your site, the Off-Page Source Layer builds the links, digital PR and mentions that each market needs before buyers there trust you.

Searchmaxxed's work has generated more than A$10 million in revenue through search for its clients.

Is Searchmaxxed right for you?

We suit growth teams entering a second market that want one team to build the pages, fix the setup and measure each country. If you only need a hreflang audit, a developer and a crawler will do it for less.

Comparing specialists? Here's my shortlist of the best international SEO agencies, which I wrote as the person who runs Searchmaxxed, so we're listed first.

Frequently asked questions

What should you do next?

List every page that exists in more than one version today, whether that's by country, by language or both. Empty list? Then you don't need hreflang yet. If there are pages on it, crawl them and check each set against the mistakes table above. If you'd like us to build and run your next market, let's talk pricing.