Autoblogging AI Writer & Internal Linking

Autoblogging.dev runs two engines that feed each other. The Auto Writer generates full SEO articles on a schedule you set, and the Auto Linker turns every keyword it produces into a site wide internal link network. You can run either engine on its own.

The plugin ships in two versions, both carrying the same release number, currently 1.1.6. They generate identical articles and identical links. The difference is how updates arrive and whether the ad slot feature is present.

Switching between versions

You can move from one to the other without losing anything. Deactivate and delete the old copy, install the other one, then activate. Your API key, credits, settings and keyword index all survive because they live in your WordPress options and database table, not in the plugin files. Your published articles are untouched either way.

What activation does

• Checks your PHP version and stops with a clear message if it is below 7.4.
• Creates the keyword index table used by the linker.
• Schedules the writer, heartbeat and pending job checks.

Activation sends nothing to our servers. The first outbound call happens when you connect for your API key.

Everything below lives on one screen: AutoBlogging-DEV > Getting Started. The steps tick themselves off as you complete them.

1. Get your API key

   Click Connect. Your site URL and admin email are sent once, a key and secret come back, and both are saved for you. There is nothing to copy or paste.

2. Add credits

   New accounts start with 2 free credits, which is enough to see two complete articles before you spend anything. Buy more from Credits & API Key when you are ready.

3. Set up Auto Writer

   Choose your categories, pick a publishing frequency, decide between draft and publish, then turn the writer on.

4. Enable Auto Linker

   Flip the toggle and set a maximum number of links per post. If you already have published articles, run Rebuild Keyword Index once.

5. Add your article signature

   Optional. Paste a logo image URL and it is appended to the end of every generated article, using the focus keyword as alt text. Add a blog URL to wrap it in an internal link.

6. Add the server cron job

   Required. Copy the one line command from the Getting Started page into your host’s cron panel. The step confirms itself within one or two minutes of the first run.

Your API key identifies your site to the backend and carries your credit balance. It is issued automatically when you click Connect, and you will find it under Credits & API Key along with your account email, site URL, plugin version and detected SEO plugin.

What the key is used for

• Requesting an article generation job.
• Reading your current credit balance when you open a plugin admin page.
• Periodic validation, signed with an HMAC signature so the key alone is not enough to impersonate your site.

Found under AutoBlogging-DEV > Auto Writer. The master toggle at the top saves itself instantly and reschedules the cron event when you flip it.

Every successful generation produces a complete, publish ready post:

• Roughly 1800 to 2200 words, written to read conversationally rather than as obvious machine output.
• An H1 title, a table of contents, five or more H2 sections, an FAQ section and a conclusion.
• One focus keyword plus four secondary keywords, chosen by the generator.
• A meta description, written and saved into your active SEO plugin’s own fields.
• Your article signature image at the end, if you set one.
• Immediate indexing into the linker, so the article can both receive and send internal links straight away.

Images beyond the signature are not inserted automatically. Add featured images and in body images the normal WordPress way, either as you review drafts or afterwards.

Duplicate topics are the fastest way to waste credits and confuse a site’s topical structure, so the writer keeps a rolling memory. Before each generation it sends the most recent 200 keywords already used on your site, along with recent titles, and those are treated as forbidden ground for the new article.

• Both the focus keyword and all four secondary keywords are added to memory after each success.
• Recent titles are checked against your existing published, draft, pending and scheduled posts.
• A longer history is retained locally so the 200 keyword window keeps moving as you publish.

Signature image

Set once on the Getting Started page. Paste a direct URL to your logo or brand image and it is appended to the end of every generated article, with the article’s focus keyword as its alt text. If you also paste a blog page URL, the image is wrapped in a link to that page, which gives every article one consistent internal link back to your hub.

Paragraph spacing

A single number in pixels, applied site wide. Some themes set paragraph spacing tight enough that long articles feel dense. Setting a value here adds breathing room without touching your theme files. Leave it blank or set 0 to keep your theme’s own spacing.

