AutoBlog - WordPress Plugin

How to Configure AutoBlog for Controlled RSS Imports in WordPress

AutoBlog is best viewed as a tool for automatically bringing content from RSS feeds into WordPress posts, but it needs to be handled more carefully than actively maintained plugins. This guide covers more than just installation and first steps. We will walk through feed logic, filters, authors, categories, images, processing schedules, result checks, and troubleshooting for common issues.

The main nuance with this product is its current status. WPMU DEV has placed AutoBlog in its legacy plugin list, published the code on GitHub, and explicitly noted that products in this category are no longer supported like regular commercial solutions. The safest approach is straightforward: start with a staging copy of the site, import into drafts, then review the feed, images, links, author permissions, and search impact.

This guide is for a webmaster, editor, or owner of a network of WordPress sites who needs to collect news, announcements, partner excerpts, content from child blogs, or videos from RSS-enabled sources. It does not cover purchasing advice, licensing, or workarounds for restrictions. The focus here is practical configuration of a plugin you already have, along with a clear understanding of where AutoBlog makes sense and where a modern alternative would be the better choice.

What Problem RSS Import Solves and Where AutoBlog Is Useful

AutoBlog automates a repetitive editorial task: it takes items from an RSS feed and turns them into WordPress posts. In the feed settings, you can choose the destination site in Multisite, the post type, the status of the new post, the author, categories, tags, keyword filters, and duplicate-handling rules. The built-in report shows feed activity, including how many sources were processed, how many items were imported, and what errors occurred.

The plugin becomes practical when the content already exists in a structured source. For example, a company may have a main blog and separate regional sites, partners may publish RSS announcements, a school may run several educational blogs, or an editorial team may track a list of niche sources while the main site only needs excerpts. Moving that content by hand takes time, and AutoBlog handles the recurring processing for you.

The best use case for AutoBlog is not blindly copying full articles, but carefully aggregating content with editorial review. The plugin can import the full text only if the full text is actually present in the RSS feed. If the source provides only a short excerpt, AutoBlog will not turn it into a full article. That limitation matters: the plugin reads what is in the feed, it does not crawl the source site.

When the Product Is a Good Fit

AutoBlog can be useful if you work with predictable RSS sources and are willing to review imports. It is especially easy to understand for workflows where you need to collect posts in one blog or distribute content across sites in a WordPress network.

• You want to import content from your own or partner sites where reuse or excerpt-based republication is allowed.
• You run a niche aggregator and are prepared to link back to the original source.
• You use WordPress Multisite and want different feeds to go to different sites in the network.
• You are willing to start in draft mode rather than publish everything immediately.
• You understand that a legacy plugin may have limitations with current versions of WordPress, PHP, themes, and feed formats.

When AutoBlog Is Probably the Wrong Starting Point

You should not install AutoBlog on an important production site without testing if the source is unstable, the feed is large, the server is slow, or you need developer support for current WordPress versions. The plugin also does not solve the legal or editorial side of the process: if a source does not allow republication, the technical ability to import it does not make that use acceptable.

If you need a supported interface, editor blocks, active updates, and dependable help for recent WordPress versions, compare AutoBlog with modern RSS aggregators right away. AutoBlog can still be useful for a one-time migration from an older project, but for a new site it is often more sensible to choose a solution that is still actively developed.

What to Check Before Installing the WordPress Plugin

Before installation, the question is not just whether the ZIP file works. You also need to know whether the site can handle recurring imports. RSS import touches the database, media library, task scheduling, HTTP requests, and category structure. A problem in a single feed can create dozens of unnecessary drafts, duplicates, or empty posts.

Site State and Backup

Make sure you have a current backup of both the files and the database. AutoBlog creates posts, may add images to the media library, can create taxonomy terms, and stores its own feed-related data. Simply deactivating the plugin does not always mean the imported content will disappear on its own, so it is better to know in advance how you would roll back a test.

