CodeCanyon Auto Robot - WordPress Plugin

Guide to Configuring and Using CodeCanyon Auto Robot Safely

CodeCanyon Auto Robot is a WordPress plugin for automatically populating a site with content from RSS, search campaigns, video services, social sources, and other external channels. This guide does not repeat the marketing copy. Instead, it walks through a working setup: how to prepare your site, install the plugin, build a campaign, configure sources, scheduling, images, post templates, duplicate checks, and logs.

The core practical point is this: Auto Robot is only useful when the site owner already understands which sources are acceptable, what content can be published, how quality will be reviewed, and where the automation should stop. The plugin can create posts on its own, but editorial responsibility still stays with the administrator. That is why this guide covers not only setup steps, but also result checks, limitations, troubleshooting, usage scenarios, and a comparison with similar tools.

This material is intended for users who already have access to the plugin archive and want to test it safely on a WordPress site. We do not cover purchasing, payment, license entry, or activation bypass. The focus here is on the features, settings, and practical use of a plugin you already have.

What Auto Robot Is Meant to Do and Where It Actually Makes Sense

Auto Robot belongs to the class of autoblogging and content aggregation plugins. Its job is to pull material from external sources, turn it into WordPress posts, and run those campaigns either manually or on a schedule. The product page and official documentation confirm campaigns for RSS, keywords, YouTube, Vimeo, Flickr, Instagram, Facebook, Twitter, Google Custom Search, post templates, execution logs, caching, WP-Cron scheduling, and settings for post type, status, author, categories, tags, and images.

The main strength of a tool like this is consistency. If a site has a clear topic, a set of vetted sources, and an editor who controls quality, the plugin can help build a news feed, digest, video catalog, topic hub, or draft queue for later manual editing much faster. It is also useful for demo sites where you need to quickly show a live news feed, a "helpful resources" section, or an example content stream without manually adding every post.

Its weakness is just as obvious: automation does not make content valuable by itself. If you connect random sources, publish everything immediately with the publish status, skip duplicate checks, and add no original context, the site quickly turns into a pile of borrowed fragments. That is bad for readers, risky for SEO, and may violate source rules. So the best CodeCanyon Auto Robot setup starts not with the Add New Campaign button, but with an editorial rule: which sources are allowed, what gets published automatically, what stays in draft, who reviews questionable material, and what counts as a successful campaign.

Common Scenarios Where the Plugin Can Help

The first scenario is a niche news section. For example, an agency site may run an industry news page and want to pull in headlines from several RSS feeds. In that case, Auto Robot can be configured so posts go into a separate category, follow a consistent template, retain the source link, and publish no more often than a defined interval.

The second scenario is a video digest. Official Auto Robot materials describe integration with the YouTube API v3 and the ability to import videos by channels, playlists, or keywords. For a school, media site, or community, that can be a practical way to keep a video collection current. But this is also where it becomes especially important to monitor API quotas, usage rights, and whether the videos actually match the page topic.

The third scenario is an editor-facing draft queue. In Auto Robot you can choose the post status, including draft, pending, and publish. For a new site, starting with drafts is safer: the plugin gathers material, the editor reviews headlines, removes junk, adds an introduction, checks the source, and only then publishes. That approach is slower, but it dramatically reduces the risk of exposing weak or borrowed content to visitors before it has any real value.

The fourth scenario is demo content for a client. If a developer is building a prototype for a news portal, real estate catalog, product blog, or community site, Auto Robot helps show what a live content stream will look like. In that mode, posts should not be indexed and should not become permanent content without review.

When a Different Approach Is Better

This plugin may not be the right fit if you expect it to replace an editor, a lawyer, an SEO specialist, and a writer. It also does not solve the originality problem if the site simply copies other people's text. Even with templates, translation, rewriting, or AI modes, you still need to verify facts, sources, copyright, and reader value.

Auto Robot is also a poor choice for a site that already has performance issues, unstable WP-Cron behavior, weak hosting, an overloaded media library, or a messy category structure. Autoblogging creates a large number of background tasks, network requests, and posts. If the database is already under strain, a new automation pipeline will only make that worse.

What to Check Before Installing It on WordPress

Before installing Auto Robot, it is worth doing a short technical and editorial audit. The official plugin documentation lists basic PHP and MySQL requirements and points to the minimum WordPress requirements. But for a real site, that is not enough. You need to understand whether the site can handle regular imports, whether you have a backup, how stable the task scheduler is, which SEO and caching plugins are already installed, and whether they might conflict with large-scale post creation.

Technical Preparation

Start with a site copy, not with the installation itself. For the first test, a staging environment, local copy, or separate test site is the best option. Automatic publishing can create dozens of posts, upload images into the media library, fill logs, and change the category structure. Those changes are much harder to roll back on a live site.

• Make sure you have a current backup of both files and the database.
• Confirm that WordPress, the active theme, and your key plugins are updated without critical errors.
• Check whether WP-Cron has been disabled at the configuration level if you plan to schedule campaigns.
• Review your hosting limits: PHP memory, request execution time, outbound HTTP request limits, and available storage for images.
• Create a separate category for test imports so they do not get mixed with your primary content.
• Decide which post status you will use first: draft or pending is safer than immediate publishing.

