Bing Rank Tracker

Track where one website ranks in Bing organic results for a bounded keyword list. The actor returns one decision-ready dataset row per keyword with the matched position, ranking URL, localized market, and optional top organic competitor context.

Use it when

• You need a dated Bing position check for a domain.
• You need repeatable checks for US, UK, German, or other localized markets.
• You want a compact row per keyword for an SEO dashboard, scheduled task, or AI agent.

Pair this actor with Bing Search Scraper when a workflow needs the full SERP, ads, related searches, or Copilot blocks alongside a target-domain rank row. Google, Yahoo, Bing Maps, backlink, search-volume, and historical trend workflows belong to their respective measurement tools; schedule repeated runs and compare these rows to create a dated history.

Output

Field	Meaning
keyword	Exact Bing query checked
position	1-based organic position, or null when not found within depthChecked
found / checkStatus	Whether Bing returned a match or a valid not_found result
rankingUrl, rankingTitle, rankingSnippet	The matched Bing result
topCompetitors	Optional top organic results for context
market, depthChecked, checkedAt	Localization, coverage boundary, and freshness

Example row

{
  "runId": "abc123XYZ",
  "keyword": "web scraping",
  "targetDomain": "example.com",
  "position": 4,
  "found": true,
  "rankingUrl": "https://example.com/guide",
  "rankingTitle": "Web scraping guide",
  "rankingSnippet": "A practical guide to web scraping.",
  "topCompetitors": [
    { "position": 1, "domain": "competitor.com", "title": "Competitor guide", "url": "https://competitor.com/guide" }
  ],
  "market": "en-US",
  "safeSearch": "moderate",
  "depthChecked": 20,
  "source": "bing-direct",
  "checkStatus": "ranked",
  "checkedAt": "2026-08-09T12:00:00.000Z"
}

Input

{
  "targetDomain": "example.com",
  "keywords": ["web scraping", "Bing rank tracker"],
  "country": "US",
  "language": "en",
  "depth": 20,
  "includeCompetitors": true
}

targetDomain and keywords are required. depth accepts 10, 20, 50, or 100. Subdomains count by default; set includeSubdomains to false for exact-host matching. Keywords without a match are persisted as successful not_found rows, keeping absence within the selected market and depth visible.

Pricing

Event	Bronze price	Billing unit
Actor start	$0.00005	One valid run, scaled by memory
Bing rank check	$0.008	One persisted keyword row

The actor uses Pay per event + usage. A 10-keyword run has a defined event-charge ceiling of about $0.08005; Apify platform compute and residential proxy usage are passed through separately. The live Pricing tab is the current source of truth for effective event prices and platform usage settings. A rank event is charged only alongside a validated persisted row.

API and agent use

curl -X POST 'https://api.apify.com/v2/acts/khadinakbar~bing-rank-tracker/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"targetDomain":"example.com","keywords":["web scraping"],"depth":20}'

MCP and AI-agent prompt card

Use Bing Rank Tracker for a read-only, localized organic-rank check: check example.com in Bing US for web scraping and Bing rank tracker at depth 20. Return each keyword, position, rankingUrl, checkStatus, market, and checkedAt. Read OUTPUT for the terminal outcome and the default dataset for the persisted rows; use source: "bing-direct", market, depth, and timestamp as provenance. This tool covers Bing organic results, not ads, Bing Maps, Google, or historical rankings. Each persisted keyword row is one billable rank-check event; keep the keyword list bounded and use the live Pricing tab for current event and platform-usage costs.

For agent readback, COMPLETE means every normalized keyword produced one row; PARTIAL keeps useful rows while identifying the affected keyword in RUN_SUMMARY; not_found is a successful bounded observation rather than a missing dataset row. The actor does not paginate a single row: increase depth to inspect more Bing positions, or schedule repeat runs and compare the timestamped rows for a history.

Practical guidance

• Bing results vary by market, language, device, personalization, and time. Keep these settings consistent across scheduled runs when building a comparison series.
• Residential Apify Proxy is used by default for a consistent search route. When Bing returns a challenge, the terminal summary identifies the affected keyword and preserves any useful rows already collected.
• Maximum input is 100 unique keywords and depth is capped at 100 organic positions.
• Output rows preserve null for unavailable rank fields and include source: "bing-direct" for provenance. Start with depth 10 or 20 for routine monitoring and reserve depth 50 or 100 for keywords where page-two visibility matters.

Builder's note

I designed the output around the decision a rank-tracking workflow actually needs: one keyword row with a position, target URL, market, and timestamp. Keeping a valid no-match as a persisted row makes scheduled reports easier to join, while coupling the billable event to that validated row keeps the cost boundary legible to both humans and agents.

Legal and compliance

Use this actor for search data you are permitted to collect. Respect applicable law, Bing terms, robots and rate limits, and the rights of destination websites. Keep the workflow focused on website visibility and content research rather than decisions about people.

Related workflow

Use the full Bing Search Scraper upstream when you need raw SERP evidence, then feed the resulting keyword/URL findings into this actor for a bounded domain check. For AI answer visibility rather than web search positions, use the separate AI rank-tracking workflow only when you need AI-platform evidence.