Is hidden content in mobile menus really considered for SEO?

What does Google mean by "content revealed through interaction"?

This refers to any element that requires a click, a tap, or a swipe to appear. Hamburger menus, FAQ accordions, navigation tabs, modals triggered by a button — in short, any commonly used mobile-first interface pattern.

Historically, Google has long regarded this content as secondary or even invisible. Mobile-first indexing has changed the game: the engine now simulates user interactions to discover what lies behind these interactive elements. Mueller confirms that this content counts for indexing, putting an end to years of uncertainty on the practitioner's side.

What’s the difference between "revealable hidden" and "permanently hidden"?

Revealable hiding means content is technically accessible via JavaScript, CSS, or HTML. A user can access it by clicking — the bot can too. The DOM contains the information; it’s just not visible by default.

Permanently hidden content is different: text with display:none without any trigger, content with font-size:0, divs off-screen with no scroll possible. In short, disguised cloaking techniques. Google makes it clear that this is not acceptable. The distinction is fine but critical.

Why is this clarification happening now?

Because mobile-first indexing has been widespread for several years, and mobile UX patterns have become standard. Sites that hid "important" content in accordions due to mobile space constraints understandably questioned: are we shooting ourselves in the foot regarding SEO?

Mueller decides: no, as long as it’s revealable through legitimate user interaction. This frees designers and developers who can now optimize mobile UX without sacrificing indexing. But it also means Google is closely monitoring attempts to manipulate through abusive hiding.

• Content in dropdowns, accordions, and tabs is normally indexed if accessible through interaction
• Permanently hidden content (display:none without a trigger, invisible text) remains a punishable blackhat practice
• Google simulates interactions to discover hidden content — its crawler executes JavaScript and detects event listeners
• The line between UX optimization and SEO manipulation depends on real accessibility for the user
• This rule mainly applies to mobile-first indexing, but the principle also holds for desktop

Is this statement consistent with field observations?

Overall yes, but with important nuances. Tests show that Google actually indexes the content in accordions and mobile menus — we see it in featured snippets that regularly pull from FAQ accordions. This confirms that the bot does execute JavaScript and detects content.

However, we still observe a differentiated SEO weight. Immediately visible content seems to have a greater impact than content hidden three tabs deep. Google has never said that "indexed" = "weighted equally". Mueller's statement remains deliberately vague on this critical point. [To be verified] on high-volume sites to measure the real impact.

Where exactly is the limit of "content never visible"?

Let’s be honest: the phrasing "avoid permanently hiding content that would never be visible" is deliberately vague. What is "never visible"? A closed accordion by default that 95% of users never open? A hamburger menu at the 4th level of depth?

The real limit is intent. If you hide content solely for SEO, without real UX value, Google will detect it. Behavioral signals (click rate on the accordion, time spent) probably give clues. But Mueller doesn’t provide any numerical threshold — typical of Google's communications that leave room for interpretation.

What practical risks are there for e-commerce and editorial sites?

Product sheets with "Description / Reviews / Delivery" tabs are in the clear — it's classic UX optimization. Articles with collapsible sections to enhance mobile readability are too. No problem as long as the user can access the content.

The danger lies in borderline practices: stuffing keywords in an accordion that is never opened, hidden duplicated content targeting multiple queries, mass-generated text hidden behind fictional "See more" links. Google has the tools to spot these patterns — Core Web Vitals and engagement metrics reveal content that no one is consulting.

What should you do concretely on a mobile-first site?

First, audit all interaction patterns that hide content: hamburger menus, accordions, tabs, modals, sliders. Ensure that each element is accessible via a clear event listener (onclick, ontap) and that the content is present in the DOM, not loaded via late AJAX after infinite scrolling.

Then, test with Google's tools: Mobile-Friendly Test and URL Inspection in Search Console. Check the rendered HTML — if your hidden content doesn’t appear, Googlebot doesn’t see it either. Fix the JavaScript if necessary, ensure that server-side rendering (SSR) or pre-rendering includes these elements.

What mistakes should you absolutely avoid?

Never set content to display:none without a mechanism for revealing it. The same goes for permanent visibility:hidden, opacity:0, text-indent:-9999px, or old-school cloaking techniques. Google has 20 years of spam detection experience — these tricks are spotted instantly.

Avoid also creating "ghost" accordions: technically clickable content but never highlighted in the UI, without a visible label, lacking affordance. If an average user can’t find it, Google will consider this manipulation. UX signals (CTR, dwell time) must reflect real usage.

How can I check that my implementation is compliant?

Set up a specific monitoring: track clicks on your accordions and menus via Google Analytics or Matomo. If no one clicks, question the relevance of this content. Cross-check with the positions on the queries targeted by this hidden content.

Conduct A/B tests: one version with content visible by default, another with an accordion. Measure the impact on crawl rate, indexing, and positions over 4-6 weeks. The results will give you a more reliable indication than any official statement. And if you see a significant negative delta, you know it’s time to revisit the architecture.

• Audit all interactive elements (accordions, tabs, menus) with a crawling tool simulating JavaScript
• Check the rendered HTML in Search Console URL Inspection to confirm the presence of hidden content
• Track user interactions (clicks on accordions) to validate the actual use of the content
• Ban any display:none, visibility:hidden, or negative text-indent without a display trigger
• Test SEO impact via A/B testing (visible content vs hidden) on a sample of pages
• Monitor Core Web Vitals and dwell time to detect hidden content not being consulted