TITLE REMOVER
Title Remover translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Title Remover 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
- Hides the title of any post, page, or custom post type item.
- Adds a metabox in the WordPress admin post creation form to toggle title visibility.
- Removes the title rather than hiding it with CSS or JavaScript.
- Avoids affecting menus and the admin area by checking that the front end is being displayed and the current point is within the loop.
- Works with themes that use the recommended WordPress function for displaying the title.
Distinctive features
Title visibility can be toggled per item from the editor. The plugin removes the title from output instead of visually concealing it. It is described as working with themes that use the recommended WordPress function for displaying the title.
Dynamic content
Title handling is described for individual posts, pages, and custom post type items. Evidence shows front-end-only behavior tied to the loop, but no broader runtime content behavior is established.
SEO and metadata
No evidence was provided for SEO metadata changes, title tag editing, or other metadata handling.
URLs and navigation
No evidence was provided for URL changes, redirects, or navigation behavior.
Forms and commerce
No evidence was provided for forms or commerce behavior.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Title Remover 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
- The plugin is described for hiding titles on posts, pages, and custom post type items. Evidence does not establish broader theme compatibility beyond themes that use the recommended WordPress title function. It is also not shown to affect menus or the admin area.
COMMON QUESTIONS
Title Remover and REEID Translate FAQ.
Does the current evidence establish translation scope for Title Remover?
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.