# Preparación para AI de beardbrand.com

> Medido en la página de inicio. Calificación general: Aceptable.

Puntuación 58/100, nota Aceptable. Medido 2026-09-10T19:01:53.414+00:00, motor axrush-engine@6.0.0.

## Comprobaciones

### Contenido — 49/100

#### Content Negotiation — 0/100

- **FAIL** Homepage does not serve Markdown via content negotiation
  Got text/html (HTTP 200) for "Accept: text/markdown"
  Serve a Markdown representation of your pages when agents request "Accept: text/markdown". Agents like Claude Code and Cursor ask for it, and Markdown cuts token usage by roughly 80% against HTML. Cloudflare ("Markdown for Agents") and Vercel can enable this without code changes.
  https://axrush.com/guides/content-negotiation#not-supported
- **WARN** No <link rel="alternate" type="text/markdown"> fallback found on the homepage
  If you cannot enable content negotiation, advertise a Markdown version with <link rel="alternate" type="text/markdown" href="/index.md"> so agents can discover it.
  https://axrush.com/guides/content-negotiation#no-alternate

#### Structured Data — 0/100

- **FAIL** No JSON-LD structured data found
  Add a <script type="application/ld+json"> block in your HTML <head> with schema.org structured data describing your site, organization, or person.
  https://axrush.com/guides/structured-data#not-found

#### HTML Rendering — 60/100

- **WARN** Sparse server-rendered content (13 words, 88 chars)
  Below thresholds: 80 words, 500 chars
  Render at least the main page content server-side. Many AI crawlers (GPTBot, ClaudeBot, CCBot) do not execute JavaScript and will see only the static HTML.
  https://axrush.com/guides/html-rendering#sparse-content
- **PASS** Text-to-markup ratio is healthy (17.0% of structural markup)
- **WARN** No semantic HTML landmarks found
  Replace generic <div> structures with semantic tags: <main>, <article>, <header>, <nav>, <footer>. Agents use these to identify the primary content region.
  https://axrush.com/guides/html-rendering#no-landmarks
- **PASS** Single <h1> heading: "Your connection needs to be verified before you can proceed"

#### SEO Basics — 70/100

- **PASS** <title> length 28 chars: "Verifying your connection..."
- **FAIL** <meta name="description"> is missing
  Add <meta name="description" content="..."> in <head> with a 70-160 character summary. Agents use this as the canonical short description.
  https://axrush.com/guides/seo-basics#no-description
- **WARN** No <link rel="canonical"> found
  Add <link rel="canonical" href="https://your-site.com/page"> so agents have an unambiguous URL to cite even when crawled via a redirect or query-string variant.
  https://axrush.com/guides/seo-basics#no-canonical
- **PASS** <html lang="en">
- **PASS** UTF-8 charset declared
- **PASS** Viewport meta present: "width=device-width, initial-scale=1.0"

#### Operabilidad para agentes — 85/100

- **WARN** 1 obstacle(s) on the entry page
  <meta http-equiv="refresh"> on the page
  A CAPTCHA or a meta refresh on the landing page stops an agent before it reaches any content. If bot protection is needed, apply it to the actions that need it, not to reading a page.
  https://axrush.com/guides/agent-operability#entry-blockers
- **PASS** Method note: this reads markup, not a rendered accessibility tree
  Labels attached by script and roles computed at runtime are invisible here, so treat low proportions as a prompt to check the real tree rather than as a count. Every finding is also a plain accessibility defect.

### Acceso — 86/100

#### TLS / HTTPS — 87/100

- **PASS** Site is served over HTTPS
- **PASS** HTTP requests redirect to HTTPS
- **WARN** HSTS max-age is short (7889238s = ~91 days)
  Use at least max-age=15768000 (~6 months); preload list submission requires max-age=31536000 (1 year).
  https://axrush.com/guides/tls-https#hsts-short
- **WARN** HSTS does not include subdomains
  Add includeSubDomains to apply HSTS across api., docs., etc. Required for preload list submission.
  https://axrush.com/guides/tls-https#hsts-no-subdomains
- **WARN** HSTS lacks the preload directive
  Add preload (and ensure max-age >= 31536000 + includeSubDomains) and submit the domain at https://hstspreload.org for browser-built-in HTTPS enforcement.
  https://axrush.com/guides/tls-https#hsts-no-preload

#### Agent Access — 98/100

- **WARN** ChatGPT-User receives a Cloudflare challenge instead of the page
  cf-mitigated: challenge
  Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#challenge-page
- **WARN** 1 crawler probe(s) could not be settled from outside
  ChatGPT-User
  ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#inconclusive-probe

#### Higiene HTTP — 80/100

