CodeCanyon WordPress Automatic Plugin - WordPress Plugin

Guide to Setting Up CodeCanyon WordPress Automatic Plugin for Automated Imports and Post Review

CodeCanyon WordPress Automatic Plugin is not meant for dropping someone else's feed onto a page one time. It is built for structured, manageable campaigns: the plugin pulls content from a selected source, transforms it according to your rules, creates WordPress posts, and runs the process on a schedule or manually. In this guide, we will look at it as a practical workflow tool, not as a "build a site automatically" button.

This guide follows a practical path: what to check before installation, how to create your first safe campaign, which settings to enable only after testing, how to use post templates and filters, how to review the results in the WordPress admin and on the live front end, and what to do if new posts do not appear or the import comes in messy.

We will also look at where the product is genuinely useful and where a narrower RSS aggregator or a manual editorial workflow is the better fit. With automated imports, copyright, source quality, hosting load, and SEO risk matter a great deal, so this guide does not promise instant site growth or treat automation as a replacement for editorial review.

When automated importing actually helps a site

This plugin makes the most sense when content arrives regularly and can be described by rules. Typical examples include an industry roundup, a job board, an affiliate product catalog, a video section, topic-based news monitoring, or a supporting draft area for an editor. In those cases, what matters is not the "magic" of automation but a repeatable flow: the source provides data, the campaign pulls only what you need, and WordPress receives a post in a predictable format.

The most common beginner mistake is turning on auto-publishing right away on a live site. Automated imports can create a large number of posts very quickly, and if the source is weak, the site ends up with duplicates, broken text fragments, unlicensed images, empty listings, weak headlines, and pages with no editorial value. That is why the first run is best kept in draft status, with a small post limit and a clear review process.

CodeCanyon WordPress Automatic Plugin is a good fit for users who are willing to manage rules: choosing sources, configuring the post template, filtering words, checking images, assigning categories, and monitoring campaign logs. It is less appropriate for sites where every post must be an original article with manual expertise, complex formatting, legal review, or a highly distinctive editorial voice.

Scenarios where the plugin makes sense

• A news or niche site that needs drafts pulled from RSS feeds for later editing.
• An affiliate project that imports products or offers from supported sources, while the site owner reviews links and listings.
• A media section that needs to pull in videos, images, or posts from an external service on a regular basis.
• A content lab where AI Articles are used to generate drafts from a list of topics, not for thoughtless bulk publishing.
• A staging environment where the webmaster tests sources, templates, and filters before moving rules to the main site.

Scenarios where automation should not be your starting point

If your site depends on expert content, personal experience, legally sensitive material, or medical or financial guidance, automated importing should not become the main publishing method. In those niches, the plugin can help collect raw material, but the final text still needs full editorial and factual review.

Practical rule of thumb: if you cannot explain what rules determine whether a post belongs on the site, which category it should go into, and how an editor will know the result is good enough, the campaign is not ready to run on a schedule.

How campaigns, sources, and post templates work

The core of the plugin is the campaign. A campaign is a separate configuration where you define the source type, keywords or URL, limits, title template, content template, categories, tags, post status, update frequency, and additional processing rules. This model is convenient because it keeps different flows separate: an RSS roundup does not get mixed with AI Articles, a YouTube campaign does not use product-import rules, and a test campaign does not affect a production one.

In ValvePress documentation, the main campaign screen is described as a set of repeating fields: campaign title, manual run, campaign type, keywords, key rotation, maximum posts, title template, publication status, and interval-based updates. That makes it easier to think in terms of a chain rather than a list of buttons: source - processing - post - review.

The source determines what data is available

An RSS feed usually includes a title, link, date, short description, and sometimes an image. YouTube or a marketplace provides a different set of fields. With AI Articles, the input becomes keywords, prepared titles, or prompts. That means you cannot copy settings from one campaign to another and expect the same outcome. Every source should be tested with a small trial import.

The safest path is to start with a source you already understand: your own site's RSS feed, an open partner feed with republishing permission, a test YouTube channel, or an AI campaign that saves everything as drafts first. After that, you can move on to more complex sources such as multi-page scraping, marketplaces, and integrations that require external keys.

The post template turns data into a page

The plugin supports content templates with tags like [post_title], [post_content], and other placeholders that vary by campaign type. This is a powerful feature, but it is also where results often go wrong when used without a plan. A good template does not just dump everything into the post. It creates a clear structure: introduction, main content, source link, image, and an extra block for a warning or editorial note.

For your first template, avoid complex layout work. A title, the main text, a clean source link, and a simple note for the editor are enough. Once you know the source is stable, you can add categories, tags, custom fields, and more advanced HTML.

