md2rich

Search Console Social Tracking 2026: For Markdown Creators

On July 7, 2026, Google added a new “Social & Video Platforms” filter group to the Search Performance report inside Search Console. The filter breaks your existing search impressions, clicks, CTR, and average position down by the platform that surfaced the link - LinkedIn, X, YouTube, TikTok, Reddit, Quora, and a handful of forum hosts. For a creator who drafts in Markdown and cross-posts to social platforms, this is the missing measurement layer for a workflow you have been running on intuition for two years.

Before this filter, a LinkedIn post that ranked in Google and drove traffic back to your site was indistinguishable from a Reddit mention or a Hacker News submission inside Search Console - all of them landed in the “Web” filter under generic search appearance. The July 7 launch is the first time Google exposes the platform as a first-class dimension, which means you can finally answer the question: which social platform is sending me the search traffic, and which queries are triggering it.

What changed on July 7, 2026

Three things changed inside the Performance report for any verified property:

  1. A new “Social & Video Platforms” filter group appeared next to the existing Search type, Date, Query, Page, Country, and Device filters.
  2. Impressions on a URL are now attributed to the platform filter when the user first encountered the URL inside a LinkedIn post card, an X status embed, a YouTube description link, a TikTok bio link, or a Reddit thread that Google surfaced as a “Discussions and forums” unit.
  3. The click that brings the user back to your property still counts against your URL-prefix or domain property as before - the social filter is additive, not a replacement.

In practice, the filter shows up as a small chip under the chart titled “Social & Video Platforms” with toggles for LinkedIn, X, YouTube, TikTok, Reddit, Quora, Stack Exchange, and a handful of forum hosts. Selecting one or more chips filters the entire report to the impressions and clicks that originated from that platform.

Why this matters for Markdown-first creators

A Markdown-first publishing workflow looks like this in 2026:

  1. Draft the article in a plain text editor - Obsidian, iA Writer, VS Code, or a plain .md file.
  2. Convert the Markdown to rich text via md2rich - this step runs entirely in the browser, no upload, no account, no third-party server.
  3. Paste the rich text into LinkedIn, an X Article, a Medium draft, a Substack post, or a Bluesky long-form post - whichever surface the audience reads on.
  4. Include a link back to the canonical version on your own site.

Until July 7, step 4 produced zero telemetry in Search Console. The link in the LinkedIn post drove traffic back to the canonical URL, and that traffic showed up as generic “Web” search or as a Direct entry - both unfiltered by where the user first saw the link. The new filter fixes this: when a user finds your LinkedIn post in Google Search, the impression is now attributed to LinkedIn, and when the user clicks through to your canonical article, the click registers as having arrived via LinkedIn-driven search appearance.

A worked example: a single article across three platforms

Consider a draft like this one, which is published three times: on LinkedIn, on X Articles, and as a Substack newsletter, with the canonical copy living on your own blog.

## Why client-side Markdown conversion still matters in 2026

Server-side Markdown converters upload your draft to a third-party server
before sending it back. Client-side converters do not. The privacy and
speed difference is large enough that the client-side approach has become
the default for security-sensitive publishing.

Three platforms that benefit:
- LinkedIn (rich-text paste)
- X Articles (long-form editor)
- Medium (rich-text paste in the editor)

Read the full analysis at <https://yourblog.com/markdown-2026>.

After running this through md2rich, the same content pastes cleanly into LinkedIn's rich-text composer, the X Articles editor, and the Medium draft editor. Each platform hosts its own copy, and each one carries the canonical URL at the end of the post.

Before July 7, a query like “client-side markdown converter 2026” would show 12 impressions and 1 click in Search Console, with no indication that 8 of those impressions came from a LinkedIn card and 4 came from an X Article card. After July 7, the same query shows up with the “Social & Video Platforms” filter chip set to LinkedIn and X, and the breakdown reveals exactly which platform is doing the search-discovery work.

How to read the new filter today

Open Search Console, pick your property, and go to Performance > Search Results. The chart looks the same as before. Scroll down to the filter row and look for a new chip group labeled “Social & Video Platforms”.

Three readings to take first:

Where the conversion step fits in this loop

The new social filter measures a search-discovery loop you have already built. It does not measure the conversion step in the middle of the loop - the step that takes your Markdown draft and produces the rich-text payload each platform's editor accepts. That step is what md2rich handles.

md2rich runs entirely in the browser. You paste Markdown on the left, the rendered rich text appears on the right, and you copy the right side into LinkedIn or X Articles or Medium or Substack or Notion or Bluesky. There is no upload, no account, no third-party server. The conversion is deterministic - what you see in the preview is what the platform receives - so when the new Search Console filter attributes an impression to a LinkedIn card, the rich-text format you pasted is the format Google indexed.

