WordPress 7.0 is out: the 7 highlights of this release

On May 20th, 2026, the next major release of WordPress came out: WordPress 7.0. While previous releases focused on improving the block editor, this release takes it to a new level. It pushes the platform into the next phase of its roadmap with smarter workflows and a more app-like experience. So, let’s dive into what’s new and what features are interesting for you.

A modern admin experience

WordPress 7.0 introduces a refreshed admin interface. One thing that’s been changed is the new way to transition between pages in your backend. When navigating to another page, this now looks a lot smoother than before, thanks to the CSS View Transitions API. The new update also comes with a new addition to the menu bar at the top, called the Command Palette shortcut. When you click on this icon (or use the shortcut ⌘K or Ctrl+K), you get easy access to the command palette that allows you to navigate your backend or perform other actions from that bar.

Command palette in adminbar WordPress 7.0
The Command Palette in the menu at the top.

Although it’s a seemingly small thing, another cool thing to mention is the new color palette. As you can see in the screenshot above, the default color scheme has changed. The palette previously known as ‘Modern’ is now the new default, better aligning the admin with the visual direction of the block and site editor. If you preferred the old look, don’t worry, it’s still available under your profile preferences, now listed as ‘Fresh’.

Overall, these improvements and others give a fresh look and feel to the backend of your website. With the intent of making WordPress feel less like a traditional CMS and more like a modern web app.

Revisions are now more visual

Whenever you need to check or restore an earlier version of a page, the revisions in WordPress help you do so. These give you an idea of what has been changed on your page and when. Now, WordPress 7.0 makes this even easier with visual revisions instead of the raw text shown until now.

Visual revisions in WordPress 7.0
An example of the visual revisions in WordPress 7.0

The revisions feature can be found in the same spot as before, and now, when you click it, it takes you to a preview of your page, where you can use the slider at the top to view earlier versions. The slider also shows you the date and time of the change. When looking at an earlier version of the page, additions are shown in green, changed sections in yellow, and deleted sections in red. Allowing you to locate the changes made right away.

As before, this allows you to quickly restore previous versions of a page, find the source of layout issues and review updates. This visualization of the revisions makes it easier to do so, as you won’t have to dive into the text to figure out what changed. You’ll notice it right away when sliding between revisions.

New blocks in the block editor

As expected, the block editor has also gotten some new additions with the release of WordPress 7.0. For starters, the new Breadcrumbs block lets you add breadcrumbs to your pages, improving navigation on your site. When added, it automatically adds the correct breadcrumb path to the top of your page, but it also gives you options to customize it. The other new block in this release is the Icon block. This allows you to add icons to your pages from a directory of icons added to the backend.

Directory of Icons for Icon block WordPress 7.0
Current selection of icons you can use in the Icon block.

There are also some improvements to existing blocks, such as the Grid Block and Cover block. The Grid block used to have an Auto/Manual toggle, but this has now been replaced by several options to help you set the responsiveness of the block and columns shown. The Cover Block now includes the option to use embedded videos as the background, so you can display videos from platforms like YouTube there. These new blocks and improvements continue to further reduce the need for plugins and custom work to achieve the desired design.

Better responsive design controls

Designing for mobile just got a little bit easier. This latest version of WordPress introduces viewport-based controls, allowing you to show or hide blocks depending on the user’s screen size. Simply go to the block, click ‘Show’ in the toolbar and select which devices should show the block (desktop, tablet, or mobile). This will automatically hide it on the devices that you don’t select. This allows you to fine-tune your design for different devices and build responsive designs without using custom CSS. A big win for anyone building sites without relying heavily on code.

Smarter pattern editing

Patterns and templates now come with different editing modes to make changes without accidentally messing up the design. When selecting a pattern, the List View will show you all the text and image elements in that pattern. This allows you to focus on the content-focused elements and change those where needed. However, when you click ‘Edit pattern’, it will also show you the remaining elements (design elements such as spacers), so you can still adjust those. This helps users focus on content optimization, while still giving the option to make changes to the design or layout if needed.

Edit pattern from the list view in WordPress 7.0
A list view showing the content and image elements in a pattern, with a button to edit the pattern further.

This new approach makes it a bit easier to customize patterns to fit specific use cases across your website.

Connect to AI tools of your choice

WordPress 7.0 doesn’t come with any AI-powered tools, but it is laying some groundwork. It comes with a Connectors section below Settings in your WordPress backend. Here you can connect to external integrations, including AI providers or agents. This allows you to connect to Claude, Gemini, OpenAI, and more. You can search the directory if the integration you’re looking for isn’t listed right away.

Connectors settings in WordPress 7.0
The Connectors section in your WordPress settings

This gives you one central place to maintain any integrations that your website or plugins need to connect to by API keys or other credentials. In addition, this gives developers a future-proof ecosystem and standardized framework to work with.

A new list filter for plugins

WordPress 7.0 adds a filter that allows plugins to register custom tabs on the Plugins screen. This enables grouping plugins under a custom tab with a proper label. For example, thanks to this feature we were able to add a dedicated “Yoast” tab on the Plugins screen. This groups all Yoast plugins on that website in one view, making it easier for site admins to check versions, manage activation, and keep the overview of their Yoast suite.

Final thoughts

As always, these are just a few highlights. New blocks, smarter workflows, a modern admin and AI foundations. There’s a lot more we haven’t discussed here. For example, performance was not ignored in this release. Particularly, client-side media processing (faster uploads, less server strain), continued improvements to block rendering, and responsiveness. These changes help WordPress scale better, especially for media-heavy sites. It’s also worth noting that WordPress 7.0 raises the minimum PHP version to 7.4.

Still to come: real-time collaboration

Originally, the real-time collaboration feature was going to be shipped in this release. But a short while back it was decided to postpone the release of this feature to ensure the stability of this release. This feature will probably be part of a future release.

But for now, we can get going with the new features in WordPress highlighted above! So, go update to the latest version or dive into more details in the release post on WordPress.org.

The post WordPress 7.0 is out: the 7 highlights of this release appeared first on Yoast.

Read more at Read More

12 Best Google Analytics Reports Used by Expert Marketers

Key Takeaways

  • Google Analytics 4 (GA4) replaced Universal Analytics in July 2023 and introduced a completely redesigned reporting interface. 
  • Standard reports are pre-built and cover everyday metrics like traffic and engagement. Explorations is a separate section for custom analysis, such as funnels and path analyses. 
  • Not every report deserves equal attention. The ones worth checking regularly are those tied to a specific question you’re trying to answer. 
  • Checking a focused set of reports on a consistent schedule is more valuable than occasionally auditing everything at once.

If you’ve ever opened Google Analytics 4 and felt overwhelmed, you’re not alone. 

GA4 replaced Universal Analytics in July 2023 and introduced a completely redesigned interface. With hundreds of data points across dozens of Google Analytics reports, it’s hard to know which ones are worth your time.

The good news? You don’t need to look at everything. 

I’ve narrowed it down to the 12 best Google Analytics reports. These are the ones worth including in your metrics. I’ll also show you exactly where to find them in GA4 and how to put the data to good use.

What to Look for in a Google Analytics Report

GA4 organizes its reporting into two main categories: standard reports and explorations.

  • Standard reports are pre-built templates that live under the Reports section in the left-hand navigation menu. They simplify your performance analysis because they’re ready to use from the get-go and cover most of the user data you’d want to see, such as traffic and engagement.
  • Explorations live under Explore and are a separate section for more custom analysis. They go beyond standard reports, covering metrics like funnels and path analyses. They’re more powerful but require more setup. Think of standard reports as your regular dashboard and explorations as your analysis workspace.

The best reports are tied to a specific question you’re trying to answer. Where are users coming from? Which pages drive engagement? Where do people drop off before converting?  

If a report doesn’t connect to a decision you can make, it’s not worth prioritizing right now.

GA4 left-hand navigation showing the Standard Reports section and the separate Explorations section

