When BrandMentions scans a page, it looks at the version of the page that is rendered in the browser , not just what a human user instantly sees. This means that some specific pieces of content from those pages are dynamic, and they might appear or not when the users are doing specific actions on the page.
This has a few implications:
Many websites use dynamic content, loaded or changed via JavaScript.
Some elements might be:
Hidden by default (e.g., dropdown menus, accordions, tabs).
Visible only after certain user actions (e.g., hovering, clicking a button, opening a menu).
Placed in navigation bars, footers, sidebars, or other template areas.
Because of this, we treat all rendered content as potential sources for mentions, including:
Navigation menus
Hidden fields or sections
Tabbed content
Collapsed accordions
Other elements that may or may not be visible depending on user interaction
Our system doesn’t reliably “know” which content is always visible to users and which is hidden in specific states, so it cannot selectively exclude mentions from these areas.
What does this mean for your mentions?
Mentions may come from navigation menus, footers, sidebars, or other template elements that repeat across many pages.
Mentions might be triggered by dynamic or conditional content, even if a typical visitor doesn’t see that exact state every time.
You may see multiple mentions from the same site structure (e.g., your brand name in a menu shown on many pages).
Can I filter or clean these mentions in any way?
While you can’t exclude mentions specifically coming from hidden elements or HTML source only, you can still:
Use filters (by source, date, sentiment, etc.) to refine the mentions you focus on.
Manually ignore or mark as irrelevant certain mentions if they’re not useful for your analysis.
Use projects and alert rules to better focus on the sources or types of content that matter most to you.
If excluding mentions from hidden or template areas becomes critical for your workflow, we recommend reaching out to our support team with details about your use case so we can log it as a feature request and evaluate potential improvements.