Automatically Detect Content Gaps Through Search

Learn how Automatic Gap Detection monitors search activity, creates and prioritizes gaps, and helps you keep your organization’s knowledge findable without manual audits.

🎯 Who this article is for: Admins who want their intranet to stay useful and findable without micromanaging content.

💼 Package requirements: Knowledge Engine is available as an add-on for the Starter, Growth, and Enterprise Packages on Google and Microsoft suites.

🔒 Permissions: Only admins can view all content gaps in the Gap Dashboard. Non-admins can manually flag gaps, see gaps assigned to them, and manage those assigned gaps, including updating priority, status, title, summary, and closing them.

💻 Limited device availability: Gaps can be detected through search on the mobile app; however, accessing the Gap Dashboard and closing a gap is not available on mobile.

1. Overview

Knowledge Engine’s Automatic Gap Detection monitors real search activity as it happens. When Happeo Search cannot confidently return a result, because content doesn’t exist, isn’t connected, or isn’t accessible to that user, a content gap is created automatically in the Gap Dashboard.

This gives your organization a continuously updated view of what people are looking for but not finding, without relying on anyone to file a report or notice the problem. You get a clear, prioritized list of where to focus, so the right people can act fast.

🔎 Learn more about Using the Gap Dashboard as an admin.

2. Use cases

• New hires find what they need from day one: When someone searches for “expense reimbursement steps” and gets an uncertain result, a content gap is created automatically. The right person is notified and can fill the gap, so the next new hire self-serves instead of interrupting a colleague.
• Policies are always where people expect them: If employees search for “remote work guidelines” and come up empty, that search is captured immediately and a gap is created. Admins can see what’s missing and can assign it to the right team, before it becomes a recurring interruption.
• You know when content exists but isn’t reachable: If documentation lives in Google Drive but the integration isn’t enabled, Happeo Search has no visibility into it. Gap detection surfaces this, so you can connect the content and make it findable.
• Permission gaps become visible: If a document exists in a page group but certain users can’t see it, Search fails from their perspective. Gap detection highlights these patterns, so you can decide whether to adjust access or surface the content differently.

3. Before you begin

• Knowledge Engine must be enabled in your environment.
• You must be an admin to view and manage all gaps in the Gap Dashboard.
• Happeo Search respects your existing access setup. If content exists but Happeo isn’t authorized to access it, or a user doesn’t have permission, Search will not return it for that user, and access restrictions won’t affect other users’ results.
• Gap detection works across desktop and mobile. Searches made on the Happeo mobile app are included.

🔍Search AI: Must be enabled for automatic gap detection to work. Without Search AI, gaps can still be created manually by users who flag missing or incorrect information, but failed searches will not generate gaps automatically.

4. How automatic gap detection works

Automatic gap detection is passive. It runs quietly in the background of Happeo Search, analyzing real usage as it happens. No configuration is needed, and users don’t need to do anything differently.

Step 1: A user performs a search

When someone searches on their platform by entering keywords or asking a question using Search AI, Happeo tries to return the most relevant result available to that user.

Search looks across content that is part of the platform, including:

• Pages and page content.
• Posts and channel content.
• Files and links attached to pages or posts.

🔎 Learn more in Federated Search.

Step 2: The search is evaluated

Each search attempts to return the most relevant result or answer. A search is considered unsuccessful if one or more of the following occurs:

• No results are returned.
• Search AI returns "no answer found."
• A result is returned but is determined to not be relevant enough to the query.
• The answer is marked as uncertain or unreliable.

These outcomes indicate that the user could not confidently find the information they needed.

🔎 Learn more in Search AI.

Step 3: A content gap is created

When a search fails, a content gap is created automatically within the Gap Dashboard.

• If a similar gap already exists, the failed search is linked to it.
• If not, a new gap is created.
• Over time, searches about similar topics are grouped together within the Gap Dashboard.

When a search fails, a gap is created in the Gap Dashboard. As related searches accumulate and are grouped together, the gap's priority is updated accordingly, so the most pressing issues rise to the top naturally.

🔒 Privacy: All search data used for gap detection is anonymized. Admins see overall search trends and cannot identify individual users who searched for something. This protects the privacy of your people.

5. When a gap is and isn't created

Not every search leads to a gap. A gap is created only when Happeo Search cannot confidently return a relevant result based on what it has access to for that user. This means content that exists and is accessible will resolve the search without creating a gap, whether it lives in Happeo Pages, attached files, or a connected integration like Google Drive.

Search is successful — no gap is created

