Skip to content

International SEO Checklist: 28 Checks Before You Launch a New Market

This international SEO checklist covers the 28 checks I run before a business launches in a new country or language, in the order they happen: proving demand, settling structure, localising pages, building them cleanly and measuring each market separately.

By Kristijan GjorgjioskiIndependent SEO consultant

Published 18 October 2026 · 7 min read

Key takeaways

  • Prove demand from your own Search Console, analytics and enquiry data before choosing a market. A tool's volume estimate is not enough on its own.
  • Settle the URL structure and the launch page set in writing before anyone translates a word, because both are expensive to change later.
  • Each market needs its own keyword map, prices, contact details and proof. Translation alone does not make a page relevant locally.
  • Google advises against automatically redirecting users between language versions, and Googlebot usually crawls from the US without an Accept-Language header.
  • Judge each market on its own clicks, rankings and enquiries. A blended global total hides the markets that are failing.

Most international launches I'm asked to rescue failed before anyone wrote a line of code.

The market was picked on a hunch, and the translations went live without a keyword in sight.

This international SEO checklist is built to stop that: 28 checks in five phases, each with a pass or fail you can confirm.

Copy it into a spreadsheet with an owner and status column before you commit a budget.

How to Use This Checklist

You don't need to start at check 1 if part of the work is done. Use this router:

  • Still deciding whether to expand? Work through phase 1 only. If it fails, stop there.
  • Market chosen, nothing built yet? Start at phase 2.
  • Translators already working? Jump to phase 3 and check their brief against it.
  • Launch is in a few weeks? Phases 4 and 5 are your priority.
  • Already live and underperforming? Run phases 4 and 5 first, then go back to phase 3.

Priority note: the checks marked (blocker) can silently stop a market from ranking at all. Fix those before anything else.

Phase 1: Prove the Market Is Worth Entering

These checks decide whether the rest of the list is worth doing.

1. Find the demand already in your data

Open your Performance report in Search Console and add a country filter.

Then do the same in your analytics and your enquiry or order records.

Pass: you can name the countries already sending impressions, visits or leads without any localised pages.

That existing demand is the strongest evidence you'll ever get.

2. Size search demand in the local language

Run your keyword research in the target country's own language, set to that country.

Pass: you have volume estimates for native-language terms, not translated English ones.

Have a native speaker sanity-check your list. My keyword research process works the same in any language.

3. Study who ranks there today

Search your main terms from the target market, using a local VPN or a rank tracker set to that country.

Pass: you know whether results are led by local specialists, marketplaces, global brands or forums, and roughly how strong they are.

4. Confirm you can actually serve the market

Check delivery, payments, local regulation, language support and time zones with the people who'd handle your customers.

Pass: operations sign off in writing. A market you can't serve well turns rankings into refunds.

5. Set a success measure per market

Agree what success means for you before launch: impressions, indexed pages, enquiries or revenue, by a set date.

Pass: each market has its own target, separate from your home market.

Phase 2: Settle Structure and Scope

Decide these before translation starts. Changing them later means redirects.

6. Choose the URL structure and record why (blocker)

Pick country domains, subfolders or subdomains, and write down your reasoning: budget, teams and existing authority.

Pass: one documented decision. My ccTLD vs subfolder vs subdomain comparison walks through the trade-offs.

7. Decide language or country targeting for each version

A Spanish version can target all Spanish speakers, or Spain specifically.

Pass: each version has a defined audience and a matching code, such as es or es-mx. If you'll run several languages, my explainer on multilingual SEO covers the language side.

8. Choose the launch page set

You don't need every one of your pages on day one.

Pass: a written list of launch pages, led by the ones that earn money: core services, categories or products, plus the trust pages that support them.

9. Fix the URL patterns and slug rules

Pass: a pattern for every page type per market, such as /de/leistungen/ (translated slugs) or /de/services/ (shared slugs), applied consistently.

10. Plan the fallback for everyone else

Decide where your visitors from untargeted markets should land.

Pass: a global page or country selector is chosen as the x-default destination.

Phase 3: Localise Every Launch Page

This is where most of the effort goes, and where translated sites fall behind localised ones.

11. Build a keyword-to-URL map per market

Pass: every launch page has a primary keyword and supporting terms in the local language, checked against the live results there.

12. Brief translators with the keyword map

Hand your translators the map, a terminology list and the purpose of each page.

Pass: translators know which phrase belongs in each title and heading, and which terms to avoid.

13. Show local prices, currency and tax

Pass: prices appear in local currency, with tax shown the way local buyers expect.

14. Localise contact details and service hours

Pass: each version shows a local phone format, a relevant address where you have one, and support hours in the market's time zone.

Google's guide to multi-regional and multilingual sites lists local addresses and phone numbers among the signals of a site's intended audience.

