The problem we are solving
Most Korea travel information is either an official page that answers a regulation but not your situation, or a blog post from three years ago with no date on it. The gap is practical detail that stays current: whether a foreign card works, whether anyone speaks English, which subway exit, how long the wait is, and when someone last checked.
How information is handled
Every public record carries the source it came from and the date it was last verified. Facts from an operator are shown separately from our own guidance and from traveler reports, so you always know who is telling you something.
Automatically collected event data is treated as raw material, not as a finished page. It can appear in a feed, but it is not published as a standalone search page, is not indexed, and carries no advertising until a person has reviewed it and added something a traveler cannot get from the official source.
What we deliberately do not do
- Publish thin pages generated from a data feed to attract search traffic
- Invent activity counts, fake reviews, or fake conversations
- Decide your visa or entry eligibility — we link to the government service
- Guarantee a fare, a schedule, or a merchant’s stock
- Show advertising in private messages, on safety pages, or on error pages
- Store your precise location or share it with other travelers
- Copy photographs whose rights are unclear
Where it is today
This is an early build focused on Seoul. Being specific is more useful than being impressive, so here is the actual scale:
- 6 verified place and event records
- 6 step-by-step guides with official sources attached
- 6 Seoul neighbourhoods with area pages
- Advertising disabled; no advertising script loads anywhere
- Public sign-up gated until bot protection is configured
Busan and Jeju come after Seoul is genuinely useful rather than merely covered. We would rather publish a guide when it is checked than fill a list.
How it is built
Korea Now runs entirely on Cloudflare’s edge platform. Pages render close to you, the database holds the canonical record, real-time messaging is coordinated per conversation, and event collection runs on a schedule against official government APIs. If event collection fails, the site keeps serving the last reviewed content rather than showing an error.
Safety and moderation
Reporting and blocking exist before the features that need them. A report removes content from advertising immediately, moderators act with a recorded reason, and moderators cannot browse private messages freely — only the reported message and a limited amount of surrounding context. Read the community guidelines and safety guidelines.
Getting in touch
Corrections, privacy requests, safety concerns, and copyright notices all have a route on the contact page. Telling us a page is out of date is the single most useful thing you can do.