News & Media

Explore AI visibility reports for news and media websites. Review crawler access and look for article dates, bylines, corrections and source links.

How websites are scored

Signals

Each one you pick narrows the list: a site must have them all.

Agent capabilities

API catalog0Lists the site's public APIs in one standard place, so an agent can find and use them without reading the docs. A bonus: it earns a badge and never costs points.
auth.md0A simple file that tells AI agents how to sign in and get access. A bonus: it earns a badge and never costs points.
A2A agent card0Describes the site's own AI agent in the A2A format, so other agents can find it and hand it work. A bonus: it earns a badge and never costs points.
Agent Skills index0Lists reusable instructions the site publishes for AI agents, with descriptions and download locations. The index earns a badge; the skill downloads themselves are not verified.
Web Bot Auth0Publishes the keys the site's own bots sign their requests with, so other websites can verify them. The badge checks the keys; the bots' requests are not observed.
ACP commerce0Publishes how agents can connect to its Agentic Commerce Protocol integration. The badge confirms discovery metadata; purchases are not tested.

Standards

llms.txt0A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt0The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap0A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt0The llms.txt describes what is behind each link, so a model knows which pages are worth reading.
llms-full.txt or .md pages0The content is also available as plain Markdown, in one llms-full.txt file or as separate .md pages. Models can read it without the HTML.
Markdown negotiation0Pages come back as clean Markdown when a bot asks for it: just the content, without menus, styling and scripts.
AI crawler rules0The site says which AI bots may visit, for training, search or answering questions. Blocking some is fine; what counts is making a choice.
Content Signals0The site says how its content may be used: for search, in AI answers or to train AI. Any mix of yes and no counts.
schema.org JSON-LD0Structured data on the homepage says what the site is, such as a company, a product or an article, so machines don't have to guess.
Semantic HTML0The page has a clear structure: a main content area, headings in order, a header and a footer. A bot can tell the content from the rest.
Crawlable navigation0Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons0Links and buttons in the collected homepage HTML have names recoverable from text, labels or native alternatives, including icon controls.
Named form fields0Observed homepage fields have recoverable names and recognizable input semantics. Submission behavior is not tested.
Control roles and states0Homepage controls meet static checks for roles, required states and relationship targets, using native HTML semantics where available.
Typed links0The page links to versions made for machines, such as a Markdown copy or an API description, so an agent can go straight to them.
Canonical URL0Each page names the one address that should be indexed and cited, so an agent quoting it links to the right URL.
Working section links0Links to part of a page, such as a table of contents or a skip link, lead to that section instead of the top of the page.

Filters · 1 active

Signals

Each one you pick narrows the list: a site must have them all.

Agent capabilities

API catalog0Lists the site's public APIs in one standard place, so an agent can find and use them without reading the docs. A bonus: it earns a badge and never costs points.
auth.md0A simple file that tells AI agents how to sign in and get access. A bonus: it earns a badge and never costs points.
A2A agent card0Describes the site's own AI agent in the A2A format, so other agents can find it and hand it work. A bonus: it earns a badge and never costs points.
Agent Skills index0Lists reusable instructions the site publishes for AI agents, with descriptions and download locations. The index earns a badge; the skill downloads themselves are not verified.
Web Bot Auth0Publishes the keys the site's own bots sign their requests with, so other websites can verify them. The badge checks the keys; the bots' requests are not observed.
ACP commerce0Publishes how agents can connect to its Agentic Commerce Protocol integration. The badge confirms discovery metadata; purchases are not tested.

Standards

llms.txt0A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt0The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap0A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt0The llms.txt describes what is behind each link, so a model knows which pages are worth reading.
llms-full.txt or .md pages0The content is also available as plain Markdown, in one llms-full.txt file or as separate .md pages. Models can read it without the HTML.
Markdown negotiation0Pages come back as clean Markdown when a bot asks for it: just the content, without menus, styling and scripts.
AI crawler rules0The site says which AI bots may visit, for training, search or answering questions. Blocking some is fine; what counts is making a choice.
Content Signals0The site says how its content may be used: for search, in AI answers or to train AI. Any mix of yes and no counts.
schema.org JSON-LD0Structured data on the homepage says what the site is, such as a company, a product or an article, so machines don't have to guess.
Semantic HTML0The page has a clear structure: a main content area, headings in order, a header and a footer. A bot can tell the content from the rest.
Crawlable navigation0Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons0Links and buttons in the collected homepage HTML have names recoverable from text, labels or native alternatives, including icon controls.
Named form fields0Observed homepage fields have recoverable names and recognizable input semantics. Submission behavior is not tested.
Control roles and states0Homepage controls meet static checks for roles, required states and relationship targets, using native HTML semantics where available.
Typed links0The page links to versions made for machines, such as a Markdown copy or an API description, so an agent can go straight to them.
Canonical URL0Each page names the one address that should be indexed and cited, so an agent quoting it links to the right URL.
Working section links0Links to part of a page, such as a table of contents or a skip link, lead to that section instead of the top of the page.

0 sites

No sites match these filters.

Promarks a Pro listing, in gold. Pro never changes a score or a place in the order.What Pro includes

Through a bot’s eyes

About News & Media

News loses meaning when its date disappears. A report about a proposal can be mistaken for an account of a law already in force, and a developing story can outlive the facts it first described. A machine-readable news page needs to preserve the context around the headline as well as the words underneath it.

Look for distinct article URLs, visible bylines and a clear separation between publication time and later updates. Corrections, source links and labels for opinion or sponsored work help a reader understand what kind of material they have found. These are editorial qualities to inspect, not promises made by a score.

Access rules can differ between a newsroom’s homepage and its archive. Check the article you intend to use, including its sources and corrections; our scanner does not fact-check reporting.

What to look for

Use these questions when reading the sites themselves. They are guidance for this category, not additional scoring checks.

Time that survives extraction: Publication and update dates should be attached to the story. A date in the site header is not enough to establish when the reported event happened.
Reporting distinguished from opinion: Visible labels and author information help readers interpret a page. The same sentence carries different weight in a reported article and an opinion column.
Corrections with a trail: An accessible correction note helps prevent an earlier version from circulating without context. Check the current article before repeating a claim.
Article-level access: Inspect the actual story, including any paywall boundary. An accessible front page does not prove that its linked reporting is readable.

Frequently asked questions

Is the score a measure of news credibility?

No. Machine readability and editorial credibility are different. The report does not verify a publication's reporting or endorse its conclusions.

Can a publisher restrict training and still be listed?

Yes. Our rubric distinguishes training crawlers from search and user-fetch crawlers. A training opt-out alone is not a visibility penalty; refusing our own bot ends its scan without a score.

Do you bypass subscriptions to inspect stories?

No. The scanner uses its declared identity, respects robots.txt and does not sign in or bypass a subscription to read restricted articles.

Questions about scores, scans and listings in general are answered in the FAQ.