Blog Category: Industry Notes

Google has added a paragraph to its “Creating helpful, reliable, people-first content” page warning site owners against fabricated author identities. It sits in the section on who created the content. Google’s page now shows a last-updated date of October 5, 2026 (UTC), and trade reports place the first appearance of the paragraph around October 1 to 2. Google announced no ranking update alongside it.

This piece sets out what the page says, what is new and what is not, and what the evidence does and does not show about bylines. It is written for teams responsible for search engine optimization and content marketing, and it ends with a short audit you can run on your own author pages.

What Google’s page says now

Read from Google’s documentation, the section on who created the content does three things in sequence. It encourages adding accurate authorship information, such as bylines, where readers might expect it. It tells site owners to avoid deceptive authorship information. And it says that fabricating creator profiles, for example with AI-generated headshots, made-up names or false credentials meant to make content look as if human experts wrote it, is a form of deception.

The consequence is stated plainly. Deception, Google says, “makes a page untrustworthy to both users and our automated quality systems.” The page adds that it is a signal of a low-quality page.

Two things about that wording matter. The target is fabrication: invented people, fake faces and false credentials. And the stated purpose is to make content appear human-expert written, which ties the problem to misleading readers about who is behind the content.

What is new, and what is not

The paragraph itself is new. Search Engine Journal’s Matt G. Southern reported on October 2 that an archived copy of the page from June 8 lacked it. The same revision added a definition of main content and four attributes that Google says its raters assess: effort, originality, talent or skill, and accuracy, with a higher bar for accuracy on topics that affect health, finances, safety or well-being.

The principle is not new. Google’s Search Quality Rater Guidelines already treat deception as grounds for the lowest rating. Section 4.5.3 of the September 11, 2025 edition covers deceptive information about a website or its content creators, and says pages using deception should be rated Lowest. Search Engine Journal adds that those guidelines already named fake creator profiles. Relevant Audience makes the useful point that what changed is where the statement appears: in public documentation aimed at site owners, not only in guidance for raters.

The date, checked at Google’s page

This is where care is needed. The date on Google’s page is the date of the latest revision, not necessarily the date the paragraph was added. Search Engine Journal described a version dated October 1 on October 2, and the page now says October 5, so it has been revised since. SEO consultant Marie Haynes said the change was made on October 2. Search Engine Journal also reported that Google’s documentation updates page did not list the edit, and we did not find an entry for it either.

The safest wording is that the paragraph appeared in early October 2026 and that Google has not published a dated announcement for it.

What it does not say

The guidance leaves several things open, and some readings going around go further than the page does.

It announces no ranking update, no system name and no penalty. It does not explain how Google would detect a fabricated profile. Google’s page also notes that its raters do not control how pages rank, so the rater attributes describe what quality evaluation looks for, not a published ranking formula.

It does not say bylines help you rank. Google’s Search Liaison said in January 2024 that “Just adding a byline doesn’t give a ranking boost.” The new paragraph does not contradict that. It says deception is a risk, not that honest authorship is a lever.

And it is not a ban on AI. The sentence concerns fabricated people presented as human experts. Our reading is that a clearly labeled editorial team, or AI assistance disclosed where readers would wonder, is a different situation from an invented doctor with a generated photo. Google’s page does suggest disclosing automation where readers would reasonably ask how content was made.

Bylines and AI citation: what the evidence shows

It is tempting to treat real authors as a way to win citations in AI answers. The evidence does not support that yet, so we would not frame it that way.

The most direct data we found comes from Discovered Labs, a vendor that sells answer engine services, so read it with that in mind. It tested Perplexity only, using 400 questions and 5,770 pages from Google’s first results page. Pages published by companies were cited more often than pages by individual authors: 39.5% against 27.1%. The study calls the gap an association, not proof of cause. It also classifies a staff byline on a company blog as company content, so it does not test bylines directly. It cites a separate study of 497 Google results across 30 queries that found no measurable effect from bylines and credentials on citation.

That is thin evidence in both directions. What it supports is modest: treat authorship as a trust and risk matter, not as a citation tactic. Real people behind your content protect you from the downside Google has now named, and they help readers judge whether to trust you. They are not a proven way to get cited.

What counts as a fabricated profile

Google’s sentence names three examples. In practice, a team should check for these:

An author who does not exist. A name invented to give content a face, with no real person who wrote, reviewed or answers for it.

A photo that is not the person. An AI-generated headshot or stock image presented as the author.

Credentials that cannot be verified. Titles, years of experience, degrees or licenses that the person does not hold.

A fourth case sits close to the line, and it is our reading, not Google’s. A real expert’s name placed on content they did not write or review. Google’s separate instruction to avoid deceptive authorship information is broader than the fabricated-profile sentence, so this is worth treating as a risk.

A byline audit you can run this week

Start with a list of every author name that appears on your site, including old posts and contributors who have left.

Check that each name belongs to a real person who can confirm they wrote or reviewed the content. If a byline is a pen name, replace it with a transparent label such as your editorial team, and say so.

Check the photo. Use a real photograph of that person, or no photo.

Check the credentials. Every claim should be something the person can document: a license, a publication, a role at a named employer.

Check the author page. Google’s page asks whether bylines lead to further information about the author and the topics they write about. Each byline should link to a page with a real bio, links to their professional profiles and a list of their work. A bio at the end of an article with no link to a profile page leaves that question half answered.

Check sensitive topics. Where content covers health, legal or financial decisions, the accuracy bar is higher. Name the expert reviewer and the review date. Teams in healthcare and legal fields should be the strictest.

Check AI disclosure. Where AI assisted the draft, decide what readers should be told, and make sure a named person is accountable for the final text.

Fix, do not delete by reflex. If an author profile cannot be verified, correct the byline, label it accurately, or have a qualified person review and sign off on the content. Removing posts without a plan can cost you pages that were working.

Why this matters for AI search visibility

AI assistants and answer engines draw on pages that readers and search systems already treat as credible. Our guide to how AI search works explains how a page can be cited without ranking at the top, and why clear answers, specific claims and self-contained sections matter more than decoration. For generative engine optimization, the practical lesson from Google’s change is to build content on accurate, attributable information so that no part of it depends on a fake face. Our full guide to generative engine optimization covers that groundwork.

The same logic applies to answer engine optimization. Answers drawn from your pages carry your name, so the people and claims behind them need to hold up. Our look at why third-party mentions matter in AI search makes a related point: independent credibility is earned, and it is hard to fake.

To see where your brand and its experts are actually mentioned, a free AI Visibility Audit checks real questions across platforms. Our complete guide to the AI Visibility Audit explains the method.

Where this leaves you

The confirmed facts are these. Google’s people-first content page now warns that fabricating creator profiles, such as with AI-generated headshots, made-up names or false credentials, is a form of deception that makes a page untrustworthy to users and automated quality systems. The page shows a last-updated date of October 5, 2026, and trade reports place the paragraph’s first appearance at October 1 to 2. Google announced no ranking update, penalty or detection method, and the page does not say bylines improve rankings.

The practical response is an audit, not a rewrite. Make sure every byline is a real person, every photo is that person, every credential can be verified and every author has a page that proves it. Whether the aim is generative engine optimization, answer engine optimization or plain search engine optimization, treat that as a baseline for trust, not as a trick.

Frequently Asked Questions

1. What did Google add to its people-first content guidance?
A paragraph in the section on who created the content saying that fabricating creator profiles, such as with AI-generated headshots, made-up names or false credentials to appear expert, is a form of deception.

2. When did Google add it?
Google’s page shows a last-updated date of October 5, 2026, which is the latest revision. Trade reports place the first appearance of the paragraph around October 1 to 2. Google has not published a dated announcement for it.

3. Is this a ranking update?
Nothing announced says so. Google named no update, system, penalty or detection method. The wording describes what quality evaluation looks for.

4. Do author bylines improve rankings?
Google’s Search Liaison said in January 2024 that adding a byline does not give a ranking boost. Google’s page encourages accurate bylines for readers, but does not call them a ranking factor.

5. Does this ban AI-generated content or AI headshots?
No. The sentence concerns fabricated profiles presented to make content seem expert-written. Google’s page does suggest disclosing automation where readers would wonder how content was made.

6. Will real authors help me get cited in AI answers?
There is no solid evidence that they do. One vendor study of Perplexity found company pages cited more often than individual-author pages, and a second study it cites reported no measurable byline effect. Treat authorship as trust, not a citation tactic.

7. What should I do first?
List every author on your site, confirm each is a real person with a real photo and verifiable credentials, and make sure each byline links to a genuine author page.

If you want to know how your brand and its experts appear across Google and AI answer engines today, that is exactly what we look at in a free AI Visibility Audit.

On October 8, 2026, Google Cloud introduced the Gemini agent, a general-purpose agent for work, at its Gemini at Work event. The announcement, published as a post by Google Cloud CEO Thomas Kurian, makes a specific pitch: an agent with its own account, its own audit trail and a budget cap that pauses it. For anyone responsible for AI governance, that is a notable shift, because controls that used to be added afterward are now described as part of the product.

This is a vendor announcement. Google’s claims have not been independently tested, and the post gives no general availability date, eligibility rules or agent pricing. This piece sets out what was announced, what is not established, and the question it raises: the features are Google’s, but who owns the policy behind them? It follows our earlier look at CrowdStrike’s shadow AI agent product and is written for teams doing AI agent development or generative AI development, and for those adopting agents from vendors.

What Google announced

According to the Google Cloud post, the Gemini agent plans tasks, uses tools, connects to a company’s business systems and returns finished work in the documents and inboxes people already use. The governance claims fall into four groups.

Identity. Google says coworker agents have dedicated identities, including their own email addresses on a company domain, and see only the context a person or team gives them. In Workspace, an agent gets its own account with an email address, a calendar, a Drive and a place in the company directory. Google also says each identity is cryptographically attested and limited to least-privilege permissions.

Audit trail. Google says every action the agent takes is written to an audit trail and “attributed to the agent rather than to a person.” The identity is stamped into the logs, and the logs can be watched in real time.

Spend caps. Administrators can set a hard limit on a project’s AI spend in the Cloud Billing Console. The project’s agent pauses when the cap is triggered, and work resumes with one click. Spend is tracked per project, so costs can be charged back to departments.

Policy and security. Rules are written once and apply to every agent, such as barring agents from documents classified as need to know. The post frames governance as four questions: who the agent is, what it is allowed to do, what it did and where you can see it, and what it should never touch.

Identity: an account is not an owner

A separate account solves a real problem. When an agent works through an employee’s login, its actions look like that employee’s, and revoking one disrupts the other. A separate identity lets security teams grant narrower access and switch the agent off without touching a person’s account. Analyst firm Futurum credits the design with giving security teams a clear line between human and agent actions.

What an account does not provide is an accountable owner: it does not say which person approved the agent’s permissions or answers when it gets something wrong. Google says an agent sees only what people share with it, which means someone is sharing, and that decision belongs to you. Our guide to AI agent governance puts inventory and scope of authority at the start of its framework for this reason.

The audit trail, and what it leaves open

An action-level log helps reconstruct what happened, and attributing entries to the agent keeps human and automated activity apart. It also raises a question the post does not address: how does a reviewer link an agent’s action back to the request, and the person, that set it off? That is our inference, not a gap Google has acknowledged.

