gitgit.me

Can AI crawlers find your content and understand your policies?

• ✓
  robots.txt present

  HTTP 200
• ✓
  sitemap.xml present

  HTTP 200
• ✓
  Sitemap declared in robots.txt
• ✓
  AI bot rules in robots.txt

  Mentions GPTBot, ClaudeBot, Google-Extended, CCBot
• ✓
  Content Signals declared

  Cloudflare Content Signals present

Standard well-known endpoints agents probe to interact with your site.

• ✓
  MCP server card (/.well-known/mcp/server-card.json)

  HTTP 200
• ✓
  API catalog (/.well-known/api-catalog)

  HTTP 200
• ✓
  OAuth protected resource (/.well-known/oauth-protected-resource)

  HTTP 200
• ✓
  OpenID configuration (/.well-known/openid-configuration)

  HTTP 200

How well your site speaks formats AI agents prefer.

• ✓
  llms.txt present

  HTTP 200
• !
  Markdown content negotiation

  Returned text/html despite Accept: text/markdown

  How to fix

  When `Accept: text/markdown` is sent, return the same content as Markdown (Content-Type: text/markdown). Agents prefer it because it's cheaper to parse than HTML.

• !
  Link header on /

  No Link header — agents can't follow alt-format relations

  How to fix

  Add an HTTP `Link:` header pointing agents at alternate representations, e.g. `Link: </openapi.json>; rel="service-desc"; type="application/openapi+json"`.

HTML signals that Google AI Search + LLM crawlers use to rank you.

• ✓
  Homepage reachable

  HTTP 200
• ✓
  HTTPS
• ✓
  Title tag

  Link in Bio: All Your Links in One Place | gitgit.me
• ✓
  Meta description

  All your links in one place. Create a professional bio link for free and connect your audi…
• ✓
  Canonical URL
• ✓
  Open Graph tags

  title, description, image
• ✓
  Schema.org structured data

  Organization, WebSite, WebPage
• ✓
  Mobile viewport
• ✓
  html lang attribute
• –
  Image alt text

  No <img> tags on homepage

Optional: cryptographic verification for trusted bots.

• ✓
  Web Bot Auth directory

  HTTP 200