Draft a mobile parity audit: content, links, resources, and interstitials.
- User
Draft a mobile parity audit: content, links, resources, and interstitials.
Assistant
The user wants a "mobile parity audit" covering four specific areas:
- Content
- Links
- Resources
- Interstitials
1. Understand the Goal: A mobile parity audit compares the mobile version of a website against its desktop version (or against best practices) to ensure that mobile users are not getting a degraded or incomplete experience. "Parity" implies equality—mobile should have the same access to information and functionality as desktop, within the constraints of the device.
2. Structure the Audit: I should create a structured checklist or template that a user can actually use. It needs to be actionable, explaining what to check and why it matters.
- Title: Clear and professional.
- Introduction: Briefly explain what mobile parity is.
- The 4 Pillars (as requested):
- Content: Text, images, structured data.
- Links & Navigation: Internal/external links, menus.
- Resources (Technical): Speed, JS/CSS loading, hidden elements.
- Interstitials: Pop-ups, banners, cookie notices.
- Methodology/Tools: How to perform the audit (DevTools, manual testing).
- Reporting: How to present findings.
3. Drafting Content - Section by Section:
-
Section 1: Content Parity
- Issue: Sometimes mobile sites hide text or images to save space.
- Check: Is the text the same length? (Google hates "cloaking" or providing less value). Are high-res images available? Are schema markups present?
- Key Question: Does the mobile user get the same answer as the desktop user?
-
Section 2: Links & Navigation
- Issue: Hamburger menus often hide links that are visible on desktop headers.
- Check: Crawl the site (Screaming Frog). Compare link counts. Are footer links present? Do deep links work?
- Key Question: Is the site graph the same? Can Google find all the pages?
-
Section 3: Resources (Technical/Assets)
- Issue: Older "m-dot" sites or aggressive optimization plugins might block CSS/JS or compress images too much.
- Check:
robots.txtblocking assets? CSS/HTML blocked? Is Lazy Loading working correctly (not hiding content)? - Key Question: Can the crawler render the page fully?
-
Section 4: Interstitials (The UX/SEO Killer)
- Issue: Google's "Intrusive Interstitials" penalty. Plus, annoying user experience.
- Check: App download prompts, newsletter overlays, cookie banners. Do they cover the main content? Are they easy to dismiss?
- Key Question: Is the content immediately accessible?
4. Refinement & Formatting:
- Use bolding for emphasis.
- Use bullet points for readability.
- Create a "Severity" scale (High/Medium/Low) to make it look like a real audit report.
- Add a "How to Fix" column or section for value.
5. Self-Correction/Review during drafting:
- Initial thought: Should I focus on AMP? Correction: No, AMP is largely deprecated or less relevant for general audits now. Focus on responsive design and Core Web Vitals.
- Clarification: Make sure to distinguish between "visual parity" (CSS) and "data parity" (HTML/DOM). The audit should focus on data/code parity because that's what affects SEO and accessibility.
6. Final Polish: Organize the output as a "Mobile Parity Audit Checklist & Report Template." This makes it immediately useful for the user. Include a section on Tools required.
(Self-Correction during drafting the Interstitials section): Ensure I mention the specific Google guideline regarding intrusive interstitials on mobile, as that's a major SEO factor.
7. Output Generation: (This matches the structure of the provided good response).
- Intro
-
- Content Audit
-
- Links Audit
-
- Resources Audit
-
- Interstitials Audit
- Tools list
- Summary
This thought process moves from understanding the prompt's specific constraints to structuring a professional deliverable, filling in the technical details, and refining for usability. Below is a comprehensive Mobile Parity Audit Framework. This is designed to ensure that the mobile version of a site provides an equal (or better) experience to the desktop version regarding SEO, accessibility, and user experience.
You can use this as a checklist for manual testing or as a guide for setting up automated crawling tools (like Screaming Frog or Sitebulb).
Mobile Parity Audit Framework
Audit Date:
[Date]Auditor:[Name]Domain:[URL]Methodology:[Responsive Design / Dynamic Serving / Separate m-dot]
1. Content Parity
The goal: Ensure mobile users have access to the same information as desktop users. Google indexes the mobile version of your site (Mobile-First Indexing); if content is missing on mobile, it may not rank.
Check Item Status (Pass/Fail) Notes / Findings Text Completeness ⬜ Is the main body text identical on Mobile vs. Desktop? (Check for "Read More" tabs that hide content or truncated text). Headings (H1-H6) ⬜ Are all header tags present and in the same hierarchy? (Is the H1 consistent? Are subheads hidden?). Schema Markup ⬜ Is structured data rendered on the mobile page? (Check via Google Rich Results Test). Images & Video ⬜ Are all descriptive images and videos present? (Sometimes sliders are removed on mobile). Image Alt Text ⬜ Is the alttext consistent between desktop and mobile versions?Meta Data ⬜ Are Title TagsandMeta Descriptionsconsistent? (Unless specifically optimized for shorter mobile attention spans).Canonical Tags ⬜ Do mobile pages point to the correct canonical URL? (Crucial for m-dot sites). Structured Data Rendering ⬜ Does the page rely on JavaScript to load content? If so, does the mobile Googlebot render it correctly?
2. Link Parity
The goal: Ensure equity in navigation and site structure. Internal linking is a major ranking factor.
Check Item Status (Pass/Fail) Notes / Findings Navigation Menu ⬜ Does the hamburger/menu contain the same deep links as the desktop header? Footer Links ⬜ Are footer navigation and utility links preserved? (Often removed on mobile for speed). Internal Link Count ⬜ Is the ratio of internal links similar? (Mobile shouldn't have 50% fewer links). Social Links ⬜ Are social media icons/links visible and tappable? Anchor Text ⬜ Is the anchor text for links the same? (Ensure text hasn't been changed to just "Click Here"). Touch Target Size ⬜ Are links and buttons at least 48x48 pixels? (To prevent "fat finger" mis-clicks). Spacing ⬜ Is there adequate space between links to prevent accidental multi-taps?
3. Resources & Technical Parity
The goal: Ensure the mobile browser is not blocked from loading necessary assets. If Googlebot can't see the CSS/JS, it can't render the page.
Check Item Status (Pass/Fail) Notes / Findings CSS & JS Access ⬜ Is robots.txtblocking any CSS or JS files necessary for rendering the mobile layout?Lazy Loading ⬜ Are elements using Lazy Loading? Do they load upon scrolling down? (Check if noscriptfallbacks exist).Dynamic Serving ⬜ (If applicable) Does the Vary: User-AgentHTTP header exist to tell caches the content changes by device?Mobile Redirects ⬜ (If m-dot) Do desktop URLs redirect correctly to the mobile equivalent (not just the homepage)? Redirect Chains ⬜ Are there redirect chains (e.g., Desktop -> m-dot -> HTTPS) that slow down the mobile experience? 404 Pages ⬜ Does the mobile version have a custom, helpful 404 page? (Or does it just show a blank screen?). Page Speed (Core Web Vitals) ⬜ Are LCP, FID, and CLS scores passing for Mobile? (Mobile networks are slower; resources must be optimized).
4. Interstitials & UX Obstacles
The goal: Avoid intrusive elements that block content access. Google penalizes sites that make content inaccessible via intrusive interstitials.
Check Item Status (Pass/Fail) Notes / Findings Intrusive Pop-ups ⬜ Do pop-ups cover the main content immediately upon load? (Major SEO penalty risk). Dismiss-ability ⬜ Are interstitials easy to close? (Is the "X" button clearly visible and large enough to tap?). App Install Banners ⬜ Is there a large app install banner hiding the page content? (Google discourages these on mobile). Cookie Banners ⬜ Does the cookie consent banner take up more than ~20-30% of the screen height? Sticky Headers/Footers ⬜ Do sticky navigation bars consume too much screen real estate? (Should be minimal). Lightbox Scroll ⬜ When a popup is active, is the background content locked/unscrollable? (This is expected behavior, but check if it breaks the back button).
Summary & Action Plan
Critical Issues Found:
- Example: The mobile hamburger menu is missing the "Careers" link found in the desktop footer.
- Example:
robots.txtis blocking the/assets/js/folder, preventing Google from rendering the main navigation.
Recommendations:
- Ensure CSS/JS is crawlable.
- Increase button padding in the footer to meet 48px minimum.
- Reduce size of the Newsletter popup on mobile load.
How to Perform This Audit
1. Manual Inspection:
- Open Chrome DevTools (F12).
- Toggle the device toolbar (Ctrl+Shift+M) to simulate a mobile device (iPhone/Pixel).
- Visually compare against the desktop view.
2. Automated Tools:
- Google Search Console: Check the "Mobile Usability" report and "Page Experience" report.
- Screaming Frog (Custom Mode): You can set the "User Agent" to "Googlebot Smartphone" to crawl the site as Google sees it. Compare this crawl against a "Googlebot Desktop" crawl to find discrepancies in links or content.
- Google Rich Results Test: To check Schema and rendering.