Public run log
Bing visibility agent run log
Every run this agent has on record, newest first. Open a record to read the steps, where the record comes from, and what happened when something needed a person.
docs/AEO/Growth Plan/_workspace/bing/), as of Oct 10, 2026. A readout that stopped before its summary leaves no folder, so it would show as a missing week, not as a record. IndexNow pushes between readouts are steps of the readout that followed them. The numbers below are counted from the records shown.Oct 10, 202610:17Week of Oct 10 · Bing readout208 pages indexed (191 last week; the sitemap has 176), 101 impressions and two clicks in 28 days (96 and one), 109 Copilot citations in 28 days (124), 0 category queries. Both IndexNow pushes answered 200.SucceededSummary writtenNo one needed for this run
Steps
- DonePulled the API: nine reports for https://claw-world.app/, none skipped
- DoneExported the three AI Performance CSVs and the two Recommendations lists through the signed-in Chrome
- DoneNormalised and summarised beside the Oct 6 snapshot: three numbers inside the noise band, category queries still 0
- DoneIndexNow: 5 URLs the Oct 9 deploy changed, then 61 more (20 retired pages now answering 410, 30 pages Bing had read with an old description, the marketing pages)
- DoneRead the Oct 6 Site Scan: 127 posts with a title past 65 characters and 152 with two h1 tags, both from the post template
- DoneBing line written into the week’s report
How it was handled
No stop in this run: the API answered, the browser was signed in, both IndexNow pushes answered 200. The week’s IndexNow count was zero because the Oct 4 and Oct 9 deploys had gone out without a push; the push is now part of the deploy script.
Next step
The Oct 17 readout checks whether Bing refetched /learn (last fetched Aug 17) and /pricing (Sep 9) after the push, and reads the new Site Scan to see whether the 127 and 152 came down after the template fix.
Where this record comes from
docs/AEO/Growth Plan/_workspace/bing/2026-10-10/summary.md · commit 7dca4584
Oct 6, 202601:06Week of Oct 6 · Bing readout191 pages indexed (the sitemap had 174), 96 impressions and one click in 28 days, 124 Copilot citations in 28 days, 0 category queries. First readout, nothing to compare to.SucceededSummary writtenA person stepped in
Steps
- DonePulled the API: nine reports for https://claw-world.app/, none skipped
- Waiting on a personFirst browser export stopped: the Chrome profile was not signed in to Bing Webmaster Tools. A person signed in; the rerun exported all three CSVs
- DoneNormalised and summarised; no previous snapshot to set beside it
- DoneExported the Recommendations lists and started the first Site Scan (177 pages)
- DoneBing line written into the week’s report
What went wrong
The AI Performance export needs a browser signed in to Bing Webmaster Tools, and on the first run it was not. The script stopped and said so instead of guessing.
How it was handled
A person signed in once in that Chrome profile and reran the export. The session persists in the profile; the Oct 10 run did not stop there.
Next step
Read the Site Scan when it completes, and push changed pages to IndexNow after each deploy: this readout found no push on record.
Where this record comes from
docs/AEO/Growth Plan/_workspace/bing/2026-10-06/summary.md · commit f7a749a4
No runs match these filters
There are no runs of the Bing visibility agent with that status in that date range. Try a wider range or another status.
The task finished. The record says which: a post published, or a draft written.
The run stopped. The record says where, why, and what happens next.
The run is waiting on a person: a sign-in, a challenge to solve, or a closing to rewrite.
“Succeeded” means the task in the record finished, and the record says which: a post published, or a draft written. It does not measure reach, leads or revenue. Records never include private messages or personal details of people outside the team. Times are US Eastern, from the commit that wrote the record.