15. Use proof that means something locally

Pass: each market shows reviews, case studies, accreditations or standards a local buyer recognises, not only home-market ones.

16. Translate the invisible parts too

Titles, meta descriptions, image alt text, form labels, error messages, cookie banners and structured data text.

Pass: a crawl of the new version shows no home-language leftovers in any of them.

Phase 4: Build It So Google Can Find Each Version

Technical faults here can hide a whole market. Run these on staging first, then again on production.

17. Generate hreflang from one source of truth (blocker)

Pass: every page in each cluster lists itself and all its alternates, using valid codes and absolute URLs.

Google's localised versions guide says tags are ignored if two pages don't point to each other. My free hreflang generator builds the full set from a list, and my guide to what hreflang is explains the rules.

18. Give each version a self-referencing canonical (blocker)

Pass: the German page canonicalises to itself, not to the English original.

19. Remove forced redirects by location or language (blocker)

Google advises against automatically redirecting users between language versions.

Its crawler usually comes from the US without an Accept-Language header.

Pass: visiting any version from any country loads that version. A dismissible banner can suggest a better match.

Pass: the selector on each page links to the same page in each other language, not to the homepages.

21. List every version in XML sitemaps

Pass: sitemaps include each market's URLs and are submitted in Search Console.

22. Confirm production is indexable (blocker)

Staging blocks often travel to live.

Check your robots.txt, meta robots tags and HTTP headers on the new folders.

Pass: sample URLs from each version show as indexable in URL Inspection.

23. Check speed from inside the market

Pass: key templates load acceptably for visitors in the target country, using a CDN where your origin server is far away. My guide to Core Web Vitals covers what to measure.

Phase 5: Launch, Then Measure Each Market Alone

24. Crawl production on launch day

Pass: a full crawl shows 200 status codes, valid hreflang return links and correct canonicals across every version.

The same crawl belongs in any technical SEO checklist you run after a release.

25. Set up reporting per market

Pass: URL-prefix Search Console properties or saved filters for each folder, and analytics segments per market. A GA4 measurement plan keeps enquiries tracked the same way everywhere.

26. Inspect and submit priority URLs

Pass: your top launch pages per market have been inspected in Search Console and requested for indexing.

27. Start building local references

Your new version needs signals from its own market: local press, partners, associations and directories.

Pass: a list of local link and citation targets exists for each market. My guide to local citations explains how listings work, and if you have a real address there, a Business Profile for that location helps too.

28. Review at 30 and 90 days

Filter your Search Console data by country and check which URLs receive the clicks.

Pass: searchers in each country mostly land on their own version. If the home-market pages still collect the clicks, go back to checks 17 to 19.

Put the Checklist to Work

Start with phase 1 for your next market, and don't skip check 4.

Most expansion budgets I've seen wasted were spent on markets the business couldn't serve.

If you're already live, run the five blockers today: structure, hreflang, canonicals, redirects and indexability.

They take an afternoon and catch the faults that quietly cap every market at once.

Moving an existing site into a new structure is a migration, so pair this list with my website migration SEO checklist.

When you'd rather have someone own the whole list, my international SEO services cover market prioritisation, structure, hreflang and per-market research. You can also see how I plan new market launches before deciding.

Frequently asked questions

How long does it take for a new international market to rank?

Fixes to an existing setup can show within weeks of Google recrawling the pages. A new market built from scratch usually takes several months, because the new version has to be crawled, indexed and earn some authority and local references of its own. Set expectations around impressions and indexing first, then rankings and enquiries once the pages have settled.

Should I launch the whole site in a new language at once?

Rarely. I prefer launching the pages that drive revenue first, such as core service, category or product pages, plus the supporting pages needed to make them credible. A smaller set of well-researched, properly localised pages tends to do better than a full site of thin translations, and it is easier to check and fix.

Do I need a separate Search Console property for each market?

You do not have to, but it helps. A domain property shows everything, and adding URL-prefix properties for each language folder, such as /de/ or /fr/, gives each market team a clean view of its own clicks, queries and indexing without filtering every report. Country domains need their own property in any case.

Is an international SEO checklist different for ecommerce sites?

The checks are the same, but some carry more weight. Currency, tax display, delivery times, returns and payment methods decide whether a foreign shopper buys, and product feeds or structured data often need a version per market. Category pages usually matter more than blog content for an online store entering a new country.

About the author

Kristijan Gjorgjioski

Independent SEO consultant · 6+ years in SEO · 60+ client websites worked on

I'm an independent SEO consultant with 6+ years in SEO. I run audits, migrations and content programmes for businesses in Europe, the UK and the USA, and I build the automation behind my own research.

Need help with international seo?

Book a free 30-minute call. I look at your site first and tell you plainly what I would fix, and in what order.