Duplicate Feed Items or Posts Imported

In some very rare cases, despite using the "Unique titles only" option and WP RSS Aggregator's internal logic to avoid importing the same feed item or post twice on the same site, this does happen. Here are a few reasons why this may be.

Feed Item Permalink Updated in the RSS Feed

Some RSS feed providers will, from time to time, change the URL of an article or post on their site. This may happen due to an error on first publishing or some other issue. When this happens, if the feed item was already imported with the original (mistaken) URL (permalink), the next time the plugin fetches feed items from this source, the post will be re-imported. 

This happens since the permalink by which WP RSS Aggregator identifies a feed item not to import duplicates has now changed, so the same post is imported with two different permalinks.

The "Unique titles only" option is a fall-back method to prevent such situations from happening.

Conflicts with Plugins or Themes

Sometimes, for an unknown reason, another plugin or theme activated on your WordPress site might interfere with WP RSS Aggregator's fetch and import process. Very rarely, this has caused duplicate posts to be imported.

Caching Plugin Issues

It is known to the WP RSS Aggregator developers that certain caching plugins cause some issues when used with WP RSS Aggregator, one of which could be the duplication of posts. These issues might vary depending on the caching plugin in use and the settings implemented.

Please see the following article for more information.

Test for Solutions

When this happens, there are a couple of things that must be done.

  1. Check whether the permalink of the duplicate imported feed items/posts is different or not. 
    1. If the permalink is the same, then you know it is the source that is updating their RSS feed permalinks for the already published articles. Enabling the "Unique titles only" option will help to prevent this.
    2. If the permalink is the same, the issue lies elsewhere, and you must move on to number 2. 
  2. Test for plugin/theme conflicts as explained here.

If none of the above produces any positive results, please contact our support team.

Still need help? Contact Us Contact Us