TranslatePress-translated pages get language-scoped meta, hreflang, and translated schema fields.
By Cozmoslabs
No — WBP layers on top. If TranslatePress exposes its own SEO fields, WBP reads them, keeps them, and only fills the gaps TranslatePress does not cover.
No content is rewritten. WBP writes to head tags, schema JSON-LD, and redirects — the TranslatePress markup on the page is untouched.
No. WBP writes at the WordPress head hook, so TranslatePress's cached HTML body stays valid and no rebuild is needed.
Grab WpBulkPublishing — the compatibility layer is included, no extra add-on.
Get WpBulkPublishingHreflang, canonical, and translated meta are handled per language — no duplicate-content ambiguity.
WeglotWeglot subdirectories or subdomains are added to hreflang and per-language canonical automatically.
Polylang ProPolylang Pro supplies the per-locale post metadata that WpBulkPublishing turns into hreflang clusters, per-language sitemaps and localized JSON-LD.
TranslatePress ProTranslatePress Pro supplies the per-locale post metadata that WpBulkPublishing turns into hreflang clusters, per-language sitemaps and localized JSON-LD.
MultilingualPressMultilingualPress supplies the per-locale post metadata that WpBulkPublishing turns into hreflang clusters, per-language sitemaps and localized JSON-LD.
Loco TranslateLoco Translate supplies the per-locale post metadata that WpBulkPublishing turns into hreflang clusters, per-language sitemaps and localized JSON-LD.