READING TIME WP
Reading Time WP translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Reading Time WP 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
- Automatically inserts an estimated reading time at the beginning of post content.
- Provides a shortcode for inserting reading time manually in posts or themes.
- Lets site owners change the reading-time label and postfix.
- Supports selecting which post types display reading time, with posts and pages as the default.
- Counts images in the reading-time calculation.
- Allows adding custom fields or other content to the word-count calculation through a filter.
- Supports specifying a different post ID in the shortcode.
Distinctive features
Estimated reading time insertion, manual shortcode placement, configurable label and postfix, post-type selection, image-aware word counting, and support for adding custom fields or other content to the count through a filter.
Dynamic content
The plugin calculates reading time from content and images, and it can include additional custom fields or other content in the word-count calculation when configured through a filter. The evidence does not establish broader runtime content handling.
SEO and metadata
The evidence does not establish SEO metadata behavior.
URLs and navigation
The evidence does not establish URL or navigation behavior.
Forms and commerce
The evidence does not establish forms or commerce behavior.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Reading Time WP 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
- Reading time is shown for post content where the plugin is enabled. The available evidence does not establish broader support beyond the listed post types, shortcode use, or custom field inclusion through a filter.
COMMON QUESTIONS
Reading Time WP and REEID Translate FAQ.
Does the current evidence establish translation scope for Reading Time WP?
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.