Antradus AI Lite — AI SEO Content Writer & Image Creator

Rejestr zmian

2.15.1

• Changed: Studio is sold after a demo, and the plugin now says so everywhere. The ✨ More Features screen showed Studio with a monthly price and an „Unlock” button that went straight to checkout, while the website, this listing and the guides all said Studio is sold after a conversation. Studio now has no price on that screen and a Book a demo button that opens the contact page. The two locked Studio tabs a Publisher licence sees on the Bulk Publishing screen book a demo too, and the plan tables in the guides say the same.

2.15.0

• Fixed (Studio): saving the Settings page disconnected Instagram in Episode Assets. The Instagram connection was stored alongside the Settings page’s own options, and WordPress clears every option of that page the form does not show — so each Settings save silently emptied it. It now lives on its own. The Instagram box on the Episode Assets tab also never actually saved what you typed; it now has a Save Instagram details button and asks for your Meta app ID and secret, so a pasted token is turned into a long-lived one straight away and renewed before it expires. The connection also moves to Meta’s current API version, as the old one reached the end of its support.
• Added (Publisher): Share to social. A „Share to social” link now sits under every published post and page. It opens a picture builder that starts from the featured image with your logo in the top-left corner and the post title along the bottom; drag anything to move it, drag a corner to resize it, add your own lines of text, and save the positions as the default for every post. It previews the post the way Facebook, Instagram and LinkedIn show it, downloads the picture, and publishes it to your own Facebook Page, Instagram Business account and LinkedIn company page, adding the article as the first comment — the link, the excerpt and link, the whole text, or nothing, your choice. Each site connects its own Meta and LinkedIn apps, and nothing is posted without a confirmation that names every account it is going to.
• Fixed (Publisher): 🧍 Humanize this post and 💬 Tell Antradus AI what to do with this post now work on long posts. Until now both refused anything over about 2,000 words, because one AI reply cannot hold a whole long post. A long post is now worked on one section at a time, and the status line counts the sections as they finish. Nothing in the editor changes until every section is back, so if one fails the post is left exactly as it was. Sections are only ever cut between blocks or paragraphs, never through one. Images and embeds are left untouched, and each section is told where it sits so it doesn’t add its own introduction or conclusion. An assistant instruction that needs the whole post at once, such as a summary, is recognised and sent in one go.

2.14.0

• Added (Studio): articles can be written in a different language from the episode, and the quotations are translated honestly. Every pull quote is printed in the article’s language, with the words that were actually said directly beneath it, smaller, and a line saying what language they were spoken in and that the quotation above is a translation. The original is still checked word for word against the recording, so every quotation still has checked words behind it. Until now the writer was told to write entirely in your language and never change a word of a quotation, and whichever of the two it obeyed, something broke.
• Changed (Studio): a translated sentence can no longer appear in quotation marks inside a paragraph. Only a pull quote has room for the original beside the translation, so quotations inside sentences are reported in the article’s own words. A translation that comes back empty, repeats the original, or runs far longer than what was said is dropped and the original is published alone, and the job notes say how many.
• Fixed (Studio): quotation marks in every language are now checked. Only “…” and „…” were checked before, so a Spanish, French or German article could put a paraphrase in «…» or „…“ under a real person’s name and nothing looked at it.
• Added (Studio): choose the language of your quote cards. Episode Assets has a Language menu beside Style and Shape. Each quotation is checked against the recording first, then translated with one request, kept for 30 days so previews and redraws are free. The card says it is a translation. A translation that adds a number the speaker did not say is refused, and the card is then drawn in the original words. Context lines and post copy follow the same language.
• Fixed (Studio): the font check could not see a missing letter. It compared every character against a reference the drawing library cannot read, so every font passed. A card in a language the chosen font cannot draw, such as Russian or Japanese with the bundled fonts, is now refused and the missing letters are named, instead of coming out as empty boxes.

2.13.2

