{"slug": "google-rank-data-issues-lighthouse-update-ai-opt-out-seo-pulse", "title": "Google Rank Data Issues, Lighthouse Update & AI Opt-Out – SEO Pulse", "summary": "SE Ranking's review of 10,000 Google US desktop keywords, published Nov. 3, found that 84 percent of flagged rank-tracking anomalies were unrelated listings built around a single word from the query, and 96.5 percent of those unrelated blocks began at position 9 or below. Nozzle, using a different methodology, reported its weekly share of impacted SERPs fell to 1.5 percent in mid-October before rising to 7.6 percent during the week of Oct. 26, while DataForSEO said Google now limits how many goto links from a single results page can be resolved in a given timeframe, cutting its High Priority and Live modes to roughly half of goto URLs. Separately, PageSpeed Insights now runs Lighthouse 13.6.0, whose revised Lantern loading simulation changes lab scores even for unchanged pages, with Google's Barry Pollard saying JavaScript-intensive sites are most likely to be affected.", "body_md": "Welcome to the week’s Pulse: what you need to know about updates that are affecting how much you can rely on rank tracking data, why PageSpeed scores can go up or down on a page that has no changes and what a shared robots.txt control would mean in terms of preferences for AI training.\n\nHere’s what matters for you and your work.\n\n## Rank Data May Carry One-Word Results And Google Redirect URLs\n\nTwo issues in the Google results that rank tracking tools collect can throw off ranking reports. Unrelated listings can crowd a tracked page out of the collected results, and unresolved goto links can hide which page ranked.\n\n**Key facts:**\n\nIn an [SE Ranking review](https://seranking.com/blog/unrelated-google-results-research-study/) of 10,000 Google US desktop keywords published Nov. 3, 84 percent of the flagged cases were unrelated listings about a single word from the query. Of those unrelated blocks, 96.5% began at position 9 or below. A related pattern is tracked by [Nozzle](https://nozzle.io/research/google-plays-dumb/) using a different methodology and it reports its weekly share of impacted SERPs had fallen to 1.5% in mid-October, then rose to 7.6% during the week of Oct. 26. [DataForSEO states](https://dataforseo.com/update/new-goto-url-limits-and-how-this-affects-your-results) Google has implemented a mechanism to restrict the amount of goto links from a single results page that can be resolved over a given timeframe. As such, they state their High Priority and Live modes will now only resolve approximately half of goto URLs. The [status page of Serper](https://serper.betteruptime.com/incident/1108349) lists the limitation of goto URLs as being on Oct. 30, while [SerpApi’s second incident](https://status.serpapi.com/incidents/w29p1wvgcz1b) of goto links replacing direct links, which opened on Nov. 3, still showed as Identified when last reviewed on Nov. 4.\n\n### Why This Matters\n\nCheck if you were dropped at a position of 9 or lower from late September on to see if your replacement URLs are about one word of your query. Also, starting with about Oct. 30 (if it was a Google redirect) compare the URL that your tracker stored versus where the redirect points. To verify which factor caused an issue use Search Console’s impression/clicks reports for the same query, as SE Ranking recommends.\n\n*Read our full coverage: [Rank Trackers Find Google Results About One Word Of A Query](https://www.searchenginejournal.com/rank-trackers-find-google-results-about-one-word-of-a-query/595798/) and [SERP Data Providers Say Google Is Throttling Goto Result Links](https://www.searchenginejournal.com/google-goto-result-links-throttling/595959/)*\n\n## PageSpeed Insights Scores Can Change After A Lighthouse Update\n\nPageSpeed Insights now runs [Lighthouse 13.6.0](https://github.com/GoogleChrome/lighthouse/releases/tag/v13.6.0), which updates the loading simulation used for its lab scores. As a result, your page’s score may change even if you haven’t changed anything on the page.\n\n**Key facts:**\n\nAccording to [a post](https://bsky.app/profile/tunetheweb.com/post/3mzdqpjuns22y) by Google’s Barry Pollard on Bluesky, the updated version of Lighthouse’s simulated FCP (First Contentful Paint) and LCP (Largest Contentful Paint) will be more accurate and will generally provide better results. He also stated that JavaScript-intensive websites would be more likely to experience the impact of this new version. The simulation used as the basis for these predictions, called Lantern, has been modified to use Chrome’s render-blocking label for every individual request made. It then defaults to using the fetch priority value if the render-blocking label cannot be found. In addition, the field data provided in the same report was based upon actual user data collected from the real world, not as part of a synthetic test like Lighthouse.\n\n### Why This Matters\n\nThe pre- and post-switch lab scores aren’t generated in the same simulation; therefore, some of the increase you see on pages you’ve optimized might be from the new version. Make sure each report lists the same Lighthouse version, and compare your field data, before claiming an improvement.\n\n*Read our full coverage: [Google Lighthouse Update Changes How PageSpeed Insights Simulates Loading](https://www.searchenginejournal.com/pagespeed-insights-scores-lighthouse-update/595698/)*\n\n## Google, Microsoft & OpenAI Plan To Honor A Shared AI Training Opt-Out\n\n[Google](https://developers.google.com/search/blog/2026/10/ai-training-control), [Microsoft](https://blogs.bing.com/search/2026/10/your-content-your-choice-clearer-preferences-for-training-and-grounding/), and [OpenAI](https://openai.com/index/helping-websites-express-ai-training-preferences/) announced on Oct. 30 that they plan to honor a shared robots.txt control for AI training preferences, based on an [Internet-Draft](https://datatracker.ietf.org/doc/draft-kelley-aipref-training-preference-signal/) by Anthropic’s Kevin Kelley.\n\n**Key facts:**\n\nThe control is a normal robots.txt group under a policy token called `__usage_ai-training`, that has both Allow & Disallow rules; at this time none of these three organizations support the control, according to their publicly announced timelines. Google’s post states that it plans to treat a shared opt-out as though a site opted out of Google-Extended, when the site does not have Google-Extended defined. In addition, [Google’s crawler documentation](https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers) states that Google-Extended also covers grounding in Gemini Apps. Microsoft will utilize the shared control for training purposes, will introduce a separate page-level AI Grounding preference, and will cease treating NoArchive and NoCache as training and/or grounding preferences after March 1, 2027.\n\n### Why This Matters\n\nA site would be able to use one robots.txt group as replacement for many per-company training rules after the companies read it; however, opting out through that group would not cover the same uses at Google and Microsoft. The documentation provided by Google regarding its robots.txt controls does not separate Gemini training from Gemini Apps’ grounding. Companies using NoArchive and/or NoCache in conjunction with Microsoft have until March 1, 2027 to switch to the new preferences.\n\n*Read our full coverage: [Google, Microsoft & OpenAI Plan To Honor Shared AI Training Opt-Out](https://www.searchenginejournal.com/google-microsoft-openai-shared-ai-training-opt-out/595387/)*\n\n## Mueller Expects Technical SEO To Stay Relevant For AI Search\n\nGoogle’s John Mueller said AI systems “build on SEO” and that he expects technical SEO in particular to stay relevant. He spoke with David Iwanow in an [interview](https://www.youtube.com/watch?v=-ZA5SNV4NjU) posted Oct. 29 from Search Central Deep Dive Europe 2026.\n\n**Key facts:**\n\nMueller also stated that AI systems crawl sites in slightly different ways using intent based on things like training versus getting the latest content; he described this as “another flavor of technical SEO”. When asked about listicle formats Mueller indicated that when tactics are effective they are likely to be mimicked poorly until the algorithms adapt and therefore establishing a solid foundation for a website is your best bet.\n\n### Why This Matters\n\nMueller placed AI crawling within technical SEO, so you can include how AI crawlers request your pages in the technical audits you already run. Just be sure to check each crawler’s access and robots.txt rules individually.\n\n*Read our full coverage: [Google Says Technical SEO Remains Key For AI SEO](https://www.searchenginejournal.com/google-says-technical-seo-remains-key-for-ai-seo/595550/)*\n\n## OpenAI Puts ChatGPT’s Search-Like Queries At A Fifth Of Google’s\n\nChatGPT consumer product lead Adam Fry told [Big Technology](https://www.bigtechnology.com/p/openai-chatgpt-search-is-about-20) that ChatGPT’s “volume of search-like queries is now roughly one-fifth the volume of queries of Google”.\n\n**Key facts:**\n\nFry noted each question that sends ChatGPT to the web is considered a search by ChatGPT’s developer; however, according to the article, there is no Google figure, period or market given for this comparison. [Ahrefs’ referral tracker](https://ahrefs.com/benchmarks/ai-vs-search) measures the source of referrals at the site level and shows Google accounts for 24.74% of tracked traffic across 118,671 sites during October with ChatGPT accounting for 0.36%.\n\n### Why This Matters\n\nOpenAI’s ratio counts questions that send ChatGPT to the web, while referral data tracks visits sent to websites. To keep your channel plan clear, name the measure behind any ChatGPT size figure, because search counts and referral shares describe different things.\n\n*Read our full coverage: [Google’s Search Volume Is About 5x ChatGPT’s, OpenAI Says](https://www.searchenginejournal.com/googles-search-volume-is-about-5x-chatgpts-openai-says/595817/)*\n\n## Theme Of The Week: Check The Method Before The Number\n\nA number of statistics reported by SEO teams this week require an assessment of how these statistics are collected prior to being viewed as information regarding performance for a website or channel. This week’s issue with rank data is the collection of one word results and redirect URLs; a simulated PageSpeed lab score will be affected when using a new simulation versus the previous simulation; and the size of ChatGPT will depend upon if you use search volume or total visits to determine its size. On the other hand, the planned shared opt-out would cover different uses based upon which company reads it; Mueller defined AI crawling, with its different intents, as technical SEO. When reporting changes in metrics or data from reports, this is where you should document which tracking tool or version of a tool was used as well as the criteria used (definition) to produce the report.\n\n**Top Stories Of The Week:**\n\n**More Resources:**\n\n- [How Rank Trackers Say They Handle Suspect Google Results](https://www.searchenginejournal.com/rank-trackers-suspect-google-results/594049/)\n- [Google Explains The Limit Of Robots.txt For AI Content Use](https://www.searchenginejournal.com/google-illyes-robots-txt-crawling-ai-training/593957/)\n- [Google Adds Experimental Soft Navigation Metrics To CrUX](https://www.searchenginejournal.com/google-experimental-soft-navigation-metrics-crux/592820/)\n\n*Featured Image: Cast Of Thousands/Shutterstock*", "url": "https://wpnews.pro/news/google-rank-data-issues-lighthouse-update-ai-opt-out-seo-pulse", "canonical_source": "https://www.searchenginejournal.com/seo-pulse-rank-data-problems-pagespeed-scores-ai-training-opt-out/596104/", "published_at": "2026-11-07 13:00:00+00:00", "updated_at": "2026-11-09 01:51:52.204991+00:00", "lang": "en", "topics": ["ai-search", "generative-engine-optimization"], "entities": ["Google", "SE Ranking", "Nozzle", "DataForSEO", "Serper", "SerpApi", "Lighthouse", "Barry Pollard"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/google-rank-data-issues-lighthouse-update-ai-opt-out-seo-pulse", "markdown": "https://wpnews.pro/news/google-rank-data-issues-lighthouse-update-ai-opt-out-seo-pulse.md", "text": "https://wpnews.pro/news/google-rank-data-issues-lighthouse-update-ai-opt-out-seo-pulse.txt", "jsonld": "https://wpnews.pro/news/google-rank-data-issues-lighthouse-update-ai-opt-out-seo-pulse.jsonld"}}