SEO & Content LLM Prompts Intermediate

Mobile Seo Auditor

Audit and optimize mobile experience to ensure your site ranks well on mobile search results.

Best Model
ChatGPT GPT-5.5 + Perplexity Sonar for current researchResearch-grounded SEO
Brevity Mode
Detailed
Difficulty
Intermediate
Automation
Needs user context

Use This When

Articles, service pages, AEO/GEO content, interlinking, SERP-informed briefs.

Inputs Needed

URL, target keyword, audience, competitors, location, search intent, internal links, products/services.

Expected Output

SEO brief or content draft with search intent, outline, on-page elements, internal links, FAQ, schema suggestions.

The Workflow Prompt

Copy-paste ready. Replace [bracketed placeholders] with your specifics.
You are a technical SEO strategist and editorial content lead.

Objective:
Mobile Seo Auditor

Context:
Audit and optimize mobile experience to ensure your site ranks well on mobile search results.

Original task:
You are a world-class mobile SEO expert who has optimized mobile experiences for 2,000+ companies, resulting in 25-50% mobile traffic increases and improved mobile rankings. Your expertise spans mobile-first indexing, mobile UX signals, mobile Core Web Vitals, mobile-specific technical issues, and mobile search optimization. You understand Google's mobile-first approach intimately.Conduct a comprehensive mobile SEO audit for [YOUR_DOMAIN]. Provide:1. **Mobile Indexing Assessment**: Confirm Google's mobile-first indexing status; analyze mobile crawl activity in Search Console2. **Mobile Usability Audit**: Test mobile rendering, navigation, tap targets, text readability, and viewport configuration3. **Mobile Core Web Vitals**: Analyze mobile-specific LCP, FID, CLS metrics; identify mobile-specific optimization opportunities4. **Mobile Speed Analysis**: Conduct mobile speed audit; identify mobile-specific bottlenecks (3G/4G constraints, device limitations)5. **Mobile-Specific Content Issues**: Identify content not rendering on mobile (tables, embedded content, forms)6. **Mobile Navigation**: Audit mobile menu, navigation structure, and internal linking for mobile users7. **Mobile Conversion Optimization**: Analyze mobile UX for conversion funnel (CTAs, forms, checkout flow)8. **Mobile Interstitials**: Identify problematic interstitials that block content or harm mobile UX9. **Mobile Structured Data**: Verify schema markup renders correctly on mobile; check for mobile-specific rich results10. **Mobile-Specific Features**: Audit click-to-call, location features, and mobile-specific functionality11. **Tablet Optimization**: Assess tablet experience; recommend responsive design improvements12. **Mobile App Indexing**: If applicable, recommend App Indexing implementation and deep linking strategy13. **Mobile Traffic Analysis**: Analyze mobile traffic patterns, user behavior, and mobile-specific pain points14. **Implementation Recommendations**: Provide prioritized mobile UX improvements with mobile traffic impact estimation

Inputs I may provide:
URL, target keyword, audience, competitors, location, search intent, internal links, products/services.

Operating instructions:
- First, restate the objective in one clear sentence.
- If critical information is missing, ask up to 5 focused questions. If there is enough information to proceed, make practical assumptions and label them.
- Use a Detailed response style.
- Be specific to the business, audience, channel, and constraints provided.
- Avoid generic AI advice. Give concrete recommendations, examples, templates, copy, or steps I can use.
- When current facts, competitors, laws, prices, policies, or market claims matter, use current research and cite sources.
- Do not expose hidden chain-of-thought. Provide a concise rationale or decision summary instead.
- End with a short QA checklist that helps me verify the output.

Required output:
SEO brief or content draft with search intent, outline, on-page elements, internal links, FAQ, schema suggestions.

Caution:
Avoid generic output; require concrete examples, assumptions, and next steps.

QA Follow-Up Checklist

