Home β€Ί Blog β€Ί How to Monetize a Jekyll Blog in 2026 (7 Strategies That Actually Work)
Tutorial

How to Monetize a Jekyll Blog in 2026 (7 Strategies That Actually Work)

Practical ways to make money from a Jekyll blog β€” affiliate marketing, sponsorships, digital products, consulting, and more. With realistic income expectations.

How to Monetize a Jekyll Blog in 2026 (7 Strategies That Actually Work)

Jekyll is a static site β€” it has no built-in monetization features. But that does not mean you cannot make money from it. The absence of a CMS or plugin marketplace just means you need to wire up monetization yourself. Here is how, with realistic numbers.

A note on traffic and income

Every monetization strategy depends on traffic. A Jekyll blog earning meaningful money typically has 10,000+ monthly page views. If you are below that, focus on content and traffic first β€” the strategies below will scale with your audience.

Strategy 1: Affiliate marketing

Affiliate marketing means promoting other companies’ products and earning a commission when readers buy through your link. It is the most common monetization strategy for developer blogs because it requires no product creation and scales with content.

Programmes worth joining for a Jekyll/developer blog:

  • GitHub Marketplace β€” affiliate links for tools and apps
  • Digital Ocean / Linode β€” hosting referrals ($25–100 per referral)
  • Amazon Associates β€” 3–10% commission on books and tools
  • Gumroad Creator Referrals β€” earn from referred creators
  • Theme marketplaces β€” refer buyers to JekyllHub or ThemeForest

What earns: Tutorial posts that recommend specific tools (β€œThe Jekyll plugin I use for X”) convert well. Review posts (β€œIs X worth it in 2026?”) convert even better. Lists (β€œBest Jekyll plugins”) convert when readers have clear purchase intent.

Realistic income: $50–500/month at 10k–50k monthly visitors, depending on your niche and audience quality.

Implementation in Jekyll:

Store your affiliate links in _data/affiliates.yml:

digital_ocean:
  url: "https://m.do.co/c/YOURREF"
  label: "DigitalOcean"

Reference in templates:

{% assign do = site.data.affiliates.digital_ocean %}
<a href="{{ do.url }}" rel="nofollow sponsored" target="_blank">
  Try {{ do.label }}
</a>

Strategy 2: Display advertising

Display ads (Google AdSense, Carbon Ads, Ethical Ads) show ads on your pages and pay per thousand impressions (CPM) or per click (CPC).

Best ad networks for developer blogs:

  • Carbon Ads β€” developer-focused, high CPM, tasteful single ad. Requires application.
  • Ethical Ads β€” privacy-focused, used by Read the Docs. Pays $2–3 CPM.
  • Google AdSense β€” lower CPM for developer content (~$2–5), easy to set up.

Realistic income: Carbon Ads pays $1–3 per 1,000 impressions. At 50,000 monthly visitors: $50–150/month. Not transformative, but passive.

Implementation: Add the ad snippet to your _includes/ for easy placement across layouts:

<!-- _includes/carbon-ad.html -->
<script async type="text/javascript" src="//cdn.carbonads.com/carbon.js?serve=YOUR_CODE&placement=jekyllhub" id="_carbonads_js"></script>
{% if site.carbon_ads_code %}
{% include carbon-ad.html %}
{% endif %}

Strategy 3: Sponsored content and newsletter sponsorships

Once you have an audience, companies pay to reach them. A sponsored post or newsletter mention is typically one of the highest-paying per-impression formats for developer content.

Rates (rough benchmarks for developer blogs):

  • Newsletter sponsorship: $50–500 per send (depending on list size)
  • Sponsored post: $200–2,000 per post (depending on traffic and niche)
  • Social mention: $50–300 per post

How to set it up: Create a /advertise/ page with your audience stats (monthly visitors, newsletter subscribers, demographics) and a contact form. Companies will find you.

Use _data/ to manage sponsor information:

