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

Updated: 2026-09-28

Short answer: connect with the email address and password of your FC2 ID under Accounts → Add new FC2 Blog account — there is no app to register. Then open Cibles → Add feed, choose FC2 Blog in Target settings and add your feed under Add source (Type = RSS feed, Link = your feed address). Every feed item is published as a complete blog post, not just a link, through FC2's XML-RPC (MetaWeblog) interface. FC2 Blog is included from the Professional plan.

FC2 Blog is one of Japan's longest-running blog services, and it still hosts an enormous number of active personal and hobby blogs. If your audience is Japanese and not primarily technical, it reaches people that the newer platforms do not. This guide is the long version; the auto-post RSS to FC2 Blog page has the short one.

XML-RPC, and what that means in practice

FC2 Blog does not have a modern token-based API. It offers the XML-RPC MetaWeblog interface, the protocol desktop blogging clients used before web editors took over, and that is what PostRSS publishes through.

The visible consequence is the credential: you connect with the email address and password of your FC2 ID rather than with a generated key. That is how the protocol works, and it is worth being clear-eyed about — there is no scoped token to revoke on its own, so changing the account password is what ends access.

If that matters to you, the practical mitigation is the same one that applies to any password-based integration: use an account whose only job is the blog, rather than one that is also your identity across other FC2 services.

Full posts, not links

Every feed item becomes a complete post on your FC2 Blog. That makes the source feed decisive: a full-text feed produces a real blog, a summary-only feed produces a list of stubs.

Before connecting anything, open your feed in a browser and look at one item. If it contains an excerpt and a "read more" link, change the setting in your CMS first. It is the single biggest factor in how this looks, and it is a two-minute fix at the source.

Where FC2 fits among the Japanese platforms

PostRSS supports four Japanese publishing destinations on the same plan, and they are not interchangeable:

• Hatena Blog — general, with a strong technical and literary readership and the bookmarking service attached.
• Livedoor Blog — consumer and hobby, very long-lived.
• FC2 Blog — the same consumer territory, with its own established audience.
• Qiita — technical articles only, community rather than blog host.

Running more than one from a single feed costs one extra Target each and no extra writing, which is usually the right answer if Japanese readership matters to you.

What arrives, and what does not

MetaWeblog is a simple protocol, and the output reflects that. The post title, the body text and inline images come through; elaborate layout does not. If your source articles depend on custom blocks, embeds or CSS from your own theme, expect the FC2 copy to be a plainer version of the same article.

For most publishing that is acceptable and arguably an improvement — a plain article reads fine, and the link back to the original is there for anyone who wants the full version. For heavily designed content it is worth publishing one item and looking at the result before leaving the Target running.

What the protocol does not offer is a draft state you can review inside FC2 before publishing, which the AtomPub platforms do provide. That makes the check-one-item-first step more important here than it is on Hatena or Livedoor.

Setting it up, step by step

1. Have the email address and password of your FC2 ID ready. There is no application to register.
2. In PostRSS, open Accounts and choose Add new FC2 Blog account. Enter the FC2 ID email address and password.
3. Open Targets and click Add feed. One feed going to one destination is one Target.
4. In Target settings, choose FC2 Blog and the account you just connected.
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 stubs, and nothing downstream can restore text the feed never sent.
• An image inside the item, if you want one — in the item content or as an enclosure, not merely on the page the item links to.
• 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

FC2 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 FC2 Blog page has the short version of the setup.

When posts stop appearing

• The account password changed. The password is the credential here, so changing it ends access until you reconnect.
• Posts arrive truncated. The source feed publishes summaries rather than full text.
• Nothing new in the feed. Only items appearing after the Target starts running are published.
• Formatting looks simplified. MetaWeblog carries a limited set of formatting; complex layout will not survive intact.

Frequently Asked Questions

Why does FC2 need my password rather than an API key?

Because FC2 Blog publishes over the XML-RPC MetaWeblog interface, which predates token-based authentication. There is no scoped key to generate, so the FC2 ID's email address and password are the credential.

Is there a way to limit that access?

Not through a scoped token. The practical mitigation is to use an FC2 account whose only role is the blog, so that changing its password affects nothing else.

Does this publish full articles or links?

Full posts. Every feed item becomes a complete blog entry, which is why a full-text source feed matters so much here.

What is MetaWeblog?

An old XML-RPC protocol that blogging platforms implemented so desktop clients could publish to them. FC2 Blog still supports it, and that is the route PostRSS uses.

Can I publish to FC2 and to other Japanese platforms from one feed?

Yes. Hatena Blog, Livedoor Blog, FC2 Blog and Qiita are all on the Professional plan, and each is a separate Target fed by the same source.

Will connecting a feed import my archive?

No. Only items appearing after the Target starts running are published.

Can posts arrive as drafts on FC2?

The MetaWeblog route does not offer the draft-and-review step that the AtomPub platforms provide, so it is worth publishing one item and checking the result before leaving the Target running unattended.

The bottom line

FC2 Blog is a full-post destination reached over an old but perfectly functional protocol, and the one thing to weigh is that the credential is an account password rather than a scoped token. Use a dedicated FC2 account, make sure your feed carries full text, and a Japanese consumer blog keeps itself current. It is included from the Professional plan.