Build real WordPress AI workflows with LemonX.

Scenario: A site owner wants Claude to review an existing service page, improve the headline, add a stronger CTA and preview the change before applying it.

Review the Services page, improve the hero copy, add a clearer CTA, and show me the proposed changes before applying anything.

AI Client: Claude Desktop
MCP Server: LemonX MCP
Target: WordPress Services page

Step 1:
Claude calls get_site_identity to confirm the connected website.

Step 2:
Claude calls get_page with the page slug "services".

Step 3:
Claude analyzes the page structure and creates a proposed hero update.

Step 4:
Claude calls preview_content_update instead of directly saving changes.

Step 5:
The user reviews the before / after preview.

Step 6:
After approval, Claude calls apply_approved_update.

Step 7:
LemonX stores an MCP activity log.

Result: Claude can help update WordPress content without receiving uncontrolled admin access. The workflow stays human-reviewed and traceable.

Best For: Agencies · Site owners · Content editors · AI workflow builders · MCP testing · Safe page editing

Scenario: A company uses an external content planning tool. When an editor approves a topic, the system should create a draft inside WordPress and prepare it for SEO optimization.

curl -X POST "https://example.com/wp-json/lemonx/v1/content/drafts" 
  -H "Authorization: Bearer YOUR_API_TOKEN" 
  -H "Content-Type: application/json" 
  -d '{
    "type": "post",
    "title": "How AI Search Changes WordPress SEO",
    "status": "draft",
    "content": "Draft content goes here...",
    "categories": ["SEO", "AI Search"],
    "tags": ["AEO", "WordPress", "AI SEO"]
  }'

{
  "success": true,
  "data": {
    "id": 1284,
    "type": "post",
    "status": "draft",
    "title": "How AI Search Changes WordPress SEO",
    "edit_url": "https://example.com/wp-admin/post.php?post=1284&action=edit"
  },
  "meta": {
    "request_id": "lx_req_1001",
    "created_at": "2026-07-04T10:00:00Z"
  }
}

Best For: Editorial platforms · Content operations · Agency workflows · Internal marketing tools · Programmatic content pipelines

Scenario: A post already exists in WordPress, but it needs better SEO and AEO structure before publication.

GET  /wp-json/lemonx/v1/content/1284
POST /wp-json/lemonx/v1/aeo/analyze
POST /wp-json/lemonx/v1/aeo/schema/generate
POST /wp-json/lemonx/v1/aeo/internal-links/suggest
POST /wp-json/lemonx/v1/content/1284/preview-update

curl -X POST "https://example.com/wp-json/lemonx/v1/aeo/analyze" 
  -H "Authorization: Bearer YOUR_API_TOKEN" 
  -H "Content-Type: application/json" 
  -d '{
    "content_id": 1284,
    "target_keyword": "WordPress AI SEO",
    "intent": "informational",
    "include_aeo": true
  }'

{
  "success": true,
  "data": {
    "content_id": 1284,
    "seo_score": 78,
    "aeo_readiness": 64,
    "recommendations": [
      "Add a clearer definition section for AI search.",
      "Add FAQ questions matching user intent.",
      "Add Article and FAQ schema.",
      "Include internal links to related AEO pages."
    ]
  }
}

Result: The post becomes easier for search engines and AI answer engines to understand, summarize and cite.

Best For: SEO teams · Blog editors · Technical SEO workflows · AEO optimization · Client reporting

Scenario: When an English blog post is created, the site needs Spanish, French and German versions prepared through LemonX Verto.

GET  /wp-json/lemonx/v1/verto/languages
POST /wp-json/lemonx/v1/verto/queue
GET  /wp-json/lemonx/v1/tasks/{task_id}
POST /wp-json/lemonx/v1/verto/seo/generate

curl -X POST "https://example.com/wp-json/lemonx/v1/verto/queue" 
  -H "Authorization: Bearer YOUR_API_TOKEN" 
  -H "Content-Type: application/json" 
  -d '{
    "content_id": 1284,
    "source_language": "en",
    "target_languages": ["es", "fr", "de"],
    "include_seo_fields": true,
    "review_required": true
  }'

