> Markdown version of https://jode.io/docs/publishing/ · Português: https://jode.io/pt/docs/publicacao/index.md · Summary: https://jode.io/llms.txt Features # Publishing Once generated, the article follows the path you chose: it goes live right away, waits as a draft, goes through client review or joins a queue that publishes one per time slot. This page explains each path, scheduling, how the live article stays protected and what happens when the address changes. PRO Updated for version 3.82 9 min read ## Publish or draft Nothing goes live without a choice of yours, made on every generation: - **From the button:** the Generate this article window asks Publish or Draft. Draft is the default. - **From scheduling:** the plan's Scheduling card has the same choice in Scheduled articles are saved as:, also with draft as the default. **Publish** puts the article live as soon as the generation finishes. **Draft** saves the article and opens a review on the review panel, where you or the client read, edit and publish. ### Auto-publishing after a few hours The Auto-publish after (hours) field, on the scheduling card, gives the draft a deadline. With a number of hours, a draft nobody reviewed publishes itself when the time runs out, together with the LinkedIn summary, and the theme card shows Publishes in …. With 0 or empty (the default), auto-publishing is off: only a person publishes. An open review keeps the deadline it was born with, even if you change the number later. ## Client review The review panel lives on jode.io and lets the client (or the author) approve articles without going into WordPress. The client signs in to the panel with the e-mail and password of their own WordPress user, and a single sign-in covers every site where they are an author. On the panel, the person sees the complete editorial plan, but only edits the themes where they are the author. Two lists stand out: - Awaiting your approval: generated or regenerated articles waiting for review and publication. - Changed articles awaiting publication: new versions of the person's articles that were saved without being published. Each article opens in Open review (the editor, in a new tab) or in Read (the reading view). The client edits the text, saves with Save changes as a draft and publishes with Publish. With a deadline, the panel shows the time left before auto-publishing. The editorial plan can also be downloaded as PDF there. - **The e-mail notice is optional.** The Email the reviewer on every scheduled run switch only decides whether the client is told; the review opens either way. The e-mail's text and recipients are on the plan's e-mail card (see [Projects and plans](https://jode.io/docs/projects-and-plans/)). - **The review follows the article's author.** If the author changes, the review moves to the new author. - **The LinkedIn summary travels with the article:** whoever approves one approves both (see [LinkedIn](https://jode.io/docs/linkedin/)). - **A failed regeneration gives the review back.** If you regenerate an article under review and the generation fails or is cancelled, the review comes back as it was: same link, same edits, clock paused, no new e-mail. ## Approval queue For those who want mandatory review and a steady pace, scheduling has the Publish through a reviewer-approved queue option. Articles come out as drafts and wait for the reviewer to approve them on the panel. Once approved, they go live 1 per schedule slot, in the plan order. - **Approving:** in the panel's editor, the reviewer uses Save and approve; the article joins the queue and goes live on its turn. - **No deadline:** the queue has no auto-publishing; nothing goes live without approval. - **An article taken down stays out:** the queue skips an article that was live once and someone took down. ## Scheduling Each plan has its own Scheduling card, which generates articles on its own at set times. It follows the same rules as the Generate button: the plan must be ready to generate (see [Article generation](https://jode.io/docs/article-generation/)). [![The plan's Scheduling window: generate or regenerate, publish or draft, review and auto-publishing.](https://jode.io/static/docs/img/scheduling-window-en.webp?v=4f67b7c02c)](https://jode.io/static/docs/img/scheduling-window-en.webp?v=4f67b7c02c) The plan's Scheduling window: generate or regenerate, publish or draft, review and auto-publishing. ### Time slots There are 3 frequencies: Daily, Weekly and Monthly. All 3 stay saved side by side, and the radio says which one runs now, so switching frequency doesn't erase the others' slots. Each slot generates 1 article, in your WordPress time zone. Use Add time to have up to 20 slots. ### What each slot does - Generate new articles: generates the next theme that has no article yet, in the plan order. - Regenerate existing articles: regenerates the articles you ticked in the list. - Both: generates the pending themes first and, when there are none left, regenerates. Regeneration follows the plan order, in laps: every ticked article is regenerated once before the list starts over. The card shows the Next to be regenerated. Cancelling a generation doesn't make the article lose its turn, and scheduled regeneration skips a version a person has edited. ### When a slot doesn't generate If a slot is refused for a reason that won't fix itself (a required setting missing, a refused key), the card shows an amber strip with the reason, and the activity log keeps the line. The strip goes away at the next successful generation. If the plan is busy with another generation, the slot waits. The spending cap also pauses scheduling (see [AI keys and costs](https://jode.io/docs/ai-keys-and-costs/)). **Scheduling reads the settings at the moment it fires.** Changed the model or the quotas? The next slot already uses the new value. On the same card, the Submit automatically to IndexNow switch notifies search engines of every article the plan publishes. See [SEO and performance](https://jode.io/docs/seo-and-performance/). ## The live article stays protected When a theme already has an article, the generation never writes over it. The new version waits beside the live article: - **With Publish,** the new version replaces the old one as soon as it is ready, in the same post, at the same address and with the same publish date. - **With Draft,** the new version waits on the review panel or in the queue, and the live article stays as it was until someone publishes. - **To throw away the new version,** use Discard new version, in the card's More menu. - **An article taken down doesn't come back on its own.** Nothing automatic (deadline, queue, scheduling) puts back online an article someone took down. A person can. The pending version can only be seen by people who can edit the article; visitors keep seeing the official address. ## Article dates Dates follow 3 rules, so Google sees a stable publish date and a real update date: - 1 **The publish date never changes** It is set the first time the article is written in WordPress, and APC never touches it again. - 2 **Every publish through APC is an update** Publishing a new version updates the modified date and goes into the history as WordPress update. - 3 **Saving without publishing touches no date** Saving an edit without publishing goes into the history as Temporary update. On a draft that was never live, any save moves the date, because it hasn't been published yet. ## One editor The review panel, the client page and the Edit via APC Editorial button all edit the same copy of the article: the one in WordPress or, if there is one, the pending version. Edit via APC Editorial opens in a new tab, with the text and the excerpt. - Edit in WP only shows up when there is no pending version, so nobody edits the wrong copy. - **Whoever saves last wins,** and the editor warns you when someone else is editing the article too. - **An old window doesn't overwrite a new version.** If a new version arrived after you opened the editor, saving is refused and asks you to reload. - **Pasted formatting doesn't go live.** Colours, fonts and styles brought in when pasting text from elsewhere are cleaned before publishing. ### Article history The Article history records when it was created, published and updated, with the columns Date, What happened, Type, Where and Who. "Where" says which screen the change came from, such as WordPress - Edit panel, APC Editorial - Briefing or APC Editorial - Theme card. In the approval queue, "Who" is whoever approved. ## Address, title and redirects The article's title and address move together in every editor: changing one updates the other. The theme's Destination URL follows a single format, tidied up as you type: lowercase letters, no accents, words separated by hyphens, no domain and no trailing slash (for example, just-cause-job-abandonment). - **Regenerating doesn't change the address** of an article that already exists. - **A draft is born at a free address,** never at an address that already has a redirect pointing elsewhere. - **Renaming a published article** through APC counts as an update in the history. ### Automatic 301 redirect When the address of a published article changes, APC creates the 301 redirect from the old address in whichever redirect plugin is active, in this order: Redirection, Yoast SEO Premium, Rank Math or, with none of them, APC's own redirect. **No chains or loops.** One redirect per old address; chains are shortened and loops undone. A redirect someone else created is left alone, and APC tells you. **Clean cache.** The pages that point to the article and the old address are cleared from the cache (LiteSpeed, WP Rocket, W3 Total Cache, Breeze, WP Super Cache and Cloudflare). **Search engines told.** The old address is sent to IndexNow, so search engines learn about the redirect quickly. ### Service page at the end of every article If the plan has a Service page linked at the end of every article, every published article of the plan ends with a block that takes the reader to that page, in the site's language. The page is chosen in the plan settings (see [Projects and plans](https://jode.io/docs/projects-and-plans/)). Found something wrong or missing? Write to [support@jode.io](mailto:support@jode.io). Updated on October 30, 2026 [jode**.io**](https://jode.io/) APC Editorial is a WordPress plugin made by jode.io. `support@jode.io` [+55 35 98815-2040](tel:+5535988152040) Rua Idalina Marcondes Mota, 55 - Nova Guará Guaratinguetá - SP, 12515-390, Brazil #### Product - [How it works](https://jode.io/#como-funciona) - [Features](https://jode.io/#recursos) - [Pricing](https://jode.io/#preco) - [Docs](https://jode.io/docs/) #### Company - [Contact](mailto:support@jode.io) - [Privacy Policy](https://jode.io/privacy-policy/) - [FAQ](https://jode.io/#faq) © 2026 jode.io Made for WordPress