SIMON'S AUTO KEYWORD LINKER
Simon's Auto Keyword Linker compatibility with REEID Translate
Simon's Auto Keyword Linker compatibility with REEID Translate is being evaluated from available plugin evidence. Dynamically injects internal and external links into post content via the 'the_content' filter without modifying database entries No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Simon's Auto Keyword Linker.
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
Simon's Auto Keyword Linker 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 Simon's Auto Keyword Linker 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
- Dynamically injects internal and external links into post content via the 'the_content' filter without modifying database entries
- Applies case-insensitive, whole-word matching while excluding headings (H1-H6), existing anchor tags, and HTML entities
- Prevents self-linking by ignoring keywords that match their own target URL and prioritizes longer phrases to avoid partial matches
- Offers configurable link limits per keyword per page and optional 'nofollow noopener noreferrer' attributes for external URLs
- Includes a Smart Keyword Scanner that analyzes published content to suggest high-relevance internal linking opportunities based on frequency and title relevance
- Compatible with major page builders (Gutenberg, Elementor, Divi) and caching plugins as long as they utilize standard WordPress content filters
CONTENT BOUNDARY
Simon's Auto Keyword Linker 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
Simon's Auto Keyword Linker and REEID Translate FAQ.
What does Simon's Auto Keyword Linker do according to the available plugin evidence?
Simon's Auto Keyword Linker 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 Simon's Auto Keyword Linker?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Simon's Auto Keyword Linker?
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 Simon's Auto Keyword Linker in a multilingual WordPress workflow.
REEID documents Simon's Auto Keyword Linker 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.