The Scenario
It's the Monday after a mobile UX sprint that shipped three weeks ago. Your team redesigned the checkout flow, optimized the product page tap targets, and cut the mobile page weight by 40%. Everyone's waiting to know if it moved the needle in search.
You work in UX research at a retail company. You've been handed the responsibility of making the case — or not — for the mobile work. The data lives in Google Search Console, split by device type. The problem is that extracting device-split performance for your top 50 landing pages in a format that your engineering team's weekly metrics sheet can absorb is not a one-click operation.
The bad version:
- Pull the Search Console export for "Desktop" — one CSV. Pull the export for "Mobile" — another CSV. Pull the export for "Tablet" just in case.
- Try to join them in Google Sheets by URL, discover that the URL formats are slightly inconsistent across the three exports, spend 25 minutes on normalization.
- Calculate the CTR delta by device type in a new column manually, format it, and then realize you also need position data to tell the full story — which means going back and pulling three more exports.
The sprint shipped three weeks ago. The metrics sheet gets updated every Monday. You've been staring at CSVs for two hours.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads what's already there, talks to Google Search Console through its built-in integration, and writes device-split performance data exactly where you need it.
Your landing page list is already in column A of the "UX Metrics" tab. Paste this:
Fetch Search Console data for the last 30 days grouped by device and page for my site showing clicks, impressions, and position for each combination, and write it into the "Device Performance" tab of my Google Sheet
What You Get
- Each device-page combination populates one row: URL, Device, Clicks, Impressions, CTR, Average Position.
- Device values are "DESKTOP," "MOBILE," and "TABLET."
- The full dataset across all pages — not capped at the UI's top 1,000 rows.
- If you asked for only the URLs from column A, only those rows appear, fully matched.
- No manual join required. The data arrives in a structure your team can pivot immediately.
What If the Data Is Not Quite Ready
You want mobile and desktop as separate columns on the same row rather than separate rows
Pull Search Console device performance for my top landing pages (listed in column A of my "Pages" tab) for the last 30 days and write the results with one row per URL and separate columns for desktop clicks, desktop CTR, mobile clicks, and mobile CTR — flag any URL where mobile CTR is more than 2 percentage points below desktop CTR
You need to limit to only the pages that were part of the mobile sprint
Get Search Console device-level performance for the last 30 days for only the URLs listed in column A of my "Sprint Pages" tab, write the results into "Sprint Metrics" with device, clicks, impressions, and position, and add a column showing the CTR gap between mobile and desktop
You want to compare two time periods to measure the sprint's impact
Fetch Search Console device performance for my site for the 30 days before April 1 and the 30 days after April 1, write both datasets side by side in my "Before vs After" tab, and calculate the percentage change in mobile CTR for each page
The full analysis in one pass — pull, compare, flag, summarize
Pull Search Console data for my site grouped by device and page for the last 30 days, write it into "Device Data," then on a second tab called "Mobile Summary" list all pages where mobile impressions exceed 200, calculate the mobile vs desktop CTR gap, sort by gap descending, and write a note in column E if the gap is over 3 percentage points: "Mobile UX review needed"
One prompt covers the data pull, the comparison, the filter, and the annotation.
Try It
Get the 7-day free trial of SheetXAI and open the Google Sheet where your UX or performance metrics live. Ask it to pull device-split Search Console data for the pages you care about — so you can walk into the Monday metrics review with the mobile vs desktop story already written. See also page-level performance or the hub overview.