Checking…

cctvcamerabuilder.com

Shopify · 50% confidenceE-COMMERCE
https://cctvcamerabuilder.com/
D35 / 100
Grade D · Level 2ReadableWeak — agents will struggle with most tasks here.
Why we think this is Shopify (1 signals)
  • · cdn.shopify.com assets
6 checks need fixing

6 failed out of 9 that apply to your site.

See top fixes

Quick Wins

Top 3 fixes ranked by score impact

  • 01Fail

    Markdown content negotiation

    +8 pts if fixed

    Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.

    See full details
  • 02Fail

    /llms.txt

    +6 pts if fixed

    Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.

    See full details
  • 03Fail

    Explicit AI bot rules

    +5 pts if fixed

    Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.

    See full details
Hand-off prompt for your coding agent6 issues
# Shopify agent-readiness fixes

Site: https://cctvcamerabuilder.com/
Platform: shopify (50% confidence)
AIScan score: 35/100 — Level 2 (Readable)
Rubric: v2026-06-08.2

## Failing checks
- **[C1] Markdown content negotiation** — FAIL
  - Evidence: no response
  - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- **[C2] /llms.txt** — FAIL
  - Evidence: HTTP 404
  - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- **[B2] Explicit AI bot rules** — FAIL
  - Evidence: 0 known AI agent(s) addressed in robots.txt
  - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- **[P1] API Catalog (RFC 9727)** — FAIL
  - Evidence: 404 at /.well-known/api-catalog
  - Fix: Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
- **[P4] OAuth discovery metadata** — FAIL
  - Evidence: auth-server: 404, protected-resource: 404
  - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- **[D3] Link header for discovery** — FAIL
  - Evidence: no Link header or <link> tag
  - Fix: Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.

## How to apply on Shopify
- **robots.txt**: edit `templates/robots.txt.liquid` to add AI bot directives (Shopify allows full override).
- **llms.txt**: create a page `/pages/llms-txt` and a redirect `/llms.txt → /pages/llms-txt` (Shopify URL redirects). Content should index collections + key product/policy pages.
- **Markdown negotiation**: not natively supported — expose JSON-LD richly on PDPs (Product, Offer, AggregateRating) as the agent-readable surface.
- **Commerce (UCP / x402)**: track Agentic Commerce Protocol support — currently Shopify-side; nothing for merchants to deploy yet beyond keeping Storefront API + checkout permissions clean.
- **Bot rules**: respect Shopify's bot-management UI in Settings → Customer events / Security.

Discoverability

77

Can agents find your pages? robots, sitemaps, llms.txt.

21
  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · D3

    What we found

    no Link header or <link> tag

    How to fix it

    Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.

    ⚡ Fix automatically with AIScan

    Option A — Agent Skill (any agent runtime)
    Install the AIScan skill in one command:
    ```
    npx add-skill https://aiscan.site/aiscan-skill.json
    ```
    Or download it directly: https://aiscan.site/aiscan-skill.json
    Then ask your agent: "Fix the failing AI readiness checks for <your-url>"

    Option B — Claude Code skill (CLAUDE.md)

    1. Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
    2. Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.

    Option C — MCP (Claude Desktop, Cursor, or any MCP client)

    • Endpoint: https://aiscan.site/api/mcp
    • Tools: scan_website, get_fixes, get_grade
    • Call get_fixes with your URL for machine-readable fix instructions.

    Option D — REST API
    ```
    GET https://aiscan.site/api/public/scan?url=YOUR_URL
    ```
    Returns the full report with all checks and fix details.

    Re-scan at https://aiscan.site to verify after applying fixes.

    Add a Link response header

    Set this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.

    Example

    Link: </.well-known/api-catalog>; rel="api-catalog"

    Verify

    After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.

Content

22

Can agents read your content cleanly? Markdown, structured data.