The Best Google Analytics Reports for Marketers

Here are the 12 reports worth having on your regular radar, along with where to find them in GA4 and how to act on what they show.

1. User Acquisition Report

The user acquisition report shows how new users find your website for the first time. It’s broken down by channel: organic search, paid, social, direct, and referral. It’s your clearest read on which marketing efforts are growing your audience.

User acquisition tracks how users were first acquired, while the traffic acquisition report (which we’ll cover next) shows where sessions come from, including those from returning users. 

If paid traffic looks strong in traffic acquisition but weak here, you’re likely good at re-engaging existing users but struggling to reach new ones. And that’s a different problem requiring a different fix.

Where it lives: Reports > Acquisition > User Acquisition.

GA4 User Acquisition Report showing channel breakdown for new users, including organic search, paid, and social

2. Traffic Acquisition Report

GA4’s traffic acquisition shows where each visit comes from, not just how someone first found you, making it a better tool for week-over-week trend monitoring. 

As a Google Analytics SEO report, it’s useful for quick diagnostics. For instance, you might use it to compare a specific date to historical performance or conduct a channel-by-channel scan.

A dip in organic traffic while other channels hold steady might point to a ranking change or technical SEO issue, not a site-wide problem. That distinction’s a big deal for deciding how to respond.

Where it lives: Reports > Acquisition > Traffic Acquisition.

GA4 Traffic Acquisition Report showing all sessions by channel with a period-over-period date comparison

3. Pages and Screens Report

Pages and screens reports break down page views, average engagement time, and other engagement metrics by individual page or screen (individual screens on a mobile app). 

These are foundational content marketing analytics data points. They make a solid starting point for understanding which posts are pulling their weight and which aren’t. You can sort by views to find high-traffic pages, and then cross-reference the engagement rate.

For example, a page driving strong traffic but showing low engagement might signal a mismatch between what users expected and what they found. That’s a page worth auditing before creating more content on the same topic.

Where it lives: Reports > Engagement > Pages and Screens.

GA4 Pages and Screens Report showing page views and engagement rate sorted by individual URL

4. Landing Page Report

Unlike the pages and screens report, which measures all page activity, the landing page report focuses on the first page a user lands on during a visit. Landing pages reveal which content is pulling traffic from sources like social or paid campaigns.

A landing page with high sessions and a low engagement rate could be telling you the entry experience doesn’t match what brought users there. That can be where conversion problems start, and it’s the right place to diagnose them before testing other changes.

Where it lives: Reports > Engagement > Landing Page.

 GA4 Landing Page Report showing sessions and engagement rate for each site entry URL

5. Engagement Overview Report

The engagement overview report gives you a quick pulse check on how actively people interact with your site. Use it to monitor engagement trends across your website and spot sudden changes before digging into individual pages or channels.

GA4 emphasizes engagement rate over the old UA bounce rate model. It measures the percentage of sessions that last longer than 10 seconds, involve a key event, or have at least two page or screen views.

According to Databox benchmark data, the median engagement rate across all industries sits at 56.23 percent

That’s a helpful reference point, if not a universal target. A meaningful drop in one traffic channel can signal a content mismatch or a technical issue that’s cutting sessions short (like a slow-loading page).

Where it lives: Reports > Engagement > Overview.

GA4 Engagement Overview showing engagement rate, engaged sessions, and average engagement time across the site

6. Events Report

GA4 tracks user interactions as events, including page views, clicks, form submissions, and other actions you configure. 

The events report shows what’s firing on your site and how often each action occurs. You’ll also be able to see the events you’ve marked as key events, aka conversions. 

Use this report to check your conversion tracking before judging content performance. If a form submission or sign-up isn’t set up as a key event, for example, your content may look like it’s underperforming even when users are taking valuable actions. 

Before you rewrite a page or change your strategy, make sure GA4 is tracking the outcome you care about.

Where it lives: Reports > Engagement > Events.

GA4 Events Report showing tracked events, event count, and Key Event flags

7. Demographic Details Report

Google’s demographic details report is great for seeing whether the people you’re reaching are genuinely your target audience. It breaks down your audience by details like age or interests. This pairs well with acquisition data if you’re monitoring Google Analytics for social media performance.

If campaigns targeting 35- to 54-year-old professionals are generating traffic that skews heavily under 25, that demographic mismatch shows up here before it turns up in the conversion numbers. That gives you a chance to correct targeting before spending more.

Where it lives: Reports > User Attributes > Demographic Details.

GA4 Demographic Details showing age, gender, location, and interest breakdown of site visitors

8. Tech Overview Report

Mobile accounts for more than half of global web traffic, which means a mobile performance problem can quickly become a revenue problem. The tech overview report is where you look to find those problems.

Sort by device category and compare conversion rates between mobile and desktop. A significant gap might indicate slow load times or a layout that doesn’t translate well to smaller screens. 

Browser breakdown is worth checking, too, since compatibility issues often affect more users than you might expect.

Where it lives: Reports > User > Tech > Tech Overview.

GA4 Tech Overview Report showing user breakdown by device type, browser, and operating system

9. Key Event Attribution (Conversion) Paths Report

Key event attribution is one of the more revealing Google Analytics SEO report views in the platform, showing how organic search contributes across multi-touch journeys.

Last-click attribution models give all the credit to the final channel a user touched before converting. The key event attribution paths report (formerly the conversions report) provides a fuller view, showing the touchpoints a user interacted with along the path to a conversion.

If social or display advertising consistently appears early in conversion paths, those channels deserve budget even when they don’t earn last-click credit. 

Where it lives: Advertising > Key Events > Key Event Attribution Paths

GA4 Attribution Paths Report showing the sequence of channels users interact with before converting

10. Search Console Report

Once you link Google Search Console to GA4, you can view organic search data inside Analytics. Metrics like queries and clicks are all tied to the landing pages they lead to. 

The Console-GA4 combination puts this among the most actionable Google Analytics SEO reports.

You can see which queries drive traffic to specific pages and where impression numbers don’t match click-through rates. The report can also uncover which pages rank but don’t convert. 

Each data point provides key context, enabling you to fix multiple tracking issues all in one place.

Where it lives: Reports > Acquisition > Search Console (requires linking Google Search Console to GA4).

GA4 Search Console Report showing organic search queries, impressions, clicks, and average position by landing page

11. Realtime Pages Report

This report shows which pages people are viewing right now and how many users are on each page. It’s less useful for strategic analysis than the others on this list, but it’s genuinely valuable as a QA tool. 

Say you’ve just pushed a campaign live. You can confirm tracking is firing before you make future spending decisions. 

Realtime can also help you confirm whether new posts or key event changes are working before standard reports catch up.

Where it lives: Reports > Real-Time.

GA4 Real-Time Report showing current active users, pages being viewed, and live event data

12. Retention Overview Report

Retention is where sustainable growth happens. The retention overview report shows whether users return to your site after their first visit and how engaged they are after they’re acquired. It’s broken down by cohort over time.

Getting people to come back builds compounding authority and revenue. A declining retention curve can reveal gaps in content quality or user experience issues. 

These trends are worth investigating before pushing harder on acquisition, because more traffic will only amplify these issues.

Where it lives: Reports > Retention.

GA4 Real-Time Report showing current active users, pages being viewed, and live event data

When to Use a Google Analytics Report Template

GA4 lets you customize reports and save them in your library. That way, you can reuse reports without rebuilding them each time. 

If you or your team need to share performance data with clients or leadership, Data Studio (formerly Looker Studio) is usually the better option.

Data Studio is Google’s free data visualization tool and connects directly to GA4. You can also use pre-built Google Analytics report templates from providers like Supermetrics and Porter Metrics. These ready-made dashboards cover key data, including traffic overviews and ecommerce performance. 

Templates let you stand up a shareable, auto-refreshing dashboard without building from scratch, a real time-saver for anyone reporting to stakeholders who don’t log into GA4 directly.

