
Primary topic Mobile Publishing and Monetization
On November 12, 2026, Yahoo Scout became the first commercial licensee of the Internet Licensing Collective. For an independent publisher, there’s now a route to license selected work for use in an AI answer product without negotiating directly with Yahoo. Start with a section you have the rights to license. Treat it as a limited licensing pilot, with no forecast income until you have payment terms you can use.
| Catalog | First move |
|---|---|
| Original reporting in one section | Check terms for a narrow pilot |
| Original and syndicated work mixed | Separate eligible URLs first |
| Subscriber guide or private archive | Keep the paywall; review delivery |
| Existing direct AI license | Compare coverage before opting in |
| No clear rights to reuse | Leave those works outside |
What Yahoo is signing up for
The collective, formerly the RSL Collective, launched under its new name with more than 3,000 media brands, content owners and platforms, a launch figure reported by the collective. That count describes the launch group, not a count of websites already earning Scout royalties. An AI company takes one agreement for participating work. For publishers, membership is free and nonexclusive. Publishers choose which content and uses to include and opt in to specific licenses. A direct deal stays in place; if its scope overlaps with a proposed license, compare the terms before you enroll the same catalog.
The agreement arrived two days after Yahoo moved Scout out of beta and introduced Pivot Search, which lets readers switch between traditional results and Scout answers. That experience is available on desktop and mobile web in the US, UK, Europe and Switzerland; the Scout app is available in the US on iOS and Android. Those are distribution details for Yahoo Search. The commercial territory and covered surfaces of the Scout license remain undisclosed. For a publisher with UK and US editions, ask for the covered markets before combining the two editions’ results in a revenue report.
Seeing a page in a crawler log tells you it was fetched. Permission and reported use are recorded elsewhere. An RSL declaration expresses terms. The portal or a participating platform handles enrollment and license choices. A paywall or access rule still controls delivery. The collective does not host publisher content; an authorized system gets it from the publisher or through a supplied access URL.
How to license one section without offering the whole site
Use a section declaration when the rights follow a URL prefix. The official section example associates /articles/ with the ILC payment standard:
<rsl xmlns="https://rslstandard.org/rsl">
<content url="/articles/">
<license>
<permits type="usage">ai-all</permits>
<payment>
<standard>https://internetcollective.org/license</standard>
</payment>
</license>
</content>
</rsl>
RSL 1.0 defines ai-all to include training, inference, retrieval, indexing, generation and evaluation. Do not deploy that permission unless it matches your intended license. Confirm a narrower configuration with the collective if you want answer generation without training.
Serve the XML at https://example.com/rsl.xml for this example. Add its discovery line to that host’s robots.txt, preferably before any User-agent group so it is global. RSL also supports group-specific declarations; a matching group’s own License: entries take precedence over global ones:
License: https://example.com/rsl.xml
Enroll https://example.com/ through the publisher portal or a platform partner, confirming licensing authority and any excluded AI systems. Enrollment identifies the host; the declaration identifies the content. For content on news.example.com, give that host its own discovery and enrollment.
Suppose a local newsroom owns its reporting on flood maps, and its syndicated updates live under /wire/. The section example covers /articles/flood-map while leaving /wire/flood-update outside this declaration. The newsroom can keep that split if it holds the required rights for everything it offers under /articles/. If a vendor’s map or photograph on that page is outside its license, hold the page back until the relevant assets are cleared or can be excluded reliably.
For mixed rights within a section, prefer a feed of cleared works until you can verify the finer scope. Private Access URLs can deliver cleared feeds or archives, with a different URL per authorized system. They control delivery; check that the declaration and agreement also express the scope you intend. Keep subscriber-facing access controls in place.
Check the declaration before enrolling
Use this preflight on your own host. It checks what you published; enrollment and reported use still need their own records.
- Fetch the public
robots.txtand follow its applicableLicense:URL. Confirm it returns the intended XML, not a login page. - Parse the XML. Check the RSL namespace, content scope, permissions and payment URL against the accepted terms.
- Check both example paths:
/articles/flood-mapmust fall within the intended scope, while/wire/flood-updatemust remain outside it. Inspect any page, feed or header declarations too; a single file does not reveal every association. - Check access separately. A
License:line does not changeAlloworDisallow. Verify the intended system can retrieve the cleared material through its agreed route.
If a check fails, pause enrollment and correct the declaration or delivery route. For a live mismatch, contact the collective about the affected works and reporting period before changing permissions. A homepage logo, a crawler visit or a public licensing pointer alone cannot confirm an active, paying license. Buying a placement on a participating site does not buy an AI citation; the licensing model pays for contributions the AI product actually uses.
What counts toward payment?
The collective’s published model ties the license fee to the AI product and divides eligible revenue according to how the work contributes, how often it is used, and the value of the product and market. Its own example asks why home insurance premiums are rising. The illustrated answer combines severe-weather losses and rebuilding costs with reinsurance costs, then names the fictional Coastal Ledger in an explanation of insurers leaving high-risk regions. Primary reporting supplies the substance; supporting material adds context; background knowledge can count without a citation. Naming a publication adds value in the model. This is an illustration of allocation, not a captured Scout answer or a payout calculation.
Payments are allocated within the relevant product and market. Yahoo usage does not entitle a publisher to revenue from an unrelated AI product that never uses its work. When assessing a report, ask which product and market its pool represents.
The collective projects its operating costs at or below 10% of license revenue. At 10%, $100 in gross licensing revenue would leave $90 for the pool before it is allocated among publishers. That leaves each publisher’s share to be calculated under the allocation rules. Yahoo’s fee, usage weightings and minimum payout remain undisclosed. Leave expected income blank until the contract or statements support a figure.
The separately published Mather Economics estimate of 15%–35% of AI-company revenue models a potential market, rather than the Yahoo contract. The study does not establish Scout’s actual rate or your share.
Licensees report use and pay the collective, which allocates royalties. The publisher dashboard shows reported usage by website, earnings and payment history. Your site analytics answer a different question: how many readers arrived, where they landed and what they did. A citation can appear without a click, and background use can happen without a citation. Keep referral visits beside the licensing statement rather than dividing one by the other to guess a per-click rate.
Start with a catalog you can check
Pick a section small enough to reconcile with a statement. Before opting in, ask for a sample report, the payout schedule and any minimum, the covered products and markets, and the procedure for removing a work or a licensee. Read the agreement for how a change applies to previously acquired copies and outstanding reporting. Account choices can be updated. Removing a discovery line is not an adequate withdrawal plan: get written confirmation of the effective date and treatment of earlier copies. If those answers matter to your catalog and aren’t available, keep it out for now.
Save the accepted scope and terms, the deployed declaration, and a note naming the hosts and sections included. When the first statement arrives, check that it identifies the correct website and period and that excluded material still stays outside the declared scope. Expand the pilot only when you can explain what you offered, what the report measures and where the money came from.