·

A merchant hides a long spec table on mobile through their theme’s visibility toggle. It looked cluttered on a small screen. Nobody thinks twice about it, because the page still looks clean on both. Then rankings for that product slide, and nobody connects it back to the toggle. That toggle is the real gap in most stores’ mobile seo strategy. It isn’t a missing tag or a slow load time, but content that simply isn’t there when Google looks.

By Florencia

September 15, 2026

6 min read.

Want to know which of your product pages are missing target keywords in their mobile-visible content? Plug In SEO‘s Scanner audits your stored titles, descriptions, and meta content. You decide what to add.

Try Plug In SEO →

Google only sees what your mobile page actually shows

The bottom line: Google indexes your mobile page, not your desktop page. Content that exists on desktop but not on mobile is content Google simply doesn’t see.

Google’s own documentation states this plainly: only the content shown on the mobile site is used for indexing. If a mobile page carries less content than its desktop counterpart, Google warns merchants to expect real traffic loss. This isn’t a minor technical footnote. It’s the core mechanic of mobile-first indexing, and it means a “cleaner-looking” mobile page can quietly cost you rankings if that cleanup removed real content rather than just reorganizing it.

“Only the content shown on the mobile site is used for indexing.” If your mobile site has less content than desktop, Google explicitly warns to expect traffic loss.

Google Search Central, mobile-first indexing documentation.

Where the content actually goes missing

The bottom line: Shopify’s own theme editor doesn’t include a native hide-on-mobile-only toggle. Where one exists, it came from a premium theme feature, custom CSS, or a page-builder app — and that’s exactly where content parity breaks.

Shopify’s default theme editor doesn’t ship a built-in way to hide one section on mobile while keeping it on desktop. Some premium themes add that toggle as a feature. Some merchants add it through custom CSS. Page-builder apps like Shogun offer it directly. None of these are wrong to use. But every one of them is a real, identifiable point where a merchant chose to simplify the mobile view, and that choice is exactly what creates the content-parity gap Google warns about.

Desktop and mobile diverge

Product spec table

Full spec table shown on desktop. On mobile, a visibility toggle hides it in favor of a short summary line, to keep the page from feeling cluttered.

Content parity restored

Product spec table

Same full spec table on both. On mobile it’s reformatted into a shorter, tappable layout instead of hidden entirely — the content stays in the page Google actually indexes.

This is a different problem than hidden accordion content

The bottom line: content collapsed inside an accordion or tab is still indexed at full weight. Content removed from the mobile DOM by a visibility toggle is not there at all. Those are two different problems with two different fixes.

It’s easy to conflate these. Our own guide on hidden content and SEO covers the accordion case: content that’s visually collapsed but still present in the page’s HTML gets indexed the same as fully visible text. This post covers a different mechanism entirely. A mobile-only visibility toggle doesn’t collapse content, it removes it from what renders on mobile at all. Google’s mobile crawler never sees it, regardless of how it would look if expanded.

Tap targets have a real, checkable number

The bottom line: the practical minimum tap target size is 48 by 48 CSS pixels, with roughly 8 pixels of spacing between targets.

“Make buttons bigger” isn’t an actionable instruction. 48×48 CSS pixels is. That’s roughly the size of an average fingertip’s contact area, and it’s Google’s own recommended minimum. A button or link doesn’t need to look that large visually. Padding around a smaller icon can bring the tappable area up to size without changing how the page looks.

Speed is a separate mobile factor worth a mention

Content parity and tap targets are structural issues. Speed is the other half of mobile SEO, and it’s a bigger drag on mobile than desktop since mobile connections and processors are usually slower. That’s a large enough topic to deserve its own read — see our image compression guide for the biggest lever most stores are missing. This post stays focused on the indexing and tap-target side of mobile SEO, not a second speed deep-dive.

What to check on your own store

A real mobile seo strategy comes down to a short checklist, run against your product and collection pages:

  1. Check every section’s visibility settings for a mobile-only hide toggle. If your theme or a page-builder app has one, confirm nothing load-bearing (specs, sizing info, key selling points) is set to hide on mobile only.
  2. Reformat instead of removing. If a section genuinely feels cluttered on mobile, restructure it into a shorter or tappable layout rather than hiding it outright.
  3. Measure your primary tap targets against 48×48 CSS pixels. Add padding around small icons rather than shrinking the tappable area to match a small visual element.
  4. Test on an actual phone, not just a resized browser window. A resized desktop browser doesn’t always reproduce what a real mobile viewport renders.
  5. Don’t confuse this with accordion or tab content. That’s a separate, already-solved case — Google indexes collapsed content at full weight as long as it’s present in the page.

Where Plug In SEO fits

Plug In SEO’s Scanner audits your stored product titles, descriptions, and meta content for missing target keywords. It can’t see which sections a mobile-only visibility toggle has hidden, since that’s a theme-rendering decision, not stored page data. But it will tell you whether the content that does reach both desktop and mobile actually carries your target keywords.

Frequently asked questions

Does Google index my desktop page or my mobile page?

Your mobile page. Under mobile-first indexing, Google explicitly states that only the content shown on the mobile site is used for indexing. Content that exists only on desktop is invisible to Google’s ranking systems.

Does Shopify have a built-in way to hide sections on mobile only?

Not natively. Shopify’s default theme editor doesn’t ship a hide-on-mobile-only toggle. Where one exists, it’s usually a premium theme feature, custom CSS, or a page-builder app add-on.

Is this the same issue as content hidden in an accordion or tab?

No. Accordion or tab content stays present in the page’s HTML and gets indexed at full weight even when visually collapsed. A mobile-only visibility toggle removes content from the page entirely on mobile, so Google’s mobile crawler never sees it at all.

What’s the minimum tap target size for mobile SEO?

48 by 48 CSS pixels, with about 8 pixels of spacing between targets. You can hit that by adding padding around a smaller visual icon rather than enlarging the icon itself.

Can Plug In SEO detect content hidden by a mobile visibility toggle?

No. Its Scanner audits stored page content like titles, descriptions, and meta fields, not theme-level rendering decisions like a mobile-only hide toggle. Checking your theme’s section visibility settings directly is a manual step.

Check your stored content for missing keywords

Plug In SEO’s Scanner audits your titles, descriptions, and meta content for missing target keywords. Pair it with a manual check of your theme’s mobile visibility settings for full coverage.

Try Plug In SEO →