Example dashboard incorporating data from multiple ad platforms, including Google and other popular social media channels.

FAQs

How do I create reports in Google Analytics?

GA4 includes pre-built reports in the left navigation under Reports. To build a custom report, go to Reports > Library and select “Create new report.” For deeper analysis, like funnel exploration, use the Explore section. This operates separately from standard reports and offers more flexible visualization options.

How do I automate Google Analytics reports?

GA4 doesn’t offer native scheduled report delivery, but Data Studio (formerly Looker Studio) handles this cleanly. Connect your GA4 property, build or copy a template, then use the scheduled email feature to send reports at your preferred cadence automatically. Tools like Porter Metrics and Supermetrics extend this further for agencies managing multiple properties or clients.

Conclusion

GA4 populates a ton of data points. It’s on marketers to sift through the noise and boil things down to the reports that move the business needle.

A good place to start is picking two or three Google Analytics reports from this list that fit your current business goals. 

If growing organic traffic is your focus, you might begin with the Search Console and traffic acquisition reports. If conversion rate is the priority, events and attribution paths can show you where the gaps are.

Whatever reports resonate with your business case, build a review cadence and stick to it. The more consistent you are, the easier it is to spot patterns and make better calls.

Read more at Read More

Google Search Universal Cart, expands UCP and AP2

Google also announced some new agentic commerce features today in Google Search including Universal Cart, expanding Universal Commerce Protocol and Agent Payments Protocol (AP2).

Plus, Google’s Shopping Graph now contains 60 billion product listings, which is up from 50 billion from earlier this year, announced Vidhya Srinivasan, VP/GM Ads & Commerce.

Universal Cart. Google announced what it is calling the Universal Cart, where you can put products and items from multiple retailers into one single Google Universal Cart and check out on all those items with your Google Wallet with the click of a button.

As you are on Google Search, you can add items directly to your Google Universal Cart without having to go to a specific retailer’s website. This will work across Google Search, Gemini, YouTube and Gmail, so just keep throwing items in your cart – across Google interface and retailer and the cart will maintain your list.

Here is a screenshot of Universal Cart showing multiple retailers:

Google will find the best prices and deals, including which retailer has it in stock and let you check out with your preferred retailer.

Plus, Google said Universal Cart will “anticipate your needs and help solve problems before they.” Google’s example:

“Say you’re building your first custom PC and add a few parts from several retailers to your cart. Your cart will proactively flag any product incompatibilities and suggest alternatives. Since the cart was built on Google Wallet, it understands your payment method perks, loyalty information and merchant offers to help you choose. This lets you quickly find opportunities for hidden savings or points without having to remember them yourself.”

Merchants. Google listed a number of merchants that support this, including Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair, and Shopify merchants such as Fenty and Steve Madden.

Availability. This is available in Google Search and the Gemini app in the U.S. starting this summer and with YouTube and Gmail later on.

UCP and AP2. Google expanded the Universal Commerce Protocol on Google to Canada and Australia in the coming months and in the U.K. later on. UCP will also be coming to YouTube and more Google verticals including hotel booking and local food delivery.

Agent Payments Protocol (AP2) helps agents make payments for you, securely and with accountability, Google said. “Just tell your agent the specific brands and products you want and how much it can spend, and the agent only makes the purchase when your criteria are met,” Google explained.

Google will launch AP2 to Google products in the coming months, starting with Gemini Spark.

Read more at Read More

Google lets you build your own app within Google Search with agentic coding

Google is now letting searchers build their own apps directly into Google Search. This enables searchers to set up a search feature that delivers the information they need, in the format they want, from the sources they want.

Liz Reid, the head of Google Search, announced at Google I/O, “Search can build the ideal response, in the right format for your question – completely on the fly. So you can get custom generative Ul, including visual tools and simulations, tailored precisely to your needs.”

Examples. Here are a few examples of what you can code yourself into Google Search:

(1) Whether you want to wrap your mind around astrophysics or visualize how your watch works, Search can design custom layouts, assembling components (like interactive visuals, tables, graphs or simulations) in real-time, Google wrote.

(2) Ongoing tasks widgets, like planning a wedding or managing a home move. Search can go a step further, building you custom dashboards or trackers that you can continue to come back to and make progress on. You can think of these like mini apps for your own specific tasks, Liz Reid explained.

(3) Fitness tracker in Search, where you can ask Google Search to build you a custom fitness tracker. Search will code it for you, tapping into fresh, real-time sources including reviews, live maps and local data like the weather, so you get a tracker that works for you, helping you stay on track week after week.

What it looks like. Here are some examples of what this looks like in Google Seaerch.

Generative UI example:

Custom tracker example:

Availability. The generative Ul capabilities will be available for everyone in Search this summer, free of charge.

The custom experiences with Antigravity, like mini apps, right in Search in the coming months, starting first for Google Al Pro and Ultra subscribers in the U.S.

Why we care. Google Search will not just answer your questions but you can code your own mini apps within Google Search to give you the answers you want, in the format and style you want.

This is really a unique way for search and likely can only be done with generative-AI features and tooling.

Read more at Read More

Google Search gains information agents and improved agentic experiences

Google also announced new search agents, including information agents and new agentic capabilities within Google Search. The information agent will continue to scan the web to find and monitor changes to your tasks and help you along your tasks journey.

“We’re entering the era of Search agents, where you can easily create, customize and manage multiple Al agents for your many tasks, right in Search,” Liz Reid, the head of Google Search said.

Information agents. The information agents will help you stay on top of your questions and tasks. Google said the agent will “intelligently look across everything on the web, like blogs, news sites and social posts, plus our freshest data, such as real-time info on finance, shopping and sports, to monitor for changes related to your specific question.”

The information agent will then send you “an intelligent, synthesized update, with the ability to take action.”

The example. Here is the example Google provided:

“So if you’re apartment hunting, you can brain dump all of the exact requirements you’re looking for, and your agent will continuously scan for you, notifying you when listings meet your needs. Or if you want to know the instant any of your favorite pro athletes announce a sneaker collab, your agent will let you know when a new drop lands so you don’t miss out.”

Availability. This will first roll out in the summer to Google Al Pro & Ultra subscribers.

Agentic experiences. Google is also expanding its agentic booking capabilities in Google Search to handle new tasks including things like local experiences and services. So if you want to find a place that has a private karaoke room for a specific time and night, that also serves specific food, you can use Google Search to book that place for you.

Google will pull together the latest pricing and availability with direct links for your to purchase it.

This works across home, repair, beauty or pet care and will roll out this summer in the U.S.

Personal intelligence expanding. Google also announced it is expanding Personal Intelligence in AI Mode to about 200 countries and territories and 98 languages.

Read more at Read More

Google Search now powered by Gemini 3.5 Flash

Google announced its latest and greatest AI model, Gemini 3.5 Flash today at Google I/O. Google’s head of Search, Liz Reid, said Gemini 3.5 Flash is Google’s “newest Flash model delivering sustained frontier performance for agents and coding.” She added that is now being used to power AI Mode globally.

Gemini 3.5 Flash. Not only is Gemini 3.5 Flash powering AI Mode in Google Search, but it is also powering the Gemini app, for all users, not just paid users.

For developers, 3.5 Flash is now live in Google Antigravity, Gemini API for Google AI Studio and Android Studio and for enterprise users for Enterprise Agent Platform and Gemini Enterprise.

Koray Kavukcuoglu, CTO of Google DeepMind and Chief AI Architect, said:

  • “Gemini 3.5 Flash delivers intelligence that rivals large flagship models on multiple dimensions, at the speeds you have come to expect from the Flash series.”
  • “It’s our strongest agentic and coding model yet, outperforming Gemini 3.1 Pro on challenging coding and agentic benchmarks like Terminal-Bench 2.1 (76.2%), GDPval-AA (1656 Elo) and MCP Atlas (83.6%), and leading in multimodal understanding (84.2% on CharXiv Reasoning).”
  • “When looking at output tokens per second, it is 4 times faster than other frontier models. Landing in the top-right quadrant of the Artificial Analysis index, 3.5 Flash delivers frontier-level intelligence at exceptional speed — proving you no longer have to trade quality for latency.”