In WordPress, WP-Cron does not run like a persistent system scheduler. It runs when the site receives visits. If the site gets low traffic, a scheduled task may start later than expected. That matters for Auto Robot: if a campaign is set to check a source regularly but the site barely gets any visits, posts may appear at uneven intervals. On high-traffic sites, the opposite issue appears: overly frequent tasks can compete for resources with caching, backups, SEO plugins, and image imports.

Safe starting point: make your first run manual, with one campaign, one source, the draft post status, a small item limit, and logging enabled. Move to scheduling only after you have verified quality.

Editorial Preparation

Autoblogging often breaks down not because of the plugin, but because the editorial model is unclear. Before you configure a campaign, answer a few questions: whose material will you use, are you allowed to quote it, should you keep a source link, will you import full text or only excerpts, who reviews posts before publication, and which topics are off limits.

If the site is commercial, be especially careful with sources that provide full text, photos, and video. An RSS feed by itself does not mean you have permission to copy everything in full. In many cases, the more responsible approach is to import the headline, a short excerpt, an image only when the source allows it, and a clearly visible link to the original. That is also better for SEO. Google has repeatedly emphasized the value of content that adds original usefulness, analysis, experience, and extra context instead of merely retelling or mass-reproducing someone else's material.

Compatibility Check with Existing Plugins

Pay special attention to your SEO plugin, caching plugin, security tools, media library plugins, and the block editor. Auto Robot can create posts, assign images, change status, add categories, and run background tasks. Your SEO plugin will generate metadata for new posts, the caching plugin may clear pages, and security tools may restrict network requests or suspicious actions in the admin area.

If the site uses a plugin that automatically publishes to social media, do not enable it for your test category. Otherwise, one failed campaign may not only create posts but also broadcast them externally. At the beginning, exclude the test category from social sharing, sitemaps, push notifications, and social auto-posting.

Installation and First Look at the Auto Robot Admin Area

The official documentation describes two installation methods: uploading the ZIP archive through the WordPress admin area or manually uploading the plugin folder to wp-content/plugins. For most users, the first option is the right one. The manual method only makes sense if WordPress cannot upload the archive because of hosting limits or file size restrictions.

Installing Through the Admin Area

1. Extract the original archive if it contains a separate auto-robot.zip file inside.
2. In WordPress, open Plugins - Add New - Upload Plugin.
3. Select the actual plugin installation ZIP, not the full archive with documentation and extra files.
4. Click Install Now, wait for the installation to finish, and activate the plugin.
5. After activation, find the Auto Robot item in the left admin menu.

If WordPress says the archive does not contain a valid plugin, it almost always means the wrong ZIP was selected. Commercial plugins often ship as a master archive that contains the documentation, license files, and a separate installer. Auto Robot documentation specifically points to auto-robot.zip, and that is the file you need to upload through the WordPress installer.

Initial Check After Activation

Do not create a campaign immediately after activation. First, open the Auto Robot menu and go through the main tabs. The documentation describes Dashboard, Campaigns, Integrations, Activation, Settings, and Logs. The labels may vary slightly in your version of the interface, but the logic is the same: overview, campaign list, external APIs, global settings, status, and logs.

On the Dashboard tab, check for system warnings. Under Campaigns, make sure the list is empty or contains only the items you expect. Under Integrations, see which sources require API keys. Under Settings, look for campaign behavior, caching, template, and limit settings. Under Logs, verify that the log screen opens and will be available after the first test run.

Why It Is Better to Start Without Third-Party APIs

Auto Robot supports many source types, but the most sensible first test is RSS. The reason is simple: an RSS feed does not require complex authorization, it is easy to open in a browser or validator, and its errors are usually understandable. YouTube, Google Custom Search, Vimeo, Twitter, and Instagram APIs depend on external dashboards, tokens, quotas, platform rules, and sometimes changes in data access. If you start there, it becomes much harder to tell what actually broke: the plugin itself, the API key, the quota, the source settings, or a service-side restriction.

An RSS test validates the core behavior: whether the campaign can be created, whether the import runs, whether the category is assigned, whether the draft status is applied, whether the image is saved, and whether entries appear in the log. Once that simple scenario works, you can move on to API integrations.

Interface Map: Campaigns, Integrations, Settings, and Logs

Auto Robot is built around campaigns. A campaign is a set of rules that tells the plugin where to fetch data, how often to check the source, what posts to create, what status to save them with, who the author should be, where categories and tags should go, whether images should be imported, and how the post content should be formatted. If you think of a campaign as a "settings folder," the interface becomes much easier to follow.

Dashboard and Campaigns

Dashboard works as the starting point: this is where you will typically see an overview, quick links, and guidance for creating your first campaign. Campaigns is the working list. It lets you see which campaigns are active, which are published, and which can be deleted or edited. The product changelog specifically mentions campaign modes, campaign import/export, optimization for RSS and keyword campaign classes, and changes to scheduling logic. That tells you the campaign list is not a decorative screen. It is the central control point.

It is also useful to establish a campaign naming rule right away. For example: RSS - Industry News - Drafts, YouTube - Brand Channel - Videos, Search - Product Reviews - Pending. Each name should include the source, topic, and publication status. A few weeks later, that saves real time: from the name alone, you can tell which campaign can be run, which one should be disabled, and which one should not be touched without editorial review.

Integrations

