Documentation

What's new in WriteOut

Every change, newest first, by the day it went live. How each feature works is in the docs.

18 November 2026

Added

  • Breakout discovery in Claude. Connect WriteOut to Claude (claude.ai, Claude Desktop or Claude Code) as a connector and ask for breakout ideas from a project brief: WriteOut builds the seed bank, pulls rising and breakout Google searches and scores the ideas, and Claude shows them. It only finds ideas, never writes or publishes. Set it up in App settings → Claude (MCP).

Changed

  • A carousel or reel that goes into your Publer posting schedule now says which slot it got (e.g. "Instagram: scheduled for 22 Nov, 10:00"), so you know where to find it in Publer's calendar.

15 November 2026

Added

  • Carousels and reels you send from a post can go into your Publer posting schedule instead of posting straight away: the next free time slot, or the best free slot in the next 7 days, with your Publer label so labelled slots are used. Pick it in the Publer settings under "When you send a carousel or reel". The send buttons say where it will go.
  • If Publer has no free slot in that window, the post moves on to the very next free slot with your label, however far ahead it is; if no slot has that label, it takes the next free slot of any kind and keeps the label. It no longer just fails.
  • The Publer settings list your Publer labels, read once when you connect your workspace (and refreshed daily in the background), so the page and every send stay fast: tap one to add it to the labels for carousels, reels or link shares. WriteOut sends Publer's exact spelling of each label (time-slot labels must match exactly), and labels the post too.
  • The assistant (in the app and on Telegram) can edit your posts. Paste a list of changes (a new title, meta description, H1, first paragraph, a link to add, a phrase to replace) and it finds each post by its address and proposes the edits; confirm, and it updates the same page (same address, never a new post), keeping the old version. It can also rewrite a post from your feedback as an update to review. Curly quotes in pasted links are straightened.

Fixed

  • Your Publer labels show up as buttons in the Publer settings more often: if your API key can't list labels, WriteOut picks them up from posts already in Publer. When it still can't find any, the page says why and what to change, instead of leaving an empty box.
  • Telegram messages that start with a page address reach the assistant. A message beginning with “/blog/…” was taken for a bot command and got the help text back; now only /start, /status, /new and /help are commands.

Changed

  • GitHub sites that build themselves. For a site whose own build (for example GitHub Actions) publishes the blog, WriteOut now commits only its own blog folder, never the built site, and reads the nav and footer for previews from the live site. A post shows “Published, live in about 2 minutes” and is called live, with its notice, indexing and sharing, only once its page is up with the new version.

14 November 2026

Added

  • Social: Reddit posts, and sites without a blog. Turn on Social for a site (in the new-site wizard or Settings → What WriteOut does) and each breakout can become social posts: a Reddit text post for the subreddit you moderate, plus the carousel and reel from the same piece. Use “Make social posts” on a breakout, or let WriteOut draft them after each run (Settings → Reddit, with a daily limit). “Open in Reddit” fills in the title and text on your subreddit's page, so no Reddit login or API is needed; mark it posted when it's up. Blog posts get a Reddit post too. A site with Social only skips every blog and publishing step and gets a Social tab instead of Posts.

Fixed

  • Reddit posts no longer show markdown symbols. Reddit's app and website show **, # and [text](link) as they are when a post is pasted or filled in, so Reddit posts are now written in plain text (TL;DR as a plain line, addresses written out), and drafts made before are converted when you open them.

13 November 2026

Added

  • Tools feed. Point WriteOut at a JSON list of your site's free tools (Settings → Write → Tools feed). It reads it every day and on Rescan site. A new tool gets a call-to-action line, a "don't compete" entry so no post targets the tool's own search, and a cluster of four posts (a launch post drafted this week and three how-tos that link to it). Its launch post gets a carousel and a reel when it goes live, and older posts are checked for links to it. You get one alert per tool. In Suggest mode nothing changes until you approve; Apply automatically does it at once. A changed tool updates its line, a retired one loses it. Lines the feed adds are kept apart from yours and never touch them. Tool pages show their Search clicks on Performance → Pages, and Optimization ideas suggest links to a tool page rather than rewriting it.

Fixed

  • Blog graphics and covers are laid out in a fixed frame. WriteOut now places every design in a box with even padding on all sides, with the headline at the top, the visual filling the middle and the source and logo at the bottom, and gives Claude house layout rules (grids, not fixed widths; no extra wrappers). Graphics no longer drift off the right edge or bunch up at the top, instead of being caught and redone afterwards.
  • The Graphics tab says what goes out. It shows how many graphics go out with the post, lets you use a flagged graphic or cover anyway, and "Update the live post" says when there are no graphics to send.
  • No more "Method Not Allowed" after posting to social. If the page reloads after a slow post, you land back on the post's social tab; nothing is posted twice.
  • A tool's launch post is about your tool. The writer is told the tool is your own and live, and writes what it does, who it's for and how to use it, instead of a roundup of other tools. Its call to action sits right after the opening as a highlighted block, and it no longer gets a second, unrelated calculator. Rewriting a launch post uses the same brief.
  • Calls to action fit the post. One is added only when the post is about its topic (in the title or main search) or mentions it more than once, not on a single passing word.
  • Designed covers show on GitHub-published sites, at the top of the post and as its share image.
  • Calculators inside posts look like a designed block in the site's colours on every site, not bare form fields.
  • Tool carousels sell the tool. When a post is about one of your tools (its launch post, or a post about a tool it links to), the carousel brings the tool in naturally, gives it the second-last slide, and ends with "Try it free" on your website instead of "read the guide". The first comment links the tool.
  • The publish check looks at the finished article on every site: broken markup, markup shown as text, an unstyled calculator, a launch post that doesn't feature its tool (or says it doesn't exist), graphics left out for not fitting, and a designed cover that didn't render. Each holds the post for review.
  • Graphics stay inside their canvas. Content running to the edge is now caught, a graphic gets two tries to fix it, and one that still doesn't fit is kept off the post (marked on the Graphics tab to redo).

Changed

  • Carousels are written for Instagram. Plain everyday words, a hook of 10 words or fewer that opens a question the carousel answers, a second slide on why it matters, one short idea per slide, and the full answer before any call to action. In a tool carousel, the tool comes in as the easy way to do the hard part, then gets its own slide.
  • The carousel, reel and both buttons sit on their own line under the network, so they fit on a phone.
  • Post the carousel, the reel, or both. When a network has both ready, the post page offers all three buttons instead of only "Post both", and "Post again" lets you pick which one goes out.

11 November 2026

