How are FAQ clicks really counted in Search Console?

Why does Google's clarification change our reading of Search Console data?

When you look at the performance reports in Search Console, you likely think that a click on your FAQ rich result is counted for the page that hosts this markup. This is partially false.

Google makes a crucial distinction here: only a click on the main URL counts as an FAQ click. If your FAQ answer contains an internal link (to a product sheet, a blog post, a landing page), and the user clicks on it from the rich result, it’s the destination URL that inherits the click and the impression.

In practical terms, this means that your FAQ pages can generate traffic to other pages on your site without that traffic appearing in the metrics of the FAQ page itself. You are likely underestimating the real impact of your FAQ markup on your overall traffic.

What exactly is a click on the main URL?

The main URL is the classic blue link in search results, the one that points to your page. In a FAQ rich result, several elements are clickable: the title of the page (main URL), but also potentially links present in the FAQ answers themselves.

If your FAQ markup includes hyperlinks in the answers (which is technically possible and sometimes recommended to improve user experience), these links become alternative entry points. The user can click directly on an internal link from the SERP without ever going through your FAQ page.

This mechanism transforms your FAQ page into a true traffic distribution hub, but Search Console data does not transparently reflect this reality. You need to analyze performance in a much more nuanced way.

What are the implications for organic traffic attribution?

Traffic attribution becomes blurry. An FAQ page can be extremely performant in terms of visibility and generating clicks, but if all clicks go to internal destination URLs, the FAQ page itself will show weak metrics.

Conversely, pages that do not rank directly can receive clicks and impressions attributed from FAQ results of other pages. This complicates the analysis of SEO performance by page and requires a more holistic approach.

You now need to consider your FAQ pages not as end destinations, but as strategic distribution points in your content architecture. Optimization is no longer just about the FAQ page ranking, but also about the quality and relevance of the destination URLs you include in the answers.

• An FAQ click in Search Console = click on the main URL only, not on internal links in the answers
• Internal links in FAQ answers transfer the click and impression to the destination URL
• Your FAQ pages can generate invisible traffic in their own Search Console metrics
• Traffic attribution becomes distributed among multiple URLs instead of being concentrated on the FAQ page
• Performance analysis requires a holistic view of the user journey from rich results

Is this counting rule consistent with real-world observations?

Yes, and it explains certain anomalies that many of us have noticed without understanding their origin. When you see a FAQ page with an excellent impression rate but abnormally low CTR, it’s often because clicks are going to internal URLs via FAQ answers.

I have observed cases where a well-ranked FAQ page displayed a CTR of 2-3% while the destination pages related in the FAQ answers saw their organic traffic increase by 40% without a visible improvement in their own ranking. The correlation becomes evident when reading this statement from Google.

That said, [To be verified]: Google does not specify how multiple impressions are treated when a user sees both the FAQ page and the destination URL in the same rich result. Do both receive an impression? The documentation remains vague on this point.

What are the gray areas in this statement?

Google says nothing about expandable FAQ results in the SERPs. When a user clicks to expand a question without clicking on a link, is it counted somewhere? Probably not, which means a significant part of engagement with your FAQs remains invisible.

Another point: this mechanism only applies to explicit links in the FAQ markup. If your FAQ answer mentions a product or service without a hyperlink, the user must click on the main URL to access your site. Therefore, the presence or absence of internal links becomes a strategic lever to guide traffic.

Finally, [To be verified]: does this rule apply the same way on mobile and desktop? FAQ rich results display differently across devices, and nothing guarantees that the counting is the same. Google remains silent on this point.

Should we reconsider our FAQ markup approach in light of this information?

Absolutely. Until now, many SEOs considered FAQs as a visibility tool for the page itself. This is reductive. FAQs are becoming a tool for distributing qualified traffic to strategic pages.

If you optimize an FAQ page for a broad informational keyword but insert internal links to transactional pages in the answers, you create a bridge between informational intent and commercial intent. It’s extremely powerful, but it requires a pre-thought content architecture.

However, be careful: don’t stuff your FAQ answers with artificial internal links just to capture traffic. Google may very well decide to stop displaying your rich results if the markup is evidently manipulated. The relevance of the links remains the number one criterion.

How to adjust your FAQ markup strategy to maximize real traffic?

Your first reflex: audit your existing FAQ pages to identify those containing internal links in the answers. Cross-reference this data with the Search Console performance of the destination URLs. You should see traffic spikes correlated with the impressions of the FAQ page.

Next, think about your internal linking architecture in the FAQs. If your goal is to push traffic to commercial pages, insert relevant links in the answers. If you want to maximize traffic to the FAQ page itself (for conversion or engagement reasons), avoid internal links or make them less visible.

Test different approaches on similar FAQ pages. One page with rich internal links, another without links. Compare overall performance (total traffic generated, conversions, engagement) and not just clicks on the FAQ page itself.

What data interpretation errors should be avoided?

Never judge the performance of an FAQ page solely based on its own Search Console metrics. If you see a low CTR but a high number of impressions, dig deeper: are the destination URLs receiving additional organic traffic? If so, your FAQ is doing its job.

Also, avoid deleting FAQ pages simply because they generate few clicks. They can be essential distribution points for other strategic pages. Look at the systemic impact, not the isolated impact.

Finally, don’t confuse impression with real visibility. An impression means your rich result has appeared, but not necessarily that the user has seen or read it. Google does not provide metrics on scrolling or visual engagement with FAQs in SERPs.

How to ensure your FAQ implementation is optimal for this counting mode?

Install a UTM tracking on all internal links present in your FAQ answers. Even if Google Analytics doesn’t capture clicks from the SERP (since the user never arrives on the FAQ page), you will be able to isolate traffic from the FAQ internal links if the user then navigates on your site.

Use search query reports in Search Console to identify which questions trigger impressions. If a question generates a lot of impressions but zero clicks, it may be because the answer contains an internal link that users are clicking on directly.

Monitor the bounce rates and the time spent on destination pages linked from the FAQs. If these pages receive traffic with an abnormally low bounce rate and high session time, it’s a signal that the traffic comes from well-targeted FAQ rich results.

• Audit all FAQ pages to identify the presence and relevance of internal links in the answers
• Cross-reference the Search Console data of the FAQ page with that of the destination URLs to measure the real impact
• Test different internal linking strategies (with/without) on similar FAQs and compare overall results
• Set up UTM tracking on FAQ internal links to isolate traffic even if indirect
• Never judge the performance of an FAQ page solely based on its own click metrics
• Ensure that all destination URLs linked in the FAQs are indexable, fast, and optimized for conversion