Naver Knowledge iN Scraper

This Actor extracts fields visible in Naver Knowledge iN search result cards from the public where=kin search page. It uses the current [data-template-id="kinItem"] card structure and the title, question, answer, profile, and profile subtext elements observed in Chrome.

Input

• query (required): the search phrase.
• maxItems (optional): maximum records to push, from 1 to 500; defaults to 50.
• proxyConfiguration (optional): Apify proxy settings.

Output fields

The Actor keeps the displayed answer preview separate from the question text. Optional fields are omitted when the page does not expose them.

Field	Meaning
position	One-based result position in this run.
title	Visible question title.
link	Question detail URL linked from the title or question.
questionText	Visible question text from the card.
answerPreview	Visible answer preview from the card.
answerLink	Link associated with the answer preview.
answerAnchor	Fragment identifier from the answer link, such as answer3.
docId	docId query parameter from the question detail URL.
dirId	dirId query parameter from the question detail URL.
answerNo	answerNo query parameter, or its numeric value derived from the answer anchor.
author	Answerer name as displayed, including any masking.
profileLink	Profile URL associated with the displayed answerer.
authorMasked	Whether the displayed name contains a mask character.
userLevel	Korean user level shown in profile subtext, when present.
date	Date text as displayed on the card.
dateIso	YYYY-MM-DD derived only from a valid absolute displayed date.
query, searchQuery	Search query; searchQuery is retained for compatibility.
page	Search result page number.
scrapedAt	ISO timestamp when the card was extracted.
retrievalMethod	playwright_dom, the method used to read the rendered page.
searchMetadata	Search engine, page, query, source URL, and extraction timestamp.

The observed card did not establish a category or an answer count. The Actor therefore does not emit category or answerCount; a count of visible question cards is not an answer count.

Parent-observed Chrome example

This is a transcription of the supplied Chrome observation, not an Actor dataset item or an Actor run. The page rendered 10 visible Q&A cards. The first card's question asked whether people could make robot humans with feelings and thoughts. The exact question and answer preview text and the full detail, answer, and profile URLs were not transcribed here, so this observation summary does not invent them.

{
  "pageUrl": "https://search.naver.com/search.naver?where=kin&query=artificial%20intelligence&start=1",
  "visibleCardCount": 10,
  "firstCard": {
    "title": "A.I Artificial Inteligence 에서 질문 하나 합니다.",
    "questionSummary": "Asked whether people can make robot humans with feelings and thoughts.",
    "detailLinkParameters": {
      "docId": "61178463",
      "dirId": "613",
      "answerNo": "3"
    },
    "answerLinkFragment": "#answer3",
    "maskedAnswerer": "nex7****",
    "displayedDate": "2002.10.23."
  }
}

Local checks

Run the focused selector, normalization, and dataset schema checks with:

npm test

To run the Actor locally with an input object, use Apify's local Actor workflow or provide INPUT.json and start the Actor with npm start.