SPELLMATIC
Spellmatic compatibility with REEID Translate
Spellmatic compatibility with REEID Translate is being evaluated from available plugin evidence. Full-site scanning across posts, pages, products, and comments, with no error cap (per provided readme text). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Spellmatic.
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
Spellmatic is documented in the Other 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 Spellmatic 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
- Full-site scanning across posts, pages, products, and comments, with no error cap (per provided readme text).
- Privacy-first grammar engine: Harper runs client-side as WebAssembly with no external connections during scanning (per provided readme text).
- Custom dictionary support to add words to ignore globally (per provided readme text).
- Scheduled email digests that include scan summaries (per provided readme text).
- Optional BYOK AI proofreading layer: when enabled and an AI scan is initiated, text is sent to a chosen AI provider using the user’s own API key; keys are encrypted and stored on the server (per provided readme text).
- Builder compatibility scanning (page builder content extraction): scans content inside multiple builders including Elementor (reads `_elementor_data` JSON widget data), Avada/Fusion Builder (parses Fusion shortcodes and page options), Divi (strips and scans Divi shortcode content), and WPBakery (scans WPBakery shortcode text), plus additional listed builders (per provided readme text).
- Freemius integration for license validation and plan management, with consent requested during plugin activation (per provided readme text).
Distinctive features
Full-site scanning across posts, pages, products, and comments, with no error cap (per provided readme text). Privacy-first grammar engine: Harper runs client-side as WebAssembly with no external connections during scanning (per provided readme text). Error handling workflow: scan results show errors with per-error fix/dismiss actions and an error dashboard with error-type badges and in-context display (per provided readme text). Custom dictionary support to add words to ignore globally (per provided readme text). Scheduled email digests that include scan summaries (per provided readme text). Optional BYOK AI proofreading layer: when enabled and an AI scan is initiated, text is sent to a chosen AI provider using the user’s own API key; keys are encrypted and stored on the server (per provided readme text). Builder compatibility scanning (page builder content extraction): scans content inside multiple builders including Elementor (reads `_elementor_data` JSON widget data), Avada/Fusion Builder (parses Fusion shortcodes and page options), Divi (strips and scans Divi shortcode content), and WPBakery (scans WPBakery shortcode text), plus additional listed builders (per provided readme text). Freemius integration for license validation and plan management, with consent requested during plugin activation (per provided readme text).
CONTENT BOUNDARY
Spellmatic 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
Spellmatic and REEID Translate FAQ.
What does Spellmatic do according to the available plugin evidence?
Spellmatic 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 Spellmatic?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Spellmatic?
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 Spellmatic in a multilingual WordPress workflow.
REEID documents Spellmatic 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.