Mangools Alternative — KWFinder, SERPChecker & LinkMiner

Freelance SEOs and AI agents get Mangools-style dataset records from a seed keyword or domain: KWFinder metrics, related keywords, SERPChecker results, SiteProfiler domain stats, and LinkMiner backlinks. Built for structured keyword and SERP research on Apify with API, schedule, and MCP access. Owner credentials are already configured for Store runs.

Best fit for this Actor

• Score a seed phrase with search volume, CPC, competition, and keyword difficulty.
• Expand that seed into related keywords, then inspect the live SERP with SERPChecker.
• Pull a SiteProfiler-style domain row or a LinkMiner backlink list for the same research pass.

When you already have a finished keyword list and only need volume plus CPC, start with Keyword Search Volume API. For Semrush-style ranked keywords a domain already ranks for, continue with SEMRush Alternative. After you pick phrases to watch over time, continue with Keyword Rank Tracker.

Practical scenario

An SEO freelancer pastes seo tools, keeps mode on kwfinder, and runs the Actor. The dataset returns one row with searchVolume, cpcUsd, keywordDifficulty, and searchIntent. They then switch mode to serp_checker with maxResults 5 to see who ranks and which SERP features appear before writing the brief. Unknown or empty matches finish SUCCEEDED with VALID_EMPTY and no seo-record charge.

Quick start input

{
  "mode": "kwfinder",
  "keywords": ["seo tools"],
  "locationName": "United States",
  "languageCode": "en",
  "maxResults": 5
}

Keyword modes use keywords. SiteProfiler and LinkMiner use target instead.

Input reference

Field	Type	What it controls
mode	enum	kwfinder, related_keywords, serp_checker, site_profiler, link_miner, or serp_competitors. Default kwfinder.
keywords	array	Seed phrases for KWFinder, related keywords, SERPChecker, and SERP competitors. Example: ["seo tools"].
target	string	Domain or URL for SiteProfiler and LinkMiner. Example: mangools.com.
locationName	string	Country name, or city,region,country for SERPChecker. Default United States.
languageCode	string	Language code such as en. Default en.
device	enum	desktop or mobile for SERPChecker. Default desktop.
maxResults	integer	Row cap 1–100. Default 5. SiteProfiler still writes at most one row.

Owner API credentials are already configured for Store runs. This Actor does not accept user API keys.

What data you receive

One dataset item is one keyword, SERP item, domain, competitor, or backlink row.

{
  "mode": "kwfinder",
  "keyword": "seo tools",
  "locationName": "United States",
  "languageCode": "en",
  "searchVolume": 5400,
  "cpcUsd": 6.1,
  "keywordDifficulty": 42,
  "searchIntent": "commercial",
  "source": "mangools_alternative/kwfinder",
  "status": "OK",
  "fetchedAt": "2026-08-22T00:00:00.000Z"
}

Field	Meaning
searchVolume / cpcUsd	Monthly search volume estimate and paid CPC
keywordDifficulty	Upstream difficulty score, not Mangools KWFinder KD
serpItemType	SERPChecker item type such as organic or people_also_ask
rankScore	Upstream SEO rank score, not a Mangools Citation Flow value
source	Mode provenance label for the row

OUTPUT and RUN_SUMMARY in the default key-value store hold outcome, itemsPushed, chargedEventCounts, and providerCostUsd. Download the dataset as JSON, CSV, Excel, or HTML.

Use through the API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~mangools-alternative/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"kwfinder","keywords":["seo tools"],"maxResults":5}'

Use with AI agents through Apify MCP

Run a KWFinder-style keyword overview for "seo tools" in the United States. Return searchVolume, cpcUsd, keywordDifficulty, searchIntent, source, and fetchedAt. Read OUTPUT.outcome and itemsPushed. Treat keywordDifficulty as an independent upstream score.

Connect via https://mcp.apify.com. Cost signal: about $0.05 per successful SEO API request plus $0.01 per saved row.

Connect the workflow

• When you already have phrases and only need volume plus CPC, then use Keyword Search Volume API.
• For Semrush-style organic keywords a competitor domain ranks for, continue with SEMRush Alternative.
• After you choose phrases to monitor, continue with Keyword Rank Tracker.
• For broader Google SERP capture after SERPChecker, continue with Google SERP All-in-One Scraper.

Pricing

This Actor uses Pay per event plus Apify platform usage. The live Pricing tab is the current source of truth for billing details.

• apify-actor-start: $0.00005 per run
• seo-api-request: $0.05 per successful upstream SEO API task
• seo-record: $0.012 per persisted row

A KWFinder prefill is one API task plus one row. Empty matches have no seo-record charge. Provider cost is recorded in RUN_SUMMARY.providerCostUsd.

How it works

1. Normalize the keyword list or domain for the selected mode.
2. Call the matching upstream SEO API endpoint for that mode.
3. Charge seo-api-request after each successful task.
4. Charge seo-record, then write each validated dataset row.

Best results

• Use a real seed such as seo tools rather than a Mangools app URL.
• Keep maxResults at 5 while you confirm the output shape, then raise it for exports.
• Treat volume, difficulty, and rank as model estimates for public keywords and domains you are authorized to research.
• A valid query with no match finishes SUCCEEDED with VALID_EMPTY.
• This Actor is a one-shot report. Historical rank watching belongs on Keyword Rank Tracker, not here.

Builder's note

I found that Mangools Store matches were either unrelated or a historical-backlink checker that still needed Mangools-shaped data. Routing this SKU through owner-managed upstream SEO APIs keeps the KWFinder / SERPChecker / SiteProfiler / LinkMiner jobs without claiming Mangools KD, scraping mangools.com, or asking buyers for API keys. SERPChecker is the mode that the Semrush-named sibling does not advertise.

Legal and responsible use

Use this Actor with public SEO research you are authorized to run. Metrics are independent of Mangools s.r.o. Follow applicable law and the upstream data provider terms, and keep the output in your own compliance workflow.

Issues and feature requests: use the Actor Issues tab on Apify.