# MultilingualPress

> Multilingual WordPress for enterprise. Powered by WordPress Multisite. Native performance, no lock-in. Built by Syde.


## search

- [Search the documentation](/search.md)

## docs

- [Documentation](/docs.md): MultilingualPress documentation. Redirects to the documentation home.
- [Alternative Language Title](/docs/concepts/alternative-language-title.md): What the Alternative Language Title module does: set a custom, per-language site title that appears in the WordPress admin toolbar so you can tell your language sites apart.
- [Block Editor (Gutenberg)](/docs/concepts/block-editor.md): The block editor (Gutenberg) is MultilingualPress's main development focus and recommended content editor: versatile, native, and suited to professional needs.
- [Building a multilingual WooCommerce store with MultilingualPress](/docs/concepts/building-a-multilingual-woocommerce-store.md): Why WordPress Multisite plus MultilingualPress is a clean, scalable way to run a multilingual WooCommerce store, with per-site store settings.
- [The command line (MLP-CLI)](/docs/concepts/command-line.md): What the MultilingualPress WP-CLI integration is, when to reach for it instead of the admin UI, and where it fits in a Multisite network.
- [Common questions about MultilingualPress](/docs/concepts/common-questions.md): Answers to the questions customers ask most: licensing, billing, requirements, connecting content, language switching, WooCommerce, and migration.
- [Debug Logging](/docs/concepts/debug-logging.md): What the Debug Logging module records, exactly where the log file is written, why the folder may not exist yet, and how to produce a log for a support ticket.
- [Domain mapping with WordPress Multisite](/docs/concepts/domain-mapping.md): What domain mapping is in WordPress Multisite, why it matters for multilingual sites, and how it works end to end.
- [What enterprise-grade software means for MultilingualPress](/docs/concepts/enterprise-grade-software.md): Why MultilingualPress is built enterprise-first: ruthless quality standards, a deliberately lean frontend, an API-first architecture you build on top of, and a strict stance on code quality and AI-generated code.
- [How AutoTranslate works](/docs/concepts/how-autotranslate-works.md): What AutoTranslate does with your content: which fields it sends, which provider it sends them to, and where the translated text is written back.
- [How MultilingualPress handles ACF integration](/docs/concepts/how-mlp-handles-acf.md): How the ACF module lets MultilingualPress copy Advanced Custom Fields data between connected sites, and why field groups must match.
- [How MultilingualPress handles URLs in post content](/docs/concepts/how-mlp-handles-urls-in-content.md): MultilingualPress rewrites media URLs in recognized core blocks when copying content, and leaves Classic Editor markup and arbitrary links untouched.
- [How the Language Manager works](/docs/concepts/how-the-language-manager-works.md): What the MultilingualPress Language Manager is: the network-wide catalog of languages you can assign to sites, how to add or override languages, and how that data feeds switchers, hreflang, and redirection.
- [How WooCommerce product data maps across stores](/docs/concepts/how-woocommerce-product-data-maps-across-stores.md): Which product data each connected store owns, which data is copied from the source product, and which Override toggles decide the difference.
- [hreflang in MultilingualPress](/docs/concepts/hreflang-implementation.md): MultilingualPress emits hreflang automatically for connected content. What hreflang is for, what you get without configuring anything, and the three ways to customize it.
- [Language switcher options in MultilingualPress](/docs/concepts/language-switcher-options.md): Compare the language switcher options in MultilingualPress: Language Menu block, widget, navigation menu, custom switcher, and Quicklinks.
- [Managing a WordPress Multisite network](/docs/concepts/managing-wordpress-multisite.md): How to manage sites, users, themes, plugins, and network-wide settings from the WordPress Network Admin dashboard.
- [Media handling in a WordPress Multisite with MultilingualPress](/docs/concepts/media-handling-in-multisite.md): How WordPress Multisite keeps per-site media libraries and how MultilingualPress eases media duplication across language sites.
- [Can I use MultilingualPress with a standard single-site WordPress?](/docs/concepts/mlp-on-single-site.md): MultilingualPress requires WordPress Multisite and cannot run on a single-site install; this explains why and how to switch.
- [Multi-market eCommerce](/docs/concepts/multi-market-ecommerce.md): The technical, regulatory, and operational challenges of running an eCommerce business across multiple markets and languages, and why most platforms handle these concerns poorly out of the box.
- [Multilingual websites](/docs/concepts/multilingual-websites.md): What a multilingual website actually is: translation versus localization, language versus locale, URL strategy, hreflang, and the core problems every multilingual site has to solve, independent of platform.
- [Multilingual WordPress: approaches and solutions](/docs/concepts/multilingual-wordpress.md): The main technical approaches to building multilingual WordPress sites, from single-site content duplication to translation proxies to Multisite networks, and how they differ at the architectural level.
- [WordPress Multisite and plugin compatibility](/docs/concepts/multisite-and-plugin-compatibility.md): How plugin compatibility works on WordPress Multisite, the compatibility categories, and licensing considerations for paid plugins.
- [WordPress Multisite: benefits and tradeoffs](/docs/concepts/multisite-benefits-and-tradeoffs.md): The technical, operational, and governance tradeoffs of running a WordPress Multisite network, and how MultilingualPress addresses the key challenges at scale.
- [Understanding the WordPress Multisite database structure](/docs/concepts/multisite-database-structure.md): How WordPress Multisite changes the database: network-level tables, global user tables, and per-subsite duplicated tables.
- [Is WordPress Multisite right for your situation?](/docs/concepts/multisite-for-different-scenarios.md): Decide whether your situation fits WordPress Multisite with MultilingualPress: the signals that point to a network, the sectors it fits best, and when single-site WordPress is the better choice.
- [The Super Admin role and Multisite Network Admin](/docs/concepts/multisite-network-admin.md): What the Super Admin role actually means, how to navigate the Network Admin area, and why its reputation for complexity is undeserved.
- [Original Language Indicator](/docs/concepts/original-language-indicator.md): What the Original Language Indicator module does: show, on the post edit screen, which language site is the original source of a connected piece of content.
- [Other page builders and content editors](/docs/concepts/other-content-editors.md): How page builders without a dedicated MultilingualPress module behave: shortcode-based builders usually translate manually, with caveats around media IDs, links, and global templates.
- [Roles and capabilities across a MultilingualPress network](/docs/concepts/roles-and-capabilities.md): Who can do what across a MultilingualPress network: MultilingualPress adds no capabilities of its own and gates every action on the standard WordPress capability for the site being acted on.
- [Routine activities for managing multilingual content](/docs/concepts/routine-multilingual-content-activities.md): An overview of the routine activities for managing multilingual content with MultilingualPress: adding sites, publishing translations, and linking comments.
- [Synchronized Trashing](/docs/concepts/synchronized-trashing.md): What the Synchronized Trashing (Trasher) module does: when you trash a post, send all of its connected translations to trash at the same time, keeping translations in sync during deletion.
- [Translating comments and product reviews](/docs/concepts/translating-comments-and-reviews.md): How the MultilingualPress Comments module links and synchronizes comments and WooCommerce reviews across connected language sites.
- [What is WordPress Multisite?](/docs/concepts/what-is-wordpress-multisite.md): WordPress Multisite runs multiple independent sites from one installation, sharing core, themes, and users, ideal for multilingual networks.
- [Content manager guides & workflows](/docs/content-managers.md): Task-based guides for running a multilingual network with MultilingualPress: connect and translate content, editorial workflows, integrations, and troubleshooting.
- [Developer reference](/docs/developers.md): The developer surface for MultilingualPress: the PHP API, hooks and filters, WP-CLI commands, settings and data formats, and release notes.
- [Get started with MultilingualPress](/docs/get-started.md): Understand what MultilingualPress is, check compatibility, choose a license, and plan a migration. The starting point for evaluating and adopting MLP.
- [Go multilingual with MultilingualPress](/docs/go-multilingual.md): The initial setup path for MultilingualPress: configure Multisite, install and activate the plugin, activate your license, and keep it updated.
- [Translate ACF blocks](/docs/guides/acf-blocks.md): How MultilingualPress copies ACF block field data across sites, what it remaps, and the limitation with ACF blocks generated at runtime in PHP.
- [ACF configuration tips](/docs/guides/acf-configuration-tips.md): What copies versus what translates for ACF fields in MultilingualPress, how to keep field groups in sync, and how repeater, image, and options-page fields behave across sites.
- [Add a language switcher to your site](/docs/guides/add-a-language-switcher.md): Step-by-step setup for each front-end language switcher in MultilingualPress: the Language Menu block, the legacy widget, a navigation menu, Quicklinks, and a custom switcher.
- [Configure the AutoTranslate feature](/docs/guides/autotranslate/configuring-autotranslate.md): Enable machine translation in MultilingualPress: activate a provider (DeepL, Amazon Translate, or OpenAI) with your own API key under Automatic Translation, set a default when several are active, and check provider status in Site Health.
- [Connect Amazon Translate to MultilingualPress AutoTranslate](/docs/guides/autotranslate/connect-amazon-translate.md): Activate Amazon Translate (Beta) under Automatic Translation, enter your AWS access key, secret access key, and region. Where to generate IAM credentials, the free tier, and the Beta caveats to weigh.
- [Connect DeepL to MultilingualPress AutoTranslate](/docs/guides/autotranslate/connect-deepl-translate.md): Activate DeepL under Automatic Translation, paste in a DeepL API key, and optionally select a glossary. Where to get the key, how the free and Pro API plans differ, and how to confirm the connection.
- [Connect OpenAI to MultilingualPress AutoTranslate](/docs/guides/autotranslate/connect-openai.md): Activate OpenAI under Automatic Translation, paste in an OpenAI API key, and choose a model. Where to get the key, which models appear, billing, and how to confirm the connection.
- [Central Stock for WooCommerce](/docs/guides/central-stock.md): Central Stock for WooCommerce gives a MultilingualPress network one shared, network-wide stock value that every store can reference.
- [Configure MultilingualPress features](/docs/guides/configure-multilingualpress-features.md): After activating your license, enable the MultilingualPress modules your site needs in the Network Admin, then move to Content managers to put them to work.
- [Configure your WordPress Multisite for MultilingualPress](/docs/guides/configure-multisite-for-multilingualpress.md): Confirm your WordPress, PHP, and Multisite requirements and enable a Multisite network before installing MultilingualPress.
- [Configure the Language Menu block](/docs/guides/configure-the-language-menu-block.md): Enable the Gutenberg Blocks module and insert the MultilingualPress Language Menu block in posts, pages, or site-wide templates.
- [Connect and translate WooCommerce attributes](/docs/guides/connect-and-translate-woocommerce-attributes.md): Global WooCommerce attributes are connected across your language sites automatically; you translate their terms in the Translation metabox.
- [Connect existing content and sites](/docs/guides/connect-content-and-sites.md): The easiest way to connect content across language sites is to let MultilingualPress do it when you create the site. For sites that already exist, connect content in the Translation metabox; for large volumes, developers can connect it programmatically.
- [Coordinate multilingual comments and reviews](/docs/guides/coordinate-multilingual-comments-and-reviews.md): Day-to-day handling of comments and WooCommerce reviews across language sites: moderate them as usual per site, and let MultilingualPress copy and optionally translate new ones to the connected sites.
- [Copy a navigation menu across sites](/docs/guides/copy-a-navigation-menu-across-sites.md): Create a language menu once on a primary site and copy it to other connected sites using MultilingualPress in classic (non-block) themes.
- [Copy and translate custom fields](/docs/guides/copy-and-translate-custom-fields.md): Copy post meta and term meta to connected sites with the sync filters, adjust values before they are written, or send them through AutoTranslate. Which mechanism to use, and the site-context rules that decide whether your code works.
- [Copy media library content between connected sites](/docs/guides/copy-media-library-content.md): Copy single or bulk media files from one subsite to another using the MultilingualPress setting in the Media Library.
- [Create a custom language switcher](/docs/guides/create-a-custom-language-switcher.md): Build a language switcher on the MultilingualPress Translations API: how to query translations, what a result contains, what you get when a translation does not exist, and a complete escaped plugin.
- [Create a language version of your site](/docs/guides/create-a-language-version-of-your-site.md): Add a new site to your Multisite network for an additional language, connect it to your existing sites, and choose whether to copy content from a source site and have AutoTranslate draft the translations.
- [Create and translate custom post types and taxonomies](/docs/guides/create-and-translate-cpts-and-taxonomies.md): Create a CPT and taxonomy on one site, replicate them on others, mark them translatable, and connect their content across languages.
- [Customize the OpenAI translation instructions](/docs/guides/customize-openai-translation-instructions.md): Append terminology and style instructions to every OpenAI translation request with the translation_prompts filter: the messages array, the append-don't-replace rule, per-language terms, and the limits of the hook.
- [Enable Advanced Custom Fields (ACF) support](/docs/guides/enable-acf-support.md): Enable the ACF module in MultilingualPress, put the same field groups on every site, and copy or translate custom field data across your language sites.
- [Enable Beaver Builder support](/docs/guides/enable-beaver-builder-support.md): Install Beaver Builder, enable the Beaver Builder module in MultilingualPress, and duplicate Beaver Builder layouts across translations.
- [Enable Cornerstone integration](/docs/guides/enable-cornerstone-support.md): Turn on the MultilingualPress integration for the Cornerstone page builder so Cornerstone-built layouts can be copied and translated across your language sites.
- [Enable Easy Digital Downloads integration](/docs/guides/enable-easy-digital-downloads-support.md): Turn on the MultilingualPress integration for Easy Digital Downloads so you can translate and connect digital products and related content across your language sites.
- [Enable Elementor support](/docs/guides/enable-elementor-support.md): Install Elementor, enable the Elementor module in MultilingualPress, and duplicate Elementor page layouts across translations.
- [Enable The Events Calendar integration](/docs/guides/enable-the-events-calendar-support.md): Turn on the MultilingualPress integration for The Events Calendar so events can be translated and connected across your language sites, created through The Events Calendar's own API.
- [Enable WooCommerce support](/docs/guides/enable-woocommerce-support.md): Install WooCommerce, enable the WooCommerce module in MultilingualPress, and mark products and taxonomies as translatable.
- [Export and import MultilingualPress data](/docs/guides/export-and-import-mlp-data.md): Back up or move your MultilingualPress relationships and network settings from Network Admin → MultilingualPress → Tools, and the import order that avoids broken relations.
- [Forward visitors to the right language](/docs/guides/forward-visitors-to-the-right-language.md): Activate the Redirect module and configure fallback, execution method, and detection type to send visitors to the matching language site.
- [Install and activate MultilingualPress](/docs/guides/install-and-activate-multilingualpress.md): Download MultilingualPress, upload it to your WordPress Multisite, and network-activate it across every site.
- [Managing a multilingual WooCommerce store with MultilingualPress](/docs/guides/manage-a-multilingual-woocommerce-store.md): The operational realities of running WooCommerce across a MultilingualPress network: what is shared, what is separate, where the friction comes from, and how to manage it.
- [Publish content in multiple languages](/docs/guides/publish-content-in-multiple-languages.md): Write a post once on a source site, then use the MultilingualPress Translation metabox to create linked translations on each language site. MultilingualPress creates the connected posts and any missing category or tag terms in the same step.
- [React to a translation being saved](/docs/guides/react-to-translation-saves.md): The hooks that fire when a translation is saved from the metabox, in the order they run: change the content being copied, act after the relationship exists, and read any metabox field the editor submitted.
- [Set up a WordPress Multisite network](/docs/guides/set-up-wordpress-multisite-network.md): Convert a single WordPress install into a Multisite network manually or with WP-CLI, then manage it from the Network Admin.
- [Translate content automatically](/docs/guides/translate-content-automatically.md): Use AutoTranslate to draft translations: one item from the Translation metabox, a whole back catalogue from WP-CLI, or an entire site during duplication. Which checkboxes control what, and what AutoTranslate covers.
- [Translate post type and taxonomy slugs](/docs/guides/translate-post-type-and-taxonomy-slugs.md): Set localized slugs for custom post types and taxonomies at registration or via the Post Type Slugs section in each site's Permalinks settings.
- [Translate WooCommerce products](/docs/guides/translate-woocommerce-products.md): Link and translate WooCommerce products across language sites using the translation metaboxes and the Product Data tab.
- [Customize the default values in the translation metabox](/docs/guides/translation-metabox-defaults.md): Precheck the translation metabox checkboxes, limit the post statuses on offer, and change how taxonomies are picked. One filter shape covers all of the checkboxes, and it has one limitation worth knowing first.
- [Working with WP-CLI across a Multisite network](/docs/guides/wp-cli-in-multisite.md): Practical tips for running WP-CLI against a multilingual Multisite: how site context works, finding your language sites, and aliases and wrappers to target a specific language site without retyping the full URL.
- [Trying MultilingualPress risk-free](/docs/licensing/30-day-refund-guarantee.md): There is no trial period. Instead, every purchase is covered by a guaranteed full refund within 30 days, so you can evaluate MultilingualPress on your own network with nothing at stake.
- [Activate your license to stay updated](/docs/licensing/activate-and-configure-license.md): Enter your Master API Key and Product ID in the License tab to activate MultilingualPress. An active license is what turns on automatic updates and support.
- [Enterprise procurement and vendor onboarding](/docs/licensing/enterprise-procurement.md): How enterprise procurement, legal, and vendor-management teams can onboard MultilingualPress as a vendor: stages, required documents, security and compliance facts, and how to share your own requirements.
- [Which MultilingualPress license is right for me?](/docs/licensing/which-license-do-i-need.md): Choose the right MultilingualPress plan for your site. One license covers one website; the plan you pick is decided by how many languages you publish.
- [Migrate from a front-end or proxy translation tool](/docs/migration/migrate-from-front-end-translation.md): How to migrate from a front-end or proxy translation tool to MultilingualPress. There is little to import, so the reliable path is a clean Multisite cloned from a template, then AutoTranslate.
- [Migrate from MultilingualPress 2.x](/docs/migration/migrate-from-mlp-2x.md): MultilingualPress 2.x is the old, unmaintained free version. It shares the Multisite model with the current plugin but stores translation relationships differently, so it cannot be updated in place. Migration uses dedicated tooling through support.
- [Migrate from Multisite Language Switcher (MSLS)](/docs/migration/migrate-from-msls.md): Multisite Language Switcher runs the same one-language-per-site Multisite model as MultilingualPress, so moving up keeps your sites and content and only converts the translation links. Small networks can relink by hand; larger ones use our migration tooling.
- [Migrate a multilingual site from another platform to WordPress](/docs/migration/migrate-from-non-wordpress.md): Moving a multilingual site from another platform to WordPress Multisite with MultilingualPress is a family of tasks, not one procedure. How to think about it: separate the web relaunch from the multilingual layer, start from data liberation, and pick the right approach for your case.
- [Migrate from a single-site multilingual plugin](/docs/migration/migrate-from-single-site-plugin.md): The reliable way to migrate a multilingual WordPress site from a single-site multilingual plugin to MultilingualPress: build a clean Multisite network and clone it, so every language site shares the same base content IDs and translations attach deterministically.
- [Migrating to WordPress Multisite with MultilingualPress](/docs/migration/migrate-to-multisite.md): The shape every migration to WordPress Multisite with MultilingualPress shares: the model shift, a repeatable template-and-clone sequence, and where to go for your specific source.
- [AutoTranslate provider configuration](/docs/reference/api/automatic-translation-provider-configuration.md): Filter hooks for configuring the DeepL, OpenAI, and Amazon Translate provider clients in MultilingualPress AutoTranslate: HTTP timeout, proxy, retries, per-provider request arguments, and the OpenAI system prompt.
- [Connecting content across sites (ContentRelations API)](/docs/reference/api/connect-content-across-sites.md): The ContentRelations API: create, read, modify, and delete translation relationships between posts, terms, and comments across network sites in code.
- [DeepL glossary integration](/docs/reference/api/deepl-glossary-integration.md): Control which DeepL glossary AutoTranslate uses: the admin preferred-glossary setting, the filter API for per-post-type and per-language glossaries, validation behavior, and language-code handling.
- [MultilingualPress API reference](/docs/reference/api/overview.md): The entry point to MultilingualPress's developer interfaces: the PHP API, hooks and filters, the WP-CLI command set, and the REST extension. Where to start for each.
- [Programmatic machine translation with translate()](/docs/reference/api/programmatic-machine-translation.md): Use the public translate() function to machine-translate arbitrary text through MultilingualPress's configured providers (DeepL, OpenAI, Amazon Translate).
- [Programmatic translation access in MultilingualPress](/docs/reference/api/programmatic-translation-access.md): Retrieve a content element's translations as rich Translation objects with the Translations API, or as a plain site-to-content ID map with translationIds().
- [MLP-CLI command reference](/docs/reference/cli-commands.md): Complete WP-CLI reference for MultilingualPress: autotranslate, relations, sites, modules, license, and import/export commands with every flag, default, and example.
- [External Sites reference: link languages outside your network](/docs/reference/external-sites.md): How the External Sites module treats an outside URL as a language site for the switcher and hreflang.
- [MultilingualPress glossary: key terms and definitions](/docs/reference/glossary.md): Definitions of common MultilingualPress and WordPress Multisite terms, from Block Editor to Super Admin.
- [AutoTranslate content filters reference](/docs/reference/hooks/autotranslate-content-filters.md): The filters that let you modify or skip content before AutoTranslate sends it to a provider, and modify the translated result before it is saved: names, signatures, parameters, and version gates.
- [Translation metabox hooks reference](/docs/reference/hooks/translation-metabox-hooks.md): The canonical contract for the filters that control the MultilingualPress translation metabox: prechecked checkbox states, available post statuses, and how taxonomies are rendered. Names, signatures, and defaults.
- [Import/export JSON format](/docs/reference/import-export-json-format.md): The JSON schema MultilingualPress uses to export and import relationship data and network settings, with field-by-field structure and complete examples. Reference for migrations, environment sync, and backups.
- [MultilingualPress relationship data structure](/docs/reference/relationship-data-structure.md): The database tables MultilingualPress adds, their exact schema, how translation relationships are stored and populated, and how to read them back. Reference for developers.
- [Cache settings reference](/docs/reference/settings/cache.md): The eight internal caches on the Cache tab, grouped as Api, Database, and Nav Menu. Every one is off by default, what each one stores, and when turning one on or off is the right move.
- [License settings reference](/docs/reference/settings/license.md): The License tab: the Master API Key and Product ID fields, where to get both, and what an inactive license does and does not stop.
- [Modules settings reference](/docs/reference/settings/modules.md): Every MultilingualPress module on the network Features tab: exact UI label, what it does, what it requires, and which ones unlock a settings tab of their own.
- [MultilingualPress settings tabs](/docs/reference/settings/overview.md): Every tab under Network Admin → MultilingualPress: which six are always present, which appear only when a module is active, and where the per-site settings live instead.
- [QuickLinks settings reference](/docs/reference/settings/quicklinks.md): The QuickLinks tab and its single setting, QuickLinks Position: the four corner positions the in-content language links can take, and what the module renders.
- [Redirect settings reference](/docs/reference/settings/redirect.md): The Redirect tab: Redirect Fallback, Redirect Execution, and Redirect Type with their exact values, plus the per-site and per-user settings that override them and what geolocation costs.
- [Translatable Post Types settings reference](/docs/reference/settings/translatable-post-types.md): The Translatable Post Types tab: which post types are enabled by default, what the Permalinks column does, and why an enabled type is what makes the Translation metabox appear.
- [Translatable Taxonomies settings reference](/docs/reference/settings/translatable-taxonomies.md): The Translatable Taxonomies tab: which taxonomies are enabled by default, what enabling one changes in the term editor, and how it interacts with creating connected terms.
- [MultilingualPress changelog](/docs/release-notes/all.md): Added, changed, fixed, deprecated, and security notes for all MultilingualPress releases.
- [MultilingualPress current release notes](/docs/release-notes/current.md): Added, changed, fixed, deprecated, and security notes for the current MultilingualPress release.
- [MultilingualPress architecture at a glance](/docs/start-here/architecture-at-a-glance.md): A one-screen mental model of how MultilingualPress is built: one language per Multisite subsite, network-global relationship tables, public PHP APIs, and the UI, modules, and frontend layers on top.
- [MultilingualPress compatibility matrix](/docs/start-here/compatibility-matrix.md): WordPress, PHP, editor, and plugin compatibility for MultilingualPress
- [Documentation Home](/docs/start-here/docs-home.md): Redirects to the MultilingualPress Get started hub.
- [What is MultilingualPress?](/docs/start-here/overview.md): MultilingualPress turns a WordPress Multisite into a multilingual network, with one site per language linked for translation and SEO.
- [Quick start](/docs/start-here/quick-start.md): Get a working two-language site with MultilingualPress: enable Multisite, install and license the plugin, enable the features you need, connect a provider, create a language site, add a switcher.
- [What can MultilingualPress do?](/docs/start-here/what-can-multilingualpress-do.md): MultilingualPress links language sites in a Multisite network, handling translation, hreflang, language switching, and scaling to 20+ languages.
- [Cache-related issues in MultilingualPress](/docs/troubleshooting/cache-related-issues.md): Diagnose stale language content, wrong switcher links, and caching conflicts in MultilingualPress.
- [Conflict with custom post types](/docs/troubleshooting/conflict-with-custom-post-types.md): Resolve missing translation metaboxes or unlinked custom post types in MultilingualPress.
- [Conflict with page builders](/docs/troubleshooting/conflict-with-page-builders.md): Fix untranslated or broken page-builder content (Elementor, Beaver Builder) in MultilingualPress.
- [Incorrect hreflangs](/docs/troubleshooting/incorrect-hreflangs.md): Diagnose wrong, missing, or duplicate hreflang tags on a MultilingualPress multilingual site.
- [Language flags not showing](/docs/troubleshooting/language-flags-not-showing.md): Fix missing country flags in the MultilingualPress language switcher or menu.
- [Upgrading from MultilingualPress 2 fails](/docs/troubleshooting/legacy-mlp2-incompatibility.md): Why the current MultilingualPress will not run on, or automatically migrate, MultilingualPress 2 data, and how to move a legacy MLP 2 network to the current version.
- [Media library content not copied during site duplication](/docs/troubleshooting/media-not-copied-during-site-duplication.md): Why site duplication stops before copying media and how to complete a clean clone in MultilingualPress.