AI SEO, GEO & Agentic Commerce Architect

    1

    Modular 2026 workflow for Technical SEO, Schema.org JSON-LD (ProductGroup), AI Search Optimization (llmstxt.org v2 & .md Shadow Corpus), Streamable HTTP MCP servers, and Agentic Commerce protocols (Google/Shopify UCP & OpenAI ACP).

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    AI SEO, GEO & Agentic Commerce Architect

    Example session with this skill installed

    Use ai-seo-skill to audit our Next.js e-commerce product page and implement 2026-compliant multi-variant JSON-LD (ProductGroup with strikethrough sale pricing), llmstxt.org v2 discovery headers, and a /llms.txt endpoint.

    • Read your context and instructions
    • Compiled the ai seo geo

    Summary

    Audited the storefront product route and upgraded the SEO & AI discovery stack to the

    2026 Google Search Central and

    llmstxt.org v2 standards (DOMAIN_PROFILE = COMMERCE, layers: CORE_SEO + AI_DISCOVERY).

    Audit AreaBeforeAfter (ai-seo-skill)
    Multi-Variant JSON-LDDeprecated AggregateOffer (disqualifies Merchant Listings)@type: "ProductGroup" with variesBy, hasVariant, brand, and StrikethroughPrice
    Description SanitizationRaw regex tag strip (<p>A</p><p>B</p> → "AB", \u0026amp; bug)5-step normalizeDescription + XSS-safe encodeJsonLd (\u003C, \u003E, \u0026, \u0027)
    Canonical URLIncluded ?sort=asc&utm_source=... (Spider Trap risk)Stripped all filter/tracking params; retained clean canonical path
    AI Agent DiscoveryNoneAdded /llms.txt, .md Shadow Corpus twin, and Link: rel="describedby" HTTP header

    1. Core Sanitization & XSS-Safe JSON-LD Serializer (src/lib/seo-utils.ts)

    import { normalizeDescription, encodeJsonLd } from './core_utils';
    
    export function buildProductGroupJsonLd(product: ProductDto) {
      const payload = {
        '@context': 'https://schema.org/',
        '@type': 'ProductGroup',
        name: product.title,
        description: normalizeDescription(product.rawHtmlDescription, 300),
        url: `https://example.com/products/${product.slug}`,
        productGroupID: String(product.id),
        brand: { '@type': 'Brand', name: product.brandName },
        variesBy: ['https://schema.org/color', 'https://schema.org/size'],
        hasVariant: product.variants.map((v) => ({
          '@type': 'Product',
          sku: v.sku,
          name: `${product.title} - ${v.color} / ${v.size}`,
          color: v.color,
          size: v.size,
          image: v.imageUrl,
          offers: {
            '@type': 'Offer',
            url: `https://example.com/products/${product.slug}?variant=${v.id}`,
            priceCurrency: v.currency,
            price: v.priceMajor,
            validFrom: v.saleValidFrom,
            validThrough: v.saleValidThrough,
            availability: v.inStock
              ? 'https://schema.org/InStock'
              : 'https://schema.org/OutOfStock',
            itemCondition: 'https://schema.org/NewCondition',
            ...(v.listPriceMajor > v.priceMajor
              ? {
                  priceSpecification: {
                    '@type': 'UnitPriceSpecification',
                    priceType: 'https://schema.org/StrikethroughPrice',
                    price: v.listPriceMajor,
                    priceCurrency: v.currency,
                  },
                }
              : {}),
          },
        })),
      };
    
      return encodeJsonLd(payload);
    }
    

    2. llmstxt.org v2 & Shadow Corpus Discovery Headers (middleware.ts)

    res.headers.append(
      'Link',
      '<https://example.com/llms.txt>; rel="describedby"; type="text/markdown"'
    );
    res.headers.append(
      'Link',
      `<https://example.com${pathname}.md>; rel="alternate"; type="text/markdown"`
    );
    

    Next steps

    • Run npm test to execute the unit test suite verifying normalizeDescription, encodeJsonLd, and toMinorUnits.
    • Optional: Enable Step 5 (AGENTIC_COMMERCE) if you want to expose /.well-known/ucp and OpenAI ACP products.jsonl feeds.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Equip your AI Coding Agent to audit and implement 2026-standard Technical SEO, Schema.org JSON-LD, GEO / AI Search Optimization (llmstxt.org v2), Streamable HTTP MCP Servers, and Agentic Commerce (UCP & OpenAI ACP) across any web stack.

    Why Developers Need This Skill

    Most LLM coding assistants rely on outdated training data when generating structured data, sitemaps, or AI endpoints—resulting in deprecated schemas, XSS vulnerabilities, and broken agent feeds. ai-seo-skill enforces the latest 2026 production specifications:

    • 2026 Google Search Central JSON-LD: Replaces deprecated AggregateOffer with @type: "ProductGroup" (variesBy + hasVariant), includes brand, and places validFrom / validThrough directly on Offer alongside StrikethroughPrice.
    • Anti-XSS & Anti-Double-Encoding Utilities: Includes drop-in Python & TypeScript reference utilities for normalizeDescription (5-step HTML block spacing + UTF-8 entity decode so &amp; never becomes \u0026amp;), encodeJsonLd (hex-escaping <, >, &, '), and toMinorUnits (strictly separating price_major for Schema.org from ISO 4217 price_minor integers for UCP/ACP).
    • llmstxt.org v2 & Markdown Shadow Corpus: Generates /llms.txt, /llms-full.txt, HTTP Link: <.../llms.txt>; rel="describedby" auto-discovery headers, per-page .md Shadow Corpus routes (rel="alternate"; type="text/markdown" reducing LLM token ingestion cost by ~95%), and granular robots.txt rules separating AI Search Bots (OAI-SearchBot, ChatGPT-User, PerplexityBot) from AI Training Crawlers (GPTBot, CCBot).
    • Streamable HTTP MCP Server (2026-07-28): Configures POST /mcp with mandatory DNS Rebinding protection (Origin validation rejecting Origin: null with HTTP 403, 127.0.0.1 local binding), Accept negotiation, _meta & Mcp-Session-Id propagation, and OAuth 2.1 / Bearer auth.
    • Agentic Commerce (UCP & OpenAI ACP): Implements GET /.well-known/ucp with RFC 9421 EC P-256 JWK signing_keys, /catalog/search, /lookup, /product, plus OpenAI /.well-known/acp.json and JSON Schema-validated products.jsonl feeds.

    Domain-Adaptive & Modular (Progressive Disclosure)

    The skill automatically detects your project's domain (COMMERCE, RESERVATION, SAAS_PLATFORM, CONTENT_PUBLISHING, or GENERIC_WEB) and loads only the reference layers you request—keeping context window usage minimal.

    Single-file XML sitemaps capped at 10k URLs. Requires manual OAuth configuration for private MCP tools. Does not support non-Python/TS templates.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 11 days ago

    Requires

    None
    macOS
    Node.js
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    src/**
    app/**
    *.md

    Reads existing routes/models to infer the project domain profile, writes SEO/JSON-LD/llms.txt/MCP/UCP endpoints, and runs the project's native test runner to verify compliance.

    Listed11 days ago

    What's inside

    Frequently Asked Questions

    Traditional SEO focuses on human readability, whereas AI SEO adds a 'Shadow Corpus' layer (via llms.txt and MCP servers) designed specifically for LLMs to crawl, index, and understand your data for Generative Engine Optimization (GEO).

    The skill is fully compatible with Python and TypeScript environments, and it is designed to work with any agent or platform that supports the Model Context Protocol (MCP) or OpenAI's Agentic Commerce Protocol.

    Yes, the skill includes specialized protocols for Agentic Commerce (UCP/ACP), allowing AI agents to understand pricing variants and execute secure automated transactions on your platform.

    You receive the full implementation logic for 2026-standard Schema.org, the AI discovery layer configuration, MCP server deployment templates, and a technical guide for integrating these into your existing codebase.

    The skill uses the 2026 Schema.org standard, which introduces `ProductGroup` logic for complex inventory and replaces outdated structures like `AggregateOffer` to ensure long-term compatibility with evolving search engines.

    While the skill automates the deployment of MCP servers over HTTP, you will still need to manually configure your OAuth 2.1 credentials to ensure secure access to your protected data.

    New in Marketing & SEO