Integrations handles connections to external services. Official Auto Robot documentation has separate instructions for the YouTube API, Vimeo API, Twitter API, Instagram API, Instagram session cookie, Flickr, Facebook, Google Custom Search API, and Google Custom Search Engine. Each source has different requirements: YouTube works through a Google Developer Console project with YouTube Data API v3 enabled, Twitter requires access tokens, the Instagram session cookie is tied to a browser session, and Google Custom Search requires both a search engine and an API key.

There is one important security rule here: do not paste shared or borrowed keys, do not store API credentials in project notes, and do not send them inside task text. The plugin admin area should only receive keys created by the site owner for that specific project. If a key is no longer needed, it is better to disable it in the service dashboard than to simply delete it from the plugin field.

Settings

Settings affects both campaign behavior and the plugin as a whole. The product page lists caching, source content word limits, post templates, content insertion before and after the post, image import, post status, post type, author, logging, and log cleanup. The exact interface items may vary by version, so this guide does not say "turn on this exact switch." Instead, it explains which setting groups you need to find and how to test them safely.

Start by checking global scheduling, caching, logging, and image behavior. If the plugin provides a general setting for request frequency or RSS caching, do not set it to the minimum interval without a reason. A shorter interval increases load, but it does not guarantee more high-quality posts. For most sites, stability matters more than aggressive frequency.

Logs

Logs is the main troubleshooting screen. The official product page states directly that the plugin adds logs for campaign runs and WP-Cron, shows log, info, warn, and error levels, and allows logs to be cleared. Do not disable logging during setup. Without it, it is hard to understand why a campaign did not create a post: there may be no new items, the source may be unavailable, the API may have returned an error, duplicate detection may have blocked it, the image may not have been saved, or WP-Cron may not have run.

Creating Your First RSS Campaign Without Putting the Site at Risk

An RSS campaign is the best first test because it checks the foundation of Auto Robot without involving complex APIs. The official "Setup Campaigns" documentation describes the sequence: open the campaign editor, choose the source type, add the RSS Feed URL, configure the schedule, post status, images, categories, and tags, then save and publish the campaign. Below is the practical version of that workflow, using safe starting values.

Goal of the Test Campaign

The goal of the first run is not to fill the site with content. It is to prove that the plugin can complete the chain of "source - rules - post - log" correctly. For that, one RSS source, a small item limit, and the draft status are enough. You should be able to see new drafts, understand how the title is built, where the image comes from, which categories are assigned, and what gets written to the log.

Choosing a Source

Use a source you are allowed to use and that is technically stable. A good RSS feed for testing opens in a browser and contains clear titles, dates, links, and descriptions. If the feed already shows an error in the browser, returns empty XML, redirects to a login page, or uses broken encoding, do not start with it. Find a stable feed first.

If you are using a news source, do not import full text without checking the site's rules. For testing, a title, excerpt, and link to the original are enough. If the source only provides a short summary, do not try to work around that with third-party methods right away. For the first run, clean mechanics matter more than full text coverage.

Campaign Setup

1. Open Auto Robot - Dashboard or Campaigns and choose Add New Campaign.
2. In the name field, enter the source, topic, and test status, for example RSS - Industry News - Draft Test.
3. For the source type, select RSS Feed if the interface offers multiple options.
4. Paste the RSS feed URL and save it without extra spaces.
5. For scheduling, choose manual run or a low-frequency check while the campaign is still being tested.
6. Set the post status to draft or pending.
7. Assign a separate test category and, if needed, a test tag.
8. Set a limit for imported items if that field is available.
9. Enable logging and save the campaign.

After saving, run the campaign manually if the interface offers that option. Do not change several settings at once if the result does not appear. First open Logs, then the WordPress post list, then the campaign itself. That order makes it easier to identify where the chain broke.

What Should Appear After the Run

In an ideal test, WordPress shows drafts in the selected category, the titles match the RSS items, the content looks as expected, the image is either assigned correctly or absent for a clear reason, and the log shows that the campaign ran successfully. If the plugin supports duplicate checking, running the same campaign a second time should not create identical posts unnecessarily.

Check three things right away. First, the link to the source material. Readers should be able to tell where the content came from, especially if this is a digest or aggregator. Second, the formatting. The automatically created post should look clean in the theme, without broken markup, oversized images, or scraps of technical text. Third, the status. If you selected draft, the post should not be visible to visitors.

Source Settings, APIs, and Scheduling: What to Enable Gradually

Once the RSS campaign works, you can move on to more complex sources. The product page lists social networks, YouTube, Vimeo, Flickr, Instagram, RSS, keywords, Google Suggest, Google Custom Search, and translation through the Google Translate API. The changelog also references updates to API integrations, YouTube cache behavior, Google Custom Search, and campaign modes. That tells you Auto Robot is designed for a wide range of sources, but every new source adds another dependency.

YouTube and Video Campaigns

For YouTube, official Auto Robot documentation states that a YouTube API Key is required. Google's documentation confirms that YouTube Data API v3 requires a Google account, a project in the console, API enablement, and quota awareness. In Auto Robot, video campaigns can import videos from channels, playlists, or keyword search, and the post template can use special variables such as {{video_embed}}, {{video_title}}, {{video_description}}, {{video_duration}}, and thumbnail URLs.

In practice, that means a video campaign needs stricter controls than RSS. If you import videos using a broad keyword, the results may include irrelevant content, duplicates, outdated material, or videos that do not fit the brand. It is safer to start with a specific channel or playlist where you already understand the subject matter.

What to Check in a YouTube Campaign