# _data/sponsors.yml
current:
  - name: "Netlify"
    url: "https://netlify.com"
    logo: "/assets/images/sponsors/netlify.svg"
    blurb: "The fastest way to build and deploy Jekyll sites."

Strategy 4: Sell digital products

Digital products β€” ebooks, templates, courses, starter kits β€” have high margins because there is no inventory or shipping. A Jekyll blog about Jekyll is particularly well-positioned to sell Jekyll-related products.

Products that sell well from developer blogs:

  • Jekyll starter templates β€” A pre-configured Jekyll setup your readers can buy and build on ($9–49)
  • Ebooks / guides β€” β€œThe Complete Jekyll Deployment Guide” ($19–39)
  • Video courses β€” If you have YouTube presence ($49–199)
  • Notion templates, Figma files, design assets β€” If your blog covers design

Implementation: Use Gumroad, Lemon Squeezy, or Payhip for simple checkout. Embed a buy button in your Jekyll site:

<a href="https://yourstore.gumroad.com/l/product-slug" class="btn btn--primary">
  Buy for $29 β†’
</a>

Strategy 5: Premium Jekyll themes

If you can build a good Jekyll theme, selling it is one of the best monetization strategies available on a Jekyll blog. Your blog readers are exactly your target buyers.

List on JekyllHub, Gumroad, and ThemeForest. A well-marketed theme at $39 can earn $500–2,000/month with the right SEO and placement.

We covered this in detail in How to Sell a Jekyll Theme.

Strategy 6: Consulting and freelance work

Developer blogs build credibility. If you write about Jekyll professionally, companies building Jekyll sites will find you and some will want to hire you.

Add a /hire/ or /consulting/ page to your site:

---
layout: page
title: "Hire Me"
permalink: /hire/
---

I help companies build fast, maintainable Jekyll sites...

Consulting rates for Jekyll/static site work: $80–200/hour depending on experience and location. Even one project per month can be significant income.

Strategy 7: Newsletter paid subscriptions

If you have a loyal newsletter audience, paid subscriptions via Ghost, Substack, or Lemon Squeezy let you charge for premium content.

This works best when you have a consistent publishing cadence and clearly differentiated free vs premium content. Most successful paid newsletters have 2,000+ free subscribers before launching a paid tier.

Monthly subscription pricing: $5–15/month for consumer content, $20–50/month for professional/B2B content.

Combining strategies

The most successful developer blogs combine multiple streams:

  1. Affiliate links in tutorial content (passive, scales with traffic)
  2. One ad network (Carbon Ads) in the sidebar (low effort, passive)
  3. A digital product (ebook or template) promoted within posts
  4. A consulting page for high-value direct work

This combination can realistically generate $500–2,000/month from a Jekyll blog with 20,000–50,000 monthly visitors β€” achievable within 12–18 months of consistent publishing.

What not to do

  • Do not add pop-up overlays β€” they hurt user experience and Core Web Vitals
  • Do not accept every sponsored post offer β€” one bad endorsement damages trust
  • Do not add multiple ad networks β€” ad clutter destroys reader experience
  • Do not launch a paid product before you have an audience who trusts you

Build the audience first. The money follows.

Display advertising on Jekyll: what actually works

Display advertising is the most accessible monetisation method β€” sign up for an ad network, add a script tag, start earning. But the revenue per visitor varies enormously between networks, and the wrong choice can harm your reader experience and Core Web Vitals scores more than the revenue justifies.

Google AdSense is the default starting point for most bloggers. It accepts sites with even modest traffic, the implementation is a JavaScript embed, and payments are reliable. The downsides are low RPM (revenue per thousand impressions) compared to premium networks, minimal control over ad appearance, and privacy compliance requirements (cookie consent banners in GDPR jurisdictions). Jekyll sites on GitHub Pages cannot use Google AdSense directly because GitHub Pages serves sites from github.io domains, which AdSense does not approve β€” you need a custom domain.