A log only helps if someone reads it. A September survey published by Guild.ai, a vendor of agent management tools, and fielded by Morning Consult, reported that 39.8% have logging or audit trails and 31% have an automated kill switch. The release does not state the base for those figures and the research is vendor-sponsored, so treat them as indicative only.

Spend caps: useful, but thinly described

The post gives no time period, no alert thresholds and no figure for how quickly a cap takes effect. An earlier Google Cloud post on billing for agents, dated August 26, 2026, describes a firm monthly project cap, alerts at 50%, 80% and 100% of budget, and an optional overage setting. The October post does not say whether the same settings apply to the Gemini agent, so do not assume they do.

Two limits follow from how a cap works, and both are our reading. The cap sits at the project level, so one runaway agent could pause others sharing the project. And a cap limits cost, not harm: an agent can send a wrong message or delete a file at almost no cost, so caps sit beside permissions and approvals, not in place of them.

What independent voices say

Coverage so far is analysis of the announcement, not testing. Carmi Levy, an independent analyst quoted by CIO on October 8, said Google is trying to become “the gatekeeper of the new enterprise operating system.” He called Google arguably ahead on identity and audit trails, but questioned whether CIOs and CISOs can trust it with mission-critical processes.

Mahmoud Ramin of Info-Tech Research Group, quoted in the same article, said the announcement does not create a new category, and called enforcing governance non-negotiable.

Futurum, in an October 9 analysis, noted that Google says it does not intend to charge a per-seat license for coworker agents in Workspace, but has not said how it will meter agent activity.

What is and is not confirmed about availability

Google’s product page says “Not every feature shown on this page is available right now.” It lists delegating multi-step background tasks, mobile and desktop access, and third-party model choice as early access.

The Kurian post gives no general availability date, eligibility criteria or agent-specific price. It labels the Financial Services and Legal specializations as in preview, with Government, Healthcare and Retail coming soon. It does not label the core agent, coworker agents or spend caps as preview or generally available, so their status is unconfirmed. Futurum makes the same point: Google gave few general availability dates.

Reworked reports that a Google spokesperson told VentureBeat the agent comes at no additional charge where Gemini Enterprise is available. We did not find that in Google’s own posts, so treat it as reported.

Who owns the policy behind the controls

Google has built mechanisms: an identity, a log, a cap and a place to write rules. None of them decides anything. Someone still has to choose which agents may exist, which data counts as need to know, what each budget should be and who reviews the logs.

This is the point our CrowdStrike piece made about detection tools. A product can enforce a policy, but it cannot write one.

There is also a coverage problem. Google’s controls cover Google’s agent, while agents from Salesforce, Microsoft and others bring their own identities, logs and caps. Shared protocols help agents talk to one another, but as we noted in our look at MCP and A2A governance, they do not settle who is responsible. That belongs to a policy that sits above any one vendor.

Is your agent governance ready? A checklist

Use Google’s four questions as a test, whichever platform you run.

Who is the agent? Keep a register in which every agent has a named owner, a purpose and an identity of its own, not a shared login or a personal account.

What can it do? Grant the narrowest access that lets it do the job, name the data it must not open, and review access on a schedule.

What did it do? Retain logs long enough to reconstruct an incident, assign someone to review them, and record who requested each task.

What should it never touch? Write a short list covering regulated data, payments, deletion and external sending, then test that the controls block those actions.

Set a budget for each agent or project, and decide who is alerted and who may resume work. Rehearse the stop by timing how fast you can disable an agent and revoke its credentials. A short AI Readiness Audit can show which of these controls you already have.

What this means if you build or buy agents

For teams doing AI agent development, identity, scoped permissions, logging and spend limits belong in the requirements from the first sprint, because they are cheaper to design in than to add later. Teams working on generative AI development can use the four questions as a design review before an agent reaches production.

For AI automation that connects agents to CRM and finance systems, start with read-only access and add actions as controls prove themselves. Wider AI development programs should treat agents as production systems with an owner and a review schedule. Google’s preview focus on financial services and legal is a signal too: finance and banking and law firms should apply the strictest version of these questions.

Where this leaves you

The confirmed facts are these. On October 8, 2026, Google Cloud introduced the Gemini agent and said its agents have their own identities, including email, that every action is written to an audit trail attributed to the agent, and that project-level spend caps pause the agent when triggered. This is a vendor announcement that has not been independently tested. Google’s post gives no general availability date, eligibility rules or agent pricing, and some related features are in early access or preview.

The practical response does not depend on any one vendor. Treat identity, logging and caps as tools, and AI governance as the policy that tells them what to enforce. Decide who owns each agent, what it may touch, what it may spend and who reviews its record. That discipline supports AI automation and AI development alike, so write it down before the platform asks for it.

Frequently Asked Questions

1. What did Google announce on October 8, 2026?
Google Cloud introduced the Gemini agent in a post by CEO Thomas Kurian. Its governance claims include agent identities with email addresses, an audit trail attributed to the agent, and project-level spend caps.

2. Does the Gemini agent really get its own email address?
Google says so. In Workspace, a coworker agent gets its own account with an email address, calendar and Drive. It is a vendor claim, with no availability date given.

3. What does the audit trail record?
Google says every action is written to an audit trail attributed to the agent, not a person. The post does not describe log retention or how an action links back to the requester.

4. How do the spend caps work?
An administrator sets a hard limit on a project’s AI spend in the Cloud Billing Console, and the project’s agent pauses when it is triggered. The post gives no time period, thresholds or enforcement speed.

5. Is the Gemini agent available to everyone?
Not as far as Google’s pages show. The post gives no general availability date or eligibility rules, some capabilities are in early access, and some industry versions are in preview.

6. If I use Google’s agent, is my AI governance solved?
No. The platform supplies identity, logging and caps, but you still decide which agents exist, what they may access, what they may spend and who reviews their activity.

7. What should my company do first?
Answer Google’s four questions for every agent you run, name an owner for each, and write the policy before relying on any vendor’s controls.

If you want to know which of your workflows are ready for AI agents, and where the governance gaps sit, that is exactly what we look at in a free AI Readiness Audit.

Every marketer working on AI visibility has the same suspicion: if AI assistants lean on third-party sources, the shortest route to a mention is to create those sources. A policy update from Anthropic, the company behind Claude, puts a line through part of that idea. Announced on October 8, 2026 and effective November 12, it prohibits using Anthropic’s products to seed the sources AI systems draw answers from with content that misrepresents who is behind it.

The wording is narrower than some headlines suggest, and the policy binds users of Anthropic’s products, not the web at large. This piece sets out what the text says, what it does not say, and the practical test it offers brands deciding between earned mentions and planted ones. It is written for teams planning generative engine optimization and digital PR programs.

What the policy says

The change sits in a new section of Anthropic’s usage policy on deceptive campaigns and artificial activity. Read from the policy page, it prohibits using Anthropic’s products to create fake personas, accounts, media outlets or organizations, or to impersonate real ones. It prohibits hiding the sponsorship of content meant to influence opinion or decision-makers, and spreading content through networks of fake or ostensibly independent sites that share a common source. It also covers building tools for deceptive campaigns and marketing any of these activities.

The clause that matters here prohibits manipulating the sources from which search engines or AI systems draw answers, by “seeding them with content that misrepresents its origin, authorship, or independence.” The policy’s own example is a network of sites posing as unaffiliated sources that corroborate the same claims.

Notice what triggers the rule. It is not seeding, volume or the use of AI. It is misrepresentation: content that hides its origin, its author or its lack of independence.

Who it binds, and who it does not

The policy applies to anyone who submits inputs to Anthropic’s products. That covers individuals using Claude.ai or Claude Code, businesses using the API, customers who reach Claude through cloud providers or resellers, and end users of products built on Claude. A marketing tool built on Claude puts its own users under the same rules, as Relevant Audience points out.

It does not bind search engines, other AI companies or the open web, and it does not govern how Claude ranks or cites content. Mike King of the GEO consultancy iPullRank makes the same point in his analysis: the policy is about how people use Claude.

Enforcement works against the account, not the website. Anthropic’s Safeguards Team monitors for violations, and if one is suspected Anthropic may warn, throttle, limit, suspend or terminate access to its products. That differs from Google’s spam policies, which act on sites.

A new rule, or a clearer one?

Search Engine Journal reads the update as a clarification, not a brand-new ban. The 2025 policy did not mention search engines or AI answers, but Anthropic says it already prohibited fake-account networks and fake news sites, spread across other sections. The new text states the principle directly and applies it to the sources AI draws on.

Search Engine Journal also describes the case Anthropic linked to the section. According to that report, Anthropic found a network of around 70 sites posing as independent local news outlets, tied to a France-based advertising agency. The network used Claude to produce articles designed to “boost their site’s authority rankings on search engines.” It published at least 8,913 articles in about 20 languages, though most got little engagement. Anthropic removed the account and banned the organization.

Two cautions apply. The coverage does not say whether those sites improved their rankings or appeared in AI answers, so the case shows the tactic being attempted, not working. And Search Engine Journal does not link the full text of Anthropic’s report, so its details rest on that outlet’s summary.

Where the line sits

Relevant Audience reads the clause as aimed at deception about who is behind content, not at producing content for AI visibility. In its reading, the policy does not ban using Claude to write content, structure pages for AI answers or publish at volume. That is the publication’s interpretation of the text, which Anthropic has not spelled out for edge cases. For example, Anthropic has not said how it would treat several openly branded sites run by one company, and the policy text points to misrepresented independence as the trigger.

Read together, the sources suggest a useful test, which Relevant Audience frames as its own and not Anthropic’s: would the tactic still work if every reader knew who wrote the content and who paid for it? King puts a similar idea in terms of durability, arguing that manufactured independence has “an expiration date.”

Earned versus planted mentions

That test separates two things that can look alike from outside.

An earned mention exists because someone independent chose to write it. A journalist cites your original research. An expert quotes you. A customer reviews your product. A publisher runs a contributed article under a real byline. A sponsored placement is labeled as sponsored.

A planted mention only looks independent. A network of sites that recommend the same brand while hiding common ownership. Reviews from fake personas. Undisclosed paid listicles. Forum answers posted by accounts that conceal their affiliation. iPullRank, which sells GEO services and so has an interest in the framing, lists these among the tactics to avoid. The policy text itself names fake personas, hidden sponsorship and networks of ostensibly independent sites.

This is the distinction our earlier piece on why third-party mentions matter for AI search turns on. The reason independent sources carry weight in AI answers is that they are independent. Faking independence takes away the thing that made the mention valuable, and it now carries account-level risk for anyone doing it with Claude.

What to do before November 12

None of this requires a strategy rewrite. It asks for a short audit.

Check your own content network. If you or an agency have used Claude to produce content for several sites that appear independent but share an owner or a sponsor, review it now. Search Engine Journal suggests this audit.

Ask vendors direct questions. Relevant Audience recommends asking agencies and tools how they build AI visibility and whether any sites in their plans are owned by them without saying so. A vague answer is information.

Label sponsorship. Where a placement is paid, say so on the page. Where a comparison page is brand-owned, make that obvious.