Why we care. Gemini 3.5 is already powering Google Search’s AI Mode and is likely soon to power AI Overviews. It is a step up from the previous AI model and will continue to get smarter and more useful.

It is important for you to see how the AI Mode responses differ from the previous model for the queries and prompts that matter to your site.

Search is changing rapidly and you need to stay on top of these changes.

Read more at Read More

Google’s new intelligent Search box – its biggest change to the search box in 25 years

Google unveiled the biggest change to its search box in 25 years. It is calling the new search box the “Intelligent Search box.” The new search box aims to bring easier access to the AI search features in Google Search to Google’s users.

And yes, this is all powered by the latest Gemini release, Gemini 3.5 Flash.

What it looks like. Google redesigned this search box to give searchers more space to ask longer, deeper queries. The search box will continue to expand as the user enters the query or prompt. There is an AI-powered suggestion that Google’s Head of Search, Liz Reid, said “goes beyond autocomplete.”

Plus, you can search with text, images, files, videos or your Chrome tabs.

Here is what the new intelligent search box looks like:

This puts Google’s “most powerful AI tools right at your fingertips, making it easier to ask your questions,” Liz Reid of Google said.

Seamless Google Search to AI Mode. Google also said it made the AI Overviews seamless link approach to AI Mode live today globally both on desktop and mobile. This is something that launched to many back in January but is now fully live.

Here is how this works:

Why we care. The Google Search box looks and feels different and that might be a big deal to how it leads to how users search on Google. It might impact the type of search traffic Google has been sending you and will send you in the future. It might lead to more people jumping to AI Mode sooner from Google Search and it might lead to more AI Overviews with deeper answers. It might lead to fewer clicks to your web site than before.

Change is not always easy, but it is inevitable, especially when it comes to Google Search.

Sundar Pichai, Google’s CEO told us that the extraordinary thing about Search is how people search and expect more from Google Search.  Search is evolving, from individual queries to ongoing conversations and now to agentic workflows.  Search is the most used product in the world, Sundar said and Google will evolve super hard to stay a step ahead of where our users want to be.

Read more at Read More

Web Design and Development San Diego

The funnel query pathway: A framework for measuring AI visibility

The funnel query pathway- A framework for measuring AI visibility

The question I get asked most in 2026 is: How do we measure this?

  • How do we measure whether our brand is showing up in ChatGPT? 
  • How do we measure whether Perplexity is recommending us? 
  • How do we measure whether the work we did last quarter on grounding for AI Mode moved the needle?

Nobody has solved this.

Anyone selling you a clean dashboard for tracking presence in grounding, visibility in display, or action at won across search, assistive, and agent simultaneously is selling you a snapshot view that amounts to a bad best guess.

The standard advice is “track these queries that we think people might ask,” or “track these queries that are a best-guess adaptation of search keywords.” 

That advice is unhelpful because prebuilt keyword lists pick queries that are easy to track, map to existing marketing efforts, or would be ideal if the audience were predictable. 

The visibility question is right. The precise-number answer it expects is wrong.

The measurement question, as the industry currently frames it, uses the wrong reference discipline. Brands still hunting for the perfect AI-era visibility KPI are hunting for something that doesn’t exist and never will.

The right answer is a methodology that takes its discipline from how economists measure systems too complex and opaque to measure precisely. My methodology is the Funnel Query Pathway, and it does more than measurement. It’s one operational artifact that does three jobs simultaneously: strategy, measurement, and analysis.

Marketers want a number on a dashboard, tracking week over week, tied to a specific query on a specific engine for any user, the way search delivered for 20 years. Search could deliver that number because the surface was finite, the rankings were stable, the click was measurable, and the journey was observable. Assistive and agential surfaces deliver none of that.

We’re operating in a new environment now, and that environment forces us to ask different questions, measure different signals, and act on different proof.

Your customers search everywhere. Make sure your brand shows up.

The SEO toolkit you know, plus the AI visibility data you need.

Start Free Trial
Get started with

Semrush One Logo

Why AI visibility is a macro measurement problem

I studied economics and statistical analysis at Liverpool John Moores University, which is why the shape of this measurement problem looks familiar. The same shape shows up whenever a discipline that worked at one scale tries to operate at a scale where its instruments stop applying. 

Microeconomics versus macroeconomics is the canonical case. The corner shop measures inventory precisely, the central bank can’t measure inflation precisely, and both disciplines are correct at their scales. Neither discipline’s instruments work in the other’s environment. The discipline I’m proposing isn’t macroeconomics applied to brands. It’s the macro instinct applied to AI-era brand measurement.

AI surfaces are macro for the same three structural reasons macroeconomics had to develop its own discipline. 

The first is opacity. The system’s internal state isn’t observable, the way central banks can’t observe every transaction and modern LLMs can’t expose why they decided what they decided. 

I call this brand-user-algorithm (BUA) opacity. The user can’t see the alternatives the algorithm rejected, the brand can’t see the journey within the walled garden, and the algorithm can’t fully introspect on why it decided what it did.

The second reason is personalization, the AI-era equivalent of heterogeneous agents: Each user gets a different answer because the engine factors in different context.

The third is the explosion of possibilities, and the explosion isn’t just across the seven engines. The surfaces now include apps (Copilot in Word, ChatGPT inside Slack, Perplexity in Comet), operating systems (Copilot baked into Windows, Apple Intelligence in macOS and iOS), and hardware (Lenovo Copilot+ laptops with a dedicated Copilot key, Samsung Galaxy AI on the phone, and Meta Ray-Bans on your face). 

Ambient research becomes a major entry mode. The AI surfaces a recommendation unprompted because it understands the context. 

That’s where the funnel query pathway lives. Importantly, it isn’t an evolution of keyword mapping or a pimped-up intent-based methodology. Because it looks at the macro level, it’s a fundamentally different beast.

The unit of measurement is a cohort

Most practitioners running keyword campaigns think they’re grouping queries by intent, but more often than not, they’re grouping by category, which isn’t the same thing as intent. A typical Google Ads campaign would place every Phuket hotel query into one ad group, with the implicit logic that “Phuket hotels” is a logical intent group. It isn’t.

“Phuket hotels” defines the destination. The buyer behind “5-star hotels in Phuket” and the buyer behind “cheap hotels in Phuket” share a destination and have almost nothing else in common: different budgets, decision criteria, conversion paths, and downstream behavior. Grouping them produces an ad group whose performance averages across two cohorts that should never have been combined.

Categories group things. Cohorts group people.

Intent is about people, not things. Google engineers tell me this is the most common mistake they see in AI Max and Performance Max campaigns because the algorithm routing a prospect doesn’t ask, “What category is this query in?” It asks, “What cohort does this user belong to, with what intent?”

The intersection of cohort and intent defines the node

A cohort is a group of people who’ll behave in a similar way given a specific stimulus. XL men, luxury travelers, and parents shopping for kids. Each is a cohort, defined by some durable identity that persists across time and context. The XL man is still an XL man when he’s buying winter coats in November, a vacation in July, and a wedding ring in March.

An intent is the situational vector that crosses through the cohort at a moment in time. Buying a shirt, booking a hotel for next month, and kitting out a child for summer. Each is an intent, and each one spans many cohorts. Buying a shirt pulls in XL men, S men, women, and parents shopping for kids, all walking different paths to different brands at different price points.

Every cohort carries many intents across a lifetime, and the same intent spans many cohorts across the market. The intersection of cohort and intent is what defines a node in the Funnel Query Pathway tree. XL men buying a shirt in winter is a node. Luxury travelers booking a hotel for next month is a node. Parents shopping for kids’ shorts for summer is a node.

