# Préparation de tripadvisor.com à l'IA

> Mesuré sur la page d'accueil. Note globale : Faible.

Score 43/100, note Faible. Mesuré 2026-09-04T22:30:37.776+00:00, moteur ax-audit@4.1.0.

## Vérifications

### Contenu — 45/100

#### Content Negotiation — 0/100

- **FAIL** Homepage does not serve Markdown via content negotiation
  Got text/html (HTTP 403) 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

#### Opérabilité par les agents — 100/100

- **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 — 50/100

- **WARN** Sparse server-rendered content (9 words, 59 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 (7.6%)
- **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
- **WARN** No <h1> heading found
  Add a single <h1> describing the page. Agents and search engines treat the H1 as the primary topic indicator.
  https://axrush.com/guides/html-rendering#no-h1

#### SEO Basics — 50/100

- **WARN** <title> is too short (15 chars): "tripadvisor.com"
  Lengthen the title to 20-70 characters with a clear topic indicator.
  https://axrush.com/guides/seo-basics#short-title
- **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">
- **WARN** No UTF-8 charset declaration in HTML head
  Add <meta charset="utf-8"> as the first child of <head>. Without it, agents can mis-decode non-ASCII content.
  https://axrush.com/guides/seo-basics#no-charset
- **WARN** Missing or incomplete viewport meta tag
  Add <meta name="viewport" content="width=device-width, initial-scale=1">. Helps mobile agents render the page correctly.
  https://axrush.com/guides/seo-basics#no-viewport

### Accès — 49/100

#### TLS / HTTPS — 87/100

- **PASS** Site is served over HTTPS
- **WARN** Could not verify HTTP→HTTPS redirect
  HTTP 403 on http://tripadvisor.com/
  Test manually: a request to http://your-site.com should respond with 301 → https://your-site.com.
  https://axrush.com/guides/tls-https#redirect-unknown
- **WARN** HSTS max-age is short (86400s = ~1 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
- **PASS** HSTS includes 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 — 0/100

- **FAIL** Baseline homepage request failed — cannot compare crawler access
  HTTP 403
  https://axrush.com/guides/agent-access#baseline-unavailable

#### Directives IA — 100/100

- **PASS** Homepage is indexable
- **WARN** Google-Extended is disallowed, but this page is still eligible for AI Overviews
  robots.txt disallows Google-Extended; no nosnippet or max-snippet directive is set on the page.
  Google-Extended governs Gemini training and grounding in Gemini Apps and Vertex AI. AI Overviews and AI Mode follow Googlebot and the snippet directives instead. If the intent was to stay out of AI Overviews, use nosnippet or max-snippet. If the intent was to opt out of training, this is already correct.
  https://axrush.com/guides/ai-directives#google-extended-mismatch

#### Hygiène HTTP — 80/100

- **WARN** A missing page redirects (301) instead of returning 404
  Location: https://www.tripadvisor.com/ax-audit-probe-3q8dkq9f
  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.tripadvisor.com/
- **PASS** Content-Type: text/html with charset

#### Crawl Efficiency — 0/100

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

### Découverte — 44/100

#### LLMs.txt — 0/100

- **FAIL** /llms.txt not found
  HTTP 403
  Create a /llms.txt file at your site root following the llmstxt.org specification. It should be a Markdown file starting with "# Your Site Name" and include a description, sections, and links.
  https://axrush.com/guides/llms-txt#not-found

#### Robots.txt — 67/100

- **PASS** /robots.txt exists
- **WARN** 11/12 core AI crawlers configured
  Claude-SearchBot — Blocking it removes your site from the index Claude cites when it searches the web.
  Add explicit User-agent entries for the missing crawlers with Allow: / for each one.
  https://axrush.com/guides/robots-txt#missing-crawlers
- **WARN** 12 AI crawler(s) explicitly blocked
  Amazonbot, Applebot-Extended, Bytespider, CCBot, ClaudeBot, GPTBot, Google-CloudVertexBot, PanguBot, PetalBot, YouBot, meta-externalagent, Google-Extended
  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
- **WARN** 2 assistant search crawler(s) blocked — your site cannot be cited by those assistants
  PetalBot — search index crawler
YouBot — Indexes pages for You.com search and its LLM answers.
  Search crawlers build the index an assistant cites from; they are separate from the training crawlers. If the intent was to opt out of training only, allow these and block the training tokens instead.
  https://axrush.com/guides/robots-txt#blocked-search-crawlers
- **PASS** 10 training crawler(s) blocked — recorded as a deliberate policy choice
  Amazonbot, Applebot-Extended, Bytespider, CCBot, ClaudeBot, GPTBot, Google-CloudVertexBot, PanguBot, meta-externalagent, Google-Extended
- **WARN** 1 robots.txt rule(s) target a retired or non-existent crawler token
  Cohere-ai — Cohere states it operates no web crawlers.
  These rules have no effect. Remove them so the file reflects your actual policy.
  https://axrush.com/guides/robots-txt#legacy-tokens
- **WARN** 5 AI crawler(s) have partial path restrictions
  ChatGPT-User, OAI-SearchBot, applebot, PerplexityBot, bingbot
  These crawlers have Disallow rules on specific paths. For full AI access, use only "Allow: /" and let the wildcard User-agent: * handle path restrictions.
  https://axrush.com/guides/robots-txt#partial-restrictions
- **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
- **PASS** 17/57 known AI crawlers have explicit rules

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

#### Sitemap — 0/100

- **FAIL** No sitemap found
  Tried robots.txt Sitemap: directive and /sitemap.xml
  Publish an XML sitemap at /sitemap.xml and reference it from robots.txt with: Sitemap: https://your-site.com/sitemap.xml
  https://axrush.com/guides/sitemap#not-found

#### HTTP Headers — 70/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
- **WARN** Only 1/7 security headers present
  Add security headers like Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy to your server response.
  https://axrush.com/guides/http-headers#low-security-headers
- **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

### Protocoles — 0/100

#### Agent Card (A2A) — N/A

- **PASS** No agent-facing surface — an Agent Card does not apply to this site
  No API, MCP server or existing card was found. An Agent Card advertises capabilities another agent can invoke; a site that offers none has nothing to put in it. Run with --profile agent to audit as though it did.

#### OpenAPI Spec — N/A

- **PASS** No API surface — API discovery does not apply to this site
  No description, catalog, service-desc relation or developer area was found. Run with --profile api to audit as though the site offered one.

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

- **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.

#### Catalogue IA — 0/100 (informe, ne note pas)

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

#### Compétences d'agent — N/A

- **PASS** No developer-facing surface — skills do not apply to this site
  No documentation links, llms.txt, or API description found. Skills describe procedures an agent follows; a site with no procedures to teach has nothing to publish.

#### WebMCP — N/A

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

#### Découverte commerce — 0/100 (informe, ne note pas)

- **FAIL** /.well-known/ucp requires authentication
  HTTP 403
  The UCP profile must be publicly accessible with no authentication. An agent reads it before it has any credentials.
  https://axrush.com/guides/commerce-discovery#profile-auth

#### Découverte d'authentification — N/A

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

### Politique — 18/100

#### Security.txt — 0/100

- **FAIL** /.well-known/security.txt not found
  HTTP 403
  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

#### Politique d'usage — 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

---

Représentation Markdown de https://axrush.com/report/tripadvisor.com
