Why a Negative Word Is Not Enough to Classify Brand Sentiment
When you measure how people talk about a brand, a negative word such as “awful” or “broken” seems like clear evidence of…
Categories
How to Keep Hreflang and Canonical Links Consistent
For international SEO, websites use hreflang annotations and canonical links to help search engines interpret pages that target different languages or regions. A canonical link names the preferred URL for duplicate or very similar pages. An hreflang annotation connects versions of a page and identifies the language or region each one targets.
Keep these signals aligned: make each intended language or regional page canonical to its own preferred URL. Then make every hreflang annotation point to the preferred URL for the language or region it describes. This helps search engines distinguish genuine localized pages from duplicate URL versions. It does not guarantee which page a search engine will index or show.
Give each locale one preferred URL
Choose one URL for each language or regional version (locale), then use it consistently in the page’s canonical link, hreflang annotations, internal links, and sitemap. A self-referencing canonical is the usual choice when a locale page is the preferred version of its own content.
For example, if a site has distinct US and UK product pages, each page can identify itself as canonical while listing both locales:
<!-- On https://example.com/en-us/product/ -->
<!-- On https://example.com/en-gb/product/ -->
The canonical and hreflang URLs on a page do not all need to match. The canonical identifies that page’s preferred URL; each hreflang URL identifies a preferred destination for a particular locale. The hreflang set should include the page itself and its relevant alternatives, and each page in the set should link back to the others. Google says missing return links can prevent it from interpreting the annotations correctly. See its guidance on localized page versions.
Regional pages in the same language can remain separate when they serve distinct regional needs. For translated pages, do not canonicalize every locale to the original-language page simply because that page came first. Google recommends a canonical in the same language, or the best available substitute if no same-language page exists. Its canonicalization guidance also distinguishes translated pages from same-language regional pages.
Keep duplicate URLs out of the hreflang set
A page may have a short alias or a URL with a parameter. Its trailing-slash version can also have a separate URL. If two URLs serve the same locale content and one is the preferred version, point the duplicate to that preferred URL with a canonical link, or redirect the duplicate when it no longer needs to remain available.
Then use the preferred URL in hreflang, internal links, and the sitemap. For example, if /uk/product/ duplicates /en-gb/product/, hreflang should identify /en-gb/product/ as the UK destination. Sending users and search engines through an alias or redirect makes the intended destination less clear.
Check that the locale pages genuinely belong in the same hreflang set. A language label does not make pages equivalent: each destination should serve the language or region specified by its annotation. If you need to diagnose a canonical that points to the wrong page, see how incorrect canonical URLs can hide the page you want search engines to use.
Audit the declared links and Google’s selected canonical
Start with the preferred URL for each language or regional page. For each page, check its server response and declared canonical. Then inspect its hreflang destinations and whether those pages link back. Confirm that people and search engines can access the intended URLs, and that the sitemap and internal links use the same URL format.
| Check | What to verify |
|---|---|
| Canonical | The page points to its intended preferred URL, or a true duplicate points to that URL. |
| Hreflang set | Each page lists itself and the relevant locale alternatives using preferred URLs. |
| Return links | The other locale pages link back to the same set. |
| URL response | Each hreflang destination loads the intended page rather than redirecting to another URL. |
| Other signals | Internal links and sitemap entries use the preferred URLs. |
| Google’s selection | URL Inspection shows whether Google selected the canonical the page declares. |
Inspect the HTML source or relevant HTTP headers to see what the site sends. Google supports hreflang in HTML, HTTP headers, and XML sitemaps; maintaining all three does not provide an additional Search benefit. Choose the method your site can keep accurate. For canonical signals, avoid declaring conflicting preferences through different methods.
A declared canonical tells Google which URL the site prefers, but Google makes the final choice. Google considers it along with other signals, including redirects and sitemap entries, and may select a different URL. Use Search Console’s URL Inspection to compare the declared canonical with Google’s selected canonical. If they differ, check the redirects, canonical tags, sitemap entries, and server behavior. Also check whether the pages are duplicates. Google’s canonical troubleshooting guidance outlines these checks.
Fix the mismatch that the evidence shows
If every translated page points its canonical to the source-language page, the site signals that the source page should represent those URLs. That conflicts with using the translations as separate locale destinations. Give each distinct locale page an appropriate canonical instead, and use those preferred URLs in hreflang.
If hreflang points to a redirect or duplicate alias, replace the target with the final preferred URL. If one locale page omits a return link, update the set so the relevant pages point to one another. If the page source, sitemap, and internal links use different URL formats, choose one format and align them.
A mismatch in the page’s tags tells you what the site declares. A different canonical in URL Inspection tells you Google selected another URL. Neither result by itself proves a ranking or traffic change. Google documents how canonicalization and hreflang work, but its guidance does not quantify a ranking gain from correcting these signals.
Bing says its AI experiences build on search crawling and indexing, which supports keeping preferred page URLs clear. That does not establish that hreflang-canonical fixes independently increase AI citations, rankings, or visits. Bing’s discussion of duplicate content and AI search visibility offers guidance but does not test this implementation under controlled conditions.
Key Takeaways
- Choose one preferred URL per locale and use it in the canonical, hreflang set, sitemap, and internal links.
- Keep hreflang reciprocal: each locale page should list itself and the relevant alternatives, and those pages should link back.
- Canonicalize true duplicates to the preferred URL for that locale; do not send translated pages to the source-language URL by default.
- Compare declared and selected canonicals in Search Console, then investigate redirects and other conflicting URL signals if they differ.
- Treat SEO and AI outcomes separately: Google documents the mechanisms, but its guidance neither quantifies ranking gains nor proves more AI citations.
What I'm buildingDelegate tasks. Get software.
Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.
Take a look at vroni.com