I want to start with the honest version of this story.
I spent over two weeks convinced my Google Reader Revenue Manager setup was working perfectly. The dashboard looked fine. The CTAs were published. Everything checked out on my end.
Not a single reader saw a single prompt.
The reason was something I’ll get to later in this post. But that mistake taught me more about how RRM actually works than any tutorial did.
If you’re trying to turn your blog into a paid publication, whether through subscriptions, reader contributions, or just a registration wall Google Reader Revenue Manager is one of the most practical free tools available right now. I’ve used it. I’ve broken it. And in this post, I’ll walk you through the entire setup so you don’t repeat what I did.
Let’s go from zero to live.
What Is Google Reader Revenue Manager?
Google Reader Revenue Manager, usually called ‘RRM’ for short, is a free tool that lets you add a paid or gated layer to your blog. You can use it to charge readers for access, collect voluntary contributions, run surveys, capture newsletter sign-ups, or simply ask readers to register before reading.
It lives inside Google Publisher Center, which is Google’s dashboard for publishers. Once you set it up, you get a small JavaScript snippet that goes on your site. That snippet is what shows prompts to your readers.
The tool handles checkout, payments, and reader identity through Google Accounts. Readers who subscribe or register stay logged in across every device where they’re signed into Google. That’s genuinely useful. You’re not asking readers to create a new account from scratch — they’re using something they already have.
The transaction fee is 5% per payment, which already includes credit card processing fees. There’s no monthly software cost. For a small blogger trying to keep overheads low, that’s a reasonable deal.
Who Is This Actually For?
Here’s something Google doesn’t make obvious enough: RRM is not just for news publishers.
The messaging has always leaned toward journalism. But the tool works for gaming blogs, education sites, sports coverage, personal finance writers, and food blogs — pretty much any content-first site with an audience worth engaging.
According to recent industry data, 70% of publisher professionals now generate at least some revenue from subscriptions in 2025, up from 56% in 2024. That’s not just newspaper websites. That’s bloggers and independent creators across every niche.
RRM is also available globally. The Reader Revenue Manager is currently available in over 40 countries, including India, the US, the UK, Australia, Canada, Brazil, Germany, France, and many more.
So if you’ve been thinking RRM was built for The Guardian and not for you, it was built for you too.
What You Need Before You Start
Before you open Publisher Center, gather these things.
For any setup, you need:
- A Google Account
- A live website with a canonical URL (more on why this matters shortly)
If you plan to collect payments (subscriptions or contributions), you also need:
- Your personal or business information for identity verification
- Your publication’s logo in PNG or JPEG format — Google recommends 1000×1000 pixels, with a minimum of 512×512
If you only want registration walls, newsletter sign-ups, or surveys, you don’t need a payments profile at all. You can skip identity verification entirely and still get substantial value from the tool.
One more thing to check right now: are you running AMP pages?
RRM code snippets are not valid AMP. If you’re running an AMP-only site, RRM will not work. If your site has both AMP and regular pages, RRM will only function on the regular ones. AMP visitors won’t see anything.
I’ll tell you why this matters from personal experience in a moment. But check this now, before you do anything else.
Step 1: Set Up Your Publication in Google Publisher Center
Go to publishercenter.google.com and sign in with your Google Account.
Click “Add publication”. Enter your site’s name and URL. Google will ask you to verify ownership of the site. The easiest way to do this is through an existing Google Search Console property — if your site is already verified in Search Console, the process is quick.
Once verified, your publication appears in the dashboard.
Now click into your publication. Look for “Reader Revenue Manager” in the left navigation menu. This is where everything lives.
At this point, you’ll be prompted to choose an organisation type. You select either “For-Profit” or “Nonprofit”. If you’re a non-profit, note that the standard subscription and contribution CTAs are disabled — instead, you get custom CTAs to redirect readers to your existing donation platform.
Most bloggers are selecting “for-profit” here, even if the blog is small. That unlocks the full CTA menu.
Step 2: Choose Your Content Access Strategy
This is the most important decision in the whole setup. Before RRM can do anything, it needs to know what kind of prompt to show readers.
Here are your CTA options and what each one actually does:
Paywall (Subscription) — Readers pay to access your content. You set the price and billing cycle. Requires a payments profile.
Registration Wall — Readers register via their Google Account for free. No payment. No new username or password. They just sign in with Google. This is what I started with, and I’d recommend it for most bloggers as a first step. It builds your audience list before you ask anyone to spend money.
Newsletter Sign-Up — A prompt asking readers to subscribe to your email list. No payment required.
Contribution Ask — A prompt asking readers for a voluntary one-time or recurring payment. Think of it like a tip jar. Requires a payments profile.
Survey — You give readers access to content in exchange for answering a short survey. No payment required.
My opinion: start with a registration wall or a survey if you’re new to gating content. They require the least setup, they don’t ask readers for money right away, and they give you a list of real readers to market to later.
Don’t start with a hard paywall on day one if your blog has fewer than a few thousand monthly readers. You’ll push people away before they’ve had a chance to fall in love with your content.
Step 3: Set Up Your Payments Profile (Only If You Need It)
Skip this step entirely if you’re going with a registration wall, newsletter sign-up, or survey. Those features cost nothing and don’t require payment infrastructure.
If you’re setting up subscriptions or contributions, navigate to Payments inside Publisher Center and connect or create a Google Payments profile. You’ll need to add your personal or business information and go through identity verification.
After setup, the critical step that many people miss is adding your bank account details.
After setup is complete, make sure to add your bank account details to your payments profile. Without your bank account info, you can’t receive payments from Google.
To do it: under “More options”, click “Go to your bank details”, then select “How you get paid”, fill in the required fields, and click Save.
It sounds obvious. But I’ve seen bloggers go live with subscriptions and wonder where their money is, only to realise they never added bank details. Don’t let that be you.
Step 4A: Installing RRM on WordPress (The Easy Way)
If you’re on WordPress, this is where the process gets much simpler than you’d expect.
To set up Reader Revenue Manager for your site, go to Site Kit > Settings > Connect More Services > Set up Reader Revenue Manager.
Google’s Site Kit plugin handles everything automatically. It places the necessary code snippet on your site, gives you page-level controls, and integrates with the WordPress block editor so you can manage which posts and pages show prompts.
If you don’t have Site Kit installed, go to your WordPress plugin directory, search for “Site Kit by Google”, install it, and connect it to your Google Account. It will also connect your Search Console and Google Analytics 4 in the same setup flow, which is genuinely useful.
Once your publication is connected, you can choose from the following options: Keep the default selection (uses default settings from the Reader Revenue Manager module), exclude from Reader Revenue Manager (prevents any configurations from displaying), or use “open access” (surveys, paywalls, and other prompts are ignored for that specific post or page).
For placement, you can set CTAs to appear site-wide or only on specific content types. Posts, pages, or custom post types — it’s your call.
One important note: if you have created a new publication, it needs to be reviewed by Google. This may take up to 2 weeks. You can continue to connect the Reader Revenue Manager module in Site Kit while your publication is being reviewed, but users won’t see any paywalls or CTAs until it has been approved.
So don’t panic if nothing shows up on your live site immediately. Wait out the review.
Step 4B: Manual Code Snippet (Non-WordPress Sites)
If you’re not on WordPress, you install RRM via a JavaScript snippet.
In Publisher Center, go to Reader Revenue Manager and click “Add code snippet to your site”. You’ll also find it under the “CMS Sync” tab if you’ve already completed setup.
Add the snippet to the <head> tag of each page.
For paywalled content specifically, there are two snippet types: one for open-access pages and one for gated pages. If you’re running a subscription model and want to charge for certain posts only, make sure you’re placing the correct snippet on the correct pages.
If you have multiple subscription products — say, a standard tier and a premium tier — each product has its own product ID. The code snippet associated with your sports subscription is added to your sports pages. The code snippet associated with your news subscription is added to your news pages. The same logic applies to any niche category split on your blog.
If you use a tag manager like Google Tag Manager, you can paste the snippet there and fire it on all pages. That’s cleaner than editing templates manually.
My Personal Failure: The AMP Problem That Ate Two Weeks
Okay. Here’s the story I promised you at the start.
When I set up RRM on my blog, I went through every step correctly. Publisher Center was configured. The snippet was in place. My CTAs were live and approved. I checked everything twice.
Nothing showed up for readers.
I spent the first few days thinking it was a cache issue. I cleared the cache. Still nothing. I thought maybe it was a plugin conflict. I tested on a staging site. Still nothing. I opened support tickets.
Then, almost two weeks in, someone pointed out the obvious: a large portion of my blog’s traffic was hitting AMP pages. My theme had AMP enabled by default from a plugin I’d installed and largely forgotten about.
For hybrid sites — canonical pages plus AMP versions — RRM works on canonical pages and is simply absent on AMP versions. Users who arrive via AMP will not see CTAs.
My mobile traffic was going straight to AMP. RRM was completely invisible to those readers. The readers hitting desktop or direct non-AMP URLs were seeing the prompts fine. But that was a fraction of my traffic.
The fix was straightforward: I deactivated the AMP plugin and redirected all traffic to canonical pages. Within 24 hours, the CTAs were showing properly across the board.
Check your AMP situation before you do anything else. It will save you a lot of confusion.
Step 5: Add Structured Data for Paywalled Content
This step only applies if you’re gating content behind a paywall or registration wall.
Google needs to understand which of your articles are behind a gate so it doesn’t penalise you for content that appears differently to Googlebot than it does to regular readers. Without structured data, you risk being flagged for cloaking.
The markup you need is so-called. It’s a JSON-LD block that tells Google whether a given article is open or gated.
For WordPress publishers, Yoast SEO, RankMath, and Schema Pro all support the isAccessibleForFree configuration. For non-WordPress sites, add the JSON-LD block to each gated article template.
If you use Yoast, this setting is in the Yoast SEO sidebar inside the post editor. For RankMath, look under Schema settings. You don’t need to write code manually if you’re on WordPress and using one of these plugins.
After you’ve deployed structured data, check the Subscribed Content report in Google Search Console. It will show you any articles where Google detects gated content but can’t find valid markup.
Don’t skip this step. It protects your search visibility while you’re running a paywall.
Step 6: Set Your Free Article Limit and Test Everything
For paywalls, you need to decide how many free articles readers get before hitting the gate. This is called a metered paywall.
Google’s guidance suggests starting at around 10 free articles per month and iterating based on your data. That’s a reasonable starting point. Too restrictive and readers bounce before they care about your content. Too generous and nobody ever hits the paywall.
Before you go fully live, test the experience yourself.
Open an incognito browser window. Visit one of your gated articles. Does the prompt appear? Does the registration or checkout flow work? Does it look right on mobile?
Then test the post-conversion experience. After registering or subscribing, does the content unlock properly?
Catch these issues before real readers do. A broken checkout flow is the fastest way to lose a subscriber you worked hard to get.
Common Mistakes That Kill the Setup
Based on my own experience and what shows up repeatedly in publisher community threads, these are the things that go wrong most often:
AMP pages blocking CTAs. Already covered this one. Check now if you haven’t.
Mismatched domains in Publisher Center. Your publication URL in Publisher Center must exactly match your live site URL. If your site is https://www.yourblog.com entered https://yourblog.com without the www, the snippet won’t fire correctly.
Missing bank account details. You set up payments but never linked your bank. Google can’t pay you to an account that doesn’t exist in the system.
Going live before publication approval. Publishing CTAs before Google approves your publication means nothing shows up. Wait for the approval email. Publication review may take up to 2 weeks.
Skipping structured data on gated pages. If you’re running a paywall and haven’t implemented isAccessibleForFree markup, you’re exposing yourself to search ranking issues down the line.
Setting the paywall too tight too early. If readers can’t sample your content before hitting a payment wall, most of them leave. Build trust first.
My Honest Take on Google RRM
I’ve used paid third-party membership plugins and platforms. Some are great. Most are expensive. A few are genuinely complicated to set up.
RRM isn’t perfect — the two-week approval wait is frustrating, and the AMP issue is more common than Google acknowledges in its documentation. But for a blogger who wants to start charging for content without paying for software or dealing with complex integrations, it’s hard to argue against free with a 5% transaction fee.
The registration wall alone, even without any payment, is worth setting up. Building a list of verified reader identities through Google Accounts gives you something that a passive newsletter form can’t — non-dismissible prompts that actually convert. One documented comparison found registration walls generated 16x more registrations than traditional newsletter signup forms.
Start there. Get your reader list. Then layer in contributions or a paywall once you know those readers are actually engaged with your content.
Frequently Asked Questions
Is Google Reader Revenue Manager free to use? Yes. There’s no monthly cost to use RRM. If you collect paid subscriptions or contributions, Google charges a 5% transaction fee that includes credit card processing. Registration walls, surveys, and newsletter sign-ups are completely free with no transaction fees.
Do I need to know how to code to set up RRM? No. Reader Revenue Manager is a free, self-service platform to launch subscriptions or contributions with no programming skills required. WordPress users can set it up entirely through the Site Kit plugin. Non-WordPress users need to paste one JavaScript snippet into their site’s header, which most platforms make easy.
How long does Google take to approve a publication? Publication review typically takes up to two weeks. You can complete the technical setup while the review is in progress, but your CTAs won’t appear to readers until approval is confirmed.
Can I use RRM on a non-news blog? Yes. RRM works for any publisher with a live website and content worth gating. Gaming, food, personal finance, education, sports, and lifestyle blogs all qualify.
What happens if my site uses AMP? RRM is incompatible with AMP pages. If you have an AMP-only site, RRM will not work. If you have a hybrid site with both AMP and canonical pages, RRM will only function on canonical pages. Consider disabling AMP before setting up RRM.
Can I use RRM without charging readers? Yes. Registration walls, newsletter sign-ups, and surveys require no payment from readers and no payment profile on your end. These are useful even if you never plan to charge for content.
What countries support Google Reader Revenue Manager? RRM is available in over 40 countries, including the United States, India, the United Kingdom, Australia, Canada, Brazil, Germany, France, Japan, Singapore, and more. See the full list on the Publisher Center Help page.
Do I need Google Analytics 4 connected to use RRM? You don’t strictly need GA4 to use RRM, but connecting it lets reader interaction data flow into your analytics. It’s worth connecting if you want to track how readers engage with your prompts.
Wrapping Up
Setting up Google Reader Revenue Manager is genuinely manageable. Most of the steps are straightforward. The dashboard is clear. The WordPress path through Site Kit is as close to one-click as these things get.
The things that trip people up are the things Google doesn’t shout about: the AMP incompatibility, the two-week approval wait, the structured data requirement for paywalls, and the bank account details you have to add separately. None of those are dealbreakers. They’re just gaps in the onboarding that catch people off guard.
Go through this post step by step. Check your AMP situation first. Pick the right CTA for where your audience is right now. And don’t launch a hard paywall before your readers have had time to trust what you’re publishing.
The rest of it works exactly like it’s supposed to.
This post reflects my personal experience setting up and using Google Reader Revenue Manager. All information was accurate as of July 2026. Always check the official Google Publisher Center Help pages for the most current requirements and country availability.