Use real bylines and real experts. Contributed content should carry the name of the person who wrote it and a verifiable role.

Fund the earned route. Original data, expert commentary and useful tools give journalists and publishers a reason to cite you. That is the work behind digital PR and ethical link building, and the slower route is the durable one.

Measure what you earn. Track whether your brand is mentioned and cited across AI platforms, and which sources drive the mentions. A free AI Visibility Audit does this across platforms and shows where earned coverage is missing.

What this does not tell you

The policy is not evidence that seeding works, or that it fails. The reporting does not show whether the network Anthropic banned gained rankings or appeared in AI answers.

It does not describe how detection works beyond general monitoring, and it does not cover other AI companies. ChatGPT, Gemini and Perplexity have their own terms, and Google has its own spam policies. Do not read this one document as a rule for all of GEO.

It also does not tell you that AI-written content is off limits. The text turns on misrepresentation, though edge cases remain untested. If you use AI tools to draft, the safe course is the same as it has always been: a real author, accurate claims and no pretense about who is speaking.

Why this matters for AI search visibility

AI assistants increasingly shape which brands get recommended, so the temptation to manufacture sources will not disappear. What this update does is move one major provider’s rules in the opposite direction, and mark provenance as the thing platforms are watching. For answer engine optimization, the safest assets are the ones that can survive scrutiny: clear answers, original information, real authors and accurate facts. Our full guide to optimizing for AI search covers that groundwork, and sound search engine optimization supports all of it.

Where this leaves you

The confirmed facts are these. Anthropic announced an updated usage policy on October 8, 2026, effective November 12. A new section prohibits using its products to seed the sources search engines and AI systems draw answers from with content that misrepresents its origin, authorship or independence. Enforcement is against accounts. The policy binds users of Anthropic’s products, not other companies or the open web.

The practical response is to build mentions that would still work if everyone knew who was behind them. That favors original research, real experts, labeled sponsorship and honest digital PR and link building, backed by measurement of what AI platforms actually say about you. Whether the aim is generative engine optimization, answer engine optimization or plain search engine optimization, the same provenance rules apply.

Frequently Asked Questions

1. What did Anthropic’s updated usage policy change?
It added a section on deceptive campaigns and artificial activity, which prohibits using Anthropic’s products to seed the sources search engines and AI systems draw answers from with content that misrepresents its origin, authorship or independence. It takes effect November 12, 2026.

2. Does it ban GEO?
No. The trigger is misrepresentation, not optimization. Writing clear content, structuring pages for AI answers and earning mentions are not what the clause describes, though Anthropic has not addressed every edge case.

3. Who does the policy apply to?
Anyone who submits inputs to Anthropic’s products, including individuals, API developers, customers using Claude through cloud providers and end users of products built on Claude. It does not bind search engines or other AI companies.

4. What happens if someone violates it?
Anthropic may warn, throttle, limit, suspend or terminate access to its products. In the case Search Engine Journal describes, Anthropic removed the account and banned the organization.

5. Is it a new rule?
Search Engine Journal reads it as a clarification. Anthropic says fake-account networks and fake news sites were already prohibited under other sections, and the update names the search and AI answer context directly.

6. How do I tell an earned mention from a planted one?
Ask whether the tactic would still work if readers knew who wrote and paid for the content. Independent coverage, real reviews, labeled sponsorships and bylined expert content pass. Fake personas, hidden-owner site networks and undisclosed paid listicles do not.

7. What should I do before November 12?
Audit any Claude-made content running across sites that appear independent, ask agencies and tools how they build AI visibility, label sponsored content and use real bylines. Then measure your actual mentions across AI platforms.

If you want to know where your brand is mentioned and cited across Google and AI answer engines today, and which sources are driving it, that is exactly what we look at in a free AI Visibility Audit

Picture a Monday morning report. Your rank tracker says a key page has fallen out of the top 10, and the pages that replaced it look unrelated. The usual reaction is to start rewriting. A new question belongs first: did the ranking change, or did the tool receive the wrong results page?

On October 10, 2026, the rank-tracking company Nozzle published research claiming that since September, Google has been returning complete, normal-looking results pages to its rank trackers with the real results swapped out. Nozzle sells rank tracking, and Google has not commented. This piece sets out what was reported, what is and is not established, and how to check before you react. It is written for teams responsible for search engine optimization reporting.

What Nozzle reported

Nozzle’s page analyzes 27.5 million search results pages from its customer datasets, collected between August 20 and October 9, 2026, across 49 countries, desktop and mobile.

From August 20 to September 9, about 0.17% of pages were poisoned, which is Nozzle’s baseline. On September 13, requests to Google began failing in large numbers. The first poisoned pages appeared on September 20. They peaked at roughly a quarter of all pages between September 27 and 29, at 24.9%, 26.7% and 27.0%. Since October 1, daily rates have run at about 4% to 11%. Across the period since September 13, Nozzle puts it at 8.0%.

The word poisoned matters. Google does not refuse these requests, according to Nozzle. It answers with a full page of wrong results. Nozzle puts it this way: “A poisoned request succeeds.” There is no error, no captcha and no change in the page template, so the only way to spot it is to compare a keyword’s results over time.

How it was measured, and a caution about the 8.0%

A keyword’s usual sites are those in the top 10 on at least 60% of its baseline pages. A page counts as poisoned when fewer than half of them appear on any page of the results, and they return later. Those thresholds are the study’s own choices.

Several limits apply. Detection is inferred from each keyword’s history, not from a signal Google has confirmed. The sample comes from Nozzle’s own customers, and the last few days are still filling in. And the headline 8.0% does not state its denominator: the daily table is labeled “All SERPs,” while the country and industry tables calculate against judged pages. Cite it as “Nozzle reports about 8%,” not as a measured rate of Google behavior.

What a poisoned page looks like

Nozzle reports these patterns on poisoned pages, compared with its baseline.

Organic results kept only 20.7% of the previous page’s sites, against 88.5% at baseline. A tracked project’s own site fell out of the top 10 on 58.6% of poisoned pages, against 2.7% at baseline. Reddit rose from 20.8% to 28.8% of top-10 appearances, and Facebook from 28.3% to 33.8%. An AI Overview appeared on 34.9% of poisoned pages, against 54.2%. Ads and shopping results were largely stable.

One example shows how complete the swap can be. For the desktop, US search “white label local seo,” all nine page-one sites on October 4 were the usual vendors. On October 7, all nine had been replaced by unrelated results, including a WordPress tool, a steakhouse and government sites.

The effect is usually brief. About 80% of poisoned spells lasted a single page, and 77.9% of poisoned pages had their usual sites back within three days. A real ranking change persists, which is how the two can be told apart.

Where it appears to hit hardest

Nozzle’s tables show wide variation. Since September 13, the poisoned share was 8.5% in the United States, 10.5% in Canada and 11.5% in Australia, with the United Kingdom lowest at 3.0%. Treat country figures as indications, since they depend on Nozzle’s sample sizes.

“Near me” searches were poisoned more often (11.4%) than other queries (7.8%), and navigational brand searches least often (5.3%). If you manage local SEO reporting, that is worth knowing.

By industry in the US, legal was highest at 15.9%, peaking at 51.3% on September 27. Pets was lowest at 4.3%. Firms in the legal sector should be the most careful about reacting to a single day.

The tools matter too. On the same days, one collection route returned 1% to 7% poisoned pages while another returned 9% to 30%, so how your vendor collects data affects what it sees.

A second vendor, and a reporter’s concern

Nozzle is not alone. DemandSphere, another rank-tracking company, posted on October 7 that Google returns spurious results when it suspects bot traffic, affecting about 11% of its daily results pages. PPC Land reported the figure on October 13. DemandSphere’s post does not describe a method or sample size. Both figures are vendor-reported and unaudited, and they agree on the mechanism and rough scale, little more.

Barry Schwartz of Search Engine Roundtable reported on October 12 that third-party rank tracking is returning incomplete or inaccurate data. He relayed the three tactics that Nozzle’s Derek Perkins described: wide IP blocking aimed at large residential proxy networks, a big increase in captchas, and injecting bad data into suspect pages. Schwartz singled out the third: “The third approach, injecting bad data, concerns me the most.” His reasoning is that tools may not notice it, so they can appear to work while their data is wrong. Several vendors, including Sistrix, SE Ranking and DataForSEO, reportedly posted notices about data problems.

What is not established

Google has not publicly commented on Nozzle’s or DemandSphere’s figures or on the September changes. Everything about motive comes from vendors and the trade press.

Nozzle reads the pattern as Google’s response to bulk collection of its results for AI grounding, which rank tracking resembles. DemandSphere’s founder makes a similar argument. Schwartz’s view, as reported, is that Google is aiming at AI bots and scraping services, not SEO tools. Roger Montti of Search Engine Journal adds that altered pages could also confuse spammers reverse-engineering rankings, a point Nozzle did not raise. None of these readings is confirmed.

There is also a confound. Google’s September 2026 spam update ran from September 24 to October 8, according to PPC Land and Looploop, so real ranking volatility and altered data overlapped in the same weeks. Our earlier piece on the September spam update covers the real-volatility side. A single dashboard showing a drop in that window could not tell the two apart.

Even first-party data can lag. Looploop reports that the Search Console Performance report ran more than 64 hours behind on October 11, so check the date range first.

How to tell a real drop from a poisoned page

Start with Search Console. If it still shows impressions and clicks for the same queries and dates, the site very likely did not drop. Confirm that its data is current first.

Compare against history. Look at the keyword’s usual top 10 over several weeks, not just yesterday, because yesterday may also have been poisoned.

Wait one to three days. Most altered pages clear quickly, while a real change persists.

Read the shape of the page. Nozzle says fewer AI Overviews, fewer “People also search for” modules, more image packs and social or forum sites, and shorter pagination are suggestive, but none is reliable alone.

Cross-check tools. A drop that only one tool reports is a question, not a conclusion.

Ask your vendor how it detects swapped pages and what its error rates are. Relevant Audience, citing PPC Land, reports that most do not yet publish comparable figures.

Hold off on changes. Do not rewrite pages from one chart. Our guide to reading your own traffic before you change anything sets out a three-step method that works here too.

What to change in your reporting

Make first-party data the reference. Search Console, analytics and conversions should anchor the monthly report, with the rank tracker used for trends. Our look at Google’s AI visibility reports in Search Console explains what that data does and does not include.

Set a rule for alerts. A drop seen on one day, in one tool, should trigger a check, not a client email. Require it to persist, or to appear in Search Console, before it is reported as a ranking loss.

Annotate your dashboards. Mark September 13 to October 9 as a period of suspected data problems, so later readers do not mistake a poisoned dip for a penalty.

Why this matters for AI search visibility

Nozzle’s data shows AI Overviews appearing less often on poisoned pages (34.9% against 54.2%). Any measurement that infers AI visibility from collected Google pages may pick up the same noise. That is our inference, not Nozzle’s finding, and tools that measure AI answers by other methods may behave differently.

The practical response is to avoid relying on one source. Generative engine optimization and answer engine optimization are about being cited and recommended in AI answers, and measuring that well means testing real buyer questions across several platforms, not reading a single scraped page. Keep the basics of generative engine optimization and answer engine optimization strong: clear answers, accurate information and consistent entities. Our complete guide to the AI Visibility Audit explains how that cross-platform measurement works. Strong search engine optimization remains the base for all of it.

