WPMMCC

Installation

Automatic Installation

1. Go to Plugins > Add New in your WordPress admin
2. Search for “WPMMCC”
3. Click Install Now and then Activate

Manual Installation

1. Download the plugin ZIP file
2. Go to Plugins > Add New > Upload Plugin
3. Upload the ZIP file and click Install Now
4. Activate the plugin

First-Time Setup

1. Go to WPMMCC > Sites and click Add New
2. Choose your group type: Directory (single site, language prefixes) or Multisite
3. Add a site entry for each language. Mark one as the Main Site
4. Go to WPMMCC > Machine translation or WPMMCC > LLM translation and click Add Rule
5. Save vendor credentials or LLM model details first, then select source language, target language, and request limits
6. Click Test Rule or test the model configuration to verify the remote service works
7. Go to WPMMCC > Translation Fields to choose which post fields to translate
8. On any post list screen, select posts and use Bulk Translate to start translating
9. Monitor progress at WPMMCC > Tasks

Admin Workflow Guide

After activation, the plugin adds a top-level WPMMCC menu in the WordPress admin. The main administrator workflow is:

1. Configure site structure in WPMMCC > Sites
2. Configure providers and rules in WPMMCC > Machine translation or WPMMCC > LLM translation
3. Choose translatable fields in WPMMCC > Translation Fields
4. Optionally configure SEO fields in WPMMCC > SEO Fields
5. Start translations from the post, media, or taxonomy list screens using Bulk Translate
6. Monitor or manage queued jobs in WPMMCC > Tasks
7. Review relations in WPMMCC > Translation management
8. Configure sitemap output in WPMMCC > Sitemap
9. Adjust global behavior in WPMMCC > Parameters

Admin Pages

WPMMCC > Sites

• Create and manage site groups
• Add, edit, or remove language sites
• Configure whether a group runs in directory mode or multisite mode
• Set the main site for each language group

WPMMCC > Machine translation

• Create translation rules for Google, DeepL, Baidu, or Youdao
• Save provider credentials on the vendor settings screen, then define source language, target language, and the per-rule Maximum characters per request
• Long text is split automatically on line, sentence, and word boundaries before sending requests, then merged back into the final translated field
• Test rule connectivity before saving

WPMMCC > LLM translation

• Register OpenAI-compatible models and endpoints
• Create LLM-based translation rules with model, prompt, temperature, and Maximum response tokens
• Maximum response tokens is passed to the API as the model’s response cap; long source content is still chunked automatically before translation and merged back after the response returns
• Test model configuration from the admin interface

WPMMCC > Theme

• Scan active-theme strings from PHP, JavaScript, templates, and database-backed theme content
• Trigger automatic theme translation for a selected site
• Review, search, edit, or manually add theme translation entries

WPMMCC > Tasks

• Task list tab: monitor background jobs, inspect status, filter by group or site, and perform operations such as retry, delete, or manual execution where available
• Task settings tab: adjust queue batch size, concurrency, overwrite behavior, retry behavior, and related execution settings

WPMMCC > Translation management

• Review translation relations across posts, media, and terms
• Filter by object type, group, or site
• Delete single relations or remove them in bulk

WPMMCC > Sitemap

• Configure sitemap output format and per-group sitemap generation
• Verify generated multilingual sitemap links from the admin screen

WPMMCC > Parameters

• Control global plugin behavior such as canonical output, hreflang, uninstall retention, logging, and related plugin-wide options

Admin List Screen Operations

The plugin also extends standard WordPress list screens used by administrators and editors:

• Posts / Pages: select content rows and use Bulk Translate to create translation tasks
• Media Library: bulk translate attachment metadata such as alt text, caption, and description
• Categories / Tags: bulk translate taxonomy terms and their descriptions/slugs
• Comments, Posts, Pages, Media, Categories: use the Site filter dropdown to view content belonging to a specific translated site
• Post edit screen: use the WPMMCC meta box to inspect or adjust site-related translation context

Typical Admin Tasks

Translate posts or pages

1. Open Posts or Pages
2. Select one or more items
3. Choose Bulk Translate
4. Select the target site/language
5. Confirm and monitor progress in WPMMCC > Tasks

Translate theme strings