Added

  • Choose where article images come from. Settings → Social design → Images inside articles: designed graphics only (your design and visuals prompt), Pixabay photos only, or a mix, where Claude uses a Pixabay photo for a spot where a real photo helps more than a graphic (a place, a product, people at work), at most two per post. Redo on a photo gives the next matching one.
  • Images inside every new article (a growth feature, off until you turn it on). Each new draft gets its in-article images automatically, up to the number you set, before it reaches you for review.
  • Designed call-to-action blocks (a growth feature, off until you turn it on). Your automatic calls to action show as a banner with a heading, a line of copy and a button in your site's colours. The one that fits best sits inside the article, right after the paragraph that mentions it; a second one, if it fits, at the end. Add a third part to a call-to-action line to set the button's words.
  • pSEO Overview: every page from launch to results. A new Overview tab, replacing the Optimization tab, for programmatic pages shows the week's non-branded impressions, clicks, pages indexed, pages with searches close to page one and pages still to write, and every page's stage: being written, live, indexed, getting impressions, has actions, or re-checking a change.
  • A weekly brief for every live page. After each Search Console sync, each page gets its actions in order: write it first if it has no content yet, a note when its data calls for one (for example a card that isn't accepting applications), the title when it misses the biggest search, an H2 or FAQ for each search intent no heading covers, and the searches at positions 4 to 20. Each page type sets its own thresholds, and what its template can't show yet is marked blocked instead of assigned. WriteOut lists the actions; you run them.
  • Re-check what you changed. Mark an action done and its searches are compared five weeks later: won, progressing or stuck.
  • Pages get indexed when they go live. Sitemaps are resubmitted, the page is checked in Search Console, unindexed pages are checked again every day, and, if you turn it on, Google's Indexing API is asked to crawl it.
  • Release batches for pSEO pages (the Releases tab). Plan staggered batches (so many pages every so many days, your priority list first), check each batch's exact changes (for example each card's addToSitemap from false to true), and approve it. On its date WriteOut makes the changes in your CMS, reads them back, and submits each page for indexing. Each page type says what “released” means for it; without that, releasing a page sends it.
  • Links between your blog and your pages (the Links tab). A scan of the blog's posts in your CMS finds posts that name a live page without linking to it, and links to your own addresses that are dead, redirect or point at a page that's off. Tick the ones to fix: WriteOut backs up each post, changes only that link, and reads it back.
  • Weekly Asana tasks for pSEO, where the Asana integration is on: a review task with the week's numbers and a task with one subtask per page that has actions. Pages still open from last week are carried over, not added twice.

Changed

  • In-article images on more sites. Graphics and photos inside the article now go out on GitHub and Hostinger sites (saved next to the post) and to Payload (uploaded to its media library and placed in the article), not only WordPress.
  • Articles mention your products where they help. The products and tools in a site's automatic calls to action are now given to the writer, which brings the one that fits into the article itself, with a sentence on what it does for the reader and a link on natural words.

Fixed

  • Drafts, fixes and publishing no longer wait behind image making. Article images are now made in a lane of their own, so a post being written, fixed or published doesn't sit for minutes behind them, and more jobs run at once.
  • Refresh live pages works on GitHub-published sites. It used to refuse with a message about Hostinger. You can now also refresh all live posts, not only the last 90 days.
  • Calls to action no longer show bare web addresses. The link sits on the call to action's own words (for example "Make a free profile"), and only the two that fit the post best are added, one per address, skipping any the article already links to. Use Refresh live pages to update posts already published.

6 November 2026

Added

  • Two new chapters in the guide (writeout.tech/docs): Publishing guardrails (limits, approval, the page check and your override, one story one page, language versions, expiry, listing pages, removed addresses) and Growth features (each of the ten features, how to set it up, and its defaults).
  • Growth features, one switch each per site (Settings → Growth features). All are off until you turn them on, and each can be tried on some categories first.
  • Search results feedback loop. Each post's clicks, impressions, click-through, position and top searches at 3, 7, 28 and 56 days after it goes live. Pages Google shows but nobody clicks get a proposed new title and description that you approve; ranking pages whose searches are falling get a refresh aimed at those searches; posts with no impressions after 6-8 weeks get a suggestion to merge them into a related post or keep them out of the index. Topics like the posts that earn clicks score higher.
  • Topic fit against your site's plan. Give a site its plan (main guides and their topic pages, pasted into Topic clusters or read from a file on your site) and every new idea shows which section it fits. Ideas that fit none are flagged “Off plan”, or dropped if you choose, and each new post goes under its main guide, in its category and with a link to the guide.
  • Topics scored before writing, with reasons. Each idea is scored on how fast it's rising, what the searcher wants, how strong Google's page one is (read from the real results when DataForSEO is connected), whether people will still search it after the spike, and how well it fits your site; the idea card shows the reason for each. Short spikes that big news sites will win anyway are skipped.
  • A look at the top results before each draft. WriteOut reads the pages that rank now for the post's main search, notes what they cover and what they all miss, and writes the draft around that gap. The review is saved with the draft (the post's Top results tab).
  • Something rivals don't have, in every post. Each post adds at least one thing the top pages lack: a calculator or checker that works on the reader's own numbers, a worked ₹ example, a comparison table, or a checklist from the official source. WriteOut builds the calculators itself from Claude's description, and related posts link to them. The page check holds a post that has none.
  • Your own experience, never an invented one. Give a site a facts file (what you've really done and used, and what you've really reviewed) and posts add a short “My take” only where one of those facts applies. Outside opinions are credited to the person who said them, your author note goes at the bottom after the disclosure, and a post is only marked as a review when you really reviewed the thing.
  • A link from the main guide to every new post under it. When a post goes live, its main guide gets a link to it, as one more item in the guide's list of topic pages. The live guide page is edited in place (with a backup), not rewritten.
  • Story tracker for developing stories. Answer keys, results, dates and prices: WriteOut reads the official page the post cites once a day and, when it changes, adds a dated update to the live post at the same address and tells you what changed. Set or change the page it follows on the post.
  • Publishing speed. Each post shows how long it took from its topic starting to rise to the post going live, step by step, and you get an alert when one takes longer than the site's target.
  • A check of each live site after every WriteOut deploy and every day. The sitemap against the addresses you removed or redirected, the listing pages against the live posts, and the Google tag, footer and scripts on the newest posts. Anything that breaks is sent to you once (Settings → Site check).

Changed

  • Your Publish or Approve click always publishes. The quality checks (the page check, working notes in the copy, the fact check, the checklist) still run and show their results on the post, but they no longer stop a post you publish or approve yourself. They only hold posts going out on their own (autopilot, automatic updates), and those wait for your click instead of a fix. A change made after your click (an update, Fix with Claude) is checked again. Publish now goes out straight away, past the site's hourly and daily publishing limit; Approve still waits for it.
  • Section headings follow the searches too, even with a set heading format. Give a section a heading pattern (Page types → the section → More, e.g. “{name} fees and charges”) and each page's heading starts from it but is rephrased around the biggest search for that item that the section answers (“HDFC Millennia annual fee and other charges”). With no matching search, the pattern stays as it is. Set a section to Fixed to keep the pattern exactly on every page. Headings can be edited on each page, go to WordPress themes with the section, and can go in their own CMS field.

Fixed

  • A live post stays in the sitemap while a change to it waits for review or is held by the page check. Its live version is still up, so it no longer drops out of the sitemap until the change goes out. The sitemap's “last modified” date is now the last time readers saw a change, not the last time WriteOut touched the post.

5 November 2026

