Antradus AI Lite — AI SEO Content Writer & Image Creator

Feroaringslog

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 a trial safe — and it is 7 days rather than 3, because nothing about search is visible in 3.
• On Publisher, the Podcast to Articles and Episode Assets tabs are shown locked rather than hidden, so it is clear what Studio adds and what it costs — and they link to a person, not just a checkout.
• Internal: the plan check matches the plan name exactly and never falls back to the licensing SDK’s ranked comparison, which a trial can outrank. Anything the plugin cannot positively identify is treated as Publisher, never as Studio.

2.6.0

• Added (Pro): Saved Plans. A planned episode is now kept instead of evaporating. Reading a three-hour episode is around twenty requests, and the plan screen is where a person fixes what no code can — who is speaking, a misheard name, which quotations are worth printing, a sponsor row that came through wrong. Until now all of that lived in a twelve-hour session and was then gone: opening the same episode a week later meant paying to read it again and re-doing every correction by hand.
• A new 💾 Saved Plans tab beside Podcast to Articles lists everything you have planned — service, show, episode, guest, how many articles and quotations, roughly what it cost — and filters by service, show and date. Load puts a plan back on the podcast screen exactly as you left it. Nothing is re-read and nothing is charged.
• Plans save two ways: a 💾 Save this plan button, and automatically when you press the button that writes the articles — which is the moment a plan is finished being corrected, and also the moment a person stops thinking about it.
• Paste an episode you have planned before and the plugin tells you before you spend anything, and offers to open that plan instead of reading it again. It recognises the same episode from a share link, a watch link, a link with a timestamp on it, or the bare id.
• The recording is kept with each plan, compressed. The copy stored beside an episode is cleaned up after thirty days; the one in the plan is not, so quotations in a plan opened next year can still be checked word for word against what was actually said. It can be turned off, and the tab shows what the plans are costing you in storage either way.
• A plan that has already written its articles says so when you open it, and how many — so reloading one cannot quietly publish the same episode a second time.
• Plans can be exported to a file and imported on another site, which also makes a problem plan something you can send us.
• Two refusals, both deliberate. A plan saved by a different version of the plugin is refused by name, saying both formats, rather than loaded with fields silently missing — a plan that comes back three fields short is worse than one that will not come back. And if the plan is too large for your host’s database to store the recording alongside it, the plan is saved without the recording and tells you, rather than the save failing and taking your corrections with it.
• Saved plans are not deleted when the plugin is uninstalled unless you explicitly tick a box asking for that. Months of your own corrections are not something an uninstall should quietly take with it.

• Nothing in the shipped Podcast to Articles pipeline changed. Quote verification, timestamp mapping, the measured clock offset, attribution, article writing and the render layer are byte-for-byte what they were.

• Changed: the whole interface has been redrawn, and nothing has moved. Every screen — the post editor box, Settings, Bulk Publishing, Reporting — was built at a different point in this plugin’s life and looked it: the same field was three different heights, the same blue was four blues, and on the Bulk screen the button that actually creates your posts was the same grey as Restore default. There is now one set of colours, corners, shadows and control heights behind all of them. Fields, buttons and tables match wherever you are; the action a form exists for looks like the action a form exists for; tabs join the panel they open; tables get a readable head and a row that follows your pointer; the Reporting figures are set as figures; hints are quieter, and the ones that are warnings look like warnings. Every control has a proper keyboard focus ring, and animation is switched off for anyone whose system asks for that. Not a single thing changed place — every element on all five screens is in the same order and the same column it was in before, which was checked element by element rather than by eye.

• Added (Pro): Episode Assets — one more step after the plan, producing the things an episode needs that are not articles.