Add this to your host’s cron panel, usually listed as Cron Jobs, replacing the domain with your own:

*/5 * * * * wget -q -O - https://yoursite.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1

The Getting Started page shows this line with your own domain already filled in, so copy it from there rather than editing by hand. A five minute interval is right regardless of your publishing frequency. The cron simply asks WordPress whether anything is due.

Confirming it works

• The cron step confirms itself automatically within one or two minutes of the first run, and turns into a tick.
• After that it keeps monitoring, and warns you if the cron has not fired in the last 30 minutes.
• If your host offers a minimum interval longer than five minutes, use the shortest they allow.

Test page

AutoBlogging-DEV > Test generates one article immediately, ignoring your schedule and the on and off toggle. It uses one credit and it obeys your draft or publish setting, so it is the fastest way to check quality, formatting and SEO meta before committing to a schedule.

Activity log

AutoBlogging-DEV > Activity Log records every queue, success and failure with the category, article title and credits remaining. If something is not behaving, this is the first place to look. There is a clear button when it gets long.

Generation is asynchronous. A run queues a job, and a background check picks the finished article up shortly after, which is why the log usually shows a “queued” line followed by a “success” line a little later.

The linker runs independently of the writer. It works on articles you wrote by hand just as well as on generated ones, as long as they have focus keywords set.

1. Indexing

   When a post is published or saved, its focus keyword and secondary keywords are stored in the plugin’s keyword table against that post ID. Generated articles are indexed the moment they save. Existing posts are picked up from Rank Math or Yoast focus keyword fields.

2. Matching

   When a single post is viewed, the plugin scans the post content for indexed keywords belonging to other posts, longest and focus keywords first.

3. Injection

   Matches are turned into links to the target post at render time, through the standard content filter. Nothing is written to your database, so your post content in the editor stays exactly as it was.

Because injection happens at render time, changes apply retroactively across your whole archive the moment you make them. Turn the linker off and every injected link is gone on the next page load, including on articles published months ago.

Settings

These rules exist so injected links never break your markup or look spammy:

• Only single posts. Links are injected on individual post pages, not on archives, category pages, the front page or any other post type.
• Never to itself. A post is always excluded from its own candidate list.
• One link per target post. The same destination is never linked twice in one article.
• One link per keyword. Only the first occurrence of a matched keyword is linked, so the same phrase is not linked repeatedly down the page.
• Whole words only. Matching respects word boundaries, so a keyword never gets linked inside a longer word.
• Headings are protected. Nothing is injected into H1 through H6.
• Existing links are protected. Text already inside an anchor tag is never touched, so your manual links and affiliate links stay intact.
• HTML is protected. Matching runs against text only, never against tag names, attributes, URLs, shortcode parameters or image alt text.
• Priority order. Focus keywords are considered before secondary keywords, and longer keywords before shorter ones, so the most specific match wins.

Auto Linker > Rebuild Keyword Index scans every published post on the site, reads the focus keyword from your SEO plugin’s own field, and rebuilds the index from scratch.

Run it when

• You have just installed the plugin on a site that already has content.
• You have bulk edited focus keywords in Rank Math or Yoast.
• You have imported or migrated posts.
• The links report does not match what you see on the front end.

It is safe to run as often as you like. It only reads your posts and rewrites the plugin’s own table. Post content is never modified.

Keyword index

Every indexed keyword, whether it is a focus or secondary keyword, and the post it points to. Use it to spot two posts competing for the same phrase.

Links report

Which posts send links and which receive them. The report is calculated with exactly the same matching logic used on the front end, so the counts you see here are the links that actually get injected, not an estimate.

Posts receiving no links are usually either very new, or their focus keyword is a phrase that never appears naturally in other articles. Editing that keyword to something you actually write in prose is normally enough to fix it.