For the first run, use a separate copy of the site or at least a private section. This matters even more in Multisite: picking the wrong destination site can send imports somewhere you are not expecting them to appear.

RSS Source Quality

Start by opening the feed URL in a browser and validating it with an RSS validator. If the feed does not return XML, responds too slowly, requires authentication, throws an SSL error, or contains invalid characters, AutoBlog may show an error message or simply fail to import items. In older discussions, WPMU DEV support noted that the plugin relies on WordPress's built-in SimplePie-based mechanism, so some errors come not from the AutoBlog interface itself, but from the feed parser.

Pre-installation check: one test feed, only a few items, import into drafts only, run processing manually, and review the log. That approach reveals problems much faster than launching a dozen sources all at once.

Permissions, Authors, and Content Policy

Decide which user account should own imported posts. If the RSS feed includes author data, AutoBlog may try to use the original author, but it is safer to create a local editorial account such as news-import or rss-editor. That makes it easier to filter imported content and distinguish automated posts from manually published ones.

Check your content usage rules separately as well. AutoBlog includes excerpt modes and links to the original source, but those do not replace permission from the author. For a site that depends on search traffic, it is usually better to start with short summaries, your own introductory context, and a clear link to the original.

Installing, Activating, and Verifying AutoBlog for the First Time

Because AutoBlog is a legacy WPMU DEV plugin distributed through GitHub, the installation flow is usually different from installing a plugin from the WordPress directory. The overall logic is still standard: upload the ZIP archive, install it through the WordPress admin panel, activate it, and confirm that the Autoblog menu item appears.

Installing on a Standard Site

If you are running a single WordPress site, use the standard path: Plugins -> Add New -> Upload Plugin. After uploading the archive, click Install Now, then Activate Plugin. Once activated, a separate Autoblog menu item should appear in the admin panel. If it does not, check whether the plugin's main file was actually activated and whether a critical PHP error occurred.

Do not enable automatic publishing right away. Create a test feed with the status set to Draft or an equivalent draft mode if your version provides one. That lets you see how AutoBlog builds the title, date, categories, images, and source link before the content reaches the public side of the site.

Installing on WordPress Multisite

The official AutoBlog description lists two Multisite options: activation per individual site, or network activation through Network Admin -> Plugins. Choose the mode that matches your use case. If AutoBlog is only needed for one editorial site, do not activate it across the entire network without a reason. If the plugin is meant to distribute feeds across multiple sites, network activation may be more convenient, but it requires more careful checks of permissions and destination-site selection.

After activation, open the Autoblog section and find the feeds list. The interface should include actions such as editing, cloning, manual processing, checking, and deleting a feed. If the plugin reports a problem with a database table, do not run random SQL commands from a forum thread. First make a backup, confirm the table prefix, and check whether the table really was not created. On a production site, those steps should be handled by a database administrator.

Configuring a Feed: From URL to Post Status

Most of the work in AutoBlog happens not in global settings, but in the configuration of each individual feed. That is useful: one source can go to news, another to blog drafts, and a third to a separate post type. But that flexibility quickly turns into chaos if you do not define clear rules in advance.

Basic Feed Fields

When creating a feed, enter a clear name in the Your Title field. The title should help the administrator, not the reader - for example, it can identify the source, topic, and destination. In the Feed URL field, paste the RSS address. If the site offers multiple feeds, choose the narrowest one available: not the site's general stream, but the category, tag, or section you actually need.

The Add posts to field is especially important in Multisite. It determines where the posts will go. The Post type for new posts field controls the post type, usually post, but on projects with custom post types you can direct imports into a separate content entity. That makes it easier to separate automated content from the regular blog and control how it is displayed.

Publication Status

For the first run, choose draft status. Auto-publishing looks tempting, but it is risky: a feed may change format, start including promotional posts, lose images, or return truncated text. Draft mode gives an editor a control point. After several successful cycles, you can decide which sources are reliable enough for automatic publishing and which should always go through manual review.

