AI Readiness Report

No robots.txt found.

No robots.txt was detected. Access rules for major AI crawlers are not declared explicitly, so they may be overlooked or left to default behavior.

1. Edit the root robots.txt file and add Allow rules for the AI crawlers below.
2. If you need to protect specific paths (e.g. admin panels), use precise Disallow rules inside the wildcard group.
3. Add a Sitemap reference: Sitemap: https://select2.org/sitemap.xml.
4. Re-run the analysis after deployment to confirm the status changes to Allowed.

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Bytespider
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: KimiBot
Allow: /

User-agent: *
Allow: /

sitemap.xml declared.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

GPTBot allowed in robots.txt.

No robots.txt was detected. Access rules for major AI crawlers are not declared explicitly, so they may be overlooked or left to default behavior.

1. Edit the root robots.txt file and add Allow rules for the AI crawlers below.
2. If you need to protect specific paths (e.g. admin panels), use precise Disallow rules inside the wildcard group.
3. Add a Sitemap reference: Sitemap: https://select2.org/sitemap.xml.
4. Re-run the analysis after deployment to confirm the status changes to Allowed.

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Bytespider
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: KimiBot
Allow: /

User-agent: *
Allow: /

ClaudeBot allowed in robots.txt.

No robots.txt was detected. Access rules for major AI crawlers are not declared explicitly, so they may be overlooked or left to default behavior.

1. Edit the root robots.txt file and add Allow rules for the AI crawlers below.
2. If you need to protect specific paths (e.g. admin panels), use precise Disallow rules inside the wildcard group.
3. Add a Sitemap reference: Sitemap: https://select2.org/sitemap.xml.
4. Re-run the analysis after deployment to confirm the status changes to Allowed.

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Bytespider
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: KimiBot
Allow: /

User-agent: *
Allow: /

Google-Extended allowed in robots.txt.

No robots.txt was detected. Access rules for major AI crawlers are not declared explicitly, so they may be overlooked or left to default behavior.

1. Edit the root robots.txt file and add Allow rules for the AI crawlers below.
2. If you need to protect specific paths (e.g. admin panels), use precise Disallow rules inside the wildcard group.
3. Add a Sitemap reference: Sitemap: https://select2.org/sitemap.xml.
4. Re-run the analysis after deployment to confirm the status changes to Allowed.

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Bytespider
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: KimiBot
Allow: /

User-agent: *
Allow: /

Bytespider allowed in robots.txt.

No robots.txt was detected. Access rules for major AI crawlers are not declared explicitly, so they may be overlooked or left to default behavior.

1. Edit the root robots.txt file and add Allow rules for the AI crawlers below.
2. If you need to protect specific paths (e.g. admin panels), use precise Disallow rules inside the wildcard group.
3. Add a Sitemap reference: Sitemap: https://select2.org/sitemap.xml.
4. Re-run the analysis after deployment to confirm the status changes to Allowed.

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Bytespider
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: KimiBot
Allow: /

User-agent: *
Allow: /

KimiBot allowed in robots.txt.

No robots.txt was detected. Access rules for major AI crawlers are not declared explicitly, so they may be overlooked or left to default behavior.

1. Edit the root robots.txt file and add Allow rules for the AI crawlers below.
2. If you need to protect specific paths (e.g. admin panels), use precise Disallow rules inside the wildcard group.
3. Add a Sitemap reference: Sitemap: https://select2.org/sitemap.xml.
4. Re-run the analysis after deployment to confirm the status changes to Allowed.

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Bytespider
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: KimiBot
Allow: /

User-agent: *
Allow: /

No Organization/LocalBusiness schema.

No Organization / LocalBusiness schema was detected. AI engines rely on this markup to build accurate entity relationships and brand understanding, which directly affects citation quality.

1. Copy the JSON-LD snippet below into the <head> section of your homepage.
2. Replace name, url and logo with your actual brand details (use an absolute URL for the logo).
3. Re-run the analysis after deploying the change.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Select2",
  "url": "https://select2.org",
  "logo": "https://select2.org/images/logo.png"
}
</script>

