How to Do International SEO: Step-by-Step Guide
A practical, step-by-step guide to plan, implement, and scale international SEO for startups and SMBs. Includes hreflang, URL strategy, and measurement.

International SEO can turn one product into many regional customer pipelines — if you plan correctly. This guide walks through how to do international SEO for startups and small teams: pick markets, choose a URL strategy, implement hreflang, build localized content clusters, publish without engineering bottlenecks, and measure results.
TL;DR:
-
Choose 1–3 priority markets by revenue potential and existing user signals, document each on a one-page brief, and test a single URL strategy for 4–12 weeks.
-
Measure per-locale impressions, clicks, conversions in Google Search Console and Analytics, iterate monthly, and prune low-performing duplicates within 4–8 weeks after testing.
Step 1: Prepare — Define Target Markets, Languages, and Success Metrics
Choose Countries vs Languages (why This Matters)
Decide whether you will target countries (e.g., Germany) or languages (e.g., German speakers across countries). Targeting by country focuses on market rules, payment rails, and local SERP behavior. Targeting by language allows content reuse across borders but can miss country-specific intent and local SERP features.
Use simple market filters:
-
Revenue potential: estimate addressable market size and conversion rate for the country
-
Existing user signals: Google Analytics audience by country and user locale
-
Competition: search difficulty for top transactional keywords in the market
Document each decision in a one-page brief listing target country, language, preferred URL strategy (ccTLD, subdirectory, subdomain), and KPIs. See our first-90-days checklist for an onboarding-style template that can be adapted to an international rollout plan.
Set Business-focused KPIs (organic Revenue, Leads, Impressions)
Translate SEO metrics to business outcomes early:
-
Primary KPI: organic conversions or revenue per locale
-
Secondary KPI: impressions, clicks, and average position for target keyword clusters
-
Operational KPI: pages published per locale per month (start with 4–8)
Keep the KPIs measurable in tools you already use: Google Analytics (goals/ecommerce), Google Search Console (impressions & queries), and your CRM for lead attribution. Include baseline values in your brief so you can declare wins.
Prerequisites: Data and Access You'll Need
Before you start, make sure you have:
-
Access to Google Search Console and the property for your preferred root URL
-
Google Analytics (or GA4) admin access and the ability to segment by country/language
-
A decision on CMS and publishing permissions (WordPress, Webflow, Ghost)
-
Stakeholder sign-off on engineering budget if ccTLDs or server changes are needed
External perspectives can help. For market selection and supporting research, see this overview that covers URL structure, hreflang, and multilingual keyword research: How to do international SEO: a complete guide.
Step 2: Audit Your Site for International Readiness
Crawl and Indexability Checks (what to Look For)
Run a full crawl and capture:
-
Pages per language and their HTTP status (200, 3xx, 4xx, 5xx)
-
Robots.txt and any server-side blocking by locale
-
Pages with meta noindex tags
-
Canonical tags pointing to a different language or default site
Industry best practices and examples are summarized in vendor write-ups like Semrush's international SEO guide.
Identify Current Geo-targeting and Hreflang Issues
Check Search Console's International Targeting report for hreflang errors and country targeting. Common findings:
-
Hreflang missing or incorrectly implemented (self-referencing hreflang absent)
-
Hreflang tag loops or inconsistent x-default
-
Canonicals that always point to a single language page, preventing localized indexing
Record counts of hreflang errors and indexed pages per language as baseline metrics you can fix and re-check.
Technical Checklist: Canonical Tags, Language Tags, Sitemaps
Audit the following:
-
Rel=canonical: confirm it points to the correct localized URL, not a default language
-
HTML lang attribute: present and matches the page language
-
Hreflang: present as link elements, sitemap entries, or HTTP headers and mutually referenced
-
Sitemap: include localized URLs or separate sitemaps per locale
-
Server behavior: check Vary: Accept-Language headers and redirects
For sector-specific issues (compliance, localized content needs), our guide for doctors shows how verticals change the audit approach: doctor SEO considerations. Also consult broader industry advice like BrightEdge's recommendations on search engines used in each country: Best Practices for International SEO.
Step 3: Configure Domains, URL Structure, and Hreflang
Choose Between Cctld, Subdirectory, or Subdomain (trade-offs)
Compare three common URL strategies:
| Option | Pros | Cons |
|---|---|---|
| ccTLD (example.de) | Strong geo-targeting signal; user trust for country | Higher cost and setup time; separate hosting/maintenance |
| Subdirectory (your website property) | Easier to implement; centralized domain authority | Slightly weaker geo-signal than ccTLD; requires clear routing |
| Subdomain (a dedicated subdomain) | Logical separation without new TLD | May be treated as separate site by some search engines; requires DNS/configure |
Estimate setup time and maintenance cost:
-
ccTLD: 2–6 weeks including DNS, hosting, and SSL per country
-
Subdirectory: Days to a few weeks depending on CMS routing
-
Subdomain: A few days to weeks for DNS and SSL setup
Document your URL mapping and expected maintenance costs before publishing. Engineering considerations and implementation examples are discussed in our guide for development teams: development shops SEO.
Implement Hreflang Correctly (link Element vs HTTP Header vs Sitemap)
Three accepted hreflang delivery methods:
-
HTML link element in head (most common for HTML pages)
-
HTTP header (for non-HTML files like PDFs)
-
Sitemap with hreflang entries (good for large sites)
Rules to follow:
-
Every localized URL must reference itself and all alternates (mutual references)
-
Use language-region codes (e.g., fr-CA) for country-specific content
-
Provide an x-default pointing to a language selector or global homepage
Before deploying, create a master mapping spreadsheet with canonical URL, localized URL, language tag, and hreflang method. For a walkthrough video covering URL choices and Search Console setup, watch this checklist-style guide — it shows configuration steps and Search Console settings you can follow: This video explains the fundamentals:
Set Up Country Targeting and Webmaster Tools
In Google Search Console, set geographic target per property if you're using subdomains or subdirectories. For ccTLDs, Google uses TLD to infer country so property targeting isn't required. Register each site property you plan to publish and add sitemaps containing localized URLs.
For detailed best practices and technical specs, BrightEdge covers recommended site structures and search engine considerations: Best Practices for International SEO in 2022.
Step 4: Localized Keyword Research and Content Cluster Strategy
Build Keyword Sets Per Market (intent + Local Language)
Run keyword discovery in the target country and language — do not reuse exact English keywords. Techniques:
-
Use Google Keyword Planner and localized SERP scraping
-
Find question-format queries with our question keyword finder
-
Track local search features and intent differences (e.g., transactional phrasing varies by country)
Cluster keywords by topic and intent, then prioritize by difficulty versus business value. For tooling, industry guides like Ahrefs explain keyword selection per locale: 10 International SEO Best Practices + Checklist.
Create Pillar Pages and Cluster Topics Per Locale
Structure each locale with a pillar page (broad topic) and 6–12 cluster pages (long-tail intent). Example: A UK payments pillar could include cluster pages for "payment gateways UK", "PCI compliance UK", "best recurring billing UK", etc. Use keyword clustering tools to automate grouping, and schedule content so each locale publishes a pillar first, then clusters over 4–12 weeks.
Many niches provide direct examples. See how ecommerce sites map categories and keywords in our ecommerce SEO checklist and how local services use pillars in home builders SEO tips.
Decide on Translation vs Locally Authored Content
Options:
-
Machine translation + human editing: fast and lower cost; good for low-priority pages
-
Native authors: slower, costlier, higher quality; recommended for pillar and high-converting pages
-
Hybrid: generate drafts with machine translation, then localize with a native editor
Compare by cost and expected time:
-
Machine + edit: 1–3 days per page
-
Native content: 1–3 weeks per page depending on research
For content-heavy products like courses, map topics to locales carefully; see our guide on localizing course content: SEO for online courses.
Step 5: Publish, Internal Link, and Optimize at Scale
CMS Strategy and Publishing Workflow
Ensure your CMS supports the chosen URL structure (WordPress, Webflow, Ghost). Set up:
-
Templates for localized metadata (hreflang tags, lang attributes, canonical)
-
A review workflow to catch translation quality and schema insertion
-
A publishing schedule (batch vs continuous)
If you want to decide whether to run this in-house or use an external service, our agency vs in-house decision guide can help.
Internal Linking Between Locales and Canonicalization
Link strategy:
-
Prioritize internal links within the same locale to build topical authority
-
Use cross-locale links sparingly for explanatory pages (e.g., “Our global pricing”)
-
Ensure canonicals point to the localized page, not a global default
Schema, Metadata, and Local Assets
Apply locale-aware schema and metadata:
-
LocalBusiness schema with correct address and language when relevant
-
Hreflang and lang attributes in metadata
-
Localized meta descriptions and title templates (include currency and local terms)
-
Alt text for images in the target language and relevant file names
Embed YouTube videos and images that match the locale. Avoid using untranslated assets that confuse users. For single-location businesses and their citation needs, review our restaurant SEO guide.
Use a consistent publishing cadence and batch content to reduce overhead.
Step 6: Measure Performance, Iterate, and Common Mistakes to Avoid
Set Up Measurement: GSC, Analytics, and Locale Reports
Track these per locale:
-
Impressions and clicks per page and per query (Google Search Console)
-
Organic conversions and revenue per locale (Google Analytics)
-
Average position and top queries per page
Map queries to pages by using GSC query exports and cross-referencing landing pages.
Iteration Cadence: Tests, Learnings, and Content Pruning
Suggested cadence:
-
Weekly: check indexing and hreflang errors
-
Monthly: review top queries, update titles, and tweak meta descriptions
-
Quarterly: prune or consolidate low-performing duplicate pages and refresh pillar content
A basic playbook:
-
A/B test titles or meta descriptions for top pages for 2–4 weeks
-
Update cluster content based on new query data monthly
-
Remove or redirect duplicate or low-value localized pages after 4–8 weeks of testing
For niche examples of pruning local pages, see our physical therapist SEO.
Common Mistakes and How to Fix Them
-
Incorrect hreflang implementation: Check mutual references and x-default. Fix within 1–3 weeks.
-
Mixed URL structures: Standardize on one approach and redirect old variants. Expect 2–6 weeks for redirects and Search Console cleanup.
-
Over-reliance on machine translation: Prioritize native content for high-value pages; edit machine translations within 1–2 weeks.
-
Missing local citations and schema: Add local citations, schema, and regional contact details within 2–4 weeks.
-
Poor internal linking: Use automation to create cluster links, or follow a manual checklist to ensure each cluster links to its pillar.
Industry references and ongoing learning help. For a broader iteration approach, consult this general international SEO guide: The Complete Guide To International SEO in 2026.
The Bottom Line
How to do international SEO starts with a narrow, measurable plan: pick 1–3 markets, audit, pick a URL strategy, publish localized pillars and clusters, and measure per-locale business outcomes. Results vary by market and volume, so run short tests, measure conversions, and iterate.
Frequently Asked Questions
Why aren't my localized pages indexed?
Start with a short checklist: confirm pages return 200 status codes, remove any meta noindex tags, check that rel=canonical doesn't point to a different language, and verify hreflang references are mutual. Use Google Search Console's coverage report and URL Inspection tool to see how Google fetches the page. If the page is crawlable but not indexed, submit the URL in Search Console and monitor for 1–2 weeks while checking server logs for crawl activity.
If indexation problems persist, review your sitemap entries, ensure the sitemap is submitted in Search Console, and check for server-side blocks like IP-based restrictions or Vary: Accept-Language misconfigurations.
Should I translate everything or prioritize a subset?
Prioritize pages that drive conversions and organic traffic. Start with pillar pages, top-converting product or service pages, and high-volume category pages. Use analytics and Search Console to identify revenue-driving pages and translate those first. For lower-priority content, machine translation plus human editing can speed rollout while you test demand.
Plan to produce fully native content for pillars and any pages tied directly to purchase decisions; these often deliver the best ROI but require more time and budget.
How do I check if hreflang is working?
Use Search Console's International Targeting report to see hreflang errors and coverage. Also inspect the page source for the link elements or check the sitemap entries if you used a hreflang sitemap. Verify mutual references — every alternate must reference every other alternate including itself. Finally, monitor localized SERP visibility and impressions in Search Console for each targeted country and language over several weeks.
Can I manage international SEO without extra engineering?
Yes, with constraints. Subdirectory approaches often require less engineering than ccTLDs. Many CMS platforms (WordPress, Webflow, Ghost) handle language routing and metadata with plugins or built-in features. For server-level changes (ccTLDs, DNS, or complex redirects), you'll still need engineering time.
Related Articles

How to Prioritize SEO Tasks: Step-by-Step Guide
A practical step-by-step method to prioritize SEO work, balance quick wins and long-term growth, and scale content production efficiently.

How to Do SEO Forecasting: Step-by-Step Guide
Discover a comprehensive, step-by-step guide to mastering SEO forecasting and boost your content strategy.

How to Analyze Search Console Data: Step-by-Step Guide
Step-by-step instructions for auditing and extracting actionable SEO insights from Google Search Console to drive content and technical fixes.
Ready to Scale Your Content?
SEOTakeoff generates SEO-optimized articles just like this one—automatically.
Start Your Free Trial