TranslateWP translates a page the first time someone visits it in a language, then stores the result in its translation cache. Later visitors get the cached translation straight away. When you edit the original page, the changed text is translated again on the next visit. TranslateWP adds no translation tables and no duplicate pages to your site.
What happens on the first visit?
- A visitor opens a page in a new language.
- TranslateWP extracts the translatable content and requests a translation.
- The page updates while the result loads.
- The successful translation is stored in the cache.
What happens on later visits?
Later visitors receive the cached result instead of creating the same request again. Your front page and menu pages are prepared at setup, so they are usually cached before anyone visits. See Warm up key pages.
When is a page translated again?
- You change the original text.
- The cache expires or is refreshed.
Caching questions
Will TranslateWP slow my site down? Only the first visit in a language waits for a translation. Later visits reuse the cache. Actual speed depends on your content, your caching and service availability.
Does it work with my page-cache plugin? TranslateWP recognises LiteSpeed Cache, WP Rocket, W3 Total Cache, WP Super Cache, SiteGround Speed Optimizer and WP Fastest Cache. It clears their cache when needed, and keeps its script out of the “delay JavaScript” and “defer” options of WP Rocket, LiteSpeed Cache and Perfmatters. You don’t need to exclude pages.
Do I need to set anything up? Make sure your cache keeps each language address separate, such as /about/ and /de/about/. Clear any CDN or edge cache, such as Cloudflare, yourself. If a translated page shows old text, TranslateWP shows a notice that says where to purge the cache.
Where are translations stored? In TranslateWP’s translation service, not in new database tables on your site.