• Changed (Studio): nothing at all is changed on your guests any more — not even the light on them. When Podcast to Articles builds each article picture from the episode thumbnail, every pixel that belongs to a person now comes through exactly as supplied: no retouching, smoothing, beautifying, ageing or slimming, no changed expression, gaze, pose or hand, no changed hair, glasses or clothing — and no relighting. The instruction used to tell the model to light your guests to match the new scene, which is the last door left open on a face: a model allowed to change the light on someone changes their skin, their age and their expression along with it.
• Changed (Studio): the background is made to suit the people instead. The model reads the light already on your guests — which side it comes from, how high, how hard, how warm — and builds and lights the new scene to match it, choosing the time of day, the room and the surfaces that make that light plausible. Every disagreement between the scene and a person is resolved by changing the scene.
• Fixed (Studio): the look you set, and the colour cast, can no longer reach a face. Both are written as whole-frame grades and the look said so in as many words („apply its light and colour to the whole picture, the people included”), which quietly outranked the keep-the-people rule above it. The look now applies to the new scene only, and a final rule after both of them exempts every person.

2.13.1

• Fixed (Publisher): the description of what you sell was only ever saved by pressing the scoring button. Type it, leave the tab without scoring, come back — and it was gone. It saves itself now, the moment you click out of the box.
• Changed (Publisher): the scoring button moved to where its result appears. It sat on step 2 beside the description it reads, so you pressed it on one screen and the list it changed was on another. It now sits directly above the write list. What had kept it on step 2 was the save above, not the reading.
• Added (Publisher): a score is remembered against what you sell, so changing that description un-scores every search — and now the screen says so. Editing the box reports how many searches need scoring again instead of letting you find out by noticing a number.
• Fixed (Publisher): the scoring button went back to saying nothing once there was nothing left to score. It now reads „Everything is scored — all 118 searches” and is greyed out, rather than falling back to a verb with no object.
• Fixed (Publisher): the brief printed its grounded ideas under an Impressions column in no particular order. 92 above 20 was a coincidence. They are sorted biggest-first now, and the suggestions list — which has no measured number to sort by — says that it is in the order the model wrote them.

2.13.0

• Changed (Publisher): the Search Demand tab was rebuilt because it was unreadable. Ten sections rendered at once, nine buttons scattered down the page, and a button labelled „Score for buyer intent” with nothing on screen saying what it was about to score. Setting up is now three numbered steps with one open at a time — connect Google, say what the site is for, then the work — and a finished step collapses to one line saying what it was set to, so nothing is hidden that you cannot read at a glance. The six result lists share one space behind tabs that carry their own counts, so the screen tells you where the work is instead of making you scroll for it. The two charts and the eight publishing options are folded away with a summary of what they are set to. Refresh sits in a bar of its own, because it is wanted from every step.
• Changed (Publisher): the scoring button now says what it scores. It reads „Score for buyer intent — 118 searches” with the real count, and the line under it says the model is shown each search on its own and never how popular it is, so a search with big numbers cannot talk it round.

2.12.0