1. Open WPMMCC > Theme
2. Select the target site
3. Run Scan and translate
4. Wait for queue completion in WPMMCC > Tasks
5. Return to WPMMCC > Theme to review or edit results

Translate SEO fields

1. Open WPMMCC > SEO Fields
2. Scan available meta fields for the selected group
3. Enable the fields you want to translate
4. Run post/page translations as usual

Review translation relations

1. Open WPMMCC > Translation management
2. Filter by type or site if needed
3. Delete stale or unwanted relations
4. Re-run translation for the affected content if you need to recreate them

Site Owner Guide

This section is intended for site owners, operators, and project managers who are responsible for launching and maintaining a multilingual site, but may not work with WordPress internals every day.

Before You Launch

• Confirm your permalink structure is enabled and working correctly before setting up directory-mode language URLs
• Decide whether your project should use directory mode or multisite mode before you begin translating live content
• Prepare valid API credentials for your chosen translation provider
• Decide which content types need translation first: posts, pages, media, taxonomy terms, theme strings, and SEO fields
• If you already use Yoast SEO or Rank Math, decide whether WPMMCC or your SEO plugin should output canonical and hreflang tags

Recommended Launch Order

1. Create the site group and language sites
2. Create and test the translation rule
3. Enable the content fields and SEO fields you want translated
4. Translate a small set of test pages first
5. Check frontend URLs, page titles, metadata, canonical tags, and hreflang
6. Scan and translate theme strings
7. Translate the remaining content in batches
8. Review sitemap output before announcing the multilingual site publicly

Daily Use For Site Owners

• Publish or update content on the source site first
• Send new or changed content to translation from the relevant list screen
• Check WPMMCC > Tasks to make sure jobs complete successfully
• Review a few translated pages on the frontend, especially high-value landing pages
• Re-scan theme strings after theme changes, theme updates, or menu/widget updates

When You Should Re-Run Translation

• After changing the source post title, content, or excerpt
• After updating featured image metadata or attachment alt text
• After editing category/tag names, descriptions, or slugs
• After changing SEO titles, meta descriptions, or enabled SEO fields
• After switching themes or updating theme templates, menu labels, widgets, or theme.json content

SEO Checklist For Site Owners

• Verify each translated page resolves on its correct language URL
• Confirm canonical tags point to the localized page you expect
• Confirm hreflang tags include the right language variants
• Check that translated pages are indexable if you want them in search engines
• Review generated sitemap URLs after major translation batches

Operations And Safety

• Keep Keep data on uninstall enabled if you want to preserve translation data during maintenance or reinstallation
• Use staging first when changing translation providers, queue settings, or site structure on an established production site
• Translate in batches for large sites rather than sending all content at once
• Monitor provider usage limits, quotas, and billing in the provider’s own dashboard

Common Issues To Check First

• If translated pages do not appear, review WPMMCC > Tasks for failed or pending jobs
• If translated URLs return 404, re-save permalinks and confirm the site group is configured correctly
• If SEO metadata is not translated, re-scan and enable the relevant field in WPMMCC > SEO Fields
• If menus, widgets, or theme labels remain untranslated, run a theme scan again from WPMMCC > Theme
• If a language variant looks outdated, re-run translation for the affected source content

Admin Roles And Typical Responsibilities

WPMMCC is primarily designed for administrators or site managers with permission to configure translation providers, site groups, queue settings, and SEO behavior.

Administrator responsibilities

• Create site groups and child sites
• Configure machine-translation or LLM providers
• Enable translatable content fields and SEO fields
• Control sitemap, canonical, hreflang, uninstall-retention, and queue settings
• Review translation relations and remove invalid mappings when necessary
• Run theme scans, delete theme translations, and manage manual theme translation entries

Content editor responsibilities

• Publish or update source content
• Trigger bulk translation from supported content list screens when permissions allow
• Review translated output on the frontend
• Report broken links, missing strings, or outdated translations back to the site administrator

Translation Data Flow

At a high level, WPMMCC processes multilingual content in the following order:

1. The administrator defines a site group, target sites, and a translation rule
2. Source content is selected from a post, media, or taxonomy list screen
3. WPMMCC creates background tasks in the queue
4. The selected translation provider translates enabled content fields
5. WPMMCC writes translated objects to the target site context
6. WPMMCC records the source-to-target mapping in the translation relations table
7. Frontend hooks resolve the correct translated URL, metadata, and theme strings for the visitor

