• Resolved Rajesh Namase

    (@namaserajesh)


    I tried the URL translation option but found these issues:

    1. For hreflang tags we should add proper translated URLs, not English URLs with /lang-code/ in them. Right now, Suppose Google bot visited default English site version, it will check the hreflang tags and will visit example.com/es/english-url/ then when the bot will check the canonical tag of this page it will find the translated version URL. So due to this issue crawl budget is getting hamperd.

    2. In language sitemaps e.g. https://techlila.com/es/post-sitemap.xml we are adding the English URLs with /es/ in it. If we are using the URL translation option then in sitemap too translated URLs should be there. Again due to this issue we are wasting the crawl budget.

    I checked one of my friend’s website who is using this plugin (Pro version) for 8+ months and found that Google has crawled some non-translated URLs and some translated URLs.

    Please advise how to tackle these issues?

    • This topic was modified 2 years, 4 months ago by Rajesh Namase.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author edo888

    (@edo888)

    Hi,

    I would not call it an issue, it is an architectural choice.

    Your original website does not store any translation info on your side. If you want to have the translated URL info then it is required to store it somewhere or pull it via network. We do not store anything on your original website and pulling it will cause performance issues on your original version, so stay away from it.

    Using canonical works just fine and we do not want to complicate things.

    Account age has nothing to do with the page age. It is possible that Google can index the non translated version of the URL, but it will be replaced with the translated URL when it discovers the canonical.

    Crawl budget is a very liquid term in my opinion. If you have quality content, then Google will index it over time, I do not think we are on a rush.

    Thanks! 🙂

Viewing 1 replies (of 1 total)
  • The topic ‘URL Translation Option Issues’ is closed to new replies.