• Added (Publisher): Search Demand now asks what the site is for — „I sell something” or „I run a blog”. The two want opposite things from the same data. A site that sells needs buyers and articles that show what it sells; a blog needs readers and articles that sell nothing. On a blog every search is now scored for whether it comes from the reader the site is written for, the chart and the labels say so, and the model’s own suggestions are the next subjects to cover rather than searches a buyer would type. Scores are kept separately for each choice, and a site that already sold something keeps every score it had.
• Fixed (Publisher): articles written from Search Demand never mentioned what you sell. Your description of the business was used to score the searches and then dropped — the article was only ever told the search — so every article came out as a neutral piece on the subject with no word about your product, your pricing or anything else of yours. On a site that sells something, every article is now told what you sell and writes one section on how it handles the problem the article is about, saying only what your description says: no invented features, prices or results, never „the best”, never a named competitor.
• Added: the pages to send readers to. Pick your pricing page, product or service pages, or the article that explains what you sell, and every article links to the ones that fit — up to three, each once — and ends with your own closing line pointing at the closest one. Those are the only pages on your site an article may link to: any other link into your own site the AI writes is removed and its words kept, because it would be a guess at an address, and a guessed address is a broken link. The link check and the closing line are done by the plugin after the AI has finished, so they cannot be skipped or invented. Internal linking could never have done this: it only links a post to other posts, and pricing and product pages are pages.
• Added: links into the articles Search Demand already wrote. A list of them sits under Write these, showing which already link to your pages. One button adds the links — around words already in each article, through the same engine as internal linking, so no sentence is rewritten and nothing lands in a heading or a quotation — and the closing line. Undo this run puts them back, and refuses to overwrite an article somebody has edited since.
• Fixed (Publisher): saving the Settings page wiped the Search Console property you had chosen. WordPress saves every setting registered to a form and stores an empty value for one the form does not show — the property and Analytics choices were registered to the Settings form but only shown on the Demand tab. They now belong to the tab alone.
• Fixed (Publisher): Undo on „Fix these” silently restored nothing when the old title had a quote mark or a dash in it. The backup lost its backslashes on the way into the database and could no longer be read. Titles written by AI models are full of dashes, so this was the common case rather than the rare one.
• Fixed: the Search Demand reading was logged as „other” in Reporting. It makes a model call and was never named; it now reports as Search Demand reading, and the new link pass as Links to your pages.
• Fixed (Studio): pictures built from an episode thumbnail no longer all come out as dark rooms. The instructions behind them were built into the plugin and asked for the same picture every time — a darker background, haze, smoke and embers, teal shadows against amber highlights, strong rim lighting, „symbolic objects and rooms”, with „a candlelit study at dusk” as the one example. So every article’s image was a dim, smoky interior whatever the article was about, often with a chessboard, a set of scales or a candle standing in for the idea. Each picture is now set in one real place where that article’s own question comes up — taken from its title rather than the episode’s broad theme, so articles on the same subject land in different places — in natural light that favours daylight, with true colours and your guests the sharpest thing in the frame.
• Added (Studio): Podcast Episode Images — set how those pictures look yourself. A new box in Antradus AI → Settings → Image Generation holds the look in plain English — the kind of place, the light, the colour — and every episode picture follows it. It ships filled with the new bright editorial look, and ↺ Restore default puts that back. While the box matches the default, a better default in a later update reaches your site on its own.
• What that box cannot change, on purpose: everyone on the thumbnail is kept exactly as they are and nobody else is added — not even a stranger in the background — the thumbnail’s own headline is removed, nothing else in the picture carries writing, and it stays one photograph filling the frame.
• Changed (Studio): episode pictures no longer use the Image Generation style preset. Presets are written for pictures invented from nothing — the default one asks for „real people”, an invitation to add a stranger beside your guests — and two styles in one request get averaged into neither. The colour cast still applies. Images written from scratch still follow the preset exactly as before.
• Fixed (Studio): a picture carrying a headline no longer asks for a darker patch behind the words. They need a calm, uncluttered area to sit on, not a dark one; the text is already set light on dark or dark on light to stay legible.

2.11.0

• Added (Publisher): Search Demand now shows you the shape of your traffic, not just a list. Two charts sit at the top of the 🔍 Demand tab. The first is how often Google showed this site day by day, with clicks under it. The second is the one that matters: the same impressions split by whether the person searching would ever buy what you sell. On a site collecting attention from the wrong audience, that second chart is the diagnosis, and it takes one glance instead of reading a table.
• Added: „What it makes of this” — it reads your data back to you and says what to write. One button, one pass over everything on the screen against your description of what you sell. It answers in two short paragraphs — what it saw, and what it makes of it — and then proposes articles in two lists that are never mixed: ones backed by a search Google really shows you for, and ones that are the model’s own judgement about searches you have never appeared for. The second list is labelled as judgement everywhere it appears, because Search Console cannot show you the demand you do not already touch, and pretending otherwise would be the exact dishonesty this feature was built to avoid. Anything in either list can be ticked and queued as ordinary articles.
• A proposed article that quotes a search you do not actually have is thrown away, not corrected. Every „backed by your data” row is checked against the real list in code before you ever see it. The impressions shown beside it are the measured ones, never anything the model said.
• Added: searches served by pages that no longer exist. If Google still shows an address that is not a post here any more — you deleted it, or moved it — that is now its own list. It used to be invisible, which meant a deleted page and a page that never existed looked identical on this screen, and they need opposite work: put it back, or write something new. The plugin was already collecting this and throwing it away.
• Fixed: the screen now says when your Search Console property is a different site from your WordPress install. This was the worst failure the feature had, because it looked like an answer. Searches still came through — a search carries no address — while everything needing a page address silently reported zero. Fix these and Losing ground would say there was nothing to do, and the Currently ranking column would print „nothing ranks” beside searches a live page really did rank for. There is now a warning above the verdict naming both sites, saying exactly which lists are affected and why.
• Fixed: „Write these” no longer renders an empty table when every search scored as a non-buyer. The rows were behind the „show non-buyers” toggle the whole time, but the block drew a bare column header over nothing — which reads as a broken screen, not as a filter doing its job. It now says how many were filtered and where to find them, and hides the publishing options and the queue button rather than offering to queue nothing.

