GSC Social Report 2026: Reddit + YouTube + TikTok Combined

Google quietly rolled out a new "Social & Video Platforms" performance report in Google Search Console on July 7, 2026. The new view combines impressions, clicks, and rich-result metrics from Reddit, YouTube, and TikTok into a single tab — the first time GSC has surfaced cross-platform social signals together. For creators who split their publishing between a YouTube channel, a TikTok short-form pipeline, and a Reddit community presence, the combined view answers the question that three separate dashboards could not: which platform is actually moving my audience, and which post is worth archiving for the next quarter's playbook?

The report is opt-in per property and limited to properties that already receive social-rich-result impressions. Once enabled, it returns up to 90 days of data and groups posts by domain, not by URL — a deliberate choice that mirrors how GSC already handles forum and discussion-page aggregations. That grouping has a side effect that affects every archive strategy: the URL you archive today may not be the URL GSC reports on tomorrow. If you want to attribute a long-tail traffic spike back to a specific TikTok or Reddit thread, you have to capture the URL and the timestamp and the engagement snapshot in a single archive action. That is exactly the gap threadgrab's sidecar JSON was built to close.

What lands in the new GSC Social & Video report

The July 7 launch ships with three platform integrations out of the box — Reddit discussions, YouTube videos, and TikTok public posts — and the underlying API model is generic enough that Google can extend it to LinkedIn newsletters, Instagram Reels, and Bluesky feeds without an interface change. Each row in the new report represents a top-level content unit (one Reddit thread, one YouTube video, one TikTok post), and the columns expose impressions, clicks, CTR, and average position the same way the traditional Search Results tab does.

The most interesting field, though, is the new source_platform filter. Without it you can see that your site received 2,800 social-video impressions yesterday; with it you can split that into 1,900 from Reddit threads, 700 from YouTube embeds, and 200 from TikTok embeds. Creators who publish a weekly recap that lives on their own domain but gets cited on Reddit, who run a YouTube series that embeds in their blog, and who cross-post short-form to TikTok finally have one place to compare the three.

Why the combined view matters for creators

Until now, cross-platform attribution for content creators lived in three separate dashboards, two of which (Reddit, TikTok) did not even expose impressions data. YouTube Studio has had impressions for years, but only for search and suggested surfaces — not for the embeds that show up on third-party blogs. Reddit Ads Manager exposes only promoted impressions. TikTok's analytics surface only shows on-platform views. None of them talk to each other, and none of them map cleanly back to the blog post or newsletter that originally produced the content.

The new GSC report does not solve every gap — it still measures what happens on your property in Google's index, not what happens on the platforms themselves. But it is the first place where a creator can see the combined social-discovery footprint of a single piece of content, and that is enough to make quarter-end reporting meaningful. If your article about a niche data-engineering pattern got cited on a Reddit thread, embedded in a YouTube tutorial, and stitched into a TikTok recap, the new report shows that one combined footprint; the per-platform dashboards show three partial stories.

Three platforms, three retention rules

The new report inherits very different retention semantics from each underlying source, and the way GSC normalizes them matters for how you build your archive:

The GSC cap of 90 days is the binding constraint: if you wait more than three months to capture a post that drove traffic in March, the report will still show the row but you will not be able to attribute it to the source URL because the source may have been deleted, edited, or buried. Pair the GSC row with the sidecar JSON from the day the post peaked, and you have a citation-grade audit trail that survives any of the three platform's deletion policies.

The URL drift problem

Reddit edits slug URLs on every moderator-driven rename. YouTube keeps the same video ID but updates the title, description, and chapters in place, so a GSC row keyed on a 12-character video ID may point to a video with three different titles by the time you look at it. TikTok usernames can change at any time without invalidating the URL, but the post itself can be set to private, deleted, or replaced by a repost with a new ID. None of these surface as 404s in GSC — the row just keeps reporting impressions on a URL that no longer matches the content.

The fix is to capture the post's identity triple at archive time: the platform ID (Reddit thread ID, YouTube video ID, TikTok post ID), the canonical URL at capture time, and the title. The sidecar JSON that threadgrab emits already does this for Reddit and YouTube; for TikTok it captures the post URL plus the creator handle at capture time, so you can resolve the URL back to a person even after a handle rename.

Build the sidecar in five steps

Here is the workflow that pairs the new GSC report with a threadgrab sidecar in five repeatable steps:

