Content Audit Prioritizer
Prioritize your pages from a CSV: traffic and freshness build the queue Keep, Update, Rewrite or Retire.
Your inputs are processed in your browser and are not transmitted to our servers. Note: third-party resources (e.g. advertising and analytics from Google/Cloudflare) and an optional PayPal donation link may transfer data when loading or when clicked. Browser extensions or plugins may be able to read content that is visible in the input fields.
The result will appear here …
Content audit: prioritize pages instead of guessing
Enter your pages as a CSV with URL, traffic and date of the last update. A scoring model weights reach and freshness and assigns each page to a queue: keep, update, rewrite or retire. The classification stays manually overridable per row, the model is a proposal, not a verdict.
Export the result as CSV sorted by priority: at the top the pages with the biggest effect per effort. That turns a vague we-should-clean-up-sometime feeling into a concrete work plan for the coming weeks. All data stays local in the browser.
Frequently asked questions
Where do I get the data for the audit?
From your Search Console or analytics export: URL, sessions or clicks and the date of the last content change. Three columns are enough, extras such as notes are optional.
How does the model decide between update and rewrite?
Traffic and freshness together build the priority, the thresholds form the four queues. A page with high traffic and an old date lands at the top of update, weak traffic with stale content tends toward retire. You can change every classification.
What is the sorted CSV good for in the end?
It is your editorial plan for existing pages: highest effect per effort on top, descending below. Attach the list to your project management and work through it row by row.