{
  "success": true,
  "task": {
    "id": "lx_task_translation_456",
    "type": "verto.translation.queue",
    "status": "queued",
    "content_id": 1284,
    "target_languages": ["es", "fr", "de"]
  }
}

Result: The translation workflow is queued, multilingual SEO fields can be generated and human review can be required before publishing.

Best For: Global websites · Cross-border ecommerce · B2B exporters · Multilingual blogs · Agency translation workflows

Scenario: A global content team wants to receive a Slack or internal dashboard notification when Verto completes a translation.

verto.translation_completed

{
  "event": "verto.translation_completed",
  "delivery_id": "lx_delivery_2001",
  "created_at": "2026-07-04T10:15:00Z",
  "site": {
    "id": "site_abc123",
    "url": "https://example.com",
    "name": "Example WordPress Site"
  },
  "resource": {
    "type": "post",
    "id": 1284,
    "title": "How AI Search Changes WordPress SEO"
  },
  "data": {
    "source_language": "en",
    "target_language": "fr",
    "status": "completed",
    "review_required": true
  }
}

Result: The content team does not need to manually check translation status. The external workflow starts automatically.

Best For: Translation teams · Global marketing teams · Agency dashboards · Make / n8n workflows · Internal notification systems

Scenario: Your system receives LemonX webhook events. Before processing them, you need to verify the signature.

function verify_lemonx_webhook( $raw_body, $timestamp, $signature_header, $secret ) {
    if ( empty( $raw_body ) || empty( $timestamp ) || empty( $signature_header ) || empty( $secret ) ) {
        return false;
    }

    $tolerance = 300;

    if ( abs( time() - (int) $timestamp ) > $tolerance ) {
        return false;
    }

    $signed_payload = $timestamp . '.' . $raw_body;
    $expected = 'sha256=' . hash_hmac( 'sha256', $signed_payload, $secret );

    return hash_equals( $expected, $signature_header );
}

Result: Your webhook endpoint only processes events that came from LemonX and were not modified in transit.

Best For: Webhook receivers · Security-sensitive integrations · Agency dashboards · Audit systems · Automation platforms

Scenario: An agency wants all AI-generated content to follow a consistent brand voice: clear, confident, practical and not overly hyped.

add_filter( 'lemonx_ai_prompt', function( $prompt, $context ) {
    $brand_rules = "
Brand voice rules:
- Use a clear and confident tone.
- Avoid exaggerated claims.
- Keep headings concise.
- Focus on practical value.
- Write for business decision-makers.
";

    return $brand_rules . "nn" . $prompt;
}, 10, 2 );

Result: Every LemonX AI generation workflow can inherit the same brand rules, reducing inconsistent output across pages, posts and reports.

Best For: Agencies · Brand teams · Content teams · Enterprise editorial workflows · AI output governance

Scenario: You want Claude or another MCP client to read and preview most pages, but not directly apply changes to pricing, checkout, account, privacy or terms pages.

add_filter( 'lemonx_mcp_apply_allowed', function( $allowed, $preview_id, $context ) {
    $protected_slugs = array(
        'pricing',
        'checkout',
        'my-account',
        'privacy',
        'terms'
    );

    if ( isset( $context['target_slug'] ) && in_array( $context['target_slug'], $protected_slugs, true ) ) {
        return false;
    }

    return $allowed;
}, 10, 3 );

Result: AI can still help review protected pages, but applying changes requires stronger manual control.

Best For: Production websites · Ecommerce sites · Agency clients · Enterprise workflows · Security-sensitive WordPress installs

Scenario: Your custom admin screen should show an advanced AEO report button only if the connected site has the correct LemonX entitlement.

GET /wp-json/lemonx/v1/pro/entitlements

{
  "success": true,
  "data": {
    "plan": "agency",
    "features": {
      "aeo.advanced_reports": true,
      "verto.translation_queue": true,
      "mcp.preview_apply": true,
      "cloud.ai_gateway": true
    }
  }
}