12
  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · C1

    What we found

    no response

    How to fix it

    Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.

    ⚡ Fix automatically with AIScan

    Option A — Agent Skill (any agent runtime)
    Install the AIScan skill in one command:
    ```
    npx add-skill https://aiscan.site/aiscan-skill.json
    ```
    Or download it directly: https://aiscan.site/aiscan-skill.json
    Then ask your agent: "Fix the failing AI readiness checks for <your-url>"

    Option B — Claude Code skill (CLAUDE.md)

    1. Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
    2. Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.

    Option C — MCP (Claude Desktop, Cursor, or any MCP client)

    • Endpoint: https://aiscan.site/api/mcp
    • Tools: scan_website, get_fixes, get_grade
    • Call get_fixes with your URL for machine-readable fix instructions.

    Option D — REST API
    ```
    GET https://aiscan.site/api/public/scan?url=YOUR_URL
    ```
    Returns the full report with all checks and fix details.

    Re-scan at https://aiscan.site to verify after applying fixes.

    Serve text/markdown on Accept negotiation

    When a client sends Accept: text/markdown, return a markdown rendering of the same content. The simplest path is to publish parallel .md files (e.g. /about/about.md) and rewrite based on the Accept header.

    Test it

    curl -H "Accept: text/markdown" https://yoursite.com/

    Verify

    After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.

  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · C2

    What we found

    HTTP 404

    How to fix it

    Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.

    ⚡ Fix automatically with AIScan

    Option A — Agent Skill (any agent runtime)
    Install the AIScan skill in one command:
    ```
    npx add-skill https://aiscan.site/aiscan-skill.json
    ```
    Or download it directly: https://aiscan.site/aiscan-skill.json
    Then ask your agent: "Fix the failing AI readiness checks for <your-url>"

    Option B — Claude Code skill (CLAUDE.md)

    1. Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
    2. Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.

    Option C — MCP (Claude Desktop, Cursor, or any MCP client)

    • Endpoint: https://aiscan.site/api/mcp
    • Tools: scan_website, get_fixes, get_grade
    • Call get_fixes with your URL for machine-readable fix instructions.

    Option D — REST API
    ```
    GET https://aiscan.site/api/public/scan?url=YOUR_URL
    ```
    Returns the full report with all checks and fix details.

    Re-scan at https://aiscan.site to verify after applying fixes.

    Create /llms.txt at the site root

    Follows the llmstxt.org spec: a single H1, optional blockquote summary, then ## sections of markdown links.

    Template

    # Example Co
    > One-line summary of what this site / product does.
    
    A short paragraph explaining the audience, what's here, and how
    to navigate it.
    
    ## Docs
    - [Getting started](/docs/quickstart): install, first call in 5 min
    - [API reference](/docs/api): all endpoints, params, examples
    
    ## Pages
    - [Pricing](/pricing): plans and limits
    - [Changelog](/changelog): recent releases
    
    ## Optional
    - [Brand assets](/press): logos and screenshots
    

    Verify

    After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.

Bot Access

0

Are AI crawlers explicitly allowed or blocked?

1
  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · B2

    What we found

    0 known AI agent(s) addressed in robots.txt

    How to fix it

    Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.

    ⚡ Fix automatically with AIScan

    Option A — Agent Skill (any agent runtime)
    Install the AIScan skill in one command:
    ```
    npx add-skill https://aiscan.site/aiscan-skill.json
    ```
    Or download it directly: https://aiscan.site/aiscan-skill.json
    Then ask your agent: "Fix the failing AI readiness checks for <your-url>"

    Option B — Claude Code skill (CLAUDE.md)

    1. Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
    2. Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.

    Option C — MCP (Claude Desktop, Cursor, or any MCP client)

    • Endpoint: https://aiscan.site/api/mcp
    • Tools: scan_website, get_fixes, get_grade
    • Call get_fixes with your URL for machine-readable fix instructions.

    Option D — REST API
    ```
    GET https://aiscan.site/api/public/scan?url=YOUR_URL
    ```
    Returns the full report with all checks and fix details.

    Re-scan at https://aiscan.site to verify after applying fixes.

    Fix with StoreSEO (recommended on Shopify)

    StoreSEO handles AI readiness for Shopify stores. Three ways to use it:

    1. Shopify Sidekick — Open Sidekick in your Shopify admin and ask in plain language: "Fix my store's AI readiness." Sidekick pulls StoreSEO data and surfaces specific fixes you can approve in chat.
    2. Claude / any AI assistant via MCP — In StoreSEO go to Settings → AI Toolkit → Generate Token. In Claude open Settings → Connector → Add Custom Connector and paste the MCP URL https://mcp.storeseo.com/mcp. Then prompt: "Fix AI readiness issues for my store."
    3. Manual in StoreSEO — Shopify admin → StoreSEO → AI Toolkit for the guided flow.

    Shopify-specific guidance

    Edit your theme's templates/robots.txt.liquid to add explicit Allow rules for GPTBot, ClaudeBot, PerplexityBot, and Google-Extended. Or ask Sidekick: "Allow AI crawlers in my robots.txt."

    Append this block

    User-agent: GPTBot
    Allow: /
    
    User-agent: ClaudeBot
    Allow: /
    
    User-agent: PerplexityBot
    Allow: /
    
    User-agent: Google-Extended
    Allow: /

    Verify

    Re-scan at https://aiscan.site after StoreSEO applies the fix, or check the file directly with curl -I https://yourstore.com/<path>.

