I’ve just delved into Goodie’s enlightening AI search traffic report for early 2026, covering the period from January to April, and I’m excited to share my insights with you. This report dives into trends in usership, referral traffic, and marketing considerations, offering a comprehensive view of the shifting landscape.
You’ll want to pay particular attention to how ChatGPT’s dominance is starting to wane, with some surprising contenders like Claude and Gemini making waves. This shift could significantly impact how marketers strategize their efforts in AI-driven search optimization.
The data reveals fascinating patterns in user habits and referral traffic, which could inform future marketing strategies and the allocation of resources. For a full dive into these emerging trends and what they might mean for businesses, I encourage you to explore the detailed findings of the report.
If Claude gives you a strong search-term analysis only after you paste the same instructions and CSV into a new chat, you have improved the task, not automated it. You still have to assemble the context, request the analysis, normalize the output, and move each approved change into Google Ads.
Claude-powered PPC automation becomes useful when you design those handoffs once. The practical system has three separate parts: decision logic, access to current campaign data, and controls over what the AI may change. Get those parts right and Claude can take recurring work off your desk without taking campaign authority away from you.
The three parts of a reliable Claude PPC system
The model is only one layer of the system. A dependable workflow also needs a stable playbook and an explicit operating boundary.
System part
What it does
The question you must answer
Claude Skill
Encodes the task, decision rules, required inputs, exceptions, and output structure.
What should happen every time this PPC job runs?
Data and tools
Supply campaign context and, when authorized, provide a way to execute an approved action.
Which data may Claude read, and which operations may it call?
Workflow controls
Define scope, approval requirements, stop conditions, and records of proposed or completed changes.
What is Claude allowed to decide, recommend, and change?
A Claude Skill is a task-specific playbook, not a general preference about tone or behavior. It can tell Claude how to audit an account, evaluate search terms, generate ad assets, or compare budget opportunities. The instructions can be stored in a Markdown file, kept locally, or shared through a repository so the team uses the same method.
The main benefit is procedural consistency. Without a fixed contract, one run might return letter grades while another uses percentages or an unrelated numerical scale. That is more than a presentation problem. A person, spreadsheet, script, or approval workflow cannot reliably consume an output whose structure changes between runs.
A Skill should make the process predictable, but it should not pretend every PPC judgment is deterministic. Campaign evidence changes, and some cases will remain ambiguous. Your playbook therefore needs both decision rules and an explicit way to return insufficient evidence, conflicting signals, or required human review.
The data layer solves a different problem. A Skill can know how to evaluate a search query report while knowing nothing about the queries currently appearing in your account. A Model Context Protocol connection can bridge that gap: MCP can connect Skill logic to live data sources and account tools. That turns a static playbook into an operating workflow, but it also makes permissions and approval gates essential.
Build the first workflow around one recurring decision
Start with a bounded job rather than asking Claude to optimize an account. Search-term mining is a practical first candidate because you can define the input, inspect every recommendation, and test the logic without granting write access.
Define the job in one sentence. For example: review search terms from the requested 14-day window, identify waste and opportunity using the account’s approved criteria, and return proposed actions for review. The 14-day period is an input to this workflow, not a universal recommendation for every account.
Write down the judgment currently living in the operator’s head. Include the evidence Claude must consider, the conditions that support each recommendation, the exceptions that require escalation, and anything it must never infer from missing data.
Lock the output contract. Name every required field, its allowed values, and what a stopped run looks like. Do not let Claude invent a new scoring system or column set each time.
Convert the SOP into a Skill. A useful instruction is: Convert this SOP into a task-specific Claude Skill. Preserve the decision rules, define required inputs, return a fixed schema, stop when required fields are missing, and do not take write actions without approval.
Run the Skill against a known CSV before connecting an account. Confirm that it covers the intended records, follows the rubric, flags exceptions, and returns the exact structure your reviewer or downstream tool expects.
Connect live data in read-only mode. Compare the live run with the CSV-based process. Add write capabilities only after the connected workflow passes the same acceptance checks.
A useful output contract for this workflow can require:
The account, campaign, and reporting window included in the run.
A completion status that distinguishes a finished analysis from a stopped or incomplete run.
The item reviewed, the evidence used, and the applicable decision rule.
The proposed action and a concise reason for it.
An exception field for missing inputs, conflicting signals, or cases outside the Skill’s authority.
An authorization state such as proposal, approved, executed, or rejected.
The output contract is what turns a clever response into a component another person or system can trust. Claude should never quietly substitute a plausible answer when a required campaign field is unavailable. A stopped run with a precise error is safer and more useful than a polished recommendation built on incomplete context.
Put money-changing actions behind explicit gates
Access and authority are not the same thing. An MCP-enabled tool may make an account change technically possible, but your workflow still decides whether Claude may propose it, prepare it, or execute it. That distinction matters whenever an action can change spend, targeting, messaging, or delivery.
Operating mode
Claude’s role
Human role
Manual-context assistant
Analyzes an uploaded report and returns structured recommendations.
Exports data, checks the result, and implements every change.
Connected analyst
Pulls permitted live data and prepares account-specific proposals.
Reviews and approves each proposed action before execution.
Controlled operator
Executes only approved action types within the defined scope and constraints.
Sets policy, handles exceptions, reviews logs, and can stop the workflow.
Most teams should move through these modes in order. Live read access removes manual report handling without immediately exposing the account to automated edits. Proposal-only operation then shows whether the logic behaves well under current conditions. Controlled execution comes last, after the team knows which exceptions appear in real runs.
Before enabling any write action, add these controls to the workflow:
Default-deny permissions. Claude may read or modify only the accounts, campaigns, objects, and action types explicitly included in scope.
Action-specific approval. Treat applying an existing extension, creating an ad experiment, changing a search-term response, and reallocating budget as separate permissions.
User-defined financial boundaries. A budget workflow must operate inside limits set by the account owner rather than deciding its own acceptable spend change.
Fail-closed behavior. Missing data, an invalid schema, an unavailable tool, or an out-of-scope request should stop the run instead of triggering a best guess.
A preview of the exact modification. The reviewer should see what object will change, its current state, the proposed state, and the reason before approving it.
An audit trail. Preserve the input scope, Skill version, findings, approval state, tool response, and execution result so a later reviewer can reconstruct what happened.
A conflict rule. Give each task one canonical Skill, because overlapping audit or optimization Skills can reintroduce the inconsistency the system was built to remove.
A recovery plan. Document how an executed change will be reversed when reversal is available. Keep irreversible or poorly understood actions manual.
Budget reallocation deserves the tightest gate because it moves money between campaigns. A recommendation can still be automated: Claude can compare the permitted data, explain the proposed shift, and prepare the action. Execution should remain subject to the account owner’s constraints and approval until the workflow has demonstrated reliable behavior in proposal-only mode.
Use acceptance checks rather than impressions when deciding whether a workflow is ready. The run should always return the required fields, stop on missing inputs, stay inside its declared scope, expose the evidence behind each proposal, and show the planned modification before execution. If any of those checks fail, improve the Skill or connection before expanding its authority.
Choose PPC tasks by controllability, not novelty
The best first automation is not necessarily the task consuming the largest budget or producing the most visible output. It is the task whose rules can be written clearly, whose evidence can be inspected, and whose mistakes can be contained.
PPC workflow
What the Skill should standardize
First safe deployment
Expanded deployment
Search-term mining
The evaluation rubric, required evidence, exception handling, and recommendation format.
Analyze an uploaded report and return proposals for review.
Pull live search-term data and implement only separately approved actions.
Ad copy generation
How landing-page information, keywords, user intent, and value propositions become proposed ad assets.
Generate structured drafts for human review.
Identify underperforming ads, prepare alternatives, and create an approved experiment.
Account auditing
The checklist, severity logic, supporting evidence, and distinction between findings and remedies.
Return a consistent audit with no account changes.
Use live account data and apply permitted remedies, such as attaching an existing extension where appropriate.
Budget reallocation
The comparison method, constraints, explanation, and escalation conditions.
Produce proposed reallocations with no write access.
Execute approved shifts inside account-owner limits and record every result.
Score a candidate workflow against five practical questions before building it:
Does the task recur often enough that removing handoffs will matter?
Can an experienced operator state the decision rules without relying on unexplained instinct?
Are the required inputs available in a stable, inspectable form?
Can a reviewer verify the recommendation before the account changes?
Can the impact of an error be contained to a narrow scope?
If the answers are weak, connecting more tools will not improve the workflow. Clarify the SOP first. Automation magnifies whatever is encoded: good judgment becomes repeatable, while an ambiguous process becomes ambiguous at greater speed.
For a first deployment, we would favor a proposal-only search-term or account-audit workflow. Both make it easy to compare Claude’s output with an existing human process. Ad experiments can follow once asset review is defined. Budget execution belongs later because its consequences reach spend directly.
Frequently asked questions
What is Claude-powered PPC automation?
It is a workflow in which a Claude Skill applies a repeatable PPC playbook, data connections supply the required campaign context, and explicit permissions determine whether Claude analyzes, proposes, or executes an action. A chat response alone is assistance; automation also handles the recurring context and handoffs.
Do you need MCP to use a Claude Skill for PPC?
No. You can run a Skill against a manually uploaded CSV and implement its recommendations yourself. MCP becomes relevant when you want Claude to retrieve live data or use connected account tools. Start with manual or read-only data if the Skill’s decision logic has not yet been validated.
Which PPC workflow should you automate first?
Choose a recurring workflow with written rules, inspectable inputs, a fixed output, and limited consequences when something goes wrong. Search-term mining or a checklist-based audit is usually easier to validate than autonomous budget reallocation. Keep the first version proposal-only so you can judge the logic before granting execution authority.
How do you prevent inconsistent Claude outputs?
Use one canonical Skill for the task, define required fields and allowed values, state how exceptions must be returned, and stop the run when required data is missing. Remove or narrow competing Skills that could handle the same request. Test structural consistency before connecting the output to another tool.
Take the next recurring search-term review or account audit and write down its rubric, output contract, and stop conditions. Test that process on a CSV, connect live data in read-only mode, and grant write access only after the workflow passes explicit acceptance checks. That sequence turns Claude from another prompt window into a PPC system you can supervise.
Your brand can appear in an AI answer and still send almost no visible traffic to your analytics. It can also send only a handful of visits that produce valuable leads or purchases. If you judge both outcomes by sessions alone, you will either dismiss AI search too early or overstate what it contributes.
The practical answer is to manage AI visibility as a pipeline: access, source selection, click and business outcome. Each stage needs its own metric and its own fix. Once you separate them, you can tell whether you have a visibility problem, a traffic problem or a conversion problem.
Key takeaways
An AI citation is exposure, an LLM referral session is a click, and a conversion is a business outcome. Do not combine them into one visibility number.
Track both LLM share of referral traffic and LLM share of total site traffic. They answer different questions and must use different denominators.
Keep raw sessions and conversions beside percentage metrics. Low traffic volumes can make conversion rates look more stable than they are.
Ordinary SEO still matters. Crawl access, clear page structure, descriptive metadata, internal links and authoritative mentions help make content discoverable.
ClaudeBot, Claude-User and Claude-SearchBot perform different jobs. Set crawler policy for each instead of treating all Claude access as one decision.
Measure the four-stage path, not one visibility score
A conventional analytics report begins after someone clicks. AI discovery often begins much earlier, and an answer can mention your brand without generating a visit. Your scorecard therefore needs four layers.
Access: Can the relevant crawler or user-initiated fetcher retrieve the page? Check robots.txt, page availability, indexing controls and server responses.
Selection: Does the brand, domain or page appear in answers for a fixed set of relevant prompts? Record mentions and citations separately because an answer can name a brand without linking to it.
Visit: How many detectable referral sessions arrive from ChatGPT, Perplexity, Gemini, Claude and other identified LLM sources? Break them down by source and landing page.
Outcome: How many of those visits produce the event that matters to the business, such as a purchase or qualified lead? Keep that event definition consistent across channels.
Those figures are useful orientation, not a forecast for your site. Industry, audience, analytics configuration and the definition of a conversion can all change the result. A small channel can also produce a high rate from very few conversions, so report the numerator and denominator: sessions, conversions and conversion rate.
Be exact about traffic share. LLM referral sessions divided by all referral sessions measures the channel’s share of referral traffic. LLM referral sessions divided by all site sessions measures its share of total acquisition. A result below 2% of referral traffic cannot automatically be restated as below 2% of all site visits.
Your working report should include the following fields:
LLM source
Landing page
Referral sessions
Defined conversion event
Number of conversions
Conversion rate using a documented denominator
Visibility or citation status for the relevant prompt group
Notes on page updates, crawler changes, PR activity and distribution
Keep the LLM source group editable. The mix of platforms and the pages cited in answers can change, so a report hard-coded around one provider will become incomplete. Referral analytics also measures detectable clicks, not every citation or unlinked mention. A zero in the referral column does not prove zero AI visibility.
Make each important page easy to retrieve and cite
AI search optimization does not replace SEO. The companies operating generative AI products also invest in technical SEO, content, conversion paths and organic acquisition. For your site, the same foundation determines whether a useful answer is available in a form that machines and people can understand.
Use a citation-ready page pattern
Give the page one clear job. Target a specific question, task or decision instead of combining several loosely related intents.
Answer before expanding. Put the direct answer near the start, then explain conditions, exceptions and evidence. Do not make a reader hunt through a long preamble.
Label the useful units. Descriptive headings, lists and genuine comparison tables make definitions, steps and distinctions easier to locate.
Separate fact from recommendation. State what is documented, what depends on context and what you recommend. This prevents a conditional claim from looking universal.
Offer value beyond the extracted answer. Original examples, methods, tools, templates or deeper supporting detail give an interested user a reason to visit the page.
Match the next action to the query. A visitor who arrived for a technical answer should see a relevant technical next step, not a generic request to contact sales.
Do not neglect basic on-page signals. Clear meta titles, useful descriptions, readable URLs, accurate tags and descriptive image names are among the technical and content elements associated with stronger search discovery. They will not force an AI system to cite you, but missing or vague signals create avoidable ambiguity.
Distribute one consistent evidence set
A strong page can still remain isolated. Align SEO, social distribution, PR and supporting content around the same canonical evidence rather than publishing disconnected versions of the claim. A unified SEO, social, PR and content strategy gives the brand more consistent language, mentions and paths back to the page you want treated as the primary resource.
Start with the canonical page. Give it the complete answer and supporting detail. Supporting articles can address narrower questions and link back to it. Social posts can surface individual findings without changing their meaning. PR outreach can point to the same evidence when it is genuinely relevant. Keep the brand name, product names, category language and core claims consistent across these surfaces.
Consistency does not mean copying the same paragraph everywhere. It means that the entity, claim and destination remain stable while the format changes for each channel. If five pages compete to be the definitive version, you have made source selection harder for search systems and readers alike.
Choose Claude crawler rules by purpose
AI training access and AI search visibility are separate decisions. Anthropic identifies three Claude user agents with different functions, so blocking one does not automatically block the others.
User agent
Purpose
What blocking changes
ClaudeBot
Collects public web content for model training.
Excludes the disallowed pages from this training crawl. It does not by itself block user-requested retrieval or search indexing.
Claude-User
Fetches a page when a user asks Claude to access information that requires it.
Prevents those user-initiated fetches from retrieving disallowed pages, which can remove your content from relevant response workflows.
Claude-SearchBot
Indexes material used to improve Claude search results.
May reduce the visibility or accuracy of your content in Claude-enhanced search responses.
If you want to block only the training crawler across the site, the directive is:
User-agent: ClaudeBot Disallow: /
Create a separate group for every bot you intend to control. If your subdomains have different policies, publish the appropriate robots.txt file on each one. Anthropic’s bots support standard directives including Disallow and Crawl-delay.
Do not use broad public-cloud IP blocking as a substitute for a precise crawler policy. These bots can operate through public cloud infrastructure, so an IP-level rule can affect unrelated traffic and may interfere with access to robots.txt. Save the previous file, verify the exact user agent and path you are changing, fetch the live robots.txt after deployment, and inspect server logs for the expected behavior. A misplaced site-wide rule can materially reduce discovery.
Run a monthly cycle around the weakest stage
Do not begin each month by asking how to get more AI traffic. Begin by locating the bottleneck. The answer determines whether you need analytics work, a crawler change, a better page or stronger distribution.
Save the baseline. Record LLM sessions, landing pages, conversions, conversion rates and results from a stable set of commercially relevant prompts. Preserve raw counts.
Check access. Review robots.txt, page availability, indexing controls, canonical destinations and the Claude user agents that match your policy.
Improve the highest-intent weak page. Clarify its answer, heading structure, metadata, evidence and next action. Log the publication date so a later change can be connected to the work.
Coordinate distribution. Point relevant supporting content, social activity and PR toward the canonical page while keeping the core entity and claim consistent.
Review by source and landing page. Compare the new period with the saved baseline, but do not call a percentage change meaningful without looking at the underlying session and conversion counts.
Use the pattern of results to choose the next action:
No appearances and no visits: investigate access, page relevance, answer clarity, internal discovery and external authority. Conversion work is not yet the bottleneck.
Appearances but no detectable visits: treat the citation as visibility, not traffic. Check whether the page offers a compelling reason to continue beyond the generated answer. Some informational prompts will naturally produce few clicks.
Visits but no conversions: inspect the landing page’s intent match, offer and next step. More citations will amplify the same conversion problem.
Conversions from low volume: protect the working page and expand into closely related high-intent questions. Do not assume the observed conversion rate will remain unchanged as volume grows.
Traffic without known visibility: confirm the referral classification and add the source and landing page to your monitored prompt set. Your visibility measurement may be missing a real route into the site.
Start with one report, one explicit crawler decision and one high-intent page. Annotate each change. The next monthly review will then tell you which stage moved and where the next unit of effort belongs, even while total LLM traffic remains small.
Analyzing nearly two million LLM sessions across nine industries throughout 2025 was a fascinating journey for me. I began with the assumption that ChatGPT would dominate and that AI usage patterns would be relatively uniform with minimal impact.
The findings, however, were surprising.
While ChatGPT does indeed control 84.1% of the trackable AI discovery traffic, it’s primarily serving as a broad-market tool. This discovery significantly impacts strategic approaches.
In today’s landscape, relying solely on a single discovery strategy is not viable. A multi-platform approach that aligns with how and where users find productivity is essential.
Brands must now discern which platforms are empowering productivity rather than merely supporting initial discovery phases.
Various LLMs are excelling in different sectors, often with stark differences. The key takeaway for 2026 is more complex than simply focusing on ChatGPT.
Here’s what I’ve discovered from the data.
The Growth Rate Divergence: ChatGPT vs. Competitors
Throughout 2025, major LLM platforms exhibited significant growth discrepancies:
ChatGPT: 3x growth
Copilot: 25x growth
Claude: 13x growth
Perplexity: 1x growth
Gemini: 1x growth
Although ChatGPT grew, Copilot and Claude experienced much more rapid growth. Platforms like Perplexity and Gemini remained steady, reinforcing specific workflows.
These numbers highlight strategic priorities:
Satya Nadella celebrated Copilot reaching 100 million monthly users.
Dario Amodei revealed that Anthropic’s revenue grew from $100 million to $8–10 billion in under two years.
Aravind Srinivas noted significant interest in Perplexity Finance.
The focus on growth is crucial because it signals true user value:
Copilot excels in the Microsoft ecosystem.
Claude appeals to developers.
Perplexity thrives among finance professionals.
Different LLMs are thriving in various industries at markedly different rates.
Pattern 1: Copilot’s Striking Growth
Copilot’s remarkable 25x growth is indicative of its premier position in B2B environments reliant on Microsoft tools.
SaaS
ChatGPT: 2x growth
Copilot: 21x growth
The rapid adoption mirrors modern SaaS practices, embedding LLMs directly into workflows.
Education
ChatGPT: 6x growth
Copilot: 27x growth
Copilot benefits from educational settings fostering knowledge sharing and synthesis.
Finance
ChatGPT: 4.2x growth
Copilot: 23x growth
Finance aligns with Copilot due to automation needs and context dependency.
Copilot’s growth is most pronounced in industries where professionals are deeply integrated with Microsoft tools.
Instruments like Excel transform into data interpretation powerhouses with Copilot, eliminating the need for external searches.
Implications
For work-centric audiences like SaaS, finance, and education specialists, AI discovery is shifting into LLMs embedded in workflows.
Pattern 2: Perplexity Shines in Finance
While Perplexity has flat growth overall, it stands strong in finance with a 24% market share, unlike in other sectors where it has diminished.
SaaS: down to 7.3%
E-commerce: down to 3.4%
Education: down to 5.2%
Publishers: down to 3.6%
Finance demands accuracy; thus, traceable sources make Perplexity vital in this sector.
Partnering with Benzinga, FactSet, and others, Perplexity offers in-depth data vital for financial decisions.
Trust and verifiability are crucial in finance, and that’s where Perplexity excels.
Implications
In finance, selection of platforms that integrate with licensed data and credible sources is critical. Success hinges on being part of these authoritative ecosystems.
Pattern 3: Claude’s Dominance in Analysis
With just a 0.6% share, Claude might appear to be an underdog, but it thrives in specialist sectors like publishing and finance.
Publishers: 49x growth
Education: 25x growth
Finance: 38x growth
SaaS: 10.3x growth
Claude’s strength lies in standalone, strategic thinking rather than integrated tools like Copilot.
Publishing professionals and financial analysts use Claude for its substantial context window, enabling complex and strategic queries.
Implications
Target audiences that require in-depth analysis should focus on creating structured and detailed content. Claude’s user base is smaller but highly influential.
Pattern 4: Challenges in Tracking Gemini
The data concerning Gemini is puzzling, showing both growth and declines. This could be attributed to issues with attribution rather than an actual decline in users.
Education: −67% tracked traffic
SaaS: +1.4x growth
Finance: +1.3x growth
E-commerce: +2.7x growth
Gemini’s interaction model keeps users within its ecosystem, making measurement challenging.
The reality is that usage might still be robust, but the tracking systems need to catch up with user behaviors.
Implications
As AI-assisted conversions increasingly occur, traditional last-click attribution models need reconsideration.
Monitor brand search performance and invest in broader visibility strategies.
Strategizing Your LLM Approach
AI discovery is diversifying rather than converging. Tailoring strategies based on your audience’s preferences and behaviors is crucial.
Enterprise Audiences: Focus on Copilot integration for SaaS and B2B environments.
High-Stakes Decisions: Consider Perplexity’s reliability in providing traceable data.
