Plugin translation is where most sites lose maintainability. Do it wrong once and every update wipes your work.
- Never edit source PO files — use a child language folder.
- Loco Translate for solo work.
- WPML/Polylang for full multilingual sites.
One client edited PO files inside the plugin folder. Every update wiped 6 languages. We migrated to wp-content/languages and never lost a string again.
- Use wp-content/languages/plugins/
- Never edit inside the plugin folder
- Commit .po + .mo together
- Test with WP_LANG override
Inside WBP Omni SEO Pro: Dynamic XML & News Sitemaps
Auto-generated index sitemaps split by post type, language and freshness, with per-URL priority, hreflang alternates and a News sitemap for time-sensitive content.
Why this matters for "Translating a WordPress Plugin the Right Way (2026)": A single flat sitemap at scale slows discovery and hides freshness signals from crawlers and LLM indexers.
- 1Step 1
SEO Features → Sitemap → Enable index sitemaps
- 2Step 2
Split by CPT, language and updated-in-last-48h
- 3Step 3
Ping IndexNow + Bing + Google on publish
- 4Step 4
Expose the News sitemap only for CPTs you mark as news
"Discovery is a solved problem; the plugins that still ship one flat sitemap just haven't updated the solution."
— WBP Omni SEO Pro
Quick pre-publish checklist
- Primary entity named in the first 100 words
- Every H2 maps to a real user question
- Schema validated in Rich Results Test
- At least 3 inbound internal links from related pillars
- Canonical set explicitly, not inferred
- FAQ present when 3+ questions are genuinely answered
A realistic rollout timeline
- Week 1
Scan the site, snapshot current state, agree the approval workflow.
- Week 2
Apply the first batch of critical fixes with rollback points enabled.
- Weeks 3–4
Re-crawl, verify, start attribution against GSC + AI citation logs.
- Weeks 5–8
Move to steady-state: weekly scan, weekly approval, monthly review.
"The unit of SEO work stopped being a report and started being a merged change. Everything else is theatre."
— WBP Editorial
Paired module: Entities & Knowledge Graph Linking
Detects entities in your content, links them to Wikidata/Wikipedia/your Fact Bank and emits sameAs and mentions properties into the schema graph. LLMs cite pages they can disambiguate — entity linking is how you tell them exactly what you mean.
- Enable Entities under Brand Authority
- Review detected entities with confidence scores
- Attach sameAs targets from Wikidata or your Fact Bank
- Publish — sameAs propagates into the page @graph automatically
Loco or WPML?
Loco for translation. WPML for full multilingual content.
Why do translations disappear?
You edited inside the plugin folder. Move to wp-content/languages.
Do I still need to submit sitemaps in GSC?
Submit the index sitemap once. WBP keeps children current and pings IndexNow on every change, so GSC re-fetches without manual resubmits.
Do I need to hand-curate every entity?
No — high-confidence entities auto-attach on save; only ambiguous ones enter the review queue. You can also lock brand entities so they never require review.
Ship this workflow inside WordPress
WBP Omni SEO Pro turns every playbook on this blog into an approvable, reversible diff.
Get WBP Omni SEO ProAffiliate — this link goes to the official WBP Omni SEO Pro product page.
