Skip to content

Welcome to the Q&A Forum

Browse the forum for helpful insights and fresh discussions about all things SEO.


  • seo tactic seo international seo seo rankings seo expert

    I have a website which I want to rank in UK, NZ and AU and I want to keep my domain as .com in all the countries. I have specified the lang=en now what needs to be done to rank one website in 3 different English countries without changing the domain extension i.e. .com.au or .com.nz

    SEO Tactics | | Ravi_Rana
    0

  • international seo

    I have got an interesting situation where I have a client who wants to merge two ccTLD's into one. They currently have .fi and .com and they want to merge both sites to .com .fi is for finland and .com for USA. They want to merge the sites and the original plan was to use subfolders for each country and pair with hreflang. However the team now wants to merge both sites with NO subfolders differentiating between finland or the US. My understanding of International SEO that this is the most opposite from best practices, but is there any specific reasons why they wouldn't want to do this? I'm struggling to find any specific reasons that I can cite to the client that would argue why we should at least do a subfolder or some sort of international seo strategy.

    International SEO | | JKhoo
    1

  • international seo seo international google rankings

    Hi there, I have a question regarding international SEO and the APAC region in particular. We currently have a website extension .com and offer our content in English. However, we notice that our website hardly ranks in Google in the APAC region, while one of the main languages in that region is also English. I figure one way would be to set up .com/sg/ (or .com/au/ or .com/nz/), but then the content would still be in English. So wouldn't that be counted as duplicate content? Does anyone have experience in improving website rankings for various English-speaking countries, without creating duplicate content? Thanks in advance for your help!

    International SEO | | Billywig
    0

  • redirect 301 redirect 302 international seo

    We need to establish if 301 or 302 response code is to be used for our auto redirects based on Accept-Language header. https://domain.com
    30x > https://domain.com/en
    30x > https://domain.com/ru
    30x > https://domain.com/de The site architecture is set up with proper inline HREFLANG.
    We have read different opinions about this, Ahrefs says 302 is the correct one:
    https://ahrefs.com/blog/301-vs-302-redirects/
    302 redirect:
    "You want to redirect users to the right version of the site for them (based on location/language)." You could argue that the root redirect is never permanent as it varies based on user language settings (302)
    On the other hand, the lang specific redirects are permanent per language: IF Accept-Language header = en
    https://domain.com > 301 > https://domain.com/en
    IF Accept-Language header = ru
    https://domain.com > 301 > https://domain.com/ru So each of these is 'permanent'. So which is the correct?

    International SEO | | fJ66doneOIdDpj
    0

  • canonical international seo

    Hello, we are facing some issues on our project and we would like to get some advice. Scenario
    We run several websites (www.brandName.com, www.brandName.be, www.brandName.ch, etc..) all in French language . All sites have nearly the same content & structure, only minor text (some headings and phone numbers due to different countries are different). There are many good quality pages, but again they are the same over all domains. Goal
    We want local domains (be, ch, fr, etc.) to appear in SERPs and also comply with Google policy of local language variants and/or canonical links. Current solution
    Currently we don’t use canonicals, instead we use rel="alternate" hreflang="x-default": <link rel="alternate" hreflang="fr-BE" href="https://www.brandName.be/" /> <link rel="alternate" hreflang="fr-CA" href="https://www.brandName.ca/" /> <link rel="alternate" hreflang="fr-CH" href="https://www.brandName.ch/" /> <link rel="alternate" hreflang="fr-FR" href="https://www.brandName.fr/" /> <link rel="alternate" hreflang="fr-LU" href="https://www.brandName.lu/" /> <link rel="alternate" hreflang="x-default" href="https://www.brandName.com/" /> Issue
    After Googlebot crawled the websites we see lot of “Duplicate without user-selected canonical” in Coverage/Excluded report (Google Search Console) for most domains. When we inspect some of those URLs we can see Google has decided that canonical URL points to (example): User-declared canonical: None
    Google-selected canonical: …same page, but on a different domain Strange is that even those URLs are on Google and can be found in SERPs. Obviously Google doesn’t know what to make of it. We noticed many websites in the same scenario use a self-referencing approach which is not really “kosher” - we are afraid if we use the same approach we can get penalized by Google. Question: What do you suggest to fix the “Duplicate without user-selected canonical” in our scenario? Any suggestions/ideas appreciated, thanks. Regards.

    International SEO | | Alex_Pisa
    0

  • hreflang international seo

    Hey everybody, We recently migrated our .co.uk to .com/en. Google for some reason is saying that the .com/en version has no hfrelang tags - even though they are clearly there and have had the same implementation as other language versions of the website. We also did a previous migration 6 months ago for the german version of our website and no hreflang problems there. We add our hreflang tags to our sitemap - which you can find here:
    https://camaloon.com/en/web-sitemap.xml Any help or suggestions would be greatly appreciated!! Thanks 🙏

    Technical SEO | | mooj
    0

  • international seo serp features

    How can I be included in http://www.google.com/flights section in Serp for other languages like Persian e.g the keyword: بلیط هواپیما

    International SEO | | fareli
    0

Looks like your connection to Moz was lost, please wait while we try to reconnect.