How does TranslatePress handle URL slug translation

Manual Slug Translation

Manual translation is ideal for users who have a few specific posts, pages, or products they want to translate. Here’s how it works:

1. Accessing the Translation Interface: Users navigate to the post, page, or product they want to translate. They then click the "Translate Page" button in the WordPress admin bar to open the TranslatePress visual interface.

2. Translating the Slug: If the SEO Pack add-on is activated, the interface will display SEO meta information and URL slugs. Users select the slug they want to translate from the dropdown menu and enter the translation in the sidebar.

3. Saving the Translation: After saving the translation, the next time the page is refreshed in another language, the translated version of the URL slug will appear[1][4].

Automatic Slug Translation

For users who prefer a more streamlined process, TranslatePress offers automatic slug translation:

1. Enabling Automatic Translation: Users go to the Settings → TranslatePress and click on the Automatic Translation tab. They then enable the "Automatically Translate Slugs" option.

2. Configuring Translation APIs: TranslatePress supports various translation APIs, including Google Translate v2, DeepL, and its own AI engine. Users need to create an account with the chosen API provider and obtain a key to use these services[3][4].

3. Slug Translation Process: Once enabled, automatic translations for slugs will be generated for posts, pages, and custom post types. The translation occurs starting with the second refresh of each page[3].

SEO Pack Add-on Requirement

Both manual and automatic slug translation require the SEO Pack add-on, which is available in all premium plans of TranslatePress. This add-on not only facilitates slug translation but also enhances SEO capabilities for multilingual sites[1].

Limitations and Workarounds

While TranslatePress handles most slug translations effectively, it does not natively support translating taxonomy or custom post type root slugs. Users may need to use custom solutions, such as `.htaccess` rewrite rules, to achieve this functionality[5]. However, the plugin does support translating taxonomy slugs and terms, which is crucial for multilingual SEO.

In summary, TranslatePress provides a robust solution for translating URL slugs in WordPress, offering flexibility through both manual and automatic methods, though it may require additional workarounds for certain advanced use cases.

Citations:
[1] https://translatepress.com/translating-url-slugs/
[2] https://translatepress.com/docs/translation-function/
[3] https://translatepress.com/docs/automatic-translation/
[4] https://translatepress.com/translate-a-web-link/
[5] https://wordpress.stackexchange.com/questions/357286/translatepress-taxonomy-and-custom-post-type-root-fix

How does automatic translation work for URL slugs in TranslatePress

Automatic translation for URL slugs in TranslatePress involves a few key steps and requires the SEO Pack add-on. Here’s a detailed overview of how it works:

Requirements for Automatic Slug Translation

1. SEO Pack Add-on: This feature is only available with the SEO Pack add-on, which is included in all premium plans of TranslatePress. The add-on enhances SEO capabilities for multilingual sites and allows for the translation of URL slugs.

2. Translation API Integration: To enable automatic translation, you need to integrate a translation API. TranslatePress supports several APIs, including Google Translate v2, DeepL, and its own AI engine. You must create an account with the chosen API provider and obtain a key to use these services.

Steps for Automatic Slug Translation

1. Enabling Automatic Translation:
- Navigate to the Settings → TranslatePress in your WordPress dashboard.
- Click on the Automatic Translation tab.
- Enable the "Automatically Translate Slugs" option. This option tells TranslatePress to automatically generate translations for URL slugs when they are not manually translated.

2. Configuring Translation APIs:
- In the same settings area, you will find options to configure your translation API. You need to enter your API key and select the translation engine you prefer.
- Ensure that the API has sufficient credits or capacity to handle the volume of translations you need.

3. Translation Process:
- Once automatic slug translation is enabled, TranslatePress will generate translations for URL slugs when a page is visited in a language other than the default.
- The translation process typically occurs on the second refresh of each page. This delay ensures that the initial page load is not slowed down by the translation process.

4. Caching Translations:
- To improve performance, TranslatePress caches the translated slugs. This means that once a slug is translated, it is stored locally and reused instead of being re-translated every time the page is loaded.

Limitations and Considerations

- Taxonomy and Custom Post Type Root Slugs: TranslatePress does not natively support translating taxonomy or custom post type root slugs. Users may need to use custom solutions, such as `.htaccess` rewrite rules, to achieve this functionality.

- SEO Impact: While automatic translation can save time, it's essential to review and refine translations for SEO purposes. Automatic translations might not always perfectly capture nuances or context-specific terms.

- API Costs: Depending on the translation API used, there may be costs associated with automatic translations. Ensure you understand the pricing model of your chosen API to avoid unexpected expenses.

In summary, automatic URL slug translation in TranslatePress is a convenient feature that streamlines the process of creating multilingual content. However, it requires careful setup and consideration of potential limitations and costs.

How do I manually translate URL slugs in TranslatePress

Manually translating URL slugs in TranslatePress is a straightforward process that allows you to have full control over the translations. This method is particularly useful when you want to ensure that your URL slugs are accurately translated and optimized for SEO. Here’s a step-by-step guide on how to manually translate URL slugs:

Requirements

1. TranslatePress Plugin: Ensure you have the TranslatePress plugin installed and activated on your WordPress site.

2. SEO Pack Add-on: Manual slug translation requires the SEO Pack add-on, which is available in all premium plans of TranslatePress. This add-on enhances SEO capabilities for multilingual sites and allows for the translation of URL slugs.

Steps to Manually Translate URL Slugs

1. Access the Translation Interface:
- Navigate to the post, page, or product you want to translate.
- Click the "Translate Page" button in the WordPress admin bar to open the TranslatePress visual interface.

2. Select the Language:
- In the translation interface, select the language you want to translate into from the dropdown menu at the top.

3. Translate the Slug:
- If the SEO Pack add-on is activated, you will see a section for SEO meta information and URL slugs. Click on the slug field to edit it.
- Enter your manual translation for the URL slug in the provided field. Ensure it is descriptive and optimized for SEO.

4. Save the Translation:
- After entering the translated slug, click the "Save" button to save your changes.

5. Review and Test:
- Visit the translated page to ensure the slug is correctly displayed in the URL. You can also test it by copying and pasting the URL into a browser to verify that it loads correctly.

Tips for Manual Slug Translation

- SEO Optimization: When manually translating slugs, focus on SEO optimization by using relevant keywords that match the content of the page.

- Consistency: Ensure consistency in your slug translations across different languages to maintain a professional appearance and improve user experience.

- Character Limitations: Be mindful of character limitations for URL slugs, as overly long slugs can be truncated or cause issues with certain browsers or platforms.

- Special Characters: Avoid using special characters in slugs whenever possible, as they can lead to encoding issues or make URLs harder to read.