Question 1

Do I need hreflang if I only have one language but target multiple countries?

Accepted Answer

Yes — hreflang is useful when targeting multiple regions even in the same language. English content targeting the UK, US, and Australia can use en-gb, en-us, and en-au to ensure Google serves the regional version with local pricing, spelling, or references to the appropriate audience. If the content is truly identical with no regional differentiation, hreflang provides less value — but if the pages differ (pricing, currency, local references, regional terms), hreflang prevents the wrong version from appearing in the wrong market's search results.

Question 2

What's the difference between ccTLDs, subdomains, and subdirectories for international SEO?

Accepted Answer

Three common URL structures for international sites: country-code TLDs (example.co.uk, example.fr) send the strongest regional signal but require separate domain authority building for each country. Subdomains (uk.example.com, fr.example.com) are more manageable but still require separate authority signals. Subdirectories (example.com/uk/, example.com/fr/) share the root domain's authority and are easiest to manage with a single CMS. Google has said all three approaches can work for international targeting, but subdirectories are generally easiest from an SEO management perspective — one domain to build authority, one Search Console property to monitor (though you can add regional properties for reporting).

Question 3

How do I check if Google is correctly applying my hreflang targeting?

Accepted Answer

The most direct check: search for a target keyword on Google.co.uk (with a UK VPN or Google's region-specific search) and verify the UK version of your page appears rather than the US or global version. Also check Search Console — under Legacy Tools → International Targeting → Language. This shows detected hreflang tags and any errors in the implementation. A "Confirmation" status means Google has confirmed the annotations are valid and reciprocal. An "Error" status means something in the annotation set is incorrect. Fix errors in the order they're reported — broken reciprocity is typically the root cause of most hreflang errors.

Question 4

Can I use hreflang with translated content generated by AI?

Accepted Answer

Hreflang is agnostic about how the content was created — it just signals regional targeting. AI-generated translations can work for international SEO if the quality is sufficient (human review is strongly recommended, particularly for fluency and local idiom). The risk with low-quality machine translation isn't hreflang — it's content quality. A page that reads like unedited machine translation may be indexed but rank poorly because it fails quality signals. Use AI translation as a starting point with human editing for the target market, and hreflang to ensure the right version reaches the right audience.

Question 5

What happens if I just don't implement hreflang at all?

Accepted Answer

Google will still index all your regional or language versions and will attempt to serve the most relevant one based on the searcher's location and language settings, plus content signals like on-page language and local references. Without hreflang, this guess is frequently wrong — UK searchers seeing US pricing, or French speakers landing on the English version. For sites with only minor regional differences (e.g., currency symbol only) this risk may be tolerable; for sites with materially different content, pricing, or legal terms per region, the wrong version showing up is a real conversion and trust problem worth the implementation effort to prevent.

Question 6

Is hreflang implementation different for WordPress multisite vs. a single installation with subdirectories?

Accepted Answer

The hreflang output requirement is identical either way — what differs is how you generate it. WordPress multisite setups and dedicated multilingual plugins (WPML, Polylang) generate and maintain reciprocal hreflang sets automatically as you link translated content together, which removes most of the manual reciprocity risk. A single installation managing regional content without a dedicated plugin requires more manual care to keep every page's annotation set complete and in sync as pages are added, renamed, or removed. For sites with more than two or three regions, a dedicated multilingual plugin is usually worth it just for the automated reciprocity handling.