← All recipes
Auditintermediate~30 seconds

Audit mobile vs desktop performance gaps

Find pages where mobile rankings or CTR diverge sharply from desktop — usually a Core Web Vitals or mobile-UX fix.

The prompt

Copy this and paste it into Claude, Cursor, or any AI client connected to your GenieSeo MCP URL.

prompt
For my main Search Console property, run a mobile vs desktop split analysis over the last 28 days:

1. For each page with at least 500 impressions on EITHER device, calculate average position and CTR for mobile and desktop separately.
2. Flag pages where mobile position is ≥3 places worse than desktop, OR where mobile CTR is ≥30% lower (relative).
3. For the top 5 most-affected pages by total impressions, run URL Inspection and report the mobile usability verdict and any flagged issues.
4. Summarise which kinds of pages are most affected (templates, content type, sitewide vs isolated).

Format: tables for the data, prose for the diagnosis.

When to use it

Quarterly, or after any mobile redesign. Mobile-first indexing means a mobile-only regression hides behind aggregated numbers.

What you get back

  • Table of pages where mobile vs desktop position differs by more than 3 places, with both positions and impression counts.
  • Same comparison for CTR.
  • Top 5 affected pages annotated with URL Inspection's mobile usability findings.

How this runs

GenieSeo doesn't execute prompts — your AI client does. Make sure your MCP URL is connected to Claude, Cursor, Codex, or Antigravity. New here? Read the 60-second setup guide.

Tags

  • mobile-first
  • core-web-vitals

Frequently asked questions

How do I run the "Audit mobile vs desktop performance gaps" prompt?+

Sign up for GenieSeo, connect Google OAuth, paste your MCP URL into Claude or Cursor, then copy the prompt from this page into a new chat. The model will call the relevant Search Console or GA4 tools automatically.

Does this recipe change my Google data?+

No. This recipe only uses read-only Search Console and GA4 scopes. It will not submit sitemaps or modify properties unless you use a separate write-enabled recipe.

What is a GenieSeo recipe?+

A recipe is a copy-paste prompt you run inside Claude, Cursor, or Codex after connecting your GenieSeo MCP URL. It tells the model which Search Console or GA4 tools to call and how to format the answer.

Do I need GenieSeo connected before using a recipe?+

Yes. Sign up at GenieSeo, approve Google OAuth, paste your personal MCP URL into your AI client, then paste the recipe prompt. Without MCP, the model cannot reach live Google data.

More audit recipes