Mediavine and AdThrive (now Raptive) are the premium alternatives, but they require minimum traffic thresholds β€” Mediavine requires 50,000 monthly sessions, AdThrive requires 100,000 monthly pageviews. Sites that qualify for these networks earn significantly higher RPMs (often 3-5Γ— AdSense rates), and the networks have teams dedicated to optimising ad layout for user experience and Core Web Vitals. If your Jekyll blog reaches these traffic levels, transitioning from AdSense to Mediavine is typically worthwhile.

Carbon Ads is the best option for technical content and developer-focused blogs. It serves a single, tastefully designed ad from technology companies β€” development tools, SaaS products, developer conferences β€” that is relevant to developer audiences. RPM is moderate but ad quality is high, user experience impact is minimal (no tracking scripts, no GDPR consent wall), and the ad appearance is consistent with technical blog aesthetics. Carbon requires a curated site with an established developer audience to be accepted.

Affiliate marketing that maintains reader trust

Affiliate marketing β€” earning commission on products you recommend β€” works exceptionally well for Jekyll-related content because the products (themes, hosting services, developer tools) are genuinely useful to the audience and the commissions are meaningful.

The affiliate programmes most relevant to a Jekyll blog are hosting providers (Cloudflare, Netlify, Vercel, and DigitalOcean all have affiliate programmes with referral commissions), theme marketplaces (ThemeForest, Creative Market), and developer tools (Ahrefs, Semrush, and other SEO tools have high-commission affiliate programmes). A single post about the best Jekyll hosting options, with affiliate links to three recommended providers, can earn commissions for years from organic search traffic.

The trust risk with affiliate marketing is real: readers who feel that your recommendations are motivated by commission rather than genuine evaluation lose trust in your content. Mitigation requires genuine editorial standards β€” only recommend products you have personally used and found valuable; disclose affiliate relationships clearly in every post that contains them (FTC requirement in the US, equivalent requirements in most other jurisdictions); and recommend against products even when there is an affiliate option if your honest assessment is negative.

Building and monetising an email list

Email is the highest-converting channel for selling paid products, courses, and services β€” consistently outperforming social media and search traffic for conversion rates. An email list of 1,000 engaged subscribers who trust your expertise is typically more valuable than 10,000 monthly blog visitors who arrived via search and have no relationship with you.

The monetisation path through email is: publish valuable free content on your blog β†’ convert readers to email subscribers with a compelling lead magnet or newsletter pitch β†’ build trust through consistent email content β†’ offer paid products or services to subscribers who have repeatedly opted in to your recommendations.

Paid products that work well for technical bloggers with Jekyll expertise include: e-books covering advanced topics not available in free content (β€œAdvanced Jekyll: Collections, Data, and Custom Plugins”), video course series on specific workflow topics, one-on-one consulting or theme audit services, and access to a private community or office hours. The revenue potential scales with audience trust and product quality, not with traffic volume β€” a small list of highly engaged readers generates more paid product revenue than a large list of passive subscribers.

Sponsored posts β€” where a company pays to have their product or service featured in your content β€” are the highest revenue-per-piece form of blog monetisation, but they require the largest audience and the most careful management of reader trust.

For a Jekyll blog, relevant sponsors include theme marketplaces, hosting providers, developer tool companies, and the broader Jamstack ecosystem. Companies that sell to developers and developers-who-design are your natural sponsors, and they typically value placement on technical content that reaches their specific audience.

Set your sponsored content policy before you receive your first inquiry. Minimum traffic requirements, disclosure requirements (all sponsored content clearly labelled), editorial control (you write the content, not the sponsor), and content standards (you only endorse products you would genuinely recommend) are the minimums worth articulating. A transparent sponsorship policy builds reader trust and attracts sponsors who respect editorial independence β€” the combination that makes sponsored content sustainable long-term.

Pricing for sponsored posts depends on your traffic, authority, and audience specificity. A Jekyll blog with 20,000 monthly organic visitors and a focused developer audience can command $300-800 per sponsored post from relevant sponsors. Building a media kit (one-page document with traffic stats, audience demographics, and sponsorship options) makes outreach to potential sponsors straightforward and signals professionalism.

Share LinkedIn