Blogs & Newsletters

Browse blogs and newsletters by AI visibility score. Inspect crawler access, then check article availability, authorship and publication dates at the source.

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.txt1A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt1The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap1A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt1The 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-LD1Structured 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 HTML1The 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 navigation1Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons1Links 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 states1Homepage 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 URL1Each 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.

Clear signals

Filters · 2 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.txt1A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt1The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap1A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt1The 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-LD1Structured 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 HTML1The 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 navigation1Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons1Links 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 states1Homepage 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 URL1Each 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.

Clear signals

1 site

Descriptive llms.txt

Websites in the directory, with their Good for Bots score. Column headers sort the list.
Site	Category	Score
Botmonster Tech botmonster.com Hands-on guides and articles on artificial intelligence, self-hosting, Linux, and developer tools	Blogs & Newsletters	View report for Botmonster Tech:

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 Blogs & Newsletters

An article can have a public URL and still reveal very little to a crawler. The title loads, the subscription prompt appears, and the argument lives somewhere the response never includes. For an assistant asked to summarise or cite a piece, the difference between a preview and the complete article matters.

Blogs and newsletters are most useful as sources when a reader can identify the author, the publication date and the article's scope. Permanent links make individual pieces addressable. A public archive gives readers somewhere to explore beyond the newest issue, while clear subscription boundaries explain what is actually available.

A scan of the homepage and a few sampled pages may not reveal restrictions on individual articles. Open the piece you need to check its availability and evidence; the score does not assess the writing.

What to look for

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

An article, not just a preview: Check what the public page actually contains. A readable introduction does not establish that a bot can access the rest of a paid issue.
Authorship and dates: Bylines and publication or update dates give a quotation context. A reader should be able to identify whose argument they are citing.
A navigable archive: Individual URLs and ordinary links make older work reachable. An endless feed should not be the only route to a specific article.
Explicit source links: Links to the material discussed let a reader follow a claim back to its origin. Readability does not make an unsupported claim reliable.

Frequently asked questions

Does a listing mean the newsletter is free?

No. A publication can offer both public and paid material. The report only describes the evidence available to the scanner on its fetched URLs.

Do you assess the quality of the writing?

No. The score concerns readability for machines, not editorial merit or factual accuracy. Assess the author's evidence separately.

Will a high score get my articles cited?

It does not guarantee citations. Access is one part of being a usable source; relevance, attribution and an assistant's source selection still matter.

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