• The policy exists in a page: An employee searches for a remote working policy. Happeo recognizes who the user is and what applies to them, finds the right policy, and returns it. No gap is created.
• The policy is attached to a page: Search detects an attached file (for example, "Remote Working Policy 2026") within a link list. The result is deemed highly relevant. No gap is created.
• The policy exists in an integrated Google Drive: Search doesn't find it in native content, but finds a relevant file in the connected Google Drive. No gap is created. - 🗒 Note: A gap would be created in this scenario if the result from Google Drive is not deemed relevant enough, or if Search AI cannot confidently answer the query.

Search fails — a gap is created

• You know the policy exists in Google Drive, but Drive isn't integrated with Happeo: Search looks through native content and attached files but finds no relevant result. Because Google Drive isn't integrated, Search has no visibility into the existing file and therefore a content gap is created.
• The content exists, but the user does not have access to it: An employee searches for information that exists in Happeo or a connected tool, but they do not have permission to view it. From their perspective, the search returns nothing. A gap is created. This can happen when content is restricted to a specific team, location, or role. Gap detection surfaces this so you can decide whether to adjust access or create a version of the content that is available to the right people.

This signals that the information is not discoverable through your platform, even if it exists elsewhere. It may need to be brought into a page or linked appropriately.

6. How gaps are grouped, prioritized, and managed

Once a gap has been created, it appears in the Gap Dashboard, where admins can review, prioritize, assign, and track it. Similar gaps are grouped together over time. For example, if ten different employees search for variations of the same thing, such as: "expense policy," "how to submit expenses," "reimbursement form" — those failed searches are recognized as related and combined into one gap. This means you see one clear item to act on, not a long list of individual searches to sort through.

🔍 For detailed guidance on reviewing, grouping, and assigning gaps, see our article on Using the Gap Dashboard.

7. Getting the most out of Gap Detection

Automatic gap detection reflects how Search performs for your users in real time. A gap signals that someone couldn’t find what they needed — but it doesn’t always mean content is missing. Documentation may exist under different terminology, sit in a tool that isn’t connected, or be behind permissions that limit who can see it. Understanding this context is what helps you get the most out of Gap Detection:

• Content titles shape discoverability: Search handles semantics and typos well, but titles that reflect how your team actually searches make it easier to return confident results. If employees search for “expense policy” and your page is titled “Financial Procedures,” a gap may be created even when the content exists. Aligning titles to real search behavior reduces gaps and improves self-service.
• Having related content isn’t always enough: If Search can’t confidently match a result to what the user was looking for, a gap is still created. This also accounts for situations where content exists but Happeo or the user doesn’t have access to it.
• Gap detection is a signal, not a complete audit: It shows where people struggled to find answers based on real search behavior. You still review gaps and decide what action makes sense — whether that’s adding content, connecting an integration, or adjusting permissions.
• Search AI is required for automatic gap detection: Search AI must be enabled for failed searches to generate gaps automatically. It interprets the intent behind queries, not just the exact words used, which also reduces false gaps and gives you a clearer picture of what's truly missing. Without it, only manually flagged gaps will appear in the Gap Dashboard.
• Manual flags raise priority: Gaps that accumulate multiple automatically detected signals reach a maximum automatic priority of medium. When a user manually flags an issue, the priority is bumped to high. A deliberate flag is a clear signal that someone was actively looking for something and found the information missing or unreliable, which is why it carries more weight.

Users can also flag issues that automatic detection may not catch. Anyone can flag a search result that looks outdated, incorrect, or incomplete directly from Search. Users can also flag content directly from a page they are reading, without needing to run a search first.

🔎 For more information, see Flag Missing or Incorrect Information From Search and Flag Missing or Incorrect Information From a Page.

8. Frequently asked questions

Does gap detection mean we have to move all our content into Pages?
No. A content gap is created only when Search cannot reliably return an answer. Where content lives matters less than whether your team can find and rely on it through your platform. If an external tool is integrated and Search can return a relevant result, no gap is created.

What happens right when a gap is created, and what changes over time?
The moment a search fails, a content gap is created and appears in the Gap Dashboard. From that point, related failed searches are grouped with it over time. This doesn't change whether the gap exists — it affects how the gap is prioritized and what context admins have when reviewing it.

Can admins see who searched for something?
No. All search data used for gap detection is anonymized. Admins only see overall search trends and cannot identify individual users.

Is automatic gap detection treated differently from gaps created manually?
Once created, both types follow the same lifecycle and are managed in the same way in the Gap Dashboard. The difference is in how they're surfaced: automatic gaps come from real search behavior, while manual gaps are created by admins who are already aware of an issue.

Can a closed gap reappear?
Yes. If users continue to experience failed searches related to the same topic after a gap has been closed, it may appear again. This ensures gaps reflect the current search experience rather than a one-time fix.