Claude Code Revenue CTA Routing: Send Articles to PDF, Gumroad, and Consultation

Pageviews are useful, but they do not pay for the site by themselves. If a reader finishes an article and still does not know whether to download the free PDF, buy a Gumroad guide, or ask for help, the article is leaking value. Claude Code can help route the reader by intent instead of using the same CTA everywhere.

This pairs well with the content funnel audit, productive prompt brief, and verification receipt workflow. The goal is not to invent more products. It is to make the existing free PDF, Gumroad products, and consultation path easier to choose.

Choose CTA by reader state, not product name

Beginners often need confidence before they need a paid guide. Send them to the free PDF first. Readers who already use Claude Code but rewrite prompts every day are closer to Prompt Templates. Readers stuck on permissions, CI/CD, team rollout, or revenue workflow design are closer to the Setup Guide or consultation.

The same CTA should not appear in every article with the same priority. A harness article, debugging article, comparison article, and content operations article each imply a different next action. Ask Claude Code to state that decision before editing the article.

cta_routing:
  owner: "Masa"
  scope:
    allowed:
      - "read repository"
      - "edit selected files"
      - "run build or test"
    blocked:
      - "delete unrelated files"
      - "touch secrets"
      - "hide failed verification"
  proof:
    - "git diff reviewed"
    - "build command recorded"
    - "public URL opened"
    - "CTA path checked"

Copy-paste CTA audit prompt

Audit this article as a revenue path, not only as content.
Return:
1. the reader's likely search intent
2. whether the reader is beginner, intermediate, team lead, or operator
3. first CTA: free PDF, Gumroad product, or consultation
4. three internal links to include in the body
5. article-end links that must remain correct
6. public URL checks for h1, canonical, hero image, and CTA

This makes Claude Code decide why the CTA belongs there before it edits copy. The result is usually more useful than adding a generic button at the end.

Turn routing into a small rule

The JavaScript below is not an ad platform. It is a simple operating rule that keeps article body, end CTA, Products page, and Training page aligned.

const routes = {
  beginner: "free_pdf",
  repeated_prompts: "prompt_templates",
  setup_blocked: "setup_guide",
  team_or_revenue_design: "consultation",
};

export function chooseCta(intent) {
  return routes[intent] ?? "free_pdf";
}

console.log(chooseCta("repeated_prompts"));

Once the rule is written, Claude Code can update body links, related product copy, and verification notes without guessing the business decision every time.

Three real examples

• A getting-started article should lead with the free PDF, then mention the Setup Guide later. Consultation appears only when the reader is rolling out Claude Code to a team or production workflow.
• A debugging article should push Prompt Templates more strongly. The reader already has a repeated pain, so copyable debugging prompts are a natural next step.
• A content operations article should show both Products and consultation. A self-serve reader can buy a guide, while a reader stuck on funnel design or verification discipline may need a call.

Failure cases

The common failure is placing the same “buy now” button on every article. Beginner traffic often needs a low-friction free asset first. The opposite failure is putting only the free PDF on intermediate articles where the reader is ready to pay for a repeatable workflow.

Multilingual routing can also fail. The article body is translated but the CTA remains English. The Gumroad path is English-first, but the localized body never explains that. The public URL returns 200, but canonical or article body points to a different slug. These issues depress the numbers after pageviews.

Free PDF, Gumroad, and consultation split

The free cheatsheet lowers friction for beginners and comparison readers. 50 Prompt Templates helps readers who repeat review, debugging, and refactoring requests. The Setup Guide fits readers blocked by permissions, setup, hooks, MCP, or CI/CD. Consultation fits workflow design, team adoption, and revenue routing decisions.

What I verified for this article

This article includes a CTA audit prompt, routing rule, three examples, failure cases, and explicit links to the free PDF, Gumroad products, and consultation. The next metrics are PDF signup rate, Gumroad click rate, and Training page visits by article slug.

Operating note after publication

When you use this pattern in production, do not stop at “the file exists.” Treat the work as done only after the public URL lets a reader choose the next action. On mobile width, inspect h1, opening body, hero image, free PDF form, Gumroad links, and consultation links. If the body is correct but the article-end CTA points to the wrong product, the revenue path is still unfinished.

For localized articles, matching slugs are not enough. Check the opening body and CTA language for Japanese, English, Chinese, Korean, Spanish, French, German, Portuguese, Hindi, and Indonesian. A translated heading with English body copy is a failed localization because the reader cannot trust the next step.

For the next improvement pass, look beyond pageviews. Put PDF signup starts, Gumroad clicks, Products page visits, Training page visits, country mix, and search source in the same brief. Claude Code makes better revenue decisions when the metric says whether to strengthen the free asset, Prompt Templates, Setup Guide, or consultation path.