Do internal links point to the translated pages?
On this page
A typical case: your Home page contains a link to Contact. You translate both pages into French. On the French Home page, the link should lead to the French Contact page, not to the English one.
Link handling belongs entirely to WPML’s translation layer. LATW only supplies the translated text through your own AI provider (BYOK) inside WPML’s normal translation flow, so link behaviour is identical whether you translate manually, with WPML credits, or with LATW.
#How it works
When content is sent through WPML’s Translation Editor, WPML detects internal links in that content and rewrites them so they point at the corresponding translation. You don’t need to set the URL for every link by hand.
Two conditions have to be met:
- The target page must already be translated.
- The link has to be part of the translated content.
#Fixing links that already point to the wrong language
If a link ended up pointing at the original language:
- Re-send the page for translation.
- Or run WPML → Settings → Translate Link Targets → Scan now and adjust links. This scans the site and rewrites internal link targets to the correct translations. It is a full-site operation, there is no way to scan only selected pages, and it can be slow on large sites, so take a backup first.
#Menus
Menus use a separate mechanism:
- Menu items linking to content (pages, posts, categories): just translate the content they link to. The menu follows automatically.
- Custom Links in menus: these hold a raw URL, so you have to add a translated Custom Link for each language yourself.
- Block-based menus (Navigation block in the Site Editor): translate the corresponding template part and the navigation block from the Translation Dashboard.
#Where automatic link conversion does not apply
Links stored in ACF fields are not automatically re-pointed to the translated page. This is the most common surprise on custom-built themes.