Where this leaves you

The confirmed facts are these. Nozzle published research on October 10, 2026, covering 27.5 million results pages, and reports that since September 13 about 8.0% were poisoned, against 0.17% at baseline, with a peak near 27% in late September. DemandSphere reports about 11% on its own data. Google has not commented, the mechanism is Nozzle’s account, the motive is interpretation, and both figures come from vendors who sell rank tracking.

The lasting lesson is about method. A rank tracker is a sample of what Google returned to a tool, not a record of what your customers saw. Before reacting to a drop, check Search Console, compare with history, wait a few days and look at more than one source.

Frequently Asked Questions

1. What did Nozzle report about Google and rank trackers?
On October 10, 2026, Nozzle reported that since September, Google has returned complete, normal-looking results pages to rank trackers with the real results swapped out. It measured 8.0% of 27.5 million pages as poisoned since September 13, against 0.17% at baseline.

2. Has Google confirmed this?
No. Google has not publicly commented on Nozzle’s or DemandSphere’s figures or on the September changes. The explanations come from vendors and trade press.

3. Can I trust the 8.0% figure?
Treat it as Nozzle’s reported estimate. It is from a rank-tracking vendor and inferred from keyword history.

4. How do I know whether my ranking drop is real?
Check Search Console for the same queries and dates, compare with several weeks of history, and wait one to three days. Altered pages usually clear within days, while a real ranking change persists.

5. Does this affect Search Console data?
Nozzle’s study concerns data collected from Google results pages, not Search Console. Search Console can lag, though, so confirm the date range first.

6. Does this change how I should track AI visibility?
Tools that infer AI visibility from collected Google pages may pick up the same noise, which is our inference. Testing real buyer questions across several AI platforms does not depend on one scraped page.

7. Should I stop using my rank tracker?
No. Use it for trends, and confirm important changes in Search Console and analytics. Ask your vendor how it detects swapped pages and what its error rates are.

If you want to know how your brand appears across Google and AI answer engines, measured from real answers and not a single dashboard, that is exactly what we look at in a free AI Visibility Audit.

For most of the last two decades, a search choice screen was a way of picking between conventional search engines. A proposal from the UK’s Competition and Markets Authority (CMA) would change that. It would put AI assistants such as ChatGPT and Perplexity on the screens Google shows UK users, and it would attach a condition: any provider listed must fairly attribute the publisher content it uses.

This is a proposal, not a rule, and it applies to the UK only. But it shows a regulator treating AI assistants as search alternatives, and source attribution as a formal requirement. This piece sets out what the CMA proposed, how it would work, what is undecided and what teams responsible for AI visibility should watch.

What the CMA proposed

On September 23, 2026, the CMA published strengthened proposals to give UK users of Google’s Android and Chrome products greater choice and more control over their search services. The CMA says it listened to publishers, search providers and consumer groups, and that the update responds to services such as ChatGPT and Perplexity.

The core elements are these. Google would show Android and Chrome users a choice of search services when they first use an Android phone or open Chrome. Users would be prompted again every year to choose their default. AI assistants could be included on the choice screens if they meet the relevant criteria, including technical and security requirements. And search providers on the screens would have to fairly attribute publisher content when it is used, so that people can easily reach the original sources.

Sarah Cardell, the CMA’s Chief Executive, said the CMA is “responding quickly to the rise of AI assistants”, which people increasingly use as search services but which do not appear on Google’s choice screens today.

The consultation closed at 5pm on October 9, 2026. The CMA expects to make its final decision on this requirement by the end of 2026.

Where this sits in the CMA’s wider approach

Google was designated as having strategic market status in general search and search advertising in October 2025, which lets the CMA set conduct requirements for it. According to the CMA, it imposed publisher controls on June 3, 2026, and fair ranking and data portability requirements on June 17. The user choice requirement is the one still being decided, an updated version of a January 2026 proposal.

How a choice screen would work

The press release gives the outline. The CMA’s consultation document, which runs to 71 pages according to PPC Land, holds the detail. We could not open that PDF, so the following comes from two independent analyses of it, by the trade publication PPC Land and by the law firm Bratby Law, which agree on the main points.

According to those analyses, the screen would list up to 12 providers. If more than 12 qualify, Google would be expected to show the five most popular plus seven chosen at random. Providers would appear in random order, and users would have to scroll the whole list before confirming. Users could trial a provider for at least a week. The screen would be unskippable on new Android devices and fresh Chrome installs, and a skippable reminder would bring it back at least once a year.

These details come from analysis of a proposal that may change, so treat them as the current draft.

How an AI assistant could qualify

The CMA says AI assistants “could in theory be able to be listed”, a phrase quoted by Bratby Law from the consultation document. Nothing guarantees a place. Per those analyses, a service would have to meet three criteria.

First, it must adequately address the full range of use cases of a general search service. The CMA’s notes describe four types of query: navigational, transactional, simple informational and more complex informational.

Second, it must provide a functioning general search experience. That covers technical operation, compatibility with Android, minimum security requirements and credible plans to operate sustainably.

Third, a significant proportion of its UK users must consider it a general search service. The notes say this means a meaningful proportion, not a majority.

A service does not need its own web index. A syndicated index is acceptable.

Who decides matters too. Under the proposal, Google, not the CMA, would run the eligibility process every six months, deciding within two months and sending written reasons for any rejection to the applicant and the CMA. Bratby Law notes that the draft contains no appeal route to the CMA against those decisions, and that the written reasons are the main check. That is one lawyer’s reading of a draft.

The condition for publishers

The attribution condition is the part most relevant to anyone who creates content. Per the CMA, search providers on the choice screens would have to fairly attribute publisher content when it is used, so people can easily access the source. In the analyses of the consultation document, any generative AI summary would have to attribute web content clearly and accurately, with a clear route to the source, and each provider could choose how to do it.

Three points deserve care.

The condition is a requirement of being listed on the screen, not a general rule for all AI products. Because the CMA can impose requirements only on Google, it works as a condition of access to Google’s distribution. Bratby Law argues that it therefore becomes a de facto standard for any rival that wants a place, though that is the author’s view.

The condition does not, in anything we reviewed, require payment to publishers or guarantee any amount of traffic. It concerns attribution and a way to reach the source.

How it would be enforced, and how fairness or accuracy would be judged, are not set out in the press release. Watch the final text.

What is not decided

A lot remains open. The requirement has not been imposed, and the criteria, slots, attribution wording and timing could all change after consultation responses. Google has not commented, according to press reports.

Timing is also uncertain. The final decision is expected by the end of 2026. According to PPC Land’s reading, some obligations would start about a month after the requirement is imposed, and the rest within six months, so screens showing AI assistants may not reach UK users until some time after that. Do not plan around a date.

Geography matters too. This is UK law, covering UK users of Android and Chrome. It changes nothing for users in the United States, so for mainly American clients it is a signal to watch, not a task for this quarter.

Why teams working on AI visibility should watch it

There are three reasons.

AI assistants are being treated as search. The CMA describes them as increasingly used as search services and wants them offered as alternatives. For anyone working on generative engine optimization, that confirms what many teams assume: visibility in AI answers is becoming part of search visibility, in the eyes of regulators as well as users.

Attribution is becoming a formal concept. If a regulator makes fair attribution a condition for AI assistants to reach users, it normalizes the idea that answers should point back to sources. That could affect how assistants display citations over time, but it is a possibility, and we found no evidence yet of any change.

Distribution could shift. If more UK users chose an assistant, more searches might begin there, which would raise the importance of answer engine optimization, being cited and recommended in AI answers. That is a scenario. The proposal does not say how many people would pick an assistant.

None of this reduces the value of traditional search engine optimization. The sensible view is that search is widening, not being replaced.

What to do now

You do not need to change strategy because of a consultation. A few low-cost steps keep you ready.

Measure AI referrals now. Check your analytics for traffic from ChatGPT, Perplexity, Gemini and other assistants, and note how it changes. A baseline lets you see any shift later, whatever the cause.

Make attribution easy. Use clear titles, visible authorship and dates, stable canonical URLs and descriptive headings, so any assistant that wants to credit you can do so accurately.

Check how you are cited. Run real customer questions in several assistants and record whether your brand and pages appear and are attributed correctly. A free AI Visibility Audit does this across platforms.

Keep your source pages strong. Pages that answer a specific question clearly and carry original information are the likeliest to be cited, which is the same work that supports search engine optimization and generative engine optimization.

For UK clients, set a review date. Look again when the CMA publishes its decision, and read the final attribution wording before advising anyone.

Where this leaves you

The confirmed facts are these. On September 23, 2026, the CMA proposed that Google show Android and Chrome users in the UK a choice of search services at first use and prompt them annually. AI assistants could be listed if they meet the criteria, and providers listed would have to fairly attribute publisher content. The consultation closed on October 9, and a final decision is expected by the end of 2026. It is a proposal for the UK only.

The lasting lesson is about direction. Regulators are beginning to treat AI assistants as search services, and attribution as something that can be required, which matters for answer engine optimization planning. For teams reviewing how a brand appears in AI answers, that is a reason to measure now and watch the final wording.

Frequently Asked Questions

1. What did the CMA propose on September 23, 2026?
It proposed that Google show UK users of Android and Chrome a choice of search services at first use and prompt them again every year. AI assistants could be listed if they meet the criteria, and listed providers would have to fairly attribute publisher content.

2. Is this a final rule?
No. It is a proposed conduct requirement. The consultation closed on October 9, 2026, and the CMA expects to make its final decision by the end of 2026.

3. Will ChatGPT and Perplexity definitely appear on the screens?
No. The CMA says assistants could be listed if they meet the criteria, and analyses of the proposal describe three: covering the full range of search queries, providing a functioning search experience and being considered a general search service by a significant proportion of UK users.

4. Who decides which services are listed?
Under the proposal, Google decides, through an eligibility process every six months, with written reasons for rejections sent to the applicant and the CMA. Bratby Law notes that the draft contains no appeal route to the CMA.

5. What does the attribution condition require?
Providers on the screen would have to fairly attribute publisher content when it is used, so users can reach the original source. Analyses of the consultation document say generative AI summaries must attribute web content clearly and accurately. We found no requirement for payment or traffic.

6. Does this affect businesses outside the UK?
Not directly. It applies to UK users of Android and Chrome, but it signals how regulators are treating AI assistants and attribution.

7. What should I do about it now?
Measure traffic from AI assistants, make your pages easy to attribute and check how assistants cite you. Review again when the CMA publishes its final decision, rather than changing strategy on a proposal.

If you want to know how your brand appears across Google and AI answer engines today, that is exactly what we look at in a free AI Visibility Audit.

Ask most IT leaders whether they know which AI agents are running in their company, and the answer is yes. A new survey suggests that confidence may be running well ahead of the controls behind it. Published by Guild.ai and fielded by Morning Consult, it found that 96.4% of IT decision-makers are confident their agent inventory is complete and accurate, while 66.7% of organizations with agents reported an agent-related operational consequence in the past 12 months.

