You have found a post that does well in search. It might be one of yours, written years ago in a voice you no longer use. It might be someone else's, and you want your own version on the same subject. Either way, RankMill can bring it into your project and write it again in your voice.
This post shows you how to import it and walks through the three import choices. It covers when a rewrite is the right call, what a rewrite keeps and changes, and what to check before the new version goes out.
The whole process at a glance
Here is the short version:
- Bring the post in by pasting it or giving its URL.
- Pick Rewrite as the import choice.
- The writer writes the post again in your project's voice.
- You check the facts, the voice and the structure.
- You schedule it or publish it.
The rest of this post goes through each step.
Two ways to bring a post in
Open the project the post belongs to and start an import. You can get the post in two ways.
- Paste it. Copy the text and paste it in. This works for anything you can copy, including a draft that has never been online.
- Give its URL. If the post is on a public page, give RankMill the address and it fetches the post for you.
RankMill can only fetch a public URL. If the page sits behind a login, paste the text instead.
Once the post is in, you pick what happens to it.
The three import choices
As is
As is stores exactly what you supplied and marks the post finished. No agent runs.
Use it when the post is already right and you just want it in RankMill. A good example is moving your older posts across so you can schedule and publish everything from one place.
Restructure
Restructure tidies the post into clean markdown. It does not change your wording.
This is the one for messy copy. Text pasted from a web page or a document often comes with odd spacing, broken lists or headings that are not really headings. Restructure sorts that out and leaves your sentences alone. It is free.
Rewrite
Rewrite keeps the subject and the facts, and writes the post again in your project's voice. This is the one for a post that ranks well and that you want your own version of.
A rewrite is a write, so it spends credits. Writing a post uses 10. While RankMill is in early access, each team gets 100 credits a month, shared across everyone in the team. If a write fails, its credits stay spent, but writing that failed post again is free.
When rewrite is the right call
Rewrite makes sense when most of these are true:
- The post is not yours, and you want a version of your own on the same subject.
- The post is yours but does not sound like you. Maybe it came from an old writer, an agency, or an earlier version of your brand.
- The subject still matters to the people who read your blog.
- The facts in it still hold.
That last point matters more than it looks. A rewrite keeps the facts. It does not go and check them for you. If the post is full of out-of-date figures, the rewrite will carry them across in a nicer voice.
So pick another choice when:
- The wording is fine and only the formatting is off. Use Restructure.
- You just want the post in RankMill so you can schedule or publish it. Use As is.
- The facts are wrong. Fix them first. If you are pasting, you can edit the text before you import it. Otherwise, fix them in the new version before it goes out.
What a rewrite keeps and what it changes
What stays the same
The subject and the facts stay. A rewrite is not a new topic. If the original says something happened, the new version says it too.
This is why you should read the facts in a rewrite as the source's claims, not yours. More on that in the checks below.
What changes
The voice changes. The writer reads two things from your project:
- The website profile. This is the document that describes what your business sells, who it sells to and how it sounds. It is where the voice of your posts comes from.
- The writing rules. These are the plain sentences every agent on the project has to follow, like "Never use em dashes" or "Keep paragraphs to three sentences or fewer".
Writing rules belong to the project. So if you import the same post into two projects, you can get two posts that sound nothing like each other.
If the voice comes out wrong
If the rewrite does not sound like you, the cause is usually the profile or the rules, not the post. Fix it there and every post you write after that will follow.
You can edit the profile by hand in the Profile tab, which saves itself. Or ask for an AI edit, which comes back as a proposed version you can accept or turn down with "Keep mine". Every version is kept, so you can always go back.
Changing the profile does not rewrite the post you already have. For that one, use the editor, covered below.
What to check before the new version goes out
A rewrite is a run by an agent. Read it before it goes anywhere. Here is what to look for.
The facts
Go through every number, date, price and name. Ask two questions about each one.
- Is it still true? The original might be old.
- Is it true for you? If you started from someone else's post, some facts will be about them: their prices, their customers, their product. Those are not your facts. Take them out or replace them with your own.
The voice
Read a few paragraphs out loud. They should sound like your website profile describes. Look for words your business would not use and anything that breaks your writing rules.
That it is really yours
If the source was someone else's post, the new version should not read like their post with the words swapped. Add what only you know. That could be an example from your own work, a step you do differently or advice you give your own customers.
The structure
Check that the headings say what each section is about, and that the post is easy to skim. Cut anything that does not help the reader.
How it fits with your other posts
An imported post can quietly contradict something you have already written. The auditor is good at catching this.
The auditor reads every finished post in the project that has not been published yet, all at once. It writes down up to five things that are wrong, such as two posts that contradict each other, a post that has drifted from your profile, or a claim that no longer holds. Each finding becomes a task, and RankMill fixes them one at a time. Audits and their fixes are free.
Fixing what you find
You have two ways to make changes.
Edit by chatting. Open the post and tell the editor agent what to change, in your own words. It remembers the conversation, so "make that shorter" still knows what "that" was a few messages later. Each change shows up as a card you can undo. Edit turns are free.
Edit it yourself. The post is editable in place, in a block editor that saves as you go. A one-word fix does not need an agent at all.
Every version of the post is kept in its version history, so you can put an older one back if a change goes wrong.
Getting the new version out
Once it is imported, the post behaves like any other post in RankMill. You can view it, edit it, audit it, schedule it, download it and publish it.
Give it a publish time from the post itself or from the calendar, where you can drag a planned post onto another day. When the time comes, it goes to your project's publish destination: a GitHub repository, a WordPress site, a Ghost site, a webhook you run, or our API.
RankMill does not publish anything unless you press Publish, give the post a time, or switch on automatic publishing. If your project publishes automatically, do your checks soon after the rewrite finishes, before the post reaches a slot.
One last thing: RankMill is not a rank tracking tool. It will not tell you how the new version does in search. It gets you a post in your voice, checked by you, and out to your site.