Usually, yes, as long as the text is already in the page when it loads. Google’s own guidance says moving content into accordions or tabs to save space on mobile is fine. The real problem is content that only loads after someone clicks, swipes or types, because Google says it won’t load content that needs that kind of interaction. So the question to ask about your FAQ accordion isn’t “is it folded?” but “is the answer there before anyone taps it?”

What Google actually says

Two Google documents cover this, and they point the same way.

Google’s mobile-first indexing best practices (last updated 10 December 2025, checked 17 November 2026) say you can use a different design on mobile, “for example, moving content into accordions or tabs”, as long as the content is equivalent to your desktop page. It even suggests accordions and tabs as a better option than deleting content to save space.

The same page draws the line clearly: “Google won’t load content that requires user interactions (for example, swiping, clicking, or typing) to load.”

For AI Overviews and AI Mode, Google’s guide to optimising for generative AI features (last updated 10 July 2026, checked 17 November 2026) says these features are rooted in its core Search systems, and that a page must be indexed and eligible to show with a snippet. In other words, there’s no separate “AI reader” with its own rules about accordions. If Google Search can index the text, it’s in the pool the AI features draw from.

Folded or missing? The difference that matters

From the visitor’s side, these two FAQ sections look identical. From Google’s side, they’re very different.

How the accordion works What’s in the page before a tap What Google can use
Answer is in the HTML, just visually hidden until tapped The full answer text The answer, like any other text on the page
Answer is fetched from a server only when someone taps Only the question The question, but not the answer

The second pattern is common in some website builders, chat-style FAQ widgets and “load more” buttons. It keeps the first page load light, which is fine for speed. It just means the hidden part may never be seen by Google at all.

A two-minute check you can do yourself

You don’t need to read code for this.

  1. Open the page in a normal browser. Don’t tap anything.
  2. Choose a phrase that only appears inside a closed accordion panel or tab, for example a sentence from one FAQ answer.
  3. Use “View page source” (on a computer, right-click the page and choose it) and search for that phrase with Ctrl+F or Cmd+F.
  4. Found it? The text is in the page’s HTML, so the accordion is very likely fine.
  5. Not found? The text may be added by JavaScript after the page loads, or only after a tap. That needs a closer look.

If you have Search Console, the URL Inspection tool is the better test. Run a live test, choose “View tested page” and search the rendered HTML for the same phrase. That shows what Google’s crawler actually ended up with.

Why “view source” isn’t the whole story

Google can process JavaScript. Its AI guide says so, with the caveat that JavaScript sites are “generally more complex” to get right. So text that’s missing from the raw source but added by a script on page load may still be indexed. Text that waits for a tap is the risky kind. The URL Inspection live test tells you which situation you’re in.

What about ChatGPT, Perplexity and other AI tools?

Here we have to be honest about the limits. OpenAI’s crawler documentation (checked 17 November 2026) explains which bots it uses for search (OAI-SearchBot), training (GPTBot) and user-triggered visits (ChatGPT-User), but we didn’t find any statement about how those bots treat JavaScript or content behind clicks. We found no equivalent statement from Perplexity either.

So we can’t tell you exactly what each tool sees. The safe assumption is simple: the less a page depends on clicks and scripts to reveal its key facts, the more likely any system can read them.

A hypothetical example

This is a hypothetical example. A [Business name] pest control company has a neat FAQ page with twelve folded questions. One answer explains that treatments are safe for pets after two hours. A customer asks an AI assistant whether the company’s treatment is safe around cats.

If that answer sits in the page’s HTML, it’s available to be found and quoted, though nothing guarantees it will be. If the page only fetches the answer when someone taps the question, an AI system may see the question “Is it safe for pets?” with no answer under it. That isn’t a helpful page for anyone, human or machine.

What to do if your answers only load on tap

  • Ask your web developer or platform support whether the accordion text is in the page on load or fetched on click. That one question usually settles it.
  • Switch to a native disclosure element if you can. HTML’s built-in <details> and <summary> elements fold content while keeping it in the page, and they work with keyboards and screen readers without extra code.
  • Keep the most important facts visible. Prices, service areas, hours and safety information are better as normal text near the top than buried in the fifth accordion.
  • Don’t duplicate everything “just in case”. Copying every answer into a hidden block for search engines can look like hidden text, which Google’s spam policies warn against. Fix how the accordion loads instead.

When folding content is the right call

Accordions aren’t a problem to remove. They help on small screens, they make long FAQ pages scannable, and Google explicitly accepts them. Fold content when it helps readers find their question faster. Just make sure the answer is already there when they, or a crawler, arrive.

What’s in your control, and what isn’t

In your control: whether your answers are in the page on load, whether key facts are visible text, and whether you’ve checked the rendered page in Search Console.

Not in your control: whether Google indexes a page, whether an AI answer uses it, and which source it quotes. Google says meeting its requirements doesn’t guarantee crawling, indexing or serving. Making your accordion content readable removes one barrier. It doesn’t promise a citation, a ranking or more visitors.