# Preparación para AI de slack.com

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

Puntuación 61/100, nota Aceptable. Medido 2026-09-04T21:41:33.963+00:00, motor ax-audit@4.0.0.

## Comprobaciones

### Contenido — 65/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

#### Operabilidad para agentes — 80/100

- **PASS** 341/341 interactive elements have an accessible name
- **WARN** 110/116 images, frames or videos have no declared dimensions
  Undeclared dimensions shift the layout as media loads. An agent working from a screenshot clicks where the button was a moment ago. Set width and height, or aspect-ratio.
  https://axrush.com/guides/agent-operability#unsized-media
- **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.

#### 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 — 100/100

- **PASS** Server-rendered content detected (2162 words, 13672 chars of visible text)
- **PASS** Text-to-markup ratio is healthy (5.3%)
- **PASS** Semantic landmarks present (main, section, header, footer, nav)
- **PASS** Single <h1> heading: "All your people and AI agents working together."
- **PASS** 91/91 <img> tags have alt attributes

#### SEO Basics — 95/100

- **PASS** <title> length 49 chars: "Slack | AI Work Platform &amp; Productivity Tools"
- **WARN** Meta description is long (173 chars)
  Trim to 70-160 characters; longer descriptions get truncated.
  https://axrush.com/guides/seo-basics#long-description
- **PASS** Canonical URL: https://slack.com
- **PASS** <html lang="en-US">
- **PASS** UTF-8 charset declared
- **PASS** Viewport meta present: "width=device-width, initial-scale=1"
- **PASS** 16 hreflang alternate(s) including x-default

### Acceso — 65/100

#### TLS / HTTPS — 100/100

- **PASS** Site is served over HTTPS
- **PASS** HTTP requests redirect to HTTPS
- **PASS** HSTS max-age=31536000
- **PASS** HSTS includes subdomains
- **PASS** HSTS preload-eligible

#### Agent Access — 30/100

- **WARN** Amazonbot is allowed in robots.txt but its User-Agent is refused
  HTTP 404
  General crawler whose content may be used to train Amazon AI models. Your firewall rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (for example Cloudflare "Block AI Crawlers").
  https://axrush.com/guides/agent-access#blocked-crawler
- **WARN** Bytespider is allowed in robots.txt but its User-Agent is refused
  HTTP 404
  Collects training data for ByteDance models. Compliance with robots.txt is disputed. Your firewall rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (for example Cloudflare "Block AI Crawlers").
  https://axrush.com/guides/agent-access#blocked-crawler
- **WARN** CCBot is allowed in robots.txt but its User-Agent is refused
  HTTP 404
  Builds the open Common Crawl corpus that many models train on. Blocking it is the single broadest training opt-out. Your firewall rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (for example Cloudflare "Block AI Crawlers").
  https://axrush.com/guides/agent-access#blocked-crawler
- **WARN** OAI-SearchBot is allowed in robots.txt but its User-Agent is refused
  HTTP 404
  Blocking it removes your site from ChatGPT search answers and citations. Your firewall rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (for example Cloudflare "Block AI Crawlers").
  https://axrush.com/guides/agent-access#blocked-crawler
- **WARN** Claude-SearchBot is allowed in robots.txt but its User-Agent is refused
  HTTP 404
  Blocking it removes your site from the index Claude cites when it searches the web. Your firewall rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (for example Cloudflare "Block AI Crawlers").
  https://axrush.com/guides/agent-access#blocked-crawler
- **WARN** PerplexityBot is allowed in robots.txt but its User-Agent is refused
  HTTP 404
  Blocking it removes your site from Perplexity answers and citations. Not used for model training. Your firewall rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (for example Cloudflare "Block AI Crawlers").
  https://axrush.com/guides/agent-access#blocked-crawler
- **WARN** ChatGPT-User is allowed in robots.txt but its User-Agent is refused
  HTTP 404
  Fetches a page because a ChatGPT user asked for that URL. Blocking it breaks link-following in conversations. Your firewall rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (for example Cloudflare "Block AI Crawlers").
  https://axrush.com/guides/agent-access#blocked-crawler

#### Directivas de IA — 100/100

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

#### Higiene HTTP — 100/100

- **PASS** Missing pages return 404
- **PASS** Homepage answers without a redirect
- **PASS** Content-Type: text/html with charset

#### Crawl Efficiency — 0/100

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

### Descubrimiento — 76/100

#### LLMs.txt — 100/100

