BlinkHub is a Korean press release distribution and PR automation SaaS. We auto-send releases to 40+ Korean media outlets via XML+FTP feed, with built-in AI press release writer and Naver news distribution support.

Which Korean media outlets does BlinkHub distribute to?

Our XML+FTP feed currently reaches 40+ Korean outlets including major dailies, online portals, and specialty trade press. Naver News distribution is included where applicable.

Can foreign companies use BlinkHub to enter the Korean market?

Yes. BlinkHub is built for global PR teams, agencies, and newsrooms expanding into Korea. We translate, localize, and submit your release to the appropriate Korean outlets.

How much does BlinkHub cost?

Free to start. Paid tiers are credit-based — pay only for what you distribute. No seat licenses, no monthly minimum. See pricing for credit packages.

Does BlinkHub include AI content generation?

Yes. We generate the press release draft from a brief, then auto-create cardnews, short video, and SNS variants for cross-channel distribution.

What format must a press release follow for Korean newsrooms?

Keep the headline within 35 Korean characters and the subheading within 60, write a lead under 200 characters that satisfies 5W1H, and keep the body between roughly 1,200 and 1,800 characters. Include a dedicated About paragraph and a press contact (name, email, phone) at the bottom, and set the correct category in metadata.

What are the XML and FTP requirements for delivery?

Use UTF-8 encoding without a BOM and wrap the body in CDATA. Include the required nodes (title, subtitle, lead, body, reporter, category, pubDate), use HTTPS absolute image URLs at 1200x800 or higher, follow each outlet's FTP filename rules, and confirm ACK responses in your delivery logs after transmission.

When is the best time to send a press release to Korean media?

Weekdays between 9 and 11 AM KST maximize pickup before desk deadlines. Avoid Monday mornings and Friday afternoons because of the release surge, and any embargo must declare the release time at the top of the body.

What are the most common reasons a Korean release gets rejected?

Frequent causes include emojis or special characters in the headline, unsupported superlatives such as best, lowest or first in the body, image files over 5MB, a missing About paragraph, sending without an embargo notice, re-sending the same release within 24 hours, and incorrect category metadata routing it to the wrong section.

What should I check after distributing the release?

Check Naver News visibility at 30 minutes, 2 hours and 24 hours, collect placement URLs per outlet for KPI reporting, re-send immediately on typos or corrections while preserving history, and monitor SERP positions for your core brand and product keywords.

Korean Media Distribution Checklist: 40 Newsroom Submission Steps

Korean newsroom submission is far more than sending an email. Per-outlet CMS specifications, XML node structure, image resolution, send timing and embargo handling — dozens of variables decide whether your release surfaces in search and on portals. The list below mirrors the pre-flight checks BlinkHub runs automatically before any release leaves the system. Teams that need PDF or HWP templates can download them at the bottom.

1. Preparation

Latest corporate registration, business license and brand identity assets on hand
Desk-editor email and phone numbers organized per outlet
FTP credentials (host, port, account, key) maintained in a per-outlet sheet
Executive quotes pre-confirmed for attribution and title

2. Manuscript format

Headline within 35 Korean characters, subheading within 60
Lead paragraph within 200 characters, satisfying 5W1H
Body of 1,200–1,800 characters (average Korean outlet cut-off)
Dedicated About paragraph at the end of the body
Press contact (name, email, phone) included at the bottom
Designated category (IT, business, culture, lifestyle, etc.) set in metadata

3. XML / FTP spec

UTF-8 encoding without BOM; body wrapped in CDATA
Required nodes: title, subtitle, lead, body, reporter, category, pubDate
HTTPS absolute image URLs, 1200x800 or higher recommended
Follow per-outlet FTP filename rules (prefix, date, serial)
Verify ACK responses through delivery logs after transmission

4. Images & captions

One hero image plus up to three supporting images
Latin-character filenames (e.g. blinkhub_launch_main.jpg)
Captions within 50 characters; for people, left-to-right title and name
Copyright holder (photographer / provider) credited

5. Timing

Weekdays 9–11 AM KST maximises pickup before desk deadlines
Avoid Monday mornings and Friday afternoons (release surge)
Embargoes must declare release time at the top of the body

6. Post-distribution

Check Naver News visibility at 30 minutes, 2 hours and 24 hours
Collect placement URLs per outlet for later KPI reporting
Re-send immediately on typos or corrections, preserving history
Monitor SERP positions for core brand and product keywords

Ten most common pitfalls

These are the failure modes most often repeated in production. Glance through them one more time right before you press send — small slips on this list can sink an entire campaign's visibility.

Emojis or special characters in the headline (break outlet CMS rendering)
Unsupported superlatives (best/lowest/first) in body — common rejection cause
Image files over 5MB causing FTP transmission failure
Missing About paragraph leading to 'unknown company' filtering
Pre-distribution without embargo notice, damaging outlet trust
Re-sending the same release within 24 hours triggering duplicate penalties
Skipping pre-approval of executive quotes, causing post-publication disputes
FTP credential expiry not monitored, silently failing delivery
Incorrect category metadata routing the release to the wrong section
Listing only a personal mobile number, overloading response handling

Download templates

The same items above are available as Korean-language HWP and PDF templates. Use them as a shared QA tool between internal approvers and external PR agencies.