Apify Store Rank Tracker (Apify)

Track Actor positions in anonymous Apify Store search results. Compare keyword visibility with a saved baseline. JSON or CSV.

Размещённый MCP-сервер

npx add-mcp 'https://mcp.apify.com/?tools=monkey.d.scraping/store-visibility-monitor'

Устанавливается в Claude Code, Codex, Cursor и другие

Документация

Apify Store Rank Tracker & Visibility Monitor (monkey.d.scraping/store-visibility-monitor) Actor

Track Actor positions in anonymous Apify Store search results. Compare keyword visibility with a saved baseline and export JSON/CSV reports. Monitor up to 20 Actors across 20 queries; errors stay distinct from absence.

Pricing

from $5.00 / 1,000 observed search queries

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the API section below.

Each client library has reference documentation the quickstart does not restate: JavaScript/TypeScript (npm install apify-client) and Python (pip install apify-client).

README

Apify Store Rank Tracker & Visibility Monitor

See whether your Actors appear in the first 100 results of an anonymous Apify Store API search, and compare the observed positions with an earlier run. Track up to 20 Actors across 20 queries and export one clear observation per Actor and query to JSON or CSV.

Use it to review visibility for the search phrases your product serves. It reads search results only, so the Actors you follow are never started.

中文用户: 本页下方有完整的中文说明(Apify Store排名监控、Actor曝光追踪、SEO关键词排名)。

Who this is for

  • Actor developers: take a baseline for the phrases your Actor serves, then compare a later observation after a listing change.
  • Teams with a portfolio: observe several Actors in the same query with one search request and one query event, rather than running each tracked Actor.
  • Automation maintainers: export structured observations and distinguish an API outage from an Actor leaving the observed sample.

Start with three relevant queries and one Actor. Use the same configuration for the next comparison. Space observations more than five minutes apart (results can be cached for up to five minutes) and look for repeated patterns across several runs.

Get your first result

  1. Paste an Actor's Store link, publisher/actor name or Actor ID into Actors to follow.
  2. Enter one or more search queries. Keep the prefilled example for a small first test.
  3. Run and open Visibility report and next steps. Use Observed positions for the exportable dataset.
{
  "actorIds": ["monkey.d.scraping/telegram-keyword-search-channel-scraper"],
  "queries": ["telegram keyword search"]
}

You get an observation even when the Actor is absent from the sample. Different entries resolving to the same Actor are rejected rather than billed twice.

Compare with an earlier run

Run once without a baseline. For the next run, select that run's key-value store in Previous snapshot store and keep the same Actors, query order, sample limit and filters.

Use a completed delivery from version 0.2 or later as the baseline; the COMPLETION record shows usableAsBaseline. An incompatible baseline is rejected before any Store search starts. The earlier store is read, never overwritten.

positionsGained is positive when the observed numerical position improves, negative when it falls, and empty when positions cannot be compared. Checks less than five minutes apart can share cached results.

Read the observations correctly

StateMeaning
presentThe Actor appeared at this original API response position.
not_observedThe Actor was not in this sample of up to 100 results.
unknownThe search for this query was not completed in this run. It is kept separate from absence and rank loss.

Comparison states distinguish comparable positions, entering or leaving the sample, absence in both samples and unknown evidence.

The dataset includes the query, Actor label and ID, state, position, timestamp, sample size, filters, search surface, comparison and any failure reason. SUMMARY reports observed, failed and skipped query counts. complete=false marks a run in which some queries are unknown.

Store searches and public Actor-name resolution run anonymously: your token is never used for them.

Filters

  • One Store request per query, returning up to 100 results.
  • Category IDs use AND semantics. Publisher, pricing model and agentic eligibility filters are optional. They narrow the sample; keep them identical for comparisons.
  • Categories are normalized to lowercase, trimmed and deduplicated. Use official category IDs.

Pricing

$0.001 per Actor start + $0.005 per successfully observed query ($5 per 1,000 query events). Platform usage is included. Up to 20 tracked Actors are included in each query; there is no per-row fee.