- **WARN** A missing page redirects (301) instead of returning 404
  Location: https://www.beardbrand.com/ax-audit-probe-3vbe77ek
  A redirect on a nonexistent path hides the error. Return 404 or 410 so a client can tell the difference.
  https://axrush.com/guides/http-hygiene#soft-404-redirect
- **PASS** Homepage answers after 1 redirect
  301 → https://www.beardbrand.com/
- **PASS** HEAD requests are supported
- **PASS** Content-Type: text/html with charset

#### Crawl Efficiency — 0/100

- **FAIL** Homepage request failed — cannot assess crawl efficiency
  HTTP 429
  https://axrush.com/guides/crawl-efficiency#fetch-failed

#### Directivas de IA — 100/100

- **PASS** Homepage is indexable
- **PASS** No directive restricts how AI assistants may use this page

### Descubrimiento — 79/100

#### LLMs.txt — 100/100

- **PASS** /llms.txt exists
- **PASS** /llms.txt Content-Type OK (text/markdown)
- **PASS** H1 heading: "Agent Instructions — Beardbrand"
- **WARN** No blockquote description found ("> ...")
  Add a blockquote description after the H1 heading, e.g.: > A brief summary of your site for AI agents.
  https://axrush.com/guides/llms-txt#missing-blockquote
- **PASS** 5 section heading(s) found
- **PASS** 5 link(s) found
- **PASS** /llms-full.txt also available (bonus)
- **WARN** No rel="describedby" link to llms.txt
  llms.txt v2 uses this relation so a page can name the file that covers it. Add <link rel="describedby" href="/llms.txt"> or the equivalent Link header, so an agent that landed on a deep page does not have to guess that an index exists.
  https://axrush.com/guides/llms-txt#no-describedby
- **WARN** 2 duplicate link(s) in llms.txt
  Each URL should appear once. Duplicates spend an agent’s budget re-reading what it already has.
  https://axrush.com/guides/llms-txt#duplicate-links
- **PASS** 3 sampled link(s) resolve
- **WARN** 1 sampled link(s) redirect
  https://www.shopify.com → https://www.shopify.com/es-es
  Point llms.txt at the final URL. Each redirect is a round trip the agent pays for on every visit.
  https://axrush.com/guides/llms-txt#redirecting-links
- **WARN** No per-page Markdown mirror found
  Tried /index.md and /index.html.md.
  llms.txt v2 documents appending .md to a URL for its Markdown version. The index tells an agent which pages exist; the mirrors are what make reading them cheap.
  https://axrush.com/guides/llms-txt#no-markdown-mirror
- **PASS** Consumer note: llms.txt is read by coding agents, not by search
  Google has stated that Search ignores llms.txt, and adoption studies find most published files are never fetched by an AI search crawler. Claude Code, Cursor and OpenCode do fetch it. Treat it as developer tooling, not as a search-visibility signal.

#### Robots.txt — 70/100

- **PASS** /robots.txt exists
- **WARN** 1/12 core AI crawlers configured
  GPTBot — Blocking it keeps your content out of OpenAI model training. It does not affect ChatGPT search citations.
ClaudeBot — Blocking it keeps your content out of Claude model training.
Meta-ExternalAgent — Blocking it keeps your content out of Meta AI training and indexing.
Google-Extended — Controls Gemini training and grounding in Gemini Apps and Vertex AI. It does NOT remove your site from AI Overviews or AI Mode, which follow Googlebot and the snippet directives.
Applebot-Extended — Opts your content out of Apple foundation-model training without affecting Siri or Spotlight.
Bytespider — Collects training data for ByteDance models. Compliance with robots.txt is disputed.
CCBot — Builds the open Common Crawl corpus that many models train on. Blocking it is the single broadest training opt-out.
OAI-SearchBot — Blocking it removes your site from ChatGPT search answers and citations.
Claude-SearchBot — Blocking it removes your site from the index Claude cites when it searches the web.
PerplexityBot — Blocking it removes your site from Perplexity answers and citations. Not used for model training.
ChatGPT-User — Fetches a page because a ChatGPT user asked for that URL. Blocking it breaks link-following in conversations.
  Add explicit User-agent entries for the missing crawlers with Allow: / for each one.
  https://axrush.com/guides/robots-txt#missing-crawlers
- **WARN** 1 AI crawler(s) explicitly blocked
  Amazonbot
  These crawlers have "Disallow: /" rules. If you want AI agents to access your site, change to "Allow: /" for each blocked crawler.
  https://axrush.com/guides/robots-txt#explicitly-blocked
- **PASS** 1 training crawler(s) blocked — recorded as a deliberate policy choice
  Amazonbot
- **PASS** Sitemap directive present
- **WARN** No Content-Signal directive found (optional)
  Declare how crawlers may use your content after access with the Content Signals Policy, e.g.: Content-Signal: search=yes, ai-train=no. Known signals: search, ai-input, ai-train, plus the optional use=immediate|reference|full. Generate yours at contentsignals.org.
  https://axrush.com/guides/robots-txt#missing-content-signals