Importantly, cohort alone doesn’t work because XL men buying pajamas behave differently from XL men buying office shirts or holidays. Intent alone won’t track because luxury travelers booking Bali behave differently from budget travelers booking Bali. The intersection is where behavioral coherence lives, and behavioral coherence is what makes the node trackable in the opaque AI surfaces we’re working with.

The query qualifies for tracking when both cohort and intent are legible in it

The test for whether a query belongs in a funnel query pathway tree is whether both cohort and intent are legible in the query itself. “Men’s red shirt from Uniqlo” surfaces a man shopping for clothes (the cohort) and buying a red shirt at the buying moment (the intent), with the brand named as the commercial destination. Both axes are legible.

“Hotels in Bali” surfaces an intent but hides the cohort (luxury, business, budget, honeymoon, family, backpacker), which is why it can’t function as a node. The people submitting it will behave nothing alike as they work their way down the funnel. Narrow it to “cheap hotels in Bali,” and the budget cohort emerges alongside the intent, and the query qualifies for the funnel query pathway.

The test is behavioral coherence, not specificity. If both axes are clear, it’s a node. If not, narrow it until they are, and you’ll discover the cohort and intent that together make sense to your business.

Build the funnel query pathway from the conversion moment upward

The funnel query pathway doesn’t track what users actually type. It tracks what the cohort would ask given the intent. Every query in the tree is a theoretical representative of cohort behavior at the buying moment, not an empirical record of individual users.

This is the macro discipline in practice. We don’t research search volume for these queries because they aren’t necessarily queries anyone has typed. We construct them by reasoning forward from cohort plus intent, building the ideal pathway a representative member of the cohort would walk.

The “would” carries the entire methodology, and the moment you slip into thinking about what users “actually” type, you’ve collapsed back into the micro instinct the methodology was designed to escape.

Once a query passes the test, it’s your starting point. The funnel query pathway (branching tree) builds upward from there. This mirrors the funnel flip at the query level. AI-era acquisition starts at the conversion moment and projects upward because the algorithm forward-calculates the conversion path from intent, not from awareness.

Start with the ideal branded BOFU query for one cohort with one intent, then project upward through the evaluation questions that cohort would ask, then upward again through the awareness questions that would come even earlier.

Example: Building one funnel query pathway tree from a single Uniqlo query

Take Uniqlo as the brand and “men shopping for clothes” as the cohort. The intent is the situational vector that defines the buying moment, and different intents inside the same cohort produce different trees: men buying a shirt, men buying winter outerwear, and men buying gym kit. Each is a node.

Start with one. For example, pick the intent of buying a red shirt, which I do often. The branded bottom-of-funnel query that fits the cohort-intent intersection is “men’s red shirt from Uniqlo.” That’s the conversion node.

Five to 10 variations of similarly shaped queries fit the same intersection and don’t need to be tracked individually: “men’s Uniqlo Oxford shirt,” “Uniqlo men’s smart shirt,” “men’s red dress shirt Uniqlo,” and “Uniqlo men’s casual red shirt.” Each is the same cohort with the same intent landing on the same brand. Pick the one that’s most useful for your business. Build upward.

Next, find the middle-of-funnel branches that would land at your ideal BOFU query. In our example, “men’s red shirt from Uniqlo,” we’re looking for the evaluation queries the same man would ask the engine before arriving at the branded buying moment. The cohort is still men shopping for clothes, the intent is still buying a red shirt, and the brand isn’t named yet because the cohort is still considering options:

  • “Best red shirt for men”
  • “Red shirt for office work”
  • “Where to buy a quality red Oxford shirt”
  • “Which red shirt looks best with chinos”
  • “Affordable men’s red shirts that don’t fade”
  • “Red shirts for men under €50”
  • “Best affordable clothing brands for men”
  • “Minimalist menswear brands with color ranges”
  • “Where to buy quality basics for men online”
  • “Best affordable men’s shirt brands”

Ten branches, all the same cohort, all the same intent, all logically routing to “men’s red shirt Uniqlo” as the ideal BOFU commercial query for the brand.

Top-of-funnel branches that would land at each of those middle-of-funnel queries are the broader awareness questions the same man would ask even earlier, before narrowing to specific shirt types or brands.

For “best red shirt for men”:

  • “Can men wear red shirts to work”
  • “How to add color to a man’s wardrobe”
  • “Shirt color rules for office wear”
  • “How many shirts should a man own”
  • “Which shirt colors suit men with what skin tone”
  • “What color clothing would make me stand out in a crowd”

That’s one 60-query funnel query pathway. I could’ve included 120 or more. That’s a choice, as we’ll see. As a rule of thumb, 60 is a reasonable number from a budget-versus-insights perspective. The point of the macro approach is that it doesn’t need you to go granular to measure.

One funnel query pathway tree- Uniqlo worked example

The important thing here is that the 60 queries all route to one branded buying moment for one cohort with one intent. Do it again with another intent inside the same cohort (men buying winter outerwear, men buying office trousers), then another cohort (women shopping for clothes, with the intent of buying pajamas, branded BOFU “women’s pajamas Uniqlo”).

The tracking surface is a forest of trees, accumulated as the methodology runs.

Get the newsletter search marketers rely on.


AI routing uses the same math as Google Ads bidding

I discovered this while running keynotes and workshops for Google Marketing Live in Asia Pacific this month, in conversations with senior Google engineers about how Gemini routes recommendations. 

The math Gemini runs to decide which answer to surface next is the same math Google Ads has been running to decide which ad to serve next: forward-calculate the probability that this cohort, with this intent, lands at a conversion, and pick the path most likely to get them there.

Every practitioner who’s bid on a campaign in the last 15 years has been working with that probability calculation. For me, this is the most useful framing the funnel query pathway can inherit, because it explains why the cohort-with-intent unit aligns with the engine’s internal logic. 

The engine isn’t tracking categories or queries in isolation. It’s running a funnel pathway probability calculation on cohort plus intent. Every node you populate teaches the engine which path is the fastest way to get this user to the best solution to their problem.

Ads includes profit margin. Organic doesn’t.

The operational formula in Ads is cohort x intent x conversion rate x profit margin. Google holds all four because the advertiser provides Google with the commercial information needed to optimize bidding. The auction maximizes expected profit because Google has the inputs to calculate it.

The operational formula in organic is cohort + intent + conversion rate. Profit margin drops out because the engine doesn’t have the commercial information. The engine doesn’t know your gross margin on a red shirt versus your gross margin on pajamas, and it doesn’t optimize for your bottom line. It optimizes for user satisfaction, which is its own proxy for engine-level commercial outcome, but not for yours.

The principle holds across both surfaces: cohort + intent + conversion rate is the unit AI algorithms work with best. What differs is the precision of the conversion estimate. In organic, the conversion is inferred from behavioral patterns. In Ads, it’s measured from data provided by the advertiser.

Interestingly, the macro discipline operates in organic where micro precision isn’t available. Micro precision operates in Ads where it is. Luckily, the funnel query pathway tree works on both. Populate it once, and use it for organic content, Ads campaign structure, and analytical insights across both.

Build the funnel query pathway from the conversion moment upward

One terminological clarification in the 15-gate model I’ve built. The AI engine pipeline runs 10 binary gates:

  • Discovered, selected, crawled, rendered, and indexed (DSCRI), which are handled by the bot, invisible to the algorithm.
  • Annotated, recruited, grounded, displayed, and won (ARGDW), which are handled by the algorithm, invisible to the bot.

Our framework extends another five gates after being won: onboarded, performed, integrated, devoted, and codified (OPIDC), which are handled by post-transaction operations that serve people, invisible to both bot and algorithm. 

Fifteen gates total, each a binary checkpoint where the brand either survives or doesn’t.

Nobody inside the system sees the whole chain. Only the brand does. Won itself has three flavors depending on surface: 

  • The imperfect click in traditional search.
  • The perfect click in assistive engines.
  • The agentic click in assistive agents.

