,

markers 2. Preserve heading levels (##/###), FAQ blocks, bullet lists, internal markdown links 3. Keep only allowed link paths 4. Target 900-1400 words in Korean 5. Translate link text but keep paths from Allowed list 6. Stay strictly on the USA subject

Let me check the links used in the EN article:

• /destinations/usa ✓ allowed
• /guides/usa-esim-guide ✓ allowed
• /guides/esim-compatibility-check ✓ allowed
• /guides/how-to-install-esim-iphone ✓ allowed
• /guides/how-to-install-esim-android ✓ allowed
• /guides/esim-vs-roaming ✓ allowed
• /guides/what-is-esim ✓ allowed
• /guides/best-esim-for-international-travel ✓ allowed
• /guides/how-much-esim-data-do-i-need ✓ allowed
• /tickets ✓ allowed

Note: /tickets link text "Check /tickets" — that's fine.

Now, the EN body has some typos like "The Elliote" (should be The Elliott? Actually Pike Place has "The Fish Counter" etc. — I'll translate as-is or keep names as proper nouns). "Sundayural Vieux Carré Jazz Festival" — this looks like a typo for "Satchmo Summer Fest" or "French Quarter Festival"? The EN text says "Sundayural Vieux Carré Jazz Festival (seasonal)". It seems garbled. I'll translate it sensibly as "뷔 카레 재즈 페스티벌(Vieux Carré Jazz Festival, 계절 운영)" — maybe "연례 뷔 카레 재즈 페스티벌". I'll keep it as seasonal jazz festival. Actually, to be faithful, I could write "뷔 카레(Vieux Carré) 재즈 페스티벌(계절별 개최)". That works.

Note about "The Elliote" — probably "The Elliott" oyster house? There's "The Athenian" and "Emmer & Rye"... Actually in Pike Place there's "The Fisherman's Restaurant"... I'll just transliterate: "더 엘리엇(The Elliott)". Hmm, keep it simple: "엘리엇(The Elliote)"? Better to just render as "The Elliote" in Korean text as "더 엘리엇". I'll keep the original name in Latin script to avoid mistranslation: "The Elliote" — actually keeping original English names is common in Korean travel content. I'll keep proper nouns mostly in Korean transliteration with original names where helpful.

Word count: 900-1400 Korean words. Korean "words" are counted by spacing units. The EN article is roughly 1000+ words. The translation should be full depth. I need to make sure the Korean body is around 900-1400 words (spacing units). Korean word counts: each spaced token counts as a word. The EN article translated fully should land around there. Let me write generously.

Let me draft the Korean translation.

Title: 미국 도보 여행 음식 & 문화 트레일 베스트: 현지인이 알려주는 상징적인 동네 가이드

Or: "미국 최고의 도보 탐방 음식·문화 트레일 발견하기: 상징적 동네를 만나는 로컬 가이드"

Description (max 160 chars): "뉴올리언스 프렌치 쿼터부터 시애틀 파이크 플레이스 마켓까지, 미국 최고의 도보 음식·문화 트레일을 탐험하세요. 미국 eSIM으로 끊김 없는 연결과 내부자 팁으로 여행을 계획하세요."

Let me count: that's within 160 chars? Korean characters count. Let me roughly count: "뉴올리언스 프렌치 쿼터부터 시애틀 파이크 플레이스 마켓까지, 미국 최고의 도보 음식·문화 트레일을 탐험하세요. 미국 eSIM으로 끊김 없는 연결과 내부자 팁으로 여행을 계획하세요." — approximately 100 characters. Fine.