How to Sell Individual Articles, Chapters, or Issues on WordPress (Without a Subscription Plugin)
The default model for WordPress membership plugins is one price, one unlock.
You pay $20 a month, you get access to everything.
You pay $200 a year, you get access to everything.
You pay $500 lifetime, you get access to everything.
For most membership sites, this is the right model.
For publishers selling individual issues, chapters, articles, or reports as standalone products, it is the wrong model.
A magazine publisher does not want one price for all 60 back issues plus every future issue.
A serialized fiction writer does not want to lump every chapter into one subscription.
A manga or anime creator releasing one chapter at a time does not want their readers paying a monthly fee for an archive of two chapters.
A research analyst selling individual whitepapers does not want to bundle a year of reports into one membership fee.
These publishers want each piece to be its own product, with its own price, sold individually, with permanent access after purchase.
That model has almost no living, well-maintained, well-documented solution in the WordPress space.
This post is the answer.
The Reddit Thread That Started This Post
A magazine publisher posted in r/WordPress recently asking exactly this question.
“I’ve been playing for months now with setting up a digital version of my magazine, but after a few days of setting things up, I always run into some unaffordable pro version / extra plugin / setup fee, etc. The latest disappointment is Leaky Paywall, to set up a link that sends readers back to the page they read before registering is $299/month! It’s the price for their launch package. WTAF? … I can obviously pay per transaction, but I am not signing up for a monthly subscription as my website is tiny.”
Pete from Leaky Paywall showed up in the thread and was straightforward about it.
“We work with mid-sized news and niche publishers who are serious about building subscription revenue, and that pricing reflects the strategy and support that comes with it. So yeah, for a magazine just getting started, that’s not the right fit.”
That is the most honest possible framing of the problem.
Leaky Paywall is a real product built for a real audience.
That audience is mid-sized publishers with budget.
It is not built for the independent magazine publisher with a tiny site who wants to charge for individual issues.
Add the 5% revenue cut Leaky Paywall takes on top of the $299/month launch package and the $750 setup fee, and the math is unambiguous.
For a small publisher just trying to sell their first issue, that pricing structure is overkill before the first sale is made.
What the Thread Recommended Instead, and Why None of It Fits
The Reddit thread filled up with alternatives.
Most of them miss the original question.
Paid Memberships Pro, MemberPress, Restrict Content Pro
All three are good membership plugins.
All three are built around the tier model.
You pay once for a tier, you unlock everything in that tier.
None of them are designed for “buy chapter 7 for $2.99, buy chapter 8 next month for $2.99, accumulate a library of individually-purchased pieces over time.”
You can hack them into that shape with enough custom work, and you are then fighting against their core design every time you publish a new chapter.
“Set Up Two WordPress Installs”
One Redditor recommended setting up two completely separate WordPress installations: one for the public site, one for the members area on a subdomain.
For a publisher who just wants to sell individual issues of a small magazine, this is dramatic overengineering.
Two installs means two databases, two backups, two security surfaces, two sets of plugin updates, two of everything.
The OP said the site is tiny.
Migrate to Ghost, beehiiv, or Substack
Same problem in a different shape.
Throw away the existing WordPress site, the existing content, the existing domain authority, and the existing audience to switch platforms.
You also move from owning your platform to building on rented land.
Your readers’ email addresses belong to the platform.
Your content lives on their servers.
Your business operates under their terms and their fee schedule.
WooCommerce as a Digital Products Store
Technically possible.
You install WooCommerce, treat each chapter or issue as a digital product, then layer a separate membership plugin on top to handle the gated access.
By the time you have stitched subscriptions, taxes, access control, and digital delivery together, you have built a $700+/year stack for what should have been a $49 problem.
Easy Digital Downloads
Closest fit conceptually.
EDD sells digital products as individual items.
The mismatch is that EDD is built around the “deliver a downloadable file after purchase” model.
Publishers selling gated reading content want the content to stay on their WordPress pages, beautifully formatted, with the publisher’s branding, accessible online whenever the buyer logs back in.
EDD can be bent into that shape with add-ons.
It is not its native shape.
The Pay-Per-Item Pattern, Explained
The right tool for this job is GetPaid’s Restrict Paid Content add-on.
GetPaid is a free WordPress payments plugin that handles checkout, subscriptions, taxes, and invoicing.
Restrict Paid Content is a $49/year add-on that turns GetPaid into a per-item paywall engine.
Here is the pattern.
The publisher creates one GetPaid Item per chapter, article, issue, or report.
Each Item gets its own title, its own description, and its own price.
Chapter 1 is one Item at $2.99.
Chapter 2 is a separate Item at $2.99.
Issue 7 of the magazine is its own Item at $9.99.
The whitepaper on Q4 market trends is its own Item at $14.99.
Each Item is independent.
The Restrict Paid Content add-on then associates each protected page on the WordPress site with its specific Item.
When a buyer hits the page for Chapter 1, they see a paywall offering them Chapter 1 for $2.99.
When they pay, the Item gets associated with their account, the paywall lifts, and they have permanent access to Chapter 1.
The next month, they come back, click on Chapter 2, see a paywall offering Chapter 2 for $2.99, click buy, and now their account holds both chapters.
Over time, the buyer accumulates a personal library on the publisher’s site.
This is the closest WordPress-native equivalent to the Kindle library model.
The Three Configurations
Restrict Paid Content supports three configuration patterns out of the box.
Configuration A: Individual Items Per Chapter
Every chapter, article, or issue is its own Item with its own price.
Best for serialized fiction (light novels, web novels), manga and anime publishers releasing chapters one at a time, individually-priced magazine issues, individually-priced whitepapers or reports, and individually-priced premium articles.
Set up:
- In GetPaid, create one Item per piece of content (Chapter 1, Chapter 2, Issue 7, and so on) with the price you want for each
- On each protected WordPress page, configure Restrict Paid Content to require purchase of the matching Item
- Buyers see a paywall per page, buy what they want, and end up with a library of individual purchases on their account
This is the canonical use case Restrict Paid Content was built for.
The original customer who drove the feature was an anime publisher releasing one chapter at a time and needed each chapter to be its own product with its own price.
Configuration B: One Umbrella Item
One GetPaid Item priced at a flat fee unlocks the entire catalog of protected pages.
Best for publishers selling a complete library at one price.
A magazine archive at $49 for all past issues.
A course library at $99 for everything.
A research vault at $199 for the full set of reports.
Set up:
- Create one GetPaid Item at the umbrella price
- Configure every protected page to require purchase of that single Item
- Buyers pay once, unlock everything
Configuration C: Hybrid
Many publishers offer both options and let the reader choose their entry point.
Set up:
- Create individual Items for each piece of content
- Create an umbrella Item for full library access
- On each protected page, configure Restrict Paid Content to accept either the individual Item OR the umbrella Item
- Buyer chooses: buy this chapter for $2.99, or buy the whole library for $29.99
The hybrid configuration is the strongest converter for publishers with a real catalog.
Casual readers buy a single chapter to test the work.
Committed fans see the math on the library deal and upgrade.
How the Setup Actually Works
The implementation is simpler than the conceptual setup above might suggest.
Restrict Paid Content adds one new block to your WordPress editor, called GP > Restrict Paid Content.
That block is a container.
You drop any content inside it (paragraphs, images, video, downloadable files, embeds) and that content becomes gated.
Here is the entire setup for a single chapter, article, or issue:
- Install and activate the free GetPaid plugin and the Restrict Paid Content add-on
- In GetPaid → Items, create one Item per piece of content with the price you want for each
- Edit the WordPress page where the gated content lives, insert the GP > Restrict Paid Content block, and paste your premium content inside it
- In the block settings, select which GetPaid Item unlocks the block and customize the message non-buyers see (offer text, buy button, optional teaser excerpt)
- Publish
That is the entire workflow.
One useful detail worth highlighting: each Restrict Paid Content block supports a built-in teaser excerpt feature, configurable in the block settings.
You can show the first paragraph or two of your premium content publicly (good for SEO, good for previewing your work to non-buyers) before the paywall kicks in.
For the hybrid configuration described above (individual Items OR an umbrella Item unlocking the same page), the block accepts multiple Item IDs with a “match any” setting that lets either purchase grant access.
For developers who prefer working in code, a shortcode equivalent is available with all the same options.
The complete walkthrough with screenshots is in the Restrict Paid Content setup guide on the GetPaid documentation site.
What This Costs to Build
A complete pay-per-item paywall on WordPress, using GetPaid plus Restrict Paid Content:
- WordPress: free
- GetPaid plugin: free, with Stripe and PayPal included
- Restrict Paid Content add-on: $49/year for a single site
Total: $49/year.
No setup fee.
No revenue cut.
No monthly subscription.
Compare to Leaky Paywall’s launch package as documented in the Reddit thread.
$299/month, plus a 5% revenue cut, plus a $750 setup fee.
A publisher selling $1,000/month in individual issues would pay $50/month in revenue cuts to Leaky Paywall alone, on top of the $299/month subscription, on top of the $750 upfront setup fee.
That is $4,338 in year one, before the publisher takes home a single dollar.
The same publisher selling $1,000/month with GetPaid plus Restrict Paid Content pays $49/year total.
Zero revenue cut.
Zero setup fee.
Zero monthly subscription.
The pricing matches the size of the problem.
Who This Is Built For
Restrict Paid Content is built for publishers whose product is content, sold per unit, with returning buyers.
- Independent magazine publishers selling individual issues
- Serialized fiction writers releasing chapters one at a time (web novels, light novels, ongoing serialized series)
- Manga, anime, and comics creators selling chapters individually
- Researchers and analysts selling individual whitepapers or industry reports
- Newsletter operators who want to sell deep-dive premium articles individually rather than as a subscription
- Course creators selling individual modules or lessons à la carte
- Trade publications selling premium articles per piece
The common thread is the business model.
Each piece of content is a product.
The buyer is making a per-purchase decision.
The buyer comes back to make another per-purchase decision.
The Buyer’s Experience
The buyer creates a free account on first purchase.
The account is required, because there is no way to gate content permanently to an anonymous buyer.
That account requirement is actually a feature for this business model.
After the first purchase, the account holds the purchase forever.
Every additional purchase from that same publisher gets added to the same account.
Over time, the buyer ends up with a personal library on the publisher’s site that grows every time they come back.
This matters for two reasons.
First, it makes the buyer’s next purchase frictionless.
They are already logged in.
Their payment details are on file.
Buying chapter 8 is one click after they bought chapter 7.
Second, the library itself becomes valuable to the buyer over time.
After buying 20 chapters of a serialized novel, the buyer’s account holds 20 chapters.
That accumulation is the closest WordPress-native equivalent to a Kindle library or a Substack archive.
The publisher gets a returning buyer who comes back by choice, not by subscription obligation.
The reader gets a permanent library of exactly what they paid for, with no risk of losing access if they cancel anything (there is nothing to cancel).
This is a different relationship than the subscription model, and for the right kind of publisher, it is a better one.
What Restrict Paid Content Does Not Do
Honesty about scope.
Restrict Paid Content does the per-item paywall job specifically.
It is not a general-purpose membership plugin.
There are things it does not do, and you should know what they are before you decide it fits your use case.
It does not drip content on a schedule.
There is no “release one chapter per week automatically” feature.
You publish what you publish, when you publish it, and you set up the matching Item before the page goes live.
It does not handle per-item free trials.
The paid trial pattern works for ongoing subscriptions, not for buy-once-access-forever items.
It does not subscribe buyers to “all future chapters.”
Every new piece you publish is a separate Item that buyers manually choose to purchase.
There is no automatic enrollment in future content.
If you want the subscription model (predictable monthly access to everything), use UsersWP Membership with GetPaid instead.
The setup is documented in our paywall tutorial, and our best WordPress membership plugin guide covers when the subscription model is the right fit.
For the architectural difference between the two models, see our breakdown of WordPress membership plugins vs subscription plugins.
If you want the per-item model with permanent buyer libraries, Restrict Paid Content is built for exactly that.
Final Thoughts
The pay-per-item model is the right model for some publishers and the wrong model for others.
It is the right model when your content is consumed in discrete units, when your readers make per-purchase buying decisions, and when their relationship to your work is “I want this specific piece” rather than “I want continuous access to your work as it comes out.”
It is the wrong model when your readers want ongoing access to everything, when value compounds over time rather than per-unit, and when a subscription would fit both you and them better.
If you fall in the first group, GetPaid plus Restrict Paid Content is the WordPress-native way to do this without paying a four-figure setup fee and a percentage of your revenue.
At $49/year flat, with no revenue cut and no monthly subscription, the pricing matches the size of the problem.
Pick the configuration that fits how your readers actually want to buy.
Ship the first item.
Let the library accumulate from there.