One point belongs at the top, not the bottom. Guild.ai sells tools for managing AI agents, so this is vendor-sponsored research, and it should be read that way. This piece follows on from our earlier look at shadow AI and sets out what the survey reports, what its wording and bases do and do not support, and what an organization can do with the findings. It is written for teams planning AI governance and AI automation programs for agents, not just buying software for them.

What the survey reports

According to Guild.ai’s September 22, 2026 release, Morning Consult surveyed 362 U.S. IT decision-makers at companies with 100 or more employees. Interviews were conducted online from August 4 to 9, 2026, and the data was weighted by age, company size, industry and role. The margin of error is plus or minus five percentage points for the full survey.

The headline figures are these. 96.4% of IT decision-makers are confident their organization has a “complete and accurate inventory” of its AI agents. 66.7% of organizations with agents had an agent-related operational consequence in the past 12 months. 96% of organizations report agents in production, and 47% of those with agents run dozens or more.

The control figures are lower. 42.7% have a centralized dashboard or monitoring tool, 39.8% have logging or audit trails, and 31% can immediately stop a malfunctioning agent with an automated kill switch. On unapproved use, 60.6% say it is very or somewhat likely that employees deploy agents without formal approval, 35.9% require agents to be registered before deployment, and about half have a formal policy on unauthorized agent use.

Who ran it, and why that matters

Morning Consult fielded the survey, but Guild.ai commissioned and published it. Guild describes its product as a control plane for the agent lifecycle, with offerings that include AI governance and AI observability tools, according to its website. The findings point toward exactly the kind of tooling it sells, such as the 83.9% who rate real-time visibility into agent activity as extremely or very valuable.

That does not make the numbers wrong. Vendor-sponsored surveys can be carefully run, and an outside firm doing the fieldwork counts in its favor. But the sponsor chose which results to feature, so treat the data as informative and the conclusions as the vendor’s.

What the numbers do and do not show

Several details affect how far the headline can be pushed.

The word incident is not defined. The release describes an “agent-related operational consequence” and, elsewhere, an agent-related incident, and neither term is defined in the material we reviewed. A consequence could be a minor disruption or a serious breach. Two in three is a striking figure, but without a definition it does not tell you how serious those events were.

The bases differ. The 96.4% is a share of IT decision-makers. The 66.7% is a share of organizations with agents. The release does not state the base for the monitoring, audit trail and kill switch figures, so they cannot be compared precisely with the others.

The scope may be narrower than it sounds. Guild’s report page describes the survey scope as internally built and actively managed agents. If that is right, the confidence is about agents an organization built and manages, and the survey does not show how confident leaders are about agents employees bring in on their own. The 60.6% on unauthorized deployment is the nearest measure of that, and it is a perception of likelihood, not a count.

Confidence is self-reported. A leader who says the inventory is complete is giving an opinion. The survey did not test whether the inventory was actually complete, so it shows a gap between belief and controls, not a measured gap between the inventory and reality.

The margin of error applies to the full survey. Subgroup figures, such as organizations with agents, rest on fewer respondents and carry more uncertainty than the plus or minus five points suggests.

The confidence gap, read carefully

The core observation is that confidence and controls do not line up. Nearly everyone is confident about the inventory, yet fewer than half have centralized monitoring and fewer than four in ten have audit trails. A complete inventory and no way to see what the agents do is a thin kind of control.

The kill switch figures need a careful reading, because they cut both ways. Only 31% have an automated kill switch. But Guild’s own release reports that 76.5% can stop a malfunctioning agent within minutes, using an automated switch or a manual process. So most organizations say they can stop an agent quickly, and a minority have automation to do it. The accurate summary is that manual shutdown is common and automation is not. Whether a manual process works at three in the morning, or when ten agents misbehave at once, is a different question the survey cannot answer.

A second survey, and the same caveat

A separate survey points in a similar direction. SecureWorld reported on August 31, 2026 on research by Cequence Security and Enterprise Management Associates, which ran the survey for Cequence. It reported that 94% of respondents were at least moderately confident that agents do not have more access than needed, while only 32.7% used least-privilege access scoped to the task. It also reported that 47% could not reliably inventory their agents, and that 65% had seen an agent act outside its intended scope.

The sample was 202 IT and security leaders, and the coverage did not describe fieldwork dates or margins of error. Cequence is also a security vendor. Two vendor-sponsored surveys finding a gap between confidence and practice is suggestive, not conclusive, since both sponsors benefit from that story. A Cequence executive said that confidence “is usually measuring compliance, not cyber”, which is one vendor’s view, not a finding.

Why a confident inventory is not a governed one

An inventory is a list. It tells you which agents exist. AI governance is what you do with the list: who owns each agent, what it may access, who approved it, what it costs, how it is monitored, how its changes are reviewed and how it is stopped or retired.

Seen that way, the survey’s pattern is easy to understand. Teams build agents quickly, record them in a spreadsheet and feel in control. Then an agent changes, a credential is shared or an owner leaves, and the list no longer matches reality. Confidence comes from writing the list. Control comes from keeping it true.

This is also why the registration figure matters. Only 35.9% require agents to be registered before deployment. Without a registration step, an inventory is something someone compiles occasionally, not something the process produces automatically.

What to do with this

You do not need the survey’s sponsor, or any vendor, to act on its lessons. These steps apply whether you buy tooling or do the work by hand.

Test the inventory by evidence. Do not ask whether the list is complete. Look for agents the list does not contain by checking service accounts, API keys, automation platforms and cloud billing for agent activity, and by asking each team what they run.

Assign an owner to every agent. A named person or team should answer for what each agent does and what it can reach.

Make registration a precondition. An agent should not go into production until it is on the list, with its permissions, data access and purpose recorded.

Log actions, not just existence. Keep a record of what each agent did, which tools it called and which data it touched, with enough retention to reconstruct an incident.

Define incident and track it. Agree what counts as an agent-related incident in your organization, from a near miss to a breach, and record each one. You cannot improve a rate you do not measure.

Rehearse the stop. Test how fast you can disable an agent and revoke its credentials, in practice, with the person who would actually do it. If the answer depends on one individual, write it down and share it.

Limit permissions. Give each agent the narrowest access that lets it do the job, and review the access on a schedule.

For businesses planning AI agent development or wider AI automation, these controls are cheaper to design in at the start than to add later. Teams doing generative AI development should treat identity, scoped permissions and logging as part of the build, not as a later compliance task.

Where this leaves you

The confirmed facts are these. Guild.ai published a Morning Consult survey of 362 U.S. IT decision-makers, fielded in August 2026. 96.4% are confident their agent inventory is complete, and 66.7% of organizations with agents reported an agent-related operational consequence in the past 12 months. Fewer than half have centralized monitoring or audit trails. The research is vendor-sponsored, its key terms are not defined in the release, and confidence is self-reported.

The practical response does not depend on any single percentage. Treat a complete-looking list as a starting point: test it, assign owners, log what agents do and practice stopping them, whether you are in AI agent development or simply adopting agents. Organizations that do this can adopt agents faster, because they know what they are running. For anyone building AI development capability, that discipline is the foundation.

Frequently Asked Questions

1. Who ran the Guild.ai AI agent survey?
Guild.ai published it and Morning Consult fielded it. It surveyed 362 U.S. IT decision-makers at companies with 100 or more employees, online, from August 4 to 9, 2026, with a margin of error of plus or minus five points. It is vendor-sponsored research.

2. What are the key findings?
96.4% of IT decision-makers are confident their agent inventory is complete and accurate, and 66.7% of organizations with agents had an agent-related operational consequence in the past 12 months. Only 42.7% have centralized monitoring, 39.8% have audit trails and 31% have an automated kill switch.

3. Does this prove that most companies have a governance problem?
It suggests a gap between confidence and controls, but it does not prove it. Confidence is self-reported, incident is not defined, and the survey is sponsored by a company that sells agent management tools.

4. Is an incident the same as a security breach?
Not necessarily. The release uses the phrase agent-related operational consequence and does not define it, so it could cover anything from minor disruption to serious harm.

5. Can most companies stop a misbehaving agent?
The release reports that 76.5% can stop one within minutes by automated or manual means, but only 31% have an automated kill switch. Manual shutdown may work in a calm test and be harder in a real incident.

6. What is the difference between an agent inventory and AI governance?
An inventory lists which agents exist. Governance covers ownership, permissions, approval, monitoring, change control and shutdown. Strong governance keeps the inventory accurate over time.

7. What should my company do first?
Test your inventory by looking for agents it does not list, then assign an owner to each agent, require registration before deployment and set up logging of what agents do.

If you want to know which of your workflows are ready for AI agents, and where the governance gaps sit, that is exactly what we look at in a free AI Readiness Audit.

When someone searches for your business by name on their phone, the panel that appears is often the first and only thing they read. For years, that panel has been built from your Google Business Profile: hours, phone number, photos, reviews and a map pin. In September 2026, marketers began reporting something new at the top of it, an “AI Overview” label above a short, AI-written description of the business.

It is a test, not a launch, and Google has not announced it. But it points in a direction every local business should take seriously, because the description is no longer only what you wrote. This piece covers what was reported, what is and is not known, and a practical checklist of what to check now.

What was reported

On September 17, 2026, Search Engine Roundtable reported that some local knowledge panels, which are Google Business Profiles, now show an “AI Overview” label. A Show more button below the description expands the panel into a chat-style follow-up experience that resembles AI Mode. Ben Fisher, co-founder of the local search agency Steady Demand, posted about it first, and Barry Schwartz of Search Engine Roundtable said he was able to reproduce it himself.

On September 23, the UK agency Marwick Marketing described the same behavior. Its write-up says the change has so far been spotted only on mobile and that UK marketers have replicated it. It also says Google has not announced anything, and it describes the change as “not confirmed as a permanent change yet”.

That is the full set of established facts. We found no official Google statement or documentation describing the feature.

A test, not a rollout

The distinction matters because it should shape your response. A rollout is a settled change that you plan around. A test is something Google may expand, modify or withdraw, and may be showing to only some users, in some places, on some devices.

There is also precedent for this kind of experiment. Search Engine Roundtable reported in June 2024 that Google had shown AI-generated text as the description in some local panels, text that business owners had not written themselves. Schwartz’s September report says Google has been testing variations of this for a while. So the sensible reading is not that local search changed overnight. It is that Google keeps experimenting with letting AI describe a business, and the current version is the most visible so far.

The practical consequence is that some customers will see the classic panel and some may see the AI version. Both need to be right.

What the one detailed example shows

The most detailed public example is Schwartz’s own. He found that most of the AI-written description of his business was correct. One part, a section on what he calls niche solutions, was somewhat out of date. Importantly, he did not blame the AI for that. He noted that the content on his own company site was old, which suggests where the description drew its detail.

That small example carries a useful lesson. An error in an AI description may not be an AI invention. It may be an accurate summary of outdated information you published, or left in place, somewhere. Schwartz’s own reaction was mixed. He wrote that he was unsure he wanted AI describing his business “when I can” do it himself.

For a local business, the lesson is that every public statement about you, on your site, your profile and elsewhere, is a potential input. If a service you stopped offering is still listed, a summary can repeat it.

What a larger snapshot adds, with caution

