大网数据广告活动
网站运营与故障问答

Internationial SEO with different alias domains

· 52CE 我爱测

Imagine I'm proprietor of two domains that are alias, i.e., they point exactly to the same server and folder: exemple.com and exemplo.com However, in that server I detect the country of the user, so that, for example: in UK it po…

问题原文

原帖链接 · João Pimentel Ferreira · CC BY-SA 3.0

Imagine I'm proprietor of two domains that are alias, i.e., they point exactly to the same server and folder: exemple.com and exemplo.com

However, in that server I detect the country of the user, so that, for example:

  • in UK it points to /index_en.html

  • in Spain it points to /index_es.html

Question: Which option is the best internationial SEO practise?

  1. allow the crawling of the four combinations,
  2. restricting only to exemple.com/index_en.html and exemplo.com/index_es.html and block exemple.com/index_es.html and exemplo.com/index_en.html avoiding thus crawling duplication, or
  3. do not crawl alias and focusing only on one domain, for example example.com and simply make a permanent 301 forwarding from exemplo.com to example.com

已采纳解答

原帖链接 · Dave Sottimano · CC BY-SA 3.0

Edit based on Joao's comment*

The domains in question are cctld, i.e .es, .it, .pt. Geotargeted subfolders on country specific domains don't work well, if the top level domain is generic (i.e. .com) this solution works. Otherwise, from a pure "best for ranking" perspective, keeping cctlds that only serve one country is best, but, like every solution, each has it's drawbacks such as additional technical overhead and having to market/optimize each cctld independently rather than consolidating signals to one domain (subfolder approach).

Edit end

Great question, I don't fully understand your setup but I think this should describe it and how to deal with it:

Where...

exemple.com/index_en.html === exemplo.com/index_en.html && exemple.com/index_es.html === exemplo.com/index_es.html

Setup:

Your 3rd option is best, use 301 redirects to redirect all pages from exemplo.com to exemple.com on a 1:1 basis, i.e. redirect each page to its equivalent. You should determine which domain is the preferred domain by checking which one ranks better/gains more traffic (the preferred domain should also have higher external link count and links from decent websites)

The preferred domain in this hypothetical scenario will be exemple.com. When a request originating from a UK IP to exemple.com, you will 302 redirect them to exemple.com/index_en.html.

A request originating from Spain with a Spanish IP to exemple.com should 302 to exemple.com/index_es.html.

That would be it - don't redirect any other requests on the domain, use hreflang to annotate the spanish and english versions accordingly.

I did the Redbull.com setup and a friend of mine did theguardian.com. We followed Google engineer's advice despite doubting the 302 redirect. The hreflang lead, Christopher Semturs confirmed in a comment on a post I wrote here.

I would highly advise you take precaution when consolidating your domains (vigoriously check google search console, run crawls, etc..) and test the international configuration (be ready to roll back immediately) as well.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2017-02-25)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。