No Product schema.

No Product schema was detected. E-commerce or product content cannot be recognised and cited by AI as a structured entity, which costs you rich-result placement.

1. Add the Product JSON-LD below to each product detail page.
2. Replace name, image, price and brand with real values (price must be a numeric string).
3. Use ItemList to aggregate multiple products on listing pages.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Select2 Product Name",
  "image": ["https://select2.org/images/logo.png"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "Select2" },
  "offers": { "@type": "Offer", "priceCurrency": "USD", "price": "0" }
}
</script>

No FAQPage schema.

No FAQPage schema was detected. Common questions and answers cannot be cited directly by AI as authoritative answers, and you miss rich-result opportunities.

1. Add the FAQPage JSON-LD below to your FAQ page.
2. Make sure the question/answer text matches the visible page content exactly.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Your first question?",
    "acceptedAnswer": { "@type": "Answer", "text": "The authoritative answer." }
  }]
}
</script>

No Article schema.

No Article schema was detected. Editorial content is less likely to be treated as an authoritative source by AI, and you miss rich-result placement.

1. Add the Article JSON-LD below to each article page.
2. Ensure author, publisher and datePublished match the visible content.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article title",
  "author": { "@type": "Person", "name": "Author name" },
  "publisher": { "@type": "Organization", "name": "Select2" },
  "datePublished": "2026-01-01",
  "dateModified": "2026-01-01"
}
</script>

No Breadcrumb schema.

No Breadcrumb schema was detected. AI cannot infer the site hierarchy and breadcrumb relationships as easily, which affects internal-link context.

1. Add the BreadcrumbList JSON-LD below to relevant pages.
2. Increment position from 1 and use real, accessible URLs for each item.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [{
    "@type": "ListItem", "position": 1,
    "name": "Home", "item": "https://select2.org/"
  },{
    "@type": "ListItem", "position": 2,
    "name": "Products", "item": "https://select2.org/products"
  }]
}
</script>

Entity fields covered: 0/11.

Brand entity coverage is insufficient. AI cannot build a complete entity profile (description, contact details, industry, sameAs social links, etc.), lowering the chance of accurate citations.

1. Extend your Organization / WebSite schema with description, telephone, email, address, industry, founder and foundingDate.
2. Link official social profiles, Wikipedia or other authoritative pages via sameAs.
3. Keep the brand name and logo consistent across all pages.

Homepage content depth: 3/5.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No About page found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No Product page found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No FAQ page found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No Blog / Case page found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Moderate content depth.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No blog or case section found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No author attribution detected.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Brand entity present but not consistently surfaced.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Few external trust signals.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No OpenAPI descriptor detected.

No OpenAPI / Swagger descriptor was detected. AI agents cannot auto-discover or invoke your API, which means you miss tool-integration opportunities.

1. Serve the OpenAPI 3.0 manifest below at /openapi.json.
2. Fill in your real paths, component schemas and authentication method.
3. Link to the descriptor from your homepage or developer docs.

{
  "openapi": "3.0.3",
  "info": {
    "title": "Select2 API",
    "version": "1.0.0",
    "description": "Machine-readable API for Select2"
  },
  "servers": [{ "url": "https://select2.org/api" }],
  "paths": {
    "/health": {
      "get": {
        "summary": "Service health",
        "responses": { "200": { "description": "OK" } }
      }
    }
  }
}

No Model Context Protocol endpoint found.

No Model Context Protocol (MCP) endpoint was detected. AI agents cannot tool-enable your service through tools or resources without it.

1. Serve the manifest below at /.well-known/mcp.json.
2. Implement the corresponding MCP server (tools and resources).
3. Document the integration path in your developer docs.

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "Select2", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://select2.org/mcp" }
}

No AI Actions manifest detected.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

API / developer documentation linked.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Served over HTTPS.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No contact info visible.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

HTTP status 200.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.