The funnel sits on the display gate. The user’s journey from question to purchase moves through three phases at display — awareness, consideration, and decision. Phases are continuous human positions. Gates are binary machine checkpoints. 

The funnel query pathway tracks the queries the user submits across those three phases, with the branded buying-moment query landing at the decision phase that triggers won. Gates and phases aren’t synonyms, and conflating them breaks the methodology. 

Step 1: Start at the bottom of the funnel

Identify the queries your ideal customer profile (ICP) would ideally submit using your brand name at the moment they’re ready to buy. The emphasis is on “ideally.” 

Keyword research asks what people actually type. The funnel query pathway asks what the cohort with this intent would ideally ask the engine just before they purchase from you, with your brand name in the query. Branded, bottom-of-funnel, intent-confirmed, cohort-coherent.

Calibrate the specificity to the cohort definition. “Men’s red shirt from Uniqlo” fits the broad cohort of men shopping for clothes. “Men’s extra-large red shirt from Uniqlo” fits a sizing sub-cohort that behaves differently because size availability constrains the consideration set. Either is fine. Pick the cohort level where you want to operate, then operate consistently upward within the branches of your tree.

Generic keyword research won’t surface these queries because keyword tools optimize for volume, and cohort-with-intent queries are usually low volume by design. You have to know your cohort well enough to write them down yourself. If you can’t write five, your ICP work needs more depth before this methodology will produce results that are actually useful to your business.

Step 2: Project the pathway upwards

Each bottom-of-funnel query branches into multiple middle-of-funnel queries (the evaluation questions the same cohort would ask before arriving at the buying moment), each of which branches into multiple top-of-funnel queries (the awareness questions that would come even earlier). 

Build out gradually, one bottom-of-funnel query at a time. The funnel flip operates at the query level: Generation starts at the conversion query and projects upward, rather than starting at top-of-funnel awareness and hoping the buyer arrives at conversion.

Granularity is cohorts x intents. Tracking is a budget call.

The question of how many trees to build has one answer: as many as the team can populate. The question of how many trees to track has one answer: as many as give you statistically meaningful data.

The starting unit is one cohort with one intent. Men shopping for clothes, with the intent of buying a red shirt. That’s one tree, around 60 queries.

Add intents inside the same cohort (XL men buying winter outerwear, office trousers, and gym kit). Add cohorts (XL women, parents). Cohorts times intents gives the tree count. The numbers scale with the budget:

Cohorts Intents per cohort Trees Approx. queries
1 1 1 60
3 5 15 900
5 10 50 3,000
10 10 100 6,000

What changes with resolution is the precision of the diagnosis. Track three trees, and you have a low-resolution read on three cohort-with-intent intersections. Track 100, and you have a high-resolution read on most of your buying landscape. Both are defensible macro reads because macro is about defining your methodology and scope to reliably read direction and rate of change, rather than specific values.

This methodology means you can start small and build out. Start tracking three Funnel Query Pathways for your most profitable ICP this month, then add another next month. Group them, and you can compare like with like starting today using a macro approach that scales and survives over time.

Populate the tree, and you teach the engine the conversion path

The shaping mechanism is what makes the funnel query pathway more than a measurement methodology. The engine routes recommendations by predicting what comes next for the cohort with the intent. 

When the brand feeds the AI with content that builds logically structured funnel query pathways and answers each node, the engine learns the chain: 

  • Which awareness questions belong to this cohort.
  • Which evaluation questions follow them.
  • Which branded buying-moment query is the conversion answer.

For obvious pathways (red shirts), the algorithms already have the pathways ingrained, but for less popular pathways, the engine has no opinion, and you have every opportunity to shape its perception. 

Since the engine is an active participant in the funnel alongside the user, it can form a predictive map, and the path it surfaces for any prospect in the cohort is the path the brand trained.

Shaping isn’t a side effect. It’s the compounding mechanism, and it means the brand stops competing for individual query rankings and starts engineering the inference paths the engine forward-calculates from. The competitor optimizing query by query is optimizing against a model the engine has already moved past.

The deeper move: Mapping the funnel query pathway into every webpage

The methodology can sit beside the website as a tracking document, and that works, but the deeper move is mapping the funnel query pathway into your strategy, both on-site and off-site.

Every node in every tree corresponds to a query the engine surfaces for the cohort. Every query needs a passage that answers it. Every page names the cohort it’s serving. Every passage names the intent that might bring the cohort there and clearly outlines the next step in the cohort’s conversion path. 

  • Top-of-funnel pages route toward the evaluation pages. 
  • Middle-of-funnel pages route toward the branded buying-moment pages. 
  • Bottom-of-funnel pages close the conversion.

If you can align the content across your brand’s digital footprint to the forward-calculation logic the engine is already running — cohort, intent, awareness layer, evaluation layer, conversion layer — then when the engine forward-calculates the next step for any user in the cohort, the brand’s site is one of the few places that has the complete chain laid out, and the probability calculation tilts in your favor.

Build all the funnel query pathways for your ICP, and you’re teaching the machine exactly what the path looks like for every cohort-intent intersection you serve, while encouraging it to bring the subset of its users who are your ideal audience right to your door.

One framework for strategy, measurement, and analysis

The funnel query pathway does three jobs simultaneously: strategy, measurement, and analysis. 

  • Strategy: You populate every node of the tree with content that proves the answer at that phase of the buying journey: awareness content at the top, evaluation content in the middle, and the branded conversion moment at the bottom. Stop running content generation as a calendar against a keyword list, and start engineering paths that represent your ICP’s buying journey.
  • Measurement: You run the same funnel query pathways across the three modes (search, assistive, and agent) and the engines (Google, ChatGPT, Perplexity, Claude, Copilot, Siri, Alexa, etc.). You can’t track every surface those engines appear on (Copilot in Word, ChatGPT in Slack, Apple Intelligence in iOS, and Copilot+ on a Lenovo laptop are all closed contexts that don’t let you rank-track). But every surface runs the same underlying engine, so your tracking extrapolates to every surface each engine sits inside.
  • Analysis: You can use the pattern of where the brand surfaces and where it doesn’t across the funnel query pathway, by mode and by engine, as the macro view you can rely on for a like-for-like comparison over time.

See the complete picture of your search visibility.

Track, optimize, and win in Google and AI search from one platform.

Start Free Trial
Get started with

Semrush One Logo

What you actually get from the funnel query pathway

Here’s what you actually get from running the funnel query pathway: a quarter-after-quarter read of whether AI is recommending your brand to the right people at the right moment. 

You see direction, momentum, and a record of what’s working. You build, you measure, you analyze, and you adjust. Then you do it again next quarter. The brands that start this discipline now will be the ones AI knows by name in three years.

Pick one cohort, the most strategically important if you have several. Pick one intent inside that cohort. Write five to 10 branded bottom-of-funnel queries that cohort-with-intent would ideally submit at the buying moment (“men’s red shirt from Uniqlo” in our example). 

Pick one and map upward: five to 15 middle-of-funnel queries that would land at it, then three to 10 top-of-funnel queries that would land at each of those. You now have one tree, somewhere between 50 and 200 queries.

Run strategy, measurement, and analysis on the funnel query pathway branches.

  • Strategy: Do you have pages and passages that address each of the nodes? Fill the gaps.
  • Measurement: Run the tree across engines and document where the brand surfaces.
  • Analysis: Where are the gaps clustered, which node is weakest, and which engines are recruiting most consistently?

Build out the content that fills the gaps in your ICP funnel query pathways, and track that set of queries monthly. You’ll see results, and you’ll be able to measure them.

AI-era optimization is about defining your methodology, picking your ICP and tracking, and building and strategizing with a macro mindset, which is the subject of the next article in this series.


This is the 14th piece in my AI authority series. 

Read more at Read More

Web Design and Development San Diego

