# Agent technologies for entertainment sites The answers about the site this list is for. Change any of them on the page: https://agentic-readiness.lumar.io/sectors/entertainment-and-media - You publish content you want AI assistants to read or quote: yes - You sell online and take payment on the site: no - Visitors can do things an agent could do for them, like search, book or track an order: no - You offer an API other software can use: no - You run bots or agents of your own that visit other sites: no ## Should have already Standard equipment for a site like yours. If you have it, scan your site to check it is right. - **AI-bot rules** (platform default, rising). Named rules for GPTBot, ClaudeBot and friends, rather than one blanket policy. Effort: low. Running cost: none. Needs: A decision on which AI crawlers may read the site; A rule for each of them in robots.txt. 32% of entertainment sites have it 0.6% of all published ones are broken. - **Canonical URL** (web baseline, flat). Tells an agent which address is the real one for this page. Effort: low. Running cost: none. Needs: A canonical link tag in each page template, pointing at the page's preferred address. - **Content Signals** (platform default, rising). Cloudflare's robots.txt vocabulary for search, AI input and AI training. Effort: low. Running cost: none. Needs: One line in robots.txt saying how your content may be used; Or Cloudflare's managed robots.txt, which adds it. 0.9% of entertainment sites have it 4.3% of all published ones are broken. - **Editorial metadata** (web baseline, flat). Author, dates and provenance behind the content. Effort: low. Running cost: none. Needs: Author, publisher and dates in the structured data of each article. - **HTTP Link header** (web baseline, flat). Relations declared in headers, readable without parsing the body. Effort: low. Running cost: none. Needs: A server or CDN rule that adds Link headers for the page's alternates. - **JSON-LD** (web baseline, flat). Structured data describing what this page is about. Effort: low. Running cost: none. Needs: Structured data in each page template, describing what the page is about. - **Language and encoding** (web baseline, flat). Declared language and charset, so text is interpreted correctly. Effort: low. Running cost: none. Needs: A lang attribute and a character set declared on every page. - **robots.txt** (web baseline, flat). The crawl-policy file every agent reads first. Effort: low. Running cost: none. Needs: A robots.txt file at the root of the site. 96% of entertainment sites have it 1.3% of all published ones are broken. - **XML sitemap** (web baseline, flat). The URL inventory agents and crawlers use for discovery. Effort: low. Running cost: none. Needs: A sitemap your CMS or a build step generates; A job that keeps it current as pages change. 75% of entertainment sites have it 33% of theirs are broken. - **Server-side rendering** (web baseline, flat). Whether the content exists before JavaScript runs. Most agents never run it. Effort: high. Running cost: low. Needs: Page content in the HTML the server sends, not only after scripts run; For a site that renders in the browser today, a framework change. ## Worth building In production at other organisations and gaining ground. Weigh each one by what it takes. - **TDMRep** (early production, rising). The W3C text and data mining reservation, used mainly by publishers. Effort: low. Running cost: none. Needs: A decision on whether you reserve text and data mining rights; A JSON file or header saying so, with a link to your licensing terms. 5 of 5,219 entertainment sites have it 19% of all published ones are broken. - **llms.txt** (early production, rising). A hand-written Markdown index of a site's most useful pages, written for language models. Effort: low. Running cost: low. Needs: A Markdown file listing your most useful pages; Someone to keep it current. 7.1% of entertainment sites have it 9.4% of all published ones are broken. - **Markdown negotiation** (early production, rising). Markdown served to agents that ask for it with Accept: text/markdown. Effort: medium. Running cost: low. Needs: A server or CDN that answers a request for Markdown with Markdown; A Vary: Accept header so caches keep the two versions apart. - **Markdown twin** (early production, rising). A clean low-token markdown version of the page for agents. Effort: medium. Running cost: low. Needs: A build step that turns each page into Markdown; The Markdown served at the page's address with .md added. ## Keep an eye on It fits your site, but it is early or still settling. Nothing to build yet; worth knowing about. - **ai.txt** (specification only, flat). Attribution preferences for AI systems that use the content. Effort: low. Running cost: none. Needs: A text file at the root of the site stating your AI usage terms. 5 of 5,219 entertainment sites have it. - **AIPREF Content-Usage** (specification only, rising). The IETF's standards-track vocabulary for stating how content may be used by AI systems. Effort: low. Running cost: none. Needs: Usage preferences declared in robots.txt or an HTTP header, once the standard settles. - **NLWeb endpoint** (early pilots, receding). Microsoft's conversational /ask route returning schema.org answers. Effort: high. Running cost: high. Needs: A vector database; An embedding model; A pipeline that keeps the embeddings in sync with your content; A language model to write the answers, paid per question; An /ask endpoint to host and scale. None of the 5,219 entertainment sites we scanned have it yet. ## Not for you yet These do not fit your answers above. Change an answer and they move. - A2A agent card: Only if visitors can do things on the site an agent could do for them. - API catalog: Only if you offer an API. - auth.md: Only if visitors can do things on the site an agent could do for them. - MCP server card: Only if visitors can do things on the site an agent could do for them. - Product / Offer schema: Only if you sell online. - schema:Action: Only if visitors can do things on the site an agent could do for them. - OpenAPI description: Only if you offer an API. - MPP (Machine Payments Protocol): Only if you offer an API. - UCP profile: Only if you sell online. - Web Bot Auth directory: Only if you run bots or agents of your own. - WebMCP: Only if visitors can do things on the site an agent could do for them. - x402: Only if you offer an API. - ACP: Only if you sell online. - AP2: Only if you sell online. - MCP authorization: Only if visitors can do things on the site an agent could do for them.