AI Readiness Report

Field	Value
Page title	Travelgram — The Gamified AI Travel Planner
Meta description	Travelgram turns trip planning into a quest. Earn XP, unlock destinations, and let our AI build itineraries you'll actually want to live.

Field

Value

Page title

Travelgram — The Gamified AI Travel Planner

Meta description

Travelgram turns trip planning into a quest. Earn XP, unlock destinations, and let our AI build itineraries you'll actually want to live.

Dimension	Score	Weight
AI Crawlability	16/20	20%
AI Understanding	0/25	25%
AI Content Readiness	1/20	20%
AI Citation Potential	3/20	20%
Agent & Protocol Readiness	2/25	25%
Trust & Security	4/5	5%
Total	26/100	Grade: Poor

Dimension

Score

Weight

AI Crawlability

16/20

20%

AI Understanding

0/25

25%

AI Content Readiness

1/20

20%

AI Citation Potential

3/20

20%

Agent & Protocol Readiness

2/25

25%

Trust & Security

4/5

Total

26/100

Grade: Poor

Detailed Findings 38

AI Crawlability 16/20

robots.txt reachable.

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

No sitemap declared.

No sitemap.xml was declared. AI crawlers cannot systematically discover all of your pages, so deeper content may remain unindexed.

Generate a sitemap.xml and place it in the website root.
Add the reference in robots.txt: Sitemap: https://travelgram.io/sitemap.xml.
Submit the sitemap to major search engine webmaster tools.

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.

AI Understanding 0/25

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.

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

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Travelgram — The Gamified AI Travel Planner",
  "url": "https://travelgram.io",
  "logo": "https://travelgram.io/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.

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

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Travelgram — The Gamified AI Travel Planner Product Name",
  "image": ["https://travelgram.io/logo.png"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "Travelgram — The Gamified AI Travel Planner" },
  "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.

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

