RANKPARSE SEO

RankParse SEO compatibility with REEID Translate

RankParse SEO compatibility with REEID Translate is being reviewed using official plugin documentation. Adds an admin dashboard widget showing SEO health score, domain authority, and referring domain count for the configured site. No specific text shown to visitors is currently confirmed for translation.

Visit RankParse SEO ↗

AWAITING VERIFICATION

What RankParse SEO does

Official plugin information supports the compatibility context documented for this category.

MANUAL REVIEW
This integration has not yet been manually verified by REEID.

PLUGIN PROFILE
RankParse SEO is documented in the SEO category with 6 documented features.

DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.

COMPATIBILITY REVIEW

How RankParse SEO compatibility is evaluated

01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.

02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.

03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.

04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.

PLUGIN INFORMATION

What the plugin does

Plugin capabilities

  • Adds an admin dashboard widget showing SEO health score, domain authority, and referring domain count for the configured site.
  • Provides a “RankParse Report” admin page that displays a full backlink health report with risk flags, link quality breakdown, anchor text profile, top/risky backlinks, and outbound link summary, with on-demand refresh.
  • Implements a hosted backlink-report embed via the `[rankparse_score]` shortcode and a corresponding block; the hosted widget loads on published pages where the shortcode/block is placed.
  • Supports shortcode/block attributes for configuring embedded widget behavior and presentation, including `domain`, `color`, `bg`, `name`, `api_key`, and `height` (as described in the plugin readme).
  • Uses a private RankParse API key configured in the plugin’s Settings for dashboard/report data requests to `api.rankparse.com`, while the hosted widget can optionally use a separate public embed key for white-labeling.
  • When the hosted embedded form is submitted, the visitor’s domain and email address are sent to RankParse so RankParse can generate and deliver a requested PDF SEO report (as described in the plugin readme).

TRANSLATION BOUNDARY

RankParse SEO capabilities and translatable content are documented separately.

Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.

A feature is not considered translatable unless it includes text that users can read.

LIMITATIONS & QA

Verification notes

  • This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.

FREQUENTLY ASKED QUESTIONS

RankParse SEO and REEID Translate FAQ.

What does RankParse SEO do?

RankParse SEO has 6 documented features listed in its official documentation. See the Plugin Information section for details.

Does RankParse SEO have any content currently confirmed for translation?

No specific content is currently confirmed for translation in this integration.

What needs to be confirmed before translating content from RankParse SEO?

Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.

RELATED GUIDES

Explore more compatibility guides.

COMPATIBILITY INFORMATION

Evaluate RankParse SEO in a multilingual WordPress workflow.

REEID documents RankParse SEO functionality separately from confirmed translation support so the distinction is clear.

Supported content will be listed when specific translatable text is identified in the official documentation.

Shopping Cart
Scroll to Top