Added

  • Publishing limits on every site, on by default. At most 1 new post an hour and 3 a day, unless you raise them (up to 6 an hour and 24 a day; they can't be switched off). Every way a post goes live waits for them, including “Publish now”, fast-tracked breakouts and language versions: a post over the limit stays approved and goes at the next allowed time.
  • A page check before anything goes live, on new posts and on every change to a live one: title and description length, a title in the page's language, no repeated headings, one Sources section, no research or Google Trends notes in the copy, a slug that names the subject, the length limit and layout from your writing guide, and, on the finished page, that your theme is intact (Google tag first in the head, the theme's scripts, the footer).
  • Dates and numbers checked against the sources a post cites before it goes live. Conflicts, facts that have gone stale, contradictions within the post and wrong citations hold it for your review; you can publish anyway once you've checked.
  • One story, one page, in every language. A new topic is checked against every post that's live or waiting, in any language or script, and results, admit cards, rates and other recurring topics are matched by what they're about. A match updates that post (with a dated update note) instead of starting a second page.
  • Language versions of a post, with their own title, address and description in that language, linked to each other with hreflang. Write one from the post page, or list the languages a site publishes in (none by default).
  • Expiry for news and event posts, if you want it. When a dated story's searches end (21 days by default, longer while Search Console still shows it being searched), WriteOut can keep it for readers but out of Google (noindex), refresh it, or redirect it, as you choose per site.
  • Listing pages. New posts get a card, in the page's own style, on the site's hub page (for example /guides/), and join its ItemList; the folder your posts live in counts without setup. A post isn't counted as published (no “published” notice, sharing or indexing request) until it's on its listing page and in the sitemap; WriteOut tries again every hour. New posts also get links from up to three related posts as soon as they're live.
  • Removed and redirected addresses stay removed. WriteOut keeps them out of the sitemap, feeds and every listing it edits, and won't publish a post at one. It reads your site's .htaccess 301 and 410 rules and adds posts you take down, and you can list more under Autopilot.
  • pSEO for WordPress custom post types. The setup now has a third answer to “Does your site already have programmatic pages?”: yes, in WordPress, as a custom post type your theme lays out (e.g. “Cost pages” at /root-canal-cost/udaipur/). Connect WordPress and pick the post type; each post becomes a page in WriteOut, with its title, address and terms as data. Add a sheet (e.g. your prices) and its rows are matched to posts by a column of page addresses. WriteOut writes each section into its own custom field (or the post content, the excerpt, or a field you name), and your theme prints each one where it belongs: Settings → Connection and data → Fields in your theme has the code to add. Sheet rows without a post can become new posts, with a slug pattern and terms from the sheet's columns, as drafts or published.
  • Themes with WriteOut support, and prices through your theme's importer. For WordPress custom post types, WriteOut can write into WriteOut's own fields when the theme has them: all sections in one field, each with the place on the page it goes (chosen per section under “Goes in”), plus the FAQs, the title and the description. It spots these fields by itself. If your theme makes its pages from its own import (e.g. a price list), WriteOut can send it your whole sheet: it reads the importer's columns, suggests how each is filled from your sheet, skips the rows you rule out, checks it without changing anything, then sends it and reads the pages again.
  • A Getting started checklist for programmatic pages. The Pages tab lists the steps for your kind of site (Payload, WordPress custom post type, or from scratch) with what's done and what's next, each linking to where it's done: the data, the plan, this sprint, briefs, where pages go, your first pages, checks, and going live (or copying, with Copy only on). Keyword research, the link map and Search Console are listed for when you're ready. It folds away once everything's in place.
  • Edit a pSEO page's SEO title, H1 and meta description. Every page now has a Title and heading block at the top of its content. WriteOut writes all three for each page (following the page type's title and description patterns), and you can change them per page. Until a page is written, its title comes from the page type's title pattern, e.g. {Treatment} Cost in {City} ({year}). If the brief already has a title, H1 or description section, that section is used instead, as before.

Changed

  • Expiry for news and event posts is now off unless you turn it on (Autopilot → When a news story's demand ends). Pages it had already taken out of Google go back in, as they were.
  • Every publish needs an approval of the post as it is, including updates to live posts, language versions and posts autopilot made. An edit after approving needs approving again. Full autopilot still counts as your approval for its own posts and for watched stories set to update themselves.
  • Research notes and trend figures stay out of posts. Drafts no longer describe search trends, get no Sources section of their own, and keep their title, headline, address and description in the post's language. Drafts over the guide's length are shortened once before you see them. Sites without their own layout get a short summary, key facts, the story, then the site's tool.

Fixed

  • The site's Google tag stays the first thing in the page head. Pages made from a scanned theme put WriteOut's tags ahead of it.
  • A page can no longer go live at a generic address such as /guides/post/.
  • Rebuilding the sitemap, feeds or listings no longer puts back pages you removed or redirected.
  • Page addresses keep their folders. A sheet column of paths such as root-canal-cost/udaipur now gives pages at /root-canal-cost/udaipur/ instead of /root-canal-cost-udaipur/. On WordPress, the parent page (/root-canal-cost/) is made as a draft, and your hub page type takes it over when it publishes there. Pages already published move to their new address on their next update.
  • Sheet pages no longer get a slug as their name and title. When a sheet has a column of slugs or paths (e.g. composite-filling-cost/delhi), WriteOut no longer picks it as the page's name; it uses it to keep each row's address. Renaming the pages (e.g. to {Treatment} cost in {City}) now keeps the same pages and addresses instead of starting them again.
  • WriteOut won't publish over a page your site already shows. Before it publishes a new WordPress page, or moves one to a new address, it checks that nothing else (a custom post type, a plugin's page, a post) is already at that address.
  • Clearer WordPress publishing messages. If WordPress gives a page a different address (…-2/) because something else uses the name, WriteOut says so and how to fix it. On a site without an SEO plugin, it says the meta description can't be shown until you install Rank Math or Yoast.

4 November 2026

