How to Improve Your Site's Agent-Readiness Score on Not Human Search

Not Human Search scores any site from 0 to 100 across 7 agentic signals and gives you a free instant score. To improve it, start by running your site through the "Score Your Site" entry to see which signals are missing, then add the machine-readable files and protocols you lack — most commonly llms.txt, an OpenAPI description, MCP support, and Schema.org markup — and re-check the score after each change. The highest-scoring indexed sites (100) carry the full set: llms.txt, ai-plugin, OpenAPI, API, AI bots, Schema.org, and MCP.

Step 1: Get your baseline score

Use the "Score Your Site" entry on Not Human Search and submit your domain. The result is an instant 0–100 score plus a per-signal breakdown, so you can see exactly which of the 7 agentic signals are present and which are missing. Treat this as your starting point — don't guess at what's absent when the tool tells you.

Step 2: Understand what each signal means

The 7 signals the site scores are:

A site at 100 carries all seven. The listing pages show the exact combination, e.g. "llms.txt ai-plugin OpenAPI API AI bots Schema.org MCP" with a "+25 llms.txt" and "+20 ai-plugin" weighting hint, so the signals are not equally weighted — llms.txt and ai-plugin appear to contribute the largest shares.

Step 3: Add the missing signals

Work from the highest-weight gaps first.

Add llms.txt

Place an llms.txt file at your site root that summarizes what your service does and links to key resources, so agents can read a compact description instead of crawling everything. This is the single most common signal among top-ranked sites.

Add ai-plugin and OpenAPI

Publish an ai-plugin manifest and an OpenAPI specification describing your endpoints, parameters, and auth. Together these let an agent discover and call your service without human interpretation. Sites like CompliAPI advertise "one API key, one GET request," which is exactly the kind of clarity an OpenAPI spec encodes.

Add MCP support

Expose your service through the Model Context Protocol so agents can use it as a tool. Several indexed sites (e.g. Agent Guild) list REST, MCP, and A2A together, signaling broad agent compatibility.

Add Schema.org markup and allow AI bots

Add structured data to your pages and make sure AI crawlers aren't blocked. Both are baseline signals that appear on every 100-scoring listing.

Step 4: Re-check and iterate

After each change, re-run "Score Your Site." Because scoring is instant, you can verify whether a new file was detected before moving to the next signal. If a signal you added isn't registering, confirm the file is reachable at the expected path and correctly formatted — a present-but-unparseable file typically won't count.

What not to worry about

Ranking is based on readiness, never payment, per the site's own statement. So improving your score is purely a matter of adding the machine-readable signals — there's no paid placement to buy. You can also study the 5,379+ indexed sites, filterable by category, protocol, or job, to see which signal combinations the top scorers use and copy the pattern.