Use URL for secondary language but not translated

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is using WPML for a WordPress site and is concerned about the SEO impact of using /EN/ URL segments for pages that are not translated into English.
Solution:
We recommend continuing to use the fallback option for untranslated pages. WPML informs Google that these /EN/ pages are displaying the default content temporarily, which prevents them from being seen as duplicate content. This approach will not negatively affect your site's SEO. If you translate these pages later, Google will recognize and index the new content accordingly. For more details, you can check our documentation here: Displaying Untranslated Content on Pages in Secondary Languages.

If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Documentation request

This topic contains 1 reply, has 2 voices.

Last updated by Noman 7 months, 3 weeks ago.

Assisted by: Noman.

Author	Posts
November 2, 2024 at 8:41 am #16356401
henkt-2	<b>Background of the issue: </b> I am using WPML for my WordPress site hidden link, which has two languages: primary Dutch and secondary English. About 70% of the content is translated to English. <b>Symptoms: </b> 30% of the pages have a URL segment with /EN/ but they are not translated. <b>Questions: </b> Can you advise me on using /EN/ for non-translated pages? I've read the documentation but I can't make a decision, I don't have enough experience to see the impact of a certain decision.
November 3, 2024 at 10:18 am #16357664
Noman WPML Supporter since 06/2016 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Hi, Thank you for contacting WPML Support. I totally get your concern about the SEO impact of using fallback content for untranslated pages. The good news is, using the fallback option won’t hurt your site SEO. WPML lets Google know that these /EN/ pages are just showing the default content for now, so Google doesn’t see them as duplicates. And if you decide to translate these pages in the future, Google will pick up the new content without any issues. So, you’re safe to keep using the fallback option without worrying about any negative SEO effects. Here is a doc for more details: https://wpml.org/documentation/translating-your-contents/displaying-untranslated-content-on-pages-in-secondary-languages/ Please let me know if this clears things up or if there’s anything else I can help with! Thank you
November 3, 2024 at 7:41 pm #16358395
henkt-2	Thanks for your answer. This helped.