# Ranking signals (`clickd_signals`)

Updated November 12, 2026.

## What does clickd_signals do?

Evaluates a scanned site or one live page against the ranking and AI corroboration signals your HTML, links and URL sections control: retrieval readiness, salient term and anchor alignment, page-role trust checks (including YMYL), section-level sitechunk health, originality, and source grounding. Any key may make this call, on any public site.

Listed at /mcp/all only. Its name answers a call at either address.

Who may call it: Any key, or over MCP no key, 60 calls an hour from one address.

## When to use it

- You want to see whether a weak URL folder (/locations, /blog) is dragging down section quality.
- You want to verify that YMYL, guide, or commercial pages satisfy their role-specific trust and corroboration checks.

## What you ask

You might say: “Check the ranking signals and section health on example.com.”

```
clickd_signals({})
```

| Argument | Type | Needed | What it is |
| --- | --- | --- | --- |
| `url` | Text | No | One live public address to evaluate on the spot, such as https://example.com/guides/a-page. |
| `site` | Text | No | A scanned domain, such as example.com, to inspect sitechunk health, page roles and priority signal fixes across its latest read. |
| `section` | Text | No | Only pages under this URL prefix on a site read, such as /guides or /locations. |
| `role` | One of these: home, ymyl, guide, commercial, experience, reference, other | No | Only pages classified in this Orbit role on a site read. |
| `limit` | Number | No | How many to return. |
| `offset` | Number | No | How many to skip, for the next part of a long list. |

## What comes back

- Site-wide signal readiness shares, URL-prefix sitechunk health, and priority fixes sorted by page count.
- Per-page Orbit role, salient terms (quoted), and pass/fail checks mapped to clickd rules.

A sample, with made-up sites and figures:

| Section | Pages | Health | Role fit |
| --- | --- | --- | --- |
| /guides | 18 | Strong | 89% |
| /services | 9 | Mixed | 67% |
| /locations | 24 | Weak | 29% |

## Over HTTP

```
curl "https://clickd.com/api/v1/check/signals" \
  -H "Authorization: Bearer $CLICKD_KEY"
```

## When it fails

| When | Status | What to do |
| --- | --- | --- |
| Your assistant has no key and has made 60 calls this hour | isError over MCP | Wait the minutes it says, or sign up with `clickd_signup` and connect again with the key it gives. |
| The key has used this hour’s free checks | 429 | The answer says signal checks are limited to an hourly allowance. Try again within the hour. |

## Sources

- [Model Context Protocol: tools](https://modelcontextprotocol.io/specification/2025-06-18/server/tools), Model Context Protocol: How an assistant calls a tool.

The call in full: [clickd_signals in the API reference](https://clickd.com/docs/reference#clickd_signals).

## Goes with

- [Brief](https://clickd.com/docs/tools/brief.md)
- [Signs of generated text](https://clickd.com/docs/tools/tells.md)
- [What an agent reads](https://clickd.com/docs/tools/agent-view.md)