Search Console measures verified social posts on the same four metrics as owned pages

The join key is the query string. Search Console reports posts on Instagram, TikTok, X and YouTube with clicks, impressions, click-through rate and average position ^[2], and the dev.to writeup describes those as the same kinds of signals the tool already produces for website content ^[6]. That is what makes any reconciliation arithmetic possible: two series in the same units, keyed on the same terms.

Whether the numbers transfer depends on a definition the writeup does not supply. It names the four Performance metrics without saying how an impression is counted for a post ^[15]. If a Reel surfacing in Discover is counted under a different rule than a URL surfacing in Search, then adding social impressions to page impressions yields a total with no consistent denominator. Google Search Central has its own announcement describing platform properties as a way to track social and video posts through verified platform accounts ^[13]; read that before you put both series in one chart.

The entry condition also changed shape. Search Console has been organised around sites an organisation owns and verifies ^[5]. A platform property instead requires a verified supported platform account, and the post can stay where it was published ^[7].

Then the constraint that sets your schedule. Data begins when the account is verified, and Search Console adds no history for periods before that ^[8]. It follows that the earliest date on which two accounts can be compared is the later of their two verification dates ^[2]. Verify TikTok in March and Instagram in June, and the cross-platform format question has a June floor. Those rows stay missing no matter how much work follows verification. Google introduced the project type on July 7, 2026 and confirmed global rollout 22 days after that, on July 29 ^[1][1].

Insights adds query groups for leading and trending terms, a 24-hour filter, and export for cross-platform comparison ^[9]. Export is the load-bearing item. Platform properties do not compute return on investment, and they say nothing about revenue, leads or what a post cost to produce ^[10], so the useful join happens outside the report, against conversion tracking you already run ^[11]. What the property contributes to that join is a split: discovery that began with a Google query, separated from activity that began inside the app ^[11]. That split is also what lets a creator brief cite demonstrated search demand rather than audience size ^[14]. The writeup names an Achievements view and then moves on ^[16], which tells you roughly how much of this release is measurement.

In my context the decision is cheap: verifying every eligible account now, rather than waiting to settle the strategy argument, avoids a gap that can't be closed later, since the meter only counts forward ^[8]. The reconciliation work, choosing which impressions can legitimately be summed, is where the effort actually goes.