Google now lists entire team rosters in its AI Overviews
Summary
Google's AI Overview is printing whole NFL rosters on some roster searches. A list page whose entire value is the data it enumerates has nothing left to offer once the overview prints all of it, and the trigger is inconsistent across teams, which suggests the rollout is still moving.
Audit the templates whose value is a complete list, on mobile where the overview runs longest, and export Search Console data for those URLs now, while a before state still exists.
Google is generating an AI Overview that lists an entire NFL roster, player by player, on at least some roster queries. Search Engine Roundtable reported the behavior on October 1, after Glenn Gabe, an SEO consultant who tracks Google’s search changes, posted on X on September 30 that he had searched for the Raiders roster during the team’s Sunday game and got an overview listing the whole team. Gabe wrote that it had never shown up for him before. Barry Schwartz, who runs Search Engine Roundtable, shows the desktop version and describes the mobile version as far longer.
The trigger is not consistent across teams. Gabe’s Raiders search put the overview first, and Schwartz’s own checks on three other teams did not match it:
| Roster query | Where the overview appeared |
|---|---|
| Raiders | First, above everything else |
| New York Jets | Below the official team site |
| New York Giants | Did not appear |
| Green Bay Packers | Did not appear |
A roster page is not like a how-to page, where the overview gives a summary and the page still holds the detail. The roster is the detail. An overview that prints every name has republished the dataset the page exists to publish, and the reader has no reason left to open it. Neither Gabe’s post nor Schwartz’s write-up measures clicks, so the cost is unmeasured, but the templates most exposed are the ones whose whole value is the enumeration.
One check per query proves little in either direction. The same query can return different results from run to run, the same variance that makes AI visibility tools disagree with each other. An absent overview on a single search is not evidence the query never fires one.
What to do
The audit unit is the template, not the individual query. The pages at risk are the ones whose value is a complete list:
- Rosters, squad lists, and lineups
- Schedules, fixtures, and standings
- Cast and credit lists
- Spec tables and product comparison lists
- Directory and member listings
Run the head queries for those templates on mobile, where the overview runs longest, and record four things each time: the query, the device, whether an overview fired, and where it sat relative to your own result. Repeat the set weekly, since the inconsistency across teams suggests the rollout is still moving.
Pull query-level clicks and impressions for those URLs out of Search Console now, while a before state still exists. French sites lost CTR in proportion to their AI Overview exposure when that market got overviews ahead of others, and that kind of comparison only works with baseline data captured first.
There is nothing to change on the page itself yet. No markup or structured data choice keeps a list out of an overview, and trimming the list to withhold data likely costs more than it protects, since completeness is what ranks these pages in the first place.