# Click Decay

> These figures are automated measurements with timestamps. They are not a review, rating, grade, or recommendation.

CTR change, click decomposition and known Search Console data anomalies for numbers you provide.

- Status: Up
- Checks passed: 14 of 22
- Uptime: Not measured
- Latency: 82 ms
- Tools: 4
- Last probe: 2026-11-12T23:23:12.358Z
- Publisher: clickdecay.com (https://mcpheartbeat.com/p/com.clickdecay)
- Endpoint: https://clickdecay.com/mcp
- Transport: streamable-http

## Tools

Showing 4.

- **check_gsc_reporting_issues**: Lists the known Google Search Console reporting issues, taken from Google's own notices, that overlap the dates you give, with the affected metrics, the sources
- **compare_ctr_periods**: Compares clicks, impressions and CTR of two equal-length, non-overlapping periods whose totals you provide, for example from Google Search Console. It splits th
- **impressions_needed_for_clicks**: Calculates how many impressions a click target needs at a CTR you choose (clicks ÷ CTR). Use it to size a goal; project_clicks_at_ctr goes the other way. The re
- **project_clicks_at_ctr**: Calculates the clicks a number of impressions would earn at a CTR you choose (impressions × CTR). Use it for a what-if on one period; compare_ctr_periods is for

## Links

- HTML: https://mcpheartbeat.com/s/com.clickdecay/mcp-server
- Markdown: https://mcpheartbeat.com/s/com.clickdecay/mcp-server.md
- MCP: https://mcpheartbeat.com/mcp
- API: https://mcpheartbeat.com/api/v1/servers
- Tools API: https://mcpheartbeat.com/api/v1/tools
- Server API: https://mcpheartbeat.com/api/v1/health?server=com.clickdecay%2Fmcp-server