Should You Build or Buy International SEO (hreflang) on Shopify?
Building international SEO correctness beats renting it: Shopify Markets already emits hreflang for the market domains and subfolders it manages, so the real work is a one-time audit and theme-head fix. An audit-and-fix engagement runs an estimated $4,000–$12,000 (Deploi estimate, illustrative). SEO apps layer tags over Shopify's own output, risking duplicates, and keep billing after the markup is right. Edge cases like x-default and cross-domain canonicals are exactly where apps stop.
Your profile — see how the verdict shifts
- Confidence
- High — Markets emits the baseline hreflang; what remains is bounded, one-time markup work in the exact edge cases tag apps structurally can't finish
- Reference scenario
- $20M–$100M GMV · 2–6 markets on one store · agency dev bench
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| One market, one language | WAIT | No hreflang problem exists yet; Shopify's defaults carry a single-market store fine. |
| 2–6 markets, one store | BUILD | Markets emits the baseline; one audit catches return-tag gaps and x-default choices before they cost rankings. |
| Markets plus separate regional stores | BUILD | Cross-domain hreflang between separate stores is hand-built territory; no app sees both sides cleanly. |
| Expansion-stage: a new market per quarter | BUILD | Bake the audit into the launch checklist; correctness compounds while subscriptions just recur. |
What International SEO (hreflang) Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — indirect | High | Correct hreflang puts each country's own URL in front of its searchers, so organic visitors arrive at a store that already matches their currency and shipping. |
| Customer experience | Medium | Searchers land on their own market instead of bouncing off the US store and hunting for a country switcher. |
| Revenue — direct | Medium | Wrong-market landings abandon at the currency or shipping reveal; fixing the signals recovers those checkouts market by market. |
| Data & insight | Low | Clean per-market landing data makes market-level SEO reporting trustworthy, instead of US pages absorbing every country's clicks. |
Spend ceiling: Correctness has a fixed price. Once the tags are right they stay right until structure changes, so pay once for the audit and fix, and refuse anything that bills monthly for static markup.
What buying enables (top apps)
- + Bulk meta-tag housekeeping across thousands of pages without dev time
- + Templated markup applied consistently as new products and pages publish
- + A dashboard non-SEO teammates can operate day to day
What building additionally unlocks
- + Edge-case coverage no template reaches: x-default policy, cross-domain canonicals, placeholder noindexing
- + Cross-store hreflang maps between separate regional stores, generated from one source of truth
- + Zero added script weight and no second tag writer fighting Shopify's output
- + An audit playbook your team reruns free at every market launch
Find Your Verdict in 3 Questions
Do you sell through more than one market or language today?
Yes: Go to question 2.
No: Your verdict: WAIT — there's no hreflang to manage yet. Bake the audit into your first market launch instead.
Is everything on one Shopify store, using Markets' domains or subfolders?
Yes: Go to question 3.
No: Your verdict: BUILD — separate regional stores need a hand-built cross-domain hreflang map; no app covers both sides.
Are wrong-country URLs ranking, or is Search Console flagging hreflang errors?
Yes: Your verdict: BUILD — commission the audit and theme fix now; every month of mixed signals costs rankings.
No: Your verdict: WAIT — Markets' defaults are holding. Re-check after the next market launch or theme swap.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | An SEO app installs in minutes; the audit-and-fix engagement runs an estimated 2–4 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | Tag apps bill monthly for markup that, once corrected, just sits there; the build's only recurring cost is a periodic re-crawl. | ||
| Maintenance & upgrades | Theme swaps and new markets reopen the work on both paths; owned snippets get fixed once, app output gets re-configured. | ||
| Switching & exit | Uninstalling a tag app risks leaving conflicting markup behind; owned head snippets travel with the theme. | ||
| Risk | |||
| Vendor risk | SEO tooling churns and consolidates; your market signals shouldn't depend on a vendor's roadmap. | ||
| Security & compliance surface | Head markup touches no customer data; the build removes one more third-party script from every page. | ||
| Platform-deprecation exposure | Apps that inject head tags chase theme architecture changes; Liquid head snippets are the stable, sanctioned surface. | ||
| Value | |||
| Fit to requirement | Edge cases decide this capability: x-default policy, cross-domain canonicals, untranslated placeholders. Apps template; audits reason. | ||
| Time to market | The app installs faster, but correctness isn't live until someone verifies return tags either way. | ||
| Performance & scale | Server-rendered head tags carry no script weight; more markets add markup, not milliseconds. | ||
| Data ownership & AI-readiness | Clean market signals decide which URL search engines and AI answer surfaces cite; owned markup keeps that under your control. | ||
| Focus & opportunity cost | Bounded, one-time scope: the audit ends, the fix ships, and the team moves on. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify Markets hreflang output | Native — Emits hreflang across the market domains and subfolders one store manages; edge cases remain (July 2026 research — re-verify) | Included with every Shopify plan | The baseline: a single store on a standard market structure |
| SEO tag apps (category) | Category — Meta-tag and markup housekeeping tools; confirm hreflang scope and conflict handling | Free–$50/mo bands (illustrative) | General on-page housekeeping when no dev bench exists |
| Hreflang audit + theme-head build | Build lane — This page's verdict: crawl the markets, fix the gaps in Liquid, verify return tags in Search Console | $4,000–$12,000 one-time (Deploi estimate, illustrative); no subscription | Edge cases: x-default, cross-domain canonicals, separate regional stores |
The Build Path
- Hreflang & canonical audit: Crawl every market's URL set, verify hreflang pairs are reciprocal, and map where canonicals and x-default disagree with your market strategy.
- Theme-head fixes in Liquid: A head snippet correcting what the audit found: x-default policy, canonical targets, and noindex rules for untranslated placeholder pages.
- Cross-store hreflang map: For separate regional stores, generate the cross-domain tag map from one source of truth so every store stays reciprocal.
- Effort band
- $4,000–$12,000 audit and fix (Deploi estimate, illustrative); sits at or below the $10–25K contact-form band
- Typical timeline
- 2–4 weeks (Deploi estimate, illustrative)
- Maintenance, honestly
- ~$1,000–$2,500/yr (Deploi estimate, illustrative), under the standard 15–20% of build cost: a re-crawl after theme swaps, market launches, or URL-structure changes. No subscription line.
- What you own — and what you take on
- You own: the hreflang logic, the x-default policy, and an audit playbook you rerun at every market launch. You take on: re-verifying return tags whenever site structure changes.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$600 | $4,000–$12,000 |
| Years 1–3 (recurring) | $1,100–$1,800 | $3,000–$7,500 (re-crawls) |
| 3-year total | ≈$1,100–$2,400 | ≈$7,000–$19,500 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: a mid-band tag app held flat for three years, assumed to cover your edge cases; generous, because most don't.
- † Build is a one-time audit and fix plus periodic re-crawls; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Tag apps layer hreflang over Shopify's own output; duplicate or conflicting tags confuse crawlers more than missing ones (community-reported pattern)
- — The subscription keeps billing long after the markup is correct and static
- — Apps can't see Search Console, so return-tag errors surface to you, not the vendor
- — Uninstalling can leave orphaned markup behind in the theme
On the build path
- — Return-tag reciprocity breaks silently when one market's page is unpublished or blocked
- — Audits go stale: theme swaps, URL changes, and new markets all reopen the work
- — Separate regional stores multiply the matrix; budget the cross-store map honestly
- — ~$1,000–$2,500/yr in re-crawl upkeep (Deploi estimate, illustrative)
What Merchants Say
The recurring shape: international pages ranking in the wrong country's results, or the US page outranking the localized one, while an SEO app reports everything green.
Search Console hreflang errors spike after a market launch or theme swap, and merchants discover the app never handled return tags on the new URLs.
If You Change Your Mind Later
If you bought and outgrow it
Uninstall carefully: tag apps can leave orphaned hreflang and canonical markup in the theme, and the conflict between leftovers and Shopify's own output is worse than either alone. Do a post-uninstall crawl of every market, then re-verify return tags in Search Console over the following weeks.
If you built and want out
Corrected markup is just Liquid in your theme: no vendor, no export, nothing stranded. The audit playbook stays reusable at every market launch, and if you later add an app for other SEO chores, the owned hreflang keeps working underneath it.
When This Answer Changes
We're watching for:
- ▸ Shopify expanding native hreflang coverage to more structures, including x-default controls
- ▸ Markets changes to URL structure or domain handling that reshuffle existing tags (monitor the Shopify changelog)
- ▸ AI answer surfaces citing wrong-market URLs, a newer visibility cost of the same markup errors (monitor)
Verdict change log:
No changes since first publication (August 2026).
Common Questions
Does Shopify generate hreflang tags automatically?
Yes, within one store: Shopify Markets emits hreflang for the market domains and subfolders it manages (July 2026 research — re-verify). Coverage stops at the edge cases: x-default choices, separate regional stores, canonical conflicts, and untranslated placeholder pages. An audit-and-fix engagement closes those for an estimated $4,000–$12,000 one-time (Deploi estimate, illustrative), and the corrected markup then needs no subscription.
Can an SEO app fix hreflang problems on Shopify?
Rarely. Shopify already outputs hreflang for managed markets, so a tag app adds a second writer to the same head, and duplicate or conflicting tags confuse crawlers more than missing ones. Apps also can't verify return-tag reciprocity across separate stores. Hreflang is correctness work: audit once, fix in the theme, re-verify in Search Console. Budget $4,000–$12,000 one-time (Deploi estimate, illustrative) instead of a monthly fee.
What hreflang edge cases does Shopify Markets miss?
Four show up constantly: the x-default choice for global visitors, cross-domain tags between separate regional stores, canonicals pointing at a different market's URL, and placeholder pages published before translation. Each one sends crawlers mixed signals about which URL serves which country. A one-time audit catches all four, and the theme-level fix runs an estimated $4,000–$12,000 (Deploi estimate, illustrative).
Your Next Steps
If you're going with BUILD(matches your selected profile)
- Crawl every market's URL set and export the current hreflang, canonical, and index state
- Decide the x-default policy deliberately, usually your global or primary-market storefront
- Fix gaps in a theme-head snippet; add noindex rules for untranslated placeholders
- Re-verify return-tag reciprocity in Search Console after two crawl cycles
- Add the audit to the launch checklist for every new market
If you're going with WAIT
- Confirm Markets is emitting hreflang on your structure with a spot-crawl of two markets
- Watch Search Console's international targeting and page-indexing reports monthly
- Skip tag apps for now; duplicate markup is the main risk while defaults are holding
- Diary a full audit for the next market launch, theme swap, or URL change
Official Docs & Sources
- Markets — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy Multi-Currency & Market Pricing on Shopify?
Multi-currency is native on Shopify. The real decision is the market-pricing layer on top.
Should You Build or Buy Translation on Shopify?
Translation on Shopify is a CUSTOMIZE call: free native Translate & Adapt as the floor, an owned AI pipeline on the translation APIs past three locales.
Should You Build or Buy Duties & Import Taxes on Shopify?
Duties and import taxes are a true DEPENDS: pay the merchant-of-record fee while lean, own the flow as international scales, never build the landed-cost engine.
Should You Build or Buy Cross-Border Compliance for Shopify?
Cross-border compliance is bought expertise: GPSR-class rules need specialist review per market, while your store publishes the documentation it produces.
Build or Buy Inventory Forecasting on Shopify?
Buying wins for inventory forecasting on Shopify: purpose-built apps model seasonality and lead times, and custom models only pay with warehouse-grade data maturity.
Ready to make every market rank on its own URL?
One audit, one theme fix, and the markup is yours with no subscription attached. We'll start with a crawl of your markets and show you exactly where the signals disagree.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing is illustrative band pricing, re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.