1. Identify the candidate post in GSC. Open the Social & Video report, sort by impressions, pick the top three rows that came from a platform you actively cross-post to.
2. Resolve each row to a source URL. Click through the GSC row to see the platform URL it references. For Reddit this is the canonical comment permalink; for YouTube it is the embed URL; for TikTok it is the post URL with the ?_t= query parameter that pins to a specific timestamp.
3. Capture each source URL with threadgrab. Run the capture CLI against each URL with the --platform flag set explicitly so the sidecar records which schema was used. The sidecar will inherit the platform-specific ID fields automatically.
4. Annotate the GSC row in a local index. Append the platform-specific ID, the capture timestamp, and the sidecar file path to a local CSV keyed on the GSC row's URL. This is what lets you cross-reference a row from the new report back to the exact archived content in three clicks instead of thirty.
5. Re-run on the 90-day boundary. The GSC report keeps 90 days of history; if a post drove a meaningful spike in the second half of that window, capture it again with a fresh sidecar so the archive records the post-engagement snapshot rather than the peak snapshot.

Wire the capture CLI to the GSC report

The capture CLI accepts a manifest file, which is the cleanest way to back-fill multiple rows from a single GSC export. A manifest is a JSON file with one entry per row, and the entry's URL field is what gets captured. Here is a minimal example:

{
  "rows": [
    {
      "gsc_url": "https://example.com/blog/data-pipeline-postgres-vs-mongo/",
      "social_url": "https://www.reddit.com/r/dataengineering/comments/1abc23z/why_we_switched/",
      "platform": "reddit",
      "impressions": 1843,
      "clicks": 41,
      "captured_at": "2026-07-20T08:12:00Z"
    },
    {
      "gsc_url": "https://example.com/blog/postgres-tuning-2026/",
      "social_url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
      "platform": "youtube",
      "impressions": 612,
      "clicks": 18,
      "captured_at": "2026-07-20T08:12:05Z"
    }
  ]
}

Run threadgrab capture-manifest manifest.json --output ./archive/ and the CLI captures every social URL, writes a sidecar JSON next to each Markdown export, and returns a manifest receipt that lists the sidecar file paths. Pipe the receipt into your local CSV from step 4 and you have a complete cross-reference in one pass.

Map the report to your archive with one SQL query

Once you have a few weeks of GSC exports and a few hundred sidecars, the cross-reference becomes a single SQL query. The example below assumes you have loaded both the GSC Social & Video export and the sidecar index into a local DuckDB instance:

SELECT
  gsc.date,
  gsc.social_url,
  gsc.impressions,
  gsc.clicks,
  sidecar.platform_id,
  sidecar.title_at_capture,
  sidecar.sidecar_path
FROM gsc_social_video AS gsc
LEFT JOIN sidecar_index AS sidecar
  ON gsc.social_url = sidecar.canonical_url
WHERE gsc.date >= '2026-07-01'
  AND gsc.impressions > 50
ORDER BY gsc.date DESC, gsc.impressions DESC;

The LEFT JOIN is the important detail: rows where sidecar.platform_id is NULL are exactly the ones you missed at archive time, and they are the rows where you cannot reconstruct the citation back to a real post. A monthly audit on the NULL count tells you whether your archive is keeping up with the new report, and gives you a clear SLA target for next month.

What still does not work

The new GSC report is opt-in per property, and the rollout has been gradual: as of July 20 the tab is visible for properties that received at least one Reddit rich-result impression in the previous 30 days, but not for properties whose only social-video traffic came from YouTube embeds. Google has not published a date for the YouTube-only path; in the meantime, properties that rely solely on YouTube embeds will not see the report even after enrollment. If your property is in that bucket, the workaround is to add a Reddit-friendly section (a community thread, an AMA, a discussion post) to your publishing cadence so the report has at least one qualifying data source.

Another gap: the report does not yet expose per-country splits for social-video impressions. If your audience is global and your top traffic spike came from a German-language Reddit thread, you cannot segment it out at the country level; you only get the combined impression count. Google has signalled that per-country splits are on the roadmap but has not committed to a date. Until then, the sidecar JSON is the only place where the country of origin is recorded, because the capture CLI geolocates each URL through the public IP at capture time.

Cluster cross-link: threadgrab cross-platform coverage

The new GSC report builds on a stack of threadgrab features that have shipped over the past two months. The Reddit-specific capture path is documented in the cross-posting workflow guide, which walks through how to capture a Reddit thread, a YouTube comment chain, and a LinkedIn newsletter in one archive session. The sidecar schema is detailed in the Markdown pipeline reference, including the field-by-field breakdown of what gets captured and what gets omitted. And the long-term retention problem — the same one the new GSC report makes more visible by capping history at 90 days — is the subject of the backup strategy guide.

FAQ