If aeo.advanced_reports is true:
  Show "Generate Advanced AEO Report"

If false:
  Show "Upgrade to unlock Advanced AEO Reports"

Result: Your interface respects licensing and plan access instead of exposing unavailable features.

Best For: Custom admin screens · Agency portals · Pro feature controls · Cloud-connected workflows · Enterprise dashboards

Scenario: After a high-value article or landing page is published, your integration should submit the URL to supported indexing channels through LemonX AEO.

curl -X POST "https://example.com/wp-json/lemonx/v1/aeo/indexing/submit" 
  -H "Authorization: Bearer YOUR_API_TOKEN" 
  -H "Content-Type: application/json" 
  -d '{
    "url": "https://example.com/blog/ai-search-wordpress-seo",
    "channels": ["google", "bing", "indexnow"],
    "reason": "new_content_published"
  }'

{
  "success": true,
  "data": {
    "url": "https://example.com/blog/ai-search-wordpress-seo",
    "status": "submitted",
    "channels": {
      "google": "queued",
      "bing": "submitted",
      "indexnow": "submitted"
    }
  }
}

Result: Publishing and indexing become part of the same workflow instead of separate manual steps.

Best For: SEO teams · News sites · Content teams · Programmatic SEO · Agency launch checklists

Scenario: An agency manages 30 client WordPress sites. The team wants a dashboard showing license status, site health, SEO progress, translation progress, MCP activity and usage warnings.

GET /wp-json/lemonx/v1/site
GET /wp-json/lemonx/v1/site/health
GET /wp-json/lemonx/v1/pro/license
GET /wp-json/lemonx/v1/pro/usage
GET /wp-json/lemonx/v1/aeo/overview
GET /wp-json/lemonx/v1/verto/reports
GET /wp-json/lemonx/v1/mcp/logs
GET /wp-json/lemonx/v1/reports/seo

Result: The agency can manage LemonX activity across all client sites without logging into each WordPress backend every day.

Best For: WordPress agencies · SEO agencies · Enterprise website networks · Client reporting · Multi-site operations

Scenario: An external app collects campaign details, then sends a request to LemonX Code to create a landing page draft inside WordPress.

GET  /wp-json/lemonx/v1/code/templates
POST /wp-json/lemonx/v1/code/pages/generate
POST /wp-json/lemonx/v1/content/drafts
POST /wp-json/lemonx/v1/aeo/analyze
POST /wp-json/lemonx/v1/content/{id}/preview-update

curl -X POST "https://example.com/wp-json/lemonx/v1/code/pages/generate" 
  -H "Authorization: Bearer YOUR_API_TOKEN" 
  -H "Content-Type: application/json" 
  -d '{
    "page_type": "landing_page",
    "topic": "AI SEO Services for WordPress",
    "audience": "WordPress agencies",
    "primary_cta": "Book a Demo",
    "target_keyword": "WordPress AI SEO service",
    "template": "saas-service-page"
  }'

Result: A structured landing page draft is generated with sections, copy, CTA and SEO-ready structure.

Best For: SaaS tools · Agency platforms · Landing page builders · Campaign automation · Programmatic service pages

Scenario: Every Monday, an agency wants to generate a report summarizing SEO progress, AEO opportunities, content updates, translations and MCP actions.

GET  /wp-json/lemonx/v1/reports/seo
GET  /wp-json/lemonx/v1/reports/content
GET  /wp-json/lemonx/v1/reports/translation
GET  /wp-json/lemonx/v1/reports/mcp
POST /wp-json/lemonx/v1/reports/export

report.generated

Result: The agency can deliver consistent reports without manually collecting data from multiple plugin screens.

Best For: SEO agencies · Client reporting · Marketing teams · Growth operations · Monthly retainers

Scenario: Your site runs translation queues, AI generation tasks and indexing requests. You want to know when something fails.

