> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/naver/search-typo>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/naver/search-typo.mdx>

---

# Naver Typo Check API

What Naver searches for instead when Korean is typed with the keyboard in English mode, or misspelled.

`GET /v1/naver/search/typo` returns `data.corrected` and `data.correctedQuery`. For `dkdlvhs` (아이폰 typed on an English keyboard) it answers `아이폰`; for words Naver keeps it answers `corrected: false`.

## Request

- **Endpoint:** `GET /v1/naver/search/typo`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by keyword
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/naver/search/typo/get)
- **Platform page:** [/platforms/naver](https://www.socialfetch.dev/platforms/naver)

## FAQ

### What does this catch?

Korean typed with the keyboard in English mode, like dkdlvhs for 아이폰, and misspellings Naver fixes.

### What if the words are fine?

data.corrected is false and data.correctedQuery is null.

### Why use it?

To clean keyword lists before searching or tracking them, so each term is the one Korean users mean.

### How many credits does a call cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.
