Myntra Keyword Rank Tracker

Captures the full Myntra search results slate for each keyword, with every product's rank and the paid (PLA) tiles placed exactly where the site renders them. Use it to track share of search for a fashion brand, and to see which brands are buying the slots above it.

What you get

• One row per search result position: position, product_id, name, brand, price, mrp, in_stock and inventory.
• is_sponsored on paid tiles, with ad_campaign_id naming the campaign, or the ad source when Myntra ships an empty campaign id.
• The true rendered order. Myntra returns organic and paid products in two separate lists plus an ordering array, and the actor walks that ordering. Reading the organic list alone would understate rank by however many ad slots sit above it.
• inventory, a total unit count across sizes, so thin stock is visible.
• captured_at on every row, so a time series can be built by appending runs.
• Ranks for the whole slate, not just one brand, so competitor rank and ad share stay derivable.

Input

Give the keywords to rank. A location is required by the input schema for consistency with the quick-commerce trackers, but Myntra ships nationally and does not vary results by pincode.

{
  "keywords": ["running shoes"],
  "locations": [
    {
      "label": "Bengaluru-MGRoad",
      "lat": 12.9716,
      "lon": 77.5946,
      "pincode": "560001"
    }
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  },
  "pages": 1
}

• keywords (required): search terms to rank. Duplicates are ignored.
• pincodes: Indian 6-digit pincodes. One is enough, since extra ones would only repeat identical rows.
• locations (advanced): exact points as {"label","lat","lon","pincode"}, in place of pincodes.
• pages: result pages to walk per keyword. Myntra returns 50 products a page and rank continues across pages.
• proxyConfiguration: egress for the run. An Indian residential proxy is the default.

Output

One dataset row per search result position.

{
  "captured_at": "2026-09-11T09:02:03+00:00",
  "platform": "myntra",
  "keyword": "running shoes",
  "location_label": "national",
  "pincode": null,
  "store_id": null,
  "position": 1,
  "is_sponsored": true,
  "ad_campaign_id": "monet",
  "product_id": "9305413",
  "name": "Sparx Men Mesh Sports Non-Marking Shoes",
  "brand": "Sparx",
  "price": 1224,
  "mrp": 1499,
  "in_stock": true,
  "inventory": 120
}

A live run of one keyword returned 50 rows, 18 of them sponsored. Because Myntra is national, location_label is always "national" and pincode and store_id are null, whichever location you passed in.

Use cases

• Share of search by keyword: how many of the top 50 positions belong to your brand.
• Ad-slot share and competitor ad monitoring, from is_sponsored and ad_campaign_id at each position.
• Rank tracking for individual styles across a keyword set, following product_id over time.
• Price and MRP benchmarking at rank, plus stock depth from inventory and in_stock.

Notes and limits

• 50 products a page, and rank continues across pages rather than restarting at 1, so page 2 positions start at 51.
• Myntra does not vary results by pincode, so a location dimension would multiply cost for identical rows. Every row is stamped national instead. The schema still requires one pincode or location.
• Ad tiles arrive in a separate list from organic ones. Only the site's own ordering array reproduces the on-screen rank, which is what this actor uses.
• An Indian residential proxy is the default and is recommended.
• India only.

FAQ

Do I need a proxy? An Indian residential proxy is the actor default and is the tested configuration.

How many results can I get? 50 positions a page per keyword, walked for as many pages as pages allows while Myntra reports another page.

Does it need a login or an API key? No.

How is the sponsored flag detected? Myntra marks paid products in its own page state and publishes an ordering array saying which slot is paid. The actor walks that ordering, so an ad at rank 1 is recorded at rank 1 and organic rows are pushed down accordingly.

Why does every row say "national"? Because Myntra serves the same results everywhere. Stamping a pincode on those rows would imply a local variation that does not exist.