GitBook Scans Docs for Gaps and Dead Links, Then Has Agent Fix Them
GitBook's Oct. 6 update adds content gap, broken link and style guide checks that its Agent turns into change requests, plus rebuilt analytics.

GitBook added a quality monitoring layer that checks published docs for unanswered questions, dead links and style guide violations, GitBook said in its Oct. 6 changelog. The checks are available on all Ultimate sites and to Enterprise customers. GitBook Agent can act on the findings by opening change requests.
Quality checks live in a new Improve section
GitBook put the checks in a new sidebar section called Improve, next to a rebuilt analytics section called Analyze. Content gaps compares visitor questions, support tickets and forum posts against published pages every day and ranks unanswered questions by severity. The Agent can draft a change request to fill a gap.
Broken links finds URLs that return a 404 and suggests one-click redirects, ranked by how much traffic they lose. GitBook said a finding closes by itself when the redirect goes live or the page is restored.
Style guide checks audit up to three spaces at once against a team’s style guidelines. The Agent produces one change request per space with the fixes.
Analytics split by traffic, agents and AI Assistant
GitBook rebuilt site analytics into separate reports for Traffic, Agents and MCP, and AI Assistant. All three share the same filters and support period comparisons. GitBook said the aim is to “turn recurring support questions into docs before they create more tickets.”
Key takeaways
- Content gaps, broken links and style guide checks now run on Ultimate and Enterprise sites.
- The Agent turns findings into change requests, one per space for style fixes.
- Analytics now has separate Traffic, Agents and MCP, and AI Assistant reports.
The take
We think the useful part is the loop: a finding that closes itself when the fix goes live. A check that knows when it is resolved is worth more than the list it produces.
The risk is in the Agent step. A change request written by an agent still needs a person to read it. A style audit that opens one request per space can pile up faster than a team reviews them.
We’d turn on broken links first. A redirect is easy to judge. Then try content gaps on one space and count how many of the Agent’s drafts reviewers accept before turning on style checks for the rest.