Added

  • Plan one part of the site at a time. On a site with several kinds of data, the pSEO idea step asks what to plan for (e.g. cards, or issuers). Only what you tick, with its collections and page types, goes into the plan.
  • Never write to. pSEO Settings → Connection and data lists your CMS collections; tick the ones WriteOut may read but never change. Out of the box that's every collection your pages take their data from (e.g. the cards a recommender uses), so page content only ever goes to the content collection (e.g. Card infos). A send rule that would change a protected collection is skipped, and the send says so.
  • Search data filtered per page type. pSEO reports, “On the page?” and the optimization overview now count only the searches that belong to a page type: pages under its own address (e.g. monzy.co/cards/…) and searches without your brand name in them. WriteOut works both out from the page address and your site; change them under Page types → Technical → Search data for these pages.
  • A rich text editor for pSEO pages. Rich sections and FAQ answers are edited as formatted text, with a toolbar for headings, bold, italics, lists and links, instead of HTML tags. “HTML” shows the tags if you want them. Pasted text keeps its headings, lists and links but not its fonts and colours.
  • pSEO sprints. Work on a few page types at a time: each page type has an In this sprint switch (Page types, in the setup and in Settings). Page types that are off get no new pages, briefs or writing, and bulk writing only picks pages from the sprint. Approving a plan turns on its first page type and writes only that brief; turn the next one on when you're ready, and WriteOut writes its brief then.
  • Keywords matched to your items by meaning. When you upload keyword research, WriteOut matches each keyword to the item it's about: by name first, then by meaning with Claude for the rest (short names, nicknames, misspellings, other word orders). Comparisons, “best” lists and branded searches stay unmatched. Settings → Keyword data shows how many matched and can match them again.
  • Headings that follow the searches. Each item page is written with the keywords matched to its item (biggest first, no branded ones), and its H2s and H3s come from those searches. The sections and their order stay as in the brief; the headings and what's under them can differ from page to page.
  • An internal link map for pSEO pages (Settings → Internal links). Use rules (e.g. card pages link to their category pages and to 3 cards from the same issuer), a CSV of from → to links with optional anchors, or both, each with its own switch. Pages are written with their mapped links, and a new check and an Internal links panel on each page show the links out (which it has, which are missing) and the written pages linking in.
  • Copy only, for testing pSEO without writing anywhere. A switch under pSEO Settings → Connection and data. While it's on, WriteOut writes and checks the pages but never sends them to your CMS or site: Send is replaced by Copy buttons on every section (formatted, so it pastes cleanly into your CMS editor; tables also paste into a sheet) and a Copy the whole page button that labels each section with the field it goes in. It's on for new pSEO sites; turn it off when you want Send to write.
  • Programmatic pages for sites that don't have any yet. The pSEO setup now asks whether your site already has programmatic pages. If it doesn't, give WriteOut your data as a sheet (a CSV or Excel file, or a Google Sheets link it reads again on every sync), one row per page, e.g. a treatment and city. Name each row's page with a pattern like "{Treatment} cost in {City}". WriteOut plans the page types and their addresses, writes the pages and publishes them on your site. On WordPress each page becomes a Page at its address (the parent pages it needs are made as drafts), published or saved as a draft per page type, with Rank Math or Yoast titles and descriptions. On a static site (Hostinger or GitHub Pages) each page is a file in your site's theme, plus a sitemap of the pages. WriteOut never overwrites a page it didn't make.
  • Publer labels. Set labels for carousels, reels and link shares in the Publer settings (comma separated, as named in Publer); every post WriteOut sends to Publer carries them, so you can sort and schedule by label there.
  • An experimental switch to attach the post's link to carousels and reels in Publer, for Publer's Link in bio. Publer's API doesn't document a link for Instagram posts, so it's off by default; the link always goes in the first comment.
  • Repurpose live posts automatically. Turn it on under Social design → Repurpose defaults: every day WriteOut makes carousels (and reels, if you want them) for live posts that don't have them, posts that just went live first and then older ones with the most Google clicks, up to the number a day you set. Each one goes to Publer as soon as it's made: into Publer's auto-scheduling (Publer picks the time within the days you set), as a draft for you to schedule, or straight out. Anything that doesn't fit waits for you on the post's Social tab.

Changed

  • The pSEO Optimization overview uses keywords matched by meaning. Keywords matched to an item count towards its page in the search patterns, and “keywords no page covers” leaves out matched and branded ones.
  • The pSEO plan step sends less to Claude: each data type's field names, not their sample values.
  • pSEO FAQ answers are rich text. WriteOut writes answers with paragraphs, lists, bold and links where they help, and sends them to your CMS as rich text. FAQ schema still gets the plain text.

Fixed

  • A new pSEO site without a CMS no longer asks you to connect one. The Pages tab, Settings and the setup's first step now follow your answer to “Does your site already have programmatic pages?”: they ask for that answer, then for your sheet (or your CMS), then for your idea, and link straight to that step.
  • Writing a pSEO page no longer fails with “'bool' object is not iterable” when a table section is linked to a CMS field that holds an on/off switch. WriteOut skips that field when it looks up the values your table columns allow.
  • Saving page types no longer fails with a server error when a FAQ or table section is linked to a CMS field that holds a single value (such as an on/off switch) instead of a list. WriteOut now skips that field when reading what's live, and asks you to pick the list field before it sends.
  • Saving a big pSEO plan works. The page types step failed with "Too many fields" once a plan had about 60 sections in all; it now saves plans of any realistic size.

3 November 2026

Added

  • Post a carousel or reel again, now or later. Each network on a post's Social tab has *Post again* once it's been shared: leave the time empty to post now, or pick a date and time and Publer schedules it.
  • A quality score for every programmatic page. Each page is scored out of 100 on checks drawn from Google's guidance for pages built at scale: how much of it is unique next to its sibling pages, substantive words, facts from its data, answer-ready FAQs (40-60 words), a title with the name and year, a first-hand note, freshness, and two that Claude judges (something only you have; would it deserve to exist without search). Pages under the pass mark can't be sent (or you send them anyway with a reason). Each page shows its score as a strip of checks with what to fix.
  • Your own gate. Per page type, change the pass mark, weights and targets, add your own yes/no checks, or drop in your gate document and WriteOut turns its rules into the profile.
  • Your notes. Sections only you can write, such as a founder's note per card category, get a draft from WriteOut with [brackets] where your real experience goes. Edit and accept it (bracketed parts must be filled first), and it appears on every written page that uses it, and is sent to the CMS with them. Drafts waiting for you show on Today.
  • Optimization for programmatic pages. Once Search Console is connected, every page shows the searches Google already shows it for, with position, impressions and whether the page answers each one. *What should this page add?* writes a report: what to add and where (a section, a new FAQ, the title), for which searches, with draft text from the page's own data. *Rewrite with these* hands it to the page's next rewrite, which then goes through review as usual.
  • Patterns across pages. The new Optimization tab finds searches many pages get ("{name} annual fee" on 4 card pages, answered by none). *Add to the brief* fixes all of them on their next rewrite. It also lists the pages closest to page one, and keywords no page covers yet (ideas for new page types).
  • Keyword data. Upload your keyword research as CSV from Ahrefs, Semrush, Keyword Planner or a sheet (Settings → Keyword data). WriteOut reads the keyword, volume, difficulty, CPC, intent and URL columns, matches each keyword to its page, and uses them in the reports. A search naming two items is left for comparison pages.
  • Programmatic pages: a second module next to the blog. For sites made of many pages built from data, such as one page per product. A site can be a blog, programmatic pages, or both, and only shows the tabs it uses. "New site" asks which, and the setup wizard walks a programmatic site through its data source, what the pages are about, page templates, and checks and review. Every one of these can be changed later under Settings.
  • Page templates you set up yourself. Each template lists the sections WriteOut writes (rich text, FAQs, small tables, SEO fields), where each one goes in your CMS, how long it should be and how to write it. *Read sections from an existing entry* fills the list in from a page you already have. Sections you leave unticked stay exactly as they are in the CMS.
  • Pages written from their own data. WriteOut reads your data from Payload CMS and keeps a page list for each template, with what's already live. It writes the next pages in your priority order, using only that page's data. Each page then gets its checks: every section written, every number on it found in its data, not a near-copy of its sibling pages, no open data alerts, data checked recently, and signed off. You can edit any section, rewrite with notes, and sign off (in the name of the expert who reviews pages, if you set one).
  • Data checks against the web. WriteOut compares the fields you pick (fees, rates and so on) with the official page and other reliable sources. Differences arrive as alerts labelled *Our data* and *Proposed*, with the source link and a confidence level. Your data is never changed: accept an alert to note it for updating in your CMS, or dismiss it.
  • Plans from a one-line idea. Describe what you want ("a page for every card, plus collections like all cashback cards"), add a link, and WriteOut reads your data and references, searches what ranks for those queries today, and drafts the plan: page types, addresses, queries, why each page deserves to exist, quality gates, internal links and rollout. Revise it with notes; approving it adds its page types. A site can hold several plans.
  • References. Upload what you already have, once, in the wizard or in Settings: design screenshots or PDFs, an example page (file or link), a brief in Markdown, a product doc, a standard list (CSV), a quality gate document. Plans and briefs follow them. A list becomes a standard list straight away.
  • Briefs for every page type. WriteOut writes the brief from the plan and your references, or imports your own. Each section says what it's for, the quality signal it earns, the data it uses, its length, where it goes in the CMS and who fills it: WriteOut, the data, sourced quotes, or you.
  • Collection pages. Besides one page per item, a page type can make one page per group, such as every card of one reward type, written from all the items in it and linking to their pages.
  • Send rules and the quality gate. A page that fails a check can't be sent; *Send it anyway* asks for a reason and saves it with the page. Each page type sets where it goes in the CMS and what a send also changes, such as keeping the item out of the sitemap, which is the default when your data has such a switch.
  • Sending pages to the CMS. A signed-off page goes to its content entry. New entries are created switched off; updating an entry that's already live needs your confirmation. Standard lists (for example, one correct name for each issuer, with its other spellings) keep names consistent on every page. Today shows pages to review, pages ready to send and open data alerts.

