You have a week of posts lined up. Each one reads fine on its own. But put two of them side by side, and one says something the other says is wrong. A reader who finds both will trust neither.
The project audit is for exactly this problem. It reads your unpublished posts together and writes down what is wrong. Then RankMill fixes each problem for you. Here is how it works, and when to run it.
What the auditor reads
The auditor reads every finished post in the project that has not been published yet. It reads them all at once, not one at a time.
That second part is the point. A post can be well written, on voice and true to your website profile, and still clash with the post going out the next day. You only see that kind of problem when you look at the posts as a set.
A few things follow from that:
- Only finished posts count. A suggested topic that has not been written yet has no post to read, so the audit does not cover it.
- Published posts are left out. Once a post is out, the auditor no longer reads it. If you want a post checked, audit it before it goes out.
- Where a post came from does not matter. A post written from a topic, one written from your own idea and one you imported are all read the same way.
So think of the audit as a check on what is about to go out. Run it while changes are still easy to make.
The kinds of problems it writes down
The auditor writes down up to five things that are wrong. They fall into three groups.
Two posts that contradict each other
This is the one in the title. One post says one thing. Another post says the opposite.
Say one post tells readers you work with businesses of any size. A second post says you only take on small teams. Or two posts give different steps for the same task. Each one looks fine alone. Together, they make you look unsure of your own business.
These slips are easy to make. Topics get suggested at different times and from different angles, and each post is written on its own. Reading posts one by one, you will rarely spot the clash. Reading them together, the auditor can.
A post that has drifted from your profile
Your website profile is where the voice and the facts in your posts come from. Every agent reads it. You can also change it whenever you like, by editing it in the Profile tab or by asking for an AI edit.
Posts written before that change were written from the old version. Maybe you changed how you describe who you sell to. Maybe you dropped a service. An older post can still say the old thing, and the auditor writes it down as drift from your profile.
A claim that no longer holds
Some claims go stale. Things can change between the day a post is written and the day it goes out. A post written before you changed your opening hours, for example, might still list the old ones.
If a claim in a post is no longer true, that is a finding too. Better to catch it now than after readers have seen it.
When there is more than five
Each audit writes down up to five findings. If you suspect your batch has more problems than that, run another audit once the first round of fixes is done.
How each finding becomes a fix
You do not have to turn the findings into edits yourself. Here is what happens after the auditor has read your posts and written its findings down.
Each finding becomes a task. RankMill then works through the tasks one at a time. For each task, it rewrites the post the task points at. The project's Audit tab shows what is still outstanding, so you can see which tasks are left.
Audits and their fixes are free. Credits are only spent by writing a post. So there is no cost to running an audit whenever you think one is worth it.
Checking the rewritten posts
A fix is still a change to your post, so give it a quick read. You have the usual tools for that:
- Edit by chatting. If something is off, open the post and tell the editor what to change, in your own words. Edit turns are free.
- Edit it yourself. For a one-word fix, change it in the block editor. It saves as you go.
- Go back. Every version is kept in the post's version history. If you prefer an older version, you can put it back.
When to run an audit
You do not need to audit after every post. Some moments matter more than others.
Right after the website profile changes
This is the clearest one. Every post you have waiting was written from the profile as it was. Change the profile, by hand, with an AI edit or by asking RankMill to rebuild it, and those posts may no longer match.
So make it a habit. Change the profile, then run an audit before any of the waiting posts go out.
Before a week of scheduled posts goes out
If you plan posts on the calendar, you may have several set to go out over the next few days. That is a batch, and a batch is where contradictions hide.
The same goes if the publish cadence is on. RankMill keeps the next two weeks of slots filled with the posts the project already has, finished posts first. Audit before the first of them goes out, since a published post is no longer read.
One thing to keep in mind: a topic placed on a slot is not always written yet. It gets written once its questions are answered, or 24 hours before its slot if they are still open. With Human in the loop switched on, it waits for the answers. Until a topic has been written, the audit has nothing to read for it.
After you import posts
Imported posts are a common source of drift. If you imported a post as is, no agent has touched it. It is exactly what you pasted in, and it may never have been checked against your website profile. An audit is a quick way to see whether it fits with everything else.
When unpublished posts have piled up
A project holds at most 20 posts that are not out yet, suggestions included. If a lot of finished posts have built up without going out, audit them before you start publishing. The more posts in the pile, the more chances for two of them to disagree.
A simple routine
If you want one habit to take away, make it this:
- Change the profile, or line up the next batch of posts.
- Run an audit.
- Check the Audit tab until nothing is outstanding.
- Read the rewritten posts and tweak anything that needs it.
- Let the batch go out.
It takes a few minutes, it spends no credits, and your readers get posts that agree with each other and with you.