Filters help block junk, but they do not replace an editor

The documentation describes banned words, must exist words, search and replace, skipping posts without content, skipping posts without images, and similar rules. These settings are useful when the source is predictable. For example, you can filter out items with no image or posts that do not contain a key term from your niche. But a filter does not understand context the way an editor does: it may let a weak post through because it includes the right word, or remove a valuable post because of an accidental match.

What to check before installation and the first launch

Before installing the plugin, prepare not just WordPress but the editorial workflow around it. Automated imports affect the database, media library, cron, SEO structure, access permissions, and how posts appear on the site. If the site is already getting traffic, testing is best done on a copy, or at least with a backup and a separate category that you can clear quickly.

Technical preparation

• Verify that you have a backup of the database and files before installing a new plugin.
• Make sure the administrator has access to hosting error logs, or at minimum to WordPress debug messages.
• Check that WordPress cron is actually running on the site. If the site gets little traffic, the internal cron may trigger inconsistently.
• Create a separate category for test imports, for example "Import - Review."
• Set new posts to draft or pending review until the campaign has completed several successful cycles.

Editorial and legal preparation

Automated importing does not remove responsibility for what gets published on the site. If a source provides only a short summary and a link, it is usually safer to show the brief description with a link to the original than to copy the full text. If the source allows republication, document that rule for the editor. If permission is unclear, use the material as a draft or roundup rather than a full copy.

From an SEO standpoint, mass-produced pages with duplicated text, repeated titles, empty images, and no reader value are especially risky. That is why you should think through canonical handling, the source link, publication status, and manual review before importing at scale. If you use imported content as raw material for an original article, that is a legitimate workflow. If the site simply republishes everything without selection, the risks go up.

Security and updates

The product has had public security advisories for older versions, including an SQL injection vulnerability that was fixed in an update. There is no need to discuss exploit techniques here, but the takeaway for administrators is simple: before installing, make sure you have a current archive and do not leave an outdated version on a production site. After updating, it is a good idea to review campaign logs, run a test import, and confirm there are no unexpected administrator accounts or modified files.

Installation, first run, and the control draft

Installing a commercial ZIP plugin in WordPress usually goes through Plugins - Add New - Upload Plugin. After activation, the plugin adds its own menu in the admin area, where campaigns are created and global settings are configured. We will not cover purchase, license activation, or downloading the archive here. The goal of this guide is to show a safe setup process for a product you already have.

The first run should answer one question: can the site create a clean, usable post from the selected source without junk or errors? That is why you should not enable multiple sources right away. Start with one simple option and keep the chain minimal.

Control checklist

1. Create a separate test category for imported content.
2. Add a new campaign and give it a clear internal name, for example "RSS test - supplier news".
3. Select the campaign type that matches the source: RSS, AI Articles, YouTube, or another confirmed option.
4. Enter one source or one small set of keywords without piling on dozens of rules.
5. Set new posts to draft status.
6. Limit the number of posts so the test does not flood the site.
7. Save the campaign and run it manually using the campaign run button.
8. Open the generated draft and check the title, text, image, category, source link, and formatting.

If the draft does not appear, do not rush to change everything at once. First check whether the manual run actually triggered, whether the plugin logs show anything, whether the source is accessible, whether the feed is empty, and whether a filter blocked the post.

Quick takeaway: the first successful result is not a published post. It is a clear draft you can open, read, and explain: where the title came from, why that category was assigned, where the source link is, and why the post is not just a duplicate.

Detailed post-install configuration: safe defaults and risky settings

After installation, it helps to split settings into three groups: required for the first run, useful after testing, and risky during bulk imports. That structure makes troubleshooting easier when a campaign produces poor results. CodeCanyon WordPress Automatic Plugin supports many sources and processors, but the configuration logic is usually the same: limit the input, shape the content to fit the site, save the result in a controlled status, review it, and only then speed up the process.

Post status and limits

For the first phase, use drafts. Auto-publishing only makes sense after several test runs, once you trust the source, template, images, and filters. A maximum post limit protects you from cases where one bad URL or an overly broad keyword creates hundreds of posts.

If you use multiple keywords, pay attention to rotation. By default, a campaign may keep processing the first keyword for a long time and only move on after exhausting it. Rotation is useful if you want a more even topic mix, but it can make troubleshooting harder because you need to know which specific query produced the result.

Categories, tags, and custom fields

Categories should help both the editor and the reader. For testing, do not import directly into the site's main category. Use a technical or review category instead, then move the content manually after checking it. Automatically adding keywords as tags is convenient, but broad queries can quickly create a messy taxonomy. Use that option only if your keyword list has already been cleaned up.