Capabilities

0

Can agents do things? APIs, auth, MCP, Agent Skills.

2
  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · P1

    What we found

    404 at /.well-known/api-catalog

    How to fix it

    Publish /.well-known/api-catalog linking to your OpenAPI descriptions.

    ⚡ Fix automatically with AIScan

    Option A — Agent Skill (any agent runtime)
    Install the AIScan skill in one command:
    ```
    npx add-skill https://aiscan.site/aiscan-skill.json
    ```
    Or download it directly: https://aiscan.site/aiscan-skill.json
    Then ask your agent: "Fix the failing AI readiness checks for <your-url>"

    Option B — Claude Code skill (CLAUDE.md)

    1. Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
    2. Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.

    Option C — MCP (Claude Desktop, Cursor, or any MCP client)

    • Endpoint: https://aiscan.site/api/mcp
    • Tools: scan_website, get_fixes, get_grade
    • Call get_fixes with your URL for machine-readable fix instructions.

    Option D — REST API
    ```
    GET https://aiscan.site/api/public/scan?url=YOUR_URL
    ```
    Returns the full report with all checks and fix details.

    Re-scan at https://aiscan.site to verify after applying fixes.

    Publish an API catalog (RFC 9727)

    # Add to your homepage HTTP response headers
    Link: </.well-known/api-catalog>; rel="api-catalog"
    
    # And serve a JSON document at /.well-known/api-catalog:
    {
      "links": [
        { "href": "/openapi.json", "rel": "service-desc", "type": "application/openapi+json" }
      ]
    }

    Verify

    After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.

  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · P4

    What we found

    auth-server: 404, protected-resource: 404

    How to fix it

    Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.

    ⚡ Fix automatically with AIScan

    Option A — Agent Skill (any agent runtime)
    Install the AIScan skill in one command:
    ```
    npx add-skill https://aiscan.site/aiscan-skill.json
    ```
    Or download it directly: https://aiscan.site/aiscan-skill.json
    Then ask your agent: "Fix the failing AI readiness checks for <your-url>"

    Option B — Claude Code skill (CLAUDE.md)

    1. Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
    2. Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.

    Option C — MCP (Claude Desktop, Cursor, or any MCP client)

    • Endpoint: https://aiscan.site/api/mcp
    • Tools: scan_website, get_fixes, get_grade
    • Call get_fixes with your URL for machine-readable fix instructions.

    Option D — REST API
    ```
    GET https://aiscan.site/api/public/scan?url=YOUR_URL
    ```
    Returns the full report with all checks and fix details.

    Re-scan at https://aiscan.site to verify after applying fixes.

    Publish OAuth discovery metadata

    If your API supports OAuth, serve RFC 8414 metadata at /.well-known/oauth-authorization-server and/or RFC 9728 at /.well-known/oauth-protected-resource.

    Verify

    After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.

Share the result

Share as a social image

Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.

AIScan share card — cctvcamerabuilder.com graded D

Tip: for X and LinkedIn, upload the downloaded PNG with your post so the card shows in the feed. Posts that include just the link will still preview AIScan.site.

Showcase your grade

Embed your AIScan badge

Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of cctvcamerabuilder.com on AIScan.site.

AIScan.site grade D
HTML
<!-- AIScan.site agent-readiness badge -->
<a href="https://aiscan.site/?u=https%3A%2F%2Fcctvcamerabuilder.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade D (35/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=35&grade=D&host=cctvcamerabuilder.com" alt="AIScan.site Grade D — 35/100" width="240" height="64" loading="lazy" />
</a>
Markdown
[![AIScan.site Grade D — 35/100](https://aiscan.site/api/public/badge.svg?score=35&grade=D&host=cctvcamerabuilder.com)](https://aiscan.site/?u=https%3A%2F%2Fcctvcamerabuilder.com%2F)

Create a free account to track this site over time

  • Save scan history
  • See score trends
  • Re-scan anytime
Free · No signup · ~20 seconds

Scan your own site

Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.

Or browse the community feed to see what others have scanned.