CORE LISTING
Core Listing compatibility with REEID Translate
Core Listing compatibility with REEID Translate is being evaluated from available plugin evidence. Provides three embed options—shortcodes and corresponding blocks—for active inventory, sold/closed transactions, and a public team roster. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Core Listing.
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
Core Listing is documented in the Other 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 Core Listing 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
- Provides three embed options—shortcodes and corresponding blocks—for active inventory, sold/closed transactions, and a public team roster.
- Renders listing cards as a responsive grid; each card links to the full listing page on the Core Listing portal.
- Supports filtering and display controls for embedded content (e.g., office, property type/status, price range, sort order, result limit, and column count) via shortcode/block attributes.
- Maintains local caching of listings using WordPress transients; clears cache quickly via signed webhooks (HMAC-SHA256 verification) when listing data changes.
- Requires an API key to connect; makes outbound requests to Core Listing only for specific actions such as rendering when cache is cold, testing the connection, registering webhooks, and a daily background re-check of the white-label domain.
- Verifies and uses a configured white-label domain so listing links can point to the brokerage’s branded host; also supports styling via stable semantic HTML and documented CSS class names.
CONTENT BOUNDARY
Core Listing 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
Core Listing and REEID Translate FAQ.
What does Core Listing do according to the available plugin evidence?
Core Listing 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 Core Listing?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Core Listing?
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 Core Listing in a multilingual WordPress workflow.
REEID documents Core Listing 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.