Since July 29, 2026, you can plug your Instagram, TikTok, X or YouTube account straight into Google Search Console and finally see which queries send people to your social content inside Google Search. No website, no tag, no DNS: a sub-minute OAuth check and you have your clicks, impressions and queries. Google calls them platform properties, the feature went globally available two days ago, and almost nobody has written yet about what it actually measures. That is what this guide is for, plus the question nobody is asking: once you have the data, what do you concretely do with it.
One thing up front, because it saves a big letdown: this data is about Google only. Google Search, Discover and News. Nothing to do with the reach, views or likes you see in the native app. We come back to it in detail below, since it is the most misunderstood part of the feature.
What a platform property is in Search Console
Until now, Search Console knew two kinds of properties: the domain property (verified through DNS) and the URL prefix property. Both assume you own a site. The catch is that your most-viewed content may not live on your site at all. It lives on an Instagram profile, a YouTube channel, a TikTok account. And Google indexes that content and surfaces it in its results, without giving you any way to measure that visibility.
The platform property fills exactly that gap. It is a new property type that does not represent a site, but your presence on a third-party platform. You prove the account is yours through an OAuth connection with the platform, and Search Console opens up the same performance reports you get for a normal site, applied to your social content as it appears inside Google.
In practice, that means an agency running a brand’s social presence can, for the first time, attribute a slice of Google traffic to Reels or videos rather than to the site alone. For an analytics consultant, it is one more source of organic data, free, that was simply waiting to exist.
What you will measure
The metrics are exactly the ones you already know from Search Console, which is good news: no new grammar to learn. You get clicks, impressions, CTR and average position, crossed with the metric that matters most, the query.
| Metric | What it tells you |
|---|---|
| Clicks | How many times someone clicked through to your social content from Google |
| Impressions | How many times your content appeared in Google results |
| CTR | Share of impressions that turn into a click |
| Average position | Average rank of your content on the query |
| Queries | The terms typed into Google that surface your content |
The most valuable data point is the query. You already know which posts work inside the native app, but you had no idea which words made people land on them from Google. You will discover that some videos capture search traffic you never suspected, sometimes on intents far removed from what you thought you were targeting. It is the same shock as the first time you open the query report for a website.
The scope covers three Google surfaces: classic search, Discover and News. If your content gets picked up in Discover, you will see it, and for short-form video that is often where the bulk of the volume hides.
Step-by-step setup
The speed promise holds, and this is probably the simplest part of the entire Google Analytics ecosystem. Here is the flow.
First, open the property selector at the top left of Search Console, then choose to add a property. A third option now sits next to domain and URL prefix: the platform property. Pick the platform you want, Instagram, TikTok, X or YouTube.
Next, Search Console redirects you to the platform’s sign-in screen. You authenticate with the account you want to attach and grant read access. It is a standard OAuth authorization, read-only on Google’s side, with no publishing rights whatsoever. Once approved, the property is verified. No file to upload, no DNS record, no tag in GTM.
Finally, let it run. As with a new site, the reports fill in over the following days, with history building up gradually. Do not judge the feature on the first twenty-four hours: give it a solid week before drawing conclusions about your volumes.
A note for agencies: each platform verifies separately, and the authorizations tie to the account that approves the OAuth. Use an account the team keeps over time, otherwise a single departure can cut off access to the property. If you already juggle several site properties, adding social properties will crowd your selector, so name and organize them cleanly from the start.
What it does NOT measure
Read this section twice, because this is where expectations go off the rails. The platform property measures the visibility of your content inside Google, full stop. It is in no way a replacement for your platforms’ native analytics.
| What it measures | What it does NOT measure |
|---|---|
| Clicks from Google Search, Discover, News | Views, reach and impressions in the native app |
| Impressions in Google results | Likes, shares, comments, follows |
| Google queries that surface your content | Traffic from the platform itself or its feed |
| Position and CTR inside Google | Video retention, watch time, demographics |
Put plainly: if a TikTok video pulls a million views in the app but nobody finds it through Google, your platform property will show tiny numbers. That is logical, not a bug. The two worlds measure different things. Social traffic comes overwhelmingly from the internal algorithmic feed, not from Google. The share Google contributes is real but a minority for most accounts, and it is precisely that share, invisible until now, that the feature lights up.
The mistake to avoid would be presenting these numbers to a client as the overall performance of their social channels. It would be wrong and you would be shooting yourself in the foot. Always frame this data for what it is: the Google slice of your social visibility, a complement, never a substitute for native stats.
How to use this data in your analytics workflow
This is where the feature gets interesting for a practitioner, and not just for ticking a box. Pulling clicks is something everyone will manage. Turning them into decisions is another matter.
First reflex, cross it with the site. If you already track your site’s Search Console data, you now hold both halves of your organic Google visibility. Look at the queries that appear on both your site and your social content: these are topics where Google finds you relevant across several formats, a strong signal for prioritizing a content cluster. The logic is the same one detailed in our guide on the SEO analyses to cross in GA4 and Search Console, transposed to social.
Second reflex, treat this social content as a channel in its own right, just like AI traffic. The logic mirrors what we apply when tracking traffic from ChatGPT, Gemini and Claude in GA4: a new touchpoint the native tools do not capture, which you have to instrument by hand for it to exist in your reports. Drop your platform properties clicks into your visibility dashboard, next to site organic and the AI channel, and you finally get a complete brand view rather than three silos.
Third reflex, use it as an intent sensor. The queries that surface your Reels or videos tell you which topics Google associates with your brand beyond your site. That is valuable raw material for your editorial strategy, and it ties into the broader brand-presence question covered in our article on measuring your visibility in AI answers. Wherever your social content already ranks, you have proof the topic may deserve a dedicated page on the site too.
My concrete recommendation for this week: verify your main social accounts now, while the discovery window is open, and let the data pile up for a month before wiring anything into a dashboard. You lose nothing by verifying early, since history starts building the moment you verify. In thirty days you will have enough to decide whether this source earns a permanent spot in your reporting, or stays a curiosity you check once a quarter. For most brands active in video, my bet is on the former.