Reasoning lift: What happens to brand visibility when AI thinks harder

kevin-indig-reasoning-lift-featured-image

AI offers a conversational experience. We use LLMs through chatbots. But no one has yet looked at how citations and mentions evolve in a conversation.

I analyzed data from the Semrush AI Visibility Toolkit to review 20 buyer journeys across four different verticals to compare high vs. low reasoning for ChatGPT5.2.

View embedded content

In this analysis:

  • Why high reasoning cites a nearly different web (only 25.6% domain overlap with minimal) and which source types gain or lose ground.
  • Why TOFU content has a payoff again: Grands cited at the Problem stage are more likely to persist all the way to Selection under high reasoning, and never under minimal.
  • How to split your prompt tracking by reasoning mode so your AI visibility reporting reflects 2 different systems, not an averaged one.

Methodology

Data comes from the Semrush AI Visibility Toolkit, which captures the prompts, citations, and fan-out queries ChatGPT generates per response.

  • We ran 100 prompts twice through GPT-5.2, once with minimal reasoning and once with high reasoning, for 200 total responses.
  • Prompts span 20 buyer journeys across 4 categories (B2B SaaS, Finance, Consumer Tech, Health/Lifestyle), with 5 stages per journey: Problem, Exploration, Comparison, Validation, Selection.
  • Citation rate is the share of prompts where the response cited at least one external source.
  • Average citation counts sources per cited response.
  • Fan-out queries are the sub-queries the model fires internally to research the prompt before answering, surfaced via the Semrush API.

GPT 5.2’s high reasoning cites and searches more

Turn high reasoning on, and the citation rate jumps from 50% to 68% (+18 percentage points), the average sources per response nearly doubles (2.6 to 4.5), and fan-out queries go up 4.6x. High reasoning also pulls from 173 unique domains across the test set vs. 127 for minimal; 99 of those domains never appear under minimal reasoning.

*Citation Rate is defined as the share of prompts where the response cited at least one external source.

This is grounding at its finest. When the model thinks harder, it relies more on web search. Reasoning plays a major role in brand visibility, though we don’t know how many users activate reasoning vs not.

Query intent is a cleaner proxy than user demographics. Free-tier users have reasoning access too, just rate-limited, and ChatGPT auto-routes hard prompts to Thinking mode without the user clicking anything. So the question isn’t who can afford reasoning. It’s which prompts trigger reasoning automatically. 

Multi-criteria comparisons, evaluation frameworks, regulatory and compliance questions, and complex shopping builds are the prompts most likely to fire reasoning regardless of plan. Map your audience by query type, not by paywall status.

High reasoning fires more fan-out queries deeper in the funnel

Users move through problem-solving and purchase decisions in stages, often within the same conversation. The gap between minimal and high reasoning isn’t constant. It scales with where the user sits in the journey.

What the five stages look like in practice. Take a buyer evaluating CRM software:

  • Problem: “How do I know if my sales team needs a CRM?”
  • Exploration: “What types of CRM software exist for B2B SaaS?”
  • Comparison: “HubSpot vs. Salesforce vs. Pipedrive for a 50-person sales team.”
  • Validation: “Is HubSpot worth the price for mid-market B2B?”
  • Selection: “How do I get started with HubSpot Sales Hub?”

The three patterns hold across all 20 journeys:

  • Citation rate climbs through the funnel under both modes, but high reasoning closes the early-stage gap most aggressively: +35pp at Problem, only +5pp at Validation. The model treats early-funnel questions as research tasks when high reasoning is on, whereas it answers-from-memory when it’s off.
  • Fan-out queries peak at Comparison. High reasoning fires 24 sub-queries per response there vs. 5.5 for minimal. Selection runs 15.4 vs. 2.6.
  • Average citations per response peaks at Comparison (9.8 high, 5.8 minimal) and narrows at Selection (4.7 high, 2.6 minimal). The model resembles an hourglass across funnel stages.

At the aggregate level, minimal reasoning fires 245 search queries across 100 prompts. High reasoning fires 1,130. When the model operates with high reasoning, it runs a mini investigation per prompt, and most of the investigation happens at the Comparison and Selection stages.

What does a fan-out actually look like?

A B2B SaaS prompt under high reasoning comparing Salesforce, HubSpot, and Pipedrive for a 50-person sales team breaks into separate queries about API rate limits per vendor, SOC 2 / ISO 27001 compliance, SAML/SSO/SCIM support, webhook architecture, OAuth flow, developer documentation, enterprise pricing tiers, and change-data-capture support. Each becomes its own retrieval. The brand that wins the answer is the one whose documentation surfaces clean for each sub-query, not the one that ranks for the parent prompt.

One prompt becomes eight retrievals

The Selection stage has the widest per-response query variance: 0 to 40 fan-out queries on the same five-stage cohort. The driver is prompt specificity. Bounded prompts (like “should I finance through the dealer at 0% APR or use a bank?” or “draft an RFP to 3 SEO agencies”) run zero queries because the answer’s structure is given. Open-ended product builds (“shopping list for a $3,000 home gym” or “which travel card ecosystem fits our grocery spending?”) run 28 to 40 queries. The Selection stage isn’t bounded by one type of question, and the model’s research effort tracks how many degrees of freedom the prompt leaves on the table.

Stage Minimal: Avg queries High: Avg queries
Problem 0.0 5.2
Exploration 0.8 2.6
Comparison 5.5 24.1
Validation 3.4 9.1
Selection 2.6 15.4

For marketers: Early-funnel visibility is a reasoning-mode story. If your buyers use ChatGPT with reasoning on, problem-stage, and exploration-stage content is in play. If they don’t, you’re effectively invisible until Comparison.

Reasoning affects how brands appear in a conversation

An LLM session is a conversation, not a single query. The question that it opens up: Does a brand cited at the start of the journey carry through to the end? If yes, early-funnel visibility compounds. If not, every stage is a fresh fight.

When a brand gets cited in the Problem stage (step 1), does it survive to the Selection stage (step 5)? When using minimal reasoning: No. Zero journeys show this kind of persistence. In high reasoning: Yes. Brand continuity is maintained in 4 journeys across all 5 stages.

Within a single response, high reasoning also anchors harder on individual sources. 51 of 100 high-reasoning responses cite the same domain more than once in the same answer, vs. 26 of 100 for minimal. High reasoning quotes a source repeatedly when it commits to it.

Brand mentions tell a softer version of the same story. If you loosen the test from cited domain to brand named in the answer text, persistence shows up in 3 high-reasoning journeys (HubSpot across CRM Selection, American Express across Business Credit Cards, Sony and Canon across Mirrorless Camera) and 2 minimal-reasoning journeys (HubSpot, Mercury). Consumer Tech shows up here even though it doesn’t show up in the citation persistence table. Brands like Sony and Canon are mentioned through the conversation without the model linking out to them, which is its own form of category dominance and worth tracking separately.

High reasoning builds a consistent mental model of the solution space throughout a session. The headline finding: TOFU prompts have value. If a brand shows up at the Problem stage, it tends to carry through to Selection. Top-of-funnel content isn’t just brand awareness for AI visibility. It’s a leading indicator of where the model lands at decision time.

Two more implications:

  • All four persistent journeys are in Finance, which suggests persistence rides on the same authoritative-source content (regulatory pages, official brand sites) that drives the +28pp Finance lift overall.
  • For marketers running an account-based or category-creation play, reasoning-mode visibility is the prize. It’s the only mode where early-funnel content compounds into selection-stage citations.

Reasoning mode is a separate search engine

The brand that wins under minimal reasoning is not the brand that wins under high reasoning: 3 in 4 cited domains are different. The mix of source types is different. The stages where citations appear are different.

I’m excited about two findings in particular from this analysis: 

The first is measurement. We need to track low vs. high reasoning in our prompt trackers. It’s best to avoid an aggregate view because the mechanisms are truly different. 

