Meesho Keyword Rank Tracker

Tracks where any catalog ranks for a keyword on Meesho and which competitors hold the paid slots above it. Every result position comes back in order with price, MRP, discount, rating, review counts and an ad flag, 50 a page, so you can measure organic and paid share of search on India's largest value-fashion marketplace.

What you get

• True ranking order: keyword, page and position, counted continuously across pages.
• An ad flag on every row: is_sponsored, taken from Meesho's own paid-listing marker.
• Price economics at the result: price, original_price, discount_percent and discount_text.
• Social proof that drives clicks: rating, rating_count and review_count, plus the mall_verified and assured trust badges.
• Landed-cost detail in shipping_charges, num_designs for catalog depth, and total_results for how contested a keyword is.

Input

keywords is required. There is no location input: Meesho ranks nationally.

{
  "keywords": ["kurti", "cotton saree"],
  "pages": 1,
  "concurrency": 2,
  "delayMs": 1000,
  "callsPerSession": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  }
}

• keywords: the search terms to rank. Duplicates are ignored.
• pages: result pages per keyword, 1 to 10, at 50 results each. concurrency runs 1 to 4 keywords in parallel.
• proxyConfiguration: residential country IN is the default and is mandatory in practice.

Output

One row per result position. A verified run over two keywords at one page returned 50 rows, one keyword having matched nothing.

{
  "keyword": "kurti",
  "page": 1,
  "position": 1,
  "is_sponsored": false,
  "id": "123456789",
  "name": "Aagam Petite Cotton Kurtis",
  "brand": null,
  "price": 349,
  "original_price": 999,
  "discount_percent": 65,
  "discount_text": "65% off",
  "rating": 3.9,
  "rating_count": 1204,
  "review_count": 187,
  "in_stock": true,
  "assured": true,
  "shipping_charges": 0,
  "total_results": 8421,
  "product_url": "https://www.meesho.com/aagam-petite-cotton-kurtis/p/123456789",
  "captured_at": "2026-09-12T11:09:33.210Z"
}

brand and seller are always null: Meesho search results carry no brand or seller field, because most catalogs are unbranded supplier listings. original_price is null without a discount.

Use cases

• Share of search: count how many of the top 50 positions your catalogs hold per keyword, daily.
• Paid share of voice from is_sponsored, and competitor pricing at rank: read price and discount_percent against position to see what wins the top of the page.
• Badge impact analysis by comparing assured and mall_verified rates in the top 10 against the rest.
• Keyword contestedness from total_results and how fast rank decays between pages.

Notes and limits

• An Indian proxy is mandatory. Meesho refuses non-Indian egress at the edge and the run fails fast saying so.
• 50 results per page and a cap of 10 pages per keyword, so 500 ranked positions each.
• A keyword that matches nothing returns zero rows. Meesho never returns an empty search: it serves a fallback feed of random catalogs and reports the whole corpus as the result count. That is detected and suppressed, with a warning naming the keyword, so you never get noise dressed up as rankings.
• Pages are walked in order because each needs the cursor from the one before. Sessions re-mint after 100 fetches.
• Sponsored density varies by keyword. Two verified captures returned no sponsored rows at all, so do not assume every query has paid slots.

FAQ

Do I need a proxy? Yes, and it must be Indian. Residential country IN is the default. Without it the run stops immediately with the reason.

How many results can I get? Up to 10 pages of 50 results per keyword, so 500 ranked positions, with no limit on how many keywords you submit.

Does it need login or an API key? No Meesho account, cookie or key is required.

How do I know a zero-row keyword is genuinely unmatched? The run logs a warning naming the keyword and marks the capture empty. That happens only when Meesho reports a result count far above its real cap, which is its own signature for a no-match query.