
AIVEC AI SEARCH SCHEMA
Aivec AI Search Schema compatibility with REEID Translate
Aivec AI Search Schema compatibility with REEID Translate is being reviewed using official plugin documentation. Generates JSON-LD structured data for Organization and LocalBusiness entities, including address, geo-coordinates, price range, payment methods, and service areas. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Aivec AI Search Schema 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
Aivec AI Search Schema is documented in the SEO 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.
COMPATIBILITY REVIEW
How Aivec AI Search Schema 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
- Generates JSON-LD structured data for Organization and LocalBusiness entities, including address, geo-coordinates, price range, payment methods, and service areas.
- Supports Article, FAQPage, QAPage, and Product schema types with per-post metabox controls and automatic WooCommerce product mapping.
- Outputs BreadcrumbList and ItemList structured data, with an optional frontend template for visual breadcrumb display.
- Includes WebSite metadata with SearchAction support to define site-wide search capabilities and supported languages.
- Automatically generates llms.txt files to assist AI systems in understanding site structure, with settings for manual editing.
- Provides self-diagnostics that validate required Google Rich Results properties and displays admin notices for missing fields.
- Integrates geocoding via Google Maps API with OpenStreetMap fallback, featuring rate limiting and caching for coordinate retrieval.
- Detects and suppresses conflicting schema outputs from popular SEO plugins such as Yoast SEO, Rank Math, and All in One SEO.
TRANSLATION BOUNDARY
Aivec AI Search Schema 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
Aivec AI Search Schema and REEID Translate FAQ.
What does Aivec AI Search Schema do?
Aivec AI Search Schema has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does Aivec AI Search Schema 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 Aivec AI Search Schema?
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 Aivec AI Search Schema in a multilingual WordPress workflow.
REEID documents Aivec AI Search Schema 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.