GV-RE LISTINGS
GV-RE Listings compatibility with REEID Translate
GV-RE Listings compatibility with REEID Translate is being evaluated from available plugin evidence. Registers a REST-enabled custom post type for properties. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for GV-RE Listings.
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
GV-RE Listings is documented in the Other category with 8 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 GV-RE Listings 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
- Registers a REST-enabled custom post type for properties.
- Provides property-related taxonomies (property type, amenities, region/state, city/district, neighborhood/locality) and extensive property fields with admin editing.
- Implements theme-independent archive, property card, and single-property templates, with optional template overrides under a theme-specific directory.
- Supports AJAX property search with shareable URL filters and provides shortcodes for search/listings/single-property views.
- Includes a private, indexed lead table and a rate-limited inquiry endpoint, plus new-inquiry email notifications and a basic private lead inbox.
- Uses Freemius for site licensing/account management, upgrades, and checkout; payment details are handled in Freemius-hosted checkout and not stored by the plugin.
- Provides structured data when Yoast SEO or Rank Math is not active.
- AI-related items in the usage plans are entitlements only; the plugin version described does not connect to an AI provider, generate content, or consume AI credits.
CONTENT BOUNDARY
GV-RE Listings 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
GV-RE Listings and REEID Translate FAQ.
What does GV-RE Listings do according to the available plugin evidence?
GV-RE Listings has 8 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 GV-RE Listings?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for GV-RE Listings?
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 GV-RE Listings in a multilingual WordPress workflow.
REEID documents GV-RE Listings 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.