Custom fields are useful for the source, price, rating, author, or another structured element if the campaign type actually provides that data. But there is no reason to add dozens of fields up front. Start with one field such as "source_url" or its equivalent so the editor can see the original page and verify the material.

Title template and content template

Keep the title template short. If the source already provides a solid title, do not pile on automatic prefixes like the site name, category, and keyword all at once. Titles like that look mechanical and make the editor's job harder. For content, use a structural template with clear blocks.

<p>[post_content]</p>
<p><strong>Source:</strong> <a href="/[source_link]" rel="nofollow">original post</a></p>

This example needs to be adapted to the tags available in your specific campaign. The documentation makes it clear that the set of supported tags varies by source type, so do not copy a template blindly between RSS, YouTube, product, and AI campaigns. If a tag does not populate, remove it from the template and check the list of tags inside the campaign editor.

"Must exist" and "banned" filters

The must exist words filter is useful for a niche site. For example, if you import WordPress news, you can require a specific term to appear in the title or content. Banned words help exclude irrelevant posts. But it is best to add these rules only after the first successful import. Otherwise, you will not know whether the source is empty or the post was simply filtered out.

Search and replace is best used surgically: remove a recurring boilerplate block, fix a broken URL, or strip out a phrase that consistently comes from the source. If you find yourself writing long regular expressions for every item, the source is unstable and probably should not be connected to auto-publishing.

Scheduling, internal cron, and external control

The documentation describes WordPress internal cron and campaign update intervals. Internal cron depends on site visits, so if traffic is low, jobs may run late. For an important schedule, most admins use a server-side cron or an external scheduling service, but at the beginning, a manual run and a short test interval are enough.

An older ValvePress article about forcing frequent campaign runs explicitly warns that the plugin is designed for low resource consumption and processes a limited number of campaigns per minute. That is an important practical signal: do not speed things up with external reloaders on a production site. If you need a large initial import, do it on a staging copy, in small batches, and with load monitoring.

AI Articles, RSS, and scraper: how to choose the right campaign type

The product supports many source types, but for a new administrator it is more useful to think in terms of the job to be done rather than a list of integrations. Do you need to generate a draft from a topic, import published content from a feed, extract part of a page, or pull listings from a supported service? The answer determines not only the campaign type, but also how you should review the output.

AI Articles for drafts and content starters

Official ValvePress articles show the AI Articles workflow: create a campaign, choose the AI Articles type, add keywords or ready-made titles, configure prompts, and run the campaign. This is convenient for draft FAQs, roundups, descriptions, and supporting content. But AI mode requires its own discipline: fact-check the output, do not publish generated text without editing, and do not mix keys from unrelated topics in the same campaign.

If you use an external AI provider, do not store keys on sites where editors have overly broad permissions. We are not covering API keys or service billing here, but in a real setup it is important to limit access to the plugin's global settings and keep a record of which campaigns use generation.

RSS for roundups and controlled imports

An RSS campaign is a good fit for stable sources. The documentation describes several options: pulling content from the feed itself, attempting to fetch the full text from the original page, extracting blocks by CSS id/class, XPath, or REGEX, applying search and replace, and importing categories, tags, author, and image. That is powerful, but you do not need all of it on day one.

For a clean and legally safer roundup, a title, short description, image when available, and a source link are often enough. Turn on full-text import only when the source allows that kind of use and the result is genuinely useful to readers.

Scraper for targeted jobs, not "any site in one click"

Single-page and multi-page scraping are useful when RSS does not provide the data you need or when you need to monitor a specific block on a page. But this is the most fragile part of automation. The site markup can change, access can be restricted, and a regular-expression extraction can break because of a minor HTML edit. This type of campaign is best kept in draft mode and reviewed more often than a standard RSS workflow.

If the campaign uses APIFY, cookies, or access to authenticated pages, make sure that does not violate the source's rules or expose sensitive data where it should not be stored. In the finished site article, you should never reveal secrets or private tokens, and campaign settings should not rely on someone else's account without permission.

Practical example: building a safe RSS roundup and reviewing the result

Let us walk through a scenario that fits most sites: you want to pull content from a niche RSS feed on a regular basis, save the results as drafts, add a source link, and pass them to an editor for review. This example does not require secret keys and does a good job of showing how the product works in practice.

Goal

Create draft posts from a single RSS source so an editor can quickly choose useful items for a roundup. Nothing should appear on the public site until a post has been reviewed manually.

Preparation