- **WARN** 1/57 known AI crawlers have explicit rules
  Add explicit User-agent entries for more AI crawlers to maximize discoverability.
  https://axrush.com/guides/robots-txt#low-coverage

#### Sitemap — 100/100

- **PASS** Sitemap located: https://www.beardbrand.com/sitemap.xml
- **PASS** Content-Type is XML (application/xml)
- **PASS** Sitemap-index references 5 child sitemap(s)
- **PASS** 3/3 sample child sitemap(s) reachable
- **PASS** Sample yielded 111 URL(s) across 3 child(ren)
- **PASS** Newest <lastmod> is recent (0 day(s) ago)

#### Meta Tags — 36/100

- **WARN** No AI meta tags (ai:*) found
  Add AI meta tags to your HTML <head>: <meta name="ai:summary" content="Brief description">, <meta name="ai:content_type" content="website">, <meta name="ai:author" content="Your Name">.
  https://axrush.com/guides/meta-tags#no-ai-meta
- **WARN** No rel="alternate" link to llms.txt in HTML
  Add to your <head>: <link rel="alternate" type="text/plain" href="/llms.txt" title="LLM-optimized content">
  https://axrush.com/guides/meta-tags#no-llms-alternate
- **WARN** No rel="alternate" link to the Agent Card in HTML
  Add to your <head>: <link rel="alternate" type="application/json" href="/.well-known/agent-card.json" title="Agent Card">
  https://axrush.com/guides/meta-tags#no-agent-alternate
- **WARN** No rel="me" identity links found
  Add rel="me" links to verify your identity across platforms: <link rel="me" href="https://github.com/yourname">, <link rel="me" href="https://twitter.com/yourname">.
  https://axrush.com/guides/meta-tags#no-rel-me
- **WARN** No OpenGraph meta tags found
  Add at minimum og:title, og:description, og:url, og:type, and og:image. Agents and link previews depend on these.
  https://axrush.com/guides/meta-tags#no-opengraph
- **WARN** No Twitter Card meta tags found
  Add twitter:card, twitter:title, twitter:description, and twitter:image so X / Threads / Bluesky / Discord agents render link previews correctly.
  https://axrush.com/guides/meta-tags#no-twitter

#### HTTP Headers — 75/100

- **FAIL** Missing critical header: Strict-Transport-Security
  Add the Strict-Transport-Security response header to your server configuration. This is a critical security header.
  https://axrush.com/guides/http-headers#missing-critical-header
- **PASS** 5/7 security headers present
- **WARN** No Link header for AI discovery (llms.txt, Agent Card)
  Add a Link response header pointing to your AI discovery files: Link: </llms.txt>; rel="alternate"; type="text/plain", </.well-known/agent-card.json>; rel="alternate"; type="application/json"
  https://axrush.com/guides/http-headers#no-link-header
- **WARN** No machine-readable discovery relations beyond llms.txt and the Agent Card
  describedby — llms.txt v2 uses this relation to point a page at the llms.txt that covers it.
api-catalog — RFC 9727: the catalog of APIs this publisher offers.
service-desc — RFC 8631: a machine-readable API description.
service-doc — RFC 8631: human documentation for the API.
ai-catalog — Draft: the AI catalog listing agent cards and MCP server cards.
c2pa-manifest — C2PA 2.4: content provenance for media on the page.
license — RSL and other machine-readable licensing terms.
  Advertise what you publish with Link relations so agents stop guessing paths. Add the ones that apply, for example: Link: </llms.txt>; rel="describedby", </.well-known/api-catalog>; rel="api-catalog". Informational in 3.x: this does not affect your score.
  https://axrush.com/guides/http-headers#discovery-relations

### Protocolos — 9/100

#### Agent Card (A2A) — 0/100

- **FAIL** /.well-known/agent-card.json not found
  Site is agent-facing (an API surface (navigation into an API or developer area)). Also tried the pre-0.3 path /.well-known/agent.json. IANA-registered well-known URI.
  This site offers something an agent could call, but nothing tells an agent what. Publish an A2A Agent Card at /.well-known/agent-card.json. A minimal 1.0 card needs name, description, version, capabilities, supportedInterfaces, defaultInputModes, defaultOutputModes and skills. Spec: https://a2a-protocol.org/latest/specification/
  https://axrush.com/guides/agent-card#not-found

#### OpenAPI Spec — 0/100

