Short answer: once a month, spend ten minutes on eight checks in your PostRSS account: the latest reports for every target, the failed items, the usage against your plan, the posting statistics, the connected accounts, the settings of each source, the devices and team members with access, and the plan renewal. Most automation problems are visible in these places weeks before anyone notices a silent page, and a short, repeated review costs far less than discovering in November that a Page has been disconnected since August.
PostRSS is built to run without attention, and for most feeds it does. That is exactly why a review is worth scheduling. A tool that works for months teaches you to stop looking, while the world around it keeps changing: a network asks you to sign in again, a blog redesign changes the feed, a colleague leaves the company, a plan is about to expire. None of these events announces itself. This guide gives you a compact routine built only from things PostRSS actually shows you: reports, item statuses, usage figures, statistics, connected accounts, source settings, devices, team members and the subscription. You can run it in ten minutes, and you can adapt the order to your own setup.
A social page that stops receiving posts rarely produces an error message that a human sees. The followers simply see fewer updates, and the owner notices much later, often when someone asks why the page is quiet. A scheduled review changes the order of events. You find the problem first, usually while it is small: one failed target among ten, one source that returns an empty feed, one account that needs to be reconnected.
The review also catches the opposite kind of problem, which is waste. A test target that nobody uses still takes one of your target slots. A source that posts to a network where the audience never reacts still uses part of the monthly allowance. Ten minutes of reading a few lists gives you facts that make the next decision easy, whether that decision is to remove something, fix something or upgrade.
Each target has a processing history. Every row shows the source, the date and time of the run, whether it succeeded, a failure reason when it did not, how many items were posted and how many items were seen. Open the most recent rows for each target and look for two patterns. Rows that succeed with zero items seen mean that the feed was read but contained nothing new, which is normal for a quiet blog and suspicious for a busy one. Rows that fail repeatedly mean something needs your attention.
Open one run in detail to see the items. Every item has a link, the message that was prepared, an image link, a status and, when something went wrong, a failure reason. The guide to PostRSS reports and item statuses explains each status. For the monthly review you only need to scan, and the quickest scan is to look for anything that is not processed or already posted.
The item statuses are unprocessed, processed, failed, skipped, already posted, maximum posts per update reached and filtered. Most of them are healthy. Already posted means PostRSS recognised an item it had published before. Filtered means a keyword filter removed it on purpose. Maximum posts per update reached means the item is waiting for a later check. The statuses that deserve a closer look are failed and skipped.
For a failed item, read the failure reason. It often points to the account: a permission that was withdrawn, a channel where the bot is no longer an administrator, a webhook that was deleted. For a skipped item, think about the network. Some networks need an image, so an item without a picture may be skipped there while it is posted elsewhere. Write down the cause and the fix for each pattern, even if the fix is only to reconnect the account.
Your subscription shows the posts used this month next to the posts limit, and the targets used next to the targets limit. Each target also has its own used value. Compare the percentage of the month that has passed with the percentage of the allowance that has been used. If you are halfway through the month and have used eighty percent, you will hit the limit; if you have used ten percent, you may be paying for more than you need.
The numbers also tell you about balance. If one target uses most of the allowance, ask whether that destination deserves it. The three limits of a plan, posts per month, posts per target and targets, interact, so look at all three figures together. Remember that items removed by a keyword filter do not count, so a better filter is the cheapest way to lower usage.
PostRSS also keeps posting statistics: a total for the selected period, a breakdown by target type and a monthly history. Use them to see which networks receive the most posts and whether the volume is growing or falling. A sudden drop in one network is a signal. Either the feed produced less, or the target failed during part of the month. Combined with the reports from Check 1, you can usually tell which.
The statistics are also useful when you report to a client or a manager. A simple line such as posts per network per month is easier to read than a list of runs, and it shows the work that the automation did without anyone opening a social network.
Your connected accounts are listed in the Accounts area of the web app. Look at the list with three questions. Is each account still needed? Is each account active? Does any account offer to synchronise, which is the way to refresh the list of pages or boards that the network lets you use? If a Facebook Page has been added to your business since you connected, synchronising makes it available for targets.
Remove accounts that you no longer use. Only the owner of the PostRSS account can disconnect an account, and disconnecting is the right step when a client leaves or a project ends. For chat networks that use a bot, a webhook or a token, remember that you can also stop publishing from the other side: removing the bot from a channel or deleting a webhook stops the posts immediately. The guide on how PostRSS connects networks lists which networks use sign-in, forms or tokens, so that you know where to look.
A source holds the settings that shape every post: the feed address, the message format, any static text, the extra query parameters for tracking, the maximum number of posts per update, the processing type, the publishing order, the start date and catch-up, the keyword filters and the hashtags. Settings that made sense in the spring may not fit the autumn. A filter that excluded a topic you no longer cover, a window that suits last year’s audience or a hashtag list that has grown stale are all small leaks.
Ask four questions for each source. Is the feed address still the right one after any site change? Is the frequency appropriate for how often the site publishes? Do the filters still match what you want to promote? Do the hashtags and static text still sound like your brand? If you use exact times, the guide to exact times, windows and intervals will help you adjust them.
Access is part of the health of an automation. The API issues a token for each device that signs in, the tokens appear under Devices in the account, and each one can be revoked at any time. If you see a device that you do not recognise or a phone you no longer use, revoke it. Tokens are shown only once when they are created, which is why old ones are easy to forget.
Team members, available on Enterprise plans through the Team menu, work inside the owner’s account. Review the list when people change roles. A person who has left the company should not keep access, and a contractor whose project has ended should be removed. The article about inviting colleagues to one account describes how the roles behave.
The subscription shows the plan, when it was activated and when it expires. Put the renewal date in your calendar, because an expired subscription changes what the account can do. Read the plan list on the pricing page once a quarter to see whether a different plan now fits your measured usage better. If you pay month by month and your usage is stable, check whether paying for a longer period suits you, since the pricing page describes the discount for annual payment.
A review is only useful if it ends in small actions, so decide on the spot instead of collecting a long list. If a target fails, reconnect the account or fix the permission and run a check on the next scheduled time. If a source returns nothing for weeks while the site keeps publishing, open the feed address in a browser and confirm that it still works. If usage is far above the pace of the month, lower the posts per update, add a filter or reduce the number of targets that receive low-value items. If usage is far below, consider whether a cheaper plan is enough or whether the feed deserves another network.
Keep one note per review with three lines: what you checked, what you changed and what you want to look at next month. This tiny habit turns a vague feeling that the automation is fine into a record that you can show to a colleague or a client, and it makes handovers easier when someone else takes over the account.
| Check | Where to look | Healthy looks like |
|---|---|---|
| Reports | Report of each target | Recent runs, no repeated failures |
| Items | Items of the latest runs | Mostly processed, already posted or filtered |
| Usage | Subscription usage and per-target usage | Pace matches the month, no single target dominating |
| Statistics | Posts by network and month | Volume in line with the feed |
| Accounts | Accounts list | Only needed accounts, all active |
| Sources | Source settings | Right feed, frequency, filters and hashtags |
| Access | Devices and team | Only people and devices you recognise |
| Plan | Subscription and pricing page | Renewal date known, plan matches usage |
Print this table or copy it into your task manager. Add the date of each review and one line of notes. After three months you will have a small history that shows trends: usage rising, one target repeatedly failing, one source that you keep adjusting.
A monthly PostRSS review is short because PostRSS shows you the right things in a few places: reports and item statuses, usage, statistics, accounts, source settings, devices, team members and the subscription. Run the eight checks, write down what you find and fix the small problems while they are small. The routine protects your pages, controls your costs and makes upgrades a decision based on numbers. You can compare plans on the pricing page and read about every option on the features page.
Once a month is a good rhythm for most accounts. Check reports weekly if you manage important pages, and always look after you change a feed, a plan or a connected account.
Reading the latest report of each target. It shows whether runs succeed, how many items were seen and posted and the reason for any failure.
The item was removed by a keyword filter on the source. It was not posted and it did not use your allowance.
Yes. The subscription shows the posts used this month next to the posts limit, and each target reports its own used value.
Open the devices of your account and revoke the token of that device. A revoked token can no longer be used to sign in.
Only the owner of the PostRSS account. Team members work inside the owner’s data but cannot perform owner-only actions.
What changed in the networks, what broke, and how to fix it before it costs you reach.
Criadas pela Internet Solutions, a equipe por trás do PostRSS. Cada uma economiza seu tempo de um jeito diferente.
English
Lietuviškai
Deutsch
Français
Русский
Español
Polski
Italiano
Українська
Čeština
Português
日本語
Latviešu valoda
Eesti
Magyar
Bahasa Indonesia
Türkçe
हिन्दी
Ελληνικά
العربية
ไทย
Tiếng Việt
Română
Bahasa Melayu
বাংলা