• Choose an RSS feed that opens in a browser and shows fresh items.
• Create a test category for imported drafts.
• Prepare a simple post template with a link to the original source.
• Make sure the editor knows which posts are safe to publish and which should be deleted.

Setup steps

1. Open the plugin menu and create a new campaign.
2. Select the Feeds campaign type, if that is what your version calls it.
3. Paste one RSS feed into the sources field instead of a long list of URLs.
4. In the content settings, start with the option that pulls text from the feed itself rather than trying to fetch the full article from the source site.
5. Set the post status to Draft or the equivalent draft status.
6. Assign the test category and do not enable automatic creation of extra tags.
7. Add the main text and a visible source link to the content template.
8. Limit the number of posts for the first run and start the campaign manually.

Post-run review

Open the WordPress posts list and filter drafts by the test category. Make sure the title is readable, the text is not oddly truncated, the link points to the original publication, the image does not break the layout, and the post has not been published on the site. Then open the public draft preview and see how your theme displays the title, image, excerpt, and link.

If everything works, add one must exist words or banned words filter and run the campaign again with a small number of posts. That will show you how the filters affect the outcome. Do not add filters, full-text extraction, search and replace, translation, and auto-publishing all at once. If something fails, the cause will be much harder to isolate.

A common sticking point

If the feed provides only short summaries, that is not a plugin error. RSS can only deliver what the source publishes. You can try full-content extraction or CSS/XPath extraction, but first think through the legal and editorial side. For many sites, a short roundup with a source link is a better choice than building an unstable scraper for someone else's page.

Practical use cases for different site types

The same product can be used in very different ways. What matters is not copying settings between projects, but starting with the goal: what should the site's visitor get, and how much manual review is required? The examples below are not a list of every feature. They are practical workflows that naturally follow from the plugin's campaign-based model.

Editorial roundup

For a media site or blog, a campaign can pull material from several trusted sources into drafts. The editor selects the best items, writes their own commentary, adds internal links, and publishes only part of the imported stream. In that workflow, the plugin saves time on monitoring, but the final value is still created by the editor.

Video section with manual moderation

If the source is YouTube or another video service, the campaign can create drafts with the title, description, and embedded video when the source supports it. The review process is different here: you need to confirm the video is available, fits the site's topic, embeds correctly in the theme, and does not create an empty page with no context.

Affiliate or product collections

For marketplaces and affiliate sources, what matters is not just the title and image, but also whether the link is correct, whether the listing is current, and whether the price or specs are still accurate if you are displaying them. These campaigns should not be published without review because the external source can change its structure and product data becomes outdated quickly.

AI drafts for editors

AI Articles can be used as a structure generator: headings, FAQ sections, a brief topic summary, and a rough draft for later rewriting. In that case, the final article should not remain a machine-generated outline. The editor still needs to verify facts, add personal expertise, sources, images, and internal links. That approach is much safer than fully automated publishing.

Checking the result: where to confirm that a campaign is working properly

Result review should happen in three places: the WordPress posts list, the draft inside the editor, and the public preview. If the campaign uses images, check the media library as well. If it runs on a schedule, review the campaign log and the actual timestamps when posts were created.

Checking in the admin area

• In the posts list, check the status, category, author, and date.
• In the editor, review the title, main content, excerpt, featured image, and custom fields.
• Compare the original source link with what ended up in the post template.
• Check whether duplicates were created for the same item.
• Review the logs or the list of posted posts inside the campaign if your version shows that block.

Checking on the public site

The preview is not just for appearance. Sometimes the post is created successfully on a technical level, but the theme displays imported images poorly, a long title breaks the card layout, a video does not fit the content column, or the source link looks like ad clutter. It is better to catch those issues while the post is still a draft, before it is indexed or shared socially.

Checking SEO and indexation

If the imported material largely repeats an external source, add a clear link to the original and think carefully about whether the page should be indexed at all. The plugin documentation mentions a canonical option, but it should be used intentionally: canonical can point to the original, but it does not turn a duplicated page into unique content. For a site with a long-term SEO strategy, it is better to publish selected, revised, and expanded posts.

Quality check: a good automated post should make sense even without opening the admin area. The reader should be able to see the topic, source, context, and value. If the page looks like a random copy of external material, stop the process and rework the setup.

Why the import failed or produced poor results

Troubleshooting in CodeCanyon WordPress Automatic Plugin usually comes down to finding the weakest link in the chain: the source, a campaign rule, a filter, cron, the template, the media library, or the theme. Do not change everything at once. Take one symptom and walk through it step by step.

The campaign runs, but no posts are created

