
SLUGSYNC
SlugSync | REEID Translate Compatibility
REEID Translate Pro translates supported WordPress menu-item labels while preserving the navigation structure, destinations and presentation managed by SlugSync.
AWAITING VERIFICATION
Keep SlugSync responsible for navigation design.
REEID handles supported multilingual menu labels while SlugSync remains responsible for menu layout, styling, effects and responsive behaviour.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
NATIVE
Supported labels remain tied to standard WordPress navigation menu items and their existing destinations.
EDITABLE
Translated menu labels remain available for normal WordPress review and refinement.
PRACTICAL WORKFLOW
Translation workflow
01 · Build the source menu
Create the original WordPress navigation and configure its presentation through SlugSync.
02 · Choose a target language
Select the language and translation settings through the REEID workflow.
03 · Prepare menu translations
REEID translates supported visitor-facing menu-item labels while preserving hierarchy and destinations.
04 · Review every menu state
Check desktop, mobile, dropdown, sticky and responsive navigation after translation.
SUPPORTED CONTENT
Translation scope
Visitor-facing text
Replace this draft item with the exact evidence-backed content coverage.
Interface content
Document supported labels, titles or interface strings where applicable.
Product-specific content
Add confirmed product-specific support before publication.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Bulk regeneration of post/content slugs from titles (preview, report, and undo protections).
- Optional transliteration for slug generation using a bundled local map for Cyrillic/Greek, with additional scripts handled only when the server provides PHP’s international transliterator.
- WooCommerce SKU handling options for product slugs (e.g., leaving the assigned SKU out of the URL when it already appears in the title, or adding it from Product data → Inventory when absent), without changing the stored product title or SKU.
- Collision-accurate preview simulation of WordPress slug rules across a run, including numeric suffix behavior and namespace scoping (flat vs hierarchical post types) and draft/pending no-uniqueness behavior.
- URL preservation via recording old-slug history for non-nesting content types (posts/products/most custom post types) so old URLs can redirect to new ones; pages require using the exported redirect report/import into a redirect plugin.
- Quiet write mode that updates slugs directly in the posts table (skipping save_post) and clears Yoast indexables for changed posts on the quiet path; a standard update path is available if needed by the stack.
- Built-in redirect export: generates a CSV of relative source/target pairs (no header row) intended for import into a redirect plugin as permanent redirects; also provides a measured URL-change summary per preview run.
- Safety mechanisms for large sites and operational continuity: batched processing with keyset pagination, resume of interrupted runs via WordPress-stored batch progress and a private write-ahead journal, and a run lock to prevent overlapping runs.
Distinctive features
Bulk regeneration of post/content slugs from titles (preview, report, and undo protections). Optional transliteration for slug generation using a bundled local map for Cyrillic/Greek, with additional scripts handled only when the server provides PHP’s international transliterator. WooCommerce SKU handling options for product slugs (e.g., leaving the assigned SKU out of the URL when it already appears in the title, or adding it from Product data → Inventory when absent), without changing the stored product title or SKU. Collision-accurate preview simulation of WordPress slug rules across a run, including numeric suffix behavior and namespace scoping (flat vs hierarchical post types) and draft/pending no-uniqueness behavior. URL preservation via recording old-slug history for non-nesting content types (posts/products/most custom post types) so old URLs can redirect to new ones; pages require using the exported redirect report/import into a redirect plugin. Quiet write mode that updates slugs directly in the posts table (skipping save_post) and clears Yoast indexables for changed posts on the quiet path; a standard update path is available if needed by the stack. Built-in redirect export: generates a CSV of relative source/target pairs (no header row) intended for import into a redirect plugin as permanent redirects; also provides a measured URL-change summary per preview run. Safety mechanisms for large sites and operational continuity: batched processing with keyset pagination, resume of interrupted runs via WordPress-stored batch progress and a private write-ahead journal, and a run lock to prevent overlapping runs.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Menu labels and navigation configuration remain separate.
REEID targets supported WordPress menu-item titles while SlugSync continues controlling menu structure, styling, effects, widgets and responsive configuration.
Embedded widgets, shortcodes, dynamically generated labels and third-party menu extensions may require separate compatibility testing.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
SlugSync and REEID Translate FAQ.
Does REEID Translate support SlugSync?
Yes. REEID Translate Pro includes tested compatibility for supported WordPress navigation menu labels used with SlugSync.
Does REEID rebuild or duplicate the SlugSync navigation layout?
No. SlugSync remains responsible for navigation structure, styling and responsive behaviour while REEID translates supported labels.
What about custom widgets or dynamic menu content?
Those can use separate storage or rendering paths and should be reviewed independently when they fall outside standard WordPress menu-item titles.
RELATED GUIDES
Continue through the compatibility library.
MULTILINGUAL NAVIGATION
Translate menu labels without rebuilding your navigation.
REEID Translate Pro adds multilingual menu content while your navigation plugin remains responsible for structure and presentation.
SlugSync remains responsible for menu layout, styling and responsive behaviour.