# Agent Readiness on seoboosterpro.com: Honest Discovery Without Fake MCP

> How we made the SEO Booster marketing site agent-discoverable with Content Signals, Link headers, api-catalog, Agent Skills, and Markdown, without inventing MCP or OAuth we do not run.

Canonical HTML: https://seoboosterpro.com/seo/agent-readiness-seoboosterpro/
**Quick answer:** We improved agent discovery on seoboosterpro.com with Content Signals, HTTP Link headers, an RFC 9727 api-catalog, real Agent Skills, and Markdown negotiation. We did **not** fake MCP, OAuth, or payment protocols we do not operate.

Cloudflare’s [Agent Readiness scanner](https://radar.cloudflare.com/scan/agents) grades how well a site talks to AI agents. Our first pass looked weak on Link headers, Content Signals, Markdown negotiation, and protocol discovery, even though we already shipped strong AI discovery assets: curated [`/llms.txt`](/llms.txt), [`/entitymap.json`](/entitymap.json), and robots lines for both.

This post is the dogfood write-up: what we added, what we refused to invent, and how that maps to [SEO Booster on WordPress](/seo/ai-search-readiness-wordpress/).

#### What scanners actually measure

At a high level, Agent Readiness asks three questions:

1. **May agents use this content, and how?** (Content Signals in `robots.txt`)
2. **Where are the machine-readable endpoints?** (HTTP `Link` headers, not only HTML `<link>` tags)
3. **What protocols and catalogs exist?** (`.well-known` discovery such as api-catalog and Agent Skills)

Commerce and OAuth checks matter when you run agent-callable APIs or payments. A product marketing site usually should not invent those.

#### What we already had

Before this work, seoboosterpro.com already published:

- [`/llms.txt`](/llms.txt) (and a Danish twin)
- EntityMap at [`/entitymap.json`](/entitymap.json) and [`/entitymap.html`](/entitymap.html)
- `LLMS:` and `EntityMap:` lines in [`robots.txt`](/robots.txt)
- HTML head discovery links for llms.txt and Entity Map

Those help real systems today. Cloudflare’s scanner still wanted newer signals: Content Signals, response `Link` headers, Markdown negotiation, and structured `.well-known` catalogs.

#### What we added

**Content Signals** in `robots.txt`:

```txt
Content-Signal: search=yes, ai-train=no, ai-input=yes
```

Search indexing is welcome. Training on our site content is not. Inference and citation with attribution are OK.

**HTTP Link headers** (nginx) advertising:

- `/llms.txt`
- `/entitymap.json`
- `/.well-known/api-catalog`
- `/.well-known/agent-skills/index.json`
- `/.well-known/agent-knowledge.json`
- `/index.md` as `text/markdown`

**Discovery catalog** at [`/.well-known/api-catalog`](/.well-known/api-catalog): an RFC 9727-style linkset over assets we actually serve (Entity Map, docs, llms.txt, skills, knowledge card). No fake OpenAPI for a product API we do not host on this domain.

**Agent Skills** (discovery RFC v0.2.0) at [`/.well-known/agent-skills/index.json`](/.well-known/agent-skills/index.json), each with a `SKILL.md` and `sha256:` digest:

- `site-discovery` — how to use our discovery files (and that MCP is absent)
- `wordpress-ai-readiness` — checklist pointing at our guides and plugin docs
- `human-support` — route hard cases to [`/support/`](/support/) (no agent ticket API)

**Honest knowledge card** at [`/.well-known/agent-knowledge.json`](/.well-known/agent-knowledge.json): publisher, content policy, discovery URLs, and `protocols.mcp: null`.

**Markdown**: site brief at [`/index.md`](/index.md), plus `.md` mirrors for the AI guide cluster (for example [`/seo/ai-search-readiness-wordpress.md`](/seo/ai-search-readiness-wordpress.md)). nginx serves markdown when `Accept` includes `text/markdown`.

#### What we deliberately do not ship

| Protocol / check | Why we skip it |
|------------------|----------------|
| MCP server card | We do not run MCP on this marketing site |
| OAuth / OIDC / Auth.md | No agent-auth APIs here |
| A2A agent card | No agent-to-agent runtime |
| DNS-AID | High operational cost; robots + Link + well-known cover the practical path |
| WebMCP / commerce protocols | Not applicable to Freemius checkout on a static site |

Passing a scan by lying about endpoints teaches agents the wrong model of your product. We would rather leave those checks failing.

#### Two layers: marketing site vs WordPress plugin

| Layer | Job |
|-------|-----|
| **seoboosterpro.com** | Honest discovery for our own brand, docs, and Entity Map |
| **SEO Booster (WordPress)** | Help *your* site publish llms.txt, Pro Entity Map, optional Markdown URLs, and Link discovery signals |

If you run WordPress, start with the [AI search readiness hub](/seo/ai-search-readiness-wordpress/), then [llms.txt](/seo/llms-txt-wordpress-guide/) and [Entity Map vs other indexes](/seo/entity-map-vs-llms-txt-schema-sitemap/). Plugin docs: [llms.txt tool](/docs/tools/llms-txt/) and [Entity Map](/docs/tools/entity-map/).

#### How to verify

```bash
curl -sI https://seoboosterpro.com/ | grep -i '^link:'
curl -sI -H 'Accept: text/markdown' https://seoboosterpro.com/ | grep -i content-type
curl -s https://seoboosterpro.com/.well-known/api-catalog | head
curl -s https://seoboosterpro.com/.well-known/agent-skills/index.json | head
curl -s https://seoboosterpro.com/robots.txt | grep Content-Signal
```

Then re-run [radar.cloudflare.com/scan/agents](https://radar.cloudflare.com/scan/agents). Expect MCP and OAuth-style checks to remain failed unless you later ship those systems for real.

#### Related reading

- [AI search readiness for WordPress](/seo/ai-search-readiness-wordpress/)
- [llms.txt for WordPress](/seo/llms-txt-wordpress-guide/)
- [AI Readiness checklist](/seo/ai-readiness-checklist-wordpress/)
- [Bridge the gap: AI bots vs GSC](/seo/bridge-the-gap/)