Bad news: This adds more effort and cost to prompt tracking. Good news: We can make prompt tracking a lot more accurate.

The second is funnel stages. In the latest AI Mode user behavior study, I found that users react strongly to shortlists, demonstrating a similar behavior seen with Google’s classic search results where the top result matters most. That result made it seem to me that focusing on BOFU prompts that return shortlists is the game. 

However, now we know there is value in TOFU prompts because of persistence: Brands that appear early in the buyer journey can persist all the way through. The best way to find that out for yourself is to map buyer journeys and track your persistence.

This post first appeared on the author’s website and is republished here with permission.

Read more at Read More

Web Design and Development San Diego

How to build custom SEO reports with Claude Code and Google Search Console

How to build custom SEO reports with Claude Code and Google Search Console

For a long time, SEO reporting revolved around dashboards. When a meeting was on your schedule, you’d spend your day preparing by exporting data from Google Search Console, cleaning it in spreadsheets, and layering charts into Data Studio. 

Now, AI coding agents are changing that workflow. Instead of the manual work that would previously take hours, you can use tools like Claude Code to surface customized data with polished visuals in just minutes.  

Here’s how to turn Google Search Console data into custom reports and speed up your reporting workflow.

What Claude Code can do with GSC data

Claude Code isn’t the same as using Claude in a browser tab. The standard Claude.ai interface works like a regular chatbot. Claude Code, on the other hand, is Anthropic’s terminal-based AI coding assistant. 

It still feels conversational, but instead of living in a browser tab, it can interact directly with files, folders, spreadsheets, and scripts on your machine. It can read exported GSC CSV files, process large datasets locally, generate charts and summaries, analyze trends across pages and queries, and ultimately create structured deliverables from raw data.

Claude Code isn’t simply generating text responses like a chatbot. Instead, it’s creating a local reporting environment that behaves like a lightweight software project. 

Dig deeper: How to turn Claude Code into your SEO command center

Your customers search everywhere. Make sure your brand shows up.

The SEO toolkit you know, plus the AI visibility data you need.

Start Free Trial
Get started with

Semrush One Logo

There’s a learning curve 

Before you can start building beautiful, custom reports, you’ll need to set up Claude Code. If you’re not an engineer or developer, this process can feel overwhelming at first. There is a learning curve, but don’t give up. 

Setup is actually the most time-intensive piece of the process, but it’s a one-time process. Depending on your technical experience, the initial setup may take a couple of hours.

The “reports in minutes” concept really applies after the environment is configured. Once you’re past the initial setup and Claude is connected to GSC, you can run any custom SEO report you want in a matter of minutes.

If you’re in an enterprise environment, this setup process can go faster with a little help from the tech team. If you’re an agency or an SEO consultant, you can always lean on the expertise of in-house developers or engineers or an outside contractor.

Getting started

If you don’t already have one, create an account at Claude.ai. You can sign up with Google, email/password, or enterprise SSO.

Most SEOs using Claude Code for reporting have a paid plan or use Anthropic API access. But you can use a free plan at the time of writing.

Install Node.js

Claude Code runs locally on your machine, so you’ll first need Node.js installed. You can also use it on a Chromebook by activating the Linux subsystem. 

For the purposes of this tutorial, I used a Mac.

Next, download the current LTS (Long-Term Support) version. Once installed, you’ll have access to npm, which is used to install Claude Code.

To verify the installation, open Terminal (Mac/Linux) or PowerShell (Windows) and run:

node -v
npm -v

If both commands return version numbers, you’re ready to continue.

Install Claude Code

Next, install Claude Code globally:

npm install -g @anthropic-ai/claude-code

Once the installation finishes, start Claude Code by running:

claude

The CLI will walk you through authentication and connect to your Anthropic account. After that, Claude Code can work directly with local project folders containing exported SEO data, scripts, spreadsheets, and reporting templates.

Dig deeper: SEO reporting outgrew Data Studio — here’s what comes next

Get the newsletter search marketers rely on.


Establishing the reporting framework

At this point, you’ll be able to interact with Claude Code in the terminal using commands much like you would with an AI chatbot.

To kick off the workflow, I gave Claude a prompt:

  • “I have a marketing meeting coming up, and I want to show our performance from Google Search Console.”
Example SEO report using Claude Code

One benefit is that Claude now becomes an onboarding assistant. Claude will ask a handful of clarifying questions to get started. For example, during the setup process, Claude asked:

  • Whether to use a service account or OAuth credentials to access the Google Search Console API.
  • Which reporting views or marketing priorities mattered most.
  • Where the reporting project should live locally on the machine.
  • Which Google Search Console property to connect to.

Claude also asked where the reporting project should live locally. 

(As an aside, we prefer to store it inside a dedicated code directory rather than a standard Documents folder because development projects can sometimes run into file permission or syncing issues when stored inside cloud-synced folders like Documents or Desktop.)

Next, I established how the visuals will be built before connecting to GSC. 

We like using Observable Framework, an open-source framework for building data apps, dashboards, and reports. 

You don’t necessarily need to follow this exact structure; Claude Code is highly customizable, and you’ll settle into what works for you. 

And remember: if you’re unsure about any next steps, you can just ask Claude, and it will help guide the setup. 

Connecting to GSC

Before Claude Code can start generating reports from live GSC data, you’ll need to connect it to the Search Console API.

This is another technical part of the process, but the good news is that Claude can walk you through much of the setup interactively.

To establish the connection, you’ll need to create a Google Cloud Project (GCP) and configure API credentials.

That setup process typically includes:

  • Creating a Google Cloud project.
  • Enabling the Search Console API.
  • Generating OAuth credentials or API secrets.
  • Adding those credentials to a local environment file.

In larger organizations, your IT or development team may already manage this infrastructure. 

If not, you can still configure it yourself using a standard Google account or Google Workspace account.

Generating reports

Once you’ve finished connecting to GSC, congratulations! You made it through the hardest part. Once setup is complete, your reporting process changes entirely.

You can now focus on the reporting views you want to create, such as: 

  • “Show me the top 10 landing pages that gained traffic this month.”
  • “Create a chart of declining nonbrand queries over the last 90 days.”
  • “Compare CTR trends by device type.”
  • “Show me the top-performing pages from New York last month.”

Claude is now like an on-demand reporting assistant. You simply open the project folder, launch Claude Code, and ask for the charts you need.

In addition, you can be more dynamic in your meetings. 

Instead of building a rigid dashboard ahead of time and hoping stakeholders ask predictable questions, you can generate new views dynamically as questions come up. 

That means you can walk into a meeting, ask Claude for a completely new chart or segmentation, and generate it in minutes rather than rebuilding an entire dashboard manually.

Now let’s look at some reports you might quickly run before your next meeting.

Here’s an example of a custom SEO performance dashboard generated from Google Search Console data. 

While some of these metrics are available inside GSC, building your own report gives you much more flexibility in how trends, comparisons, and supporting metrics are visualized together. 

You could also generate a bar chart with YoY rankings, or a heat map of rankings for keywords by month. Both examples are below.

Example SEO ranking report using Claude Code

What we like to include in our reporting is a combination of scorecards, time-series charts, year-over-year bar chart comparisons, and heat maps that break down the key drivers behind a metric. 

See the complete picture of your search visibility.

Track, optimize, and win in Google and AI search from one platform.

Start Free Trial
Get started with

Semrush One Logo

Claude Code completely transforms SEO reporting

SEO reporting has always been a push and pull between speed and flexibility. 

Dashboards are fast once they are built, but they are often rigid. Custom analysis is powerful but historically has been time-intensive. 

Claude Code changes everything. 

Now you can interact with your GSC data more dynamically, explore new questions as they arise, and create reporting views that would have previously taken hours to build manually. 

Once the initial setup is complete, reporting becomes far more adaptable to the needs of you and your stakeholders. 

Dig deeper: How to vibe-code an SEO tool without losing control of your LLM

Read more at Read More