translate slug …. first!

  • Resolved fff654

    (@fff654)


    4 months, 3 weeks ago

    Hi,

    More like a feature request: it would be great to translate the slug ASAP (ie automatically when post is saved), and that to all languages registered in the backend in one go, rather than waiting that some visitor visit each language version.
    From my experience, with the current process, because of the ping made my most SEO plugins, google or bing are frequently the 1st visitor (they say “some days”, but if your site has frequent updates or good history, it is almost instantaneous), indexing the NOT translated slug …. making later a SEO error or redirect needed … = BAD
    I would say the slug is translation priority #1 by far

    That could even benefit from some independent translation toggle in the backend (when automatic translation is disable, slug is not necessary disable either, at least with an independent choice)

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Daniel

    (@danieldandu)

    4 months, 3 weeks ago

    Hi @fff654,

    Thank you for your message.

    At the moment, slug translations are generated only when the translated version of a page is accessed for the first time, whether by a visitor or a bot. Unfortunately, there isn’t a quick fix available yet to automatically translate slugs for all languages immediately when a post is saved, nor a separate toggle to handle slug translation independently.

    As a workaround, we recommend manually visiting the translated version of the page right after publishing, which triggers the translation before search engine bots index it.

    We’ll take this into account when evaluating future improvements.

    Thread Starter fff654

    (@fff654)

    4 months, 3 weeks ago

    As all saving and editing posts, the first post save is rarely the only one. So I am rarely faster than the indexing engine. Not to say also that post creation can be automatic and/or in batch. So your method does not work in all these cases, and tedious anyway if several 6-7 languages.

    I never said it would be a quick fix, but a feature request. But something not huge compared to what you have already:

    • hooking to the existing post save
    • looking if not already translated (optional; only if your translation function in #3 does not look that already)
    • iterating through all registered languages to use your translation function with the slug

    The longest is possibly implementing 1 or 2 toggles in the backend to activate this function or not.

    Plugin Support Daniel

    (@danieldandu)

    4 months, 3 weeks ago

    Hi @fff654,

    I’ve shared your suggestion with our development team for consideration in future updates. Detailed feedback like yours helps us improve the product more effectively.

    We appreciate you taking the time to share your ideas and insights. Thank you!

    Thread Starter fff654

    (@fff654)

    2 months, 3 weeks ago

    your latest update rocks (automatic language selection and translation starting) = small bits that do increase the workflow when translating many posts in many languages. Thanks a lot.

    Plugin Support Daniel

    (@danieldandu)

    2 months, 3 weeks ago

    Hi @fff654,

    Thank you for your feedback! I’m glad the latest update is helping make your workflow easier.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.