On September 26, Fisher’s company published a study of how AI Overviews merge with business panels on mobile. It should be read with that context in mind: the author sells local search services, and the study is a single-day snapshot, which the author acknowledges.

The sample was 100 local brands across ten service industries, searched on mobile from a New York anchor point, with four query variations per brand. The study reported that 26% of brands showed an AI Overview on a plain brand-name search on mobile, against 6% on desktop. Of the overviews that appeared, about 80% were merged into the business panel. In four of 68 phone searches, the result surfaced a different, similarly named business. And in a three-day repeat test, one of 20 brands changed layout from one day to the next.

We would not treat those figures as a benchmark. One day, one city and an agency author make the findings suggestive, not conclusive. They support three cautious observations. The experience is not uniform. It appears more common on mobile. And a business can be confused with another of similar name, which is a reason to check your own results rather than assume.

What may feed the description, and what is unproven

The obvious question is which of your information the AI uses. Marwick Marketing says local panels draw on Google Business Profile data and on Google’s Knowledge Graph. Beyond that, advice circulating in the industry gets more speculative.

Some commentators say the services list matters more than website copy, or that review wording shapes the description, or that posts and photos act as freshness signals. Those are interpretations. We found no published test showing which fields drive the text, and one widely cited guide rests on a single reported example with no sample size or method.

So the honest position is this: nobody outside Google can say exactly how the description is built. What you can do is make every plausible source accurate, current and consistent. That costs little, and it is the same work that supports good local search engine optimization whether or not the test continues.

What to check now

Start with what customers see.

Search for your business by name on a phone while logged out of your Google account. Note whether an AI Overview label appears, read the description line by line, and take a dated screenshot. Do the same for a search like your name plus reviews. Results vary, so repeat the check on different days.

Look for errors. List anything wrong, outdated or missing, such as retired services, old locations or wrong hours, then trace each one to its source: your website, your profile, a directory or a review.

Then fix the sources.

Review your Business Profile against Google’s own guidelines. Choose categories carefully: Google tells businesses to use “the fewest number of categories” that describe the core business, and to pick the most specific ones. Make sure the services and products you list are real and current. Keep the business description honest and relevant, and remember that the guidelines do not allow special promotions, prices or links in it.

Check hours, including holiday and seasonal hours, and make sure your address and phone number match exactly across your website, your profile and your main directories. A mismatch gives any summarizer two versions to choose from.

Update your website. If the AI reads your site, an outdated services page or an old about page is a liability. Remove or revise anything that no longer applies.

Look at your reviews. Respond to recent ones, and read how customers describe you. Their language will appear in the public record about your business. Do not ask for scripted reviews or write fake ones.

Test for confusion. If your name is similar to another business, search from a different location or on a different device and see whether the wrong business appears. If it does, keep your name, address and categories distinct and accurate.

Finally, set a routine. Pick a day each month, repeat the checks and keep the dated screenshots in one place.

What not to do

Do not stuff keywords into your business name or description to influence the AI. Google’s guidelines say the name should reflect how customers know the business, and violations can lead to changes in your information or removal of your listing.

Do not assume you can opt out. Marwick Marketing reports that the only option it found was filtering AI results with the Web results toggle, which is a viewer’s choice, not a business’s.

Why this matters beyond Google

This is part of a broader shift in how people find local providers. Generative engine optimization and answer engine optimization are about being described correctly and recommended in AI-generated answers, and the AI Overview in a business panel is one of those answers, attached to your name. The same discipline applies on every platform: clear, accurate, consistent information published in places machines can read.

The Steady Demand snapshot also found that most AI citations in its sample pointed to third-party platforms, such as review sites and forums, rather than official brand sites. As a single-day sample, that is only an indication. But it is a reminder that what other people say about you may shape the answer as much as what you say yourself. Strong local search engine optimization, generative engine optimization and answer engine optimization now overlap, and a profile that is accurate everywhere is the common denominator.

Where this leaves you

The confirmed facts are these. Search Engine Roundtable reported on September 17, 2026 that some local knowledge panels show an AI Overview label, with a Show more button that opens a follow-up chat. The change was reproduced by Schwartz and by UK marketers, appears so far to be mobile only, and has not been announced by Google. It is a test.

The response is a routine, not a rebuild. An AI Visibility Audit can show where your information is wrong across AI platforms. Search for yourself, read what the panel says, trace any error to its source, and correct your profile, your website and your listings. Treat your public information as the raw material for every summary of your business, human or machine.

Frequently Asked Questions

1. What is the AI Overview label in local knowledge panels?
It is a label that some searchers see at the top of a business’s panel, above a short AI-written description. A Show more button opens a chat-style follow-up, similar to AI Mode. Search Engine Roundtable reported it on September 17, 2026.

2. Has Google confirmed this feature?
No. Google has not announced it, and we found no official documentation. It should be treated as a test that may change or disappear.

3. Is it only on mobile?
So far, reports describe mobile. Marwick Marketing says it has only been spotted there, and a September snapshot study by Steady Demand found AI Overviews far more often on mobile than on desktop. That study was a single-day, agency-run sample, so treat it as an indication.

4. Can I opt out of AI descriptions of my business?
We found no business-side opt-out. Marwick Marketing reports that the only option it found is a viewer filtering AI results with the Web results toggle.

5. What should I check first?
Search for your business by name on a phone while logged out, read the description, and screenshot it. Then check your profile categories, services, description, hours and contact details, and your website for outdated statements.

6. Does review wording affect the AI description?
Some commentators say so, but we found no published test that proves it. What you can do is respond to reviews, keep your service information accurate and never write or script fake reviews.

7. How often should I check?
Monthly is a reasonable routine for most local businesses. Keep dated screenshots so you can see what changed and when, and check more often if you make major changes to your services or hours.

If you want to know how your business appears across Google and AI answer engines, and where the information is wrong or missing, that is exactly what we look at in a free AI Visibility Audit.

For years, shopping on Google followed a familiar path: a search, a click, a visit to your store, a purchase. Your analytics were built around it. In late September 2026, part of that path moved. Eligible US Shopify merchants can now sell directly inside Google’s AI Mode and the Gemini app, where a shopper taps Buy and pays without ever opening the merchant’s website.

For merchants, the change is both an opportunity and a measurement problem. Sales can arrive from a surface where your tracking does not run. This piece sets out what was announced, who is affected, how to opt out, what the checkout supports and what it does not, and a decision framework for whether to leave it switched on. We have kept to what documentation and reputable reporting confirm, and flagged what is unclear.

What changed

On September 22, 2026, Search Engine Land reported that Google is notifying eligible Shopify merchants that their products can be bought directly in AI Mode in Google Search and in the Gemini app. The checkout runs on the Universal Commerce Protocol, an open standard Google developed with other companies, including Shopify, that lets AI agents interact with merchants and payment systems during shopping.

Two details deserve attention. First, merchants did not have to apply. Search Engine Land reports that eligible products are included automatically once a Shopify store is matched with its Google Merchant Center account, and Shopify’s help center confirms that direct checkout is on by default for eligible stores. Second, the rollout is gradual. Shopify says direct checkout is still rolling out to Google users and may not yet be available in every store, and Google’s own documentation, as quoted by ContentGrip, describes the program as “a phased program for select participating merchants”.

Who is eligible

Shopify’s help center lists the requirements. Your store must be based in the United States and sell to US customers. You need a valid Google Merchant Center account and must meet Google’s requirements, including its free listing eligibility and return policy rules. Your products must be available in Merchant Center, either through Shopify’s Google and YouTube sales channel with product and shipping sync turned on, or through a third-party feed provider or manual upload. Products must also be eligible for Shopify Catalog, you must agree to the Shopify Agentic Storefronts Supplemental Terms of Service, and your terms of service, privacy policy and refund policy must be completed in your Shopify settings.

Direct checkout is shown only to US-based shoppers.

There is no extra fee. Shopify states that you pay only your standard payment processing fees. Merchants also keep the underlying customer and order relationship, according to Search Engine Land, and the retailer remains the seller of record, according to Google’s documentation as cited by ContentGrip.

How to opt out

If you want shoppers to complete purchases on your own site, Shopify’s help center gives these steps. In the Shopify admin, go to Sales channels, then Agentic. Deactivate the setting called Allow Shopify to manage for me. Click Google AI Mode and Gemini. Switch Direct checkout off, then click Save.

Opting out does not remove you from AI Mode. Your products can still appear in results, but shoppers are redirected to your online store to complete the purchase.

What direct checkout supports, and what it does not

The in-AI checkout is not an exact copy of your store’s checkout. Shopify’s documentation sets out the gaps.

Supported: automatic discounts and discount codes, and Shopify Functions for shipping, discounts and cart and checkout validation.

Not supported: subscriptions, product bundles, customizable products and B2B-only products. Local delivery, in-store pickup and pickup points. Requiring customers to sign in before checkout. Only a subset of accelerated checkout options. Many checkout blocks, including upsells, loyalty and rewards blocks, consent collection blocks, chat blocks and trust badges, may not display, so the checkout can look different from your own. Shopify also asks that required legal disclosures appear within the first 6,000 characters of a product description.

Why this is a measurement problem

Shopify’s help page states plainly that “Google Analytics and custom pixels won’t fire” in direct checkout. Only server-to-server pixel events fire, and only two of them: checkout started and checkout completed.

Your analytics tag, ad platform pixels and attribution tools all depend on code running in the shopper’s browser on your site. When the purchase happens inside Google’s surface, that code never loads. The sale is real, but the session your tools normally record does not exist on your side.

Three practical consequences follow.

Revenue can be undercounted in tools that rely on client-side tracking. If you compare Google Analytics revenue with Shopify order totals, a widening gap may be this checkout, not a tracking bug.

Channel reporting can shift. Because the journey no longer includes a visit to your site, orders may not be credited the way you expect. Shopify’s page does not describe how these orders are labeled in your admin or reports, and we found no authoritative source that does, so treat any confident claim about it with caution.

Funnel analysis loses steps. These buyers generate no product page views, add-to-cart events or checkout steps on your site, so a shift in conversion rate could reflect where people buy, not how well your pages convert.

The practical answer is to reconcile against Shopify’s own order data, which records the purchase wherever it happens, and to stop treating the browser-side analytics tag as the only source of truth for revenue.

What is still unclear

Some claims in circulation should stay out of your planning until they are confirmed. Some coverage repeats specific review thresholds, such as a minimum number of reviews and a minimum star rating. Those figures relate to Merchant Center’s store ratings rules for showing ratings with ads, and we could not confirm that they are conditions for this checkout. Shopify’s eligibility list above does not include them.

Reports of a separate, wider default-on rollout of agent checkout across Shopify, including a figure of about one million merchants, rest on thin sourcing, so we have not relied on them.

Finally, there are open questions on reporting: how these orders are labeled, what Google will offer in Merchant Center for AI surface performance, and how consent settings apply. Recheck the documentation before committing.

Opt in or opt out: a decision framework

There is no single right answer. It depends on what you sell and how you measure it. Use these questions.

Do you sell subscriptions, bundles, customizable items or B2B-only products? If these make up a large share of revenue, the AI checkout cannot handle them, and keeping the feature on mainly matters for your simpler products.

