
CADOSY SEO & SITE MANAGEMENT API
Cadosy SEO & Site Management API compatibility with REEID Translate
Cadosy SEO & Site Management API compatibility with REEID Translate is being evaluated from available plugin evidence. Provides an authenticated WordPress REST API under the `ai-site-controller/v1` namespace for SEO and site management tasks. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Cadosy SEO & Site Management API.
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
Cadosy SEO & Site Management API is documented in the SEO 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 Cadosy SEO & Site Management API 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 an authenticated WordPress REST API under the `ai-site-controller/v1` namespace for SEO and site management tasks.
- SEO meta endpoints can read and update SEO title, description, focus keyword, canonical URL, robots directives, and Open Graph fields; when RankMath or Yoast SEO is active, it bridges to their meta, otherwise it uses its own lightweight meta-tag output.
- Sitemap endpoints can inspect the core WordPress sitemap, toggle search-engine visibility, and exclude specific post types or taxonomies.
- Redirects endpoints can list, create, and delete simple path-based redirects.
- Permalinks endpoints can read and update the permalink structure.
- Block editing endpoints can list, insert, update, delete, and reorder blocks in a post.
CONTENT BOUNDARY
Cadosy SEO & Site Management API 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
Cadosy SEO & Site Management API and REEID Translate FAQ.
What does Cadosy SEO & Site Management API do according to the available plugin evidence?
Cadosy SEO & Site Management API 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 Cadosy SEO & Site Management API?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Cadosy SEO & Site Management API?
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 Cadosy SEO & Site Management API in a multilingual WordPress workflow.
REEID documents Cadosy SEO & Site Management API 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.