# Nykaa Keyword Rank Tracker (`ikmal_suzali_atr/nykaa-rank`) Actor

Full Nykaa (India) search results per keyword with position and sponsored (AD) flag — see where a brand ranks and who holds the paid tiles. Category-like keywords are followed through Nykaa's redirect. Dual-mode: the same code runs as an ATR BullMQ worker.

- **URL**: https://apify.com/ikmal\_suzali\_atr/nykaa-rank.md
- **Developed by:** [AtTheRate AI](https://apify.com/ikmal_suzali_atr) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Nykaa Keyword Rank Tracker

Captures the full Nykaa (India) search results slate for each keyword, with the rank of every product and the sponsored (AD) tiles marked. Use it to see where a beauty brand ranks for the terms that matter, and which competitors are paying for the slots above it.

### What you get

- One row per search result position: `keyword`, `page`, `position`, `id`, `name`, `brand`, `price`, `original_price`, `mrp`, `discount_pct` and `product_url`.
- `is_sponsored` on paid tiles, detected from Nykaa's AD tag and its paid-placement metadata, so ad share of the first screen is measurable.
- `featured` flags an editorial pin, which is not an ad and stays `is_sponsored: false`.
- `total_results` for the keyword, so share of search has a denominator.
- Ratings as `rating` and `rating_count`, stock as `in_stock`.
- Category-like keywords are followed through Nykaa's own redirect, and those rows carry `search_redirect_category`.

### Input

Give the keywords to rank. Everything else has a working default.

```json
{
  "keywords": ["kajal", "lipstick"],
  "locale": "in",
  "pages": 1,
  "concurrency": 2,
  "delayMs": 1200,
  "callsPerSession": 60,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  }
}
```

- `keywords` (required): search terms to rank. Duplicates are ignored.
- `pages`: result pages to capture per keyword. Nykaa serves 20 results a page.
- `concurrency`: keywords captured in parallel, 1 to 4.
- `delayMs` and `callsPerSession`: pacing and session rotation.
- `proxyConfiguration`: egress for the run. An Indian residential proxy is the default.

### Output

One dataset row per search result position.

```json
{
  "platform": "nykaa",
  "locale": "in",
  "keyword": "kajal",
  "page": 1,
  "position": 1,
  "id": "1234567",
  "name": "Lakme Eyeconic Kajal",
  "brand": "Lakme",
  "price": 225,
  "original_price": 250,
  "mrp": 250,
  "discount_pct": 10,
  "currency": "INR",
  "rating": 4.4,
  "rating_count": 8123,
  "in_stock": true,
  "is_sponsored": true,
  "featured": false,
  "search_redirect_category": null,
  "total_results": 812,
  "product_url": "https://www.nykaa.com/lakme-eyeconic-kajal/p/1234567",
  "captured_at": "2026-09-12T03:35:09.757Z"
}
```

`seller` is always null: Nykaa does not name a seller on listings. `search_redirect_category` is null unless the keyword was redirected to a category.

### Use cases

- Weekly share of search: your `brand` count in the top 20 against `total_results`.
- Rank tracking for a SKU across a keyword set, from `keyword` plus `position`.
- Competitor ad monitoring: which brands appear with `is_sponsored` true, and how high.
- Price-position analysis, pairing `position` with `price` and `discount_pct`.
- Availability checks on high-traffic keywords using `in_stock`.

### Notes and limits

- 20 results a page, fixed by Nykaa.
- A category-like keyword such as "lipstick" is redirected by Nykaa to a category page. The actor follows that redirect and ranks the category listing, and stamps `search_redirect_category` on those rows so the two cases stay distinguishable.
- A keyword with no matches finishes cleanly with zero rows rather than failing the run.
- `pages` is capped at 10 per keyword.
- Only the India storefront exists.
- An Indian residential proxy is needed. Other egress is answered with an access-denied page.

### FAQ

**Do I need a proxy?** Yes. An Indian residential proxy, which is the actor default.

**How many results can I get?** 20 rows a page and up to 10 pages per keyword, so up to 200 ranked positions per keyword per run.

**Does it need a login or an API key?** No. No account and no key.

**How is the sponsored flag detected?** From the AD tag on the tile and the paid-placement fields Nykaa attaches to it. Editorial pins are reported as `featured`, not as ads.

**Why do some keywords come back as a category?** Nykaa treats broad terms as navigation and redirects them. The actor follows the redirect so you still get a ranked slate, and records the category id in `search_redirect_category`.

# Actor input Schema

## `keywords` (type: `array`):

Search keywords to rank. Duplicates are ignored. Category-like terms (e.g. "lipstick") are redirected by Nykaa to a category; the actor follows the redirect and ranks that category (rows carry search\_redirect\_category).

## `locale` (type: `string`):

Which storefront / locale.

## `pages` (type: `integer`):

Result pages to capture per keyword. Leave at 0 to capture every result page; the run stops as soon as the results end.

## `concurrency` (type: `integer`):

Keywords captured in parallel (1-4).

## `delayMs` (type: `integer`):

Pause between page fetches.

## `callsPerSession` (type: `integer`):

Re-mint the session after this many page fetches.

## `proxyConfiguration` (type: `object`):

On the Apify platform this decides egress. A residential proxy in the storefront's country is recommended (IN for the default). On our own servers it is ignored and our residential proxy is used.

## Actor input object example

```json
{
  "keywords": [
    "kajal"
  ],
  "locale": "in",
  "pages": 0,
  "concurrency": 2,
  "delayMs": 1200,
  "callsPerSession": 60,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "IN"
  }
}
```

# Actor output Schema

## `results` (type: `string`):

One row per search result position.

## `summary` (type: `string`):

Counts for the run: what was requested, captured, skipped and failed.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "kajal"
    ],
    "pages": 0
};

// Run the Actor and wait for it to finish
const run = await client.actor("ikmal_suzali_atr/nykaa-rank").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": ["kajal"],
    "pages": 0,
}

# Run the Actor and wait for it to finish
run = client.actor("ikmal_suzali_atr/nykaa-rank").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "kajal"
  ],
  "pages": 0
}' |
apify call ikmal_suzali_atr/nykaa-rank --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ikmal_suzali_atr/nykaa-rank"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/lX8kquePRHF89BaX8/builds/ANWS1Fdrgn78xBfdM/openapi.json