2.10.0

• Added (Publisher): Search Demand — what you already rank for, and what to do about it. A new 🔍 Demand tab on the Bulk Publishing page connects your own Google Search Console (and optionally Analytics), reads what this site is already being shown for, and turns it into two lists with a button on each. Not a keyword tool: it answers „what should I write about” from your own impression data — the only source that knows what Google already thinks your site is about — rather than from search volume bought from somebody else.
• Every search is scored for whether that person would actually buy. You describe what you sell in one plain paragraph, and each search is rated 0-3 on the person typing it, not the topic. This is the part that matters: a site can collect a year of impressions from an audience that will never buy anything, and without this filter the obvious next step is to write more of the same. The rejected searches stay visible with the reason each was rejected, because seeing what was thrown away is how you know whether to trust the filter.
• „Write these” — searches you get impressions for that no page of yours aims at. Tick them and they become ordinary bulk articles, each one’s focus keyphrase set to the exact search it was written for. Live web search is off by default here, deliberately unlike Trends: a commercial search does not postdate the model’s training data, so paying for one would buy nothing.
• „Fix these” — posts that are indexed and being seen, but whose title aims at something nobody types, or that rank on page one or two and earn far fewer clicks than that position normally does. Only the two lines Google shows are ever changed — the article, its heading and its web address are never touched — every rewrite is shown to you as before-and-after before anything is saved, and one button puts the whole run back.
• It refuses the advice it cannot stand behind. A page Google has never indexed is reported separately and offered no title fix, because that is an indexing problem and a new title would not touch it. A page losing impressions as well as clicks is told plainly that it is losing positions and needs the article updating, not a new title. And if the AI proposes a keyphrase your page does not actually get impressions for, the suggestion is refused rather than quietly corrected — inventing a phrase nobody searches is the exact fault the feature exists to fix.
• Set up with a Google service account, so nothing is shared with anyone and no third-party app needs approving. The screen shows the address to give read access to, names which Google API is switched off when one is, and tells you if your server’s clock is what Google is objecting to.
• Fixed (Publisher): Google Trends and SEO clusters were logged as „other” in Reporting. Both make model calls, and neither was named in the usage log, so their cost appeared under a heading that explained nothing. They now report as Trending article and Cluster planning.
• Added (all editions): ✨ More Features — one screen that shows you what the other plans do. Until now, a free install could only see the paid features that happen to sit beside a free control. Everything living on a screen of its own — Bulk Publishing, Google Trends, SEO clusters, Reporting, and the whole podcast pipeline — was simply invisible, so the honest answer to „what would I get” was „go and read the website”. Now Antradus AI → ✨ More Features lists every feature in Lite, Publisher and Studio, with a tick beside the ones your license already covers and a padlock beside the ones it doesn’t. Publisher installs see only what Studio adds; Studio installs are not shown the screen at all, because there is nothing left to sell them.
• Bulk Publishing and Reporting now appear in the free menu, locked. They sit exactly where they appear on a paid plan, so the free menu is the paid menu with padlocks on it rather than a different shape. Both are links to the More Features screen — nothing here opens a page that renders an error or an empty table.
• Nothing moved across the free/paid line. Every feature that was free is still free, and nothing that was paid became free or vice versa. This release adds visibility, not entitlement.
• The feature list now lives in one place. The screen, this readme and the documentation are generated from a single list in the plugin, and a test fails the build if the three ever disagree — so the plugin can no longer advertise a feature it dropped, or quietly ship one it never mentioned.
• New guide: „Which Plan Do I Need?” — Lite vs Publisher vs Studio vs Managed, what each one is actually for, and how to decide. Readable inside the plugin under Antradus AI → Docs, and online at antradusai.com/docs.
• More signposting to the things that explain this plugin — the full feature list, for publishers, for studios, the documentation and the blog are now linked from the readme, the docs and the new screen, instead of being something you had to already know about.

