
VL RELATED POSTS BY TAXONOMY
VL Related Posts by Taxonomy compatibility with REEID Translate
VL Related Posts by Taxonomy compatibility with REEID Translate is being reviewed using official plugin documentation. {"task": "Research factual plugin behavior for compatibility context only. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What VL Related Posts by Taxonomy 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
VL Related Posts by Taxonomy is documented in the Other category with 8 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.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- {"task": "Research factual plugin behavior for compatibility context only.
- Do not extract translation-surface observations.", "plugin_identity": {"name": "VL Related Posts by Taxonomy", "slug": "vl-related-posts-by-taxonomy", "homepage_url": "", "plugin_url": ""}, "official_search_domains": ["wordpress.org"], "rules": ["Return one JSON object only.", "Use only facts supported by supplied plugin evidence or web research from the allowed official domains.", "Use web search only when supplied evidence is insufficient.", "For web research, use only first-party vendor/product documentation and WordPress.org sources within official_search_domains.", "Do not use reviews, blogs, forums, aggregators, search snippets, or third-party documentation as evidence.", "Do not invent plugin behavior, capabilities, settings, or integrations.", "Do not decide REEID compatibility, translation support, approval, or eligibility.", "Follow category_research.rules for what to investigate in this Integration Category.", "Return observations as an empty list.", "Return 4 to 8 concise high-value factual capabilities in features.", "Group related implementation details into broader capability statements.", "Prefer stable product capabilities over minor settings or repeated variations.", "Do not include ratings, installation counts, version requirements, or promotional claims.", "Use unknowns only for materially relevant facts that official evidence does not establish.", "seo_display_name must be the shortest distinctive search-facing product or brand identity that can be copied exactly as one contiguous phrase from plugin_identity.name.
- Preserve the exact capitalization, spelling, and punctuation used in plugin_identity.name.
- Never invent, rename, expand, normalize, lowercase, or substitute the plugin brand.
- Remove generic leading or trailing descriptors when a shorter distinctive product or brand phrase is present, including terms such as Plugin, WordPress Plugin, Page Builder, Website Builder, WooCommerce, Forms, SEO, Addons, Widgets, Templates, Booking, Membership, or similar category/marketing wording.
- The distinctive brand may appear at the beginning, middle, or end of plugin_identity.name; for example, a title shaped like generic description – Brand should return Brand when Brand is clearly the product identity.
- When a short distinctive acronym, product token, or branded abbreviation appears after a separator and clearly identifies the plugin, prefer that exact token over the preceding generic description; for example Database Addon for Contact Form 7 – CFDB7 should return CFDB7.
- Use plugin_identity.slug only as an identity clue, not as output text unless that exact casing and phrase also appears in plugin_identity.name.
Distinctive features
{"task": "Research factual plugin behavior for compatibility context only. Do not extract translation-surface observations.", "plugin_identity": {"name": "VL Related Posts by Taxonomy", "slug": "vl-related-posts-by-taxonomy", "homepage_url": "", "plugin_url": ""}, "official_search_domains": ["wordpress.org"], "rules": ["Return one JSON object only.", "Use only facts supported by supplied plugin evidence or web research from the allowed official domains.", "Use web search only when supplied evidence is insufficient.", "For web research, use only first-party vendor/product documentation and WordPress.org sources within official_search_domains.", "Do not use reviews, blogs, forums, aggregators, search snippets, or third-party documentation as evidence.", "Do not invent plugin behavior, capabilities, settings, or integrations.", "Do not decide REEID compatibility, translation support, approval, or eligibility.", "Follow category_research.rules for what to investigate in this Integration Category.", "Return observations as an empty list.", "Return 4 to 8 concise high-value factual capabilities in features.", "Group related implementation details into broader capability statements.", "Prefer stable product capabilities over minor settings or repeated variations.", "Do not include ratings, installation counts, version requirements, or promotional claims.", "Use unknowns only for materially relevant facts that official evidence does not establish.", "seo_display_name must be the shortest distinctive search-facing product or brand identity that can be copied exactly as one contiguous phrase from plugin_identity.name. Preserve the exact capitalization, spelling, and punctuation used in plugin_identity.name. Never invent, rename, expand, normalize, lowercase, or substitute the plugin brand. Remove generic leading or trailing descriptors when a shorter distinctive product or brand phrase is present, including terms such as Plugin, WordPress Plugin, Page Builder, Website Builder, WooCommerce, Forms, SEO, Addons, Widgets, Templates, Booking, Membership, or similar category/marketing wording. The distinctive brand may appear at the beginning, middle, or end of plugin_identity.name; for example, a title shaped like generic description – Brand should return Brand when Brand is clearly the product identity. When a short distinctive acronym, product token, or branded abbreviation appears after a separator and clearly identifies the plugin, prefer that exact token over the preceding generic description; for example Database Addon for Contact Form 7 – CFDB7 should return CFDB7. Use plugin_identity.slug only as an identity clue, not as output text unless that exact casing and phrase also appears in plugin_identity.name. If no shorter distinctive product or brand phrase can be selected safely, return the full plugin_identity.name.", "seo_keyword_candidates must contain 2 to 4 concise plugin-specific identity phrases based on seo_display_name, plugin_identity.name, and plugin_identity.slug. When the slug corresponds to a brand or product phrase present in the official name, include that phrase as a candidate. Do not return generic category-only phrases and do not assert REEID compatibility, verification, translation support, or other unsupported state claims."], "category_research": {"integration_category": "Other", "mode": "compatibility_only", "rules": ["Research concise factual plugin behavior from official sources for compatibility context without assuming any translation surface.", "This Integration Category is compatibility-only.", "Do not research, infer, or emit translation-surface observations.", "Return observations as an empty list.", "Use features and unknowns only for factual compatibility context."], "evidence_focus": {"integration_category": "Other", "look_for_literal_terms": []}}, "output_schema": {"observations": [{"text": "", "evidence": "", "source_url": ""}], "features": [], "unknowns": [], "seo_display_name": "", "seo_keyword_candidates": []}, "evidence": {"description": "[VL Related Posts by Taxonomy] is a powerful plugin for WordPress that allows you to display a list of related posts on your website and in your feed.\n It shows the list of posts on the pages on the basis of the vrp-tags . It relates all the posts having the same vrp-tags .\n Although several similar plugins exist today, VL Related Posts by Taxonomy is one of the most powerful plugin that can support all of your custom post types. Only you have to select the post types to be suported by this plugin in its options page. It mapped the specified number of posts to the posts only once and stores them in the databse. So that it will not repeat the process of mapping.\n Key features\n ShortCode : WRP will start displaying related posts on your site and feed to the place where you will add the ShortCode when you activate the plugin and assign the post types tp display.\n Custom Template : You can define your own custom template in the settings page to customize the related posts sections.\n Custom Tags : You can define your own custom vrp tags on basis of which related posts section will be populated.\n Widgets : Add related posts to widgetized areas.", "installation_instructions": "Upload the vl-related-posts-by-taxonomy folder to the /wp-content/plugins/ directory\nActivate the plugin through the 'Plugins' menu in WordPress\nGo to Settings > VL Related Posts to configure the plugin", "changelog": null}}}
TRANSLATION BOUNDARY
VL Related Posts by Taxonomy 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.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate VL Related Posts by Taxonomy in a multilingual WordPress workflow.
REEID documents VL Related Posts by Taxonomy 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.