• The API key was created for a project owned by the site owner.
• YouTube Data API is enabled in Google Cloud Console.
• The campaign uses a narrow source: a channel, playlist, or precise keywords.
• The post template does not create an empty block when a video has no description or thumbnail.
• The run frequency does not consume quota unnecessarily.
• The result is initially saved as draft or pending.

If a YouTube campaign is not working, do not start by changing the template, schedule, and key all at once. First check the log to see whether there is an API error. Then open Google Cloud Console and confirm the service is enabled and the quota has not been exhausted. After that, review the source itself: does the channel exist, is the playlist public, and are the search parameters correct.

Google Custom Search and Keyword Campaigns

Auto Robot supports keyword-based campaigns and Google Custom Search settings. Google states that the Custom Search JSON API requires a configured Programmable Search Engine and an API key, and it also has limits and customer transition conditions. Because of that, these campaigns should be used carefully. They are helpful when you need to find material on a specific topic, but the quality of the results depends heavily on the search engine, domains, language, and filters.

For testing, do not use a single broad word. Instead, start with 3 to 5 narrow phrases tied closely to your site's subject. If the plugin offers suggestions through Google Suggest, treat them as idea starters, not as an automatic publication list. Broad keywords usually produce noise. A narrow phrase with a niche name, city, product, or category yields fewer posts, but a much higher chance of relevance.

Instagram, Twitter, Vimeo, Flickr, and Other Sources

Official Auto Robot documentation for the Instagram session cookie shows a separate workflow for obtaining the sessionid value through browser developer tools. That method is security-sensitive because the cookie is effectively tied to a user session. Use it only if you understand the risk, never share the value with third parties, and disable the source if the account is no longer needed for imports.

For Twitter, Auto Robot documentation lists Access Token and Access Token Secret. For Vimeo, it lists an API Key on the integrations page. Flickr and Facebook also have dedicated documentation pages. The overall logic is the same: first create and verify the key in the service dashboard, then paste it into Integrations, then create a small test campaign, then check the log. Do not try to connect five services at the same time. That only makes troubleshooting harder.

Scheduling and WP-Cron

The official product page says Auto Robot uses WP-Cron to run campaigns automatically in the background. WordPress documentation explains the key nuance: WP-Cron checks tasks on page loads and does not behave like a persistent system cron. So a campaign schedule is not a guarantee of an exact start time. It is a rule WordPress will execute at the next available opportunity.

For a low-traffic site, that means a campaign may run later than expected. For a high-traffic site, it means too many tasks can create extra load. A good practice is to begin with one source and a low-frequency schedule, then add campaigns gradually. If the site gets few visits, discuss a system cron setup for WordPress with your hosting provider or developer. But do not do that blindly inside the plugin and do not change server-side tasks without understanding the consequences.

Post Templates, Images, and Duplicate Protection

The post template determines what readers see after an import. The CodeCanyon page lists video shortcodes, content insertion before and after the post, source text word limits, featured image support from feeds and Instagram, and selection of post type, status, and author. This is where Auto Robot becomes more than a simple importer and starts acting like an editorial tool. A weak template creates repetitive pages. A strong one helps the reader understand the context and reach the original source.

How to Design a Post Template

Start by deciding what kind of post format your site needs. For a news digest, a title, short excerpt, source, and link to the original are usually enough. For a video roundup, you want the embed, title, short description, and category. For a resource catalog, you may need a card-like structure with source, date, author, tags, and a note explaining why the item was included. Do not try to force every source type into one template.

If the plugin provides "before content" and "after content" fields, use them carefully. At the top, you can add a short note saying the item was imported from an external source and should be reviewed by an editor if it is still a draft. At the bottom, you can add a source link and a short editorial note. Do not inject aggressive promotional blocks into every automated post without checking how they fit the theme and layout.

Example of a Safe HTML Snippet for a Source Note

If the plugin interface allows HTML in the template, you can use a small block without scripts or external code. This is not an Auto Robot hook. It is just standard markup for a template field that supports HTML:

<p class="source-note">
  Material imported from an external source. Before publishing, check the headline,
  image, original link, and compliance with the site's editorial rules.
</p>

The test is simple: save the template, run one test post as a draft, open the preview, and make sure the block does not break the layout. The rollback is simple too: remove the snippet from the template and recreate the test post or edit the existing one manually.

Images and the Media Library

Auto Robot can assign a featured image from a feed or Instagram, and the changelog mentions saving remote images to the media library. That is convenient, but it can also consume disk space quickly. If every campaign downloads images automatically, the media library will grow faster than expected. Before enabling image import, check the average image size from the source, how your theme crops thumbnails, and whether every post actually needs that visual.

For the first test, enable images in only one campaign. If the source does not provide an image, it is better to use your own category placeholder than to try importing a random file. If the image is pulled from an external site, verify whether it is stored in the media library or left as an external URL. For site stability, it is usually better to store allowed images locally, but only if that complies with the source's rules.

Duplicate Checking

The product page mentions advanced options for checking and preventing duplicate content. In a real setup, this is one of the most important areas. Duplicates can appear if the source changes URLs, an RSS feed serves the same item with different parameters, a campaign runs twice, a keyword search finds material that was already imported, or several sources cite the same story.

