louderagency.com

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

  Add a `Sitemap:` line to robots.txt

  How to fix

  Append a line like `Sitemap: https://yoursite.com/sitemap.xml` to robots.txt so crawlers find the sitemap immediately.

• !
  AI bot rules in robots.txt

  No explicit rules for GPTBot / ClaudeBot / Google-Extended

  How to fix

  Add `User-agent: GPTBot`, `User-agent: ClaudeBot`, `User-agent: Google-Extended` blocks with explicit Allow/Disallow so AI crawlers know your stance.

• !
  Content Signals declared

  No Cloudflare Content-Signal directive

  How to fix

  Add `Content-Signal: search=yes, ai-train=no, ai-input=yes` (tune the values to your policy) inside a User-agent group in robots.txt.

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

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

  Publish an MCP server card to expose agent tools

  How to fix

  Publish an MCP server-card JSON at /.well-known/mcp/server-card.json describing your tools, transport, and capabilities. Spec: SEP-1649/SEP-2127.

• ✗
  API catalog (/.well-known/api-catalog)

  RFC 9727 API catalog helps agents discover your APIs

  How to fix

  Serve a `application/linkset+json` document at /.well-known/api-catalog listing your OpenAPI / service descriptions. RFC 9727.

• ✗
  OAuth protected resource (/.well-known/oauth-protected-resource)

  RFC 9728 lets agents discover auth requirements

  How to fix

  Publish a JSON document at /.well-known/oauth-protected-resource with `resource` and `authorization_servers` fields. RFC 9728.

• ✗
  OpenID configuration (/.well-known/openid-configuration)

  Helpful if your site offers identity / sign-in for agents

  How to fix

  If your product supports sign-in, expose OpenID Connect discovery at /.well-known/openid-configuration so agents can authenticate users on their behalf.

How well your site speaks formats AI agents prefer.

• ✓
  llms.txt present

  HTTP 200
• !
  Markdown content negotiation

  Returned text/html; charset=utf-8 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

  Louder Agency | A Mission-Driven Web and Marketing Agency
• ✓
  Meta description

  We help purposeful brands, nonprofits and mission-minded entrepreneurs positively impact t…
• ✓
  Canonical URL
• ✓
  Open Graph tags

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

  Add JSON-LD (Organization, Product, FAQPage…)

  How to fix

  Embed a `<script type="application/ld+json">` block with an Organization, Product, FAQPage, or HowTo schema. Validate with schema.org/validator.

• ✓
  Mobile viewport
• ✓
  html lang attribute
• ✗
  Image alt text

  26/71 images have alt

  How to fix

  Add descriptive `alt` text to every `<img>` (use `alt=""` for purely decorative images). Improves accessibility AND AI/SEO ranking.

Optional: cryptographic verification for trusted bots.

• ✗
  Web Bot Auth directory

  Publish /.well-known/http-message-signatures-directory to verify trusted bots

  How to fix

  If you operate a bot, publish your signing keys at /.well-known/http-message-signatures-directory per draft-meunier-web-bot-auth-architecture. Most non-bot sites can leave this missing.