You sell in the US and Canada. You have two English versions of almost every page and a French version that someone translated in a hurry. Google keeps showing your US page to people in Toronto, with US dollar prices and a shipping policy that does not apply to them. This international SEO checklist is built for exactly that setup: two countries that share a language, a border and most of a search vocabulary, plus a French-speaking province with its own rules.
Most international SEO advice assumes you are launching in Germany and Japan, where the languages differ. The US/Canada problem is harder because the pages look the same. The compact checklist at the end is the version to hand to your developer.
Are near-identical US and Canadian pages duplicate content?
No penalty applies. Google’s own guidance on managing multi-regional and multilingual sites treats similar same-language content for different regions as normal, and tells you to use rel="canonical" and hreflang so the right regional URL is served.
The real risk is quieter. If your en-us and en-ca pages are word-for-word identical, Google may treat them as duplicates and index one URL. Hreflang can still show the Canadian URL to Canadians, but you are relying on a hint across two pages Google already considers the same. The more genuinely local each page is (currency, shipping, tax wording, phone number, spelling), the more reliable the setup.
When to merge, when to split
Split into country versions when something a buyer cares about actually differs: price, currency, availability, shipping, returns or warranty terms. Keep one page when nothing differs. A case study or an “about us” page does not need an en-ca twin; creating one doubles maintenance and gives Google two URLs to choose between for no benefit.
Here is the trade-off nobody tidies up for you: a single English site concentrates links and authority, but Canadian searchers see US prices and may bounce. Split sites convert better locally, but every new page has to be built, translated and kept in sync three times. For a B2B services firm with one price list in USD, one site is often the right answer. For a WooCommerce or Shopify store with CAD pricing and Canadian warehousing, it rarely is.
ccTLD vs subfolder vs one site: which URL structure fits?
For most businesses selling into both countries, subfolders on one .com domain (/en-ca/, /fr-ca/) are the best balance of signal strength and effort. A .ca ccTLD sends the strongest country signal but behaves like a second website you have to build authority for from scratch.
| Option | Country signal | Authority | Effort and cost | Good fit when |
|---|---|---|---|---|
| example.ca (ccTLD) | Strongest. Google treats a .ca as targeted at Canada. | Starts from zero; links to .com do not transfer. | Highest: second hosting setup, separate Search Console property, separate link building. | You have a real Canadian entity, local team and budget to market the .ca on its own. |
| example.com/en-ca/ (subfolder) | Clear, via hreflang and on-page localization. | Shares the .com’s authority. | Moderate: one site, one CMS, more templates. | Most US-first businesses adding Canada, including WordPress and WooCommerce stores. |
| ca.example.com (subdomain) | Similar to a subfolder. | Often treated more like a separate site in practice. | Moderate to high. | Your platform forces it, for example a separate Shopify store per market. |
| One site, no country versions | None. You rely on general relevance. | All in one place. | Lowest. | Prices, offer and terms are identical for both countries. |
Parameters such as ?country=ca are left out on purpose: Google’s documentation does not recommend them for locale, and they make hreflang and analytics harder.
A note on Search Console: the old International Targeting report, where you could set a target country for a property, has been retired. Your country signals now come from the domain, hreflang and the content itself, which is one more reason the on-page localization below matters.
Hreflang done right: en-us, en-ca, fr-ca and x-default
Every version of a page lists itself and every other version, using ISO 639-1 language codes with optional ISO 3166-1 region codes, and every version links back. Google’s localized versions documentation is explicit: if two pages don’t both point to each other, the tags are ignored.
For a product page in a subfolder setup, the identical block goes in the <head> of all three versions:
<link rel="alternate" hreflang="en-us" href="https://example.com/products/trail-jacket/" />
<link rel="alternate" hreflang="en-ca" href="https://example.com/en-ca/products/trail-jacket/" />
<link rel="alternate" hreflang="fr-ca" href="https://example.com/fr-ca/produits/manteau-trail/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/products/trail-jacket/" />Here x-default points at the US page, the version for anyone who matches none of the three, such as someone in the UK. If you run a country selector page, point x-default there instead. The same annotations can go in your XML sitemap instead of the head; pick one method.
The hreflang errors we see most
- Missing return links. The en-ca page references the US page, but nobody updated the US template, usually because Canada launched as a separate project.
- Using “ca” as a language code.
hreflang="ca"means Catalan. Canada always needs a language first: en-ca or fr-ca. - Pointing hreflang at URLs that redirect or are canonicalized elsewhere. Every href should be the final, indexable, 200-status URL. Trailing slash mismatches and http vs https count.
- Annotating pages that do not exist in the other locale. Plugins sometimes output an alternate pointing at a 404 or the home page.
- Different hreflang sets on different versions. The French page lists only itself and en-ca, so the US page is missing from the cluster.
On WordPress, WPML and Polylang generate hreflang for you, which removes typing errors but not the logical ones above. Crawl with Screaming Frog (its hreflang tab flags missing return links and non-200 targets), then use URL Inspection in Google Search Console to see which canonical Google chose.
How canonical and hreflang work together
Each regional page should carry a self-referencing canonical, and hreflang should connect those canonical URLs. Do not canonicalize the en-ca page to the en-us page: that tells Google the Canadian page should not be indexed, which contradicts the hreflang saying it should be shown in Canada.
This is the most common mistake on US/Canada sites, and it comes from good intentions. Someone reads that duplicate content is bad, sees two English pages and “fixes” it with a cross-country canonical. The Canadian URLs drop out of the index and Canadian traffic lands on US prices again.
- Canonical stays within the same locale:
/en-ca/page/canonicalizes to/en-ca/page/. - Filtered or parameter URLs inside a locale canonicalize to that locale’s clean URL, not to the US one.
- Hreflang lists only canonical URLs. If a URL is not its own canonical, it does not belong in the cluster.
- If you decide a Canadian page should not exist separately, remove it from the hreflang set and redirect it, rather than keeping it live with a cross-country canonical.
For the wider crawl and indexing basics behind this, our technical SEO guide to crawlability and Core Web Vitals covers how Google discovers and chooses canonical URLs.
Localize what buyers notice: prices, spelling, addresses
Localization turns two duplicate pages into two useful ones. The en-us vs en-ca differences are small, but buyers spot every one.
Prices in CAD vs USD
Show CAD on Canadian pages and label it (“$49 CAD”), because a bare “$49” is ambiguous on both sides of the border. In Product structured data, set priceCurrency to CAD on the Canadian page and USD on the US page, and make sure the visible price matches the markup. In Google Merchant Center, Canada needs its own feed or country setting with CAD prices; a USD feed will not do. Sales tax wording differs too: Canadian shoppers expect to see GST/HST (and PST or QST where it applies) mentioned at checkout, not US state sales tax.
Spelling and vocabulary
Canadian English uses colour, centre and cheque, and measurements are metric. These details matter more for trust than for rankings, but they also show Google the pages serve different audiences. Pull keyword data per country in Semrush or Ahrefs, because some product terms differ entirely.
Addresses, phone numbers and Google Business Profile
Put your Canadian address and phone number on Canadian pages, if you have them. Both countries share the +1 calling code, so a local area code is what tells a Canadian buyer you are reachable.
Create a Google Business Profile for a Canadian office only if it is a real, staffed location. Virtual offices and mail drops break Google’s profile guidelines and can get listings suspended. With genuine offices on both sides, keep each profile consistent with its location page; our local SEO services page explains how we handle multi-location profiles, and you can see how we structure city pages on our locations hub.
French content for Quebec (fr-ca SEO)
If you sell to customers in Quebec, French content is a legal question first and an SEO question second. Quebec’s Charter of the French Language, as amended by Bill 96 (An Act respecting French, the official and common language of Québec, adopted in 2022), generally requires commercial publications, which can include websites, to be available in French, with French at least as prominent as other languages.
The rules include exceptions and phased dates, and the Office québécois de la langue française (OQLF) handles enforcement. We are not lawyers, so check your situation with counsel before deciding the scope of your French site. What we can speak to is the search side.
- Use fr-ca, not fr. If your French version is written for Quebec, fr-ca is the accurate code.
- Translate the URL slugs.
/fr-ca/produits/manteau-trail/helps both users and search more than/fr-ca/products/trail-jacket/. - Do keyword research in French. Quebec searchers do not always use the terms a translator picks. “Courriel” vs “email”, or France-French vocabulary that sounds wrong in Montreal, are classic examples. Run the French terms through Semrush or Ahrefs with the Canada database, not France.
- Translate everything on the page. Titles, meta descriptions, image alt text, schema, form labels, error messages and checkout. A French page with English menus and an English cart is the most common half-finished version we see.
Machine translation is a reasonable first draft and a poor final one. DeepL and Google Translate get general copy close, then fail on product terms, warranty wording and brand voice. Have a native Quebec French speaker review every template and your top pages at minimum. Google also recommends one language per page for the main content, so leftover English paragraphs send a mixed signal.
On WordPress, the cleanest setups we build use WPML or Polylang with one language per subfolder, translated slugs and per-language menus. If your current theme makes that painful, it is usually a sign the build needs work first; our WordPress development team handles multilingual builds alongside the SEO.
Don’t redirect visitors automatically by IP address
Google advises against automatically redirecting users to a language or country version based on what you think they want. Show a dismissible banner (“Looks like you’re in Canada. View prices in CAD?”) and a visible country/language switcher instead.
The reason is practical. Google’s documentation on locale-adaptive pages notes that Googlebot’s crawl requests mostly come from US IP addresses. If your site sends every US IP to the US version, Googlebot may never see your Canadian or French pages at all. IP-based redirects also trap real people, like a Canadian on a US business trip or a Quebec customer who prefers English.
Check your CDN and plugins too. Cloudflare Workers, Shopify Markets and some WooCommerce geolocation plugins can redirect by country. Make sure every locale URL stays directly reachable and returns a 200.
Measuring each market separately
Report on Canada separately, otherwise US volume hides every Canadian problem. In Google Search Console, filter Performance by country and by the /en-ca/ or /fr-ca/ page prefix. In GA4, compare by country and page path.
Watch for Canadian impressions going to US URLs: it usually means hreflang is broken or the pages are too similar to separate. For a second pair of eyes, our SEO services team audits hreflang clusters, canonicals and country reporting as one piece of work, and our Toronto SEO services cover the Canadian side for businesses based there.
The compact international SEO checklist for USA and Canada
- Decide per page type whether US and Canadian versions genuinely differ; only split where they do.
- Choose a URL structure (subfolders by default, .ca only with a real Canadian marketing budget) and avoid locale parameters.
- Add hreflang for en-us, en-ca, fr-ca and x-default on every version, with return links on all of them.
- Point hreflang only at final, 200-status, self-canonical URLs.
- Use self-referencing canonicals per locale; never canonicalize en-ca to en-us.
- Show CAD prices on Canadian pages, label the currency, and match
priceCurrencyin Product schema and Merchant Center. - Use Canadian spelling, metric units, Canadian tax wording, address and phone number on en-ca pages.
- Create a Google Business Profile in Canada only for a real, staffed location.
- Check your Quebec French obligations under the Charter of the French Language and Bill 96 with counsel.
- Have fr-ca content reviewed by a native Quebec French speaker; translate slugs, metadata, alt text, forms and checkout.
- Remove automatic IP-based redirects; use a banner and a visible switcher.
- Crawl with Screaming Frog for hreflang errors, then confirm Google’s chosen canonicals in Search Console.
- Report Search Console and GA4 by country and locale path, and watch for Canadian impressions landing on US URLs.
FAQ
Do I need a .ca domain to rank in Canada?
No. A .ca is a strong country signal, but a .com with a localized /en-ca/ subfolder and correct hreflang can rank in Canada and keeps your authority on one domain.
What is the difference between en-us and en-ca in hreflang?
Both are English; the region code tells Google which country each version is for. en-us targets English speakers in the US, en-ca targets English speakers in Canada.
Will Google penalize duplicate US and Canadian pages?
No. Similar regional content is not treated as spam. The risk is that Google indexes only one of them, which hreflang and real localization help prevent.
Should x-default point to the US site?
It should point to whatever page best serves visitors who match none of your versions. That is often the US page, or a country selector if you have one.
Is machine translation good enough for fr-ca SEO?
As a draft, yes. As the published version, rarely. Have a native Quebec French speaker review templates, product terms and your most visited pages.
Can I use one page for both the US and Canada?
Yes, when price, availability and terms are the same for both countries. Many informational and B2B pages do not need a Canadian copy.