After the first run, perform a second run of the same campaign without changing the source. If the plugin creates the same posts again, look for duplicate-check settings: by URL, title, RSS unique identifier, content hash, or whatever matching signal the interface exposes. If there is no exact switch, reduce the risk operationally: use draft, manual review, a separate category, a low item limit, and remove junk before publication.

Practical check: a test campaign is only ready for scheduling after two consecutive runs without unexpected duplicates, broken markup, or unwanted published posts.

Practical Example: An Industry News Section Built as Drafts

Let us look at a concrete scenario. The site has an industry news section. The team wants to pull material from several trusted RSS sources, but publish it only after editorial review. Auto Robot's job is to create drafts with the correct category, source link, clean template, and execution log. This is a realistic example because it does not require complex APIs and does not risk exposing unreviewed content to visitors right away.

Goal

Create an automated stream of drafts in the "Industry News" category. Each post should have a clear title, short body content, a link to the original, a bot author or dedicated editorial user, the draft status, a test tag, and a corresponding entry in the Auto Robot log. After review, the editor either refines the material manually or deletes it.

Preparation

Create a separate category, for example "Industry News - Imported." If the site is already indexed, temporarily exclude this category from the sitemap or simply avoid publishing the content until it has been reviewed. Create a dedicated author account, for example Content Import, so it is obvious in the post list which items were created automatically. Choose one RSS source that you are allowed to use in digest format.

Check the RSS URL in a browser. If it opens as XML or a valid feed, you can continue. If you see a regular page, an error, a CAPTCHA, or a login redirect instead of a feed, that source is not suitable for the first test.

Setup Steps

1. Open Auto Robot - Campaigns and create a new campaign.
2. Name it RSS - Industry News - Drafts so its purpose is obvious in the list.
3. Select RSS Feed as the source type and paste the feed URL.
4. Choose manual run or a low-frequency schedule if manual mode is not available.
5. Set the post status to draft.
6. Leave the post type as the standard post unless the site has a separate custom post type for news.
7. Assign the author Content Import or another dedicated user.
8. Select the "Industry News - Imported" category and add the import-test tag.
9. For images, start with the safest option: do not download unknown files unless you are sure the source allows it.
10. In the template, add a short source note and a place for the original link if those variables are available in the interface.
11. Save the campaign and run it manually.

Checking the Result

After the run, open the WordPress post list and filter by category or author. You should see new drafts, not published posts. Open one draft in the editor. Check the title, body content, link, category, tags, image, and author. Then open the public preview and evaluate the layout: look for empty blocks, strange symbols, duplicate headings, oversized images, or repeated phrases.

Next, open Auto Robot - Logs. The log should contain messages about the campaign run and the result. If the log shows a warning, do not ignore it. A warning may be harmless, but it is often the clue that explains why the import only partially worked. For example, the source may be available but the image failed to download, or the post may not have been created because duplicate detection blocked it.

One Important Detail: How to Keep Drafts from Turning Into a Junk Queue

Automated drafts still require discipline. If a campaign creates dozens of items every day and the editor cannot keep up with the review workload, the database will fill up fast. Set an item limit, remove old drafts, disable weak sources, and do not add a second source until the first one has proved useful. Good autoblogging is a controlled flow, not endless post accumulation.

Quality Control, SEO, and Legally Careful Publishing

Content automation is especially sensitive to quality. If a site publishes other people's material without adding value, that does not become a useful guide, news page, or expert section. Google recommends focusing on content created for people, offering independent value, showing real experience, and avoiding mass-produced pages built only for search traffic. In the context of Auto Robot, that means the plugin can help gather raw material, but the final page still has to be clear, accurate, and useful.

Editorial Review of a Single Post

Before publishing a draft, go through a short checklist. Do not treat it as a formality. Automated posts tend to repeat the same kinds of mistakes: a truncated title, an unsuitable image, an empty description, a duplicated source, a broken link, the wrong category, broken encoding, or too much copied third-party text.

• The title makes sense on its own and does not look like a broken RSS fragment.
• The post includes your site's own explanation, not just someone else's excerpt.
• The source is attributed correctly, the link opens, and it leads to the original.
• The category and tags improve navigation instead of creating chaos.
• The image is licensed for use or disabled.
• The post does not duplicate material that has already been published.
• The SEO plugin did not generate a meaningless title or description.
• The page looks normal on a mobile screen.

How to Add Original Value

The simplest way to make an aggregated post useful is to add editorial context. For example, before linking to a news item, explain why it matters to your audience, what conclusions can be drawn, which related materials already exist on the site, and where the reader should start. For a video post, add a short summary, say who the video is useful for, and point out which parts are worth watching first. For a news roundup, group material by topic instead of publishing every link as a separate empty post.

If the site still uses automatic publishing without manual review, limit it to safer types of content: your own RSS feeds, partner sources with permission, internal company news, demo material, or sources that explicitly allow republishing. In all other cases, keep the status as draft or pending.

Duplicates, Canonical Handling, and Indexing

When several pages contain the same or nearly the same material, search engines may choose the canonical version on their own. This matters even more for aggregators: if your site adds no value and simply copies the source, it is unlikely to become the preferred version. Technically, you can use canonicals, noindex on utility pages, exclude test categories from the sitemap, and apply manual editing, but those measures do not replace substance.

A practical approach is this: do not index test imports, do not auto-publish drafts, give final pages their own context, and keep source links intact. If a piece of content is only needed as an internal feed for the editor, do not publish it at all. If you need a public digest, make it a digest, not a copy.

