The editor.
A proper rich-text editor with autosave, a re-tune tool on any selection, and 20 versions of undo. Two things to know: autosave doesn't create a version, and Delete only archives.
Once an article is generated, the body becomes a proper rich-text editor. You can type in it like a document, and it saves itself. Two things are worth reading before you rely on it: how the saving actually works, and what “delete” really does.
The toolbar
A formatting bar sits above the article and stays there. Left to right:
- Block type — a dropdown: Paragraph, Heading 1, Heading 2, Heading 3, Heading 4. It always shows the block your cursor is currently in.
- Bold · Italic · Strikethrough · Inline code
- Bullet list · Numbered list
- Blockquote · Divider
- Link — prompts you for a URL. Leave it blank and press OK to remove a link. Links are inserted so they open in a new tab.
- Clear formatting — strips every mark from the selection and flattens it back to plain paragraphs. It's blunt; use it deliberately.
- Voice — pushed to the far right, in orange. It opens the re-tune tool. Re-tune a passage →
The selection bubble
Select any text and a small floating bar appears above it, carrying the same set — paragraph, H2, H3, the inline marks, lists, quote, divider, link, clear formatting — plus a Re-tune ▾ button on the end.
Re-tune is the reason the bubble exists. Highlight a passage you don't like, pick an operation (improve it, put it in your brand voice, shorten it, lengthen it, change the tone…), and you'll get a preview. Nothing in your article changes until you accept it. The eight operations →
Autosave, and forcing a save
You do not need to save. The editor does it for you, 600 milliseconds after you stop typing — so a continuous burst of typing produces one save at the end of it, not one per keystroke. If nothing has actually changed, it doesn't send anything.
The status pill at the top-left of the editor tells you where you stand:
| It says | It means |
|---|---|
| Saving… | A save is in flight. |
| Saved | It landed. Fades back after a couple of seconds. |
| Last saved 14:32 | Idle, with the time of the last successful save. |
| Couldn't save | The save failed — usually the network. Your text is still in the editor. Fix your connection and make another edit, or press Ctrl/Cmd+S. |
Ctrl+S (or Cmd+S on a Mac) cancels the pending debounce and saves immediately. Use it before you close the tab if you're impatient — and if you ever see “Couldn't save”.
Saving and versioning are separate things. Autosave overwrites your article in place — it does not add a snapshot to version history. Versions only exist when you ask for one, or when a restore auto-creates one. Before you make a big structural edit, save a version deliberately.
The 60,000-character cap
The editor stops accepting input at 60,000 characters. That's roughly 9,000–10,000 words — comfortably past the longest article BlogCraft will generate (5,000 words), but reachable if you keep pasting into one piece.
It's a hard cap, not a warning: past it, typing simply doesn't register. If an article is bumping against it, it isn't one article any more. Split it.
The live word count sits at the top-right of the editor, next to the save pill.
Version history
In the article's ··· menu → Version history. It slides in from the right and lists your snapshots, newest first.
Each row shows a label, the word count and the Content Score at the time it was taken.
- The last 20 versions are kept. Saving a 21st quietly deletes the oldest. There is no way to raise the cap or pin a version.
- Saving a version is manual. If you don't give it a name, it labels itself — something like “Manual save · Mar 4 · 1,840 words”.
- A version stores the title, the body, the word count and the score. It does not store your schema, your entities or the rest of your SEO pack.
Restoring — and undoing a restore
Every row has a Restore button. It swaps the article's title and body back to that snapshot. You'll be asked to confirm first, because it overwrites what's on screen.
Before it restores anything, ScoutRival snapshots your current state first and files it as “Pre-restore · <date>”. So if you restore the wrong version, open version history again and restore the Pre-restore entry. You cannot lose work this way — the only thing that can lose it is running out of your 20 slots.
One honest limit: a restore brings back the body and title only. The FAQ schema, the entities and the SEO pack stay exactly as they are now — they don't roll back with it. If you restore an old body, re-run the re-optimise from the SEO pack so the two agree again.
Duplicate
From the article's ··· menu, or from the row menu in your library.
You get a full copy titled “Copy of …”, with a new slug, as a fresh draft. The body, the outline, the schema, the entities, the keyword, the intent, the length and the scores all come across. It costs nothing — no AI runs.
It's the right move when you want to try a different angle on a piece you've already got right, without risking the original.
Delete is an archive
Deleting an article does not destroy it.
- The article's status changes to Archived. The row, its body, its versions and its history all stay in the database.
- It disappears from the default list — but it's one filter away. Set Status: Archived on the hub and it's there.
- Every active share link on it is revoked immediately. Anyone holding a public URL to that article gets nothing from that moment on. That part is irreversible: revoking a link is permanent, and un-archiving the article doesn't bring the old link back — you'd create a new one. Sharing & exporting →
ScoutRival has no way to erase an article for good today. If you need something genuinely gone — a legal or client-confidentiality reason — email support and we'll remove it for you.