TIME serves bots a different website, and User-Agent is now a billing identity

TIME’s 2026 deployment with Mobian serves conventional HTML pages to browsers and Googlebot while delivering much smaller markdown versions containing a single agent-targeted advertisement to user agents such as ClaudeBot, PerplexityBot, and OAI-SearchBot, with each request assigned a unique impression identifier and token count for measurement and billing. The arrangement highlights the risks of treating a self-declared User-Agent header as a commercial identity, since headers can be spoofed and tests found that TLS fingerprinting and client behavior could change results even when the declared agent was identical. The text argues that Web Bot Auth, an emerging IETF-based system using HTTP message signatures, public-key directories, short-lived credentials, and potentially declared content-use purposes, offers a more verifiable basis for access controls, licensing, and metered agent content. However, signed identity would not resolve concerns about cloaking, the downstream handling of sponsored markdown content, or loss of ad disclosures when retrieval systems split material into chunks. As AI crawler traffic and related policy efforts grow, including proposed disclosure requirements, publishers are encouraged to audit differences in responses across clients and bot identities, align stated crawling policies with deployed behavior, and reserve authenticated identity rather than User-Agent strings for consequential decisions such as billing and paid access.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.