Performance, Caching, and Campaign Maintenance

Auto Robot can use caching, scheduling, and background tasks. The product page mentions a caching system and configurable RSS cache time. This is an important area because autoblogging affects not only content, but also the database, media library, HTTP requests, task scheduling, and page cache.

How to Choose an Update Frequency

The frequency should match the actual value of the updates. If a source publishes one item per day, there is no reason to check it every few minutes. If a source is very active but the site only publishes a digest, it is better to import fewer items and review the result manually. Frequent checks can consume API quotas, create unnecessary requests, and fill the log without providing any benefit.

For the first week, keep the number of campaigns low and the schedule conservative. Then look at the numbers: how many posts are created, how many the editor actually publishes, how many get deleted, which sources generate junk, which create duplicates, and where errors happen most often. Use that data to decide what to speed up and what to disable.

Cache Behavior and Page Clearing

If the site uses page caching, new posts may appear in the admin area but not immediately show up in public lists. That is not necessarily an Auto Robot issue. Check whether the category archive updates, whether the main blog page updates, whether the latest-posts block refreshes, and whether the sitemap changes. If the caching plugin can purge cache when a new post is published, make sure it reacts to automated posts the same way it reacts to manual ones.

Do not disable all caching because of one campaign. It is better to tune the rules precisely: use a lower run frequency, clear only the necessary archives, exclude the test category, and publish manually after review. If the import creates drafts, public cache usually should not change at all until the post is actually published.

Logs and Database Maintenance

Logs help diagnose problems, but they also take up space. The product page mentions a log cleanup option. During setup, keep logs long enough to see the history of campaign runs. Once your campaigns stabilize, create a maintenance routine: delete old logs, remove unused drafts, review the media library, disable dead sources, and audit API keys.

If a campaign becomes slow, do not start by raising PHP limits. First reduce the number of sources, temporarily disable image imports, lower the item limit, check the log, run one campaign manually, and see where the delay occurs. More resources only help when the campaign logic is already clean.

How to Manage Multiple Campaigns Without Losing Control

After a successful first test, the usual temptation is to add more sources. That is natural: once one RSS feed works, it is easy to want five more feeds, a YouTube channel, keyword search, and a social source. But this is also the stage where autoblogging most often becomes unmanageable. Auto Robot can handle multiple campaigns, and the product changelog mentions campaign import/export, optimized campaign modes, logs, notifications, and task-class improvements. So the plugin is built for systematic work, but the administrator needs a system too.

The biggest mistake is creating campaigns on the principle of "one source, one automatic publication" without any overall map. A month later, the admin area is full of similar tasks, nobody remembers which one is a test, which one is live, where publish is enabled, where draft is enabled, which API keys are being used, and why a certain category suddenly filled up with nearly identical material. To prevent that, create a simple campaign matrix before you scale up.

Campaign Matrix

The matrix does not have to be complex. A table in project notes or an internal document is enough. For each campaign, record the name, source type, source URL or identifier, category, post status, schedule, author, item limit, whether image import is enabled, who is responsible for review, the date of the last audit, and the disable criterion. Visitors do not need this information, but the site owner does. Otherwise, the plugin turns into a black box.

A table like this helps you make decisions without guesswork. If a source generates lots of errors or the editor only publishes one item out of twenty, the campaign is not working. If the source is stable, produces useful drafts, and does not create duplicates, then it is worth keeping and gradually improving the template.

Grouping by Trust Level

Split campaigns into three groups. The first group contains trusted sources where automatic publishing may be allowed after a long testing period. The second group contains working sources that should always go to draft or pending. The third group contains experimental sources that should only be run manually and should never feed public categories.

The first group should have the strictest standards: stable source, clear usage rights, no duplicates, clean image handling, predictable publication frequency, log monitoring, and a fast way to disable the campaign. For the second group, good-quality drafts and a clear editorial review process are enough. For the third group, automatic publishing, social distribution, and public notifications should never be enabled.

Do not mix trust levels inside the same category. If one category contains original articles, experimental imports, and automatically published news all together, the editor quickly loses visibility. It is better to use separate internal categories that can later be merged manually or used only for admin-side filtering.

What to Do with Campaign Import and Export

The Auto Robot changelog mentions campaign import/export. That is useful if you need to move settings between staging and production or save a working configuration before experimenting. But a campaign export is not a full site backup. It does not replace the database, media library, API keys, settings from other plugins, or WordPress categories.

Use export as a snapshot of your Auto Robot rules, not as your only recovery mechanism. Before making major campaign changes, back up the site, then export the campaigns, then change the settings. If the new setup starts creating duplicates or errors, recovery becomes much easier: you can restore the site or reapply the previous campaign rules.

How to Audit Campaigns

Campaign review should happen at least as often as plugin updates. On a regular schedule, open the campaign list and ask five questions about each one: is the source still useful, does the material still pass editorial review, are duplicates appearing, is the log filling with errors, and have the API policy or source-site policy changed. If the answer is negative, the campaign should be disabled, narrowed, or moved back to drafts.

Pay special attention to older keyword campaigns. Search results change, source sites in the results change, newer sites push older ones out, and broad phrases tend to generate more junk over time. If a campaign was created "just as an experiment" and never reviewed again, do not leave it enabled just because it once worked.

Campaign Modes, Keywords, and the Post Template as an Editorial Mechanism

