AdSense calculator
Estimate monthly and yearly display ad revenue from pageviews, Page RPM, CTR, and CPC. Use the result to plan traffic goals, compare RPM scenarios, and decide whether your site needs more traffic, better commercial intent, or stronger monetization pages.
Enter a traffic level and Page RPM. Optional CTR and CPC fields help compare the estimate with a click-based model.
Page RPM means revenue per thousand pageviews. The formula is simple: divide estimated revenue by pageviews, then multiply by 1,000. If a website earns $500 from 100,000 pageviews, the Page RPM is $5. The calculator uses the same relationship in the other direction. When you enter 100,000 pageviews and a $5 Page RPM, it returns $500 per month and $6,000 per year.
Page RPM is useful because it gives small publishers a clean planning unit. Instead of guessing whether a site is large enough, you can ask sharper questions. What happens if traffic reaches 250,000 pageviews? What happens if the RPM improves from $3 to $8? How many pageviews are needed for a $1,000 monthly target? These estimates are not guarantees, but they make growth targets easier to reason about.
Start with a conservative pageview number. If the site is already live, use analytics data from the last 28 or 30 days. If the site is new, use a target such as 10,000, 50,000, or 100,000 monthly pageviews. Then add a Page RPM assumption. A broad global content site may need a low assumption. A site with strong buyer intent, English traffic, and a useful tool or comparison page may justify a higher scenario.
You can also compare the RPM model with a CTR and CPC model. In that model, revenue equals ad impressions multiplied by click-through rate and cost per click. For example, 200,000 ad impressions at a 1 percent ad CTR and $0.25 CPC would estimate $500. This is still simplified because modern display ad reporting also includes auction mechanics, viewability, ad formats, invalid traffic filtering, and other factors. The reason to compare the two models is not to predict the exact AdSense dashboard. It is to understand which lever matters most.
The table in the calculator shows revenue at $2, $5, $10, and $20 Page RPM. This range is intentional. A single RPM number can create false confidence, especially before a site has stable traffic. If the $2 scenario is unacceptable, the site may need better commercial topics, stronger internal links to monetizable pages, or a non-ad revenue line such as templates, affiliate recommendations, or sponsorships. If the $10 or $20 scenario would make the business work, the next question is whether the niche, country mix, and page type can realistically support that level.
This calculator is not connected to your AdSense account and does not inspect your ad setup. It does not know your fill rate, ad viewability, invalid traffic adjustments, seasonal advertiser budgets, user geography, or policy status. It should be used for planning and scenario comparison, not for financial promises. A publisher should still review AdSense reports, traffic quality, page speed, layout, content value, and policy compliance before making business decisions.
The safest use is to keep three scenarios: conservative, expected, and upside. A new site might plan around $2 to $5 RPM until real data arrives. A site with strong search intent and tier-one English traffic might add a higher upside scenario. After launch, replace assumptions with actual Page RPM from your dashboard and compare month over month.
Next in the RedBit roadmap: Website RPM Simulator, AdSense Approval Auditor, Invalid Traffic Checklist, and GSC Query Opportunity Finder.
AdSense revenue is not based only on pageviews, but pageviews are a useful planning input. Actual earnings depend on ad impressions, viewability, advertiser demand, country mix, page topic, device, placement, CTR, CPC, and invalid traffic filtering.
A good Page RPM depends on niche, country, device mix, seasonality, and ad setup. A small publisher might see less than $2 RPM on low commercial intent traffic, while high value English traffic can be much higher. Use ranges, not a single promise.
Revenue can fluctuate because traffic sources change, advertiser budgets change, auction pressure changes, pages receive different country mixes, engagement changes, or invalid traffic systems filter more activity.
Yes, if the network reports revenue and pageviews or impressions. The RPM formula is general. Network-specific rules, fill rates, fees, and reporting definitions can still make the final number different.