The plugin detects which SEO plugin is active and writes into that plugin’s own fields, so the data appears exactly where you expect it and remains yours if you ever remove Autoblogging.dev.

Both engines still work with no SEO plugin at all. You simply lose automatic meta writing, and the linker has no focus keyword field to read from on your older, hand written posts.

The Getting Started page tells you which plugin was detected. If it says none while you clearly have one installed, the SEO plugin is probably deactivated or a version the detection does not recognise. Email support with the plugin name and version and we will add it.

Everything is built on standard WordPress hooks and filters, which is why compatibility is broad rather than a list of tested themes.

• Themes: any theme. Articles are ordinary posts, styled by whatever your theme already does to posts.
• Page builders: Elementor, Divi, Beaver Builder, Bricks and the block editor all display generated posts normally. Generated content is standard post content, not a builder layout.
• Caching: LiteSpeed Cache, WP Rocket, W3 Total Cache, Cloudflare and others are fine.

Ad slots let you place ad network code into generated articles automatically, so a growing archive monetises itself without you editing each post.

Allowlisted networks

Pasted code is validated against an explicit allowlist of ad network domains, both when you save it and again before it is output. Anything outside the allowlist is rejected rather than stored. Supported networks include Google AdSense, Media.net, Amazon, Ezoic, Mediavine and AdThrive or Raptive, among others.

This is a deliberate restriction, not a limitation we forgot to lift. It means a compromised admin account cannot use the plugin to inject arbitrary scripts across your entire archive.

The direct download version checks autoblogging.dev for new releases and surfaces them in Dashboard > Updates and on your Plugins screen, the same as any plugin from the directory. Click update and it installs in place, keeping your settings, API key, credits and keyword index.

The WordPress.org version contains no updater at all, because the directory handles updates itself. Running both mechanisms would create update conflicts, which is why the two are packaged separately.

One credit is one complete article, including its SEO meta and its indexing into the linker. There is no subscription and nothing renews.

• Charged on success only. A credit is deducted after the article is saved to your site. If a generation fails at any stage, no credit is used and the category returns to the queue for the next run.
• Credits never expire. Buy when you need them, use them whenever.
• Two free credits are added when you first connect, so you can see real output before spending.
• Internal linking costs nothing. The linker is not metered. It is included whether you generate one article or a thousand.
• Balance is shown in the plugin header and on the Credits page, refreshed when you load an admin page.

Running out of credits does not break anything. The writer simply stops publishing and logs it. Top up and it resumes on the next scheduled run with no reconfiguration.

Go to AutoBlogging-DEV > Credits & API Key. Packs are listed with their credit count, total price in USD and the resulting cost per article. Larger packs bring the per article cost down.

1. Pick a pack.
2. Tick the box confirming you understand credits are non-refundable digital goods and accept the Terms of Service.
3. Click Buy with Card. Secure card checkout opens inside your WordPress dashboard.
4. Credits are added automatically once payment confirms, usually within a few seconds.

A one time trial pack is available to new accounts so you can test at low cost before committing to a larger pack. It disappears from the list once used.

There is no subscription, so there is nothing to cancel. Stop buying credits and nothing further is charged. Any credits you already hold stay on your account indefinitely.

• Credits already spent on generated articles are non-refundable. The article was produced and delivered to your site.
• Articles remain yours permanently. Everything already published stays on your site whether or not you keep using the plugin, and whether or not you have credits left.
• Failed generations are never charged, so you are never billed for something you did not receive.

If something has gone wrong with a purchase or a generation, email admin@autoblogging.dev before anything else. Most billing issues turn out to be a payment that did not confirm, and those are quick to fix.

Full terms: autoblogging.dev/terms.

The plugin talks to backend.autoblogging.dev, because all AI processing happens on our servers. There is no local model and no offline generation. Here is exactly what is sent and when:

No personally identifiable data is collected beyond the site URL and admin email used to issue the key, and both only after you click Connect. Full detail: Privacy Policy and Terms of Service.