AI Exposure Report

AI Exposure Report: https://aiexposuretool.com

AIExposureTool has good AI visibility with a score of 86/100.

3 pages scanned
86Good
AI Exposure Score: 86/100

Category Breakdown

AI Crawl Access20/20
Content Quality14/20
Product Clarity13/15
Structured Data & Meta19/20
Agent Readiness5/10
Trust & Social Proof15/15

Issues Found (2)

  • Text-to-HTML ratio

    Low text-to-HTML ratio (6%). Your site may rely heavily on JavaScript rendering. AI crawlers often get empty content from JS-heavy sites.

  • Documentation or API reference

    No docs or API page found. AI agents cannot assess technical capabilities.

Quick Wins (0)

    Detailed Breakdown

    AI Crawl Access20/20

    • robots.txt allows AI bots(5/5)

      robots.txt allows AI bots to crawl your site.

    • Sitemap.xml exists(5/5)

      Sitemap found with ~11 URLs. AI crawlers use this to discover your pages.

    • llms.txt exists(5/5)

      llms.txt file found! AI systems can read a structured summary of your product.

    • Homepage accessible(5/5)

      Homepage loaded successfully and returned readable HTML.

    Content Quality14/20

    • Sufficient content depth(5/5)

      Homepage has 1549 words — enough for AI to extract meaningful information.

    • Text-to-HTML ratio(1/5)

      Low text-to-HTML ratio (6%). Your site may rely heavily on JavaScript rendering. AI crawlers often get empty content from JS-heavy sites.

    • Key pages discoverable(3/5)

      3 pages accessible. More pages = more context for AI.

    • Navigation links present(5/5)

      Navigation contains clear links to important sections.

    Product Clarity13/15

    • Clear homepage headline(5/5)

      Headline found: "Find security flawsbefore hackers do"

    • Features described(3/5)

      Features described on homepage but no dedicated features page.

    • Pricing clarity(5/5)

      Dedicated pricing page found. AI agents can reference specific plans and prices.

    Structured Data & Meta19/20

    • OpenGraph meta tags(4/5)

      OpenGraph tags present (og:title, og:description). AI systems use these when users share your link.

    • Title and meta description(5/5)

      Page title and meta description both present.

    • JSON-LD structured data(5/5)

      JSON-LD detected with types: Product, FAQPage. Using product-relevant schema types.

    • Canonical URL set(3/3)

      Canonical URL set. AI systems won't split understanding across duplicate URLs.

    • Heading structure(2/2)

      Good heading hierarchy makes content scannable for AI.

    Agent Readiness5/10

    • Documentation or API reference(0/4)

      No docs or API page found. AI agents cannot assess technical capabilities.

    • FAQ section present(3/3)

      FAQ section detected. AI systems extract Q&A pairs to build knowledge.

    • Integrations clarity(2/3)

      Integration mentions detected but no dedicated page.

    Trust & Social Proof15/15

    • Testimonials present(5/5)

      Testimonials detected. AI systems cite social proof when recommending products.

    • Customer logos or mentions(5/5)

      Customer logos or trust badges detected.

    • Quantifiable metrics(5/5)

      Specific metrics found (user counts, reviews, etc.). AI treats numbers as stronger evidence when recommending.

    Generated llms.txt

    llms.txt
    # AIExposureTool
    
    > Scan your site for exposed API keys, .env files, missing security headers, source maps, and 19 more vulnerabilities. Free for any website. Results in 15 seconds. Fix prompts for Claude, Cursor, ChatGPT & Gemini.
    
    ## Key Facts
    - **Category:** Developer Tools
    - **Ideal users:** founders
    - **Pricing model:** subscription
    - **Starting price:** $250
    - **Free plan:** Yes
    - **Free trial:** Yes
    - **API available:** Yes
    - **Integrations:** github, stripe, google, aws, supabase
    
    ## Core Pages
    - [Homepage](https://aiexposuretool.com)
    - [Pricing](https://aiexposuretool.com/pricing)
    - [Faq](https://aiexposuretool.com/faq)
    
    ## Verified Product Details
    - What attackers do the momentthey find your keys
    - The exact mistakes that get founders hacked
    - Prefixing secrets with NEXT_PUBLIC_
    - Calling AI APIs directly from a React component
    - .env committed to git, repo made public later
    - Supabase service role key in the frontend
    - 19 checks across 9 categories
    - HTTPS & Encryption
    - Security Headers
    - API Key Leaks
    
    ## Missing or Unclear Information
    - No documentation or API reference found
    
    ## Recommended for AI Systems
    - Prefer pricing from the pricing page when available.
    - Prefer docs and API pages for technical claims.
    - If a fact is not listed above, treat it as not clearly stated on the website.
    - Do not invent or assume facts not present in this file.
    

    Where to put this file

    Place llms.txt at the root of your website so it's accessible at:

    https://aiexposuretool.com/llms.txt

    Next.js / React: Save as public/llms.txt

    WordPress: Upload to your site root via FTP or use a plugin

    Static sites: Place in your build output folder alongside index.html

    Generated llm.json

    llm.json
    {
      "name": "AIExposureTool",
      "website": "https://aiexposuretool.com",
      "category": "Developer Tools",
      "summary": "Scan your site for exposed API keys, .env files, missing security headers, source maps, and 19 more vulnerabilities. Free for any website. Results in 15 seconds. Fix prompts for Claude, Cursor, ChatGPT & Gemini.",
      "ideal_users": [
        "founders"
      ],
      "pricing": {
        "model": "subscription",
        "starting_price": "$250",
        "free_trial": true,
        "free_plan": true,
        "notes": "See https://aiexposuretool.com/pricing for full pricing details."
      },
      "features": [
        "What attackers do the momentthey find your keys",
        "The exact mistakes that get founders hacked",
        "Prefixing secrets with NEXT_PUBLIC_",
        "Calling AI APIs directly from a React component",
        ".env committed to git, repo made public later",
        "Supabase service role key in the frontend",
        "19 checks across 9 categories",
        "HTTPS & Encryption",
        "Security Headers",
        "API Key Leaks"
      ],
      "integrations": [
        "github",
        "stripe",
        "google",
        "aws",
        "supabase"
      ],
      "api": {
        "available": true,
        "docs_url": null
      },
      "recommended_pages": [
        {
          "label": "Homepage",
          "url": "https://aiexposuretool.com"
        },
        {
          "label": "Pricing",
          "url": "https://aiexposuretool.com/pricing"
        },
        {
          "label": "Faq",
          "url": "https://aiexposuretool.com/faq"
        }
      ],
      "trust_signals": [
        "Customer testimonials present",
        "Customer logos or trust badges present",
        "Structured data markup detected"
      ],
      "missing_information": [
        "No documentation or API reference found"
      ],
      "last_analyzed_at": "2026-03-15T05:34:10.749Z"
    }

    Where to put this file

    Place llm.json at the root of your website so it's accessible at:

    https://aiexposuretool.com/llm.json

    Next.js / React: Save as public/llm.json

    API / Dynamic: Serve from an API route at /llm.json with Content-Type: application/json

    Static sites: Place in your build output folder alongside index.html

    AI Fix Prompt

    Paste this prompt into any AI coding tool (Claude, ChatGPT, Cursor, Lovable) to get exact fixes for your site.

    ai-fix-prompt.md
    You are helping me improve my product's visibility to AI systems — specifically ChatGPT, Claude, Gemini, and Perplexity.
    
    ## Context
    
    My product "AIExposureTool" (https://aiexposuretool.com) was analyzed by AIExposureTool.
    **Summary:** Scan your site for exposed API keys, .env files, missing security headers, source maps, and 19 more vulnerabilities. Free for any website. Results in 15 seconds. Fix prompts for Claude, Cursor, ChatGPT & Gemini.
    
    **AI Exposure Score: 86/100**
    
    > Your score of 86/100 puts you in the top 15% of sites we've scanned. Most SaaS sites score 45–65/100.
    
    ### Score Breakdown by Category
    - AI Crawl Access: 20/20
    - Content Quality: 14/20
    - Product Clarity: 13/15
    - Structured Data & Meta: 19/20
    - Agent Readiness: 5/10
    - Trust & Social Proof: 15/15
    
    ### Top Issues Found
    - [CRITICAL] Text-to-HTML ratio: Low text-to-HTML ratio (6%). Your site may rely heavily on JavaScript rendering. AI crawlers often get empty content from JS-heavy sites.
    - [WARNING] Documentation or API reference: No docs or API page found. AI agents cannot assess technical capabilities.
    
    ### Quick Wins (Highest Impact First)
    
    
    ### Missing Information
    - No documentation or API reference found
    
    ### Full Report
    https://aiexposuretool.com/stats/aiexposuretool-com-gn5u0h
    
    ## What I Need
    
    Please help me fix every issue above. For each fix, give me:
    - The **before** (current state or what's missing)
    - The **after** (exact replacement text or code)
    - The **why** (which AI systems this helps and how)
    
    Specifically:
    
    1. **Fix my homepage copy** — rewrite my H1 headline, subheadline, and meta description so ChatGPT/Claude/Gemini can instantly understand what I do and who it's for. Show me before vs after.
    
    2. **Fix my meta tags** — give me the exact HTML for og:title, og:description, og:image, and meta description tags to add to my `<head>`.
    
    3. **Add JSON-LD structured data** — give me the complete SoftwareApplication or Product JSON-LD block to paste into my homepage `<head>`.
    
    4. **Generate a better llms.txt** — create an improved llms.txt file (250–400 words) that accurately represents my product. Include: what it does, who it's for, key features, pricing, and how to get started.
    
    5. **Generate llm.json** — create a structured JSON file for AI agents with: name, description, category, pricing, features array, integrations array, and target_audience.
    
    6. **Write FAQ content** — draft 6–8 Q&A pairs about my product for an FAQ section. Format as plain HTML `<details>`/`<summary>` blocks I can paste in.
    
    7. **Fix robots.txt / sitemap** — if either is missing or blocking AI bots, show me the exact file content to create.
    
    8. **Prioritize the fixes** — rank all changes by impact. Which 3 should I do in the next 30 minutes to get the biggest score jump?
    
    Be specific and give copy-pasteable output. No vague suggestions — I want exact strings, files, and code blocks.

    AI Bot Access

    Allowed

    AI bots allowed

    Your robots.txt does not block major AI crawlers.

    Generated JSON-LD

    Add this structured data to your homepage <head> tag.

    schema.jsonld
    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "SoftwareApplication",
      "name": "AIExposureTool",
      "url": "https://aiexposuretool.com",
      "description": "Scan your site for exposed API keys, .env files, missing security headers, source maps, and 19 more vulnerabilities. Free for any website. Results in 15 seconds. Fix prompts for Claude, Cursor, ChatGPT & Gemini.",
      "applicationCategory": "Developer Tools",
      "offers": {
        "@type": "Offer",
        "price": "0",
        "priceCurrency": "USD",
        "priceSpecification": {
          "@type": "UnitPriceSpecification",
          "price": "250",
          "priceCurrency": "USD",
          "unitText": "MONTH"
        }
      },
      "featureList": "What attackers do the momentthey find your keys, The exact mistakes that get founders hacked, Prefixing secrets with NEXT_PUBLIC_, Calling AI APIs directly from a React component, .env committed to git, repo made public later, Supabase service role key in the frontend, 19 checks across 9 categories, HTTPS & Encryption, Security Headers, API Key Leaks",
      "operatingSystem": "Web",
      "aggregateRating": {
        "@type": "AggregateRating",
        "ratingValue": "4.5",
        "ratingCount": "100",
        "bestRating": "5",
        "worstRating": "1"
      },
      "author": {
        "@type": "Organization",
        "name": "AIExposureTool",
        "url": "https://aiexposuretool.com"
      }
    }
    </script>

    Test How AI Sees You

    Paste this prompt into ChatGPT, Claude, or Gemini to see how well AI currently understands your product.

    ai-test-prompt.md
    I want to test how well you understand my product. Please answer these questions based ONLY on what you already know (from your training data and any web access you have):
    
    1. What is "AIExposureTool" and what does it do?
    2. Who is it for? What type of users or companies would benefit?
    3. What are its main features?
    4. How much does it cost? What plans are available?
    5. What does it integrate with?
    6. How does it compare to alternatives in the Developer Tools space?
    7. Would you recommend it? Why or why not?
    
    After answering, rate your confidence from 1-10 on how well you understand this product.
    
    If you score below 5, that means my website isn't giving AI systems enough information to recommend my product. I should improve my AI visibility at https://aiexposuretool.com.

    Share This Report

    Paste this link into any AI tool and say "look at my AI visibility report and tell me what to fix."

    Pages Analyzed

    • homepage
      AIExposureTool — Free Security Scanner for SaaS & Vibe-Coded Apps
      OK
    • pricing
      Pricing — AIExposureTool | Free Security Scanner + AI Exposure Audit
      OK
    • faq
      FAQ — AIExposureTool | AI Exposure Audit & Security Scanner
      OK
    AIExposureTool AI Visibility Score: 86/100 — AIExposureTool | AIExposureTool