SEO and AI Search News | Early November 2026
By David Roche | Reviewed 13 November 2026
This edition covers selected developments highlighted in the 1 and 8 November SEOFOMO newsletters, including announcements from 30 October. It is an early-November briefing, rather than a roundup of the whole month.
The main developments concern AI content preferences, agent activity on websites, performance testing and shopping. They raise practical questions: can customers and agents complete useful tasks, are you comparing reports fairly, and do your content controls reflect your intentions?
Here is what changed, who it affects and what is worth doing next.
1 AI content controls are changing with important dates in 2027
Google and Microsoft both announced developments on 30 October. Understanding the purposes involved helps avoid changing the wrong setting.
Training grounding and crawling serve different purposes
Training involves developing a model. Grounding uses information to support an answer when it is generated. Crawling is the process of fetching content. A provider’s controls can cover more than one use, so their exact documentation matters.
Google plans to support a shared training preference
Google says it aims to support a shared robots.txt training control in 2027, based on work from the IETF AI Preferences group. The proposed signal would work across participating providers while existing provider-specific controls continue alongside it.
This is planned support, not a universal control already operating everywhere. Google also describes how the proposal would interact with Google-Extended. That control has implications for grounding in Gemini Apps as well, so avoid treating every provider’s setting as a training-only switch.
Source: Google’s shared AI training control announcement
Microsoft announces separate training and grounding preferences
Microsoft’s new preferences distinguish training from grounding while preserving eligibility for traditional Bing search, subject to ordinary requirements. They begin taking effect on 1 February 2027 as content is crawled. Restricting grounding can reduce AI visibility.
For sites using NoArchive or NoCache, transition steps matter. Those tags stop controlling these uses after 1 March 2027. Maintaining grounding restrictions requires page-level preferences and a temporary choice in Bing Webmaster Tools. Eligible transition settings open on 15 December 2026; temporary protection ends at recrawl or 30 September 2027, whichever comes first.
Allowing content use does not override a crawl block or guarantee inclusion, visits or payment.
Source: Microsoft’s preferences and transition instructions
What website owners should do
Ask whoever manages your website to record its existing crawler and content-use settings, what they are intended to achieve and which provider they affect. If you use Microsoft’s legacy tags, review the transition with that person. Avoid replacing working rules with copied examples from a news summary.
An llms.txt file remains a separate, optional information resource. These announcements do not turn it into a permission file.
Understand crawler access and AI controls
2 Microsoft Clarity adds ways to investigate AI agent activity
On 4 November, Microsoft announced Clarity’s Agentic Analytics, including an Agent Activity dashboard and task simulations. Supported operators include those from Google, OpenAI and Anthropic. Simulations initially cover commerce and travel scenarios.
The announcement also expands Brand Agents for eligible merchants and local businesses. Ask Clarity can investigate behavioural data with session evidence, but the article identifies a closed retail beta. Check the individual feature’s eligibility rather than assume the whole announcement is available in every account.
Source: Microsoft Clarity’s announcement
Why this matters to a business
A mention in an AI answer, a visitor arriving from an assistant and an agent completing a task are different events. A dashboard about agent activity does not measure every AI citation or prove that a sale followed.
Our recommendation is to choose one important task, such as finding delivery information or requesting a booking. If a supported assessment is available, investigate where the task fails and verify the outcome through the relevant business system. Keep the normal human journey working too.
Check whether agents can use your website
Keep AI measurement in context
3 A better PageSpeed score may reflect a changed test
Lighthouse 13.6.0 changes its page-loading simulation, including how it models requests and rendering. This means a laboratory result can change even when the website has not. A higher score alone is insufficient evidence that optimisation work made a site faster.
Source: Lighthouse 13.6.0 release notes
Check the report before claiming an improvement
Record the page, device setting, test date and Lighthouse version when comparing reports. If the version changes, explain that difference. Repeat relevant tests under comparable conditions and check the actual customer task.
PageSpeed Insights separates laboratory data from real-user data. Its field data covers a rolling 28-day period and may represent the page or the wider origin. Some websites have insufficient samples, so field data may be absent. It cannot instantly confirm yesterday’s improvement.
Source: Google’s explanation of PageSpeed Insights data
A useful report might say: “The lab result improved after a change in testing version. We are checking comparable tests and real-user evidence before attributing the difference to our work.” That is an example of reporting language, not a client result.
Build useful audits and reports
4 Google expands AI checkout to eligible Canadian retailers
Google announced a Canadian rollout on 4 November. UCP-powered direct checkout is expanding to AI Mode in Search and the Gemini app, initially involving eligible retailers including lululemon, select Shopify merchants, Shoppers Drug Mart and Simons.
UCP means Universal Commerce Protocol, a standard designed to help systems work together across shopping tasks. Google also says a simplified Merchant Center integration is planned for 2027. That is a future expansion, not a feature every merchant can activate today.
Source: Google Canada’s shopping announcement
What retailers should take from this
Check your own platform, market and account eligibility before planning an integration. The announcement is not a requirement for every shop to commission a protocol project.
Our practical priority remains accurate information: product variants, prices, availability, delivery, returns and purchase conditions. Review your feeds against the visible pages. A more convenient buying route still needs reliable commercial details behind it.
Review product information and ecommerce SEO
5 Google clarifies guidance for user-created and shared pages
Google’s updated spam-prevention guidance explicitly addresses tools that let users publish shared pages, generated outputs or web apps. It asks platforms to consider whether these pages are intended for public search discovery or direct access.
It also recommends monitoring for unexpected growth in published or indexed pages and unrelated search queries. This is particularly relevant to businesses running publishing tools, communities or services that generate public URLs.
Source: Google’s user-generated spam guidance
What owners should check
If visitors can create pages on your website, ask which outputs should be public, searchable or private. Review moderation and unexpected URL growth with the person managing the platform.
For pages that should stay out of search, choose the appropriate indexing control. A robots.txt crawl block is not equivalent to removing an indexed URL, and noindex must be accessible to a crawler to be read. Confidential material needs proper access controls. This technical distinction matters when applying the guidance.
Understand indexing and sitemaps
Choose the action that fits your website
| Your situation | Useful next step |
| You use AI content restrictions | Review provider-specific settings and any applicable 2027 transition. |
| Your site has booking or shopping journeys | Check the relevant Clarity feature and test one commercially important task. |
| You report speed improvements | Record test versions and distinguish laboratory changes from real-user evidence. |
| You sell through an ecommerce platform | Verify market eligibility and reconcile product data before planning integrations. |
| Users generate public pages on your site | Review indexability, access controls and abuse monitoring. |
You do not need to adopt every feature. Select the change relevant to your customers, investigate its practical value and record how you will check the result. Announcements are a reason to review priorities, not a guarantee of rankings or revenue.
Use the complete free SEO checklist
Sources and coverage
This briefing draws on the SEOFOMO editions below, with the main announcements checked against the original sources linked within the article. Reporting cut-off: 8 November 2026. Sources checked: 13 November 2026. Features and transition instructions can change.
