agentability

← AI-Readiness Index

paycomonline.net

40/100   Closed by policy #728 of 1186

Audited November 9, 2026 from public surfaces only. Can AI agents discover, read, and act on paycomonline.net? Check by check:

GPTBot: blocked ClaudeBot: blocked PerplexityBot: blocked Google-Extended: blocked CCBot: blocked Claude-User: blocked ChatGPT-User: blocked Perplexity-User: blocked

CheckFindingPointsResult
A1 llms.txt for AI readers
No /llms.txt found — AI readers get no curated entry point.
0/15 fail
A2 AI crawler access policy
robots.txt blocks: GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, Claude-User, ChatGPT-User, Perplexity-User.
0/15 fail
A3 Content readable without a browser
Plain fetch of the homepage yields ~2200 words of visible text.
25/25 pass
A4 Structured data (schema.org JSON-LD)
Valid JSON-LD found on the homepage.
15/15 pass
A5 Sitemap discoverable
No sitemap found.
0/10 fail
A6 Everyday agent tasks reachable from the homepage
None of pricing, support, docs, or legal are reachable from the homepage. Link found but not confirmed: support/contact (/contact-us/), legal/privacy (/privacy/).
0/20 fail
B1 MCP server advertised
No MCP advertisement (bonus check — most sites skip this).
0/5 skip
B2 OpenAPI description published
No OpenAPI document (bonus check — only relevant for APIs).
0/5 skip
B3 UCP commerce profile published
No UCP profile (bonus check — agentic commerce, relevant to shops).
0/5 skip

What paycomonline.net would have to change

4 checks cost paycomonline.net points. Each one below is the specific remedy for what we measured, not general advice.

  1. llms.txt for AI readers0/15

    Serve a plain-text file at https://paycomonline.net/llms.txt listing the pages an agent most often needs — pricing, docs, support, account management — each as a one-line description and an absolute URL. It is read by an agent arriving cold with no idea of your structure. Fifteen points, and most teams ship it in an afternoon.

  2. AI crawler access policy0/15

    Your robots.txt currently refuses GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, Claude-User, ChatGPT-User, Perplexity-User. If that is deliberate, this score is the cost and the trade is yours to make. If it is inherited from an old rule or a security plugin — which is the commonest cause we see — those agents cannot read paycomonline.net on a user's behalf at all.

  3. Sitemap discoverable0/10

    Serve https://paycomonline.net/sitemap.xml and point to it from robots.txt. Without it an agent has to guess your URL structure from whatever the homepage happens to link.

  4. Everyday agent tasks reachable from the homepage0/20

    An agent could not reach pricing, support/contact, docs/api, legal/privacy from the paycomonline.net homepage. These are what agents are sent to find most often. Each needs a plain link an agent can follow from the homepage in one hop — not behind a menu that only appears once JavaScript runs, and not solely in a logged-in view.

  5. MCP server advertised0/5

    Optional, and rare — only a handful of the sites we track run one. An MCP server lets an agent act on paycomonline.net through a defined interface instead of scraping it. Advertise it at /.well-known/mcp/server-card.json.

  6. OpenAPI description published0/5

    Optional. If paycomonline.net has a public API, publishing an OpenAPI document at /openapi.json lets an agent call it correctly without a human reading your docs first.

How this score has moved

Down 10 points since October 7. Every audit is a fresh fetch, so a change here means something on paycomonline.net changed.

50Oct 7 50Oct 12 50Oct 14 50Oct 19 50Oct 25 50Oct 26 50Oct 30 40Nov 1 40Nov 2 40Nov 3 40Nov 9

Put this score on your site

The badge reads live from this page, so it updates itself when the score changes. Free, no attribution required beyond the link it already carries.

AI-Ready 40 out of 100 for paycomonline.net

HTML

Markdown

Work on paycomonline.net? Each failed check maps to a concrete fix in the methodology — most ship in under an hour. Scores refresh weekly; request a re-run after you deploy.