Automated Builder.io Stale Content Audits
Every Monday, WebRun opens Builder.io, walks your spaces and content models, reads the last updated date on every published entry, ranks the ones untouched longest, logs them in Airtable, and files a dated refresh list in Google Drive for the content team.
How do I find published pages that have gone stale?
Every Monday WebRun opens Builder.io, walks your spaces and models, and lists the published entries nobody has touched in months. It ranks them by how long they have sat untouched, logs each in Airtable, and files the refresh list in Google Drive, so old pages get updated instead of forgotten.
- Long untouched pages surface every Monday
- The refresh list is ranked by days stale, not by guesswork
- Nothing is edited or unpublished without a person
Built for content leads · marketing teams · web teams · SEO managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
builder.ioin a real browser with your saved login - no setup, no API keys. -
1
Builder.io - find long untouched entries
- Open Builder.io and go through each space and content model in turn
- List the entries with published status and read the last updated date on each
- Keep anything older than your staleness threshold. Read only: never edit or unpublish an entry
Done when Every published entry has a last updated date and a stale or fresh verdict.
-
2
Airtable - log the refresh backlog
WebRun opens Airtable to log the refresh backlog. - Append the stale entries to your content backlog base in Airtable
- Record the model, the space, the entry name, and the days since it was last updated
- Update rows that already exist rather than adding a second copy
Done when The Airtable backlog matches this week's stale entries with no duplicates.
-
3
Google Drive - file the ranked list
WebRun opens Google Drive to file the ranked list. - Write a dated refresh list into your content folder in Google Drive
- Rank by days untouched, with the oldest published pages at the top
- Note how the list changed since last week, so progress is visible
Done when This week's ranked refresh list is filed in Google Drive.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it edit or unpublish anything?
No. WebRun only reads entries and their last updated dates. It never edits content, changes publish state, or archives an entry, so nothing on your live site moves.
How stale is stale?
You set the threshold, commonly 90 or 180 days. Anything published and untouched longer than that lands on the list, ranked with the oldest first.
Does it cover every space and model?
Yes by default, and you can narrow it. Point it at specific spaces or models at setup and the audit skips the rest, so a test space never pads the backlog.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.