2.9.0

• Added (all editions): the AI disclosure line. Every article the plugin writes now ends with one sentence telling readers it was written with AI, and naming the model that wrote it — „This content was created with the help of AI (Antradus AI – gpt-4o).” On by default, because the EU AI Act (Article 50) asks anyone publishing AI-generated text to say so, and that duty does not belong to a paid plan.
• It names the model that actually wrote that article. The model is recorded on the post as it is written, so switching provider next month does not rewrite the history of what you published last month.
• Only the posts Antradus wrote. Articles from the editor, from Bulk Publishing (clusters, Trends and podcast spin-offs included) and product copy written from a photo. Posts you wrote yourself are never marked, a CSV import is never marked, and using the AI Assistant or Human Voice to edit your own writing does not mark it either.
• Yours to word, and to switch off. Antradus AI → Settings → AI Disclosure: turn it off, or rewrite the sentence with [model] and [provider] placeholders, and every article follows at once — the line is added when the page is read, never written into your post content, so nothing can delete it by accident and nothing is left behind if you turn it off. Any single post can opt out from its own AI Disclosure box in the editor.
• Changed (Publisher): a Google Trends source now counts as fresh if it was published in the last 48 hours, counted back from right now rather than rounded to a calendar day. The old „published today” rule accepted half an hour of reporting at 00:30 and threw away last night’s report on the story still trending this morning. The tighter settings are unchanged in spirit and now read as within 12 hours of the trend and within 6 hours of the trend, both on top of the 48-hour floor; an install that had chosen „published today” moves to the 48-hour setting rather than to a stricter one. Times shown to you are still your site’s local time.

2.8.0

• Added (Publisher): Google Trends, with the freshness actually checked. A new 📈 Trends tab on the Bulk Publishing page shows what your country is searching for right now — country, past 4 hours to 7 days, category, active trends only, search volume and how fast each one is climbing. Press Write about this topic on any row and Antradus pulls the news reports Google Trends itself lists behind that trend, then does the part nobody else does: it fetches each report, reads the publication time out of the page (structured data, article:published_time, the article’s own time tag) and keeps only what was published today in your site’s timezone. Live web search is always on for these, so the model can confirm and fill gaps — but the checked reports are the spine, and it is told not to outrun them.
• When nothing is fresh enough, it says so and hands you the controls. Instead of writing a confident article from a model’s memory, the tab tells you how many sources it looked at, which was the newest, and when it was published — then offers a box to paste your own source, which goes through exactly the same check. Nothing is queued until at least one source has passed.
• The list of sources is real. Optionally ends each trend article with the reports it was actually written from — outlet, headline and publication time — built by the plugin from the pages it read, never written by the AI. The full record, including the sources that were checked and dropped and why, is kept on the post itself.
• Write about ten trends without ten trips through the screen. Tick the trends you want, press ⚡ Add to the queue, and each one is checked and queued in turn against your saved settings — style, tone, language, post type, category, author — with a running count and a Stop button that finishes the trend in hand and leaves the rest. They all land in one batch, so the Queue tab runs and reports them together. Your choices are remembered the first time, so tomorrow morning is one click.
• New settings (Antradus AI → Settings → Google Trends): your SerpApi key with a Test connection button that reports how many searches your plan has left without spending one, a default country, how many sources one article may use (never two from the same outlet), and how fresh a source must be — published today, or within 12 or 6 hours of the trend.

2.7.0

• Two paid plans instead of one. Publisher is everything for a website — bulk publishing, internal linking, SEO clusters, AI Search, Human Voice, YouTube to Article, and the rest. Studio adds the whole show pipeline on top: Podcast to Articles, Saved Plans and Episode Assets. Antradus AI Lite is unchanged and stays free forever.
• Nobody loses anything they already bought. Every existing licence carries the full Studio feature set, by licence number as well as by name, so a rename can never quietly take a feature away from someone who paid for it.
• A 7-day free trial on Publisher. There was no trial at all before, because the only plan was a one-time payment and a trial on one of those bills the whole amount the day it ends. Publisher is monthly, which is what makes …