• Quote cards, drawn rather than generated. Every competitor’s quote images are AI-selected and AI-transcribed, and nobody checks them. These are composed by the server from a font file, and each quotation is re-checked against the recording in the instant before it is drawn — through the same checker the articles use, not a second copy of it. Change one character of a verified quotation and no card is produced at all. Four styles: flat, the episode picture behind the words, a split with the picture above, and a highlighted-paper marker style whose strokes are measured off each line rather than stamped out as identical rectangles.
• The design gives way, never the words. A quotation too long for a style falls back to a roomier one and tells you it did. It is never shortened, re-punctuated or squeezed into unreadable type to fit. Right-to-left text is refused with an explanation rather than drawn reversed and unshaped, which is what the drawing library would otherwise do.
• Your colours, saved per show — seven of them, plus four one-click presets, contrast warnings against the accessibility threshold (a warning, never a block), and a button that reads five colours out of the episode picture for you to assign. Two open-licensed typefaces ship with the plugin, and your own can be uploaded — checked at upload for the quotation marks and dashes a quote card needs, so you find out then rather than after a card goes out with empty boxes in it.
• The episode picture is its own step, on screen before you choose a style. Two of the four styles are drawn on it, so the panel shows you the picture it has — where it came from and how big it is — instead of letting you pick Photo and find out ten cards later that they all came out flat. It is taken from the episode itself (YouTube’s 16:9 still when the run has a YouTube address, Spotify’s cover art otherwise), fetched once and kept in your Media Library. If neither service will give one up, the reason says so and you can upload your own, which the cards, the preview and the colour picker then all use. Styles that need a picture are offered but not selectable until there is one, with the reason written beside them.
• The preview is the real card, rendered by the same code that writes the file and scaled down in the browser — not a JavaScript approximation that disagrees with it about where a line wraps.
• A newsletter built from the episode: verified quotations with the timestamp linked to the moment, your articles, the sponsor block with its disclosure, and a subscribe row. Real email HTML — tables, inline styles, 600px, a plain-text alternate — in whichever shape your provider actually wants, because sending the wrong one produces something that looks perfect in the provider’s preview and breaks in real inboxes. Copy it, download it, or send yourself a test, all of which work with any provider on earth.
• Kit, Mailchimp and beehiiv create a draft. There is no send button anywhere in this plugin and no code path that could reach one. beehiiv’s API restricts creating posts to Enterprise plans, so that one is expected to refuse on most accounts — it says so plainly and points you at Copy HTML instead of failing mysteriously.
• Instagram, optional and off until you set it up. Instagram has no drafts, so publishing is immediate and public — it asks you to confirm, naming the account and counting the slides, every time. Before a single slide is uploaded it checks that Instagram can actually download your images, which is what stops a half-built carousel on a local, staging or password-protected site. The ten-slide API limit is enforced in the interface with the reason, and the daily posting limit is read from your own account rather than guessed at.
• Post copy for Instagram, LinkedIn and X in one request, with hashtags built from the people the episode actually names. The AI writes the words around the quotation and never the quotation itself.
• Context lines are the only part that costs anything — one request per card, stated on screen before you commit. The AI sees ninety seconds either side of the quotation and nothing else, and what comes back is checked in code for quotation marks, invented figures, outside names, links and phrases lifted off the recording. Anything that fails is thrown away and the card is drawn quote-only. It is never patched up to pass.

2.5.11

• Fixed (Pro): a Spotify-only episode showed no quotations at all. The recording was read perfectly — the voices labelled, the caption timings exact, every quotation checked word for word against it — and then the plan screen drew none of them. The quotations table, and the Who is speaking step above it, were shown only when the plan had found two or more named people; on a Spotify-only run it never does, because who is on an episode is read out of the show notes and Spotify’s notes are refused (it serves a truncated share preview, not your description). The articles then lost the quotes too: one nobody can be named for reaches the writer marked speaker unknown, and a writer told that will often leave it out. Both mode was unaffected throughout, because the YouTube half supplies the notes — which is why the same episode showed its quotes there and not here.
• The question is now asked because the recording says there are two voices, not because we managed to guess their names — the sensible order, given that guessing them is the part that fails. Where there is no list to pick from, Who is speaking gives you a box to type each name into, beside the first line that voice actually says and a link to hear it. Where the plan did find the people, the dropdown is exactly as it was.
• A voice you leave blank stays blank. In particular, on a two-voice episode with one name filled in, the other voice’s quotations are no longer handed that single name — they are published with no name, as they should be. That path could not arise while the table was hidden, and would have printed one speaker’s words under the other’s the moment it was shown.
• A quotation whose speaker is not on the offered list is no longer thrown away — the words passed the check against the recording, so it is kept and published unattributed. Losing a verified quotation over an unrecognised name was the wrong half to lose.

2.5.10

• Changed (Pro): in Both mode, a timestamp that was moved onto the other service’s clock now opens the player two seconds early. Those seconds are measured, not read off the recording the words came from, and a measurement is good to about a second either way — the anchors are caption chunks, and a caption chunk starts where the chunk starts, not where the sentence does. So a line Spotify puts at 0:05 lands at 0:04 or 0:06 on YouTube, and there is no way to know from here which one it is.
• The two mistakes are not worth the same. A second late opens the player mid-sentence or past the line entirely, and the one reader who checks a quotation concludes it was invented. Two seconds early costs them the tail of the previous sentence, which is what anyone scrubbing to a quotation does by hand anyway. So the link now aims deliberately at the harmless side.
• The printed time does not move with it: the number in the article is still the moment the words were said, because that is what the article is claiming and it is the true one. The run-up applies only to links that were translated between two recordings — a single-service episode’s timestamps are read straight off the recording you are being sent to and are unchanged.

