Informe del sitio: 1 página medida. Valoración general: Aceptable.
Puntuación del sitio · slack.com
Combina el origen y 1 página medida. El reporte de abajo detalla solamente la página de origen.
Lleva los hallazgos a quienes pueden resolverlos. Copia un resumen listo para enviar por Slack, Teams o revisar en la próxima reunión.
Este informe es público. Tu equipo puede abrirlo sin una cuenta.
¿Hay algo que un agente pueda leer?
Homepage does not serve Markdown via content negotiation
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.
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.
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.
341/341 interactive elements have an accessible name
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.
1 obstacle(s) on the entry 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.
Method note: this reads markup, not a rendered accessibility tree
<title> length 49 chars: "Slack | AI Work Platform & Productivity Tools"
Meta description is long (173 chars)
Trim to 70-160 characters; longer descriptions get truncated.
Canonical URL: https://slack.com
<html lang="en-US">
UTF-8 charset declared
Viewport meta present: "width=device-width, initial-scale=1"
16 hreflang alternate(s) including x-default
Server-rendered content detected (2162 words, 13672 chars of visible text)
Text-to-markup ratio is healthy (5.3%)
Semantic landmarks present (main, section, header, footer, nav)
Single <h1> heading: "All your people and AI agents working together."
91/91 <img> tags have alt attributes
¿Un agente puede siquiera llegar al sitio?
Homepage request failed — cannot assess crawl efficiency
Amazonbot is allowed in robots.txt but its User-Agent is refused
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").
Bytespider is allowed in robots.txt but its User-Agent is refused
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").
CCBot is allowed in robots.txt but its User-Agent is refused
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").
OAI-SearchBot is allowed in robots.txt but its User-Agent is refused
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").
Claude-SearchBot is allowed in robots.txt but its User-Agent is refused
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").
PerplexityBot is allowed in robots.txt but its User-Agent is refused
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").
ChatGPT-User is allowed in robots.txt but its User-Agent is refused
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").
Site is served over HTTPS
HTTP requests redirect to HTTPS
HSTS max-age=31536000
HSTS includes subdomains
HSTS preload-eligible
Homepage is indexable
No directive restricts how AI assistants may use this page
Missing pages return 404
Homepage answers without a redirect
Content-Type: text/html with charset
¿Un agente encuentra lo que publicas?
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">.
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">
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">
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">.
OpenGraph required tags present (og:title, og:description, og:url, og:type)
Twitter Card required tags present (twitter:card, twitter:title, twitter:description)
/robots.txt exists
No core AI crawlers explicitly configured
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.
Sitemap directive present
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.
0/57 known AI crawlers have explicit rules
Add explicit User-agent entries for more AI crawlers to maximize discoverability.
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.
4/7 security headers present
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"
No machine-readable discovery relations beyond llms.txt and the Agent Card
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.
/llms.txt exists
/llms.txt Content-Type OK (text/plain)
H1 heading: "Slack"
Blockquote description present
7 section heading(s) found
165 link(s) found
/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.
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.
8/15 sampled llms.txt link(s) are broken
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.
2 sampled link(s) redirect
Point llms.txt at the final URL. Each redirect is a round trip the agent pays for on every visit.
No per-page Markdown mirror found
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.
Consumer note: llms.txt is read by coding agents, not by search
Sitemap located: https://slack.com/sitemap.xml
Content-Type is XML (application/xml)
Sitemap-index references 13 child sitemap(s)
3/3 sample child sitemap(s) reachable
Sample yielded 4532 URL(s) across 3 child(ren)
¿Qué puede invocar un agente?
/.well-known/agent-card.json not found
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/
No agent resource catalog found
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.
No Agent Skills published
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.
API description found at /api/openapi.json via conventional file path
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.
Valid JSON
No "openapi" or "swagger" version field
Add an "openapi" field naming the specification version, for example "3.1.0".
Missing info.title
Add info.title naming the API. Agents show it when choosing between tools.
Missing info.description
Add info.description explaining what the API does. This is the text an agent reads to decide whether to use it.
No paths documented
Document your endpoints under "paths". A description with no operations tells an agent nothing it can act on.
No servers declared
Add a "servers" array with the base URL. Without it an agent has to guess where to send requests.
No MCP server — MCP discovery does not apply to this site
No forms and no WebMCP code — nothing here for an agent to invoke as a tool
No commerce surface — agentic-commerce discovery does not apply to this site
Nothing on this site requires authorization — auth discovery does not apply
¿Qué derechos de uso están declarados?
No RSL license discovery found
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.
No machine-readable usage policy declared
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.
/.well-known/security.txt exists
Required field "Contact" present
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
1/5 optional fields present
Dale a tu equipo informes completos, correcciones priorizadas y seguimiento para mantener las mejoras después de cada lanzamiento.