Post Date

AutoBlog lets you choose between the import date and the original publication date, if that setting exists in your version. The source date is useful for archives and news streams where chronology matters. The import date is more convenient if you want newly imported posts to appear at the top of the site when the feed is processed. Be careful with original dates from older sources: you can accidentally create posts that immediately disappear deep into the archive and never get noticed by the editor.

Authors, Categories, and Tags

In the author section, you can choose a local user or try to use the author provided by the feed. For a controlled site, assigning a specific local author is more reliable. If you need the original author, check how your theme displays the author field and whether that could create confusion with real site users.

The taxonomy settings include a convenient but risky option to automatically add terms from the feed. On public sources, tags can be noisy, duplicated, inconsistent in capitalization, or filled with utility words. Do not enable automatic category creation on the first run. It is better to assign one base category, add 2-3 editorial tags, and see how the content groups itself.

Filters, Excerpts, and Images: Best Settings for the First Run

The most useful part of AutoBlog is not the fact that it imports content, but that it lets you limit what actually reaches the site. Filters based on words, phrases, and tags help remove irrelevant items from a source. Excerpt and image settings make the import safer for readers, search visibility, and site performance.

Filtering by Words and Phrases

In the Post Filtering block, you can specify words that must be present in a post, words where any one match is enough for import, an exact phrase, and words that must not appear. Start with gentle rules. Filters that are too strict create the false impression that something is broken: the feed works, but no items pass the conditions.

For a news site, a two-level approach works well. At the first level, set a broad topic such as a brand, product, city, or industry. At the second level, add exclusions: irrelevant categories, contest posts, job listings, or repeated press release items. After each change, run processing manually and see how many items pass. If the number drops to zero, temporarily remove some conditions and test the feed again.

Excerpts and the Original Source Link

AutoBlog can import either the full text or an excerpt, but full text is only available when the RSS feed itself provides the complete article. For most public aggregators, it is better to use excerpts and configure the source-link text. Older plugin documentation mentions settings for the original-source link, the nofollow flag, and opening the link in a new window. Treat those parameters as part of your editorial policy, not as a guarantee of any SEO outcome.

Automatically imported content should be clear to the reader: what the source is, why the post appeared on the site, and where to go for the full version. If your site's topic requires your own analysis, add an editorial intro manually after the import.

Images and the Media Library

AutoBlog includes add-ons for importing images, setting featured images, removing images from content, and choosing the featured-image source. The available options may depend on what the RSS feed provides: a media:thumbnail tag, an enclosure, the first image in the content, or the last image. If the feed contains no image, the plugin has nothing to use except a default image, if that option exists.

On the first run, do not import every image without checking the results. A media library grows quickly, and external images may be heavy, incorrectly sized, or subject to usage restrictions. It is better to enable featured-image import for a single test feed, then review file sizes, alt text, HTTPS links, and how the site's theme renders the cards.

Processing Schedule, Duplicates, and Admin Reports

RSS import feels simple until you have a few dozen sources. At that point, the main concerns become scheduling, limits, duplicates, and reporting. AutoBlog lets you define how many recent items to process, how often a feed should run, what time range the import should cover, and whether already imported posts should be updated.

How to Choose a Processing Frequency

The right frequency depends on the source. If a feed updates once a day, there is no point checking it every few minutes. If it is a news stream, more frequent processing may make sense, but only after load testing. WordPress uses WP-Cron, which depends on site visits or a server-level cron configuration. On a low-traffic site, tasks may run late, while on an overloaded server, HTTP requests to feeds may time out.

A typical safe starting pattern looks like this:

1. One feed with a small number of items, such as the latest 3-5 posts.
2. New posts set to draft status.
3. Manual processing via the Process action.
4. Review of the report and error log.
5. A gradual increase in the number of sources and processing frequency.

Duplicates and Re-Importing

