Web content best practice: Can AI crawlers read accordion boxes?

The great accordion box/FAQ conundrum

It’s a good question, and one you should be asking if you’re trying to manage the new reality of SEO/AEO/GEO web searchability. The answer is mostly yes — AI crawlers can read accordion content, but with some important nuances worth knowing.

The technical reality

Most accordion/FAQ components are built with HTML that's already present in the page source, just visually collapsed via CSS. When an AI crawler (Googlebot, GPTBot, PerplexityBot, etc.) fetches a page, it reads the raw HTML — not what's visually rendered. So if your FAQ answers are in the DOM (What is DOM? See below.), they get read regardless of whether a user has clicked to expand them.

Where it gets complicated

If the accordion content is loaded via JavaScript after the initial page load (lazy-loaded or fetched from an API on click), some crawlers may miss it. Google's crawler handles JavaScript reasonably well but with known delays. Less sophisticated AI crawlers may not execute JavaScript at all, meaning dynamically injected content could be invisible to them.

The practical upside for your purposes

For AEO and GEO specifically — the channels that matter most for getting cited in AI-generated answers — structured FAQ content is actually one of the highest-value things you can publish. Google even has a specific FAQ schema markup that signals "this is a question-and-answer pair" to crawlers. Properly marked-up FAQ content is a direct path to featured snippets and AI Overview inclusions.

The real-world-do-it-now recommendation

Don't rely on accordion UI alone to signal importance. A few things worth doing:

• Use <details> and <summary> HTML elements where possible. They're semantic, accessible and crawler-friendly by default.

• Add FAQ schema markup (JSON-LD) to the page so crawlers know explicitly that these are Q&A pairs, regardless of the visual treatment.

• Make sure the content isn't dependent on a JavaScript click event to populate. The answers should be in the source HTML even if they're visually hidden.

• If your site is built on a CMS like Squarespace (which the jooj uses), test your pages in Google Search Console's URL Inspection tool to see the rendered HTML and confirm your accordion content is being indexed.

Bottom line: accordion boxes are not an inherently bad choice for FAQ content. The concern isn't the visual interaction pattern — it's whether the underlying HTML is crawler-accessible and whether you're using schema markup to make the structure machine-readable.

DOM DOM DOM DOM

What does DOM mean?

DOM stands for Document Object Model — it's essentially the structured, readable version of a webpage that a browser (or crawler) builds from your HTML code.

Think of it this way: when a web page loads, the browser takes all the HTML code and assembles it into a tree of content — headings, paragraphs, buttons, hidden text, everything. That assembled structure is the DOM. "In the DOM" just means the content exists in that structure, even if it's not visually visible to a human reader at that moment.

So when an accordion box is closed and a user can't see the answer, there are two possibilities:

The answer is already in the DOM — the text is sitting in the HTML, just hidden with CSS (something like display: none or height: 0). A crawler reads right through that. The content is there; it's just invisible on screen.

The answer is not yet in the DOM — the text doesn't exist in the HTML at all until someone clicks the accordion, at which point JavaScript fetches or injects it. A crawler that doesn't execute JavaScript would see nothing, because there's literally nothing there to read yet.

The practical takeaway: if you build an accordion in Squarespace (like this site) or most modern/current CMS platforms, the content is almost always already in the DOM and hidden with CSS — meaning crawlers can read it just fine. The risky scenario is custom-built components that deliberately withhold content until user interaction triggers a fetch.

Getting the technical details right matters. But so does having content worth crawling in the first place. Accordion structure, schema markup and DOM hygiene are all in service of one goal: making sure your web content is findable, citable and useful to both human readers and the AI systems increasingly shaping how people discover healthcare information. If your practice website needs content that's built for the way search actually works today, that's exactly what the jooj does.

Visit our web content services page to learn more. https://www.thejooj.com/web-content-development