Google now lets verified account owners inspect how Instagram, TikTok, X and YouTube content performs across Search, Discover and News. The useful workflow is to verify each property, export it separately and compare like with like.
The tiny failure happens in a spreadsheet. A content team exports one platform’s clicks, copies another platform’s top videos beside them, and labels the result “organic search performance.” The rows look comparable, but the ownership, formats and reporting context are different. A combined total hides the very channel decision the analysis was supposed to support.
Google made Search Console platform properties globally available on July 29, 2026. They report how eligible social and video account content appears across Google Search, Discover and News. Supported platforms named by Google include Instagram, TikTok, X and YouTube. This walkthrough explains the setup and comparison boundary; it does not claim access to a live property.
The finished state
Each owned account appears as its own verified Search Console property. Within that property, the team can inspect clicks over time, top-performing content and search queries, use a 24-hour view for recent movement, and apply format or playlist filters where the platform supports them. When cross-channel analysis is needed, each property is exported separately and normalized in a controlled workbook or data model.
The goal is not one giant dashboard. It is a comparable set of channel views with preserved provenance. Every row should still answer: which account, which platform property, which Google surface, which date range and which content unit?
| Step | Constraint | Consequence if ignored |
|---|---|---|
| Verify | Add and verify each account individually; Search profiles may be added automatically when Google can associate them | Data can be attributed to an account the team does not actually control |
| Inspect | Keep the platform property and Google surface visible in the analysis | Search, Discover and News movement becomes one unexplained total |
| Filter | Interpret playlist and format filters as documented | A playlist page can be confused with performance of every video inside it |
| Export | Export each property separately | Channels are merged before their dimensions and definitions are aligned |
| Compare | Normalize date range, account, content type and metric before calculating shares | The largest account appears to be the most efficient channel by default |
Step 1: add only accounts the organization owns
Open Search Console’s property selector and use the platform-property flow for the supported account. Complete the verification method Google presents. Document the account owner and the internal team responsible for the property. If Search Console automatically adds an associated profile, confirm that it is the intended business account before using its data in reporting.
Agency and multi-brand teams should resist the temptation to verify everything under one personal login. Verification is an access-control event. Use the organization’s account policy, grant least-privilege access, and record who can remove or reverify the property when staff or vendors change.
Step 2: read the performance report inside one property
Google’s social and video content analysis guide says the report can show clicks, trends, top content and queries across Search, Discover and News. Start with a stable date range, then use the 24-hour filter to investigate a recent launch or spike. A short window is useful for diagnosis, not enough by itself for a durable channel strategy.
Separate discovery from explanation. A rising content item tells you where to look; it does not prove why Google surfaced it. Compare publication timing, topic, format and query patterns, then form a hypothesis that the next release can test. Avoid turning one popular clip into a universal prescription.
Step 3: handle playlists and formats deliberately
On properties that support playlist filtering, Google notes that the report concerns the playlist page, not all videos contained in that playlist. That distinction changes the unit of analysis. If the question is “which collection attracts search discovery?”, playlist data is relevant. If the question is “which individual video earns clicks?”, inspect the content-level rows instead.
Format comparisons need the same care. A short video and a profile page may occupy different roles in the user journey. Compare each format against its intended job—reach, query coverage, return discovery or conversion support—rather than declaring the format with the most total clicks the winner.
Step 4: export first, combine second
Search Console does not turn separate platform properties into one automatic cross-platform comparison. Export each property and add explicit columns for platform, account, Google surface, date range, content URL or identifier, format and metric. Preserve raw exports unchanged; build comparison tabs or tables downstream.
Useful derived measures include clicks per published item, the share of clicks generated by the top ten items, and the percentage of query-bearing content that supports a target topic. Keep them labeled as calculations, not native Search Console metrics. When platform inventories differ sharply, compare distributions and rates as well as totals.
Verification: prove the report answers the question
Before presenting a chart, trace one row back to its property and visible content item. Confirm the account, period and surface. Then state the decision the chart supports. “YouTube received more clicks” is a description. “For the next product launch, publish a searchable long-form video because comparable launches generated sustained Search clicks after the first 24 hours” is a testable decision—provided the underlying rows actually support it.
Official sources
- Platform properties announcement — Google Search Central, July 29, 2026.
- Social and video content analysis — Google Search Central, checked August 15, 2026.
- Documentation update log — Google Search Central, checked August 15, 2026.
