Google 代表 John Mueller 指出，在網址中使用特定的國家代碼路徑（如 /en-us/）與通用路徑（如 /blog/）之間，並不存在實質上的 SEO 排名差異。雖然採用細分的資料夾結構有助於管理員在數據分析時更精確地篩選指標，但對搜尋引擎而言效果相當。此外，專家建議應盡量避免在不同地區版本中放置完全重複的內容，以減少標準網址判定上的混淆。若發生內容重疊，Google 通常會透過 hreflang 標記來確保不同地區的搜尋用戶能看到正確的頁面版本。
原始對話
John responded in full:
IMO the advantage of using /en-us/blog/ instead of /blog/ for US content (on an internation site that uses /LL-CC/anything URL patterns) is that it’s easier for you to filter & slice your metrics by country/language. I don’t think you’d see a practical SEO difference between using /blog/ or /en-us/blog/ for your US content. /blog/ looks nice, but /en-us/blog/ is also not super-weird.
Regarding different country / same language content, that can happen is that we see them as identical and pick a canonical for them, but then use hreflang to show the right URL. It will look confusing in Search Console, but it should work out. In general, I’d avoid using exact duplicate content across hreflang versions because of that (it just makes your life easier).
For example, you might consider having just an English version of informational content, and if there’s something country-specific (e.g., products for sale with different availability/currencies), then do those on a per-country basis. Obviously, this is more work, and depending on your site it might not be feasible. Alternatively, like you mentioned, making sure the English versions are localized per country also helps to avoid them being seen as duplicates. In the worst case, if they are considered duplicates, then usually hreflang results in the right URLs being shown in Search, regardless (but Search Console reporting will be on the canonical URL).
