How to Auto-Post an RSS Feed to Livedoor Blog (2026)

Updated: 2026-09-28

Short answer: enter your livedoor ID and the AtomPub API key from Blog settings → API Key into PostRSS under Accounts → Add new Livedoor Blog account. The blog ID is only needed if it differs from your livedoor ID. Then open Hedefler → Add feed, choose Livedoor Blog in Target settings — where you also choose published or draft — and add your feed under Add source (Type = RSS feed, Link = your feed address). Each item becomes a full blog post with its title, text, picture and a link back to the original, through the official AtomPub API. Livedoor Blog is included from the Professional plan.

Livedoor Blog is one of Japan's long-standing blogging services, and a large share of the country's highest-traffic personal and hobby blogs still live there. It has outlasted several waves of platform fashion, which for anyone publishing in Japanese makes it a safer home than the newest option. This guide is the long version; the auto-post RSS to Livedoor Blog page has the short one.

Two values, sometimes three

Livedoor Blog also publishes over AtomPub, so there is no application to register and no review to wait for. You need your livedoor ID and the API key from Blog settings → API Key.

The third value, the blog ID, is only required when it differs from your livedoor ID — which happens when a blog was created under a different name or moved between accounts. If your blog address matches your ID, you can leave it alone.

Published or draft

As with the other full-post destinations, each incoming item can go live immediately or be saved as a draft for review inside Livedoor Blog.

The case for drafts on a first run is the same everywhere: your feed's HTML was written for your own theme, and seeing how it renders in a Livedoor post once is cheaper than discovering it publicly. Once the output looks right, switch to immediate publishing and leave it alone.

Why a long-lived platform is worth something

Livedoor Blog launched in 2003 and is still running under the same name, which in the blogging world is close to remarkable. Platforms that promised to host writing forever have closed, been sold, been rewritten or quietly stopped accepting new posts; Livedoor has not.

For anyone deciding where a Japanese-language mirror of their work should live, that track record is a real input. An archive is only useful if it is still there, and the cost of a platform disappearing is not the migration — it is the links, the search rankings and the readers that do not come with you.

It is also an argument for the arrangement this integration supports: your own site stays the original, the platform carries a copy, and every post links back. If the platform outlives your site, the archive is still readable. If your site outlives the platform, you have lost nothing that mattered.

Where it fits

• Consumer and hobby content. Livedoor's readership skews away from the strictly technical, which makes it complementary to Hatena rather than a duplicate.
• Companies with a Japanese consumer audience maintaining a blog they would otherwise update by hand.
• Long-term archives. The platform's longevity is a real argument when you want posts to still be there in a decade.

If you publish in Japanese at any volume, running Livedoor alongside Hatena Blog ve FC2 Blog from one feed costs three Targets and no extra writing.

Setting it up, step by step

1. In Blog settings → API Key, copy the AtomPub API key, and note your livedoor ID.
2. In PostRSS, open Accounts and choose Add new Livedoor Blog account. Enter the livedoor ID and the API key, plus the blog ID if it differs.
3. Open Targets and click Add feed. One feed going to one destination is one Target.
4. In Target settings, choose Livedoor Blog and the account you just connected. This is also where you choose published or draft.
5. Click Add source. Set Type to RSS feed and paste your feed address into Link. Save.
6. Check the first item that arrives. PostRSS checks the feed every 5 minutes, and every minute on Enterprise plans.

PostRSS publishes items that appear in the feed after the Target starts running. It does not import the back catalogue — the alternative would be a destination flooded with years of archive on its first day.

Get the source feed right first

These are full-post destinations, so the feed decides the quality of the result more than any setting does.

• Full text, not summaries. A summary-only feed produces a blog of stubs. If your CMS has a full-text feed option, turn it on before connecting anything.
• An image inside the item. The picture has to be in the feed — in the item content or as an enclosure — not merely on the page the item links to. Many themes show a featured image without putting it in the feed.
• Absolute links. Relative URLs work on your site and break everywhere else.
• Anything new since you connected it. Only items appearing after the Target starts running are published.

Which plan includes it

Livedoor Blog is included from the Professional plan. Each destination you connect counts as one Target, and your plan decides how many Targets and how many posts a month you get. An annual subscription is cheaper than paying monthly. Current limits per tier are on the pricing page, and the full lineup of 66 networks is on the supported networks page. The Livedoor Blog page has the short version of the setup.

When posts stop appearing

• The API key was regenerated. Keys are managed in the blog's own settings and stop working the moment they change.
• The wrong blog identifier. An account can hold more than one blog; check the value you entered.
• Posts arrive without a picture. The feed item carries none. Check the raw feed before blaming the connection.
• Posts arrive truncated. The source feed publishes summaries rather than full text.

Frequently Asked Questions

Do I need to register an app with livedoor?

No. Livedoor Blog publishes over AtomPub, so the API key from your own blog settings is the whole authorisation.

Where is the API key?

In Blog settings, under API Key.

When do I need the blog ID?

Only when it differs from your livedoor ID, which happens if the blog was created under a different name or moved between accounts. Otherwise you can leave it out.

Can posts arrive as drafts?

Yes. The Target setting lets each new item publish immediately or wait as a draft for you to review first.

Is the article picture included?

Yes, when the feed item carries one. Each post gets the title, the text, the picture and a link to the original.

Can I publish to Livedoor and Hatena from the same feed?

Yes. Each blog is its own Target, and the same feed can be a source for both — plus FC2 Blog and Qiita, which are on the same plan.

Which plan includes Livedoor Blog?

The Professional plan.

The bottom line

Livedoor Blog is a full-post destination with a standard protocol behind it and a readership that has stayed put for twenty years. Two values from your own settings, drafts while you check the formatting, and a Japanese-language blog that keeps pace with your main site. It is included from the Professional plan.