Search Visibility Analyzer — SISTRIX Alternative

Measure Google search visibility for a domain and keywords you supply. Export observed ranks, transparent sample-based visibility scores, source URLs, and optional comparison-domain results. For SEO analysts, the dataset combines observed keyword ranks with a visibility summary calculated for the supplied keyword sample.

Workflow: put the results to work

Use a keyword list that reflects the market you want to measure. Compare the target domain and optional comparison domains under the same search settings. The aggregate score describes this supplied sample and is distinct from the proprietary SISTRIX Visibility Index.

What you get

• One validated dataset observation for each successfully processed keyword.
• The target domain's current organic rank within the requested Google depth, or a valid zero-score observation when it is not found.
• A transparent visibilityPoints score: 100 / observed organic rank; the run-level visibilityScore is the average across your supplied keyword sample.
• A source results URL, timestamp, country, language, device, provider run ID, and optional ranks for up to three comparison domains.
• Stable OUTPUT, RUN_SUMMARY, and STATE records for automation and polling.

The score is deliberately transparent and comparable only when you use the same keyword list, locale, device, and depth. It does not recreate or estimate the proprietary SISTRIX Visibility Index.

How this workflow compares with SISTRIX

Capability	This Actor	SISTRIX suite
Input	Your domain and up to 20 supplied keywords	A proprietary SEO data platform and broader product suite
Visibility measure	Explicit average of 100 / current observed rank	Proprietary Visibility Index methodology and keyword corpus
Time coverage	One current run	Historic product data and trend tooling
Output	Source-linked JSON rows and compact key-value summaries	Hosted dashboards, reports, and product workflows
Billing and cost model	Bounded Pay per event report plus Apify platform usage	Subscription suite
Effective efficiency	A completed call yields an exportable dataset and compact run summary	Broader suite workflows are selected for ongoing workspace needs
Integration and automation	Apify API, schedules, and Actor chaining can consume the records	Suite integrations and automation depend on the selected SISTRIX plan

Workflow: from keyword list to visibility decision

An agency starts with a target domain, a focused keyword sample, locale, device, depth, and optional competitors. The Actor then requests the same current Google result pages for every supplied keyword, persists one evidence row per successful observation, and calculates the transparent aggregate. Next, the team reads OUTPUT.visibilitySnapshot for the decision, opens the Dataset for source URLs and ranks, and can export the result or schedule a like-for-like repeat with the same input.

Input

{
  "targetDomain": "apify.com",
  "keywords": [
    "apify",
    "web scraping platform",
    "data extraction tools"
  ],
  "countryCode": "us",
  "languageCode": "en",
  "device": "desktop",
  "depth": 20,
  "compareDomains": ["semrush.com", "ahrefs.com"]
}

targetDomain accepts a domain or URL and is normalized to a hostname. keywords accepts 1–20 phrases; blank and duplicate items are removed. depth is 10, 20, 50, or 100. compareDomains is optional and accepts up to three domains.

No third-party API key or subscription is required. The Actor invokes Apify's Google Search Results Scraper and passes through underlying Apify platform usage.

Output and outcomes

The Dataset contains keyword_visibility_observation records. Each record includes targetRank, visibilityPoints, sampleVisibilitySharePercent, comparisonDomains, checkUrl, observedAt, and providerRunId.

The OUTPUT key contains the aggregate snapshot:

{
  "outcome": "COMPLETE",
  "visibilitySnapshot": {
    "targetDomain": "apify.com",
    "keywordCount": 3,
    "keywordsRanked": 2,
    "visibilityScore": 52.78,
    "averageRank": 3.5
  }
}

Terminal outcomes are:

• COMPLETE — every selected keyword produced a valid observation and at least one ranked result was found.
• VALID_EMPTY — valid observations were persisted, but the target was not found at the requested depth.
• PARTIAL — some requested observations could not be persisted; inspect RUN_SUMMARY.
• INVALID_INPUT — the request was accepted but did not meet semantic validation; correct the provided values.
• UPSTREAM_FAILED or CONFIG_ERROR — no usable report could be completed; retry later and inspect RUN_SUMMARY.

Programmatic use

Start a run with the Actor API using the input above, then read the default Dataset and the OUTPUT key.

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~sistrix-alternative/runs?waitForFinish=300" \
  -H "Authorization: Bearer <YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  --data '{
    "targetDomain": "apify.com",
    "keywords": ["apify", "web scraping platform"],
    "countryCode": "us",
    "languageCode": "en",
    "device": "desktop",
    "depth": 20
  }'

For an agent or MCP workflow:

Create a US desktop visibility snapshot for apify.com using the supplied keywords. After completion, read OUTPUT for the terminal outcome and aggregate, then read the Dataset for per-keyword rank evidence, source URLs, timestamps, provenance, and any partial-run warning.

Builder's note

I built this around one source-linked observation per supplied keyword because a caller can inspect exactly what changed between two comparable runs. The transparent 100 / rank rule keeps the result useful for a focused workflow while leaving proprietary suite metrics and broader SEO research in their proper context.

Responsible use and best results

This Actor requests public Google result pages through Apify's maintained provider. Submit only public, non-sensitive search terms and domains, use the data lawfully, respect applicable search-engine terms and rate limits, and operate only on sources you are authorized to access. Search results change frequently, so use the same inputs when comparing reports and treat every score as evidence for its recorded run only.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
keyword-visibility-observation	Keyword visibility observation	Charged only after one complete source-linked keyword visibility observation is persisted. Underlying Google-search and Apify platform usage are additional.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.

Independent alternative

This Actor provides the specific workflow described above. It is not affiliated with or endorsed by SISTRIX; the named product and its trademarks belong to their respective owners.

Connect an AI agent

Use the Apify MCP configurator to choose an available client connection. Inspect this Actor’s current input schema and required credentials before running it.