This is the loop in full:

  1. You write in Markdown, locally.
  2. You convert with md2rich, locally.
  3. You paste the rich text into a platform whose editor accepts it, and include a canonical link.
  4. Google indexes the platform's surface and serves it as a search result.
  5. The new social filter tells you which platform drove the discovery.

Step 5 is what changed on July 7. Steps 1 through 4 are the workflow md2rich has been supporting since launch. The new filter is the first time you can see all five steps in one report.

Limitations to know about

The new filter is a useful first step, but it has three limitations as of July 8, 2026:

The first limitation is the one that matters most for a Markdown-first creator: if you publish to Bluesky long-form, your impressions will still show up under “Web” for now. Google has hinted that the platform list will expand later in 2026.

Quick start: three steps to use the filter today

  1. Open Search Console for your verified property. Go to Performance > Search Results. Wait for the “Social & Video Platforms” filter to appear (rolling out between July 7 and July 21).
  2. Toggle LinkedIn first, since LinkedIn cards tend to drive the most search impressions for text-heavy cross-posts. Sort the table by impressions, scan the top 10 queries, and check whether each query's CTR is above 2%.
  3. Cross-check the URLs - take the URLs that appear in the LinkedIn filter, open each one in your blog's analytics, and confirm the link is still live and still renders correctly. The conversion you ran with md2rich is the format Google indexed; if the rich-text paste ever broke (LinkedIn changed its accepted subset, for example), the impressions will dry up within a week.

The bigger picture

Search Console has historically been a tool for site owners. The July 7 launch is the first time Google has formally recognized that the search results page is now a mix of organic web URLs and platform-native embeds, and that the platform-native embeds deserve their own measurement layer. For a creator who publishes across multiple platforms, this is the validation that the multi-platform workflow is a first-class publishing strategy, not a workaround for not having a big enough audience on any single platform.

The Markdown-first publishing workflow - draft locally, convert locally with md2rich, paste into whatever platform the audience reads - is exactly the workflow this filter was built to measure. If you have been running it without telemetry, today is the first day you can see what is working.

FAQ

What did Google Search Console launch on July 7, 2026?

Google added a new “Social & Video Platforms” filter group inside the Search Performance report. You can now break down search impressions, clicks, CTR, and position by LinkedIn, X, YouTube, TikTok, and a small set of other platforms that surface Google's search results as embedded units.

Does this track how my LinkedIn post ranks in Google search?

Yes. When a LinkedIn post that contains a URL you control appears as a “people also viewed” card or a discussion-and-forums unit in Google Search, that impression is now attributed to the LinkedIn platform filter in Search Console, and the click that the user makes back to your URL is recorded in your property.

Do I need a verified TikTok or YouTube channel in Search Console to see this data?

No. The new social filter works against the web property you have already verified. Google matches impressions on LinkedIn, X, YouTube, TikTok, Reddit, Quora, and a handful of forum hosts to your existing property; you do not need to claim a separate social handle inside Search Console.

What should a Markdown creator check first inside the new panel?

Start with the “social_platform” dimension on the Performance report, sort by impressions, and look for queries where your article URL appears inside a LinkedIn or X embed. Those impressions are the search-discovery signal for the platform-cross-post workflow you have already built; if the CTR is below 2 percent, the article's title or thumbnail is not matching the searcher intent.

How does md2rich fit into this tracking picture?

md2rich is the conversion step between your Markdown draft and the rich-text payload that LinkedIn, X Articles, Medium, and Substack accept. When that payload includes a link back to your own property, the new social filter is what makes the search-discovery loop visible: you can see the query that triggered the LinkedIn card, the URL the user clicked, and the page that received the click, all without leaving Search Console.

Is the social panel available for every Search Console property?

Yes for verified domain and URL-prefix properties. Google is rolling the filter out between July 7 and July 21, 2026. If you do not see it on the Performance page yet, give it a few days or refresh the property status.

Try the Workflow

If you have been publishing Markdown to LinkedIn, X Articles, Medium, or Substack without knowing which platform is driving search discovery, today is a good day to open Search Console and look at the new Social & Video Platforms filter. If the filter is not on your property yet, refresh in a few days - the rollout runs through July 21.

If you also publish from Markdown, the conversion step that turns your draft into rich text stays the same as ever: open md2rich.com, paste in your Markdown, copy the formatted output, drop it into wherever you publish. The conversion runs in your browser. There is no upload, no account, and no third-party server. And as of the launch of the social filter on July 7, the platform you paste into is now a measurable surface in Search Console.

Draft in Markdown — Publish Anywhere, 100% in Your Browser

md2rich converts Markdown to rich text without sending your draft to any server. Use it for X Articles, LinkedIn, Medium, Substack, Notion, Bluesky long-form, and beyond. The conversion is deterministic - what you see in the preview is what the platform receives.

Open md2rich →