Organic Audit in Topical Authority

The Organic Audit (“Audit” tab in Topical Authority) connects your Google Search Console data to your Topical Map to show how Google Search actually sees your content. It maps real search queries and landing pages to your topical hierarchy so you can see which topics earn clicks and impressions and which are invisible to organic search.

• How to connect Google Search Console
• How to import GSC data
• Switching between By Topic and By Page views
• Understanding the hierarchy tree with GSC overlay
• Reading per-topic metrics (clicks, impressions, position)
• Understanding performance classifications
• Using opportunity clusters to find new topics
• Manually matching a page to a topic when attribution misses it
• Tracking trends over time with sparklines
• Exporting your data

Before using the Organic Audit, you need:

• A completed Topical Map promoted into Topical Authority
• A Google Search Console property with verified access to your domain
• At least a few weeks of GSC data for meaningful analysis

1. Navigate to Topical Authority and select the Audit tab
2. Click Connect Google Search Console
3. Sign in with your Google account and grant Floyi read-only access to your Search Console data
4. Select the GSC property (domain or URL prefix) that matches your brand’s website

[!TIP] Domain properties (e.g., sc-domain:example.com) capture the most complete data because they include all subdomains and protocols.

Once connected, choose your date range and click Fetch Data. Floyi imports your search queries and landing pages, then runs the attribution engine to map them to your topical hierarchy.

The Organic Audit uses a three-phase matching system to connect GSC queries and pages to your topical map nodes:

1. Exact keyword match — Query text matches a node’s name, tracking query or cluster keywords exactly (highest confidence)
2. Stemmed keyword match — After word stemming, the query matches a node’s keywords (high confidence)
3. Semantic embedding match — Queries that don’t match via keywords are embedded and compared against your topic node embeddings using cosine similarity (requires a 0.70 threshold)

Queries that don’t match any node are classified as either opportunities (potential new topics) or noise (irrelevant traffic).

Once data is imported, the Audit tab splits into two sibling views you can toggle between with the tabs at the top of the panel:

• By Topic — the original two-panel hierarchy view. Browse traffic organized by your topical map (pillars, hubs, topics).
• By Page — a flat, sortable table of every URL on your site that has GSC data. Useful for page-level audits, finding cannibalization, and manually fixing attribution.

Both views read from the same underlying GSC import. Switching tabs is instant once data is loaded.

The By Topic view displays your topical hierarchy as a two-panel layout:

Your topical map structure (pillars, hubs, topics) is displayed as a collapsible tree. Each node shows:

• Clicks and impressions from attributed GSC queries
• Coverage bar showing how many child topics have GSC data
• Matrix classification badge (Strong, Emerging, Broad Reach, Weak Signal)
• Confidence dots indicating how well queries match this topic

Use the matrix filter at the top to focus on specific classification types.

Click any node in the tree to see its detail panel:

• Pillar detail — aggregate metrics across all hubs and topics in this pillar
• Hub detail — coverage and metrics for all topics under this hub
• Topic detail — individual query list, landing pages and match confidence scores
• Default overview — summary of total attributed clicks, impressions and top-performing topics

The By Page view is a single full-width table that lists every URL with GSC data, sorted by impressions by default. This is the fastest way to scan page-level performance and fix attribution mistakes.

Click any column header to sort. Click again to reverse direction. The page list is capped at the top 500 pages by impressions; an “(showing top 500)” hint appears when you exceed that.

• A search field at the top filters pages by URL substring as you type.
• Click any row to expand it inline and see the full list of queries driving that page, with per-query clicks, impressions, and position.
• Only one row stays expanded at a time, so the list stays scannable.

If automatic attribution didn’t link a URL to a topic, you can match it yourself:

1. Hover the empty Topic Match cell and click + Match.
2. A popover opens with your topical map topics. Pick the right one.
3. Optionally update the topic’s URL slug to this page’s path so future audits attribute it automatically.
4. Save. The row updates immediately and other GSC views (the topic drawer, By Topic detail panels) refresh in the background.

To remove a manual match, hover the matched row and click the small × that appears next to the topic name. You’ll see an inline confirmation strip before the unmatch is committed.

[!TIP] Manual matches are most useful when a single page covers a topic Floyi couldn’t auto-detect (e.g. branded pages, hub pages, or pages with thin keyword overlap to the topic name). The match persists across imports until you remove it.

You can also create the same match from the topic details drawer in the Planner. Click the eye icon on any Resource-level topic, expand the Search Console section, and use + Match a URL to pick a URL with GSC data. Topic-side and page-side matches write to the same record — pick whichever direction is more convenient for the task at hand.

Every topic with GSC data is classified into one of four categories based on two dimensions:

• Confidence is based on how well the matched queries relate to the topic (keyword match confidence and semantic similarity)
• Volume is based on total impressions for the attributed queries

Queries that don’t match any node in your topical map are analyzed for patterns. Related unmatched queries are grouped into opportunity clusters that suggest potential new topics for your map.

Each cluster shows:

• Cluster theme and representative queries
• Combined clicks and impressions
• An Add as New Topic button to add the cluster directly to your topical map

[!TIP] Opportunity clusters reveal what Google thinks your site is about beyond your current map. These are real queries people use to find your content that don’t fit your existing topic structure.

After running multiple GSC imports over time, each topic shows a sparkline chart displaying impressions trends. This lets you see at a glance whether a topic’s organic visibility is growing, stable or declining without leaving the Audit tab.

Sparklines appear in the hierarchy tree next to each node that has historical data.

At the top of the Audit tab, a metrics strip shows aggregate numbers:

• Total clicks across all attributed queries
• Total impressions across all attributed queries
• Attribution coverage — percentage of GSC rows matched to your topical map
• Date range of the imported data

Click the Export button to download your GSC attribution data as CSV. The export includes:

• Node name and hierarchy level
• Clicks, impressions and average position per topic
• Matrix classification
• Top queries per topic with individual metrics
• Match type and confidence scores

Use exports for client reports, stakeholder presentations or offline analysis.

You can run a new GSC fetch at any time to get fresh data. Previous imports are kept for trend comparison. The Organic Audit automatically detects when attribution needs re-running (for example, after topical map changes) and prompts you to refresh.

No. The Organic Audit is optional. Scorecard, Planner and Silo Analysis work independently using SERP and AI search data. The Organic Audit adds a layer of validation by showing how Google’s actual search data aligns with your strategy.

Monthly imports give you good trend visibility. Weekly is useful during active content campaigns. The date range selector lets you control how much data to import.

Topics with no attributed GSC data either have no published content yet or their published content is not appearing in Google Search results for related queries. This is valuable signal — it tells you where your map has gaps in organic visibility.

Use By Topic when you’re thinking strategically — which pillars are weak, which hubs need more coverage, which topics deserve a refresh.

Use By Page when you’re doing page-level work — auditing a specific URL, fixing a missed attribution, scanning for thin pages with high impressions but no clicks, or finding cannibalization where multiple pages compete for the same topic. By Page is also where you can manually match a URL to a topic when automatic attribution misses it.

Floyi requests read-only access to your Search Console data. It cannot modify your GSC settings, submit URLs or make any changes to your Google account.