A successful query is charged even when no tracked Actor appears in the sample. Failed and skipped queries have no query fee; the start fee still applies. One successful query costs $0.006 in total; nine cost $0.046; twenty cost $0.101. The minimum selectable run budget is $0.006.

Rows are saved before a query event is charged. Before starting the next query, the Actor checks whether another event fits the run budget. If the budget only covers part of the input, remaining queries are reported as unknown. The Pricing tab is authoritative for active rates.

Files, automations and delivery

  • REPORT.html: readable observations, query billing and the store ID for your next baseline.
  • Dataset: one observation per requested query and Actor; use JSON or CSV export.
  • SNAPSHOT: reusable configuration and observed sample.
  • COMPARISON: present when a compatible baseline was supplied.
  • SUMMARY: completeness, skipped work, safe errors and query billing counts.
  • RESULTS.csv: convenient CSV with formula prefixes neutralized. JSON retains the original text.
  • COMPLETION: written last, after the promised outputs were saved. usableAsBaseline=true is required for a later comparison.

Rows delivered before a run stops stay in the dataset, and their successful queries remain charged; use a completed run as your baseline. A repeat is a fresh run with its own budget.

You can connect the dataset to your own workflow or schedule runs yourself, and choose which snapshot to use as the baseline. A completed snapshot with some unknown queries can be compared; those queries remain unknown.

Frequently asked questions

Does this track Apify Store keyword rankings?

It tracks the observed position of selected Actors for your search queries in the anonymous Store API response, up to the first 100 results.

Can I compare my Actors with competitors?

Yes. Supply their public Actor names, links or IDs alongside yours, up to 20 distinct Actors. The monitor reads search results only; the tracked Actors are never started.

How does this help with Store SEO?

Use snapshots to observe visibility before and after listing edits, then compare positions across several runs.

Can I export keyword positions to an automation?

Yes. Use the dataset's JSON or CSV output. Preserve the query, timestamp, sample size and observation state so downstream workflows keep unknown checks separate from ranking losses.

Store API transition

The client is designed for the one-page contract announced for November 15, 2026.

Official Store API announcement

中文说明:Apify Store排名监控工具(Apify Store Rank Tracker 爬虫 / API)

Apify Store Rank Tracker & Visibility Monitor 专为Apify开发者打造:查看你的Actor在匿名Apify Store API搜索前100个结果中的位置,并与之前的运行结果对比。每次最多追踪20个Actor、20个搜索词,每个Actor和搜索词生成一条清晰的观测记录,可导出为JSON或CSV。

为什么选择这款Apify Store排名监控工具?

  • 一次搜索覆盖多个Actor:同一搜索词下最多20个Actor只算一次查询,无需逐个运行被追踪的Actor。
  • 与基准对比:选择上一次运行的存储作为基准,positionsGained 直接显示排名上升或下降了多少位。
  • 状态清晰:present 表示出现在样本中,not_observed 表示未出现在本次样本中,unknown 表示搜索失败或被跳过,API故障不会被误记为排名下降。
  • 追踪竞品:输入竞品Actor的公开名称、链接或ID,与自己的Actor放在一起比较;工具只读取搜索结果,不会运行被追踪的Actor。
  • 可选筛选:支持按类别、发布者、计费模式和是否允许AI智能体用户筛选搜索样本。
  • 多种输出:REPORT.html 可读报告、数据集、RESULTS.csv、SNAPSHOT、COMPARISON 和 SUMMARY。

适用场景

  • Store SEO优化:为Actor服务的关键词建立基准,修改标题、描述或README后再次观测,查看关键词排名变化。
  • Actor组合管理:同时观测多个Actor在同一关键词下的曝光情况。
  • 竞品对比:比较你的Actor与竞品在相同搜索词下的位置。
  • 自动化流程:将结构化观测数据接入你自己的工作流,区分API故障和Actor离开样本。

可以获取哪些数据?

每个搜索词和Actor生成一条记录,包括:搜索词、Actor名称和ID、状态、排名位置、时间戳、样本大小、筛选条件、搜索来源、与基准的对比结果以及失败原因(如有)。SUMMARY 汇总已观测、失败和跳过的查询数量。

