Knowledge base v2.13.0 · Community edition · data through 2 October 2026
Topic · Working with Google
On Day 1, the advice for getting Google to build something, such as an addition to an API, was to request it publicly and in volume. Day 2 showed the other side: Google often needs to see a markup type adopted on websites before it invests in a feature that uses it, a chicken-and-egg problem that schema.org's usage statistics, published for every type and property since 2026, are meant to help break (said at the event, not in Google's docs). Google also asked site owners to report mistakes in its own systems, such as pages wrongly treated as soft 404s, in its forums. Author’s view: markup for types Google does not use yet is a bet on future features, so check a type's usage bucket on schema.org before investing. Day 3 widened the channels: Google's quality talk invited attendees to share the quality issues they want Google to work on next, and the Search Console team asks for feedback on every new feature through its thumbs up and thumbs down buttons, which it said it takes very seriously; a community speaker publicly asked for query data in the generative AI report. A second recording placed that advice in the Day 1 Q&A, after a question about crawl stats in the Search Console API: Google added that its Search Relations team now talks with the Search Console team about the API more than before, partly because with so many vibe-coded systems around it is very easy to say 'use the Search Console API to do something', and annoying when Search Console has no API for that.
Things in this topic 6
Counts are claims that name the thing. All things
What to do
To get Google to build something, such as an addition to an API, report and request it publicly and in volume.
Speaker not identifiedIn Day 1, 16:35 · Q&AEvidence notes, transcript
An audience member asked whether and when crawl stats will be added to the Search Console API.
From the audienceIn Day 1, 16:35 · Q&AEvidence transcript
Google's Search Relations team talks with the Search Console team about the API more than before, partly because with so many vibe-coded systems around it is very easy to just say 'use the Search Console API to do something', and it is annoying when Search Console has no API for that.
Speaker not identifiedIn Day 1, 16:35 · Q&AEvidence transcript
Mistakes in Google's own systems are a further cause of soft 404s, and Gary Illyes asked site owners to report such mistakes in Google's forums.
“BONUS: Mistakes in Google's systems (that you should notify us about)”
Wording checked against the slide or recording
Speaker Gary IllyesIn Day 2, 11:30 · Understanding what's on a pageEvidence slide photo, transcript
Google often needs to see a markup type adopted on websites before it invests in a feature that uses it, a chicken-and-egg problem that the schema.org usage statistics are meant to help break.
Speaker Ryan LeveringIn Day 2, 13:35 · What is Structured Data and why we need it on the internet.Evidence transcript
Markup for schema.org types that Google does not use yet is a bet on future features; check a type's usage bucket on schema.org before investing, since adoption is what Google says it watches before building a feature.
Author Ibrahim AnjroAnnotates Day 2, 13:35 · What is Structured Data and why we need it on the internet.
Google's quality talk said Google receives a lot of feedback at conferences and online, and invited attendees to share the quality issues they run into or want Google to work on next.
Speaker GoogleIn Day 3, 11:15 · How Google thinks about QualityEvidence transcript
Google's Search Console team asks for feedback on every new feature, through the thumbs up and thumbs down buttons or any other feedback feature in Search Console, and said it takes that feedback very seriously.
Speaker Ariel KroszynskiIn Day 3, 13:55 · Inside Search Console: What’s New & How to Use ItEvidence transcript
Nik Vujic said he hopes Search Console's generative AI report will get query data.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
Google often needs to see a markup type adopted on websites before it invests in a feature that uses it, a chicken-and-egg problem that the schema.org usage statistics are meant to help break.
Nik Vujic said he hopes Search Console's generative AI report will get query data.
Google's launch post for the Generative AI performance reports in Search Console (3 June 2026; rolled out to all sites worldwide by 31 August 2026) lists impressions, pages, countries, devices (Search only) and dates, and no click or query metrics.
Nik Vujic said he hopes Search Console's generative AI report will get query data.
Google called AI reporting in Search Console an evolving space and expects the generative AI report to get richer, with more information in the future.