- **FAIL** API surface present but no machine-readable description found
  Evidence of an API: navigation into an API or developer area. Checked /.well-known/api-catalog, Link and <link> rel="service-desc", and /.well-known/openapi.json, /openapi.json, /openapi.yaml, /.well-known/openapi.yaml, /api/openapi.json, /v1/openapi.json, /swagger.json, /api-docs, /asyncapi.json, /arazzo.json
  The API exists; nothing describes it in a form an agent can read, so using it requires a human to read your documentation first. Serve an OpenAPI description at /openapi.json and advertise it with Link: </openapi.json>; rel="service-desc". For several APIs, publish an RFC 9727 catalog.
  https://axrush.com/guides/api-discovery#not-found

#### MCP (Model Context Protocol) — N/D

- **PASS** No MCP server — MCP discovery does not apply to this site
  A server card describes an MCP server so agents can find it. A site that runs none has nothing to advertise. Run with --profile mcp to audit as though it did.

#### Catálogo de IA — 0/100 (informa, no puntúa)

- **WARN** No agent resource catalog found
  Checked robots.txt Agentmap: directive, Link header rel="ai-catalog", <link rel="ai-catalog">, well-known path and /.well-known/ai-catalog.json, /.well-known/ard.json. Both specifications are drafts.
  A catalog is one document listing everything an agent can call here — agent cards, MCP servers, APIs, skills — so a client stops probing four conventions to find out. Worth publishing once you have more than one of those. Informational: both ai-catalog.json and ard.json are still drafts, so this never affects your score.
  https://axrush.com/guides/ai-catalog#not-found

#### Habilidades de agente — 0/100

- **WARN** No Agent Skills published
  Checked /.well-known/agent-skills/index.json, /.well-known/skills/index.json, /skill.md, /SKILL.md. Draft specification — the path may still change. Cloudflare RFC v0.2.0 (2026-03-12). Not registered; a competing shorter path (/.well-known/skills/) also ships.
  This site has documentation, so it has procedures worth teaching. A skill is a SKILL.md an agent installs and follows: setup steps, argument shapes, the mistakes to avoid. Publish one per task at /.well-known/agent-skills/{name}/SKILL.md and list them in /.well-known/agent-skills/index.json.
  https://axrush.com/guides/agent-skills#not-found

#### Descubrimiento de comercio — 75/100 (informa, no puntúa)

- **PASS** UCP profile published at /.well-known/ucp
  Vendor convention, not IANA-registered. Google-led, adopted by Shopify, Etsy, Walmart and Stripe. Not IANA-registered.
- **PASS** UCP version 2026-08-25
- **PASS** 1 commerce service(s) declared: dev.ucp.shopping
- **PASS** 2 declared schema URL(s) resolve
- **WARN** UCP profile declares no payment handlers
  Without a payment handler an agent can read your catalog but cannot complete a purchase. Declare the handlers you accept.
  https://axrush.com/guides/commerce-discovery#no-payment-handlers
- **WARN** UCP profile declares no signing keys
  Publish the public keys an agent uses to verify your responses. Money is moving; identity should not rest on DNS alone.
  https://axrush.com/guides/commerce-discovery#no-keys

#### Descubrimiento de autenticación — 90/100

- **PASS** Protected-resource metadata published (RFC 9728)
  IANA-registered well-known URI.
- **PASS** 2 authorization server(s) named
- **PASS** Authorization server https://account.beardbrand.com publishes discovery metadata
- **PASS** PKCE with S256 supported
- **WARN** No automated client registration
  Without dynamic registration or Client ID Metadata Documents, every new agent needs a human to register it first. That is a queue, not an integration.
  https://axrush.com/guides/auth-discovery#no-registration

#### WebMCP — N/D

- **PASS** No forms and no WebMCP code — nothing here for an agent to invoke as a tool

### Política — 18/100

#### Security.txt — 0/100

- **FAIL** /.well-known/security.txt not found
  HTTP 404
  Create a /.well-known/security.txt file per RFC 9116. At minimum, include Contact: and Expires: fields. See https://securitytxt.org/ for a generator.
  https://axrush.com/guides/security-txt#not-found

#### RSL License — 0/100

- **FAIL** No RSL license discovery found
  Checked robots.txt License directive, Link header, and <link rel="license" type="application/rsl+xml">
  Declare machine-readable licensing terms for your content with Really Simple Licensing. Add to robots.txt: License: https://your-site.com/license.xml — then publish the RSL document. See https://rslstandard.org.
  https://axrush.com/guides/rsl#not-found

#### Política de uso — 40/100

- **WARN** No machine-readable usage policy declared
  Checked robots.txt Content-Signal and Content-Usage, the Content-Usage and content-signal response headers, an RSL licence, TDMRep, and the noai meta directive.
  State your terms where they can be read without a lawyer. The lowest-effort option is a Content-Signal line in robots.txt: Content-Signal: search=yes, ai-input=yes, ai-train=no. Absence is neutral, not permission — but it also gives you nothing to point at.
  https://axrush.com/guides/usage-policy#no-policy

---

Representación en Markdown de https://axrush.com/report/beardbrand.com