For posts and pages

• The plugin reads enabled source fields such as title, content, excerpt, and selected SEO meta
• A translation task is queued and executed in the background
• In directory mode, translated content is stored as a shadow post on the same WordPress install and served under the language-prefixed URL
• In multisite mode, translated content is written into the corresponding target site
• The translation relation is stored so WPMMCC can connect the source object to the translated object later

Translation Rule Sizing And Long-Content Handling

WPMMCC applies translation-rule sizing differently for machine providers and LLM providers:

• Machine translation rules use Maximum characters per request as the main request-size control
• The effective machine-request size is the lower of the rule value and the provider hard limit built into the plugin
• LLM translation rules use Maximum response tokens as the API max_tokens value; this affects the model output budget, not the source-text chunk size directly
• Long source fields are chunked automatically before dispatch so large posts, excerpts, SEO fields, and theme strings can still be translated safely

When long content is translated, WPMMCC currently follows this flow:

1. It calculates the effective per-request character budget for the selected rule/provider
2. It tries to split long plain text on line breaks, sentence boundaries, and word boundaries
3. If the field contains HTML, it keeps tag structure balanced while chunking so translated fragments can be merged back into valid markup
4. It sends the resulting fragments to the provider in order
5. It validates the returned fragment count and fills any missing pieces with original content when necessary
6. It merges translated fragments back into a single field value before saving the translated object

This means:

• Lowering machine-rule length gives you more conservative, smaller requests
• Raising machine-rule length cannot exceed the provider hard limit enforced by the plugin
• Increasing LLM response tokens can help with longer answers from the model, but it does not replace the plugin’s source-content chunking
• Very large HTML fields are translated fragment-by-fragment and then reassembled in order

For media

• The plugin translates attachment metadata such as alt text, caption, and description
• The translated media relation is tracked so the translated parent content can resolve the correct localized media information

For categories and tags

• The plugin translates taxonomy names, descriptions, and slugs
• Term relations are stored separately so frontend category/tag links can remain localized

For theme strings

• WPMMCC scans the active theme for translatable strings in files, menus, widgets, and selected database-backed theme content
• The scan creates theme-translation tasks, which are then translated and cached for frontend use
• Theme translations are loaded dynamically for the current site/language combination rather than being treated like normal posts

Managing Translated Content After Translation

WPMMCC does not stop at initial translation. The plugin also provides ongoing translated-content management tools:

Translation management page

• Open WPMMCC > Translation management
• View source-to-target mappings for posts, pages, media, categories, and tags
• Filter by object type, group, or search term
• Delete stale relations individually or in bulk

Translated post and term maintenance

• Re-run translation when source content changes significantly
• Use the admin Site filter on posts, pages, media, categories, and comments to inspect content by language site
• Review frontend output after major source edits, taxonomy changes, or SEO-field changes

Queue-based management

• Open WPMMCC > Tasks
• Inspect pending, running, completed, or failed jobs
• Retry or manually run tasks where the interface allows
• Tune task settings when you need smaller batches or more conservative execution

Theme Scan, Manual Add, And Edit Workflow

Theme translations have their own management workflow because they are not stored like regular post content.

Theme scan workflow

1. Open WPMMCC > Theme
2. Select the group and child site you want to manage
3. Choose a scan mode:
   • Overwrite existing translations: regenerate and replace existing theme translations for that site
   • Only add new content: keep existing translated entries and only add strings that were not translated before
4. Click Scan and translate
5. Track progress in WPMMCC > Tasks

Manual theme translation entry

On the Theme page, administrators can click Add manually and enter:

• Source identifier: a label used to distinguish the manual entry
• Original content: the source text
• Translated content: the target-language text

This is useful when:

• a theme string is not discovered automatically
• a site owner wants to override an automatic result
• a small number of strings should be curated manually

Editing existing theme translations

• Use the Theme page results list to locate an existing translation entry
• Open the edit view
• Update the original text or translated text
• Save the entry so the frontend can use the revised translation

Deleting theme translations

• Administrators can delete all theme translations for the selected child site from WPMMCC > Theme
• This is useful after a theme switch, a large redesign, or when a full re-scan is preferred over incremental cleanup