All articles, and the rewrites the audit asks for

Two views for what happens after an article has gone out.

All articles

Everything the calendar has written, with its keyword and where it got to. Before the calendar has run it says so: once it has, every article appears here.

This is the view to open when you want to know what was published and when, rather than what is planned. Opening a row goes to that article's day page, where the draft, the evidence and the publishing history live.

Rewrites

Suggested rewrites are "Pages you have already published that the site audit has since found a problem with. Each one keeps the finding that justifies it."

This is the loop closing. The calendar writes an article, it gets published, the site audit later reads it as part of your site, and if it finds a problem, that problem comes back here as a specific suggestion to rewrite rather than as an anonymous row in the fix list.

Each entry keeps the measurement behind it, so you can see why it is being suggested rather than taking it on faith. Read the proposed rewrite shows what it would change, and I've applied this clears it once you have.

When rewrites is empty

Two requirements, and the page names them: at least one article published through Rankbench, and a finished site audit.

Until both are true there is nothing to compare. The page says so plainly rather than looking broken, and offers to look for some.

Why this is separate from the fix list

A rewrite is a different kind of work from the rest of the Fixes tab. Everything else there is a change to a page you wrote yourself, at some point, for your own reasons. A rewrite is a change to a page this product wrote, which means it can be rewritten by the same machine rather than by you.

Keeping them apart means the fix list stays a list of things you do, and this stays a list of things you approve.

Where to go next

Publishing and what happens next covers how articles get here. The Fixes tab is where everything else the audit found lives.