What makes Auto Robot interesting is not just its ability to run sources on a schedule. It also provides a campaign editor, keywords, templates, status selection, author assignment, categories, tags, images, and logic for processing source material. When you combine those settings, you no longer have an "automatic copier." You have an editorial mechanism. It determines which input signal turns into which post and what checks must happen before publication.

Smart and Expert Approaches to a Campaign

The product changelog mentions smart and expert campaign modes. Even if your version of the interface looks different, the idea is still useful: a simple setup works well for a first run, while advanced settings are for precise control. New users often want to open every parameter immediately, but that does not always help. If you do not understand what a field changes, it is better to start with the simple scenario and lock down a working baseline first.

The simple mode is useful for validating the source: URL, source type, status, category, and schedule. The advanced mode becomes useful once you know exactly what needs adjusting: the post template, word limit, image handling, keywords, post type, author, duplicate checks, translation, or API parameters. That order reduces risk because you are changing one block at a time instead of the whole pipeline at once.

Keywords as a Filter, Not a Junk Magnet

The product page mentions keyword campaigns, long-tail keywords, and suggestions through the Google Suggest API. That can be useful for finding topics, but it should not turn into a mechanical dump of every popular phrase. In autoblogging, a keyword is an intent filter. It should select material that truly belongs on the site.

A poor example is a broad phrase like "WordPress." It will return a lot of material, but most of it will not be relevant to your actual goal. It is better to use narrower phrasing: the niche name, product type, region, content format, specific source, or a combination of topic and audience. The more precise the keyword, the fewer posts you get, but the greater the chance that the editor will not end up deleting nine out of ten.

After launching a keyword campaign, look not only at how many posts were created, but also at the quality of the selection. If the campaign generates many irrelevant drafts, do not expand the keyword list. Do the opposite: narrow it, add exclusions, change the source, or switch to manual runs. Automation should help the editor, not test their patience.

The Post Template as a Place for Context

The post template in Auto Robot allows you to insert elements before and after the content, use source variables, and define the structure of the post. The product page lists video shortcodes for YouTube campaigns, including embed, URL, title, description, duration, views, likes, and thumbnails. For RSS and other sources, the available variables may differ, so work only with the tokens visible in your version's interface or documentation.

The template should answer three questions: where the material came from, why it is here, and what the reader should do next. If it is a news item, it needs the source and a short editorial comment. If it is a video, it needs the embed, a brief description, and a category. If it is a keyword-based roundup, it needs topical context and a relevance check. Without that, an automated post just looks like a raw import.

Mini Template for a Draft

For drafts, you can add a short internal note at the top that the editor will remove before publication. It should not appear in public posts if you publish automatically. Example:

<p class="source-note">
  Draft created by Auto Robot. Before publishing, check the source,
  duplicates, image, category, and add your own editorial context.
</p>

This snippet does not depend on the plugin's internal functions. It simply supports the workflow if the template field accepts HTML. When the post is ready for publication, the editor can remove the block or replace it with a public source note.

Checking Results with the Input -> Product logic -> Output Chain

For every important campaign, it is useful to define a short validation chain. Input is the specific source, keyword, channel, or RSS feed. Product logic is the Auto Robot rule set: campaign type, schedule, template, status, duplicate filter, image handling. Output is the resulting draft, post, video post, or custom post type entry. After that come verification, failure symptom, and fix.

For example, for an RSS campaign, the input is one feed URL. The product logic is draft status, the "Imported" category, an item limit, and no auto-publishing. The output is WordPress drafts. Verification means 2 to 3 posts appear, there are no duplicates, and the source link opens correctly. The failure symptom is either no posts or duplicated posts. The fix is to check the URL, log, campaign status, duplicate check, and WP-Cron.

For a YouTube campaign, the input is a channel or playlist. The product logic is a YouTube API Key, a template with embed and title, a low-frequency schedule, and pending status. The output is video posts. Verification means the embed works, the description is not empty, the thumbnail is correct, and quota use is reasonable. The failure symptom is an API error, an empty embed, or irrelevant videos. The fix is to check the key, YouTube Data API enablement, the source, the template, and the schedule frequency.

This kind of chain brings discipline to the setup process. It forces you to define the expected result before you hit run instead of guessing after something fails. On a more complex site, you can keep a separate card for each campaign next to the source matrix.

Common Auto Robot Problems and How to Diagnose Them

Problems in Auto Robot usually come from one of five places: the source, the API key, the schedule, the post template, or site-level restrictions. Do not try to fix everything at once. Work through the chain: does the source exist, can the campaign see it, does the task run, is the post created, and what does the log say.

The Campaign Does Not Create Posts

Symptom: you saved and ran the campaign, but nothing appears in the WordPress post list.

Possible causes: an empty source, an incorrect RSS URL, the campaign is not published, the selected status or post type is not the one you are checking, duplicate protection blocked it, WP-Cron did not run the task, or the API returned an error.

Check things in order. Open the source URL in a browser. Then check the campaign status under Campaigns. Next open Logs and look for warn or error level entries. After that, open the WordPress post list and filter by author, category, draft, and pending status. Often the posts were created, but the user only looked under published posts.

The fix depends on the cause: replace the URL, enable the campaign, relax restrictions, update the API key, change the status to draft, or temporarily disable duplicate checks for testing. If a post appears after the change, restore the protective settings and repeat the test with the correct source.

