NIFTEE REDIRECTION
Niftee Redirection translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Niftee Redirection does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Front-end redirect rule execution supporting HTTP 301, 302, 303, 307, and 308, plus direct status responses 410 (Gone) and 451 (Unavailable for Legal Reasons).
- Redirect matching supports both plain-text and regular-expression URL matching, with configurable query-string handling and enabled/disabled rule states.
- Loop-safety checks are performed for front-end redirects to avoid redirect loops.
- 404 monitoring records missing URLs with hit counts, referrers, and last-seen timestamps; it also supports workflows to ignore and restore unwanted 404 records.
- Separate logging for redirect and status-response activity, with independent retention controls for 404 records vs redirect logs.
- Data portability via export/import of redirect rules in CSV and JSON formats, including import support for Niftee CSV/JSON and JSON exports from the Redirection plugin (with an import preview).
- Privacy controls include IP anonymisation enabled by default, and the plugin does not send redirect/monitoring data to an external service; redirect rules, 404 records, logs, and settings remain in the WordPress database.
- Redirect matching is scoped to normal front-end requests and skips wp-admin, REST, AJAX, cron, and CLI contexts.
Distinctive features
Front-end redirect rule execution supporting HTTP 301, 302, 303, 307, and 308, plus direct status responses 410 (Gone) and 451 (Unavailable for Legal Reasons). Redirect matching supports both plain-text and regular-expression URL matching, with configurable query-string handling and enabled/disabled rule states. Loop-safety checks are performed for front-end redirects to avoid redirect loops. 404 monitoring records missing URLs with hit counts, referrers, and last-seen timestamps; it also supports workflows to ignore and restore unwanted 404 records. Separate logging for redirect and status-response activity, with independent retention controls for 404 records vs redirect logs. Data portability via export/import of redirect rules in CSV and JSON formats, including import support for Niftee CSV/JSON and JSON exports from the Redirection plugin (with an import preview). Privacy controls include IP anonymisation enabled by default, and the plugin does not send redirect/monitoring data to an external service; redirect rules, 404 records, logs, and settings remain in the WordPress database. Redirect matching is scoped to normal front-end requests and skips wp-admin, REST, AJAX, cron, and CLI contexts.
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
Keep plugin capabilities separate from translation scope.
Current evidence documents what Niftee Redirection does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Niftee Redirection and REEID Translate FAQ.
Does the current evidence establish translation scope for Niftee Redirection?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.