A content audit
that ends with a decision on every page.

Storyflow is built for exactly this job: the inventory in tables, the decision rule above them, the pages grouped by topic, and a short rewrite brief for every page worth saving, all on one board the writers can open from a link. Its AI reads your export and the pages you point it at. Finding every URL and pulling rankings still takes a crawler such as Screaming Frog or a suite such as Semrush or Ahrefs.

Eight columns: title and link, type, topic, date published or updated, visits in the last twelve months, conversions, the decision, and the owner. Above the table, the written rule for keep, fix, merge and cut. Below it in Storyflow, a short brief for each fix. More columns rarely change a decision.

Write the rule first. A common one: cut a page with under 50 visits in twelve months, no conversions and no links to it; fix one whose visits fell by over a third but still converts; merge two that answer the same question; keep the rest. On Storyflow's board the rule sits above the table, so it decides the clear rows.

It can do the slow parts. Storyflow's AI reads the CSV or Excel export you attach and lays it out as tables, reads any page you give it a link to and says what looks dated or which page overlaps it, and drafts a brief for each fix. It does not crawl your site or decide for you; you set the rule and make the final call.

About two minutes a row once the inventory is built. A blog of 140 posts takes under five hours of deciding, plus an hour to export and set up. On a Storyflow board the AI builds the tables from the export, so most of the time goes on the decisions rather than on copying data.

Once a year for most teams, or every six months if you publish more than four pieces a week. Keep each year's Storyflow board. The second audit is faster because most rows are already decided, and it shows whether last year's fixes actually moved visits and sign-ups. A light check every quarter on the twenty pages that bring in the most sign-ups catches the worst decay in between.

Redirect each one to the closest live page that answers a similar question, and note the target in the row. Never delete a page that still has links pointing to it without a redirect. On Storyflow's board the cut rows keep their redirect target, so whoever updates the site has the full list in one place.

No. Storyflow does not crawl a site, find every URL by itself, or pull rankings and traffic automatically. Export the page list and numbers from your analytics, Search Console, Screaming Frog, Semrush or Ahrefs, and attach the file. Storyflow's AI reads it, and can read any single page you give it a link to.

As big as you need. When the AI builds the inventory, each table holds up to fifty rows and eight columns, so a large site splits into one table per topic or content type. That split is useful on its own: it shows on Storyflow's board where one topic has twenty thin pages and another has none.

An inventory is the list: every page with its basic facts. An audit adds a judgement on each one and a plan to act on it. The inventory is the first table on a Storyflow audit board; the decision column, the rule and the rewrite briefs are what turn it into an audit. Many teams build the inventory and stop, which is why the same thin pages are still live a year later.

One person who owns the decisions, one who knows the analytics, and the writers who will do the fixes. Keep the deciding group small. Share the Storyflow board with everyone else by a view-only link; they read it with no account and sign in to comment on a row they disagree with.

No. Storyflow runs in the browser and there are no native mobile or desktop apps. Open the audit board in any browser, and share it with writers and leadership by link. Exports from your analytics or SEO tool are attached in the same browser tab, so there is nothing else to set up.