WHOKNEW DIRECTORY SEO
WhoKnew Directory SEO – Repository Ranking & Readme Optimizer compatibility with REEID Translate
WhoKnew Directory SEO – Repository Ranking & Readme Optimizer compatibility with REEID Translate is being evaluated from available plugin evidence. Frontend client for whoknew.io ranking service; keyword scans, readme analysis, ranking calculations, and keyword research are performed exclusively on whoknew.io servers (plugin contains no ranking/analysis logic). No specific visitor-facing translation surface is currently confirmed.
Visit WhoKnew Directory SEO – Repository Ranking & Readme Optimizer ↗
AWAITING VERIFICATION
What the available evidence establishes for WhoKnew Directory SEO – Repository Ranking & Readme Optimizer.
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
WhoKnew Directory SEO – Repository Ranking & Readme Optimizer is documented in the SEO 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 WhoKnew Directory SEO – Repository Ranking & Readme Optimizer 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
- Frontend client for whoknew.io ranking service; keyword scans, readme analysis, ranking calculations, and keyword research are performed exclusively on whoknew.io servers (plugin contains no ranking/analysis logic).
- Keyword Scan workflow: enter a plugin slug and keyword to see the plugin’s exact position in WordPress.org plugin directory search results; scans consume API credits.
- Readme Optimizer workflow: analyzes a plugin’s readme.txt against 7 indexed readme fields (name, slug, tags, short description, description, author, contributors) and indicates which fields contain the keyword and which do not, with field-by-field suggestions.
- Repository ranking explanation: provides a “How Ranking Works” explainer describing the repository’s two-phase algorithm (relevance score and quality score) as documented by WordPress.org plugin directory source code.
- External service connectivity behavior: no passive data sent on page load; external calls occur on actions such as running a scan/readme analysis, clicking “Test connection” in Settings, and once per day via WordPress Cron to sync API credit balance locally.
- External API usage and caching model: during ranking scans, whoknew.io queries WordPress.org Plugin Directory API endpoints (plugins/info/1.2/ and query_plugins) from its own servers; results are cached on whoknew.io servers for up to 6 hours and shared across users scanning the same keyword.
- Client-side WordPress.org lookups: when looking up a plugin by slug or name in Scan/Readme Optimizer tabs, the browser contacts api.wordpress.org directly to fetch public plugin metadata; when loading readme.txt, the WordPress installation fetches it directly from plugins.svn.wordpress.org.
CONTENT BOUNDARY
WhoKnew Directory SEO – Repository Ranking & Readme Optimizer 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
WhoKnew Directory SEO – Repository Ranking & Readme Optimizer and REEID Translate FAQ.
What does WhoKnew Directory SEO – Repository Ranking & Readme Optimizer do according to the available plugin evidence?
WhoKnew Directory SEO – Repository Ranking & Readme Optimizer 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 WhoKnew Directory SEO – Repository Ranking & Readme Optimizer?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for WhoKnew Directory SEO – Repository Ranking & Readme Optimizer?
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 WhoKnew Directory SEO – Repository Ranking & Readme Optimizer in a multilingual WordPress workflow.
REEID documents WhoKnew Directory SEO – Repository Ranking & Readme Optimizer 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.