{ "version": "v2.13.0", "data_through": "2026-10-02", "about": "Where what was said or shown at the event differs from Google's documentation, and what to follow: the rows (hand-written in 25-kits/differences.yaml, every claim checked by the build), then the claims linked by contradicts or updates and the claims whose text says they are uncertain (both added by the build). Cite the claim ids; follow is the author's guidance.", "rule": "Where the event and Google's documentation differ, follow the documentation and say that they differ (for example canonicals on paginated pages, max-snippet:-1, 'Discovered – currently not indexed', SpamBrain's launch year, PageRank's role in ranking, Google's 2023 testing figures, the source year of the 40 billion spam pages figure).", "rows": [ { "id": "DIF-01", "title": "How many crawlers Google runs", "follow": "Follow Google's Inside Googlebot post: dozens of other clients share Googlebot's crawling infrastructure and only the larger crawlers are documented. A Google user agent missing from the public lists is not proof of a fake request; verify with reverse DNS or Google's published IP ranges.", "event": [ { "id": "D1-C324", "day": 1, "session_id": "D1-S05", "session": "How crawling works", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Google runs probably hundreds, if not thousands, of crawlers on its crawler infrastructure; some of them are named and some are not.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": "Gary Illyes", "sources": [], "by": "Google", "cite": "[D1-C324, stage, Gary Illyes, Day 1]" } ], "docs": [ { "id": "D1-C342", "day": 1, "session_id": "D1-S05", "session": "How crawling works", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's Inside Googlebot post (March 2026) says Googlebot is today just one user of a centralized crawling platform, and that dozens of other clients, such as Google Shopping and AdSense, send their crawl requests through the same infrastructure under other crawler names, with only the larger ones documented.", "quote": "Googlebot is just a user of something that resembles a centralized crawling platform", "quote_checked": false, "credit": "Search Central blog (31 March 2026)", "speaker": null, "sources": [ { "key": "inside-googlebot-blog", "title": "Inside Googlebot: demystifying crawling, fetching, and the bytes we process", "url": "https://developers.google.com/search/blog/2026/03/crawler-blog-post", "publisher": "Search Central blog (31 March 2026)", "kind": "google", "checked": "2026-10-03" } ], "by": "Search Central blog (31 March 2026)", "cite": "[D1-C342, docs, Search Central blog (31 March 2026), https://developers.google.com/search/blog/2026/03/crawler-blog-post]" }, { "id": "D1-C138", "day": 1, "session_id": "D1-S06", "session": "How crawling errors affect Search", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's page on verifying its crawlers says Googlebot and Google's other common crawlers resolve to crawl-*.googlebot.com or geo-crawl-*.geo.googlebot.com host names, special-case crawlers to rate-limited-proxy-*.google.com and user-triggered fetchers to *.gae.googleusercontent.com or google-proxy-*.google.com, and it publishes each group's IP ranges as JSON files such as common-crawlers.json and special-crawlers.json.", "quote": "", "quote_checked": false, "credit": "Google", "speaker": null, "sources": [ { "key": "verify-google-requests", "title": "Verify requests from Google crawlers and fetchers", "url": "https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requests", "publisher": "Google", "kind": "google", "checked": "2026-10-02" } ], "by": "Google", "cite": "[D1-C138, docs, Google, https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requests]" } ], "pages": [ { "key": "inside-googlebot-blog", "title": "Inside Googlebot: demystifying crawling, fetching, and the bytes we process", "url": "https://developers.google.com/search/blog/2026/03/crawler-blog-post", "publisher": "Search Central blog (31 March 2026)", "checked": "2026-10-03" }, { "key": "verify-google-requests", "title": "Verify requests from Google crawlers and fetchers", "url": "https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requests", "publisher": "Google", "checked": "2026-10-02" } ], "analysis": [ { "id": "D1-C344", "day": 1, "session_id": "D1-S05", "session": "How crawling works", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "On stage Google spoke of probably hundreds, if not thousands, of crawlers, while its Inside Googlebot post speaks of dozens of other clients; both agree that only the larger crawlers are documented, so a Google user agent missing from the public lists is not proof of a fake request, and reverse DNS or Google's published IP ranges are the test.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D1-C344, analysis, Ibrahim Anjro]" } ], "topics": [ "ai-crawlers-and-agents", "crawl-pipeline", "crawl-errors" ], "entities": [ { "id": "googlebot", "name": "Googlebot", "count": 3 }, { "id": "google-shopping", "name": "Google Shopping", "count": 1 }, { "id": "special-case-crawlers", "name": "Special-case crawlers", "count": 1 }, { "id": "user-triggered-fetchers", "name": "User-triggered fetchers", "count": 1 } ] }, { "id": "DIF-02", "title": "4xx responses, 429 and crawl budget", "follow": "Follow Google's HTTP status code documentation: 4xx codes other than 429 do not slow crawling, while 429 slows it like a 5xx error. A 404 is still a fetch. Return 429 or 503 only for temporary overload; Google's crawl rate guide warns against doing so for longer than 1-2 days.", "event": [ { "id": "D1-C385", "day": 1, "session_id": "D1-S10", "session": "How Google thinks about crawl budget", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "4xx responses do not affect a site's crawl budget, because Google expects pages, content and products to come and go as a natural part of the web.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": null, "sources": [ { "key": "http-network-errors", "title": "How HTTP status codes affect Google's crawlers", "url": "https://developers.google.com/crawling/docs/troubleshooting/http-status-codes", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "Google", "cite": "[D1-C385, stage, Google, Day 1]" } ], "docs": [ { "id": "D1-C072", "day": 1, "session_id": "D1-S06", "session": "How crawling errors affect Search", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "4xx status codes other than 429 have no effect on crawl rate.", "quote": "The 4xx status codes, except 429, have no effect on crawl rate.", "quote_checked": false, "credit": "Google", "speaker": null, "sources": [ { "key": "http-network-errors", "title": "How HTTP status codes affect Google's crawlers", "url": "https://developers.google.com/crawling/docs/troubleshooting/http-status-codes", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "Google", "cite": "[D1-C072, docs, Google, https://developers.google.com/crawling/docs/troubleshooting/http-status-codes]" }, { "id": "D1-C071", "day": 1, "session_id": "D1-S06", "session": "How crawling errors affect Search", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "5xx and 429 responses prompt Google's crawlers to slow down temporarily. Already indexed URLs are preserved in the index for a while but eventually dropped.", "quote": "already indexed URLs are preserved in the index, but eventually dropped", "quote_checked": false, "credit": "Google", "speaker": null, "sources": [ { "key": "http-network-errors", "title": "How HTTP status codes affect Google's crawlers", "url": "https://developers.google.com/crawling/docs/troubleshooting/http-status-codes", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "Google", "cite": "[D1-C071, docs, Google, https://developers.google.com/crawling/docs/troubleshooting/http-status-codes]" }, { "id": "D3-C668", "day": 3, "session_id": "D3-S17", "session": "How long does it take to..?", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's crawl rate guide says that when a significant number of URLs return 500, 503 or 429, Google reduces the site's crawl rate, which starts increasing again automatically once the errors drop; it warns against doing this for longer than 1-2 days.", "quote": "", "quote_checked": false, "credit": "Google", "speaker": null, "sources": [ { "key": "reduce-crawl-rate", "title": "Reduce the Google crawl rate", "url": "https://developers.google.com/crawling/docs/crawlers-fetchers/reduce-crawl-rate", "publisher": "Google", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D3-C668, docs, Google, https://developers.google.com/crawling/docs/crawlers-fetchers/reduce-crawl-rate]" } ], "pages": [ { "key": "http-network-errors", "title": "How HTTP status codes affect Google's crawlers", "url": "https://developers.google.com/crawling/docs/troubleshooting/http-status-codes", "publisher": "Google", "checked": "2026-10-04" }, { "key": "reduce-crawl-rate", "title": "Reduce the Google crawl rate", "url": "https://developers.google.com/crawling/docs/crawlers-fetchers/reduce-crawl-rate", "publisher": "Google", "checked": "2026-10-03" } ], "analysis": [ { "id": "D1-C386", "day": 1, "session_id": "D1-S10", "session": "How Google thinks about crawl budget", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "The stage point that 4xx responses do not affect crawl budget matches Google's documentation that 4xx codes have no effect on crawl rate (D1-C072), with one exception: 429 Too Many Requests counts as a server error and slows crawling like a 5xx (D1-C071, D1-C092).", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D1-C386, analysis, Ibrahim Anjro]" }, { "id": "D1-C419", "day": 1, "session_id": "D1-S10", "session": "How Google thinks about crawl budget", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "A 404 fetch is still a fetch: Google's 2017 crawl budget post says generally any URL Googlebot crawls counts towards a site's crawl budget, so the stage point that 4xx responses do not affect crawl budget is best read as 'they do not slow crawling, and a 404 tells Google to crawl that URL less over time'.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "crawl-budget-blog", "title": "What Crawl Budget Means for Googlebot", "url": "https://developers.google.com/search/blog/2017/01/what-crawl-budget-means-for-googlebot", "publisher": "Search Central blog (16 January 2017)", "kind": "google", "checked": "2026-10-03" }, { "key": "http-network-errors", "title": "How HTTP status codes affect Google's crawlers", "url": "https://developers.google.com/crawling/docs/troubleshooting/http-status-codes", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "the author", "cite": "[D1-C419, analysis, Ibrahim Anjro]" } ], "topics": [ "crawl-errors", "crawl-rate-limit", "crawl-budget" ], "entities": [ { "id": "http-429", "name": "429", "count": 4 }, { "id": "http-4xx", "name": "4xx", "count": 4 }, { "id": "crawl-budget-metric", "name": "Crawl budget", "count": 3 }, { "id": "http-5xx", "name": "5xx", "count": 2 }, { "id": "googlebot", "name": "Googlebot", "count": 1 }, { "id": "http-404", "name": "404", "count": 1 }, { "id": "http-503", "name": "503", "count": 1 } ] }, { "id": "DIF-03", "title": "Whether a robots.txt block frees crawl budget for other pages", "follow": "Follow Google's crawl budget guide: use robots.txt only for sections you never want crawled, never to reallocate crawl budget for a while. Freed budget goes to other pages only when Google is already at the site's crawl capacity limit, so do not expect a block to speed up crawling elsewhere on a site that is not.", "event": [ { "id": "D1-C469", "day": 1, "session_id": "D1-S12", "session": "Q&A", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Gary Illyes said disallowing a section that should not be crawled, such as /ads, in a Googlebot group in robots.txt shifts crawl budget to the rest of the site.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": "Gary Illyes", "sources": [ { "key": "crawl-budget-guide", "title": "Optimize your crawl budget", "url": "https://developers.google.com/crawling/docs/crawl-budget", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "Google", "cite": "[D1-C469, stage, Gary Illyes, Day 1]" } ], "docs": [ { "id": "D1-C109", "day": 1, "session_id": "D1-S10", "session": "How Google thinks about crawl budget", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google advises against using noindex to save crawl budget and against using robots.txt to temporarily reallocate budget. Use robots.txt only for pages you never want crawled, and 404 or 410 for removed pages.", "quote": "", "quote_checked": false, "credit": "Google", "speaker": null, "sources": [ { "key": "crawl-budget-guide", "title": "Optimize your crawl budget", "url": "https://developers.google.com/crawling/docs/crawl-budget", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "Google", "cite": "[D1-C109, docs, Google, https://developers.google.com/crawling/docs/crawl-budget]" } ], "pages": [ { "key": "crawl-budget-guide", "title": "Optimize your crawl budget", "url": "https://developers.google.com/crawling/docs/crawl-budget", "publisher": "Google", "checked": "2026-10-04" } ], "analysis": [ { "id": "D1-C470", "day": 1, "session_id": "D1-S12", "session": "Q&A", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "Google's crawl budget guide says crawl budget freed by robots.txt blocks is not shifted to other pages unless the site already hits its crawl capacity limit, and advises against robots.txt for temporary reallocation; so block only sections you never want crawled, and expect a shift only on capacity-limited sites.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "crawl-budget-guide", "title": "Optimize your crawl budget", "url": "https://developers.google.com/crawling/docs/crawl-budget", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "the author", "cite": "[D1-C470, analysis, Ibrahim Anjro]" } ], "topics": [ "crawl-directives", "crawl-budget", "robots-txt" ], "entities": [ { "id": "crawl-budget-metric", "name": "Crawl budget", "count": 3 }, { "id": "robots-txt-file", "name": "robots.txt", "count": 3 }, { "id": "crawl-capacity-limit", "name": "Crawl capacity limit", "count": 1 }, { "id": "googlebot", "name": "Googlebot", "count": 1 }, { "id": "http-404", "name": "404", "count": 1 }, { "id": "http-410", "name": "410", "count": 1 }, { "id": "noindex", "name": "noindex", "count": 1 } ] }, { "id": "DIF-04", "title": "A misspelt rule name in robots.txt", "follow": "Google's documentation is silent here: its robots.txt specification does not mention typos, so spell rule names correctly. On stage a misspelt rule name was said to make Google ignore the line, but Google's open-source parser accepts common misspellings of disallow and user-agent (not of allow) and other crawlers may be stricter: rely on neither.", "event": [ { "id": "D1-C525", "day": 1, "session_id": "D1-S07", "session": "How Google interprets robots.txt", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Google called robots.txt extremely forgiving: a typo in a path only blocks the wrong path, a typo in a rule name such as disallow makes Google ignore that line, and the rest of the file is still used.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": null, "sources": [], "by": "Google", "cite": "[D1-C525, stage, Google, Day 1]" } ], "docs": [], "pages": [ { "key": "robots-spec", "title": "How Google interprets the robots.txt specification", "url": "https://developers.google.com/crawling/docs/robots-txt/robots-txt-spec", "publisher": "Google", "checked": "2026-10-04" }, { "key": "robotstxt-parser", "title": "google/robotstxt", "url": "https://github.com/google/robotstxt", "publisher": "Google (open-source robots.txt parser and matcher library, GitHub)", "checked": "2026-10-04" } ], "analysis": [ { "id": "D1-C532", "day": 1, "session_id": "D1-S07", "session": "How Google interprets robots.txt", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "A typo in a rule name is not always ignored by Google: its open-source robots.txt parser deliberately accepts common misspellings of disallow (such as dissallow, dissalow and disalow) and of user-agent (useragent, user agent), but not of allow. Google's spec page does not mention typos, and other crawlers may be stricter, so spell rule names correctly.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "robotstxt-parser", "title": "google/robotstxt", "url": "https://github.com/google/robotstxt", "publisher": "Google (open-source robots.txt parser and matcher library, GitHub)", "kind": "google", "checked": "2026-10-04" }, { "key": "robots-spec", "title": "How Google interprets the robots.txt specification", "url": "https://developers.google.com/crawling/docs/robots-txt/robots-txt-spec", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "the author", "cite": "[D1-C532, analysis, Ibrahim Anjro]" } ], "topics": [ "robots-txt" ], "entities": [ { "id": "disallow", "name": "Disallow", "count": 2 }, { "id": "robots-txt-file", "name": "robots.txt", "count": 2 }, { "id": "allow", "name": "Allow", "count": 1 } ] }, { "id": "DIF-05", "title": "Why a URL is 'Discovered – currently not indexed'", "follow": "Follow the Page indexing report help first: rule out server overload (slow responses, 5xx errors, a falling crawl rate in the Crawl Stats report). Then treat the status as a demand problem and raise the quality of the pages already indexed; resubmitting the URLs does not change why they wait.", "event": [ { "id": "D2-C706", "day": 2, "session_id": "D2-S20", "session": "Deciding what goes in the index?", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "'Discovered – currently not indexed' in Search Console is a crawl-scheduling state: Google knows the URL exists but does not want to crawl it yet. Of the two not-indexed statuses discussed, it was called the 'kind of nastier' one.", "quote": "The first one is kind of nastier.", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [], "by": "Google", "cite": "[D2-C706, stage, Google, Day 2]" } ], "docs": [ { "id": "D2-C707", "day": 2, "session_id": "D2-S20", "session": "Deciding what goes in the index?", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's Page indexing report help says a 'Discovered – currently not indexed' page was found but not crawled yet, typically because Google wanted to crawl it but expected the crawl to overload the site, so it rescheduled the crawl.", "quote": "", "quote_checked": false, "credit": "Google Search Console Help", "speaker": null, "sources": [ { "key": "page-indexing-help", "title": "Page indexing report", "url": "https://support.google.com/webmasters/answer/7440203?hl=en", "publisher": "Google Search Console Help", "kind": "google", "checked": "2026-10-04" } ], "by": "Google Search Console Help", "cite": "[D2-C707, docs, Google Search Console Help, https://support.google.com/webmasters/answer/7440203?hl=en]" } ], "pages": [ { "key": "page-indexing-help", "title": "Page indexing report", "url": "https://support.google.com/webmasters/answer/7440203?hl=en", "publisher": "Google Search Console Help", "checked": "2026-10-04" } ], "analysis": [ { "id": "D2-C708", "day": 2, "session_id": "D2-S20", "session": "Deciding what goes in the index?", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "The help page explains 'Discovered – currently not indexed' by expected server overload (capacity), while on stage it was explained as Google not wanting the URL yet (demand); the crawl budget guide covers both, so first rule out slow responses and server errors, then treat the status as a quality and demand problem.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "crawl-budget-guide", "title": "Optimize your crawl budget", "url": "https://developers.google.com/crawling/docs/crawl-budget", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "the author", "cite": "[D2-C708, analysis, Ibrahim Anjro]" }, { "id": "D2-C710", "day": 2, "session_id": "D2-S20", "session": "Deciding what goes in the index?", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "Repeatedly submitting 'Discovered – currently not indexed' URLs does not change why they wait, because the status reflects a crawl-scheduling decision; raise the site's demonstrated quality instead, for example by improving or removing weak pages that are already indexed.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D2-C710, analysis, Ibrahim Anjro]" } ], "topics": [ "page-indexing-report", "crawl-budget", "crawl-demand" ], "entities": [ { "id": "crawl-budget-metric", "name": "Crawl budget", "count": 1 }, { "id": "google-search-console", "name": "Search Console", "count": 1 }, { "id": "http-5xx", "name": "5xx", "count": 1 }, { "id": "page-indexing", "name": "Page indexing report", "count": 1 } ] }, { "id": "DIF-06", "title": "Links Google cannot extract", "follow": "Follow Google's link best practices: only an a element with an href is a dependable link. The documentation says Google may still try to parse routerLink, href on a span, onclick-only links and javascript: URLs, where the slide said it cannot; either way, do not rely on them for discovery.", "event": [ { "id": "D2-C041", "day": 2, "session_id": "D2-S03", "session": "How is HTML interpreted", "label": "slide", "label_meaning": "shown on screen", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Google cannot extract a link from an href attribute placed on an element other than a, such as a span, because that is not a standard way to make a link.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [ { "key": "links-crawlable", "title": "Link best practices for Google", "url": "https://developers.google.com/search/docs/crawling-indexing/links-crawlable", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-02" } ], "by": "Google", "cite": "[D2-C041, slide, Google, Day 2]" }, { "id": "D2-C042", "day": 2, "session_id": "D2-S03", "session": "How is HTML interpreted", "label": "slide", "label_meaning": "shown on screen", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "A Google slide also listed as not extractable an a element with a routerLink attribute instead of an href, and javascript: URLs such as javascript:goTo('products') or javascript:window.location.href='/products'.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [ { "key": "links-crawlable", "title": "Link best practices for Google", "url": "https://developers.google.com/search/docs/crawling-indexing/links-crawlable", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-02" } ], "by": "Google", "cite": "[D2-C042, slide, Google, Day 2]" } ], "docs": [ { "id": "D2-C043", "day": 2, "session_id": "D2-S03", "session": "How is HTML interpreted", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's link best practices say Google can generally crawl a link only if it is an a element with an href attribute, and list routerLink without href, href on a span, onclick-only a elements and javascript: URLs as not recommended, while noting that Google may still attempt to parse them.", "quote": "", "quote_checked": false, "credit": "Google Search Central", "speaker": null, "sources": [ { "key": "links-crawlable", "title": "Link best practices for Google", "url": "https://developers.google.com/search/docs/crawling-indexing/links-crawlable", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-02" } ], "by": "Google Search Central", "cite": "[D2-C043, docs, Google Search Central, https://developers.google.com/search/docs/crawling-indexing/links-crawlable]" } ], "pages": [ { "key": "links-crawlable", "title": "Link best practices for Google", "url": "https://developers.google.com/search/docs/crawling-indexing/links-crawlable", "publisher": "Google Search Central", "checked": "2026-10-02" } ], "analysis": [ { "id": "D2-C044", "day": 2, "session_id": "D2-S03", "session": "How is HTML interpreted", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "Google's link-extraction slide put routerLink, href on a span, onclick-only links and javascript: URLs under 'can not extract', which is stricter than Google's link documentation saying Google may still try to parse them; either way they are not dependable links for discovery.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D2-C044, analysis, Ibrahim Anjro]" } ], "topics": [ "crawlable-links", "javascript-seo" ], "entities": [] }, { "id": "DIF-07", "title": "A noindex page and its JavaScript", "follow": "Follow the JavaScript SEO basics guide, which says only that Google may skip rendering a page served with noindex. The practical rule is the same either way: never serve a noindex that JavaScript is expected to remove.", "event": [ { "id": "D2-C852", "day": 2, "session_id": "D2-S04", "session": "Controlling indexing", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "When Google finds a noindex rule in a page's HTML, it drops the page without even processing its JavaScript, so a script cannot switch the page back to indexable, John Mueller said.", "quote": "we will see the noindex and say, oh, we will get rid of this page; we won't even process the JavaScript", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "John Mueller", "sources": [ { "key": "javascript-seo-basics", "title": "Understand the JavaScript SEO basics", "url": "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C852, stage, John Mueller, Day 2]" }, { "id": "D2-C108", "day": 2, "session_id": "D2-S04", "session": "Controlling indexing", "label": "slide", "label_meaning": "shown on screen", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Removing a robots restriction such as noindex with JavaScript does not work, a slide said.", "quote": "But... it takes more time, and removing restrictions (like \"noindex\") doesn't work.", "quote_checked": true, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "John Mueller", "sources": [ { "key": "javascript-seo-basics", "title": "Understand the JavaScript SEO basics", "url": "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C108, slide, John Mueller, Day 2]" } ], "docs": [ { "id": "D2-C854", "day": 2, "session_id": "D2-S04", "session": "Controlling indexing", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's JavaScript SEO basics guide says that when Google encounters a noindex rule it may skip rendering and JavaScript execution, so using JavaScript to change or remove a noindex robots meta tag may not work as expected.", "quote": "it may skip rendering and JavaScript execution", "quote_checked": false, "credit": "Google Search Central", "speaker": null, "sources": [ { "key": "javascript-seo-basics", "title": "Understand the JavaScript SEO basics", "url": "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search Central", "cite": "[D2-C854, docs, Google Search Central, https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics]" } ], "pages": [ { "key": "javascript-seo-basics", "title": "Understand the JavaScript SEO basics", "url": "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics", "publisher": "Google Search Central", "checked": "2026-10-03" } ], "analysis": [ { "id": "D2-C855", "day": 2, "session_id": "D2-S04", "session": "Controlling indexing", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "On stage the rule was absolute (Google won't even process the JavaScript of a page served with noindex), while Google's guide says only that it may skip rendering; either way, a noindex in the served HTML must never be one that JavaScript is expected to lift.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D2-C855, analysis, Ibrahim Anjro]" } ], "topics": [ "robots-meta-tag", "javascript-seo", "rendering" ], "entities": [ { "id": "javascript", "name": "JavaScript", "count": 4 }, { "id": "noindex", "name": "noindex", "count": 4 }, { "id": "rendering-concept", "name": "Rendering", "count": 2 }, { "id": "meta-robots-tag", "name": "Robots meta tag", "count": 1 } ] }, { "id": "DIF-08", "title": "Whether every page gets rendered", "follow": "Follow the JavaScript SEO basics guide: every page with a 200 status is queued for rendering unless a robots rule blocks indexing. Queued is not the same as rendered, so put the content, links and meta tags that indexing needs in the HTML the server sends.", "event": [ { "id": "D2-C130", "day": 2, "session_id": "D2-S05", "session": "Lightning session D: Rendering and JavaScript", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Google said its pipeline needs to ensure that content indexable without JavaScript can pass through without rendering, while content that appears only through JavaScript and CSS takes a longer rendering pass.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "Erin Sparling", "sources": [], "by": "Google", "cite": "[D2-C130, stage, Erin Sparling, Day 2]" }, { "id": "D3-C628", "day": 3, "session_id": "D3-S17", "session": "How long does it take to..?", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Gary Illyes said Google keeps saying it renders every URL on the internet and that he would say this is not true, though it is what he was told; he went on to say that Google's logs show the rendering queue cleared within weeks.", "quote": "we keep saying that we render every single URL on the internet. I would say that that's not true", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": "Gary Illyes", "sources": [], "by": "Google", "cite": "[D3-C628, stage, Gary Illyes, Day 3]" } ], "docs": [ { "id": "D2-C131", "day": 2, "session_id": "D2-S05", "session": "Lightning session D: Rendering and JavaScript", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's JavaScript SEO guide says Googlebot sends every page with a 200 HTTP status code to the rendering queue, whether or not it contains JavaScript, unless a robots meta tag or header tells Google not to index it, and Google uses the rendered HTML to index the page.", "quote": "", "quote_checked": false, "credit": "Google Search Central", "speaker": null, "sources": [ { "key": "javascript-seo-basics", "title": "Understand the JavaScript SEO basics", "url": "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search Central", "cite": "[D2-C131, docs, Google Search Central, https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics]" } ], "pages": [ { "key": "javascript-seo-basics", "title": "Understand the JavaScript SEO basics", "url": "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics", "publisher": "Google Search Central", "checked": "2026-10-03" } ], "analysis": [ { "id": "D2-C132", "day": 2, "session_id": "D2-S05", "session": "Lightning session D: Rendering and JavaScript", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "The stage remark that content indexable without JavaScript can pass through without rendering does not mean such pages skip rendering, because Google's guide queues every 200 page for rendering; read it as: content already in the raw HTML does not depend on the slower rendering pass.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D2-C132, analysis, Ibrahim Anjro]" }, { "id": "D3-C676", "day": 3, "session_id": "D3-S17", "session": "How long does it take to..?", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "The stage doubt that every URL gets rendered sits beside Google's JavaScript guide, which says every page with a 200 status is queued for rendering unless a robots rule blocks indexing: queued is not the same as rendered, so do not rely on rendering for critical content.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "javascript-seo-basics", "title": "Understand the JavaScript SEO basics", "url": "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "the author", "cite": "[D3-C676, analysis, Ibrahim Anjro]" } ], "topics": [ "rendering", "javascript-seo", "indexing-pipeline" ], "entities": [ { "id": "rendering-concept", "name": "Rendering", "count": 5 }, { "id": "javascript", "name": "JavaScript", "count": 4 }, { "id": "http-200", "name": "200", "count": 3 }, { "id": "googlebot", "name": "Googlebot", "count": 1 }, { "id": "meta-robots-tag", "name": "Robots meta tag", "count": 1 } ] }, { "id": "DIF-09", "title": "How strong a signal rel=canonical is", "follow": "Follow Google's canonical guide: redirects and rel=canonical are strong signals, sitemap inclusion is a weak one. Use the strong signals as the main levers, keep sitemaps as support, and point all of them at the same URL.", "event": [ { "id": "D2-C390", "day": 2, "session_id": "D2-S08", "session": "Handling web duplication", "label": "slide", "label_meaning": "shown on screen", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Clear site-owner signals about which URL should be canonical make a big difference to Google's choice; the speaker named redirects, listing only the preferred URL in sitemaps, and rel=canonical, which the speaker said also helps a bit.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [ { "key": "consolidate-duplicate-urls", "title": "How to specify a canonical URL with rel=\"canonical\" and other methods", "url": "https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" }, { "key": "canonicalization", "title": "What is canonicalization", "url": "https://developers.google.com/search/docs/crawling-indexing/canonicalization", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C390, slide, Google, Day 2]" } ], "docs": [ { "id": "D2-C391", "day": 2, "session_id": "D2-S08", "session": "Handling web duplication", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's canonical guide ranks the ways to signal a preferred canonical by strength: redirects and rel=canonical annotations are strong signals, sitemap inclusion is a weak signal, and combining methods makes them more effective.", "quote": "", "quote_checked": false, "credit": "Google Search Central", "speaker": null, "sources": [ { "key": "consolidate-duplicate-urls", "title": "How to specify a canonical URL with rel=\"canonical\" and other methods", "url": "https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search Central", "cite": "[D2-C391, docs, Google Search Central, https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls]" } ], "pages": [ { "key": "consolidate-duplicate-urls", "title": "How to specify a canonical URL with rel=\"canonical\" and other methods", "url": "https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls", "publisher": "Google Search Central", "checked": "2026-10-03" } ], "analysis": [ { "id": "D2-C392", "day": 2, "session_id": "D2-S08", "session": "Handling web duplication", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "Google's duplication talk described rel=canonical as something that 'also helps a bit', while Google's canonical guide calls it a strong signal alongside redirects and calls sitemap inclusion weak; treat redirects and rel=canonical as the main levers and sitemaps as support.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "consolidate-duplicate-urls", "title": "How to specify a canonical URL with rel=\"canonical\" and other methods", "url": "https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "the author", "cite": "[D2-C392, analysis, Ibrahim Anjro]" } ], "topics": [ "sitemaps", "canonical-selection", "site-moves" ], "entities": [ { "id": "canonicalization", "name": "Canonicalization", "count": 3 }, { "id": "redirects", "name": "Redirects", "count": 3 }, { "id": "rel-canonical", "name": "rel=canonical", "count": 3 }, { "id": "sitemap-file", "name": "Sitemaps", "count": 3 } ] }, { "id": "DIF-10", "title": "Canonicals on paginated pages", "follow": "Follow Google's pagination guide: give every page of a series its own URL, a self-referencing canonical and a crawlable link to the next page. Pointing the canonical of later pages at page 1 is a deliberate trade-off, not the default: it folds them into page 1, so the items they list need links from elsewhere.", "event": [ { "id": "D2-C393", "day": 2, "session_id": "D2-S08", "session": "Handling web duplication", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Google's speaker said that pointing rel=canonical from the pages of a paginated set to the first page can sometimes make sense depending on the goal, for example to make a category page more visible, but that it affects canonicalization and deduplication.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [], "by": "Google", "cite": "[D2-C393, stage, Google, Day 2]" } ], "docs": [ { "id": "D1-C115", "day": 1, "session_id": "D1-S00", "session": "Day 1, session not recorded", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's crawlers do not click buttons. Each page in a series needs its own URL and an link to the next page, should not use page 1 as its canonical, and rel=next and rel=prev are no longer used.", "quote": "", "quote_checked": false, "credit": "Google Search Central", "speaker": null, "sources": [ { "key": "pagination-guide", "title": "Pagination, incremental page loading, and their impact on Google Search", "url": "https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search Central", "cite": "[D1-C115, docs, Google Search Central, https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading]" } ], "pages": [ { "key": "pagination-guide", "title": "Pagination, incremental page loading, and their impact on Google Search", "url": "https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading", "publisher": "Google Search Central", "checked": "2026-10-03" } ], "analysis": [ { "id": "D2-C394", "day": 2, "session_id": "D2-S08", "session": "Handling web duplication", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "Google's pagination guide still says not to use page 1 as the canonical of a paginated series, so keep self-referencing canonicals on paginated pages unless you deliberately want later pages folded into page 1 and the items they list are linked from elsewhere.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "pagination-guide", "title": "Pagination, incremental page loading, and their impact on Google Search", "url": "https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "the author", "cite": "[D2-C394, analysis, Ibrahim Anjro]" } ], "topics": [ "pagination", "canonical-selection" ], "entities": [ { "id": "canonicalization", "name": "Canonicalization", "count": 2 }, { "id": "duplicate-content-concept", "name": "Duplicate content", "count": 1 }, { "id": "rel-canonical", "name": "rel=canonical", "count": 1 } ] }, { "id": "DIF-11", "title": "Whether only canonicals are shown in results", "follow": "Follow Google's documentation: a result usually points to the canonical, but another page of the same duplicate cluster can be shown in some contexts, such as a mobile page to a user on a mobile device.", "event": [ { "id": "D2-C701", "day": 2, "session_id": "D2-S20", "session": "Deciding what goes in the index?", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "When Google already has duplicate information for a document, for example when reprocessing it, index selection uses it to drop non-canonical duplicates from further processing, so that, as the speaker put it, only canonicals end up in search results (a simplification; see D2-C703).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [ { "key": "canonicalization", "title": "What is canonicalization", "url": "https://developers.google.com/search/docs/crawling-indexing/canonicalization", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" }, { "key": "page-indexing-help", "title": "Page indexing report", "url": "https://support.google.com/webmasters/answer/7440203?hl=en", "publisher": "Google Search Console Help", "kind": "google", "checked": "2026-10-04" } ], "by": "Google", "cite": "[D2-C701, stage, Google, Day 2]" } ], "docs": [ { "id": "D2-C702", "day": 2, "session_id": "D2-S20", "session": "Deciding what goes in the index?", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's documentation says a search result usually points to the canonical page, but the other pages in a duplicate cluster are alternate versions that may be served in different contexts, for example a mobile page for a user on a mobile device.", "quote": "", "quote_checked": false, "credit": "Google Search Central", "speaker": null, "sources": [ { "key": "canonicalization", "title": "What is canonicalization", "url": "https://developers.google.com/search/docs/crawling-indexing/canonicalization", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" }, { "key": "how-search-works", "title": "In-depth guide to how Google Search works", "url": "https://developers.google.com/search/docs/fundamentals/how-search-works", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search Central", "cite": "[D2-C702, docs, Google Search Central, https://developers.google.com/search/docs/crawling-indexing/canonicalization]" } ], "pages": [ { "key": "canonicalization", "title": "What is canonicalization", "url": "https://developers.google.com/search/docs/crawling-indexing/canonicalization", "publisher": "Google Search Central", "checked": "2026-10-03" }, { "key": "how-search-works", "title": "In-depth guide to how Google Search works", "url": "https://developers.google.com/search/docs/fundamentals/how-search-works", "publisher": "Google Search Central", "checked": "2026-10-03" } ], "analysis": [ { "id": "D2-C703", "day": 2, "session_id": "D2-S20", "session": "Deciding what goes in the index?", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "'Only canonicals end up in search results' as said on stage is a simplification: non-canonical duplicates are dropped from the index, but Google's documentation says an alternate from the same cluster can still be shown in some contexts, such as a mobile version to a mobile user.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D2-C703, analysis, Ibrahim Anjro]" } ], "topics": [ "duplicate-content", "canonical-selection", "index-selection" ], "entities": [ { "id": "canonicalization", "name": "Canonicalization", "count": 1 }, { "id": "duplicate-content-concept", "name": "Duplicate content", "count": 1 }, { "id": "index-selection-concept", "name": "Index selection", "count": 1 } ] }, { "id": "DIF-12", "title": "Videos placed below the fold", "follow": "Follow the Video indexing report help: the video needs a watch page and a player that is there when the page loads, at a size and position Google can determine, with no click-to-play placeholder. The documentation does not say that a video below the fold is never indexed; putting the main video in the first viewport is the safe choice.", "event": [ { "id": "D2-C924", "day": 2, "session_id": "D2-S13", "session": "Using images to your advantage and Engaging Search users with videos", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "For a video to be discovered it must be embedded prominently, above the fold; Gary Illyes said a video placed below the fold is not going to be indexed.", "quote": "If it's not above the fold, then you basically lost the game.", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "Gary Illyes", "sources": [], "by": "Google", "cite": "[D2-C924, stage, Gary Illyes, Day 2]" } ], "docs": [ { "id": "D2-C942", "day": 2, "session_id": "D2-S13", "session": "Using images to your advantage and Engaging Search users with videos", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's Video indexing report help says only videos on a watch page are eligible for indexing, and flags 'Cannot determine video position and size' when the player is not on the page at load, for example behind a click-to-play image, asking for the player to load at its real size and position without user interaction.", "quote": "", "quote_checked": false, "credit": "Google Search Console Help", "speaker": null, "sources": [ { "key": "video-indexing-report", "title": "Video indexing report", "url": "https://support.google.com/webmasters/answer/9495631?hl=en", "publisher": "Google Search Console Help", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search Console Help", "cite": "[D2-C942, docs, Google Search Console Help, https://support.google.com/webmasters/answer/9495631?hl=en]" } ], "pages": [ { "key": "video-indexing-report", "title": "Video indexing report", "url": "https://support.google.com/webmasters/answer/9495631?hl=en", "publisher": "Google Search Console Help", "checked": "2026-10-03" } ], "analysis": [ { "id": "D2-C944", "day": 2, "session_id": "D2-S13", "session": "Using images to your advantage and Engaging Search users with videos", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "Gary Illyes said a video below the fold is not indexed, but Google's video documentation only requires the player to be present at load, at a position and size Google can determine and not hidden behind other elements; to be safe, put the main video of a watch page in the first viewport and load the player without a click-to-play placeholder.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "video-seo", "title": "Video SEO best practices", "url": "https://developers.google.com/search/docs/appearance/video", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" }, { "key": "video-indexing-report", "title": "Video indexing report", "url": "https://support.google.com/webmasters/answer/9495631?hl=en", "publisher": "Google Search Console Help", "kind": "google", "checked": "2026-10-03" } ], "by": "the author", "cite": "[D2-C944, analysis, Ibrahim Anjro]" } ], "topics": [ "video" ], "entities": [] }, { "id": "DIF-13", "title": "What max-snippet:-1 does", "follow": "Follow the robots meta tag specification: max-snippet:-1 removes the length limit and lets Google choose the snippet length it finds most effective. Do not promise longer snippets from it; use it to lift a lower limit that a template, plug-in or CDN sets.", "event": [ { "id": "D2-C085", "day": 2, "session_id": "D2-S04", "session": "Controlling indexing", "label": "slide", "label_meaning": "shown on screen", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "max-snippet:-1 removes the length limit and can produce a longer snippet than having no rule, because by default Google keeps snippets to a length it considers reasonable instead of quoting a page at length.", "quote": "max-snippet:-1 = No limit. (can be more than without)", "quote_checked": true, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "John Mueller", "sources": [], "by": "Google", "cite": "[D2-C085, slide, John Mueller, Day 2]" }, { "id": "D2-C104", "day": 2, "session_id": "D2-S04", "session": "Controlling indexing", "label": "slide", "label_meaning": "shown on screen", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "To be as visible as possible in Google, John Mueller's closing slide recommended the robots rules max-image-preview:large and max-snippet:-1.", "quote": "To be as visible as possible in Google, use: max-image-preview:large, max-snippet:-1", "quote_checked": true, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "John Mueller", "sources": [ { "key": "robots-meta-tag-spec", "title": "Robots meta tag, data-nosnippet, and X-Robots-Tag specifications", "url": "https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" }, { "key": "google-discover", "title": "Discover and your website", "url": "https://developers.google.com/search/docs/appearance/google-discover", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C104, slide, John Mueller, Day 2]" } ], "docs": [ { "id": "D2-C086", "day": 2, "session_id": "D2-S04", "session": "Controlling indexing", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's robots meta tag specification says Google chooses the snippet length when no max-snippet rule is set, and with max-snippet:-1 chooses the length it believes most effective; it does not say that -1 produces longer snippets.", "quote": "", "quote_checked": false, "credit": "Google Search Central", "speaker": null, "sources": [ { "key": "robots-meta-tag-spec", "title": "Robots meta tag, data-nosnippet, and X-Robots-Tag specifications", "url": "https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search Central", "cite": "[D2-C086, docs, Google Search Central, https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag]" } ], "pages": [ { "key": "robots-meta-tag-spec", "title": "Robots meta tag, data-nosnippet, and X-Robots-Tag specifications", "url": "https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag", "publisher": "Google Search Central", "checked": "2026-10-03" } ], "analysis": [ { "id": "D2-C105", "day": 2, "session_id": "D2-S04", "session": "Controlling indexing", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "Set max-snippet:-1 and max-image-preview:large on every indexable template unless licensing requires otherwise, and check that no CMS, plug-in or CDN setting adds lower snippet or image preview limits by default.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D2-C105, analysis, Ibrahim Anjro]" } ], "topics": [ "snippet-controls", "images" ], "entities": [ { "id": "max-snippet", "name": "max-snippet", "count": 4 }, { "id": "snippets", "name": "Snippets", "count": 3 }, { "id": "max-image-preview", "name": "max-image-preview", "count": 2 }, { "id": "cdn", "name": "CDN", "count": 1 }, { "id": "meta-robots-tag", "name": "Robots meta tag", "count": 1 } ] }, { "id": "DIF-14", "title": "PageRank's and MUM's role in ranking", "follow": "Follow Google's ranking systems guide: PageRank has evolved a lot and is still part of the core ranking systems, and MUM is not used for general ranking, only for specific applications. Quote the stage remark that PageRank is not used so much anymore only as a remark, never as PageRank being switched off, and read the slide's list as systems Google runs, not as systems that rank every query.", "event": [ { "id": "D3-C136", "day": 3, "session_id": "D3-S05", "session": "How Google thinks about Quality", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Google's quality talk called PageRank the speaker's favourite ranking system, elegant in its time, but said Google does not really use it so much anymore.", "quote": "My favorite is probably PageRank, even though we don't really use them so much anymore.", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [ { "key": "ranking-systems-guide", "title": "A guide to Google Search ranking systems", "url": "https://developers.google.com/search/docs/appearance/ranking-systems-guide", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D3-C136, stage, Google, Day 3]" }, { "id": "D3-C133", "day": 3, "session_id": "D3-S05", "session": "How Google thinks about Quality", "label": "slide", "label_meaning": "shown on screen", "verification": "confirmed", "verification_meaning": "confirmed by Google docs", "text": "Google's slide said there is not one single ranking system and named spam detection systems, the reviews system, BERT, MUM, RankBrain, freshness systems, deduplication systems, crisis information systems and link analysis systems (PageRank).", "quote": "There’s not one single ranking system...", "quote_checked": true, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [ { "key": "ranking-systems-guide", "title": "A guide to Google Search ranking systems", "url": "https://developers.google.com/search/docs/appearance/ranking-systems-guide", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D3-C133, slide, Google, Day 3]" } ], "docs": [ { "id": "D3-C138", "day": 3, "session_id": "D3-S05", "session": "How Google thinks about Quality", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's ranking systems guide says PageRank, one of its core ranking systems when Google first launched, has evolved a lot since then and continues to be part of its core ranking systems.", "quote": "", "quote_checked": false, "credit": "Google Search Central", "speaker": null, "sources": [ { "key": "ranking-systems-guide", "title": "A guide to Google Search ranking systems", "url": "https://developers.google.com/search/docs/appearance/ranking-systems-guide", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search Central", "cite": "[D3-C138, docs, Google Search Central, https://developers.google.com/search/docs/appearance/ranking-systems-guide]" }, { "id": "D1-C130", "day": 1, "session_id": "D1-S03", "session": "How Search works and where's AI?", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's ranking systems guide says MUM is not currently used for general ranking in Search, only for specific applications such as COVID-19 vaccine searches and featured snippet callouts.", "quote": "It's not currently used for general ranking in Search", "quote_checked": false, "credit": "Google Search Central", "speaker": null, "sources": [ { "key": "ranking-systems-guide", "title": "A guide to Google Search ranking systems", "url": "https://developers.google.com/search/docs/appearance/ranking-systems-guide", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search Central", "cite": "[D1-C130, docs, Google Search Central, https://developers.google.com/search/docs/appearance/ranking-systems-guide]" } ], "pages": [ { "key": "ranking-systems-guide", "title": "A guide to Google Search ranking systems", "url": "https://developers.google.com/search/docs/appearance/ranking-systems-guide", "publisher": "Google Search Central", "checked": "2026-10-03" } ], "analysis": [ { "id": "D3-C137", "day": 3, "session_id": "D3-S05", "session": "How Google thinks about Quality", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "The remark that PageRank is not used so much anymore differs from Google's ranking systems guide, which says PageRank has evolved a lot and continues to be part of the core ranking systems; read it as PageRank weighing less among many signals, not as PageRank being switched off, so links still matter.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "ranking-systems-guide", "title": "A guide to Google Search ranking systems", "url": "https://developers.google.com/search/docs/appearance/ranking-systems-guide", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "the author", "cite": "[D3-C137, analysis, Ibrahim Anjro]" }, { "id": "D3-C135", "day": 3, "session_id": "D3-S05", "session": "How Google thinks about Quality", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "The quality talk's slide listed MUM among Google's ranking systems, while Google's ranking systems guide says MUM is not currently used for general ranking in Search; read the slide as a list of systems Google runs, not as proof that each one ranks every query.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "ranking-systems-guide", "title": "A guide to Google Search ranking systems", "url": "https://developers.google.com/search/docs/appearance/ranking-systems-guide", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "the author", "cite": "[D3-C135, analysis, Ibrahim Anjro]" } ], "topics": [ "ranking-systems", "ai-in-search-systems" ], "entities": [ { "id": "pagerank", "name": "PageRank", "count": 4 }, { "id": "duplicate-content-concept", "name": "Duplicate content", "count": 1 } ] }, { "id": "DIF-15", "title": "SpamBrain's launch year and its '5 times more spam sites'", "follow": "Cite 2018 as SpamBrain's launch year, from Google's 2021 webspam report; the 2022 heard on stage is the year of the improvements in the 2022 report. Quote '5 times more spam sites' as that report does, 2022 against 2021 (and 200 times more than at launch), not as SpamBrain against Google's earlier spam algorithms.", "event": [ { "id": "D2-C670", "day": 2, "session_id": "D2-S19", "session": "Calculating (some) signals", "label": "stage", "label_meaning": "said on stage", "verification": "confirmed", "verification_meaning": "confirmed by Google docs", "text": "SpamBrain is central to Google's spam-fighting efforts and has been improved many times since its launch.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [ { "key": "webspam-report-2022", "title": "How we fought spam on Google Search in 2022", "url": "https://developers.google.com/search/blog/2023/04/webspam-report-2022", "publisher": "Search Central blog (11 April 2023)", "kind": "google", "checked": "2026-10-03" }, { "key": "webspam-report-2021", "title": "How we fought Search spam on Google in 2021", "url": "https://developers.google.com/search/blog/2022/04/webspam-report-2021", "publisher": "Search Central blog (21 April 2022)", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C670, stage, Google, Day 2]" }, { "id": "D2-C673", "day": 2, "session_id": "D2-S19", "session": "Calculating (some) signals", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "SpamBrain was said to detect 5 times more spam sites than the spam algorithms Google had launched before it.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [], "by": "Google", "cite": "[D2-C673, stage, Google, Day 2]" } ], "docs": [ { "id": "D2-C671", "day": 2, "session_id": "D2-S19", "session": "Calculating (some) signals", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's 2021 webspam report says SpamBrain, its AI-based spam-prevention system, was launched in 2018 and has been continuously improved since.", "quote": "", "quote_checked": false, "credit": "Search Central blog (21 April 2022)", "speaker": null, "sources": [ { "key": "webspam-report-2021", "title": "How we fought Search spam on Google in 2021", "url": "https://developers.google.com/search/blog/2022/04/webspam-report-2021", "publisher": "Search Central blog (21 April 2022)", "kind": "google", "checked": "2026-10-03" } ], "by": "Search Central blog (21 April 2022)", "cite": "[D2-C671, docs, Search Central blog (21 April 2022), https://developers.google.com/search/blog/2022/04/webspam-report-2021]" }, { "id": "D2-C674", "day": 2, "session_id": "D2-S19", "session": "Calculating (some) signals", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's 2022 webspam report says SpamBrain detected 5 times more spam sites in 2022 than in 2021, and 200 times more than when it first launched.", "quote": "", "quote_checked": false, "credit": "Search Central blog (11 April 2023)", "speaker": null, "sources": [ { "key": "webspam-report-2022", "title": "How we fought spam on Google Search in 2022", "url": "https://developers.google.com/search/blog/2023/04/webspam-report-2022", "publisher": "Search Central blog (11 April 2023)", "kind": "google", "checked": "2026-10-03" } ], "by": "Search Central blog (11 April 2023)", "cite": "[D2-C674, docs, Search Central blog (11 April 2023), https://developers.google.com/search/blog/2023/04/webspam-report-2022]" } ], "pages": [ { "key": "webspam-report-2021", "title": "How we fought Search spam on Google in 2021", "url": "https://developers.google.com/search/blog/2022/04/webspam-report-2021", "publisher": "Search Central blog (21 April 2022)", "checked": "2026-10-03" }, { "key": "webspam-report-2022", "title": "How we fought spam on Google Search in 2022", "url": "https://developers.google.com/search/blog/2023/04/webspam-report-2022", "publisher": "Search Central blog (11 April 2023)", "checked": "2026-10-03" } ], "analysis": [ { "id": "D2-C672", "day": 2, "session_id": "D2-S19", "session": "Calculating (some) signals", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "The SpamBrain launch year mentioned on stage, with hesitation, was 2022, which does not match Google's documented 2018; 2022 is the year of the improvements described in Google's 2022 webspam report, so cite 2018 as the launch year.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D2-C672, analysis, Ibrahim Anjro]" }, { "id": "D2-C675", "day": 2, "session_id": "D2-S19", "session": "Calculating (some) signals", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "The '5 times more spam sites' figure said on stage matches Google's 2022 webspam report, but the report compares 2022 with 2021 (and gives 200 times since launch), not SpamBrain with earlier algorithms; quote the documented comparison.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D2-C675, analysis, Ibrahim Anjro]" } ], "topics": [ "spam-detection" ], "entities": [ { "id": "spambrain", "name": "SpamBrain", "count": 6 } ] }, { "id": "DIF-16", "title": "The year of the 40 billion spammy pages a day", "follow": "Cite 40 billion spammy pages a day as Google's published figure, from its webspam report for 2020 (published in April 2021) and its How Search Works page. The slide's 'In 2023' heading does not make it a 2023 measurement.", "event": [ { "id": "D3-C197", "day": 3, "session_id": "D3-S05", "session": "How Google thinks about Quality", "label": "stage", "label_meaning": "said on stage", "verification": "confirmed", "verification_meaning": "confirmed by Google docs", "text": "Google's quality talk said Google discovers tens of billions of spam pages every day.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [ { "key": "hsw-detecting-spam", "title": "Detecting spam to bring you relevant and reliable results", "url": "https://www.google.com/search/howsearchworks/how-search-works/detecting-spam/", "publisher": "Google Search (How Search Works)", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D3-C197, stage, Google, Day 3]" }, { "id": "D3-C239", "day": 3, "session_id": "D3-S07", "session": "What are quality updates", "label": "slide", "label_meaning": "shown on screen", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Google's slide, headed 'In 2023, there were...', said 40 billion spammy pages are detected every day.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [ { "key": "webspam-report-2020", "title": "How we fought Search spam on Google in 2020", "url": "https://developers.google.com/search/blog/2021/04/how-we-fought-search-spam-2020", "publisher": "Search Central blog (29 April 2021)", "kind": "google", "checked": "2026-10-03" }, { "key": "hsw-detecting-spam", "title": "Detecting spam to bring you relevant and reliable results", "url": "https://www.google.com/search/howsearchworks/how-search-works/detecting-spam/", "publisher": "Google Search (How Search Works)", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D3-C239, slide, Google, Day 3]" } ], "docs": [ { "id": "D3-C240", "day": 3, "session_id": "D3-S07", "session": "What are quality updates", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's webspam report for 2020, published in April 2021, says Google discovers 40 billion spammy pages every day.", "quote": "", "quote_checked": false, "credit": "Search Central blog (29 April 2021)", "speaker": null, "sources": [ { "key": "webspam-report-2020", "title": "How we fought Search spam on Google in 2020", "url": "https://developers.google.com/search/blog/2021/04/how-we-fought-search-spam-2020", "publisher": "Search Central blog (29 April 2021)", "kind": "google", "checked": "2026-10-03" } ], "by": "Search Central blog (29 April 2021)", "cite": "[D3-C240, docs, Search Central blog (29 April 2021), https://developers.google.com/search/blog/2021/04/how-we-fought-search-spam-2020]" } ], "pages": [ { "key": "webspam-report-2020", "title": "How we fought Search spam on Google in 2020", "url": "https://developers.google.com/search/blog/2021/04/how-we-fought-search-spam-2020", "publisher": "Search Central blog (29 April 2021)", "checked": "2026-10-03" } ], "analysis": [ { "id": "D3-C241", "day": 3, "session_id": "D3-S07", "session": "What are quality updates", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "Cite 40 billion spammy pages a day as Google's published figure, from its webspam report for 2020 and its How Search Works page: the slide's 'In 2023' heading does not make it a 2023 measurement, because the 2021 and 2022 reports give no daily count.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "webspam-report-2020", "title": "How we fought Search spam on Google in 2020", "url": "https://developers.google.com/search/blog/2021/04/how-we-fought-search-spam-2020", "publisher": "Search Central blog (29 April 2021)", "kind": "google", "checked": "2026-10-03" }, { "key": "webspam-report-2021", "title": "How we fought Search spam on Google in 2021", "url": "https://developers.google.com/search/blog/2022/04/webspam-report-2021", "publisher": "Search Central blog (21 April 2022)", "kind": "google", "checked": "2026-10-03" }, { "key": "webspam-report-2022", "title": "How we fought spam on Google Search in 2022", "url": "https://developers.google.com/search/blog/2023/04/webspam-report-2022", "publisher": "Search Central blog (11 April 2023)", "kind": "google", "checked": "2026-10-03" }, { "key": "hsw-detecting-spam", "title": "Detecting spam to bring you relevant and reliable results", "url": "https://www.google.com/search/howsearchworks/how-search-works/detecting-spam/", "publisher": "Google Search (How Search Works)", "kind": "google", "checked": "2026-10-03" } ], "by": "the author", "cite": "[D3-C241, analysis, Ibrahim Anjro]" }, { "id": "D3-C200", "day": 3, "session_id": "D3-S05", "session": "How Google thinks about Quality", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "The spoken 'tens of billions of spam pages' a day matches Google's How Search Works page, which says its systems find 40 billion spammy pages every day, and the later Day 3 slide '40B spammy pages detected every day' (under 'In 2023'); cite 40 billion a day.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "hsw-detecting-spam", "title": "Detecting spam to bring you relevant and reliable results", "url": "https://www.google.com/search/howsearchworks/how-search-works/detecting-spam/", "publisher": "Google Search (How Search Works)", "kind": "google", "checked": "2026-10-03" } ], "by": "the author", "cite": "[D3-C200, analysis, Ibrahim Anjro]" } ], "topics": [ "spam-detection" ], "entities": [] }, { "id": "DIF-17", "title": "Google's 2023 testing figures", "follow": "Cite the figures on Google's How Search Works page, with the year 2023: 719,326 search quality tests, 124,942 side-by-side experiments, 16,871 live traffic experiments and 4,781 launches. Do not use the rounded 800,000+ tests, which match no figure on that page, or the spoken 'close to 5,000' launches.", "event": [ { "id": "D3-C236", "day": 3, "session_id": "D3-S07", "session": "What are quality updates", "label": "slide", "label_meaning": "shown on screen", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Google's slide said that in 2023 Google ran more than 800,000 search quality tests; the speaker added that a more recent figure might exist.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [], "by": "Google", "cite": "[D3-C236, slide, Google, Day 3]" }, { "id": "D3-C237", "day": 3, "session_id": "D3-S07", "session": "What are quality updates", "label": "slide", "label_meaning": "shown on screen", "verification": "confirmed", "verification_meaning": "confirmed by Google docs", "text": "Google's slide said Google made more than 4,700 launches to Search in 2023; the speaker rounded this to close to 5,000.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [ { "key": "hsw-rigorous-testing", "title": "Improving Search with rigorous testing", "url": "https://www.google.com/search/howsearchworks/how-search-works/rigorous-testing/", "publisher": "Google Search (How Search Works)", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D3-C237, slide, Google, Day 3]" }, { "id": "D3-C149", "day": 3, "session_id": "D3-S05", "session": "How Google thinks about Quality", "label": "slide", "label_meaning": "shown on screen", "verification": "confirmed", "verification_meaning": "confirmed by Google docs", "text": "Google's slide said that in 2023 Google ran 719,326 search quality tests, 124,942 side-by-side experiments and 16,871 live traffic experiments, and made 4,781 launches to Search.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [ { "key": "hsw-rigorous-testing", "title": "Improving Search with rigorous testing", "url": "https://www.google.com/search/howsearchworks/how-search-works/rigorous-testing/", "publisher": "Google Search (How Search Works)", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D3-C149, slide, Google, Day 3]" } ], "docs": [ { "id": "D3-C238", "day": 3, "session_id": "D3-S07", "session": "What are quality updates", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's page on how it tests Search says that in 2023 it ran 719,326 search quality tests, 124,942 side-by-side experiments and 16,871 live traffic experiments, and made 4,781 launches.", "quote": "", "quote_checked": false, "credit": "Google Search (How Search Works)", "speaker": null, "sources": [ { "key": "hsw-rigorous-testing", "title": "Improving Search with rigorous testing", "url": "https://www.google.com/search/howsearchworks/how-search-works/rigorous-testing/", "publisher": "Google Search (How Search Works)", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search (How Search Works)", "cite": "[D3-C238, docs, Google Search (How Search Works), https://www.google.com/search/howsearchworks/how-search-works/rigorous-testing/]" } ], "pages": [ { "key": "hsw-rigorous-testing", "title": "Improving Search with rigorous testing", "url": "https://www.google.com/search/howsearchworks/how-search-works/rigorous-testing/", "publisher": "Google Search (How Search Works)", "checked": "2026-10-03" } ], "analysis": [ { "id": "D3-C150", "day": 3, "session_id": "D3-S05", "session": "How Google thinks about Quality", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "Two Day 3 slides headed 'In 2023' gave Google's testing figures in two versions: exact in the quality talk (719,326 search quality tests, 4,781 launches) and rounded in the updates talk (800,000+ tests, 4,700+ launches). Google's How Search Works page states the exact 719,326 and 4,781, so cite those with the year 2023; 800,000+ matches no figure on that page, although the page's three test counts (719,326 quality tests, 124,942 side-by-side and 16,871 live traffic experiments) add up to 861,139.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "hsw-rigorous-testing", "title": "Improving Search with rigorous testing", "url": "https://www.google.com/search/howsearchworks/how-search-works/rigorous-testing/", "publisher": "Google Search (How Search Works)", "kind": "google", "checked": "2026-10-03" } ], "by": "the author", "cite": "[D3-C150, analysis, Ibrahim Anjro]" } ], "topics": [ "search-quality-evaluation" ], "entities": [] }, { "id": "DIF-18", "title": "The size of Gemini's context window", "follow": "Follow the Gemini API's long-context documentation: Gemini models have context windows of 1 million or more tokens, so plan with about one million tokens as the documented floor, not the several million said on stage. Do not quote the 900,000 heard on stage, which had no unit.", "event": [ { "id": "D2-C331", "day": 2, "session_id": "D2-S07", "session": "Understanding what's on a page", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Gary Illyes said Gemini's context window, where chunking actually matters, holds millions of tokens.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "Gary Illyes", "sources": [ { "key": "gemini-long-context", "title": "Long context", "url": "https://ai.google.dev/gemini-api/docs/long-context", "publisher": "Google AI for Developers (Gemini API docs)", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C331, stage, Gary Illyes, Day 2]" }, { "id": "D2-C869", "day": 2, "session_id": "D2-S07", "session": "Understanding what's on a page", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Right after saying Gemini's context window holds millions of tokens, Gary Illyes put its size at perhaps 900,000 or even closer to a million, without a unit that the recordings capture.", "quote": "the context window is perhaps 900,000 or even closer to a million big", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "Gary Illyes", "sources": [ { "key": "gemini-long-context", "title": "Long context", "url": "https://ai.google.dev/gemini-api/docs/long-context", "publisher": "Google AI for Developers (Gemini API docs)", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C869, stage, Gary Illyes, Day 2]" } ], "docs": [], "pages": [ { "key": "gemini-long-context", "title": "Long context", "url": "https://ai.google.dev/gemini-api/docs/long-context", "publisher": "Google AI for Developers (Gemini API docs)", "checked": "2026-10-03" } ], "analysis": [ { "id": "D2-C872", "day": 2, "session_id": "D2-S07", "session": "Understanding what's on a page", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "The talk gave Gemini's context window both as millions of tokens and as roughly 900,000 to a million; Google's long-context docs say Gemini models have context windows of 1 million or more tokens (about eight average novels per million), so plan with about one million tokens as the documented floor rather than several million.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D2-C872, analysis, Ibrahim Anjro]" } ], "topics": [ "gemini-and-search", "chunking" ], "entities": [ { "id": "gemini", "name": "Gemini", "count": 3 } ] }, { "id": "DIF-19", "title": "What the popularity rank attribute measures", "follow": "Follow Merchant Center's definition: popularity_rank is the merchant's own 0-100 rank of a product against the rest of its inventory, based on its recent sales. It is not a sales figure across shops or marketplaces.", "event": [ { "id": "D3-C374", "day": 3, "session_id": "D3-S11", "session": "Shopping on Search: Beyond the blue links", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Google added a popularity rank feed attribute because consumers want to know how well a product sells on a marketplace.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": "Alex Jansen", "sources": [ { "key": "mc-popularity-rank", "title": "Popularity rank [popularity_rank]", "url": "https://support.google.com/merchants/answer/17085297?hl=en", "publisher": "Google Merchant Center Help", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D3-C374, stage, Alex Jansen, Day 3]" } ], "docs": [ { "id": "D3-C375", "day": 3, "session_id": "D3-S11", "session": "Shopping on Search: Beyond the blue links", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Merchant Center's popularity_rank is a 0-100 value the merchant assigns to rank a product's popularity, based on its recent sales, against the rest of its own inventory; it does not reflect user ratings.", "quote": "", "quote_checked": false, "credit": "Google Merchant Center Help", "speaker": null, "sources": [ { "key": "mc-popularity-rank", "title": "Popularity rank [popularity_rank]", "url": "https://support.google.com/merchants/answer/17085297?hl=en", "publisher": "Google Merchant Center Help", "kind": "google", "checked": "2026-10-03" }, { "key": "mc-product-data-spec", "title": "Product data specification", "url": "https://support.google.com/merchants/answer/7052112?hl=en", "publisher": "Google Merchant Center Help", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Merchant Center Help", "cite": "[D3-C375, docs, Google Merchant Center Help, https://support.google.com/merchants/answer/17085297?hl=en]" } ], "pages": [ { "key": "mc-popularity-rank", "title": "Popularity rank [popularity_rank]", "url": "https://support.google.com/merchants/answer/17085297?hl=en", "publisher": "Google Merchant Center Help", "checked": "2026-10-03" }, { "key": "mc-product-data-spec", "title": "Product data specification", "url": "https://support.google.com/merchants/answer/7052112?hl=en", "publisher": "Google Merchant Center Help", "checked": "2026-10-03" } ], "analysis": [ { "id": "D3-C376", "day": 3, "session_id": "D3-S11", "session": "Shopping on Search: Beyond the blue links", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "On stage the popularity rank was framed as how well a product sells on a marketplace, but Google's documentation defines it as the merchant's own 0-100 ranking against the rest of its inventory: a self-reported, relative value, not a sales figure across shops.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "mc-popularity-rank", "title": "Popularity rank [popularity_rank]", "url": "https://support.google.com/merchants/answer/17085297?hl=en", "publisher": "Google Merchant Center Help", "kind": "google", "checked": "2026-10-03" } ], "by": "the author", "cite": "[D3-C376, analysis, Ibrahim Anjro]" } ], "topics": [ "shopping-data" ], "entities": [ { "id": "merchant-center", "name": "Merchant Center", "count": 1 } ] }, { "id": "DIF-20", "title": "New Merchant Center attributes in schema.org markup", "follow": "Send the new attributes in the Merchant Center feed, the documented route, and keep the documented Product markup next to the feed, which Google says maximises eligibility. As of 3 October 2026 Google documents no schema.org property for the new attributes except item_group_title (ProductGroup.name); add markup for the others only once Google documents it.", "event": [ { "id": "D3-C380", "day": 3, "session_id": "D3-S11", "session": "Shopping on Search: Beyond the blue links", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Most of the new conversational feed attributes were already available in schema.org, so Google ties them back to structured data and can use them from product markup as well as from feeds.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": "Alex Jansen", "sources": [], "by": "Google", "cite": "[D3-C380, stage, Alex Jansen, Day 3]" } ], "docs": [ { "id": "D3-C344", "day": 3, "session_id": "D3-S10", "session": "How Search results are born", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's Product structured data introduction says that providing both on-page structured data and a Merchant Center feed maximizes eligibility for shopping experiences and helps Google understand and verify the data; product snippets may take pricing from the feed when the markup lacks it.", "quote": "", "quote_checked": false, "credit": "Google Search Central", "speaker": null, "sources": [ { "key": "product-sd-intro", "title": "Introduction to Product structured data", "url": "https://developers.google.com/search/docs/appearance/structured-data/product", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search Central", "cite": "[D3-C344, docs, Google Search Central, https://developers.google.com/search/docs/appearance/structured-data/product]" } ], "pages": [ { "key": "product-sd-intro", "title": "Introduction to Product structured data", "url": "https://developers.google.com/search/docs/appearance/structured-data/product", "publisher": "Google Search Central", "checked": "2026-10-03" }, { "key": "mc-product-data-spec", "title": "Product data specification", "url": "https://support.google.com/merchants/answer/7052112?hl=en", "publisher": "Google Merchant Center Help", "checked": "2026-10-03" }, { "key": "merchant-listing-sd", "title": "Merchant listing (Product, Offer) structured data", "url": "https://developers.google.com/search/docs/appearance/structured-data/merchant-listing", "publisher": "Google Search Central", "checked": "2026-10-04" } ], "analysis": [ { "id": "D3-C381", "day": 3, "session_id": "D3-S11", "session": "Shopping on Search: Beyond the blue links", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "As of 3 October 2026 Google's Merchant Center help lists no schema.org property for question_and_answer, document_link, related_product, popularity_rank, variant_option or product_detail (only item_group_title maps, to ProductGroup.name), and Search Central does not document such markup: reading these attributes from schema.org is a stage statement, the feed is the documented route.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "mc-question-and-answer", "title": "Question and answer [question_and_answer]", "url": "https://support.google.com/merchants/answer/17085211?hl=en", "publisher": "Google Merchant Center Help", "kind": "google", "checked": "2026-10-03" }, { "key": "mc-document-link", "title": "Document link [document_link]", "url": "https://support.google.com/merchants/answer/17084656?hl=en", "publisher": "Google Merchant Center Help", "kind": "google", "checked": "2026-10-03" }, { "key": "mc-related-product", "title": "Related product [related_product]", "url": "https://support.google.com/merchants/answer/17085213?hl=en", "publisher": "Google Merchant Center Help", "kind": "google", "checked": "2026-10-03" }, { "key": "mc-popularity-rank", "title": "Popularity rank [popularity_rank]", "url": "https://support.google.com/merchants/answer/17085297?hl=en", "publisher": "Google Merchant Center Help", "kind": "google", "checked": "2026-10-03" }, { "key": "mc-variant-option", "title": "Variant option [variant_option]", "url": "https://support.google.com/merchants/answer/17085214?hl=en", "publisher": "Google Merchant Center Help", "kind": "google", "checked": "2026-10-03" }, { "key": "mc-product-detail", "title": "Product detail [product_detail]", "url": "https://support.google.com/merchants/answer/9218260?hl=en", "publisher": "Google Merchant Center Help", "kind": "google", "checked": "2026-10-03" }, { "key": "mc-item-group-title", "title": "Item group title [item_group_title]", "url": "https://support.google.com/merchants/answer/17085146?hl=en", "publisher": "Google Merchant Center Help", "kind": "google", "checked": "2026-10-03" }, { "key": "merchant-listing-sd", "title": "Merchant listing (Product, Offer) structured data", "url": "https://developers.google.com/search/docs/appearance/structured-data/merchant-listing", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-04" } ], "by": "the author", "cite": "[D3-C381, analysis, Ibrahim Anjro]" } ], "topics": [ "merchant-markup", "shopping-data", "schema-org" ], "entities": [ { "id": "merchant-center", "name": "Merchant Center", "count": 2 }, { "id": "schema-org-vocabulary", "name": "Schema.org", "count": 2 }, { "id": "structured-data-concept", "name": "Structured data", "count": 2 } ] } ], "pairs": [ { "type": "updates", "from": { "id": "D1-C125", "day": 1, "session_id": "D1-S02", "session": "What's new in the world of Search", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Since 16 September 2026, US publishers and creators qualify for a Search profile with 10,000 followers across YouTube, Instagram, X or TikTok, and media organisations can claim and manage profiles for all their sub-brands from one login.", "quote": "We've lowered the eligibility threshold to 10,000 followers across YouTube, Instagram, X, or TikTok.", "quote_checked": false, "credit": "Google blog (16 September 2026)", "speaker": null, "sources": [ { "key": "search-profiles-update", "title": "3 new ways we're improving Search profiles for publishers", "url": "https://blog.google/products-and-platforms/products/search/3-new-ways-were-improving-search-profiles-for-publishers/", "publisher": "Google blog (16 September 2026)", "kind": "google", "checked": "2026-10-02" } ], "by": "Google blog (16 September 2026)", "cite": "[D1-C125, docs, Google blog (16 September 2026), https://blog.google/products-and-platforms/products/search/3-new-ways-were-improving-search-profiles-for-publishers/]" }, "to": { "id": "D1-C026", "day": 1, "session_id": "D1-S02", "session": "What's new in the world of Search", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Search profiles launched on 4 June 2026, in the US first, for creators and publishers with a sizable following on at least one major social or video platform. They appear in knowledge panels and Discover.", "quote": "", "quote_checked": false, "credit": "Google blog (4 June 2026)", "speaker": null, "sources": [ { "key": "search-profiles-blog", "title": "A new profile to help publishers and creators highlight their work on Search", "url": "https://blog.google/products-and-platforms/products/search/a-new-profile-to-help-publishers-and-creators-highlight-their-work-on-search/", "publisher": "Google blog (4 June 2026)", "kind": "google", "checked": "2026-10-02" } ], "by": "Google blog (4 June 2026)", "cite": "[D1-C026, docs, Google blog (4 June 2026), https://blog.google/products-and-platforms/products/search/a-new-profile-to-help-publishers-and-creators-highlight-their-work-on-search/]" }, "rows": [] }, { "type": "contradicts", "from": { "id": "D1-C296", "day": 1, "session_id": "D1-S04", "session": "Lightning session A: Automation and AI", "label": "stage", "label_meaning": "said on stage", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "A community speaker argued for adopting the GEO label as the industry's chance to leave behind the bad reputation SEO built, unlike Google's view earlier the same day that the new name is not needed.", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": "Thiago Pojda", "sources": [], "by": "a community speaker", "cite": "[D1-C296, stage, Thiago Pojda, Day 1]" }, "to": { "id": "D1-C049", "day": 1, "session_id": "D1-S02", "session": "What's new in the world of Search", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Gary Illyes argued that GEO is a label invented to create a new field and is not needed. Understanding how SEO works is enough.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": "Gary Illyes", "sources": [ { "key": "ai-optimization-guide", "title": "Optimizing your website for generative AI features on Google Search", "url": "https://developers.google.com/search/docs/fundamentals/ai-optimization-guide", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D1-C049, stage, Gary Illyes, Day 1]" }, "rows": [] }, { "type": "contradicts", "from": { "id": "D1-C296", "day": 1, "session_id": "D1-S04", "session": "Lightning session A: Automation and AI", "label": "stage", "label_meaning": "said on stage", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "A community speaker argued for adopting the GEO label as the industry's chance to leave behind the bad reputation SEO built, unlike Google's view earlier the same day that the new name is not needed.", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": "Thiago Pojda", "sources": [], "by": "a community speaker", "cite": "[D1-C296, stage, Thiago Pojda, Day 1]" }, "to": { "id": "D1-C050", "day": 1, "session_id": "D1-S03", "session": "How Search works and where's AI?", "label": "slide", "label_meaning": "shown on screen", "verification": "confirmed", "verification_meaning": "confirmed by Google docs", "text": "Google's answer to 'SEO is dead, long live GEO' is not to worry about the name: good SEO is good GEO and AEO.", "quote": "Don't worry about what to call it. Good SEO is good GEO, AEO.", "quote_checked": true, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": null, "sources": [ { "key": "ai-optimization-guide", "title": "Optimizing your website for generative AI features on Google Search", "url": "https://developers.google.com/search/docs/fundamentals/ai-optimization-guide", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D1-C050, slide, Google, Day 1]" }, "rows": [] }, { "type": "contradicts", "from": { "id": "D2-C325", "day": 2, "session_id": "D2-S07", "session": "Understanding what's on a page", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Tokenization for AI models such as Gemini, in training and in inference, differs from tokenization for Search, although Gary Illyes qualified this with 'or mostly'.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "Gary Illyes", "sources": [], "by": "Google", "cite": "[D2-C325, stage, Gary Illyes, Day 2]" }, "to": { "id": "D1-C039", "day": 1, "session_id": "D1-S03", "session": "How Search works and where's AI?", "label": "slide", "label_meaning": "shown on screen", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Gemini is not part of Search, but it uses crawlers for data, shares some technologies such as tokenization and deduping, and grounds on the Search index.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": null, "sources": [ { "key": "common-crawlers", "title": "List of Google's common crawlers", "url": "https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "Google", "cite": "[D1-C039, slide, Google, Day 1]" }, "rows": [] }, { "type": "contradicts", "from": { "id": "D2-C393", "day": 2, "session_id": "D2-S08", "session": "Handling web duplication", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Google's speaker said that pointing rel=canonical from the pages of a paginated set to the first page can sometimes make sense depending on the goal, for example to make a category page more visible, but that it affects canonicalization and deduplication.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [], "by": "Google", "cite": "[D2-C393, stage, Google, Day 2]" }, "to": { "id": "D1-C115", "day": 1, "session_id": "D1-S00", "session": "Day 1, session not recorded", "label": "docs", "label_meaning": "Google's documentation", "verification": "source", "verification_meaning": "is the documentation", "text": "Google's crawlers do not click buttons. Each page in a series needs its own URL and an link to the next page, should not use page 1 as its canonical, and rel=next and rel=prev are no longer used.", "quote": "", "quote_checked": false, "credit": "Google Search Central", "speaker": null, "sources": [ { "key": "pagination-guide", "title": "Pagination, incremental page loading, and their impact on Google Search", "url": "https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google Search Central", "cite": "[D1-C115, docs, Google Search Central, https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading]" }, "rows": [ "DIF-10" ] }, { "type": "contradicts", "from": { "id": "D2-C429", "day": 2, "session_id": "D2-S09", "session": "Lightning session E: Managing Duplicates and Site Moves", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "A community speaker said pages carry different link equity, and a canonical leader that is not the strongest page in its group is technically valid but most likely suboptimal for ranking, so the strongest page should be the leader.", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "Tobias Schwarz", "sources": [], "by": "a community speaker", "cite": "[D2-C429, stage, Tobias Schwarz, Day 2]" }, "to": { "id": "D2-C348", "day": 2, "session_id": "D2-S08", "session": "Handling web duplication", "label": "slide", "label_meaning": "shown on screen", "verification": "confirmed", "verification_meaning": "confirmed by Google docs", "text": "Google forwards the signals attached to every URL in a duplicate cluster, such as links, to the representative URL, so that nothing is lost by showing only one URL.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [ { "key": "consolidate-duplicate-urls", "title": "How to specify a canonical URL with rel=\"canonical\" and other methods", "url": "https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C348, slide, Google, Day 2]" }, "rows": [] } ], "hedged": [ { "id": "D1-C499", "day": 1, "session_id": "D1-S01", "session": "Welcome and opening keynotes", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "The keynote added that people who also use a standalone LLM keep certain types of use anchored on Google (the example given is unclear in both recordings).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": "Lino Cattaruzzi", "sources": [], "by": "Google", "cite": "[D1-C499, stage, Lino Cattaruzzi, Day 1]" }, { "id": "D1-C249", "day": 1, "session_id": "D1-S04", "session": "Lightning session A: Automation and AI", "label": "stage", "label_meaning": "said on stage", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "A community demo showed a script that opens Chrome with a saved session, pastes a URL into Google's Rich Results Test, waits about 15 seconds, then screenshots and saves the result and retries on failure (the demo's recording is largely unintelligible; the tool name is a best reading).", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": null, "sources": [], "by": "a community speaker", "cite": "[D1-C249, stage, a community speaker, Day 1]" }, { "id": "D1-C272", "day": 1, "session_id": "D1-S04", "session": "Lightning session A: Automation and AI", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "A community speaker advised against publishing markdown copies of HTML pages for AI agents: the copy is a duplicate (which the speaker also called a possible source of cloaking, an uncertain word in the recordings), and the models are trained to read HTML, CSS and JavaScript.", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": "Carlos Ortega", "sources": [ { "key": "ai-optimization-guide", "title": "Optimizing your website for generative AI features on Google Search", "url": "https://developers.google.com/search/docs/fundamentals/ai-optimization-guide", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "a community speaker", "cite": "[D1-C272, stage, Carlos Ortega, Day 1]" }, { "id": "D1-C501", "day": 1, "session_id": "D1-S04", "session": "Lightning session A: Automation and AI", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "A community demo's script used both input modes of Google's Rich Results Test: the URL mode for public pages, which Google fetches itself, and the code mode, into which the script pasted the page's HTML, for private pages and pages Google cannot fetch (best reading of a largely unintelligible recording; the second kind of page was heard as 'dead', possibly 'dev').", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": null, "sources": [ { "key": "rich-results-test-help", "title": "Rich Results Test", "url": "https://support.google.com/webmasters/answer/7445569?hl=en", "publisher": "Google Search Console Help", "kind": "google", "checked": "2026-10-04" } ], "by": "a community speaker", "cite": "[D1-C501, stage, a community speaker, Day 1]" }, { "id": "D1-C502", "day": 1, "session_id": "D1-S04", "session": "Lightning session A: Automation and AI", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "In a community demo, the structured-data problems Google's Rich Results Test reported on the test page included an empty name, a breadcrumb problem and a price of zero, with errors shown in pink and warnings in orange (best readings of a largely unintelligible recording; each item is heard in only one of the two recordings).", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": null, "sources": [ { "key": "rich-results-test-help", "title": "Rich Results Test", "url": "https://support.google.com/webmasters/answer/7445569?hl=en", "publisher": "Google Search Console Help", "kind": "google", "checked": "2026-10-04" }, { "key": "merchant-listing-sd", "title": "Merchant listing (Product, Offer) structured data", "url": "https://developers.google.com/search/docs/appearance/structured-data/merchant-listing", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-04" } ], "by": "a community speaker", "cite": "[D1-C502, stage, a community speaker, Day 1]" }, { "id": "D1-C526", "day": 1, "session_id": "D1-S07", "session": "How Google interprets robots.txt", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "The real trouble is an unknown line placed between two user-agent lines: while writing RFC 9309, Google asked people whether the first crawler should then inherit the rules that follow, and opinions split roughly 50-50 (how the talk said the question was settled is unclear in the recording).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": null, "sources": [], "by": "Google", "cite": "[D1-C526, stage, Google, Day 1]" }, { "id": "D1-C407", "day": 1, "session_id": "D1-S11", "session": "Lightning session C: Crawling", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "A community speaker cited more than 900 million weekly active ChatGPT users and 2.5 billion monthly users of a Google AI feature (the recording is unclear which), adding that these are not comparable market-share figures.", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": "Jovana Avramovic", "sources": [], "by": "a community speaker", "cite": "[D1-C407, stage, Jovana Avramovic, Day 1]" }, { "id": "D1-C432", "day": 1, "session_id": "D1-S12", "session": "Q&A", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "A Google panelist said they were working on a set of crawler best practices and offering research, malware-scanning and privacy crawlers an exemption from following them, apparently because such crawlers sometimes need to ignore robots.txt or probe URLs that other crawlers would not touch (the reason is a best reading: the audio has 'don't need', which would not explain an exemption).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": null, "sources": [], "by": "Google", "cite": "[D1-C432, stage, Google, Day 1]" }, { "id": "D1-C539", "day": 1, "session_id": "D1-S12", "session": "Q&A", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "A Google panelist said useless plugin-generated parameter URLs can be handled at the web server, for example with a rule or a custom module in Apache, which saves crawl budget so that Google may pick up the URLs that matter instead (the exact mechanism is not clear in the recording).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": null, "sources": [ { "key": "crawl-budget-guide", "title": "Optimize your crawl budget", "url": "https://developers.google.com/crawling/docs/crawl-budget", "publisher": "Google", "kind": "google", "checked": "2026-10-04" }, { "key": "faceted-nav-guide", "title": "Managing crawling of faceted navigation URLs", "url": "https://developers.google.com/crawling/docs/faceted-navigation", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "Google", "cite": "[D1-C539, stage, Google, Day 1]" }, { "id": "D1-C543", "day": 1, "session_id": "D1-S12", "session": "Q&A", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Gary Illyes said that if the time from publishing to Googlebot's first crawl starts rising, how much it rises matters: for the crawling of fresh stories, something like two hours is probably not great (a smaller example figure is unclear in the recording).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": "Gary Illyes", "sources": [], "by": "Google", "cite": "[D1-C543, stage, Gary Illyes, Day 1]" }, { "id": "D1-C546", "day": 1, "session_id": "D1-S12", "session": "Q&A", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "A Google panelist illustrated a crawl capacity limit drop as a step down in the site's hostload, for example from 10 to 5, which the panelist said means Googlebot then makes up to five requests per second (the recording adds 'per connection', which is unclear).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 1)", "speaker": null, "sources": [ { "key": "crawl-budget-guide", "title": "Optimize your crawl budget", "url": "https://developers.google.com/crawling/docs/crawl-budget", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "Google", "cite": "[D1-C546, stage, Google, Day 1]" }, { "id": "D2-C046", "day": 2, "session_id": "D2-S03", "session": "How is HTML interpreted", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "The speaker said Google sometimes also extracts URLs that are typed out as plain text on a page without being hyperlinked; the remarks around this point were unclear in the recording.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [], "by": "Google", "cite": "[D2-C046, stage, Google, Day 2]" }, { "id": "D2-C123", "day": 2, "session_id": "D2-S05", "session": "Lightning session D: Rendering and JavaScript", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "Google documents Gemini grounding only as content from the Search index at prompt time; the live read of a specific page at a user's request, described on stage, is not documented, so it is unclear whether it works like a user-triggered fetcher, which generally ignores robots.txt, or follows Google-Extended.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [], "by": "the author", "cite": "[D2-C123, analysis, Ibrahim Anjro]" }, { "id": "D2-C146", "day": 2, "session_id": "D2-S05", "session": "Lightning session D: Rendering and JavaScript", "label": "stage", "label_meaning": "said on stage", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "On a retail brand's page, the rendered version promised a bigger discount for a newsletter sign-up than the non-rendered version that was served, a mismatch that can hurt customer satisfaction; the two recordings disagree on the figure the rendered page promised.", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "Sören Bendig", "sources": [], "by": "a community speaker", "cite": "[D2-C146, stage, Sören Bendig, Day 2]" }, { "id": "D2-C175", "day": 2, "session_id": "D2-S05", "session": "Lightning session D: Rendering and JavaScript", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "If a page keeps loading content indefinitely, not all of that content will be indexed, because Google's rendering does not go on forever (this passage of the recording is partly unclear).", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "Rebecca Yu", "sources": [], "by": "a community speaker", "cite": "[D2-C175, stage, Rebecca Yu, Day 2]" }, { "id": "D2-C182", "day": 2, "session_id": "D2-S05", "session": "Lightning session D: Rendering and JavaScript", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "If the cause of missing JavaScript content is still unclear after checking the network requests, search the source code for a string related to the missing content.", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "Rebecca Yu", "sources": [], "by": "a community speaker", "cite": "[D2-C182, stage, Rebecca Yu, Day 2]" }, { "id": "D2-C379", "day": 2, "session_id": "D2-S08", "session": "Handling web duplication", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "rel=canonical is probably the most common way site owners signal duplicates, but it is very often wrong, for example a tag whose value reads 'canonical target' instead of a real URL (the example is partly unclear in the recording), so Google can only sometimes trust it.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [ { "key": "canonicalization-troubleshooting", "title": "Fix canonicalization issues", "url": "https://developers.google.com/search/docs/crawling-indexing/canonicalization-troubleshooting", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" }, { "key": "rel-canonical-mistakes-blog", "title": "5 common mistakes with rel=canonical", "url": "https://developers.google.com/search/blog/2013/04/5-common-mistakes-with-relcanonical", "publisher": "Search Central blog (8 April 2013)", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C379, stage, Google, Day 2]" }, { "id": "D2-C882", "day": 2, "session_id": "D2-S09", "session": "Lightning session E: Managing Duplicates and Site Moves", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "In a community case study, an old URL got a 301 redirect only when a new page served the same intent; URLs with no same-intent match were removed with an error status instead of being redirected (the exact code is unclear in the recording).", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "Martyna Ağanoğlu", "sources": [ { "key": "site-move-with-url-changes", "title": "How to move a site", "url": "https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-04" }, { "key": "http-network-errors", "title": "How HTTP status codes affect Google's crawlers", "url": "https://developers.google.com/crawling/docs/troubleshooting/http-status-codes", "publisher": "Google", "kind": "google", "checked": "2026-10-04" } ], "by": "a community speaker", "cite": "[D2-C882, stage, Martyna Ağanoğlu, Day 2]" }, { "id": "D2-C549", "day": 2, "session_id": "D2-S13", "session": "Using images to your advantage and Engaging Search users with videos", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Videos can appear in the main search results, in video-specific result tabs and in Discover (the tab names are unclear in the recording).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": "Gary Illyes", "sources": [ { "key": "video-seo", "title": "Video SEO best practices", "url": "https://developers.google.com/search/docs/appearance/video", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C549, stage, Gary Illyes, Day 2]" }, { "id": "D2-C592", "day": 2, "session_id": "D2-S15", "session": "Focusing on Internationalisation and Localisation", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Server location is not really a reliable country-targeting signal nowadays, so Google does not use it much; the recording is unclear on the word 'server'.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [], "by": "Google", "cite": "[D2-C592, stage, Google, Day 2]" }, { "id": "D2-C977", "day": 2, "session_id": "D2-S16", "session": "Lightning session G: Internationalisation", "label": "stage", "label_meaning": "said on stage", "verification": "confirmed", "verification_meaning": "confirmed by Google docs", "text": "The presenter of the non-Latin-script talk recalled that Google officially treats buying links for ranking as spam (the year of the announcement was not clear in the recording).", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [ { "key": "spam-policies", "title": "Spam policies for Google web search", "url": "https://developers.google.com/search/docs/essentials/spam-policies", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-04" } ], "by": "a community speaker", "cite": "[D2-C977, stage, a community speaker, Day 2]" }, { "id": "D2-C691", "day": 2, "session_id": "D2-S20", "session": "Deciding what goes in the index?", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Under-served languages were presented as an opportunity: where Google's index holds a lot of spam in a language such as Basque, a site that starts publishing in that language can very likely replace that spam with its own content and rank for those keywords (one clause of the reasoning was inaudible).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [], "by": "Google", "cite": "[D2-C691, stage, Google, Day 2]" }, { "id": "D2-C696", "day": 2, "session_id": "D2-S20", "session": "Deciding what goes in the index?", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Index selection applies the negative signals that immediately block indexing: noindex (the likely reading of one unclear word), expired unavailable_after dates, soft 404s, non-canonical duplicates, spam signals and other policies.", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [ { "key": "page-indexing-help", "title": "Page indexing report", "url": "https://support.google.com/webmasters/answer/7440203?hl=en", "publisher": "Google Search Console Help", "kind": "google", "checked": "2026-10-04" }, { "key": "robots-meta-tag-spec", "title": "Robots meta tag, data-nosnippet, and X-Robots-Tag specifications", "url": "https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" }, { "key": "webspam-report-2022", "title": "How we fought spam on Google Search in 2022", "url": "https://developers.google.com/search/blog/2023/04/webspam-report-2022", "publisher": "Search Central blog (11 April 2023)", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C696, stage, Google, Day 2]" }, { "id": "D2-C727", "day": 2, "session_id": "D2-S23", "session": "How does the index look like?", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Google said that when AI Overviews or AI Mode run a query fan-out, the generated queries are sent to Google's Search index and documents come back with their snippets, which then feed the AI-generated answer (part of this passage is unclear in the recording).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 2)", "speaker": null, "sources": [ { "key": "ai-optimization-guide", "title": "Optimizing your website for generative AI features on Google Search", "url": "https://developers.google.com/search/docs/fundamentals/ai-optimization-guide", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" }, { "key": "ai-features-guide", "title": "AI features and your website", "url": "https://developers.google.com/search/docs/appearance/ai-features", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" }, { "key": "robots-meta-tag-spec", "title": "Robots meta tag, data-nosnippet, and X-Robots-Tag specifications", "url": "https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-03" } ], "by": "Google", "cite": "[D2-C727, stage, Google, Day 2]" }, { "id": "D3-C026", "day": 3, "session_id": "D3-S03", "session": "Making sense of users' queries", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Google suggested a test: a search that lists a term's synonyms joined with OR will probably return results very similar to the plain query, because Google adds the synonyms itself (part of the sentence is unclear in the recording).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": "John Mueller", "sources": [], "by": "Google", "cite": "[D3-C026, stage, John Mueller, Day 3]" }, { "id": "D3-C040", "day": 3, "session_id": "D3-S03", "session": "Making sense of users' queries", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Google learns synonyms and siblings from search behaviour: words people search with in the same way become synonyms, while frequent comparison queries mark words as not interchangeable (the end of the sentence is unclear in the recording).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": "John Mueller", "sources": [], "by": "Google", "cite": "[D3-C040, stage, John Mueller, Day 3]" }, { "id": "D3-C509", "day": 3, "session_id": "D3-S13", "session": "Lightning session L: Understanding SERPs and your users", "label": "stage", "label_meaning": "said on stage", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "A community speaker said the loss of clicks on informational queries to AI summaries probably happened for a good reason, with benefits for the user journey (the word 'benefits' is an uncertain reading of the recording).", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [], "by": "a community speaker", "cite": "[D3-C509, stage, a community speaker, Day 3]" }, { "id": "D3-C528", "day": 3, "session_id": "D3-S13", "session": "Lightning session L: Understanding SERPs and your users", "label": "stage", "label_meaning": "said on stage", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "A community speaker said brand familiarity should be built through AI-driven services and earned media as a whole, by improving content and visibility across services ('earned media' is an uncertain reading of the recording).", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [], "by": "a community speaker", "cite": "[D3-C528, stage, a community speaker, Day 3]" }, { "id": "D3-C537", "day": 3, "session_id": "D3-S13", "session": "Lightning session L: Understanding SERPs and your users", "label": "stage", "label_meaning": "said on stage", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "For the brand in a community speaker's controlled test, organic sessions in GA4 roughly halved while direct sessions stayed fairly stable (an uncertain reading; a change of about 2% was mentioned, direction unclear in the recording).", "quote": "", "quote_checked": false, "credit": "a community speaker at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [], "by": "a community speaker", "cite": "[D3-C537, stage, a community speaker, Day 3]" }, { "id": "D3-C564", "day": 3, "session_id": "D3-S16", "session": "Mastering the messy middle", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Assistance also includes showing consumers what people in similar situations chose, because people are social and want that reassurance (the wording of this passage is partly uncertain in the recording).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [], "by": "Google", "cite": "[D3-C564, stage, Google, Day 3]" }, { "id": "D3-C573", "day": 3, "session_id": "D3-S16", "session": "Mastering the messy middle", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "AI users sometimes take even longer purchase journeys, but they perceive their journeys as shorter, a perception the data does not always support (part of this passage is uncertain in the recording).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [], "by": "Google", "cite": "[D3-C573, stage, Google, Day 3]" }, { "id": "D3-C585", "day": 3, "session_id": "D3-S16", "session": "Mastering the messy middle", "label": "stage", "label_meaning": "said on stage", "verification": "undocumented", "verification_meaning": "not in Google docs", "text": "Consumers boosted by AI in their purchase decisions were still a small group in October 2026, but the group is growing as more people start using AI (the word 'boosted' is an uncertain reading at this point of the recording).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [], "by": "Google", "cite": "[D3-C585, stage, Google, Day 3]" }, { "id": "D3-C607", "day": 3, "session_id": "D3-S17", "session": "How long does it take to..?", "label": "stage", "label_meaning": "said on stage", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "An audience member reported recrawl intervals on one very large, popular client site: the homepage about 5 times a day, first-level pages about every 1.5 days (uncertain reading), and pages clustered as soft 404s every 160 to 190 days, adding that other sites will differ.", "quote": "", "quote_checked": false, "credit": "an audience member at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": null, "sources": [], "by": "an audience member", "cite": "[D3-C607, stage, an audience member, Day 3]" }, { "id": "D3-C644", "day": 3, "session_id": "D3-S17", "session": "How long does it take to..?", "label": "stage", "label_meaning": "said on stage", "verification": "consistent", "verification_meaning": "consistent with Google docs", "text": "Gary Illyes said a site move can take up to about a year in the worst case, because Google's slowest signal is recalculated only about once a year (some words of this passage are uncertain readings).", "quote": "", "quote_checked": false, "credit": "Google at Search Central Live Deep Dive Europe 2026 (Day 3)", "speaker": "Gary Illyes", "sources": [ { "key": "site-move-with-url-changes", "title": "How to move a site", "url": "https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-04" } ], "by": "Google", "cite": "[D3-C644, stage, Gary Illyes, Day 3]" }, { "id": "D3-C645", "day": 3, "session_id": "D3-S17", "session": "How long does it take to..?", "label": "analysis", "label_meaning": "the author's interpretation", "verification": "n/a", "verification_meaning": "nothing to verify", "text": "Keep migration redirects in place for at least a year and judge a site move after one to three months, not days: Google's speaker said its slowest signal needs about a year to be recalculated (a partly uncertain passage of the recording), and Google's site move guide says to keep redirects generally at least one year.", "quote": "", "quote_checked": false, "credit": "Ibrahim Anjro (author)", "speaker": null, "sources": [ { "key": "site-move-with-url-changes", "title": "How to move a site", "url": "https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes", "publisher": "Google Search Central", "kind": "google", "checked": "2026-10-04" } ], "by": "the author", "cite": "[D3-C645, analysis, Ibrahim Anjro]" } ] }