html

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

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

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article title",
  "author": { "@type": "Person", "name": "Author name" },
  "publisher": { "@type": "Organization", "name": "Travelgram — The Gamified AI Travel Planner" },
  "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.

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

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [{
    "@type": "ListItem", "position": 1,
    "name": "Home", "item": "https://travelgram.io/"
  },{
    "@type": "ListItem", "position": 2,
    "name": "Products", "item": "https://travelgram.io/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.

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

Content Quality 1/20

Homepage content depth: 1/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.

AI Citation 3/20

Thin content; little to cite.

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.

No authoritative external references.

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

Agent & Protocol Readiness 2/25

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.

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

json

{
  "openapi": "3.0.3",
  "info": {
    "title": "Travelgram — The Gamified AI Travel Planner API",
    "version": "1.0.0",
    "description": "Machine-readable API for Travelgram — The Gamified AI Travel Planner"
  },
  "servers": [{ "url": "https://travelgram.io/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.

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

json

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "Travelgram — The Gamified AI Travel Planner", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://travelgram.io/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.

No RFC 8288 Link response header detected.

No RFC 8288 Link response header was found. Agents cannot discover your API, docs or AI feed from response headers.

Add a Link header on your homepage pointing to key machine-readable resources.
Example: Link: <https://travelgram.io/openapi.json>; rel="service-desc", <https://travelgram.io/llms.txt>; rel="describedby"

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.

Publish SVCB or HTTPS DNS records that point to your AI/agent service.
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.

When the request Accept header is text/markdown, return a clean Markdown version of the page.
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.

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.

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

json

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "Travelgram — The Gamified AI Travel Planner", "version": "1.0.0" },
  "capabilities": { "tools": {}, "resources": {} },
  "endpoints": { "base": "https://travelgram.io/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.

Create .well-known/agent-skills/ with an index.json listing your skills.
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.

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.

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

Trust & Safety 4/5

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.

Actionable Recommendations 20

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.

Dimension: AI Understanding

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

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Travelgram — The Gamified AI Travel Planner",
  "url": "https://travelgram.io",
  "logo": "https://travelgram.io/logo.png"
}
</script>

The page relies heavily on client-side rendering. With JavaScript disabled, only 7 words of visible text remain, so AI crawlers and LLM agents that do not execute JavaScript may index an empty page.

Dimension: AI Crawlability

Enable server-side rendering (SSR) or static site generation (SSG) for public pages.
Alternatively add pre-rendering for crawler user-agents (GPTBot, ClaudeBot, etc.).
Verify the no-JS HTML contains the same primary content as the rendered page.

text

# robots.txt — let AI crawlers see the pre-rendered version
User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: *
Allow: /

No llms.txt was found at the site root. LLMs and AI agents lack a machine-readable site guide to quickly discover key sections and entry points.

Dimension: AI Crawlability

Create a file named llms.txt in the website root.
Paste the template below and replace the links and sections with your real paths.
Optionally provide llms-full.txt with full page content for deeper indexing.

markdown

# Travelgram — The Gamified AI Travel Planner

> Travelgram — The Gamified AI Travel Planner — AI-readable overview for LLMs and agents.

## Home
- [Home](https://travelgram.io/): Main landing page for Travelgram — The Gamified AI Travel Planner.

## Documentation
- [About](https://travelgram.io/about): Company background and mission.
- [Products](https://travelgram.io/products): Product and service overview.
- [Blog](https://travelgram.io/blog): Insights, guides and case studies.

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

Dimension: Agent

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

json

{
  "openapi": "3.0.3",
  "info": {
    "title": "Travelgram — The Gamified AI Travel Planner API",
    "version": "1.0.0",
    "description": "Machine-readable API for Travelgram — The Gamified AI Travel Planner"
  },
  "servers": [{ "url": "https://travelgram.io/api" }],
  "paths": {
    "/health": {
      "get": {
        "summary": "Service health",
        "responses": { "200": { "description": "OK" } }
      }
    }
  }
}

The homepage lacks semantic structure (header / main / article tags or a clear H1-H3 hierarchy), making it harder for AI to distinguish content, navigation and decorative elements.

Dimension: AI Understanding

Wrap the page skeleton with <header>, <main>, <article> and <footer>.
Use exactly one <h1> per page and build a clear hierarchy with <h2> and <h3>.
Avoid stacking content with generic <div> elements alone.

html

<body>
  <header>
    <nav><!-- Site navigation --></nav>
  </header>
  <main>
    <article>
      <h1>Primary page title</h1>
      <h2>Section heading</h2>
      <p>Body content...</p>
    </article>
  </main>
  <footer><!-- Footer --></footer>
</body>

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.

Dimension: AI Understanding

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

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.

Dimension: AI Understanding

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

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Travelgram — The Gamified AI Travel Planner Product Name",
  "image": ["https://travelgram.io/logo.png"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "Travelgram — The Gamified AI Travel Planner" },
  "offers": { "@type": "Offer", "priceCurrency": "USD", "price": "0" }
}
</script>

No sitemap.xml was declared. AI crawlers cannot systematically discover all of your pages, so deeper content may remain unindexed.

Dimension: AI Crawlability

Generate a sitemap.xml and place it in the website root.
Add the reference in robots.txt: Sitemap: https://travelgram.io/sitemap.xml.
Submit the sitemap to major search engine webmaster tools.

No RFC 8288 Link response header was found. Agents cannot discover your API, docs or AI feed from response headers.

Dimension: Agent

Add a Link header on your homepage pointing to key machine-readable resources.
Example: Link: <https://travelgram.io/openapi.json>; rel="service-desc", <https://travelgram.io/llms.txt>; rel="describedby"

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

Dimension: Agent

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

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

Dimension: Agent

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

json

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "Travelgram — The Gamified AI Travel Planner", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://travelgram.io/mcp" }
}

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

Dimension: Agent

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

json

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "Travelgram — The Gamified AI Travel Planner", "version": "1.0.0" },
  "capabilities": { "tools": {}, "resources": {} },
  "endpoints": { "base": "https://travelgram.io/mcp" }
}

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

Dimension: AI Understanding

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

html

<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 was detected. Editorial content is less likely to be treated as an authoritative source by AI, and you miss rich-result placement.

Dimension: AI Understanding

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

html

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

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

Dimension: Agent

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

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

Dimension: Agent

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

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

Dimension: AI Understanding

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

html

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

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

Dimension: Agent

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

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

Dimension: Agent

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

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

Dimension: Agent

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

Site Meta Snapshot

Score Overview

Detailed Findings 38

AI Crawlability 16/20

AI Understanding 0/25

Content Quality 1/20

AI Citation 3/20

Agent & Protocol Readiness 2/25

Trust & Safety 4/5

Actionable Recommendations 20

Websites we've checked

AI Readiness Report

Site Meta Snapshot

Score Overview

Detailed Findings 38

AI Crawlability 16/20

AI Understanding 0/25

Content Quality 1/20

AI Citation 3/20

Agent & Protocol Readiness 2/25

Trust & Safety 4/5

Actionable Recommendations 20

Websites we've checked

Share SVG Badge