International SEO makes your content discoverable across countries and languages. This guide covers architecture decisions, hreflang implementation, and a practical playbook for Nepal-based sites expanding to global English audiences.

→ Hreflang dictionary · Search Intent Guide · Complete SEO Guide Nepal

URL structure options

Structure Example Geo signal Management
ccTLD example.com.np Strongest for Nepal Separate site per country
Subfolder example.com/np/ Good (GSC geo-target) Single site, easy
Subdomain np.example.com Moderate Separate hosting possible
gTLD + hreflang example.com + hreflang Relies on hreflang Simplest for global English

This site (arjankc.com.np): ccTLD with global English content — ranks internationally for marketing terms while dominating Nepal local queries via local proof and NPR data.

When you need international SEO

  • Multiple language versions (English + Nepali)
  • Same language, different regions (US vs. UK vs. Nepal English)
  • Global SaaS/tool content + local service pages
  • E-commerce shipping to multiple countries

If you only target Nepal in one language, focus on local SEO instead.

Hreflang implementation

HTML head method

On English Nepal page:

International SEO Strategy Guide (2026): Hreflang, Geo-Targeting & Global Rankings 
<link
  rel="alternate"
  hreflang="en-np"
  href="https://example.com/en-np/guide/"
/>
<link
  rel="alternate"
  hreflang="ne-np"
  href="https://example.com/ne-np/guide/"
/>
<link
  rel="alternate"
  hreflang="en-us"
  href="https://example.com/en-us/guide/"
/>
<link rel="alternate" hreflang="x-default" href="https://example.com/guide/" />

Rules:

  • Every page references ALL alternates (including itself)
  • Alternates must be reciprocal
  • Use ne for Nepali language (not np — that’s the country code)
  • x-default = fallback for unmatched users

→ Hreflang dictionary

Common hreflang patterns for Nepal sites

Pattern hreflang Use case
English for Nepal audience en-np Current site default
Nepali language ne-np Future Nepali content layer
Global English en or x-default Marketing guides, tools
India English en-in South Asia expansion

Google Search Console geo-targeting

  • ccTLD (.com.np): automatically associated with Nepal — no setting needed
  • Subfolder (/np/): set geo-target in GSC → International Targeting → Nepal
  • gTLD (.com): use hreflang; optionally set country target if single-country

Do not geo-target a global English subfolder to Nepal if content targets worldwide.

Content localization vs. translation

Approach Effort SEO value
Full translation High Strong for ne-np queries
Localization Medium Adapt examples, currency, laws for region
Same English, regional sections Low “Nepal Context” paragraphs (this site’s model)

This site’s model: Global English methodology + Nepal Context sections in dictionary entries and commercial guides — unique E-E-A-T without maintaining separate sites.

International keyword research

  1. Same keyword may differ by region (“digital marketing course” vs. “online marketing training”)
  2. Check SERP per target country (VPN or Ahrefs country filter)
  3. US/UK English spelling differences (optimization vs. optimisation)
  4. Currency in titles affects CTR (USD vs. NPR)

Technical checklist

  • Hreflang on all language/region alternates
  • Canonical self-referencing on each version
  • lang attribute on <html> tag (en, ne)
  • Currency/units localized in schema markup
  • Server location or CDN edge (latency for target audience)
  • Separate XML sitemap per language (optional, large sites)
  • Canonical tags prevent duplicate indexing

Nepal → global expansion playbook

Phase 1 (current): Global English content on .com.np with Nepal commercial pages

  • Marketing metrics hub, glossaries, calculators → global traffic
  • Website cost, pricing, benchmarks → Nepal leads

Phase 2: Strengthen global clusters without diluting local

  • More global tool/comparison content
  • Nepal posts link to global methodology pages

Phase 3: Optional Nepali language layer

  • Implement hreflang ne-np / en-np
  • Translate top 20 commercial pages (not entire 800+ post archive)

Phase 4: Optional separate gTLD

  • arjankc.com for global brand if ccTLD limits international trust (debated; many .com.np sites rank globally fine)

AI search and international SEO

  • AI answer engines cite structured English content regardless of domain TLD
  • Include clear definitions, tables, and FAQ schema for global citation
  • Entity consistency (Person schema, same author bio) across all content

→ AEO/GEO Guide

Common mistakes

  1. Machine-translated pages without editing — thin content penalty
  2. Hreflang pointing to 404 or redirected URLs
  3. Geo-targeting entire site to Nepal when content is global English
  4. Duplicate content across /us/ and /uk/ with no differentiation
  5. Using np as language code — use ne for Nepali