- **PASS** /llms.txt exists
- **PASS** /llms.txt Content-Type OK (text/plain)
- **PASS** H1 heading: "Slack"
- **PASS** Blockquote description present
- **PASS** 7 section heading(s) found
- **PASS** 165 link(s) found
- **WARN** /llms-full.txt not found (optional but recommended)
  Create a /llms-full.txt with expanded content — full documentation, API details, and comprehensive site information for AI agents.
  https://axrush.com/guides/llms-txt#missing-full
- **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
- **FAIL** 8/15 sampled llms.txt link(s) are broken
  https://slack.com/customer-stories (HTTP 404)
https://slack.com/trust (HTTP 404)
https://slack.com/pricing (HTTP 404)
https://slack.com/downloads/mac (HTTP 404)
https://slack.com/downloads/linux (HTTP 404)
https://slack.com/enterprise (HTTP 404)
https://slack.com/demo (HTTP 404)
https://slack.com/features/channels (HTTP 404)
  An index of dead links wastes exactly the budget it was meant to save, and an agent has no way to tell a moved page from a removed one. Revalidate llms.txt when you move pages.
  https://axrush.com/guides/llms-txt#broken-links
- **WARN** 2 sampled link(s) redirect
  https://slack.com/downloads → https://slack.com/downloads/other
https://slack.com/team-chat → https://slack.com/features/team-chat
  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 — 60/100

- **PASS** /robots.txt exists
- **FAIL** No core AI crawlers explicitly configured
  Expected: GPTBot, ClaudeBot, Meta-ExternalAgent, Google-Extended, Applebot-Extended, Amazonbot, Bytespider, CCBot, OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User
  Add User-agent entries for core AI crawlers in your robots.txt. For each crawler, add: User-agent: <name> followed by Allow: / on the next line.
  https://axrush.com/guides/robots-txt#no-core-crawlers
- **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** 0/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

#### Meta Tags — 54/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
- **PASS** OpenGraph required tags present (og:title, og:description, og:url, og:type)
- **PASS** Twitter Card required tags present (twitter:card, twitter:title, twitter:description)

#### Sitemap — 100/100

- **PASS** Sitemap located: https://slack.com/sitemap.xml
- **PASS** Content-Type is XML (application/xml)
- **PASS** Sitemap-index references 13 child sitemap(s)
- **PASS** 3/3 sample child sitemap(s) reachable
- **PASS** Sample yielded 4532 URL(s) across 3 child(ren)

#### HTTP Headers — 75/100

- **FAIL** Missing critical header: X-Content-Type-Options
  Add the X-Content-Type-Options response header to your server configuration. This is a critical security header.
  https://axrush.com/guides/http-headers#missing-critical-header
- **PASS** 4/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 — 20/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 — 45/100

- **PASS** API description found at /api/openapi.json via conventional file path
- **WARN** API description is only discoverable by guessing its path
  Nothing on the site points at it, so an agent has to try known filenames. Advertise it with a Link header (Link: <…>; rel="service-desc") or a <link rel="service-desc"> tag, and for multiple APIs an RFC 9727 catalog.
  https://axrush.com/guides/api-discovery#undiscoverable
- **PASS** Valid JSON
- **FAIL** No "openapi" or "swagger" version field
  Add an "openapi" field naming the specification version, for example "3.1.0".
  https://axrush.com/guides/api-discovery#no-version
- **WARN** Missing info.title
  Add info.title naming the API. Agents show it when choosing between tools.
  https://axrush.com/guides/api-discovery#no-title
- **WARN** Missing info.description
  Add info.description explaining what the API does. This is the text an agent reads to decide whether to use it.
  https://axrush.com/guides/api-discovery#no-description
- **WARN** No paths documented
  Document your endpoints under "paths". A description with no operations tells an agent nothing it can act on.
  https://axrush.com/guides/api-discovery#no-paths
- **WARN** No servers declared
  Add a "servers" array with the base URL. Without it an agent has to guess where to send requests.
  https://axrush.com/guides/api-discovery#no-servers

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

#### WebMCP — N/D

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

#### Descubrimiento de comercio — N/D

- **PASS** No commerce surface — agentic-commerce discovery does not apply to this site
  No Product or Offer structured data, cart links, or product price tags found.

#### Descubrimiento de autenticación — N/D

- **PASS** Nothing on this site requires authorization — auth discovery does not apply
  No API description, API catalog, MCP server card or commerce profile found.

### Política — 43/100

#### Security.txt — 75/100

- **PASS** /.well-known/security.txt exists
- **PASS** Required field "Contact" present
- **FAIL** Required field "Expires" missing (RFC 9116)
  Add "Expires:" to your security.txt. Use an ISO 8601 date, e.g., Expires: 2026-12-31T23:59:59.000Z
  https://axrush.com/guides/security-txt#missing-field
- **PASS** 1/5 optional fields present

#### 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/slack.com
