Your FAQ Answers May Be Invisible to Google. Here Is How to Check.

We went looking for something else this week and found a defect worth writing up, because it is invisible from the browser and it costs a site the single most quotable content it has. An FAQ section rendered as a JavaScript accordion can look completely normal to a visitor while publishing almost none of its answers to Google.

why can google not see my faq answers

Because a common accordion pattern never puts the closed answers into the page at all. The code says to render an answer only when its question is open, so a closed answer is not hidden by CSS, it simply does not exist in the HTML that gets served. A crawler reads the served HTML. What is not there cannot be indexed, quoted or ranked.

The distinction that matters is between hidden and absent. Content hidden behind a click, still present in the HTML, is fine and Google has said so for years. Content that is generated only after a user interacts is a different thing, because no crawler clicks anything.

how do i check if my faq is in the html

Open your FAQ page, press Ctrl+U or Cmd+Option+U to view the page source, and search that source for a distinctive phrase from an answer that is currently collapsed. If the phrase is there, you are fine. If the phrase is missing while the question above it is present, your answers are being generated on click and Google has never seen them.

View source, not inspect element. The inspector shows the live page after JavaScript has run, which is exactly the state that hides this problem. View source shows what was actually delivered.

what should an faq accordion be built with instead

The browser has had a native answer for years: the details and summary elements. The question goes in summary, the answer goes in details, the browser handles the open and close with no JavaScript, and every answer sits permanently in the served HTML whether it is expanded or not. It is keyboard accessible and screen reader friendly by default, which a hand-rolled div accordion usually is not.

• Every answer is in the HTML on first load, collapsed or not
• No JavaScript, so nothing to break and nothing to wait for
• Keyboard and screen reader support come free
• Browsers can find collapsed text with the browser find function

does this actually cost anything in search

It costs the thing FAQ content exists for. Google fills a People Also Ask box, and increasingly an AI summary, by lifting a passage from a page it has already indexed. A passage that was never served cannot be lifted. So a business can write genuinely good answers, mark them up correctly, and still be structurally unable to win the box its own content was written for.

There is a second cost that is easy to miss. If your FAQPage structured data lists answers that a visitor cannot see on the page, that is a mismatch between markup and content, which is the thing the guidelines are most explicit about. The safest position is simple: publish every answer in the HTML, then mark up exactly what is published.

the wider point

This is what we mean when we say a site can look finished and still be quietly losing. Nothing was broken on screen. Nobody would have reported it. It only shows up if you read the HTML your server actually sends, which is the version of your site that decides how you rank. If you have never looked at yours, the view source test above takes a minute and it is worth doing today.