GSC for social & video creators

Use platform properties to track how Instagram, TikTok, X, and YouTube posts are found on Google.

GSC UI required Beginner

Search Console platform properties report how content from a supported social account or channel performs on Google. They do not report views, reach, watch time, engagement, followers, or recommendations inside Instagram, TikTok, X, or YouTube.

As of July 18, 2026, platform properties support:

  • Instagram;
  • TikTok;
  • X;
  • YouTube.

The feature is still rolling out gradually, so it might not appear for every Search Console user. Treat availability and the interface as rollout-sensitive.

What a platform property represents

Each account or channel is added as its own Search Console property. If a creator manages three platforms or two profiles on the same platform, each needs a separate property.

Ownership is verified through the setup flow, using a supported platform login or an automated connection where offered. Verification can take a few days before reports populate.

For security, Google periodically checks ownership. If the external login expires or the connection is lost, Search Console access pauses until reverification. After reverifying, the creator returns to the same report and does not need to wait for the historical data to accumulate again.

What Search Console counts

Platform properties use familiar Search Console metrics:

Metric Platform-property meaning
Impressions Supported account content appeared in a counted Google result or surface
Clicks A user clicked the content in a way Search Console counts for that result
CTR Clicks divided by impressions
Average position Average topmost position under the applicable Search counting rules

Examples from Google's documentation:

  • an Instagram Story shown in Google Search receives an impression; clicking it receives a click;
  • a video shown in Search or Discover receives an impression;
  • when a click opens a video in Google's viewer, Search Console still counts the click.

These events describe Google discovery. They do not guarantee that a user opened the native app, watched for a minimum duration, followed the account, or converted.

Available reports

Performance

Performance shows clicks, impressions, CTR, and average position for the selected platform property. It can identify which posts drive Google visibility across Search and, when eligible, Discover and Google News.

Discover and Google News reports appear only when content receives enough traffic from those surfaces. A missing report is not proof of a configuration failure.

Insights

Insights summarizes recent traffic trends, top content, and how users discover platform content through Google Search. The top summary card includes clicks across Google sources such as Web, Image, Video, and News searches. Detailed lists below focus on Web Search, so their totals can be lower than the summary.

The default range for Insights and Performance is 28 days. New properties may show empty or partial charts until processing begins.

Achievements

Achievements records click-based milestones and growth accomplishments from Search. It is motivational context, not a ranking factor or proof of native-platform growth.

A creator analysis workflow

Find content Google can surface

  1. Select the exact platform property.
  2. Compare an equivalent period in Performance.
  3. Review top content by impressions and clicks.
  4. Inspect the queries, countries, devices, or surfaces the report makes available.
  5. Open the native post and verify its title/caption, preview, thumbnail, accessibility, and current availability.
  6. Compare the same post in native analytics using its stable platform identifier.

Do not combine account properties until after exporting or recording each property's scope. A YouTube click and an Instagram click can represent different result and consumption behavior.

Separate discovery from consumption

Use Search Console to answer:

  • Which posts are visible on Google?
  • Which Google queries or contexts expose the account?
  • Which content earns clicks from Google?
  • Is Google visibility changing by content or surface?

Use native analytics to answer:

  • Did viewers watch or engage on the platform?
  • Did they follow, share, save, or subscribe?
  • Which recommendation or feed produced the view?
  • Did the post generate platform-native revenue?

Use website analytics and commerce systems for newsletter, store, course, or sponsorship outcomes after a user reaches an owned destination.

Interpret winners carefully

A post with many impressions and low CTR might have a weak or mismatched Google preview, but it could also rank lower, appear for broad queries, or be consumed directly in a Google viewer. Control for query, position, surface, device, and content format before recommending a thumbnail or title change.

A post with few Search Console impressions can still be very successful inside its native platform. Conversely, strong Google clicks do not prove strong watch time or engagement.

Compare absolute changes as well as percentages. Recently added properties contain only data collected since setup, and low-volume posts can produce dramatic percentage movements.

Reporting across platforms

Build a table that preserves source boundaries:

Field Source
Platform, account, post ID, post type, publication date Platform or creator inventory
Google impressions, clicks, CTR, position Search Console platform property
Native views, watch time, engagement, follows Native platform analytics
Owned-site sessions and conversions Website analytics/commerce

Normalize identifiers, not metric definitions. Never sum Google impressions with native impressions and label the result “total reach”; the products count different events and surfaces.

Operating cadence

Weekly

  • Confirm each property connection remains active.
  • Review new Google-visible content and top absolute changes.
  • Compare Search Console results with native post performance.
  • Note launches, viral events, collaborations, and major edits.

Monthly

  • Report each platform separately, then create a clearly labeled cross-platform summary.
  • Group content by format, topic, and publishing cohort using first-party metadata.
  • Identify posts with durable Google demand versus short event spikes.
  • Review queries for owned-site or follow-up content opportunities.

Quarterly

  • Audit account ownership and recovery access.
  • Revisit which platforms and profiles require properties.
  • Review whether Google visibility produces useful owned-audience or business outcomes.
  • Recheck rollout documentation and report capabilities.

Current limitations

Platform properties are primarily UI reporting properties. Do not assume every website-property API, indexing, sitemap, or technical report applies to a hosted social account. The creator does not control the platform's canonical tags, crawl responses, or structured data as they would on an owned website.

Search Console cannot reveal native recommendation traffic, private content performance, all platform impressions, or why Google chose to rank one hosted post. It is one view of discovery across Google.

Official sources