Skip to main content

Implementation depth

Guides

The long-form reference tier: how to implement what the audit measures, with our own production setup as the worked example. Fewer pieces, more depth.

Small robot crawlers queueing at an open gate, one passing through under a mint pass mark

AI crawler directory: who fetches your site, and what to allow

The working list of AI crawlers worth a robots.txt decision: who operates each one, what it feeds (training, search index, or live answers), and a decision framework, with this site's 15-crawler allowlist as the example.

A structured document with highlighted section bars being scanned line by line while a small block arrives to read it

How to write an llms.txt that actually gets read

A working llms.txt is a curated index, not a sitemap dump. This guide walks through the three-file setup running on this site (llms.txt, llms-full.txt, and a handshake briefing), with the real files as the worked example.

A panel framed by curly braces holding a small graph of connected nodes, one node lit in mint

JSON-LD recipes for AI visibility: the five blocks that matter

Structured data is the weakest layer in the AI-readiness benchmark. Five copy-pasteable JSON-LD recipes fix most of it: Organization, Person, WebSite, FAQPage, and Dataset, annotated from this site's production graph.

A clipboard of checklist rows with mint check squares filling in one after another

The AI visibility checklist: 33 checks, in scoring order

Every binary check that decides whether AI engines can fetch, parse, trust, and cite your site, organized by the nine sections of the audit rubric and ordered by weight. Work it top to bottom.