Skip to content

Track Naver SERP Ads With One HTTP Request

Naver SERP ad placements change fast, and the page is JavaScript-heavy.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains what a managed Naver ad results API returns, which request parameters matter, and how to decide whether it fits your rank-tracking or creative-monitoring pipeline. It is a product overview, not a live test report.

What the Naver Ad Results API returns

You pass a Naver SERP URL that contains ad placements. The service renders the page in a headless browser, rotates proxies, and returns parsed ad data. The fields the page describes are: ad headline, display URL, sponsored copy, slot position, and landing destination. That set supports three common jobs — spotting trending topics, comparing creatives across advertisers, and building a library of ad examples.

If you only need raw HTML, a plain fetch is cheaper. The value here is the rendered, parsed result plus the proxy and anti-bot handling you would otherwise build and maintain.

Request inputs that change the result

The request is a GET with your API key and the target Naver SERP URL. Four parameters do most of the work when the default response is not enough:

  • render_js=true — runs the page in a real headless browser and returns post-render HTML. Use this when ad slots are injected by JavaScript.
  • stealth_proxy — enable when a target reacts aggressively to normal traffic.
  • country_code — routes the request through a residential IP in that country. Useful when Naver content varies by geography.
  • ai_extract_rules — natural-language extraction rules for pulling structured data without writing selectors.

Screenshots and CSS/XPath extraction rules are also available for capturing the full page or targeting exact elements.

Field map: what each returned value is for

A quick map from returned field to practical use:

  • Ad headline — the visible title of the sponsored result. Compare phrasing across advertisers for the same query.
  • Display URL — the URL shown to the user. Useful for spotting which domains bid on which queries.
  • Sponsored copy — the body text of the ad. Track messaging changes over time.
  • Slot position — where the ad appeared on the SERP. Use it for rank tracking rather than assuming a fixed order.
  • Landing destination — the final URL the ad points to. Pair with display URL to see redirects or landing-page swaps.

Treat position as a snapshot per request. Naver can reorder or rotate ads between calls, so compare like-for-like timestamps rather than assuming a stable ranking.

Distinguish the three common failure modes

Not every empty or partial result means the same thing. Separate them before changing parameters:

  • Blocked or challenged — you get a CAPTCHA page, a 403, or a bot-check interstitial. Try stealth_proxy, and slow the cadence if the target throttles aggressive patterns.
  • JavaScript not rendered — the response looks like a shell with no ad slots. Set render_js=true so the page executes server-side before extraction.
  • Geo mismatch — the page loads but the ads differ from what you expect for a market. Set country_code to route through a residential IP in the target country.

If none of these fit, check whether the URL you passed actually contains ad placements; a SERP without ads will return no ad fields by design.

Worked credit-cost example

Credit cost is built from a base charge plus feature surcharges, not a single flat rate. Using the supplied per-request rules:

  • Every request starts at 1 credit.
  • Enabling JS rendering adds 5 credits per successful request.
  • Enabling premium proxies adds 10 credits without JS rendering, or 25 credits with JS rendering.

These are the stated per-request figures. A rendered request without premium proxies is charged at 5 credits per successful request; a request with premium proxies is charged at 10 credits when rendering is off, or 25 credits when rendering is on. The base request starts at 1 credit. Whether the feature figures stack on top of the base credit or replace it is a billing detail to confirm with the operator before sizing a plan.

Using the stated rendered-request figure, tracking 1,000 Naver SERP URLs per day with rendering and no premium proxies is 5,000 credits per day before any retries. Credits are valid for one month and do not roll over, so size the plan against your monthly request volume rather than a single day's peak.

Decision checklist before you build

Use this to decide whether the managed API fits, or whether you should keep a self-hosted stack:

  1. Do your target Naver SERPs inject ad slots via JavaScript? If yes, you need rendering; a plain HTTP fetch will miss them.
  2. Do you need per-country ad views? If yes, plan for country_code and residential routing.
  3. How many URLs per day, and how many retries per URL? Multiply by the per-request credit cost above to size the plan.
  4. Do you need screenshots or CSS/XPath extraction in the same call, or is parsed JSON enough?
  5. Do you need a no-code path? The dashboard request builder can generate a snippet in Python, Node, Go, PHP, Ruby, or cURL.
  6. Do you need team-level quota control? That is a plan-level feature, not a per-request parameter.

If most answers point to rendering plus geo routing at volume, a managed API removes the proxy and browser maintenance. If you only need occasional raw HTML, a lighter approach may be enough.

Pricing and commercial terms

Plan prices, credit allowances, concurrency limits, trial credits, and support commitments are commercial terms that should be verified against the current offer before you commit to a plan. The plan table in the accompanying pricing module is a dated reference; treat those figures as historical rather than as current offers on this page. Until verified terms are published, use the following worksheet to collect what you need from the operator or from your own billing records, and leave any line blank rather than guessing a number.

Data handling and compliance

The service states that it does not collect or store personal data from scraped sites unless the user explicitly requests it, and that it handles proxy rotation and headless rendering to reduce blocking risk. Compliance obligations for the data you collect — including Naver's terms and applicable privacy law — remain with you as the operator of the pipeline. Confirm the current data-processing terms with the operator before relying on them.

Plan reference (dated captured evidence — verify current terms)
PlanMonthly priceAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100Not includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

All prices are exclusive of VAT. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots/extraction rules are included on every plan. Figures are a dated reference and must be confirmed with the operator before publication.

Per-request credit cost by feature
FeatureCredit cost per successful request
Base request1
JS rendering enabled5
Premium proxies, JS rendering disabled10
Premium proxies, JS rendering enabled25

Credits are valid for one month and do not roll over. These are the stated per-request figures: a base request starts at 1 credit, JS rendering is 5 credits per successful request, and premium proxies are 10 credits without rendering or 25 credits with rendering. Whether feature figures stack on the base credit or replace it is a billing detail to confirm with the operator.

Frequently asked questions

How do I start scraping Naver ad results?

Create an account to get an API key, then send a GET request with the target Naver SERP URL. The service renders the page, rotates proxies, and returns the parsed data. A free credit allowance is available for testing; confirm the current amount with the operator.

Will I get blocked when scraping Naver ad results?

The service rotates residential proxies and uses a real headless browser so requests resemble normal traffic. If a target reacts aggressively, enable stealth_proxy on the request. No service can guarantee zero blocks; treat blocking as a parameter-tuning problem first.

Can I scrape Naver ad results without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby, or cURL. You still need somewhere to run the snippet, or a no-code automation tool such as n8n.

How do I handle JavaScript when scraping Naver ad results?

Pass render_js=true. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML. Without this, ad slots injected by JavaScript may be missing from the response.

Can I scrape Naver ad results from a specific country?

Yes. Pass country_code to route the request through a residential IP in that country. This matters when Naver serves different ad content by geography.

What's the rate limit for scraping Naver ad results?

Limits are expressed as concurrency per plan, not as a per-target rate limit. If a target throttles aggressive patterns, space out requests or use multiple sessions. Check your plan's concurrency figure before sizing a batch job.

Which ad fields come back in the response?

The page describes ad headline, display URL, sponsored copy, slot position, and landing destination. Position is a per-request snapshot, so compare results captured at the same time rather than assuming a stable order.

Why did I get no ad results for a Naver SERP?

Check three things in order: whether the URL actually contains ad placements, whether render_js is enabled for JavaScript-injected slots, and whether country_code matches the market you expect. A SERP without ads returns no ad fields by design.