How to Auto-Post an RSS Feed to Qiita (2026)

Updated: 2026-09-28

Short answer: create a personal access token in your Qiita account settings and paste it into PostRSS under Accounts → Add new Qiita account — there is no app to register. Then open Ziele → Add feed, choose Qiita in Target settings, set one to five tags (Qiita articles require them) and choose whether articles are public or shared only with people who have the link, then add your feed under Add source (Type = RSS feed, Link = your feed address). Qiita is included from the Professional plan.

Qiita is where Japanese engineers publish and read technical articles. It occupies roughly the position DEV holds in English — a community platform rather than a blog host — and for a developer-facing product with any Japanese market, it is the place technical content actually circulates. This guide is the long version; the auto-post RSS to Qiita page has the short one.

Tags are mandatory, and they decide everything

Qiita requires at least one tag and allows up to five, and PostRSS asks you to set them on the Target. This is not a formality to fill in and forget.

Qiita distribution runs on tags. An article tagged Python oder AWS appears in those tag feeds, where people browse; an article with a vague or wrong tag is published into a space where only your existing followers will see it. Worse, a tag that does not match the content is noticed — the community is small enough and attentive enough that articles turning up in a tag they do not belong to get remarked on.

Because tags are set per Target, the practical consequence is that a broad company blog is the wrong source. Point the Target at a category or tag feed from your own site that matches the Qiita tags you are setting, and create a second Target with different tags if you publish on a second subject.

Public or limited sharing

The other Target setting decides visibility: articles can be published publicly, or with limited sharing so that only people holding the link can read them.

Limited sharing is genuinely useful for a first run. It lets you see how your feed's HTML renders as a Qiita article — code blocks in particular — without the result being public while you work it out. Once the output looks right, switch the Target to public.

Writing for Qiita, honestly

Qiita is a technical community, and the same rules apply that apply to DEV or to any developer forum. Articles that explain something specific do well. Marketing posts dressed as tutorials do not, and the readership is quick about it.

Two practical points. First, the audience reads Japanese — an English feed will find a narrower readership than the platform's size suggests, though technical English is widely read. Second, Qiita is a place people comment. An account that publishes automatically and never replies loses credibility faster than one that publishes less.

Qiita next to DEV and your own blog

The three sit in a sensible order. Your own site is the original and keeps the canonical URL. DEV reaches the English-speaking developer community and supports a canonical link back. Qiita reaches Japanese engineers, and its discovery runs on tags rather than on follows.

One feed can serve all three, which is the argument for doing it at all: the writing happens once, and the distribution is three Targets. Where they differ is in what you configure — DEV wants the canonical URL set, Qiita wants the right tags, and your own site wants neither because it is the source.

If you publish in both languages, the tidy arrangement is separate Targets from separate category feeds rather than one Target trying to serve both audiences.

Setting it up, step by step

1. Create a personal access token in your Qiita account settings.
2. In PostRSS, open Accounts and choose Add new Qiita account. Paste the personal access token.
3. Open Targets and click Add feed. One feed going to one destination is one Target.
4. In Target settings, choose Qiita and the account you just connected. This is where you set one to five tags and choose public or limited sharing.
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

Qiita 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 Qiita page has the short version of the setup. It sits alongside the Japanese blogging platforms and Chatwork on the same tier.

When articles stop appearing

• The token was revoked. Personal access tokens are managed in your Qiita settings and stop working the moment they are removed.
• No tags were set. Qiita requires at least one tag; an article without any cannot be created.
• Formatting looks wrong. Compare against the raw feed item. Feeds shipping stripped HTML produce thin articles, and that is fixed at the source.
• Nothing new in the feed. Only items appearing after the Target starts running are published.

Frequently Asked Questions

Does Qiita require tags?

Yes. Every article needs at least one tag and can carry up to five. You set them on the Target, so all articles from that feed share them — which is a reason to point each Target at a narrow source feed.

Can articles be private while I test?

Yes. The Target setting offers limited sharing, where only people with the link can read the article. It is the sensible choice for a first run while you check how your HTML renders.

Do I need to register an application?

No. A personal access token created in your Qiita account settings is the whole credential.

Should I publish English articles to Qiita?

You can, and technical English is widely read there, but the platform's audience is Japanese and a Japanese-language feed will reach further.

Can I use different tags for different feeds?

Yes. Tags are a Target setting, so one connected account can publish a Python feed with Python tags and a front-end feed with different ones.

Will connecting a feed publish my archive?

No. Only items appearing after the Target starts running are published, which also avoids arriving on the platform as a bulk poster.

Which plan includes Qiita?

The Professional plan.

Should I set a canonical URL back to my own site?

Qiita's own article options are where that is handled if you want it. The important thing to be aware of is that publishing the same article on two domains is duplication, and the original is the version you usually want ranking.

The bottom line

Qiita is the Japanese developer community's publishing platform, and the setting that decides whether your articles are read is the tags. Use limited sharing while you check the formatting, point each Target at a source feed that matches its tags, and show up in the comments. It is included from the Professional plan.