How much of your profit comes from checkout upsells or loyalty features? If the answer is a lot, redirecting shoppers to your own checkout protects that revenue.

How dependent is your reporting on client-side tracking? If your team, or your agency, cannot trust revenue numbers without it, you may prefer to opt out until your reporting is ready.

Do you want to learn? Some merchants will reasonably leave it on for a few weeks and compare Shopify order data with previous periods, as long as they set a review date.

For most stores, a good default is to keep the feature on for a defined trial period if your product mix is mostly simple, one-time purchases, and to switch it off if subscriptions, bundles or upsells drive revenue.

What to do this week

Open the Agentic section in Shopify and see whether direct checkout is on for your store.

Review your Merchant Center feed and your Shopify policies. Product discovery in AI Mode is powered by Merchant Center, so missing attributes, mismatched prices or incomplete return policies can limit what shows up.

Check product descriptions for legal disclosures in the first 6,000 characters.

Place a test order if possible and see how it appears in Shopify and in your analytics.

Reconcile weekly. Compare Shopify order totals with analytics revenue.

Why this matters for visibility

This checkout sits at the end of a discovery path, and the path begins with product data. Shopify’s documentation says product discovery in AI Mode is powered by Google Merchant Center, so a store whose data is complete and consistent has a better chance of being shown. That is where search engine optimization, generative engine optimization and answer engine optimization meet ecommerce: accurate titles, complete attributes, clear policies, authentic reviews and consistent information across your site and your feed.

The checkout does not change the basics. It raises the stakes on them, because a recommendation in an AI answer can now turn into a sale without a visit to your site. For brands that want to understand how they appear in these answers before deciding how to respond, an AI Visibility Audit is a sensible starting point, because you cannot manage what you have not measured.

Where this leaves you

The confirmed facts are these. Google and Shopify have enabled a native checkout in AI Mode and the Gemini app for eligible US Shopify merchants, powered by the Universal Commerce Protocol. It is on by default for eligible stores and can be turned off in the Agentic settings. Merchants keep the customer and order relationship. Google Analytics and custom pixels do not fire, and only server-to-server started and completed events are sent. Several features, including subscriptions and bundles, are unsupported.

The response is a decision, not a panic. Check your setting, choose deliberately, protect what depends on your own checkout, and measure through Shopify’s order data while your reporting catches up. Strong search engine optimization, generative engine optimization and answer engine optimization all start with clean product data, either way.

Frequently Asked Questions

1. Is Google’s AI Mode checkout turned on for my Shopify store?
If your store is based in the US, sells to US customers and is matched with a valid Merchant Center account, it is likely eligible, and Shopify says direct checkout is on by default for eligible stores. The rollout is gradual, so check Sales channels, then Agentic, in your Shopify admin.

2. How do I opt out of direct checkout in AI Mode?
In Shopify admin, go to Sales channels, then Agentic. Deactivate Allow Shopify to manage for me, click Google AI Mode and Gemini, switch Direct checkout off and save. Your products can still appear, but shoppers are sent to your online store to buy.

3. Do I still own the customer and the order?
Search Engine Land reports that merchants keep the underlying customer and order relationship, and Google’s documentation, as cited by ContentGrip, says the retailer remains the seller of record. Shopify charges no extra fee beyond standard payment processing.

4. Will Google Analytics track these purchases?
No. Shopify’s help page says Google Analytics and custom pixels do not fire in direct checkout. Only server-to-server started and completed events are sent. Use Shopify’s order data to reconcile revenue.

5. Which products and features does the AI checkout not support?
Subscriptions, bundles, customizable products and B2B-only products are not supported, nor are local delivery, pickup or required sign-in. Many checkout blocks, such as upsells, loyalty and consent blocks, may not display.

6. Do I need 100 reviews and a 3.5 star rating?
We could not confirm that. Those figures relate to Merchant Center store ratings for ads and are not on Shopify’s eligibility list.

7. Should I leave it on or switch it off?
It depends on your product mix and your reporting. Stores with mostly simple, one-time purchases may reasonably test it for a defined period. Stores that rely on subscriptions, bundles, upsells or client-side tracking may prefer to opt out.

If you want to know how your brand and products show up across Google and AI answer engines, that is exactly what we look at in a free AI Visibility Audit.

On September 24, 2026, Google began rolling out its September 2026 spam update. Spam updates usually finish in a couple of days, so most site owners are used to a short burst of volatility followed by a clear before and after. This one is different. Google says the rollout may take up to two weeks, which means that for a full fortnight, every ranking change you see is a reading from a moving target.

That changes how you should respond. This piece covers what Google has confirmed, what it has not said, what early volatility data does and does not show, and a practical plan for the days between now and the end of the rollout. It is written for anyone responsible for search engine optimization at their company, whether you run a small site or manage a large content library.

What is confirmed

The core facts come from Google’s Search Status Dashboard and are consistent across Search Engine Land, Search Engine Journal and Search Engine Roundtable.

The update began on September 24, 2026, at 9:15 a.m. Pacific time. It applies globally and to all languages. Google’s dashboard says the rollout may take “up to two weeks to complete”, which puts the latest possible finish around October 8. It is the fourth spam update of 2026, following releases in March, June and August.

The rollout window is what stands out. The dashboard lists the earlier 2026 spam updates at 19 hours and 30 minutes for March, 2 days and 1 hour for June, and 2 days and 16 hours for August. Two weeks is several times longer than any of them. One point of precision matters here: two weeks is the announced maximum, not a measured duration. The update could finish sooner, and until Google marks it complete, nobody outside Google knows how long it will really take.

What Google has not said

Google has not said what this update targets. According to PPC Land, Search Central described it only as a normal spam update, with no new policy, no named category and no figures on how many queries are affected. That gap matters, because much of the commentary this week has filled it with confident claims about which sites are being hit and why. Treat those claims as hypotheses. The only firm statement from Google is that sites which see a change should review its spam policies. Anything more specific is inference from other people’s data.

What early data shows, and what it does not

Search Engine Roundtable reported that a long list of volatility trackers showed significant movement across the first weekend, September 25 to 27. The tools it named include Semrush Sensor, AccuRanker, Mozcast, Sistrix, Algoroo and several others. When that many independent trackers move at once, it is a reasonable signal that something real is happening in the results.

Glenn Gabe, a well-known analyst of Google updates, reported big drops across a number of sites in multiple verticals and countries. He described AI-generated content sites and programmatic content farms as among those losing rankings. That is one experienced observer’s read of the sites he tracks, and it fits how Google’s spam policies treat scaled content, but it is not confirmed by Google and it is not a full picture of who is affected.

There are three reasons to be careful with early data.

First, volatility is not damaging. Trackers measure how much results moved, not who won or lost. A large reading can come from a few sites moving a long way.

Second, the update is not finished, so the pattern on day five may look different by day ten.

Third, you are reading a mix of signals. Seasonal demand, your own recent changes, other Google systems and ordinary news cycles all move traffic at the same time. Attributing a dip to the spam update before it ends is a guess.

What to do while it rolls out

The most useful thing to do during a long rollout is resist the urge to react. Here is a working plan.

Record a baseline. Before anything else, capture your current position. Export Search Console performance data for the last 90 days by page and by query, along with clicks, impressions, average position and the countries you care about. Note recent changes such as redesigns, migrations, new content batches and link campaigns.

Annotate the timeline. Mark September 24 in your analytics and reporting tools, and add a note when Google marks the rollout complete.

Compare like with like. Weekday traffic and weekend traffic behave differently for many sites. Compare the days since September 24 with the same weekdays in earlier weeks.

Segment before you conclude. A sitewide traffic drop is rarely uniform. Split the data by page type, by folder, by template and by query group. If the loss is concentrated in one section, such as a batch of AI-assisted pages or a subdirectory of third-party content, that tells you far more than a total.

Do not make sweeping changes. Deleting hundreds of pages, rewriting templates or disavowing links mid-rollout makes it impossible to tell what caused what. If you suspect a policy problem, plan the fix and stage it.

Fix what is clearly broken. If you find hacked content, injected links, broken redirects or a security issue, fix it immediately.

Hold your publishing rhythm. Search Engine Land’s coverage advises sites that are not affected to keep doing what they were doing.

Audit against Google’s spam policies now

Whether or not you see a drop, this is a good week to check yourself against the policies Google points to. Google’s documentation names categories including cloaking, doorway abuse, expired domain abuse, hacked content, hidden text and links, keyword stuffing, link spam, scaled content abuse, scraping, site reputation abuse, sneaky redirects, thin affiliation and user-generated spam.

Three of these tend to matter most for modern content teams.

Scaled content abuse is about producing large volumes of low-value pages in order to manipulate rankings, whether the pages are written by people, generated by AI tools or scrapped. The test is value per page, not the tool used. A large batch of near-duplicate location pages or templated question pages with thin answers is the pattern to look for.

Site reputation abuse covers publishing third-party content on an established site mainly to borrow its ranking strength. Sponsored sections or partner content hubs on an established site are examples.

Link spam covers buying, exchanging or generating links mainly to manipulate rankings. If you have inherited a backlink profile from a past agency, this is the moment to review it critically, not defensively.

If you find something that fits, note what it is, how many pages it affects and what you would do about it. You need not act during the rollout, but be ready to.

What recovery looks like

If you are affected, it helps to set expectations early. Google’s spam update documentation says that fixing problems may help a site improve if its automated systems learn “over a period of months” that the site complies with its policies. It also warns that for link spam, changes may not bring an improvement, because ranking benefits from those links cannot be regained.

So recovery is not a matter of days, and it is not guaranteed. The right frame is a remediation plan measured in months, not a quick reaction to a bad week.

Spam updates also occasionally catch sites that were not breaking the rules. Search Engine Land notes that this should not typically happen but sometimes does. If you believe you were caught unfairly, audit yourself carefully, document your evidence and keep monitoring.

Why this matters beyond classic rankings

Most teams now think about visibility in more places than the ten blue links. Generative engine optimization and answer engine optimization are about being cited and recommended in AI answers, which draw on the wider web and on search results. No one has published data showing how this specific spam update affects citations in AI Overviews, ChatGPT or Perplexity, and it would be a mistake to claim otherwise.

What can be said is narrower and more practical. Pages that lose organic visibility in Google lose a route to being seen and cited, and the qualities that spam policies punish, such as thin, repetitive, mass-produced content, are also poor candidates for being quoted in an AI answer. Strong search engine optimization, generative engine optimization and answer engine optimization all tend to rest on the same base: original, useful pages that answer a real question well. If you are building visibility for AI search, the spam policies are a sensible floor.

If you track AI citations, set that baseline now too, and compare again after Google says the update is complete.

Where this leaves you

The confirmed facts are these. Google started the September 2026 spam update on September 24, it is global, and it may take up to two weeks. It is the fourth spam update this year and the longest announced window. Google has not said what it targets. Early volatility is real, and some analysts report losses among AI-generated and programmatic sites, but that is observation, not confirmation.

The practical response for any search engine optimization team is patience with discipline. Take a baseline, mark the dates, segment your data, audit your own site against the spam policies, fix genuine defects and hold back on big changes until the rollout ends. A two-week update rewards teams that measure carefully, not teams that react fastest.

