QUERY2SLUG
Query2Slug compatibility with REEID Translate
Query2Slug compatibility with REEID Translate is being evaluated from available plugin evidence. Maps query string parameters to clean, canonical URL slugs without creating new pages No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Query2Slug.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Query2Slug is documented in the SEO category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Query2Slug compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Maps query string parameters to clean, canonical URL slugs without creating new pages
- Automatically issues 301 redirects from query-string URLs to the defined clean slug
- Preserves UTM and tracking parameters (e.g., utm_source, fbclid) during canonical redirects
- Supports any WordPress taxonomy or query variable, including WooCommerce categories, tags, and attributes
- Registers rewrite rules dynamically based on configured URL prefix and mapping rules
- Provides an admin interface with autocomplete for selecting taxonomies and terms in rule creation
- Operates entirely server-side with zero frontend CSS or JavaScript impact
CONTENT BOUNDARY
Query2Slug capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Query2Slug and REEID Translate FAQ.
What does Query2Slug do according to the available plugin evidence?
Query2Slug has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Query2Slug?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Query2Slug?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Query2Slug in a multilingual WordPress workflow.
REEID documents Query2Slug functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.