PRISNA GWT
Prisna GWT – Google Website Translator translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Prisna GWT – Google Website Translator 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
- Translates a WordPress site into 100+ languages using Google’s automatic translation service.
- Provides inline and tabbed display styles for the translation widget.
- Lets site owners select which languages are available.
- Can be used as a widget or via shortcode.
- Includes import/export of settings for transferring configurations.
- Supports excluding parts of a page from translation with a jQuery selector or the `notranslate` class.
- Stores settings in a single database record and avoids loading external files, according to the plugin’s documentation.
Distinctive features
WordPress translation plugin with Google automatic translation, 100+ language coverage, widget and shortcode delivery, inline or tabbed widget presentation, and configurable exclusions for page sections.
Dynamic content
The supplied evidence supports translation of WordPress site content through a widget or shortcode, but it does not establish how dynamic or runtime-generated content is handled beyond the documented page-section exclusion options.
SEO and metadata
No factual evidence was supplied showing SEO metadata translation, metadata rewriting, or search-engine-specific handling.
URLs and navigation
No factual evidence was supplied showing URL translation, localized URL structures, or navigation-specific behavior.
Forms and commerce
No factual evidence was supplied showing form handling, checkout behavior, or commerce-specific translation support.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Prisna GWT – Google Website Translator 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
- Evidence shows translation is provided through a widget or shortcode on WordPress sites, with selectable languages and inline or tabbed display styles. The available evidence does not establish support for specific content types beyond page content, nor does it establish behavior for admin-only areas, forms, commerce flows, SEO metadata, or URL handling.
COMMON QUESTIONS
Prisna GWT – Google Website Translator and REEID Translate FAQ.
Does the current evidence establish translation scope for Prisna GWT – Google Website Translator?
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.