Turn failed doc searches into next week's writing backlog
Every Monday, WebRun signs in to Archbee, reads the reader analytics for each document space, pulls the search queries that returned nothing useful, groups them into topics, ranks them by how many people searched, records the list in Google Sheets, and posts the top gaps to Microsoft Teams as the week's writing backlog.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find out what my documentation is missing?
WebRun signs in to Archbee every Monday, reads reader analytics for each document space, and pulls the search queries that returned nothing useful over the past week. It groups and ranks them in Google Sheets and posts the top gaps to Microsoft Teams, so writing effort goes where readers are already looking.
- The docs backlog is built from real reader searches, not guesswork
- Missing topics are separated from topics that just need better titles
- A gap that persists week after week is visible instead of forgotten
Built for technical writers · developer relations · product teams · support leads
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
app.archbee.comin a real browser with your saved login - no setup, no API keys. -
1
Archbee - read searches that found nothing
archbee.com
WebRun opens Archbee to read searches that found nothing. - Sign in and open the reader analytics for each document space
- Pull the search queries from the last 7 days
- Keep the ones that returned no result or led to no document being opened
- Note which space each search came from and how many times it was run
Done when Every failing search from the week is captured with its space and count.
-
2
Google Sheets - rank the topic gaps
google.com How to Automate Google Sheets
WebRun opens Google Sheets to rank the topic gaps. - Group similar queries into a single topic so wording differences do not split the count
- Rank topics by total searches, most searched first
- Check the changelog and mark topics where a doc exists but was not found
- Carry the ranking week to week so a persistent gap stands out
Done when The gap list is grouped, ranked, and compared with last week.
-
3
Microsoft Teams - post the writing backlog
microsoft.com How to Automate Microsoft Teams
WebRun opens Microsoft Teams to post the writing backlog. - Post the top gaps to the docs channel with search counts
- Separate missing topics from topics that exist but are hard to find
- Name the space each gap belongs to so the writer knows where it goes
- Suggest only. WebRun never creates, edits, or publishes a document
Done when The docs team starts the week with a ranked backlog.
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 write or publish documents on its own?
No. WebRun reads reader analytics and produces a backlog. It never creates a document, edits existing content, or publishes anything in Archbee. Writing stays with your team.
How does it group similar searches?
By topic rather than exact wording, so different phrasings of the same question count together. Each grouped topic carries the total number of searches behind it.
Can it tell a missing doc from a hard to find one?
Yes. Searches that returned nothing are listed as missing topics. Searches that returned results nobody opened are listed separately, since those need better titles, not new pages.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.