Duplicates Appear After Every Run

Symptom: the same item gets imported again even though the source has not changed.

The cause may be that the source serves different parameterized URLs, does not provide a stable GUID, changes titles, or that multiple campaigns are watching the same feed. Check whether two similar campaigns exist. Run only one. Compare what differs in the duplicates: URL, title, date, image, or text fragment.

Look for duplicate-check settings in the campaign or global options. If the interface allows matching by link, title, or content, choose the most stable signal for that source. If there is no precise control, keep the status as draft, limit the item count, and remove any source that constantly creates duplicates.

WP-Cron Does Not Run Campaigns on Time

Symptom: manual runs work, but scheduled runs miss their expected time or behave irregularly.

WP-Cron depends on site visits. If traffic is low, the task may start late. If WP-Cron is disabled and no system cron is configured, tasks will not run as expected. Check whether other plugins' scheduled tasks work, whether Auto Robot logs show activity, and whether background tasks have been disabled in WordPress configuration.

Fix: reduce the number of campaigns, use a more realistic interval, review the system cron setup with your developer or hosting provider, and keep manual runs for important imports. Do not increase the frequency until you have confirmed that the current tasks run reliably.

Images Do Not Save or Break the Layout

Symptom: the post is created, but the featured image is missing, too large, duplicated, or visually inappropriate.

Check whether the source actually provides an image in the RSS feed. Some feeds are text-only, some provide thumbnails, and some do not allow downloads. If the image comes from Instagram or another source, verify the integration and access rights. If the file is saved but looks bad, adjust image sizes in the theme and make sure the template is not inserting the image twice: once as the featured image and again inside the post body.

A safe fix is to temporarily disable image import, use your own category placeholder, or keep posts as drafts until an image can be chosen manually. If the source does not provide good images, do not try to force the plugin to guess them.

An API Source Returns Errors

Symptom: RSS works, but YouTube, Google Custom Search, Twitter, Vimeo, or another API-based source does not create posts.

First check the Auto Robot log. Then open the service dashboard and confirm the API is enabled, the key still exists, the quota is not exhausted, and access is allowed for the correct project. For YouTube, YouTube Data API v3 must be enabled. For Google Custom Search, you need both a Programmable Search Engine and an API key. For Twitter and Instagram, platform restrictions may change over time, so older instructions may need a current verification.

Fix: update the key, enable the required API, lower the campaign frequency, narrow the query, and test the source manually. If the platform changed its access rules, do not work around those restrictions. It is better to disable the campaign temporarily and document the reason.

Automated Posts All Look Too Similar

Symptom: the site fills up with similar-looking pages containing borrowed fragments and very little value.

This is not a technical bug. It is an editorial-model problem. The plugin did what it was told, but the site did not end up with useful material. The fix is not a new API. It is structural: use draft, apply manual editing, add original introductions, publish thematic digests instead of one-off copies, keep source links, limit sources, and stop publishing weak material.

Safe Improvements Without Editing the Plugin Core

Auto Robot should not be modified inside the plugin files. That is poor practice: an update will overwrite your changes, and a coding mistake can break imports. Safe improvements should live in the theme, child theme, a CSS plugin, Code Snippets, or Auto Robot's own settings. Below are only small, reversible techniques that do not depend on internal plugin hooks.

Visual Marker for Imported Posts

If you added the source-note class to the post template, you can style it with CSS in a child theme or a safe Custom CSS field. This helps both editors and visitors distinguish aggregated material from the site's original articles.

.source-note {
  border-left: 4px solid #f59b22;
  padding: 12px 14px;
  background: #fff7ec;
  font-size: 0.95rem;
  line-height: 1.5;
}

Check: open the preview of an imported post and make sure the block does not overlap the content and looks fine on mobile. Rollback: remove the CSS and refresh the page after clearing cache.

Editorial Status Instead of Full Automatic Publishing

The strongest no-code improvement is to use draft or pending as the permanent mode for questionable sources. Let Auto Robot gather drafts, and let the editor decide what should be published. Later, for fully trusted sources, you can create a separate campaign that publishes automatically, but do not mix it with test streams.

Separate Authors and Categories

Create a separate author for automated imports and separate categories for each major source or campaign type. This is not just about keeping the admin area tidy. It also makes it easier to control indexing, review metrics, find errors, remove failed batches, and understand which source is actually providing value.

When CodeCanyon Auto Robot Is a Good Choice

CodeCanyon Auto Robot is worth using if you need a manageable pipeline for RSS, media sources, API campaigns, post templates, scheduling, and logging inside WordPress. It is especially useful for news sections, topical digests, video roundups, demo sites, and draft workflows that an editor later turns into publishable material.

The plugin should not be treated as a "build me a content site" button. Without clear sources, rules, duplicate checks, a careful template, and editorial control, it will create more problems than value. Start with one RSS campaign, the draft status, a separate category, and logging. After you verify the results, add API sources, scheduling, images, and more advanced templates.

If the test makes it clear which sources you want to use, how posts will be reviewed, and how automatic publishing will be limited, you can get the WordPress version and deploy it on a test copy of the site. From that point on, the main rule is simple: every campaign should produce material that helps the reader, not just increase the number of posts in WordPress.

Video on Setting Up CodeCanyon Auto Robot

This video complements the guide: a product-specific walkthrough. Open it after the basic setup to compare the interface and the sequence of actions.