The Override duplicates setting is useful when a source updates items that were already published, but it can also unexpectedly overwrite local editorial changes. If you manually enhance imported posts, keep duplicate overwriting disabled or test it on a separate feed first. For a news showcase where freshness matters and there is no manual editing, updating duplicates may be acceptable.

Before enabling duplicate overwrites, decide what matters more: preserving local edits or keeping the post synchronized with the source. That is not a technical detail. It is an editorial rule.

Reports and the Activity Log

The AutoBlog interface includes a reporting panel for feed activity. It helps you see how many feeds were processed, how many items were imported, and how many errors were recorded. After each settings change, do not just look at whether new posts appeared. Check the report as well. If the error count goes up, roll back the last change and test again.

In Multisite, also verify which blog received the posts. Choosing the wrong destination site can look like "the plugin is not importing anything" when in fact the content was imported somewhere else in the network.

Practical Scenario: Partner News Drafts

Let us walk through a realistic scenario. A company runs a WordPress site, and three partners publish news feeds via RSS. The goal is to pull in new announcements once a day, place them in a "Partner News" category, show only content related to the right topic, avoid copying full articles, and keep a link to the source.

Goal

Create a controlled stream of drafts that an editor can quickly review and publish manually. Random content, full copies of articles, unnecessary categories, and posts with no source link should never reach the public side of the site.

Preparation

Before configuring the feed, create a "Partner News" category and a separate author account for imported content. Validate each RSS feed both in a browser and through a validator. Choose one source for the first test. If that source provides a category-specific feed, use it instead of the general stream.

Configuration Steps

1. Open Autoblog -> All Feeds and click Add New.
2. In Your Title, enter a clear internal name, such as "Partner A - product news".
3. Paste the RSS address into Feed URL and save the feed in draft mode.
4. In Add posts to, choose the correct site if you are using Multisite.
5. In Post type for new posts, leave post selected if you do not use a separate post type for aggregated news.
6. Assign the local author and the "Partner News" category.
7. In the filters, add 1-2 required topical keywords and 2-3 exclusions for irrelevant content.
8. Enable excerpt import, configure the original-source link text, and check the nofollow flag if it matches your link policy.
9. Run Process manually and open the draft list.

Checking the Result

The posts list should now contain drafts with clear titles, the correct category, the selected author, and a link to the original source. Open 2-3 posts in the editor and check the excerpt length, formatting, image, date, and absence of unnecessary HTML fragments. Then preview them and confirm that your theme displays the imported posts correctly.

Scenario takeaway: if manual processing produces drafts, the source link works, the category stays clean, the images do not break the layout, and the report shows no new errors, the feed can gradually be moved to a schedule.

What Can Go Wrong

If no posts appear, do not change every setting at once. First disable the filters, reduce the number of imported items, validate the RSS feed again, and run processing manually. If posts appear after disabling the filters, the problem is in the selection rules. If they still do not appear, check the feed itself, WP-Cron, timeouts, source-server availability, and the AutoBlog error log.

SEO, Performance, and Editorial Safety in Auto-Posting

Automatic import affects more than editorial convenience. It changes the site structure, creates new URLs, adds internal archives, pulls in images, and can produce similar pages. That means your AutoBlog setup should account for search visibility, speed, and content quality.

Search and Duplicates

Google describes canonicalization as the process of choosing the primary version among similar pages and emphasizes that the rel="canonical" signal is a hint, not an absolute rule. For an RSS aggregator, that leads to one simple conclusion: you cannot rely on an automatic link or a similar meta tag to fully solve duplicate-content issues. It is better to build the page so it has independent value of its own: a short introduction, context, a category, a source link, and a clear role within the site's structure.

For most sites, importing excerpts is safer than importing full text. If you publish full copies of your own content from child sites, think through canonical URLs at the SEO-plugin and template level. If the sources are external, confirm permissions and do not present someone else's content as your own.

Performance and the Media Library

