Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    SEO Intelligence

    1

    Audit and fix technical SEO issues, Core Web Vitals, and AI crawler visibility directly in your codebase.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    SEO Intelligence

    SEO Intelligence

    Example session with this skill installed

    Run a full SEO audit on http://localhost:3000 and check if AI crawlers like ClaudeBot can access the documentation pages.

    • Read your context and instructions
    • Compiled the seo intelligence
    • Generated the document

    Audit completed for http://localhost:3000. I found one critical indexability blocker and confirmed that AI crawlers are currently allowed, though structured data is missing for the documentation.

    SEO Audit Results: http://localhost:3000

    CategoryStatusFindingRecommendation
    Indexability❌ FailX-Robots-Tag: noindex found in headers.Remove header in next.config.js.
    AI Access✅ PassClaudeBot and GPTBot are allowed.No action needed.
    Schema⚠️ WarningMissing TechArticle structured data.Add JSON-LD to docs/[slug]/page.tsx.
    Discovery✅ Passsitemap.xml found via robots.txt.No action needed.
    Metadata⚠️ WarningTitle tag exceeds 60 characters.Shorten title in layout.tsx.

    Baseline Comparison: Baseline established. The noindex header is the primary reason this site will not be indexed if deployed.

    Next steps

    1. I will remove the noindex header from your next.config.js file.
    2. I will generate and inject TechArticle JSON-LD into the documentation template.
    3. We will re-run the audit to verify the X-Robots-Tag now returns 200 OK without restrictions.

    page.tsx

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    Technical SEO is a frequent source of invisible friction. A page looks perfect but won't index, or a site-wide template change accidentally blocks crawlers. This skill identifies why content isn't ranking and fixes the underlying code.

    What it does

    • Full site audits to identify indexability blockers, broken links, and redirect chains.
    • Core Web Vitals measurement using Lighthouse to analyze mobile performance and LCP images.
    • AI crawler analysis to check visibility for agents like GPTBot, ClaudeBot, and Gemini.
    • Structured data validation for JSON-LD, Organization schema, and FAQ rich results.
    • Multi-language verification of hreflang tags and return-link clusters.
    • Automated code fixing that maps SEO findings to project files and applies the repair.

    How it works

    1. Tool discovery starts by verifying the presence of the technical-seo MCP server.
    2. Audit execution involves selecting the specific check, such as seo_full_audit for single pages or crawl_audit for site-wide discovery.
    3. Triage and fix identifies indexability blockers first, finds the source file in your framework, and applies the necessary code changes.
    4. Verification re-runs the audit with baseline comparison to prove the fix works before deployment.

    Frameworks & tools

    Works with Next.js, Nuxt, Astro, SvelteKit, Remix, Gatsby, and WordPress. Supports deployment platforms like Vercel, Netlify, and Cloudflare, along with standard web servers like Nginx and Apache.

    Why this beats prompting it yourself

    Generic prompts can't fetch live HTTP headers, check robots.txt logic, or run Lighthouse simulations. This skill uses a dedicated MCP server to gather real-world data, preventing halluncinations about why a page is missing from search results.

    Use cases

    • Auditing a staging site before a major migration to prevent ranking loss.
    • Fixing "Discovered - currently not indexed" errors in Search Console.
    • Optimizing a codebase for visibility in AI-powered search engines.
    • Generating client-ready SEO reports with verified code fixes.

    Known limitations

    Lighthouse checks require Google Chrome and take 1 to 2 minutes. The crawler does not execute JavaScript unless using the Lighthouse tool, which is intended to surface SPA rendering issues.

    Lighthouse requires Chrome. No JS execution during standard crawls. Fixes to CDN headers or redirects may require deployment to verify. Crawl limit is 100 pages.

    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 28 days ago

    Requires

    Technical Seo MCP
    Node.js
    ENOENT

    Permissions

    Network Access
    Write Files
    Listed1 month ago
    Updated28 days ago

    What's inside

    Frequently Asked Questions

    This skill uses a specialized MCP server to fetch live HTTP headers and run real-world Lighthouse simulations, whereas standard LLMs often hallucinate SEO data based on static text. It doesn't just diagnose issues; it maps findings directly to your source files to apply verified code fixes.

    It is compatible with all major modern frameworks including Next.js, Nuxt, Astro, SvelteKit, Remix, and Gatsby, as well as traditional setups like WordPress and Nginx. It works with any AI agent that supports the Model Context Protocol (MCP).

    Beyond standard Googlebot checks, this skill specifically analyzes your site's visibility for LLM-based crawlers like GPTBot, ClaudeBot, and Gemini. It ensures your robots.txt and structured data are optimized for inclusion in AI-powered search results.

    Yes, the Lighthouse and site audit tools identify specific performance bottlenecks like Large Contentful Paint (LCP) and Cumulative Layout Shift (CLS). The skill then identifies the specific components or CSS in your codebase causing the lag and proposes direct repairs.

    The Lighthouse tool requires Google Chrome to be installed on the environment where the MCP server is running. While the standard crawler is lightweight, Lighthouse audits typically take 1-2 minutes per page to simulate real-world mobile performance accurately.

    New in LLM Ops