Fixed

  • Instagram carousels go out through Publer. They were sent in a format Publer accepted but then dropped, so the carousel never reached Instagram or Publer's queue. They now use the multi-photo format from Publer's documentation.
  • Carousels and reels shared through Publer report their real status. Instagram can take a few minutes to publish them after Publer accepts the post, so instead of “not found”, the log now says it's still being published and adds the result a few minutes later, with a link to the post on Instagram.
  • “Post everything that's ready” no longer posts the link to Instagram as a photo when the post has a carousel or a reel. Instagram gets the carousel or reel; the link still goes to Facebook, X and Pinterest.
  • Sharing through Publer no longer reports “not found in Publer” for posts that went out. After a share, WriteOut looks the new post up in Publer to report its status. Publer's search missed captions that start with an emoji, a hashtag or a line break, so the lookup now also reads each account's latest posts and matches them itself.
  • Posts sent to Payload get a featured image. Set a default under the Payload settings: paste the image's address from the CMS's media library, its file name or its id, and every post sent uses it. A post whose own Featured image URL is already in the media library uses that instead, and an image an editor picked in the CMS is kept.

Changed

  • Open goes to the post itself. After a share, the Open link on the post's Social tab and in the share log goes to the post on Instagram (or Facebook, YouTube) once Publer reports it, instead of Publer's home page.
  • Programmatic pages are set up in three steps. Connect your CMS, and WriteOut works out your data by itself and says it in a sentence ("Your cards are in recommender-cards. Each one's page content is in card-info…") for you to confirm. Then write your idea in a line and approve the plan; WriteOut writes each page type's brief.
  • Briefs read like a page outline. One line per section that you can edit, who fills it, and where it goes. Drop a design, an example page or your own brief on a page type and WriteOut rebuilds the brief from it. CMS fields, matching and send rules are folded under *Technical*.
  • Preview a page type before writing hundreds. *Preview on…* writes one real page from the brief and shows it section by section, without saving it.

2 November 2026

Added

  • Send posts to a Payload CMS as drafts. Connect Payload under a site's integrations (CMS address, API key, author, category). Each post then has *Send as a draft* on its Article tab, or every new draft can go automatically. The article, FAQs and sources arrive in the CMS's own rich-text format with headings, links, lists and tables intact, the schema markup is filled in, and WriteOut picks the category. Sending again updates the same draft; WriteOut never publishes and never touches a post that's already published.

Fixed

  • Word downloads no longer fail on some posts. A hidden control character copied in with text (in a title, an FAQ, a link or a source), an FAQ with a missing answer, or an empty keyword made *Download .docx* show a server error. These are now cleaned out, and the document downloads.

31 October 2026

Added

  • Internal links. WriteOut finds the links each post is missing, both ways: the pages it should link to, and your older posts that should link to it. The link text is a few words already in the paragraph, so nothing else in the post changes. Posts Google hasn't indexed yet get links first, from the posts Google already indexed and crawls most. Suggestions arrive on Today when a post goes live; add them with one click. *Scan and suggest links* does the whole site at once, and live posts are republished with their new links up to a daily limit you set.
  • Links for posts Google hasn't indexed, on autopilot. When the next-day check finds a post isn't indexed, WriteOut finds your posts Google already indexes and crawls that should link to it, and adds those links by itself (within the daily limit), then tells you what it added. Or it suggests them on Today, or does nothing: a setting per site, which follows the site's autopilot until you choose.

Changed

  • Posts published to a GitHub Pages site now carry the site's author box after the article and name that author (a person, not the organisation) as the article's author in its schema, when the site provides them.
  • writeout.tech shows what happens after a post goes live. The homepage has new sections on repurposing a post into a carousel, a reel and graphics, on designs that match your site and sharing to your social accounts, and on the Today page. Features has new Repurpose, Your design, Share and send and Built for Google sections, and How it works follows one breakout through nine steps, now including repurposing and sharing. Samples are from kidharmilega.in.

30 October 2026

