# Reuters and Time Block All AI Crawlers, Force OpenAI and Perplexity to Ask First

*Publishers flip default permission to denial, proving brand story requires active protection at infrastructure level.*

By **Jenny Huang Goodman MPA MSc MHSA, Principal** — The Stash Edge, Hako Shikin LLC.
Published 2026-06-09.

Canonical: https://www.pops4.com/stash/articles/reuters-time-publishers-2026-06-09t21-7
Subject: Reuters & Time (Publishers)
Tags: brand protection, content licensing, ai crawlers, brand narrative, media kit strategy, origin story

---

Reuters and Time implemented block-all bot strategies this month, forcing AI companies to request whitelist access before crawling their content, according to Digiday. The publishers moved from passive opt-out to active gatekeeping, changing robots.txt files to deny all automated crawlers unless explicitly approved. The shift reflects growing publisher concern that AI training consumes editorial work without compensation or attribution.

The mechanics are straightforward. Both publishers modified their robots.txt files to disallow all user agents by default, then created whitelist exceptions for approved crawlers like Google and Bing. AI companies including OpenAI, Anthropic, and Perplexity must now negotiate access rather than assume it. Time confirmed the change to Digiday but declined to detail whitelist criteria. Reuters did not respond to requests for comment on which AI crawlers received approval. The block-all approach represents a harder line than the piecemeal bot-by-bot blocking most publishers used previously.

This works because it inverts the negotiation power. Under the old model, publishers played defense, blocking new AI crawlers as they appeared while existing bots scraped freely. The block-all stance forces AI companies to identify themselves, explain their use case, and offer terms before touching content. Publishers gain visibility into who accesses their work and leverage to demand licensing fees or attribution standards. The strategy also creates friction for undisclosed crawlers that ignore robots.txt, making unauthorized access more legally defensible as trespass rather than ambiguous fair use.

A physical product brand can run the same play with its owned content and brand story. Start with your product photography, founder narrative, and origin story content. Audit where these assets live and who can access them. Move all brand story materials behind a simple permission layer: a lightweight media kit request form that collects company name, use case, and contact information before granting download access. This mirrors the whitelist model at brand scale.

Build the gate this way. Host brand assets on a subdomain with its own robots.txt file set to disallow all by default. Create a landing page explaining your brand story protection policy: we license our images, founder story, and origin content to partners who attribute properly and align with our values. Include a two-field form: company name and intended use. Review requests manually or auto-approve based on email domain. Grant access via expiring download links or a password-protected asset library. Track who requests what. The infrastructure costs nothing beyond a subdomain and basic form tool.

This creates three advantages for a small brand. First, you know exactly who is using your brand story and how, converting invisible asset drift into visible partnership opportunities. Second, you gain negotiation position when larger retailers, publications, or AI companies want your narrative for their purposes—they ask first, establishing that your story has value. Third, you build a documented record of protection efforts, strengthening trademark and copyright enforcement if your brand story gets misused or diluted later. The permission layer is evidence of active brand stewardship.

The broader pattern: brand story is infrastructure, not decoration. Reuters and Time treat editorial content as protected inventory requiring explicit access terms. Physical product brands should treat origin story, founder narrative, and product imagery the same way. The default should be controlled access, not open distribution. When someone wants your brand story, make them request it, explain their use, and enter a relationship—even if you approve every request. The ask itself establishes that your brand narrative belongs to you, not to whoever scrapes it first.

## The takeaway

Block-all default on brand assets forces AI and partners to request access, converting invisible usage into documented relationships.

---

## Publisher

**Hako Shikin LLC** — Virginia Beach, Virginia. Founded 1997. ASI 217876 · DUNS 18-204-6339.
Principal and author: **Jenny Huang Goodman MPA MSc MHSA**.

- Author: https://www.huanggoodman.com/about
- LLM context: https://www.pops4.com/stash/llms.txt
- MCP endpoint, for AI agents: https://mcp.pops4.com/mcp
- Client dashboard: https://dashboard.pops4.com/
- Catalogue: 70,000+ products, 200+ brands