Frequently Asked Questions

1. When did Google’s September 2026 spam update start, and when will it finish?
Answer: It began on September 24, 2026, at 9:15 a.m. Pacific time. Google says the rollout may take up to two weeks, so the latest expected finish is around October 8. It could end sooner.

2. Why is this spam update considered the longest of 2026?
Answer: Because the announced window of up to two weeks is far longer than the earlier 2026 spam updates, which the dashboard lists at 19 hours and 30 minutes, 2 days and 1 hour, and 2 days and 16 hours. Two weeks is a maximum, not a confirmed actual duration.

3. What does the September 2026 spam update target?
Answer: Google has not said. It applies worldwide to all languages. Some analysts report ranking losses among AI-generated content sites and programmatic content farms, but that is their observation, not a statement from Google.

4. Should I change my site while the update is rolling out?
Answer: Not in a sweeping way. Record a baseline, annotate the dates, and segment your data. Fix clear defects such as hacked content or broken redirects immediately, but avoid large deletions, rewrites or disavows until the rollout is complete.

5. How long does it take to recover from a spam update?
Answer: Google says recovery can take months, because its automated systems must learn over time that a site follows its spam policies. For link spam, ranking benefits from those links may not return at all, even after cleanup.

6. Does the spam update affect visibility in AI answers?
Answer: No data has been published on that yet. Pages that lose Google visibility lose one route to being cited, and low-value mass-produced content is a poor candidate for citation anyway. Measure AI citations before and after the rollout and compare, and do not draw conclusions from one week.

7. How can I check whether my site is at risk?
Answer: Audit against Google’s spam policies, especially scaled content abuse, site reputation abuse and link spam. Then compare your Search Console data by page type and query group against a 90-day baseline.

If you want to know where your brand appears, and where it is missing, across Google and AI answer engines, that is exactly what we look at in a free AI Visibility Audit.

For the last two years, enterprise AI has mostly been sold as a feature: a chatbot in the corner of a screen, a summarize button, an assistant that answers one question at a time. On September 11, 2026, Salesforce made a different kind of pitch. It introduced seven named Agentforce agents, each built for a specific job, and described one of them as able to pursue a goal across weeks instead of a single conversation.

The naming is not a cosmetic detail. It signals a shift in how vendors want buyers to think about AI: less as software you configure and more as labour you deploy. This piece follows on from our earlier look at MCP and A2A governance, and it covers what Salesforce announced, what its customer results do and do not show, and what a buyer should ask before treating an AI agent like an employee.

What Salesforce announced

According to Salesforce’s announcement and coverage from Unite.AI and Startup Fortune, the seven agents and their jobs are as follows.

Casey is a help agent for customer service, working across voice, SMS, WhatsApp, and web chat. Paige handles IT and HR requests for employees, including through Slack and employee portals. Carter is a shopper agent that helps with product discovery, comparison, and checkout. Marshall is a supply chain agent that orchestrates back-office processes with audit trails. Piper handles inbound lead generation, engaging and qualifying leads for B2B sales. Fin is a customer agent that resolves complex customer-experience workflows. Hunter is an outbound sales agent that manages a pipeline from research through outreach.

Availability differs. Six of the seven, Casey, Paige, Carter, Marshall, Piper, and Fin, are generally available now. Hunter is in pilot, with general availability planned for November 2026.

Hunter is also the agent that uses a new long-horizon runtime. Salesforce describes it as built on three capabilities: memory, which preserves context across sessions; durable execution, which keeps a plan running over time; and dynamic steering, which adapts behavior based on feedback from users. The point of the runtime is that an agent can work toward a goal across days and weeks, instead of finishing one task and forgetting it. Hunter is the first agent to run on it.

The announcement included other platform pieces. Multi-Agent Orchestration, which routes work across coordinated teams of agents, is generally available. Agentforce Coworker, an employee-facing agent with AI Skills, and Agent Optimizer, a tool for refining agents, are scheduled for general availability in October 2026. Salesforce also introduced Agent Script, an open-source language for defining agent behavior with deterministic rules, which matters because it gives builders a way to fix certain steps in place instead of leaving everything to the model. None of the coverage we reviewed gave pricing.

How long the memory lasts

Some headlines around this launch describe agents with months of memory. The sources we reviewed do not support that. Salesforce’s own description is days and weeks. That is still a meaningful change, but the difference matters when a buyer is estimating how long an agent can hold onto a plan.

The customer results, and why to read them carefully

Salesforce published six customer results with the launch. All of them are reported by Salesforce, and none of the coverage we reviewed included independent verification or a definition of how each metric was measured.

Engine reported that 50% of chat inquiries are fully resolved by its help agent, which it calls Eva. Perk reported that Hunter built 60% of its sales pipeline. Autism Queensland reported that Paige resolves 70% of administrative requests. Hibbett reported that an agent handles 90% of core shopper journeys, after going live in six weeks. Asana reported 4x conversation volume driven by Piper. Anthropic reported that Fin resolves 79% of conversations autonomously.

These are useful as directional evidence. They are not benchmarks, and four things are missing that any buyer should ask about.

The first is definitions. Resolved could mean that a customer got a correct answer, or it could mean that the conversation ended without escalation. Those are very different outcomes. The second is baselines. Fifty percent resolved means more or less depending on what was resolved before the agent arrived. The third is scope. A figure for one team, one region, or one channel may not transfer to your business. The fourth is selection. Vendors highlight their strongest results, so a set of six published numbers says little about the distribution of outcomes across all customers.

There is one specific point on Perk. Hunter is still in pilot, so that result necessarily comes from early use, not a generally available product. Startup Fortune’s coverage made the same overall point, describing the results as early evidence and not a guarantee.

The governance layer was announced separately

Coverage of this launch sometimes lumps the AI Control Plane in with the seven agents. It was announced separately, one day earlier, on September 10, alongside what Salesforce calls a Trusted Enterprise AI Harness.

According to AI Weekly, the control plane provides routing, lineage, and cost and observability across both Salesforce and third-party AI, and it is positioned as a governance layer over a multi-vendor agent landscape. An analyst blog covering Dreamforce described it as a central registry of agents, MCP servers, and APIs with automatic discovery and a single gateway for model, MCP, and agent calls, and said it is designed to cover agents beyond Salesforce’s own.

Two cautions apply. AI Weekly reported that most capabilities are live while the rest are scheduled for fiscal year 2028, so buyers should not assume everything described is available today. And the same analyst blog noted that the control plane was initially previewed in 2025, which suggests some of it is an evolution of earlier work and not new this month. Neither source gave a general availability date for the full set.

A registry of agents, MCP servers, and APIs is exactly the kind of inventory that AI governance requires. It is also a reminder that governance products from a platform vendor cover that vendor’s view of the world first, so a company running agents from several suppliers should test how well the third-party coverage actually works.

Why names and job titles matter

Giving an agent a name and a role is a marketing decision, and it is also a framing decision. A named agent with a job title invites the same expectations we place on a person in that role: that it owns an outcome, that someone is accountable for it, and that it can be evaluated like a hire.

That framing has real benefits. It gives buyers a clearer mental model than a generic assistant. It pushes vendors to tie agents to measurable jobs such as resolving support tickets or qualifying leads, which is what sensible AI automation projects do anyway. And it makes it easier for a business to ask what work is being replaced, augmented, or created.

It also creates a risk. Names encourage people to trust an agent in the way they would trust a colleague, and an agent is not a colleague. It has no professional judgment, no personal accountability, and no understanding of context beyond what it has been given. Startup Fortune raised the question directly: “which decisions stay with people, which ones the agent takes alone?” That question should be answered in writing before an agent goes live, not discovered after an error.

Why weeks-long agents change the risk

The long-horizon runtime deserves separate attention, because it changes what can go wrong. A chatbot that answers one question and forgets it produces contained errors. An agent that holds a plan for weeks, remembers past interactions, and adjusts its behavior can compound a mistake, act on stale information, or continue a course of action after circumstances have changed.

Memory also raises data questions. What does the agent retain, for how long, and who can see or delete it? Durable execution raises control questions. How do you pause or stop an agent that is mid-plan, and how do you review what it did while nobody was watching? Dynamic steering raises accountability questions. When feedback changes an agent’s behavior, who approved that change?

These are design questions for anyone working on AI agent development, and they are procurement questions for anyone buying agents. The sensible default for a weeks-long agent is tighter limits: narrow permissions, explicit approval for irreversible actions, clear stop conditions, and a complete log of what it decided and why.

What to ask before you deploy a job-ready agent

Whether you buy from Salesforce or another vendor, the same questions apply.

What exactly is the job, and how is success measured? Define the metric before the pilot, including what counts as resolved or qualified.

What does the agent decide alone, and what needs a person? Write the boundary down and test it.

What data does it read, retain, and write? Confirm retention periods and deletion.

How do you audit and stop it? This is the core of AI governance for agents. Ask to see the logs and the pause controls.

How does it behave when it is wrong? Test escalation paths and error handling with real edge cases.

What is the fallback? Keep a documented way to run the process without the agent.

How does it fit with the rest of your agents? If you run agents from more than one vendor, check whether the governance layer really covers them.

Where this leaves you

The confirmed facts are these. Salesforce launched seven named agents on September 11, 2026. Six are generally available and Hunter is in pilot until a planned November release. Hunter runs on a new runtime designed to pursue goals over days and weeks. A separate governance announcement the day before introduced an AI Control Plane, with parts still to roll out. All customer results are Salesforce-reported and lack published definitions.

The broader shift is real. Enterprise AI is increasingly sold as a defined piece of work with a name attached. That makes it easier to evaluate, provided you insist on definitions, baselines, and limits. Businesses exploring AI automation, AI agent development, or generative AI development can borrow the useful part of the framing, which is to scope each agent to a specific job, and skip the risky part, which is treating it like a person.

Frequently Asked Questions

1. What are the seven Agentforce agents?
Answer: Casey (customer service), Paige (IT and HR), Carter (shopping), Marshall (supply chain), Piper (inbound lead generation), Fin (customer experience workflows), and Hunter (outbound sales). Salesforce announced them on September 11, 2026.

2. Which agents are available now?
Answer: Casey, Paige, Carter, Marshall, Piper, and Fin are generally available. Hunter is in pilot, with general availability planned for November 2026.

3. What is the long-horizon runtime?
Answer: It is a new runtime that lets an agent pursue goals across days and weeks using memory, durable execution, and dynamic steering. Hunter is the first agent to use it.

4. Are Salesforce’s customer results independent?
Answer: No. All six results are reported by Salesforce, and the coverage reviewed did not define how metrics such as resolved were measured. Treat them as directional evidence, not benchmarks.

5. What is the AI Control Plane?
Answer: It is a governance layer announced separately on September 10, 2026 that provides routing, lineage, cost and observability across Salesforce and third-party AI. Some capabilities are live and the rest are scheduled for fiscal year 2028.

6. How should a business evaluate an AI agent before deploying it?
Answer: Define the job and success metric, set the boundary between agent and human decisions, confirm data retention, check audit logs and stop controls, and test failure handling.

If you want to know which of your workflows are ready for AI agents and where the risks sit, that is exactly what we look at in a free AI Readiness Audit.