{
  "event": "task.failed",
  "delivery_id": "lx_delivery_3001",
  "created_at": "2026-07-04T10:30:00Z",
  "data": {
    "task_id": "lx_task_789",
    "task_type": "verto.translation",
    "status": "failed",
    "error_code": "provider_unavailable",
    "message": "Translation provider is unavailable."
  }
}

Result: Failed workflows become visible quickly instead of silently blocking growth operations.

Best For: Agencies · Global content teams · Technical SEO teams · Operations dashboards · Enterprise monitoring

Scenario: A webhook tells your system that an AEO report has been generated. Instead of sending the full report inside the webhook, your app uses the REST API to fetch report details.

{
  "event": "report.generated",
  "delivery_id": "lx_delivery_4001",
  "data": {
    "report_id": "lx_report_901",
    "report_type": "seo"
  }
}

curl -X GET "https://example.com/wp-json/lemonx/v1/reports/lx_report_901" 
  -H "Authorization: Bearer YOUR_API_TOKEN"

Result: Webhook payloads stay lightweight, while REST API provides full data when needed.

Best For: Client portals · Dashboards · Automation platforms · Large reports · Security-conscious integrations

Scenario: A marketing team wants AI to generate new page copy, but no change should go live without editor approval.

Result: The team gets AI speed without losing editorial control.

Best For: Enterprise teams · Agencies · Client approval workflows · Legal-sensitive websites · Production content updates

Scenario: A B2B company needs product names, technical terms and brand phrases to remain consistent during translation.

add_filter( 'lemonx_verto_glossary_terms', function( $terms, $target_language ) {
    $terms[] = array(
        'source' => 'LemonX',
        'target' => 'LemonX',
        'rule'   => 'never_translate',
    );

    $terms[] = array(
        'source' => 'Answer Engine Optimization',
        'target' => 'Answer Engine Optimization',
        'rule'   => 'preserve',
    );

    $terms[] = array(
        'source' => 'MCP',
        'target' => 'MCP',
        'rule'   => 'preserve',
    );

    return $terms;
}, 10, 2 );

Result: Translations become more consistent and brand-safe across languages.

Best For: B2B exporters · Technical websites · SaaS documentation · Multilingual SEO · Product-heavy websites

Scenario: A developer wants to use a cost-efficient model for drafts, a stronger model for final landing pages and a specialized provider for translations.

add_filter( 'lemonx_ai_model', function( $model, $context ) {
    if ( isset( $context['workflow'] ) && 'draft_generation' === $context['workflow'] ) {
        return 'fast-draft-model';
    }

    if ( isset( $context['workflow'] ) && 'landing_page_final' === $context['workflow'] ) {
        return 'premium-reasoning-model';
    }

    if ( isset( $context['workflow'] ) && 'translation' === $context['workflow'] ) {
        return 'translation-optimized-model';
    }

    return $model;
}, 10, 2 );

Result: The site uses AI more efficiently by routing requests based on cost, quality and task type.

Best For: High-volume sites · Agencies · Cost-control workflows · Enterprise AI governance · AI provider management

Scenario: An agency platform automatically creates a webhook subscription when a new client site is connected.

curl -X POST "https://example.com/wp-json/lemonx/v1/webhooks" 
  -H "Authorization: Bearer YOUR_API_TOKEN" 
  -H "Content-Type: application/json" 
  -d '{
    "name": "Agency Platform",
    "url": "https://agency.example.com/webhooks/lemonx",
    "events": [
      "content.updated",
      "aeo.analysis_completed",
      "verto.translation_completed",
      "mcp.preview_applied",
      "task.failed"
    ],
    "status": "active"
  }'

{
  "success": true,
  "data": {
    "id": "wh_123",
    "name": "Agency Platform",
    "status": "active",
    "events": [
      "content.updated",
      "aeo.analysis_completed",
      "verto.translation_completed",
      "mcp.preview_applied",
      "task.failed"
    ],
    "secret_preview": "whsec_****abcd"
  }
}

Result: The new client site automatically starts sending LemonX activity events to the agency platform.

Best For: Agency SaaS platforms · Client portals · Automation systems · Multi-site dashboards · Onboarding flows