Install the official plugin and PostRSS runs inside wp-admin. Choose the content type and categories you want published, pick the destinations, and the plugin builds the feed and creates the target for you — no feed URLs to copy, no second tab to keep open.
PostRSS works perfectly well without a plugin: you paste a feed URL on postrss.com, choose a destination, and you are finished. So it is worth being clear about what installing something on your site adds.
The plugin, PostRSS Advanced Dashboard Integration, moves the whole workflow into wp-admin. Instead of finding the right feed URL yourself — and on WordPress there are a great many of them, one per category, per tag, per author, per post type — you tick what you want in a list of your own content, and the plugin constructs the feed and creates the matching target on PostRSS for you.
That is the substantive difference. Everything else follows from it: your plan, your posting statistics and your billing history appear in the dashboard too, so the site you publish from is also the place you manage publishing.
One thing it deliberately does not do is upload your content anywhere. When you add a feed, the plugin builds a normal WordPress feed URL for your selection and asks PostRSS to watch it. PostRSS then polls that URL exactly as it would poll any other RSS source. Nothing is copied ahead of time, and nothing about your site changes for visitors.
You need three things, and all three are ordinary.
A PostRSS account — if you do not have one, the plugin’s Settings page links straight to registration and password recovery on postrss.com, so you can create one without leaving the dashboard.
WordPress 5.0 or newer and PHP 7.4 or newer. The current release is tested up to WordPress 7.1. Almost any maintained site already meets this.
A publicly reachable site. This is the one requirement that catches people out, and it is worth understanding now rather than after a confusing hour: PostRSS fetches your feed over the internet like any other reader. A site on localhost, behind HTTP authentication, inside a VPN, or with its feeds blocked by a security plugin cannot be polled. The section on troubleshooting covers how to check this.
Go to Plugins → Add New, search for PostRSS Advanced Dashboard Integration, then click Install Now and Activate. This is the route most people should take, because updates then arrive through the normal WordPress update mechanism.
Download the ZIP from the plugin page on WordPress.org, then either use Plugins → Add New → Upload Plugin, or extract it into /wp-content/plugins/ over FTP. Activate it from the Plugins screen afterwards.
Either way, a PostRSS item appears in the wp-admin sidebar once the plugin is active.
Open PostRSS → Settings and sign in with the email and password you use on postrss.com.
It is worth knowing exactly what happens here, because “enter your password into a plugin” deserves scrutiny. Your email and password are sent directly to postrss.com over HTTPS to start a session — the same request your browser makes when you log in on postrss.com itself. The password is not stored. Only the resulting session is kept, so that the site can manage feeds and targets on your behalf, and clicking Disconnect ends it.
If you do not have an account yet, the same screen links to registration and to password recovery.
This is the page the plugin exists for. Open PostRSS → Feeds.
Choose what this site should publish:
Posts, optionally filtered by category. This is the common case, and the filtering matters more than it first appears — a site that publishes both long articles and short notices usually wants only one of them going to a given destination.
Pages, if your site publishes meaningful content as pages.
Any other public content type your theme or plugins register. This is the quietly powerful part. If you run WooCommerce, your products are available. If your theme registers a portfolio, case study, event or recipe type, it appears in the list alongside posts. You do not need to know what a custom post type is, or how to build a feed for one — if it is public, it is offered.
Choose which of your connected PostRSS destinations should receive it — Facebook, LinkedIn, X, Pinterest, VK and the rest. If the account you want is not connected yet, you can connect a new destination account from this same page rather than going to postrss.com.
Four controls decide the rhythm, and all four are on this screen:
How often to check the feed. The daily posting window, which keeps publishing inside hours you choose rather than firing at three in the morning. Publishing order, which determines whether the oldest or newest item goes first — this matters most on the first run. And maximum posts per run, which is the setting that prevents an editorial burst from becoming six consecutive notifications.
You can also set the post text here, which controls how the message reads on the destination.
The plugin now builds a WordPress feed URL matching exactly what you selected, and creates the target on PostRSS pointed at it. From this point, publishing on your site is the only action required.
Click any existing target on the Feeds page to open it. From there you can:
See its status at a glance. Add any number of additional sources to the same target, which is how one destination receives several slices of your site — posts from two categories, say, plus your products. Edit or remove any individual source without touching the others. Pause or resume the whole target, which is the right move before a site migration or a bulk import. Jump to its posting report to see what was sent and when. Or remove the target entirely.
Pausing deserves a specific mention. If you are about to import a few hundred old articles, or re-publish drafts in bulk, pause the target first. An import makes every one of those items look new to a feed reader, and an unpaused target will faithfully publish all of them.
Four more pages sit under the PostRSS menu, and they exist so you do not have to leave the site to answer ordinary questions.
Account shows your PostRSS profile and subscription usage — your plan, tasks used, targets and expiry date — alongside the full list of available plans with Upgrade and Downgrade buttons. This is the page to check when posts stop arriving near the end of a busy month.
Statistics shows this month’s and previous months’ posting activity per destination type, which is the quickest way to see whether a particular network has gone quiet.
Orders is your billing history.
Affiliate shows your affiliate statistics if you are enrolled in the programme.
Help links to the official setup documentation.
No, and the reason is structural rather than a matter of optimisation.
The plugin adds admin dashboard pages and a single extra RSS feed endpoint. The admin pages load only for logged-in administrators looking at them. The feed endpoint runs only when something actually requests it — PostRSS polling, or you opening it in a browser.
Front-end visitors load none of this code. There is no script added to your theme, no database query on page render, and nothing in the critical path of a page view. On a site where performance is measured and defended, this is the relevant answer: the plugin is invisible to the front end.
Both work, and they are not exclusive. Targets created through the plugin are ordinary PostRSS targets, visible and editable on postrss.com like any other.
The plugin is the better choice when the content you publish lives in this WordPress site, when you want category or post-type filtering without hand-building feed URLs, when other people manage the site and should not need a separate login to see what is being published, or when you simply prefer one place for everything.
postrss.com directly is the better choice when you are automating feeds that are not yours — a competitor’s blog, a news source, a podcast — or when you run destinations for several different sites from one account and want them all on one screen.
Most people end up using both: the plugin for their own site’s content, and the web dashboard for everything else.
On a WordPress multisite network, each site has its own content and its own feeds. Install and activate the plugin per site, connect the account on each, and create targets from each site’s own Feeds page.
The practical advantage is that filtering stays local: each site in the network publishes its own posts to its own destinations, without anyone assembling network-wide feed URLs by hand.
This is the most common problem, and it is almost always environmental. Open the feed URL in a private browser window while logged out. If you see XML, PostRSS can see it too. If you see a login prompt, an error, or nothing, the cause is on your site.
Usual culprits: a security plugin blocking feed requests or non-browser user agents, a “coming soon” or maintenance-mode plugin, HTTP authentication left on from a staging phase, a firewall rule, or a site that is simply not public yet.
Check three things in order. Is the target paused on the Feeds page? Does Account show tasks remaining on your plan? And did the feed itself update — a caching plugin serving a stale copy looks exactly like a broken automation from the outside.
Destinations build their preview cards from your page’s open-graph tags, not from the plugin. If an article has no og:image, or the image is very large, or a CDN rule blocks the fetcher, the card arrives bare. Fixing it on the site fixes every destination at once.
Something made them look new to the feed — a bulk import, a re-publish, or a changed publication date. Pause the target before operations like that.
The plugin offers public content types. A type registered as private, or excluded from feeds, will not appear. That is a decision made by whichever theme or plugin registered it.
Reconnect from Settings. Sessions do not last forever, and changing your postrss.com password ends them.
Deactivating the plugin removes the dashboard pages and the extra feed endpoint. It does not delete your PostRSS targets, which live on postrss.com and keep running — they are watching feed URLs, and those URLs are ordinary WordPress feeds that still exist.
If you want publishing to stop as well, pause or remove the targets first, either from the Feeds page before deactivating or from postrss.com afterwards. Clicking Disconnect on the Settings page ends the stored session without touching anything on your PostRSS account.
Once the plugin is connected, the destinations are the interesting part. Telegram, Discord, Bluesky, Mastodon and Tumblr each have their own setup guide, and a webhook covers anything without native support.
Two further WordPress questions come up often enough to be worth linking: whether to use the plugin or an external tool, and how auto-posting works across a multisite network. There is also a complete setup and usage guide covering every screen in more depth than this page does.
No. Your email and password are sent directly to postrss.com over HTTPS to start a session, exactly as logging in on postrss.com would. Only the session is stored, and Disconnect ends it.
The plugin builds a normal WordPress RSS feed URL for the content type and categories you selected — the same kind of feed WordPress already exposes — and asks PostRSS to create a target watching it. No content is uploaded; PostRSS polls the URL like any other RSS source.
No. It adds admin pages and one feed endpoint that is only requested when actually loaded. Front-end visitors do not load any of this code.
Yes. Any public content type registered by your theme or plugins appears alongside Posts and Pages — products, portfolios, events and so on.
Yes. Open the target and add as many additional sources as you need; each can be edited or removed independently.
Yes, and the plugin links to registration if you do not have one. Targets created here are ordinary PostRSS targets and remain manageable on the website.
Install the plugin, connect the account, and create a single target: one category, one destination, a daily posting window and a low maximum per run. Publish something and watch it arrive. Once that works, adding a second content type or a second destination takes under a minute — and at that point the site is publishing itself.
