HARPERFLOW
HarperFlow compatibility with REEID Translate
HarperFlow compatibility with REEID Translate is being evaluated from available plugin evidence. Integrates with Yoast SEO and Rank Math to write title and description metadata, or emits basic meta tags if no supported SEO plugin is active. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for HarperFlow.
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
HarperFlow is documented in the SEO category with 6 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 HarperFlow 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
- Integrates with Yoast SEO and Rank Math to write title and description metadata, or emits basic meta tags if no supported SEO plugin is active.
- Generates FAQPage structured data in JSON-LD format for HarperFlow-authored posts to enhance visibility in search engines and AI answer platforms.
- Registers custom post metadata (_hf_*) with REST API exposure to allow external services to inject SEO, FAQ, and TL;DR content programmatically.
- Re-exposes hidden Yoast and Rank Math SEO meta keys via the WordPress REST API to facilitate third-party integration.
- Provides a health check endpoint (/wp-json/harperflow/v1/health) that identifies the active SEO engine for external service compatibility.
- Applies scoped styling and content enhancements (TL;DR boxes, FAQ accordions) exclusively to posts authored by HarperFlow without affecting site-wide templates.
CONTENT BOUNDARY
HarperFlow 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
HarperFlow and REEID Translate FAQ.
What does HarperFlow do according to the available plugin evidence?
HarperFlow has 6 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 HarperFlow?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for HarperFlow?
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 HarperFlow in a multilingual WordPress workflow.
REEID documents HarperFlow 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.