Symptom: the manual run completes, but no new drafts appear. Possible causes include an empty source, URLs that were already imported, overly strict filters, the wrong campaign type, or the post limit. First temporarily disable filters, reduce the template to the minimum, and test one source. If a post appears, add the rules back one at a time.

When to roll back a setting

If posts stop appearing after you enable banned words or must exist words, roll back that specific filter first. Do not touch cron or the template until you have confirmed that the source is actually returning material.

Posts are created, but the text is cut off or empty

Symptom: the title is there, but the content is thin or consists mostly of boilerplate. With RSS, that may mean the feed only provides an excerpt. With full-text import, the cause may be that the plugin could not find the right block on the source page. Check the original feed first, then try CSS id/class or XPath extraction on just one test item.

The image does not make it into the post

Symptom: the draft has no featured image, or the image breaks on the site. Common causes include the source not providing an image, the file being too small, the server blocking the download, the theme pulling the image from a different field, or the media library rejecting the file type. Check whether the image exists in the original feed item, whether it appears in the media library, and what URL is stored in the draft.

Scheduled automatic runs are inconsistent

Symptom: manual runs create posts, but scheduled runs happen rarely. WordPress internal cron depends on site visits, so it can lag behind on low-traffic projects. Check whether WP-Cron has been disabled on the host, and move to a server cron only after manual runs are stable.

Duplicates or too many similar posts appear

Symptom: the site receives multiple posts about the same event or several nearly identical listings. Check the rules for detecting already published items, the RSS "same title" setting, the post limit, and the keyword list. If the source itself produces duplicates, address that with filters and manual moderation, not by increasing the run frequency.

The public page looks worse than the draft in the editor

Symptom: the post looks fine in the admin area, but the card layout, image, video, or spacing breaks on the public site. At that point, you are dealing with the theme and the post template. Check the preview in a default theme or temporarily simplify the campaign HTML template. If the problem disappears, the conflict is in the theme layout or an overly complex content template.

Safe improvements without editing the plugin core

For this product, do not invent PHP hooks or internal APIs unless they are confirmed in the documentation. It is safer to work through campaign settings, templates, publication status, categories, and small theme-level CSS tweaks. The code below does not change WordPress core or interfere with the plugin itself. It simply helps you visually distinguish imported drafts if they have been assigned a separate category.

Add the CSS in Appearance - Customize - Additional CSS or in a child theme. Replace the category slug if your theme outputs it in the category-import-review class.

.category-import-review .entry-title::before {
  content: "Needs Review";
  display: inline-block;
  margin-right: 0.5rem;
  padding: 0.15rem 0.45rem;
  border-radius: 4px;
  background: #f4b942;
  color: #1f2933;
  font-size: 0.75em;
  font-weight: 700;
}

The check is simple: open the preview of a post from the test category and make sure a small marker appears before the title. If the theme does not add the category class to the post, the CSS will not work. In that case, roll the change back and use a standard marker in the draft title or a separate editorial status instead.

Another safe approach is organizational rather than code-based: use a dedicated import category, a separate author account for campaigns, and a rule that publication only happens after an editor changes the category. That is easier to maintain than complex snippets and does not depend on the plugin's internal functions.

A clear video walkthrough of an AI campaign

ValvePress has a focused video on the AI Articles workflow for WordPress Automatic Plugin: it shows campaign creation, selecting the AI Articles type, entering titles, and running the campaign manually. The video is most useful after reading the sections on a safe first run because it answers the practical "how do I use an AI Articles campaign?" question, but it does not replace editorial review of the result.

When watching the video, focus not just on the buttons but on the logic itself: a new campaign, a source type, input titles, and manual review. On a real site, add draft status, a post limit, and editorial fact-checking on top of that workflow.

When CodeCanyon WordPress Automatic Plugin is the right choice

CodeCanyon WordPress Automatic Plugin is worth using if you understand the source, can define clear import rules, are willing to test campaigns as drafts, and do not expect automation to solve your editorial strategy on its own. Its main strength is the wide range of sources and the flexible campaign model, which lets you separate RSS, AI Articles, scraping, video, and product workflows into distinct rule sets.

Before moving into production, follow a short sequence: one source, one campaign type, draft status, a post limit, a simple template, result review, then filters and scheduling. If the result still looks useful and manageable after that, you can download the ZIP archive and continue testing it in your own environment.

If all you need is simple RSS output, occasional imports of a few posts, or a fully manual editorial workflow, start with a narrower tool or skip automation entirely. The best choice is not the one with the longest feature list. It is the one that minimizes the risk of junk pages and gives you the most control over the final content.