Some thinking after testing
-
1.Bought the paid version last night and tested. basically it’s smooth in function, but when i translated the homepage into some language(for example, greek), then i clicked a product on the homepage to the product page, the url was changed to mydomain.com/el/English-product-name, but nothing happened. The translation stopped. I tried to refresh the page, nothing again. On this page, if i change to some other language, for example, french, translation started again. Then i click Greek language, nothing, still English product content. My default language is English, so why is that? Am i missing something?
2. By the way, i couldn’t understand very much about the plugin settings. I suggest you can give example in the setting, so it’s easier to understand. For example: Rewrite language URL, instead of this long description—The translated pages will have a specific URL corresponding to the translated language. This can be useful for visitors who have URLs that identify the current language and for search engines that can index pages by language and make search engines index real multilanguage URLs that can also be automatically translated by enabling the ‘Auto-translate detected language’ option. It can be simpler and straight forward: Add language short code in the url of the translated pages, eg. Translated english page will be yourdomain.com/en/, better for search engine index and visitor browsing. similar to other settings, it’s a bit too thechnical.
3. The header contents and footer contents for most pages are the same, every time it will be translated again and again for every page and every language. Is there better solution? since the translation has been stored in database, why it needs to be translated again and again?
We just uninstalled Translatepress and tried GPtranslate, it’s much more efficient and affordable. Hope this product becomes better and better.
-
Hi there! Thanks a lot for choosing GPTranslate Pro and for the thoughtful feedback. I’ll address your three questions below and include a quick checklist to get you fully sorted.
1) Greek product page shows /el/English-product-name but content stays English
That behavior could come from a settings combinations. The plugin by default works by propagating the selected language also for navigated pages.
It must work as on the demo site: https://gptranslate.storejextensions.org/, if you choose Greek for the home page, then navigate to a different page post, it’s again translated into Greek. Eventually you can start from scratch with all default settings in the case something has been messed.
2) Settings wording feels too technical
Great point—and thank you. We’ll simplify the labels in the next update. For now, here’s the short version you can rely on in the UI:
Rewrite language URL: “Add a language code in URLs (e.g., /en/, /el/) for SEO and clearer navigation.”
3) Headers/footers re-translated on every page
As of now GPTranslate stores strings and reuses them automatically for each page, as you see each page is handled separately by other ones. So it’s not possible to reuse parts of other pages like the header/footer. Eventually this could be a feature to develop for next releases.
We really appreciate the comparison with TranslatePress—our goal is exactly what you noticed: efficient, affordable, and now powered by ChatGPT-5.
GPTranslate is actively developed and will become more and more powerful in next months, a crawler engine will be available in next release along with other improvements, additionally it will be soon launched at WPTuts.
Thanks again for your trust and feedback!
The topic ‘Some thinking after testing’ is closed to new replies.
