Same flag as the earlier pages: “RM50 enrollment fee,” “SOP,” and the whole pricing/comparison table structure are dense, numbers-heavy content — worth a careful proofread pass once pasted in, since misaligned pricing figures across three languages (e.g. a wrong RM amount in the Malay version) is a much costlier mistake on a pricing page than on a testimonial.

Straight answer: the tedium isn’t really about translation quality — it’s a documented Polylang + Elementor gap. Polylang’s own docs state Pro isn’t natively compatible with Elementor, and even with the third-party “Polylang Connect for Elementor” bridge plugin, DeepL/automatic translation still doesn’t reach into Elementor widget content. So on your current stack, manually pasting into every widget isn’t a workaround you’re doing wrong — it’s currently the only path Polylang offers for Elementor pages.

Here are your actual options, ranked by how much they solve the real problem:

1. Switch to TranslatePress (biggest actual fix)
TranslatePress works fundamentally differently — instead of duplicating your page as a separate WP post (Polylang’s approach, which is also what caused your boxed-hero bug earlier), it overlays a live front-end editor on top of however your page actually renders. Since it reads the rendered output rather than the underlying post structure, it works with Elementor content out of the box, no compatibility bridge needed. It also has real automatic translation built in — Google Translate is free, DeepL/AI-engine translation is on paid tiers — so you could run the auto-translate pass across your whole site in one go, then just manually correct the handful of lines that came out awkward (which will still include things like your myopia-claim wording, since machine translation won’t fix content/legal issues, just language).

The catch: switching means migrating off Polylang, which means rebuilding your language setup and losing the manual work you’ve already put into linking pages/menus. Worth it if you’re translating aggressively going forward, less worth it if you’re 90% done already.

2. Stay on Polylang, add AutoPoly
There’s a dedicated add-on called AutoPoly — AI Translation For Polylang, built specifically to solve this exact gap. It duplicates your pages/posts and auto-translates the content (including images/galleries/meta) into your target language, and is built to work with Elementor specifically. This is the lower-disruption option since it keeps your existing Polylang setup, menu links, and everything you’ve already built — it just automates the page-duplication + translation step instead of you copy-pasting per widget.

3. Keep doing it manually, but batch it better
If you don’t want to touch your plugin stack at all: instead of translating page-by-page as you’ve been doing in this thread, export all your remaining English copy into one document, run it through a single translation pass (which is exactly what I’ve been doing for you here), then do one dedicated pasting session per language rather than context-switching between translate-then-paste every time. It won’t remove the manual Elementor work, but it removes the back-and-forth overhead.

Given how much translation work you clearly still have left (course pages, pricing page detail, remaining FAQ answers, footer variants), I’d lean toward option 2 (AutoPoly) — it keeps everything you’ve already built in Polylang, directly targets the Elementor gap, and turns “manually paste into every widget” into “review what the AI already pasted.” Option 1 is the technically cleaner long-term answer but only worth the migration cost if this site is going to keep growing content-wise after launch.