After the AI returns its output, verify against:

  1. Output is specific to the provided business/context.
  2. Assumptions are clearly labeled.
  3. No unsupported claims without source checks.
  4. Next actions are clear and usable.
  5. Search intent, internal links, FAQ, and on-page elements are included.

Follow-Up Prompt

Run this next to refine the first output into a client-ready version.
Now turn the result for 'Mobile Seo Auditor' into a client-ready version: tighten wording, remove fluff, add missing assumptions, and provide the next 3 actions.

Avoid / Cautions

Avoid generic output; require concrete examples, assumptions, and next steps.

How Different Verticals Use This Workflow

Restaurant & Hospitality

A restaurant chain with 80% of traffic from mobile audits and finds the mobile menu is loaded as an image (unreadable to Google), the reservation widget breaks on iOS, and the location finder requires desktop-style hover interactions. The audit recommends rebuilding the menu in HTML, swapping the reservation widget, and a tap-friendly location finder. Mobile organic traffic lifts 34% in 90 days and online reservations climb 22%.

Retail & E-commerce

A DTC brand audits and discovers their mobile PDP hides product specs behind a 'see more' accordion that defaults closed, hides reviews behind a tab, and removes related products entirely. Google's indexing the stripped version. The fix is to make all content visible (just visually compressed) on mobile. Mobile organic to PDPs lifts 27% over 4 months and the affected pages move up an average of 4 positions for product-related queries.

Professional Services & B2B

A B2B SaaS audits and discovers their mobile homepage removes the customer logo wall, three testimonials, and a comparison section that exists on desktop. The mobile version is 40% lighter on content. The fix is a responsive redesign that retains all content with mobile-appropriate formatting. Branded search impressions lift 18% in 90 days and the site picks up featured snippets for two key category terms.

Beauty & Personal Care

A skincare brand audits and finds the mobile site has a perpetual coupon banner that pushes the H1 below the fold and obscures product imagery. Google's signal: the page's primary content is the banner. The fix is a dismissible banner that respects the fold and doesn't fire on bot traffic. Mobile organic conversion improves 16%, primarily on PDPs where the banner had been most aggressive.

Local & Trade Services

A regional contractor audits and discovers their mobile contact form has 9 fields when desktop has 4, the click-to-call button is below the fold on iPhone, and the location page has no map embed on mobile. The fix is a 3-field mobile form, a prominent above-fold call button, and a Google Maps embed. Mobile form submissions lift 38% and click-to-call up 52% — translating to ~$1.2M annual incremental pipeline.

Frequently Asked

What's the most overlooked mobile SEO issue that kills rankings?

Differential content between desktop and mobile. Google indexes the mobile version — if your mobile site hides FAQs, collapses content, or removes internal links 'for a cleaner mobile experience,' Google sees the stripped-down version as your full content. Audit your mobile vs. desktop HTML side-by-side; if mobile is missing more than 10% of the body copy or links, that's likely your ranking problem.

How much of my SEO traffic is realistically from mobile?

60-75% for B2C, 35-50% for B2B. If your analytics shows under 50% mobile traffic for B2C, you have a tracking or speed problem suppressing mobile sessions. The mobile audit should start with: does your real mobile traffic match your category benchmark? If not, you have a mobile experience problem before you have a mobile SEO problem.

Should I build a separate mobile site (m.example.com) or responsive?

Responsive, always, in 2026. The separate mobile site era ended a decade ago. If you still have one, the audit should prioritize migrating to responsive — separate mobile sites split authority, create canonicalization headaches, and underperform on Core Web Vitals because they're usually older code. The migration is painful for 2 weeks and beneficial for 5 years.

When is a mobile-specific audit unnecessary?

If your site already passes mobile Core Web Vitals on 80%+ of pages and your mobile-vs-desktop conversion ratio is in the normal range (within 30% of desktop), a mobile-specific audit produces marginal improvements. Spend the time on content gaps or link acquisition instead — both have higher leverage at that point.

Related Workflows

Copied to clipboard