2.5.9

• New (Pro): you can now name the speaker on a quotation the recording refuses to attribute. A line that starts in one person’s turn and ends in the next carries no speaker label, so the plan screen printed “Not named — this line crosses a change of speaker” and left it there: unticked, greyed out, and nothing you could do about it. That is the honest reading of the transcript and it is still what the row leads with — but the recording cannot say is not nobody can. Very often the second turn is an interruption or a “yeah, exactly” and the line really is one person’s, which anyone who heard the episode settles in four seconds. Those rows now carry their own dropdown of the people in the episode, underneath the recording’s own answer.
• It starts on Leave it unnamed, so nothing changes if you ignore it and the row still arrives unticked. Name somebody and the row ticks itself and is published under that name — your answer outranks everything else in the plugin, exactly as it already did on a YouTube episode. Naming a voice in Who is speaking never reaches these rows and never overwrites an answer you gave here: they belong to no voice, which is the whole reason they had to be asked about separately. Every other row on a labelled recording is unchanged and still has no dropdown — that column reports what the recording said, and it is not there to be argued with.
• Fixed (Pro): the suggested names for “Speaker 1” and “Speaker 2” could come out backwards on exactly the episodes where it matters. The guess reads who says whose name — a host says the guest’s name constantly and almost nobody says their own — and that count was taken per episode rather than per thousand words. A voice holding three quarters of the recording therefore picks up more of every term simply by being longer, the guest’s own name included, because a diariser that lumps the interviewer’s question into the guest’s block files that name under the guest. The count is now a rate, and the majority voice is never named the host: an interviewer who talks two thirds of the time is rare, that lumping is not. Where the two signals disagree the share wins, the reason on screen says the count disagreed, and the row is marked as the one to check first.
• Fixed (Pro): a reason that contradicted the number printed beside it. With two voices in the room, whichever one was left over was described as doing “most of the answering” whatever its share — so a row could read “does most of the answering. 38% of the talking” in one sentence. It now says that only when it is true.
• Changed (Pro): the First heard column on the voices table is now Hear this line, and the time is the moment of the line quoted on that row rather than the first noise the voice makes. A voice opens with “wrong, beginner’s luck” far more often than with a sentence, and four seconds there identify nobody — which is the opposite of what the column is for.
• Fixed: the voices step had a test written for it that was never added to the suite, so it had never once run. That is how the backwards guess above reached a real episode.

2.5.8

• Changed (Pro): podcast articles are now as long as the episode gave them, and no longer. There was a word target — 900-1400 for a spin-off, 2000-3000 for the episode article — and a stretch of conversation carrying one projection and three quotations cannot fill it honestly. So it was filled dishonestly: one measured article ran to 1,483 words in which the same population projection was restated under four of its six headings, its timestamp printed five times, its two years eight times each, and the focus keyphrase used fourteen times with all six headings carrying it.
• None of that was the writer breaking a rule. Every anti-repetition rule was already there and every one of them lost to the number, because a length target on material of unknown size is an instruction to pad. The target is gone. The size is counted from what that article was actually given — its verified quotations, figures, the speaker’s own qualifications and the objections put to them — at roughly one section per two of those, and the article stops when the material does. Expect shorter articles, and expect the same episode to produce articles of noticeably different lengths.
• Fixed (Pro): two headings counts contradicted each other. The spin-off rule asked for four to six sections while the running-order shapes asked for “5 to 7” and “4 to 7” — and the shapes were added to the prompt last, so the looser number won every time. The size rule is now the final word on it.
• Changed (Pro): counts that were per-section are now per-article. A per-section allowance is an allowance a writer spends: “one keyphrase per section” across six sections produced fourteen uses, and “at least one short sentence per section” produced a third of the article in clipped fragments. The keyphrase is now three times in the whole article and at most one heading; short sentences are fewer than one in eight, never two side by side. Each figure and each timestamp is used once and never repeated.
• Changed (Pro): the writing brief now comes before the rules rather than after them, and says plainly that the rules are a floor rather than the assignment. The prompt had grown to roughly ninety prohibitions, and an article that breaks none of them can still …