Revenue paths for indie sites: ads, payments and tool subscriptions — methods and trade-offs

1. Ground rules first

This post covers methods and trade-offs only. There are no income figures, and I won't present any single site as a success story. I'm Hugozen, and I practise monetizing indie sites myself. This site currently has no ads and no checkout; articles are free to read, and it may offer products, services or consulting later, clearly labelled when it does. That is today's fact, not a permanent promise.

I split revenue paths into two groups: traffic-based and payment-based. Which one fits depends on what kind of site you have, not on which one pays more.

2. Traffic-based: advertising

Display ads such as AdSense are the usual starting point. The logic is simple: pages get visits, ads monetize them, and you don't build a product or run support.

Upsides:

• Low threshold; you don't have to build any payment feature.
• Fits content and information sites where visitors don't register.
• Natural match for sites whose traffic comes from search.

Costs:

• Approval is required. The site needs enough original content and the basic pages (about, privacy, a way to reach you), or it may be rejected.
• Revenue is tied to traffic, and search traffic moves with algorithm changes.
• Ads slow pages down and take up space, which hurts experience and can affect search performance.
• For visitors in the EEA and UK you need a certified consent management platform (CMP) for ad consent, which is more involved than analytics consent.
• Policy risk: invalid clicks or restricted content types can get an account limited.

When it fits: pages that people read and leave, from an owner willing to accept the effect on experience. When it doesn't: tools with a clear task, where ads compete with the user's goal.

3. Payment-based: how to collect

If your site offers a tool, a service or a digital product, you have to collect payment. The hard part for an indie site isn't wiring up payments; it's tax and compliance.

Your own payment gateway (for example Stripe or PayPal directly):

• Upside: transparent fees and more control.
• Cost: you're the seller. You handle sales tax and VAT across countries, invoices, refunds and chargebacks. For one person, that's hard to sustain.

Merchant of Record (MoR):

• A MoR is a third party that is the legal seller: it collects from the buyer, handles sales tax, VAT, invoicing and most compliance, then settles the remainder to you after fees. Services such as Paddle and Creem fall into this category.
• Upside: tax and compliance sit with them, which matters a lot for one person selling across borders.
• Cost: fees are usually higher than a bare gateway; you control less of the buyer relationship and refund rules; what you can sell is limited by their policies (some categories are excluded); payouts have schedules and thresholds.

My judgment: for one person, with buyers in many countries and many sites to run, the "less to worry about" of a MoR is likely worth more than the fee difference. If you only sell in one country and the business is simple, your own gateway is fine.

Either way, one precondition applies: first find out whether anyone will pay for the thing, then wire up collection. Don't build a polished payment flow and then go looking for buyers.

4. Tool subscriptions

If the site is a tool with ongoing value (not a calculator people use once and leave), subscriptions are one path.

Upside: steadier income than one-off sales, and a reason to keep improving the tool.

Costs:

• A subscription is a long-term commitment: accounts, login, support, refunds, data retention. For one person that is far heavier than a static site.
• Drawing the free/paid line is hard: too tight and nobody uses it, too loose and nobody pays.
• Cancellation, failed renewals and data export are easy to overlook.

So I'm cautious: only when the tool has real recurring use and I'm willing to maintain it for years do I consider it. Otherwise I'd rather sell something one-off, or keep it free.

5. Other routes

• Affiliate links: recommend someone else's product and earn a commission on sales. It requires that you've used it and believe in it, and it must be clearly labelled. Once readers suspect a recommendation is about commission, trust is hard to win back.
• Sponsorship: a brand pays to appear in your content. Also must be labelled, with editorial independence kept.
• Consulting and services: sell your experience as a service. Income tracks your time and doesn't scale, but depends least on traffic.
• Digital products: templates, checklists, small guides. Make once, sell repeatedly, as long as someone wants to buy.

6. A few principles

1. Value first, monetization second. Without readers and a real use case, every revenue path is empty.
2. Monetization must not damage trust. Ads, affiliate links, sponsorship and paid content must be labelled and reflected in the privacy and about pages.
3. Don't launch everything at once. One main path per site; give it time before changing.
4. Know what you can maintain long term. Once subscriptions and accounts ship, they're obligations.
5. Compliance first. Consent for European visitors, tax by country, and refund rules aren't things to patch in later.

7. My own trade-offs

No numbers, just how I choose right now:

• Tool sites go subscription. A tool with an ongoing use case fits a subscription, provided I'm willing to maintain it for the long run.
• Content sites get nurtured first. The first job of a content site is to get its content and indexing healthy; monetization comes later, for example Google AdSense or directly placed ad slots. Putting ads on a content site that hasn't found its feet hurts the experience and pulls attention away from quality.

These are my current trade-offs, not a verdict; if they change, I'll update the post.

Looking back: keyword choice and indexing decide whether anyone shows up; the revenue path decides whether the people who show up can sustain the site. The previous post covers the former: keywords, launch, indexing and GEO. There's no public contact address on this site; to follow new posts, subscribe to the RSS feed.