Added

  • Share images in each site's own design. Every post's share image (what Facebook, WhatsApp, X and Google Discover show) is now drawn in your website's colours, heading font and logo, read in Social design. Sites without a design yet get a clean WriteOut look. On WordPress, a post with no photo or designed cover gets its share image as the featured image, instead of the site's one default picture.
  • FAQ schema on WordPress posts. Posts published to WordPress now carry their FAQs as FAQPage schema, and on sites without an SEO plugin also the article schema (headline, dates, author, publisher, image), which Yoast or Rank Math otherwise provide.
  • Today, the new home screen. It replaces the Inbox and sorts everything across your sites into four lanes: *Publish* (drafts and updates to approve, new breakouts to write), *Repurpose* (carousels and reels ready to share, and live posts still missing graphics, a carousel or a reel, the ones with the most Google clicks first), *Improve* (optimization ideas) and *Fix* (posts, renders and shares that failed, with the reason and *Try again*). Each card has its one next step on it, like *Approve · next slot* or *Share both*. Filter by site or lane, and see what got published, repurposed and shared today.
  • Repurpose… asks what to make. On a live post, pick any of a carousel, a reel, a cover and graphics (WordPress) and a fresh link share, choose English or Hinglish for this post, and tick *Share as soon as they're ready* to post them through Publer the moment they're done (anything that doesn't fit waits for you). *Remember these choices* saves them as the site's defaults, also editable under Social design → *Repurpose defaults*.
  • Where it goes, per network. The post's Social tab lists Instagram, the Facebook page, X, Pinterest and YouTube Shorts with what's been posted and what's waiting, one button each (*Post both*, *Post reel*, *Pin it*), plus *Post everything that's ready*. Networks you haven't set up are greyed out with a *Connect* link. Slides and the video download from the same list.
  • Share with your team on every post: Asana and Trello (greyed out with a nudge to connect when they're not set up, and when it was last sent when they are), and the Word and HTML downloads.
  • A designed cover and graphics for blog posts (WordPress). *Make visuals* on the post page has Claude design a cover and one graphic per key finding in the article, in your website's own look: charts drawn exactly from the article's numbers (dot grids, bars, rings, scales), comparisons, tiers, scorecards, steps and mock-ups of what the article describes, each with a takeaway headline and its source. WriteOut reads your site's colours, fonts, gradients and logo from the website itself (a logo saved on a white box is cleaned up and trimmed), checks every graphic for text that runs off, overlaps or is crammed against a chart, and fixes it. They're saved as WebP (1600×900; the cover 1200×630) and go to WordPress with the post, each placed after the paragraph it explains, with alt text and a caption. Redo one (with a note on what to change), remove it, redo all, see them in the preview, and update a live post with one click.
  • One design for everything Claude makes for a site. Settings → Social design → *Your design* takes any of three things: your website (read automatically when the site is added: colours, gradients, fonts, logo; *Rescan design* after a redesign), a reference image (a screenshot of your site, a brand board or a design you like, which Claude looks at while designing), and a style prompt in your own words. Blog graphics, carousels and reels all follow it.
  • Featured image choice per site. Social design now has *Featured image*: the Pixabay photo (or your own image) as before, or the designed cover from *Make visuals*.
  • Reels from any post. *Make a reel* on the post page turns the article into a 20-second vertical video (1080×1920) in your website's look: Claude directs 5 to 7 scenes where the numbers move (bars grow, rings sweep, counters count up, dot grids fill), WriteOut checks the text stays clear of the apps' buttons and captions, fixes any scene that doesn't fit, and renders the video with music, with scene changes on the beat. Watch it on the page, redo one scene (with a note) or all of it, edit the caption, YouTube title and first comment, download the video, or share it through Publer as an Instagram Reel, a Facebook Reel and a YouTube Short.
  • Music for reels. Five built-in upbeat tracks ("Happy Beats / Business Moves" by Sascha Ende, free to use with credit; the credit is added to the caption for you), your own uploaded tracks, or no music, set per site in Settings → Social design, which also holds the reel prompt Claude follows.
  • YouTube in the Publer settings. Pick a YouTube channel to post reels to as Shorts.
  • Instagram carousels from any post. *Make a carousel* on the post page turns the article into 5 to 10 swipeable slides (about 7) in your brand: Claude designs them, WriteOut renders them at 1080×1350, checks that the text fits and fixes any slide that doesn't. Redo one slide (with a note on what to change) or all of them, edit the caption and first comment, download the slides, or share the carousel on Instagram through Publer, optionally also as a multi-photo post on your Facebook page. The link to the article goes in the first comment once the post is live.
  • Social design settings. Each site has a brand kit for carousels: brand name, Instagram handle, brand colour, fonts, tone, the call to action on the last slide, a logo (uploaded, or the one found on your website) and an editable design prompt. Slides are in English or Hinglish, following the Publer setting.
  • Share posts on social media through Publer. A new integration (Settings → Integrations → Publer): connect your Publer API key and workspace, pick the Facebook page, Instagram account, Pinterest account and board, and X account to post to, the caption language (English or Hinglish) and when to share. Every post is then shared automatically when it goes live: Claude writes a caption for each network; Facebook and X get a link post, Instagram gets the post's image with the link as the first comment, and Pinterest gets a pin linking to the article. Live posts also have a "Share on social media" button.
  • Pick the Claude model. The Claude connection page has a new "Which Claude model" box with two choices: one for writing (drafts, updates, rechecks and fixes, rewrites, web research and Ask) and one for the routine work around it (ideas and scores, briefs, seed banks, topic plans, reading your site). Options: Opus 5.5 (the default, as before), Sonnet 5.5, Haiku 5.5 and Fable 5.1, for your Claude account sign-in or an API key alike.
  • Turn off fast-tracking for top breakouts. Settings → Autopilot has a new "Fast-track WriteOut Score 70+ breakouts" switch, on by default. Untick it and a site's strongest breakouts no longer skip the queue: they're drafted within the daily limit and go live in the next free publishing slot (or when you approve them, into that slot) instead of straight away.

Changed

  • The post page is organised around what's next. A progress bar runs Written → Approved → Live → Graphics → Carousel → Reel → Shared, with the next step clickable, and the main button at the top changes with it (*Approve*, *Share carousel + reel*, *Repurpose…*). The page is split into Article, Graphics, Social and Search tabs.
  • Site settings are grouped in the order of the work: Find topics, Write, Publish, Design and repurpose, Share and send, and Measure, with a meter showing how much is set up and the unfinished rows marked.
  • English or Hinglish for carousels and reels is now set in Social design (it used to follow the Publer caption language), and can be changed for one post from *Repurpose…*.
  • Carousels are now designed like the blog graphics: in your website's own look, with a takeaway headline per slide and charts drawn exactly from the article's numbers, and checked for text that overlaps, runs into a chart or breaks a number over two lines. The progress bar and swipe arrow take your site's colours. A custom carousel prompt saved before this change goes back to the new default.

Fixed

  • Article schema now names the publisher's logo, as Google asks for news articles: the logo in the site's settings, or else the one WriteOut found on the website.
  • Follow-ups to a live story update that story instead of becoming a second page. On busy sites the list of posts WriteOut could update only reached back about 120 posts, so later news on an older story (a price, a result, a storm's next day) was written up as a new, near-duplicate page. Every post from the last 60 days now counts, a draft written under a live post's own address updates that post instead of going up at a "-2" address, and an update idea always updates its post, from any button or from Ask. *Write as new post* still makes a separate page when you choose it.
  • Search Console was sent a sitemap address that doesn't exist after each post on sites where WriteOut keeps the site's own sitemap up to date. Now only the site's sitemap and news sitemap are resubmitted (the news sitemap wasn't before).
  • The brand mark on carousel slides now shows even when Claude gives it an animation or extra style.
  • Settings → Publishing now scrolls to the publishing settings on WordPress and Hostinger sites too (it opened the page at the top, so options like the Pixabay photo setting were easy to miss).
  • Share on social media (Publer) stopped with "'list' object has no attribute 'get'": Publer's replies come in more than one form, and WriteOut now reads all of them. If a reply still can't be read, the error quotes what Publer sent.
  • Sharing through Publer said "shared" even when Publer turned the whole post down, so nothing appeared on the networks. A refusal is now shown as a failure with Publer's reason, and each share's log says what Publer holds for every account afterwards: published (with the link to the post), scheduled, failed, or not found. Facebook and X link posts now carry the full preview (title, description, image) Publer asks for.
  • When a network turns down a post shared through Publer, the share's log now gives the reason Publer recorded (for example an expired page connection), instead of just "failed".
  • A share's log could report another, older post on the same account as this share's result; it now only counts the post just sent. The Publer settings page shows the last share step by step: each request and Publer's exact reply.
  • When Publer takes more than a few seconds, sharing no longer gives up early: the post's log says the share was sent, and adds Publer's result for each network (published with its link, or the reason it failed) once Publer has finished, up to ten minutes later.

29 October 2026

Added

  • Featured photos from Pixabay for WordPress sites. Turn it on per site (Settings → Publishing) after adding a free Pixabay API key in App settings. Every new draft gets a landscape photo picked for its primary keyword; the post's Featured image panel shows it with a dozen alternatives to swap, a search box, and Remove. On publishing, the photo goes to WordPress as a 1200×630 WebP with the primary keyword as its alt text and becomes the featured image. The featured image alt text for other images now uses the primary keyword too.

Fixed

  • When a REST API login plugin on a WordPress site (like miniOrange's) refuses WriteOut's Application Password, the error now says so and how to fix it in that plugin, instead of a bare "no explanation from WordPress".

28 October 2026

Added

  • More optimization ideas on demand. "Show 5 more ideas" under the Optimization ideas list adds the next pages in line, past the weekly limit, whenever you want more; Claude writes their briefs in the background.
  • Send an optimization idea to Asana or Trello. Each idea with a brief gets a Send to Asana / Send to Trello button (whichever the site has set up): one task or card with the brief, the page, the target searches with their position, impressions and clicks, what's missing from the title, headings and text, the searches to keep working, and a link back to the idea. The idea shows when it was sent, with a link to the task or card.
  • A Rebuild from my site button at the top of every seed bank page (one per site when several sites share the bank): it builds a fresh bank from the site's own pages for you to review, and the current bank keeps running until you use the new one.

Fixed

  • Seed bank pages made before the site-built seed banks showed an internal server error. They open again, with every seed and its check result kept.
  • Deleting a seed with an apostrophe in it (like "levi's jeans") did nothing; it asks and deletes again.
  • Download .docx (and Download HTML) showed an internal server error for posts whose address isn't in English letters, like Hindi posts; the file now downloads with its real name. A post source without a title no longer breaks the .docx either, and images with non-English file names upload to WordPress.
  • A post whose page went live is no longer reported as "Publishing failed" when only the blog index page or sitemap couldn't be updated: it shows as published, with a note on the post (and an alert) saying what wasn't updated.
  • The Blog index page and Sitemap file settings accept a pasted page address (like https://example.com/guides/) or a folder, and turn it into the file it means (guides/index.html). A full address there used to make every publish on that site fail.
  • Publishing to WordPress no longer stops at a bare "WordPress said 400 400": when WordPress refuses the SEO title and description fields without saying why, the post is published without them; any other refusal now says which step failed (saving the post, uploading the image, adding tags…), which fields WordPress rejected, and what the server replied when WordPress itself didn't explain (often a security plugin or firewall).

27 October 2026

Added

  • Trello integration. Send drafts and updates to a Trello list as cards, with the post's SEO details, a link back to WriteOut and the post attached as a Word file; pick the board, list, member, label, due date and position, and optionally send every new draft or update automatically. Set it up in a site's Settings → Integrations: once the API key is saved, a link asks Trello for a token that doesn't expire.
  • AI citations, a new tab on every site: how often Microsoft Copilot and Bing's AI answers cite your site, laid out like Performance (last 7 and 28 days with the change, a daily chart, week by week, the pages cited and the searches Copilot ran when it cited you, with their intent, topic and your share of the citations, and citations by intent and by topic). Upload the CSV exports from Bing Webmaster Tools → AI Performance; WriteOut keeps every day you upload, so the history goes back further than Bing's 90 days. Busy searches where other sites get most of the citations are marked low share, and searches no page of yours seems to answer get a Draft a post button.
  • Optimization ideas, a new tab on every site (and in the Inbox, labelled, never among breakouts). Each week WriteOut finds the searches your pages already rank 5 to 20 for (at least 100 impressions in 28 days, adjustable; your brand's own searches left out), checks whether the page has their wording in its title, a heading or its text, and suggests the cheapest fix: a new title, the missing wording, one new section, internal links from your other posts, or a new page when the search wants something else. Claude writes a one-change brief that keeps what already brings clicks. Make this change applies exactly that change to a WriteOut post for your review; the change is logged when it goes live and judged five weeks later on that page and those searches (won, progressing or stuck), and the tab shows which fixes work on your site. At most five ideas a week; pages changed in the last five weeks are left alone.
  • Seed banks built from your own site. Adding a site now asks what kind of site it is (News, B2B SaaS, Ecommerce, Creator, Local business or Others) and the country it writes for (or worldwide). WriteOut reads the site (menus, sitemap, headings, feeds, product types) and builds a seed bank from what it says: literal seeds in the site's own words and lateral seeds a step sideways, picked with the playbook for its category, each tagged with where it came from and which move made it, and seasonal ones tagged. Every seed is tried in Google autocomplete and in Google Trends over the past 90 days before you review it; ones people only type into autocomplete are kept but left out of runs. Breakout runs then check the bank over the past 7 days. Brand seeds are listed separately and stay off until you turn them on (News sites use them freely). The bank page shows which moves find breakouts. Existing sites keep their bank until you click Rebuild from its site and approve the new one.
  • A seed whose rising searches mostly have nothing to do with it is flagged, and those searches are left out (not on News sites, where rising lists are names and events).

Fixed

  • Publishing showed the wrong host and no progress. A post going to GitHub Pages said "Publishing to Hostinger…" for minutes. The post page now says which step it's on: checking the facts again (when the research is a few hours old), checking the links, then publishing to GitHub, WordPress or Hostinger.

Changed

  • Suggest improvements on a post or page now uses the same check and writes a one-change brief, not a full plan.
  • Performance's "Do this next" now shows optimization ideas; the older improvement ideas stay listed until you act on them.

25 October 2026

Added

  • GitHub Pages publishing. A site built from a GitHub repository can publish straight from WriteOut: each post, update or take-down is one commit that writes the post where the site's own build keeps it and a live copy with the site's nav and footer (live about a minute later), the /blog/ listing, its RSS feed and the post's sitemap entry, and nothing else in the repository. Connect it with a fine-grained token for just that repository; Test connection checks it. Unpublish, Refresh live pages and IndexNow work too.

24 October 2026

Added

  • The WriteOut Score in Telegram and push alerts: "Draft ready", "Publish now" and autopilot alerts start with the idea's score (e.g. "WriteOut Score 82 · publish now"), and the breakouts alert lists each idea's score.
  • WriteOut's breakout publishing strategy, for every site. Each idea gets a WriteOut Score out of 100: growth ×5 + intent ×4 + gap ×4 + evergreen tail ×4 + tool potential ×3, each factor 0-5. Growth is measured from the Trends data itself (breakouts, percentage rise, Trending now volume) and only searches rising in the last 1-7 days score high on it, so no growth figure is ever invented; Claude rates the other four against fixed definitions. 70 or more: publish now (P1/P2). 50-69: a fast explainer (P3, a shorter brief). Under 50: skipped. The score and its parts show on every idea. This is the rule KyunTrend grew on; a site's own topic rules can add to it. (Proprietary: the public site names the score and its bands, not the weights.)
  • "Publish now" ideas skip the queue. Ideas with a WriteOut Score of 70+ are drafted straight away, even past the daily draft limit; Fix with Claude runs on them by itself as soon as the draft (or update) is written; the main button, the Telegram and push buttons all say Publish now and publish at once, outside the publishing slots and the daily post limit; and on full autopilot they go live without waiting for approval.
  • Fix with Claude on the publish checklist: one click sends only the flagged problems (keyword in the H1, title and meta, the slug, stale wording, a missing official link, links that don't open, a missing section…) to Claude, which fixes just those, looking up official addresses first when one is missing. The previous version is saved, and a live post waits for republishing.
  • Publish checklist on every post's review screen: green, amber or red for the keyword in the H1, a slug that names the subject, title and meta length, page language, outbound link tagging, a primary source, wording that goes stale ("today", "Friday's final", "we hadn't seen…") and how fresh the research is. It runs again when the post is published.
  • How-to posts must link the official site. A login, admit card, apply, result or download post with no link to the official portal is held back for review instead of publishing, with a Publish anyway button. Can be turned off per site.
  • Facts rechecked before publishing. When a draft's research is older than a few hours (3 by default) at publish time, WriteOut looks the key figures up again, corrects any that changed, replaces overtaken wording, saves the old version and notes what changed on the post.
  • Your posts' own sections, in every draft. WriteOut reads the blocks your published posts have beside the article (a TL;DR, a Key facts box, a Trend Monitor) with their markup, and every draft and update writes them, in the same order and styled by your site's CSS. Or describe your own layout in words. The checklist warns when one is missing.
  • Link rules per site. Tracking parameters for every link that leaves the site, and affiliate tags by domain (e.g. the Amazon tag) with rel="sponsored nofollow".
  • A share image for every post: a 1200×630 card with the category, headline and site name, in any Indian script, used for social shares, Google Discover, the article schema and the sitemap.
  • Refresh live pages for static sites: re-render recent posts with WriteOut's current output without counting it as an update.
  • Sections from a post you pick: when Find sections misses, give a post's address or upload its saved .html.
  • Official links get into the draft: research looks for the official portal's exact address, how-to drafts must link it (first paragraph, steps, the TL;DR action), and each site keeps a list of official sites drafts reuse. A post held for a missing link gets an "Add the official link" box that inserts it and remembers it.
  • Topic rules per site: your scoring and skip list are used when ideas are picked from each run.
  • Real Trends figures in posts: the writer gets the actual growth numbers behind the topic (and when they were checked) for sections like a Trend Monitor, and is told never to invent them.
  • Automatic calls to action by topic (e.g. a credit-card offers link whenever a post mentions credit cards) and a disclosure line per affiliate programme, added at the bottom when a post has that kind of link.
  • Review schema for review posts (Movie, Product, Book…), with a rating only when the review gives one.
  • Author profile link (e.g. LinkedIn) in the article schema.
  • More checks: the keyword in the title and meta, slugs that start with the subject, links that open (checked before publishing, or with Check links now), and the live page answering after publishing, with an alert if not.

Fixed

  • Site sections were placed inside the article text, where the site's article styles (KyunTrend's .prose) broke them: the TL;DR showed one word per line even with the right markup. A TL;DR and Key facts now go just before the article text and a Trend Monitor just after it, where the site's own posts have them. Sections that share a class (Key facts and Trend Monitor are both "box") are told apart by all their classes.
  • Find sections still came back empty when the post it compared against wasn't a post (a tool or category page) or had moved. It now compares with up to three other posts from the same part of the site, tries another post when the saved one doesn't load, and errors name the post it read.
  • Find sections found nothing on KyunTrend. It took the whole <article> for the article text, so the TL;DR, Key facts and Trend Monitor beside the text looked like part of it. It now narrows to the block that holds the text (KyunTrend's story body) and finds all three.
  • Pages zoomed in on iPhone after tapping a text box, running off the right edge and leaving the tab bar mid-screen. Text boxes now use a 16px font on phones, which stops Safari's zoom.
  • Site sections lost their inner markup: a draft could keep the TL;DR's classes but drop the wrapper inside each bullet (KyunTrend's <span class="tldr__t">), so the site's layout broke the bullet into one word per line. Bullets now get the site's wrapper back when a post is published or refreshed, and drafts are told to keep it.
  • The phone tab bar could sit mid-screen on iPhone after scrolling or closing the keyboard; it's now held to the bottom of the screen and hides while the keyboard is open.
  • Topic searches stuck on "Working" after the app restarted mid-search. An interrupted search now says so with a way to start again, and one running over two hours counts as stopped. Seed-bank generation gets the same fix.
  • Site sections were dropped from new posts. The theme scan copied the page around the article but treated blocks like the TL;DR and Trend Monitor as one post's leftovers, so new posts never had them. Post markup also lost its classes, so the site's styling didn't apply.
  • The Google News sitemap stayed empty when it had no entry to copy. It now gets every post from the last two days, with publication name and language, and drops older ones.
  • Updates didn't look like updates. dateModified, the page's "Updated" time and the sitemap's lastmod now move when a post's content changes, and only then.
  • Hindi and other-language posts were tagged as English. lang and inLanguage now follow the language the post is written in.
  • Outbound links in the article body had no tracking parameters; only the sources list did.

Changed

  • Author and brand has its own row in a site's Settings (author name, author profile, organisation, logo), instead of being hidden in the site details page.
  • Drafts and updates follow stricter writing rules: the search query in the H1 in its own script, dates written out in full, official sources first with unofficial figures labelled, the official link readers searched for, internal links only on topic (never affiliate pages from news), and the site's matching tool linked. Slugs always name the subject, meta descriptions are cut to 155 characters, and one-word generic keywords are dropped.

23 October 2026

Added

  • Free breakout scanner at writeout.tech/tools/breakout-scanner: today's trending searches by country without an account, then a free Google sign-up to scan your own site (3 scans every 30 days). Each scan picks the 2–3 trends a site could write about, with a brief draft for each. Free users and their scans are listed in App settings.
  • Built-in blog at writeout.tech/blog, published from the app: index, categories, RSS, sitemap, structured data, Unpublish and View on blog buttons.
  • Website: features page, animated walkthrough, 11 industry pages with their own example report and AI-answer example, examples and the KyunTrend case study, contact, privacy and terms, docs in the footer, Google Analytics.
  • The AEO angle across the site: breakout posts as the first source AI answers can cite.
  • Publish queue across all sites, with a site picker and every stage from idea to live.
  • Redesign around the core loop: Inbox, site tabs, slim Performance with details, phone tab bar.
  • A clearer Delete site section in each site's settings.
  • Telegram both ways: ask the assistant from the chat; chats have their own workers and history.

Changed

  • Homepage rebuilt for conversion, leading with KyunTrend's average position 8.6 at nine days old and naming it as our own test site; the FAQ recommends an Anthropic API key.

Fixed

  • Posts and ideas ran off the screen on phones; each row is now a card.
  • Phones kept old styles after a deploy; the stylesheet is now versioned.
  • The phone tab bar drifted on iPhone.

22 October 2026

Added

  • Seed banks: automatic, self-expanding Google Trends discovery per niche.
  • Writing guide per site and an automatic quality check.
  • Autopilot and notifications: publishing slots, Telegram and push approvals, a morning summary.
  • Search Console, indexing and topic clusters: weekly performance, wins and risks, sitemap resubmits, IndexNow, index checks.
  • Developing stories: update ideas, dated updates to live posts and watched stories.
  • WordPress publishing, Word downloads for any CMS, integrations starting with Asana, and the assistant.
  • The full Trending now list, and drafts from any rising query.
  • Docs at writeout.tech/docs.

Fixed

  • Google Trends rate limits: shared spacing and cache, a cooldown, and runs that keep what they fetched.

21 October 2026

Added

  • WriteOut: breakout searches from Google Trends to researched drafts to published posts on static sites through Hostinger, in the site's own theme.
  • Site feeds: new posts listed on the site's home and category pages, sitemaps and RSS.