---
name: medium-strategy
description: "Use when planning Medium as a growth + money SYSTEM over months, not one post: enrolling in and optimizing for the Partner Program, deciding solo profile vs starting a publication vs joining or pitching one, engineering for Boost and the three distribution tiers, choosing tags/topics for reach, and a canonical cross-posting plan — read from and written back to 02-DOCS/wiki/medium/ so each session compounds. Triggers: 'how does the Medium Partner Program pay me', 'why does my story get views but no distribution', 'how do I get Boosted', 'should I start my own publication or pitch the big ones', 'repurpose my blog onto Medium without tanking my SEO', 'what tags maximize reach', 'qué tags uso en Medium', 'com guanyar diners a Medium'. NOT writing the article's hook/structure/prose (that is medium-writing), NOT the mechanical format-and-submit-one-story step (that is medium-publishing)."
tags: [medium, partner-program, monetization, distribution, publications, cross-posting]
recommends: [medium-writing, medium-publishing, content-engine, seo-geo, decision-records]
origin: risco
---

# Medium Strategy — The Account as a Payout System, Not the Next Post

*You operate at account + monetization altitude.* You decide how a Medium presence becomes a **growth and payout system** over months: how it earns from the Partner Program, where stories live (your profile, your publication, someone else's), how they win distribution, and what gets repurposed from owned content. You do not draft the article or press the publish button — those are single-story jobs you route out. Mixing altitudes is the fastest way to give generic advice: a portfolio question answered with per-post tactics produces noise.

Your spine is a read/write loop with the account's own history. You **read** accumulated learnings before deciding and **write** the decision back, so next quarter compounds instead of restarting from a generic blog post.

## Altitude boundary — route single-story work out

| If the ask is… | Route to | Why it is not you |
|---|---|---|
| The article's hook, structure, story, prose | `medium-writing` | You decide where it goes and why; writing produces the words. |
| Format one draft, toggle canonical, schedule, submit to a pub's queue | `medium-publishing` | You set the cross-post + publication plan; publishing presses the buttons per story. |
| A calendar/repurposing plan across all channels | [`../content-engine/SKILL.md`](../content-engine/SKILL.md) | Multi-platform; you are Medium-only. |
| Push the same post to many networks at once | [`../social-publisher/SKILL.md`](../social-publisher/SKILL.md) | Distribution fan-out, not Medium monetization. |
| SEO/canonical mechanics on the *owned* site the cross-post points back to | [`../seo-geo/SKILL.md`](../seo-geo/SKILL.md) | Owned-site SEO; you only set the canonical-import decision. |
| Building a subscriber email list | [`../newsletter/SKILL.md`](../newsletter/SKILL.md) | Medium is not your list. |

## 1. Read the wiki FIRST — before any decision

Before you recommend anything, read `02-DOCS/wiki/medium/`. **Why:** Medium strategy is iterative; last quarter's Boost hits, accepted-pub list, and tag wins are the only non-generic data you have. Skipping this means re-deriving from blog advice the writer could have Googled.

Look for, in order:
- **Decision log** — prior calls on solo vs publication, which pubs were pitched/accepted/dropped, the tag sets tried.
- **Boost hit/miss log** — which stories were nominated, which got the extra reach, what they had in common.
- **Member-reading-time learnings** — which topics/formats drove member *dwell time* (the thing that pays), not just views.
- **Referral-source notes** — external vs on-platform reads (external reads now pay extra — see §3), and which off-Medium channels sent them.
- **Dead experiments** — pubs that never replied, tags that pulled nothing. Do not re-run them.

If the directory is empty or absent, **bootstrap it**: create `02-DOCS/wiki/medium/` with a `decisions/` subfolder and a `what-worked.md`, then proceed — this session becomes record #1. Templates and layout: [`references/wiki-records.md`](references/wiki-records.md).

## 2. The money model — get this right or everything downstream is vanity

Partner Program earnings are driven by **member reading time** (read + listen time from paying members, combined). Claps, highlights, and responses are secondary engagement signals, not the payout. Non-members and ads pay you nothing. Minimum payout threshold is **$10**.

- Bad: "Get this to 50k views and 2k claps." Views from logged-out readers and claps from non-members do not move the payout.
- Good: "Get members to *finish* it — depth, pacing, a reason to keep reading — because member dwell time is the meter."

The 2025-2026 overhaul changed *which dwell time pays most*. These dates are the spine connecting tags, titles, and cross-posting to money:

| Effective | Change | Strategic implication |
|---|---|---|
| 2025-10-01 | A member read originating from **outside** Medium earns a **+5% bonus**. | Off-Medium referral (newsletter, social, your blog) is now a payout lever, not just traffic. |
| 2025-11-01 | **~15% of the Partner Program budget** is allocated to stories members discover via **search engines** (e.g. Google). | SEO-discoverable titles + evergreen topics now monetize directly. |
| 2026-02 | When a non-member hits your paywall and **joins to read your story**, you earn a small one-time amount. | A genuinely worth-paying-for story can convert readers into members you get credited for. |
| 2026-06-01 | A qualifying-publication **editor who assigns themselves to a story earns 25%** of that story's earnings; the writer keeps **100%** of their original earnings. | Editors are now financially motivated to recruit and edit good writers — pubs court you (see §6). |

Conclusion to carry forward: **external + SEO referral now pay extra.** That is why the cross-posting plan (§8) and tag/title choices (§7) are monetization levers, not decoration.

## 3. Enrollment — the bar is low; the old gate is gone

The 100-follower requirement was removed in Aug 2023. Current bar — check each before advising "you're ready":
- [ ] 18 or older.
- [ ] Published at least **~6 stories**.
- [ ] Account active **~3 months**.
- [ ] File taxes / have a bank account in an **eligible country** (80+ supported).
- [ ] A paid Medium membership is **NOT** required to enroll.

If they clear this, the answer to "can I monetize?" is yes — move to the money model and distribution, not "build your following first."

## 4. Distribution mechanics — three tiers

A story does not just "go to your followers." Medium routes it through three tiers:

- **Network Distribution** — to your followers + readers who follow the story's **tags/topics**.
- **General Distribution** — broader algorithmic feeds, for any story that passes the distribution guidelines.
- **Boost** — a curated tier that gives a story extra reach across the platform.

Tags are a primary input the algorithm uses to match a story to interested readers across *all* tiers — which is why §7 treats them as a lever.

**Clearing General** = follow the distribution guidelines (original, non-spammy, not overtly promotional, well-formed). This is table stakes; most decent stories pass.

**Earning Boost** is a two-step, publication-independent path:
1. A community curator **or** a Boost-eligible publication editor **nominates** the story.
2. Medium's internal curation team **validates** it against distribution standards before it gets the extra reach.

To qualify it must be **constructive, original, insightful, well-crafted, and memorable**. You do NOT need to be in a publication to be Boosted — but being in a Boost-eligible pub gives you a nomination path you otherwise lack. Depth, disqualifiers, and the eligible-pub landscape: [`references/distribution-and-boost.md`](references/distribution-and-boost.md).

Note the common confusion to correct on sight: **views ≠ distribution.** A story can rack up views from a shared link while getting near-zero algorithmic distribution. The fix is tags + Boost-worthiness, not "post more."

## 5. Publications — solo vs your own vs joining vs pitching

Acceptance into pubs is **craft-gated, not follower-gated** — even a brand-new writer gets in if the story fits the guidelines. Decide deliberately:

| Path | Choose when | Tradeoff |
|---|---|---|
| **Solo profile** | Early, or your brand IS the draw, or you cross-post owned content with canonical (§8). | No editor nomination path to Boost; you carry all distribution yourself. |
| **Your own publication** | You publish consistently and want a branded home + the ability to nominate. | You become the editor; growth is on you; setup + curation overhead. |
| **Join an existing pub** | You want reach + an editor nomination path now, and have stories fitting its niche. | You publish on their terms and follow their guidelines/queue. |
| **Pitch an editor** | A specific big pub matches your topic and you can write to its bar. | Slower; requires originals (see tension in §8). |

How to pitch, in order: (1) **read and follow the pub's submission guidelines** — skipping this is the #1 rejection cause; (2) the story must be **100% original / never published anywhere** — Medium rejects duplicate content even when it's your own; (3) it must **not be overtly self-promotional**. The 2026-06 editor-earns-25% change means editors are now paid to find and edit good writers, so a well-targeted pitch lands better than before — lead with fit, not flattery.

## 6. Tags & titles as distribution levers

Up to **5 tags** per story. Use a deliberate mix, not five popular ones:
- **2-3 high-volume tags** for reach (e.g. `Artificial Intelligence`, `Productivity`).
- **2-3 long-tail tags** for precise, lower-competition match (e.g. `AI Coding Tools`, `LLM Evaluation`).

- Bad: 5 broad tags → `Technology, AI, Programming, Software, Coding` — you compete with everyone and match no one precisely.
- Good: `Artificial Intelligence, Programming` (reach) + `AI Coding Tools, Developer Productivity, Claude Code` (precise) — Network distribution finds the exact interested readers.

Titles now carry money: with ~15% of the budget on search-discovered reads (§3), an SEO-discoverable, search-intent title earns from the search budget. Write the title for what a member would *type into Google*, not only for a clever in-feed hook.

## 7. Cross-posting plan — protect owned SEO

To repurpose owned content (blog, newsletter) onto Medium without competing with yourself, use Medium's official **"import a story"** flow: it sets `rel=canonical` back to your original URL, so Google credits the owned site and Medium does not rank as a duplicate.

The tension to resolve every time: **most publications require originals** (§5), so the canonical-import play is for **your own profile/publication**, NOT for pitching pub editors. The decision rule:

- Repurposing owned content for reach + member reads → **canonical-import to your own profile/pub.**
- Targeting a publication → **write native (original) for that pub.** Do not import a published piece into a pub that requires originals; it gets rejected.

Pair this with §3: external referral now pays +5%, so a canonical import you also drive traffic *to* from your list earns the bonus on top.

## 8. Review / double-down loop

On a monthly/quarterly review:
1. Read `what-worked.md` and the Boost log.
2. Pick the **next bet** — double down on the tag set / pub / format that drove member reading time; name the metric it bets on.
3. **Drop dead pub relationships** — pubs that never replied or never distributed.
4. Log all of it (next section). A review you don't write down is a review you'll redo.

## 9. Write the decision back to the wiki

Every session ends with a dated record under `02-DOCS/wiki/medium/decisions/`. Minimum fields — the bet-on metric is mandatory, because a decision with no metric is an opinion, not a checkable bet:

```markdown
# 2026-06-02 — Solo vs publication for AI-tools series

Decision: Stay solo profile + canonical-import the blog series; pitch one Boost-eligible AI pub with a native original.
Rationale: 400 followers, no editor nomination path; the blog has evergreen search traffic worth importing (external +5%, search 15%).
Bets on metric: member reading time from external/search referral; 1 Boost nomination this quarter.
```

After a review, append a `what-worked.md` entry tied to specific stories/pubs/tags (e.g. "`AI Coding Tools` long-tail + Boost → 3.2h member reading time"). Full templates, layout, and the verify.sh contract: [`references/wiki-records.md`](references/wiki-records.md). Sanity-check the wiki with `scripts/verify.sh 02-DOCS/wiki/medium/`.

## Anti-patterns

| Anti-pattern | Why it fails | Do instead |
|---|---|---|
| Chasing views and claps | Neither pays; **member reading time** does. | Optimize for member dwell time and finish rate. |
| Treating views as distribution | A shared link can spike views with zero algorithmic reach. | Fix tags + Boost-worthiness, not post volume. |
| Importing an already-published piece into a pub that requires originals | Medium rejects duplicate content, even your own. | Native original for pubs; canonical-import only to your own profile/pub. |
| Five broad tags | You compete with everyone, match no one. | 2-3 popular + 2-3 long-tail. |
| Pitching without reading the pub's guidelines | The #1 rejection cause. | Read guidelines first; lead with fit. |
| Ignoring the external/search referral bonus | Leaves the +5% and the 15% search budget on the table. | Drive off-Medium traffic; write search-intent titles. |
| "Build your following first" before enrolling | The 100-follower gate is gone since 2023. | If they clear the ~6 stories / ~3 months / eligible-country bar, enroll now. |
| Never writing decisions to the wiki | Next quarter restarts from generic advice. | End every session with a dated decision record. |

## References

- [`references/distribution-and-boost.md`](references/distribution-and-boost.md) — the three tiers in depth, the Boost two-step path, the 5 curation criteria expanded, common distribution disqualifiers, the Boost-eligible publication landscape.
- [`references/wiki-records.md`](references/wiki-records.md) — decision-record + what-worked templates, the `02-DOCS/wiki/medium/` layout, and exactly what verify.sh checks.
