AI Readiness Report

robots.txt reachable.

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

sitemap.xml declared.

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

GPTBot allowed in robots.txt.

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

ClaudeBot allowed in robots.txt.

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

Google-Extended allowed in robots.txt.

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

Bytespider allowed in robots.txt.

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

KimiBot allowed in robots.txt.

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

Organization schema with name + url.

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

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": "Ghost Roots Hair Inspiration: Color and Placement Ideas Product Name",
  "image": ["https://ghostroots.hair/brand/ghost-roots-hair-logo-transparent.webp"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "Ghost Roots Hair Inspiration: Color and Placement Ideas" },
  "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": "Ghost Roots Hair Inspiration: Color and Placement Ideas" },
  "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://ghostroots.hair/"
  },{
    "@type": "ListItem", "position": 2,
    "name": "Products", "item": "https://ghostroots.hair/products"
  }]
}
</script>

Entity fields covered: 6/11.

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

Homepage content depth: 5/5.

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

About page reachable.

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.

Blog / Case page reachable.

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

Rich topical content detected.

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

Blog / case / news section reachable.

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

Author / byline information present.

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

Brand entity consistent across pages.

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

No authoritative external references.

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": "Ghost Roots Hair Inspiration: Color and Placement Ideas API",
    "version": "1.0.0",
    "description": "Machine-readable API for Ghost Roots Hair Inspiration: Color and Placement Ideas"
  },
  "servers": [{ "url": "https://ghostroots.hair/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": "Ghost Roots Hair Inspiration: Color and Placement Ideas", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://ghostroots.hair/mcp" }
}

No AI Actions manifest detected.

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

No API documentation link found.

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

RFC 8288 Link header present on homepage.

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

No DNS-AID (SVCB/HTTPS) records detected.

No DNS-AID (SVCB/HTTPS) records were detected. Agents cannot discover your AI service endpoint directly from DNS.

1. Publish SVCB or HTTPS DNS records that point to your AI/agent service.
2. These let agents resolve your MCP or API endpoint without crawling HTML.

No Markdown content negotiation (Accept: text/markdown) detected.

No Markdown content negotiation (Accept: text/markdown) was detected. Agents must parse HTML instead of clean Markdown.

1. When the request Accept header is text/markdown, return a clean Markdown version of the page.
2. Point agents to /llms.txt as a fallback machine-readable overview.

No Content Signals directive (ai-train/search/ai-input) detected.

No Content Signals directive (ai-train / search / ai-input) was detected. You are not explicitly telling AI bots how they may use your content.

1. Add a Content-Signals response header or <meta name="content-signals" content="ai-train=yes; search=yes; ai-input=yes">.

No MCP Server Card (.well-known/mcp/server-card.json) found.

No MCP Server Card was found at .well-known/mcp/server-card.json. Agents cannot discover your MCP tools and resources.

1. Serve the Server Card below at /.well-known/mcp/server-card.json.
2. Implement the corresponding MCP server (tools and resources).

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "Ghost Roots Hair Inspiration: Color and Placement Ideas", "version": "1.0.0" },
  "capabilities": { "tools": {}, "resources": {} },
  "endpoints": { "base": "https://ghostroots.hair/mcp" }
}

No Agent Skills catalog (.well-known/agent-skills) found.

No Agent Skills catalog was found at .well-known/agent-skills. Agents cannot discover the skills your site offers.

1. Create .well-known/agent-skills/ with an index.json listing your skills.
2. Each skill should have a SKILL.md describing when and how to use it.

No OAuth discovery (.well-known/oauth-authorization-server) found.

No OAuth discovery endpoint (.well-known/oauth-authorization-server) was detected. Agents cannot securely authenticate to your API.

1. Publish an OAuth 2.0 authorization server metadata document at /.well-known/oauth-authorization-server.

No Auth.md found.

No Auth.md was found. Agents lack guidance on how to authenticate against your services.

1. Add an Auth.md at your site root or .well-known/ describing authentication flows for agents.

Served over HTTPS.

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

Business contact 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.