价格

内容价格
每次运行启动0.001美元
每个成功观测的搜索词0.005美元(每1,000次5美元)
示例:1个搜索词0.006美元
示例:9个搜索词0.046美元
示例:20个搜索词0.101美元

平台用量已包含。每个搜索词最多包含20个被追踪的Actor,不按行收费。即使被追踪的Actor未出现在样本中,成功的查询也会计费;失败和跳过的查询不收取查询费用。可选的最低运行预算为0.006美元。

使用方法

  1. 在 Actors to follow(actorIds)中粘贴Actor的Store链接、publisher/actor 名称或ID。
  2. 在 queries 中输入一个或多个搜索词。
  3. 运行后打开 Visibility report and next steps 查看报告,在 Observed positions 中导出数据集。
  4. 下一次运行时,在 Previous snapshot store(baselineStoreId)中选择上一次运行的存储,并保持相同的Actor、搜索词顺序、样本数量和筛选条件。
{
  "actorIds": ["monkey.d.scraping/telegram-keyword-search-channel-scraper"],
  "queries": ["telegram keyword search"]
}

常见问题

能追踪Apify Store的关键词排名吗? 可以。工具记录所选Actor在匿名Store API搜索结果前100位中的观测位置。

能和竞品Actor对比吗? 可以。把竞品的公开Actor名称、链接或ID和你的Actor一起输入,最多20个。

能导出到自动化流程吗? 可以。使用数据集的JSON或CSV输出,并保留搜索词、时间戳、样本大小和观测状态。

多久对比一次比较合适? 建议两次观测间隔超过五分钟(结果可能有缓存),并观察多次运行中的重复趋势。

其他工具

Actor input Schema

actorIds (type: array):

One Actor per line: paste an Apify Store URL, publisher/actor name, or 17-character ID. Up to 20 Actors; none are executed.

queries (type: array):

One query per line, up to 20. Each query produces an anonymous API sample.

baselineStoreId (type: string):

Choose the key-value store of a completed run from version 0.2 or later, with the same Actors, query order, result count and filters. Leave empty for your first run.

limit (type: integer):

Results are read from a single search page per query.

categories (type: array):

Optional official Apify Store category IDs.

username (type: string):

Restricts the search sample; use the same filter in baseline and current run.

pricingModel (type: string):

Official pricingModel value, for example PAY_PER_EVENT.

allowsAgenticUsers (type: boolean):

Unset means no filter. Filters Actors by agentic payment eligibility.

Actor input object example

{
  "actorIds": [
    "monkey.d.scraping/telegram-keyword-search-channel-scraper"
  ],
  "queries": [
    "telegram keyword search"
  ],
  "limit": 100,
  "categories": []
}

Actor output Schema

report (type: string):

No description

results (type: string):

No description

csv (type: string):

No description

snapshot (type: string):

No description

summary (type: string):

No description

completion (type: string):

No description

API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

JavaScript example

import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "actorIds": [
        "monkey.d.scraping/telegram-keyword-search-channel-scraper"
    ],
    "queries": [
        "telegram keyword search"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("monkey.d.scraping/store-visibility-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

Python example

from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "actorIds": ["monkey.d.scraping/telegram-keyword-search-channel-scraper"],
    "queries": ["telegram keyword search"],
}

# Run the Actor and wait for it to finish
run = client.actor("monkey.d.scraping/store-visibility-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

CLI example

echo '{
  "actorIds": [
    "monkey.d.scraping/telegram-keyword-search-channel-scraper"
  ],
  "queries": [
    "telegram keyword search"
  ]
}' |
apify call monkey.d.scraping/store-visibility-monitor --silent --output-dataset

MCP server setup

{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,monkey.d.scraping/store-visibility-monitor"
        }
    }
}

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an Authorization: Bearer <APIFY_API_TOKEN> header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Gca5mkdAKseFeXYBP/builds/Cr1QvBgepVKqM5cgM/openapi.json