
CARMA STRUCTURED DATA AND GEO AUDIT
Carma Structured Data and GEO Audit compatibility with REEID Translate
Carma Structured Data and GEO Audit compatibility with REEID Translate is being evaluated from available plugin evidence. Adds structured website profile data and related JSON files (ai-profile.json, ai-services.json, ai-faq.json) stored locally in the WordPress database No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Carma Structured Data and GEO Audit.
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
Carma Structured Data and GEO Audit is documented in the SEO category with 7 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 Carma Structured Data and GEO Audit 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
- Adds structured website profile data and related JSON files (ai-profile.json, ai-services.json, ai-faq.json) stored locally in the WordPress database
- Generates JSON-LD / Schema.org structured data output for the website
- Provides REST API endpoints under /wp-json/carma-geo/v1/ for machine-readable data
- Includes an optional llms.txt support feature for machine-readable website guidance
- Offers a simple GEO audit/checklist within the WordPress admin area
- Adds robots.txt hints for machine-readable endpoints
- Does not change the visible website layout and does not include visitor monitoring/log storage or external data sending
CONTENT BOUNDARY
Carma Structured Data and GEO Audit 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
Carma Structured Data and GEO Audit and REEID Translate FAQ.
What does Carma Structured Data and GEO Audit do according to the available plugin evidence?
Carma Structured Data and GEO Audit has 7 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 Carma Structured Data and GEO Audit?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Carma Structured Data and GEO Audit?
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 Carma Structured Data and GEO Audit in a multilingual WordPress workflow.
REEID documents Carma Structured Data and GEO Audit 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.