neptune-nautica.com
escaneado 5/8/2026, 11:29:42 · en caché · se actualiza en 22 h · rubric 2026.10.4
Construido con WordPress
Necesita trabajo
Así experimentan neptune-nautica.com los agentes de IA (no los navegadores). La puntuación pondera cinco categorías de legibilidad para máquinas; las marcas del arco son las 36 comprobaciones individuales que hay detrás.
Los detalles técnicos de las comprobaciones aparecen en inglés, pues provienen directamente del escáner.
Envíalo a quien edita el sitio. El enlace muestra la puntuación y la nota como tarjeta de vista previa, y se mantiene al día: relee el último análisis en vez de congelar el valor de hoy.
Correcciones principales
failLink response headers+1 ptDescubribilidadNo HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.
Ver los pasos exactos
Qué significa
HTTP responses can carry a Link header: the same canonical and alternate-language information your HTML declares, but delivered in the response envelope itself. Agents that only send a HEAD request, or that decide what to do while the page is still streaming, read the header without parsing any HTML. Yours is missing (or carries none of the relations agents use: canonical, alternate, describedby).
Por qué importa
An agent triaging fifty URLs doesn’t want to download and parse fifty pages to learn which are duplicates of which. The Link header answers at the cheapest possible layer. Sites that provide it get correctly de-duplicated and correctly language-routed even by the most minimal fetchers.
Haz esto
- Emit a Link header alongside each page, mirroring what your HTML head already declares. Example: Link: <https://yoursite.com/page>; rel="canonical".
- Most stacks set this in one place: Next.js headers() config, an nginx add_header line, or a CDN response-header rule.
- If you serve translations, add rel="alternate" entries with hreflang, matching your HTML.
No pierdas este informe
Recíbelo ahora en tu correo, más un aviso cada vez que cambie la puntuación de neptune-nautica.com. Gratis, date de baja cuando quieras.
¿Prefieres que lo vigilemos por ti? Monitor reescanea cada semana y avisa de cualquier cambio, $29/mo. Empezar a monitorizar →
Este escaneo calificó una página. Tu sitio es más que una página.
Esto calificó solo tu página de inicio. Tus precios, documentación y checkout viven en otras páginas: justo las que los asistentes citan cuando te recomiendan. Un 72/100 aquí significa que los agentes ya se pierden cosas en tu mejor página. El Deep Scan ($29) audita todo el sitio con las 36 comprobaciones y envía un PDF con cada fallo y su corrección exacta, ordenados por lo que más visibilidad te cuesta. Pago único, entregado en minutos, sin suscripción.
Lo que recibe el agente
Muestra tu puntuación
Inserta esta insignia en tu sitio. Enlaza a este escaneo en vivo y se actualiza con cada reescaneo.
<a href="https://agentspeed.com/scan/neptune-nautica.com"><img src="https://agentspeed.com/badge/neptune-nautica.com" alt="AgentSpeed agent-readiness score" height="56"></a>Seguir esta puntuación
Recibe este informe por correo, y un aviso cuando la preparación de neptune-nautica.com cambie de verdad: una comprobación que empeora o la puntuación global que baja.
Dos cosas nunca disparan un correo: un cambio de puntuación causado por publicar nosotros una nueva rúbrica (es otro instrumento de medida, no un cambio en tu sitio), y movimientos que solo se explican por comprobaciones dependientes del tiempo, que varían de una ejecución a otra.
¿Lo prefieres con tu propio calendario, con Slack o webhook en lugar de correo? La monitorización de deriva está en todos los planes de pago.
Esta puntuación dice si un agente de IA podría leer neptune-nautica.com. La analítica de tráfico IA dice si uno vino de verdad, y qué páginas lo rechazaron.
Desglose completo
16 pass4 warn13 fail3 skip
Descubribilidad
pass
robots.txt present
A robots.txt is reachable at the site root.
100/100
pass
robots.txt allows AI agents
All 9 answer-time access agents allowed.
100/100
fail
Content-Signal directivesemerging
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
0/100
pass
llms.txt present
Found /llms.txt but missing H1 header and markdown links. Not scored.
100/100
pass
Sitemap present
sitemap.xml reachable and referenced from robots.txt.
100/100
fail
Link response headers
No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.
0/100
pass
Canonical URL
Canonical points to self: https://neptune-nautica.com/.
100/100
fail
MCP server cardemerging
No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.
0/100
fail
OAuth authorization metadataemerging
No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.
0/100
fail
OAuth resource metadataemerging
No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.
0/100
fail
API catalog / OpenAPIemerging
No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.
0/100
fail
Web Bot Authemerging
No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.
0/100
Legibilidad
fail
Markdown negotiationemerging
Accept: text/markdown returns HTML, not markdown. Serve a markdown variant of primary content when requested; agents summarize and cite it more reliably.
0/100
fail
Text-to-markup ratio
Visible text is 5.4% of HTML weight (12323/229377 bytes). 17% of the document is inline script, 67% is markup.
40/100
pass
Content without JavaScript
Primary content is present in the initial HTML — agents without JS can read it. (Measured statically; a rendered comparison was not run because the static reading sufficed.)
90/100
fail
Heading hierarchy
Heading issues: no <h1>; 3 skipped level(s).
50/100
warn
Cookie wall blocks content
Consent modal detected ([aria-label*="cookie" i]); content still visible. Verify the modal does not block first-paint for screenshot agents.
70/100
pass
Declared language
Declared lang="x-default" with 2 well-formed hreflang alternate(s).
100/100
pass
Page title
A concise <title> is present (70 chars).
100/100
pass
Meta description
A well-sized meta description is present (142 chars).
100/100
Datos estructurados
pass
JSON-LD present
Found 1 JSON-LD block.
100/100
warn
Structured data validates
2 recommended-field warning(s). First: Organization recommends "logo" (improves agent comprehension). 2 block(s) skipped: type outside the set we check.
90/100
fail
Schema type coverage
Page looks like Article|BlogPosting|NewsArticle; missing JSON-LD type(s): Article|BlogPosting|NewsArticle.
0/100
Coherencia: ¿coinciden sus canales?
skip
JSON-LD price matches the visible priceemerging
No price declared in JSON-LD, so there is nothing to cross-check. (Whether a price SHOULD be declared is the structured-data checks’ question.)
—
pass
JSON-LD name appears on the pageemerging
Declared entity name "Neptune Nautica" appears on the visible page.
100/100
warn
Declared language matches the contentemerging
Declared lang="x-default" but the visible content reads as "en". The usual cause is a template default nobody edited. Agents pick tokenizers, markets, and which variant to quote from this attribute. Declare the language the page is actually in.
40/100
Accionabilidad
pass
Paywall / login wall
No paywall or login-wall detected on the landing URL.
100/100
fail
Agent Skills manifestemerging
No Agent Skills manifest at /.well-known/agent-skills.json. Enumerate the tasks agents can perform (search, add-to-cart, contact-support) so they pick the right one without scraping.
0/100
fail
WebMCP actionsemerging
No WebMCP detected. On pages with first-class actions (cart, support, account), embed a WebMCP server so on-page agents invoke tools directly.
0/100
pass
Primary action reachable
A primary offering and a price or call to action were both identifiable from the served HTML, so an agent can tell what this page sells and what it costs without running scripts.
100/100
pass
Reachability
HTTP 200.
100/100
pass
Primary action is clickableemerging
1 clickable element(s) carry an action an agent can take: <button> announcing "subscribe". An agent driving the page has something real to click.
100/100
skip
Filters reachable by URLemerging
This page does not offer to filter or sort a list, so there is nothing to address by URL. Pages without facets are not penalised here.
—
Rendimiento
warn
Time to first byte
TTFB 857ms. Acceptable.
60/100
skip
Full render time
Full-render time unavailable (browser pass skipped or failed).
—
pass
Page weight
Initial document is a lean 224 KB.
100/100
Más allá del escaneo
¿Ejecutas tus propios agentes de IA? AgentSpeed también los monitoriza en producción: cada ejecución, su latencia, coste y fallos, con alertas cuando algo se rompe. Gratis hasta 10.000 eventos al mes, sin tarjeta.