Image importing can slow down a site if the feed delivers large files. Check featured-image sizes, make sure your image optimizer works correctly, verify HTTPS, and review how the theme behaves on archive pages. If you have many feeds, do not run them all at the same time. Spread out the schedule, reduce the number of items per pass, and watch your hosting load.

Permissions and Editorial Control

Do not give automated imports permission to publish everything in the first stage. Draft status, a separate author, and a separate category make it easy to find and remove weak content. If an editor manually changes imported posts, disable duplicate overwriting or document which fields can be edited safely without losing changes.

A good AutoBlog setup does not end when you click Create Feed. It ends with a clear review process for new content. This is especially important for sites dealing with legally sensitive content, medical topics, financial news, or partner materials.

Common AutoBlog Problems and RSS Import Troubleshooting

AutoBlog errors are usually tied not to a single button, but to a chain of components: source - HTTP request - parser - feed settings - WordPress - theme. That is why troubleshooting is best done from the external source inward to the final result on the site.

Typical symptoms and safe checks

Symptom	Likely cause	What to check	What to do
The feed is marked invalid	The RSS contains an XML error, the response type is wrong, there is an SSL issue, or the request is timing out.	Open the URL in a browser and validate it with the W3C Feed Validator.	Fix the source, choose another feed, or work only with sources that consistently return valid RSS.
Processing completed, but no posts were created	The filters are too strict, all items are already treated as duplicates, or the wrong destination site was selected.	Temporarily disable filters, reduce the item limit, and review the AutoBlog report.	Restore filters one at a time and see which condition stops the import.
Import only works when run manually	WP-Cron is not running regularly, or the site receives very little traffic.	Check cron events using a diagnostic plugin or your hosting tools.	Set up a server-side cron job for WordPress or reduce feed-processing frequency.
No featured image is set	The RSS feed does not contain a suitable image, or the wrong thumbnail source was selected.	Inspect the feed XML to see whether it includes media:thumbnail, an enclosure, or an image in the content.	Switch the image source, set a default image, or disable thumbnail import for that feed.
Local edits disappear	Duplicate overwriting is enabled, and AutoBlog is updating posts that were already imported.	Check the Override duplicates setting and the processing log.	Disable overwriting for feeds where an editor manually refines the content.

When to Enable Force Feed and Disable Sanitization

The Allow Force Feed and Disable Sanitization add-ons exist for difficult sources that fail normal validation. Use them only after troubleshooting. If a feed is valid but still will not process, these options may help with an unusual response type or overly strict content cleaning. If the feed is genuinely broken, those modes will not turn it into a reliable source.

Roll these modes back if enabling them leads to empty posts, strange markup, extra tags, or theme errors. On a public site, it is better to lose one problematic source than to keep importing junk into your content.

What to Do About a cURL Timeout

A timeout usually means the WordPress server did not receive a response from the source in time. The cause may be the size of the RSS feed, a slow source server, hosting network restrictions, or SSL. Start with simple checks: test the feed in a browser, in a validator, and from another server. If the issue occurs only on your hosting environment, send your host the exact error text and the source URL. Raising limits without understanding the reason will often just hide the problem until the next large feed arrives.

When AutoBlog Is the Right Choice

AutoBlog makes sense if you understand its legacy status, work with trusted RSS sources, are willing to import content into drafts, and do not expect current support from WPMU DEV. Its strengths are flexible feed configuration, filters, Multisite destination-site selection, categories, authors, excerpts, source links, reports, and a set of add-ons for images and compatibility.

If you are only now choosing a tool for a new project, compare AutoBlog honestly with modern alternatives. If your goal is to support an existing RSS import workflow or carefully test an older WPMU DEV plugin, you can download the AutoBlog archive, install it on a staging copy of the site, and go through the step-by-step checks from this guide.

The final rule is simple: start with a valid feed, then drafts, then filters, images, and reporting, and only after that move on to scheduling and publishing. That sequence reduces the risk of duplicates, empty posts, unnecessary categories, and source-related problems.