Page Search-Readiness Check

What it does

Page Search-Readiness Check reads ONE public page and says, in plain words, what stops search engines from finding, reading or listing it. Ten rows, each pass, fix or unknown, with what we saw and what to change: title, description, headings, canonical address, noindex signals, robots.txt, sitemap, structured data, image alt text and page weight (the HTML document). Three fetches at most (the page, robots.txt, one sitemap), no crawling, no scripts run. Every answer is dated and signed with our key, so you can keep it as proof, and anyone can check it at the stamp page. No model, nothing stored.

Who it is for

Agents and people who publish a page and want a quick, checkable read on whether search engines can find and list it, before a launch, after a site change or when a page is not showing up.

Price

Free, no sign-up: 100 checks a day per address. Paid calls are not offered.

Limits

One page per call; no lists, no site crawl. Public http(s) pages, ports 80 and 443. Pages built by scripts after loading look empty because we do not run scripts. robots.txt is judged for all crawlers and two named ones; AI-crawler rules are not. A sitemap index is not opened. Page weight is the HTML only. The rules are ours and plain (title 10 to 70 characters, description 50 to 170, one h1, HTML under 250,000 bytes); they say what the page showed, not how any search engine will rank it. At most 30 checks of one site an hour for everyone.

How to get one

Ask your own agent: it sends the page address and gets back ten rows (pass, fix or unknown, with what was seen and what to change) and a signed note. Keep the note: it shows what the page showed that day.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"page_search_ready","arguments":{"url":"https://example.com/"}}}
-> overall (needs_work / ready_on_these_checks / no_problems_found_some_unknown), ten checks (status, summary, what we saw, what to do), signed observation, receipt, stamp link

For agents

Tool page_search_ready on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:trddhgs7y4ve4ixymi324xdpcu): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): HPkgJNsZNmvfbIN4Vm2FDpjL7rgEBjAMeKSxH8x0R6k=

For agents that look for a page check (road: Search for agents, agent-search), reached through the Campus gateway: MCP, Agent2Agent and REST. One signed, checkable answer per call; keep the signed observation with your work. How a stamp is checked: https://llpro.ai/stamp

Next

• Connect your agent: Use this and the other LLPRO tools from your own agent.
• Get your agent: No agent yet? Get one that asks first.
• Hand the whole job to the Hub: One page is one part. Tell the Hub the job (a site that does not show up in search); it routes you to the right checks.

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card