Find the broken links other sites point at you, with proof of impact
The Recommendations page now lists the links from other sites that people followed to a missing page of yours, grouped by referring site with how many arrived and sample referring URLs, straight from your logs; counts are a lower bound, bots are excluded, and a referrer is evidence, not proof.
Other people's links to your site break too: a page moves, a URL is mistyped in an article, an old campaign path is retired. A crawler cannot see those links, because they live on sites it does not crawl, and it cannot tell you whether anyone follows them. Your logs can. Every visitor who follows one arrives at a page that answers 404 or 410, and the request carries the address they came from.
Inbound broken links, a new list on the Recommendations page, gathers exactly those requests and groups them by the site that sent the visitor and the path they asked for, with how many people arrived, how many distinct visitors that was, when the first and last one came, and up to three of the referring URLs so you can look at the linking page yourself. It is ordered by hits, so the link that fails for the most people is at the top. Fix or redirect the path, or ask the referring site to correct its link, then mark the row resolved; it stays hidden unless the same host and path show up again.
Links between your own pages that visitors actually followed to a missing page are listed separately, so you can see which of the crawler's broken-link findings people really trip over.
The numbers are honest about what a log can know. Browsers send the referrer only when the linking page allows it, and many trim or withhold it, so every count is a lower bound and the referring page is known only sometimes. Bot requests are excluded, because they never carry a meaningful referrer. And a referrer is evidence that people arrived from that host, not proof that the page still carries the link; the sample URLs let you check before you contact anyone. Nothing here makes a request to the referring site.
The public API, MCP and CLI carry the same list. See Recommendations help for how to read and act on it.