This website ad revenue calculator estimates monthly and annual display-ad revenue from two inputs: monthly pageviews and page revenue per thousand pageviews (page RPM). It shows conservative, base, and upside scenarios without claiming that a network will accept your site or deliver a particular RPM.
Start with pageviews and page RPM for the same site, currency and period. Visitors, sessions and ad impressions use different denominators. The traffic table below provides hypothetical examples; replace those assumptions with your own network and analytics evidence.
Interactive decision tool Use pageviews and page RPM from the same measurement period. This tool does not predict acceptance or earnings. Illustrative scenarios only. Network acceptance, RPM, traffic, and earnings are not guaranteed.Estimate display-ad revenue scenarios
Illustrative revenue
Scenario Monthly Annualized Conservative Base Upside
Estimate disclaimer: The output is an illustrative scenario, not a forecast or guarantee. Network eligibility, advertiser demand, geography, content, consent, policy compliance, viewability, seasonality, and implementation can change actual results.
The formula
Google AdSense defines RPM as estimated earnings divided by pageviews, impressions, or queries, multiplied by 1,000. Reversing the page-RPM formula gives the estimate used here:
Estimated revenue = monthly pageviews ÷ 1,000 × page RPM
Google also warns that RPM is not the amount actually earned; it is a normalized rate used for comparison. See the official AdSense RPM definition.
Keep the unit consistent. Page RPM uses pageviews. Impression RPM uses ad impressions. Session RPM uses sessions. Entering an impression RPM beside pageviews produces a meaningless result.
Ad revenue at 10,000 to 1 million monthly pageviews
The rates below are deliberately chosen hypothetical page-RPM inputs, not measured market averages or a promise that an ad network will pay them. Each cell is pageviews ÷ 1,000 × page RPM, before operating costs.
| Monthly pageviews | $5 page RPM | $10 page RPM | $20 page RPM |
|---|---|---|---|
| 10,000 | $50 | $100 | $200 |
| 50,000 | $250 | $500 | $1,000 |
| 100,000 | $500 | $1,000 | $2,000 |
| 500,000 | $2,500 | $5,000 | $10,000 |
| 1,000,000 | $5,000 | $10,000 | $20,000 |
How many pageviews would a $1,000 monthly target require?
Reverse the same formula: required pageviews = target revenue ÷ page RPM × 1,000. Holding RPM constant is a modeling assumption, not a claim that more traffic will preserve the audience or ad rate.
| Hypothetical page RPM | Monthly ad-revenue target | Required monthly pageviews |
|---|---|---|
| $5 | $1,000 | 200,000 |
| $10 | $1,000 | 100,000 |
| $20 | $1,000 | 50,000 |
Use a range rather than selecting the most attractive row. Google’s RPM definition explains the denominator; the separate per-visitor example later in this guide uses a user count instead of pageviews.
How the three scenarios work
You enter a base page RPM. The calculator applies visible factors:
| Scenario | RPM factor | What it tests |
|---|---|---|
| Conservative | 70% of base | Lower advertiser demand, weaker mix, or seasonal softness |
| Base | 100% of base | Your stated assumption |
| Upside | 130% of base | Better demand or execution, without presenting it as expected |
The ±30% spread is a scenario convention, not an industry benchmark. Choose a base assumption you can explain and compare the three cases with your own evidence.
Worked example
Assume a site receives 100,000 monthly pageviews and you model a $12 page RPM.
100,000 ÷ 1,000 × $12 = $1,200 per month
The default scenarios are:
| Scenario | Modeled page RPM | Monthly estimate | Annualized estimate |
|---|---|---|---|
| Conservative | $8.40 | $840 | $10,080 |
| Base | $12.00 | $1,200 | $14,400 |
| Upside | $15.60 | $1,560 | $18,720 |
Annualized means the monthly scenario multiplied by 12. It does not model seasonality or growth.
Use a defensible pageview input
Use pageviews from the source analytics property for a representative period. Check that tracking is consistent and that the number is not dominated by bot traffic, internal visits, a one-time referral spike, or a short-lived viral page.
For an acquisition, compare analytics with server or content-delivery data and the ad network's own reporting. Google explains that Search Console and Analytics properties have distinct roles and access controls; request delegated access rather than relying on screenshots or shared passwords.
If the site is growing or declining, calculate several periods separately instead of averaging away the trend.
Use RPM as a scenario, not a promise
Do not copy another publisher's RPM without matching the underlying conditions. Actual page RPM can vary with:
- Visitor geography: advertiser demand differs by country and region.
- Content and intent: topics attract different advertisers and bids.
- Viewability and layout: ads that are not meaningfully viewed may earn differently.
- Device mix: mobile and desktop experiences can produce different inventory and behavior.
- Seasonality: advertiser spending can change throughout the year.
- Consent and privacy: lawful consent choices can affect available targeting and demand.
- Network and contract: eligibility, revenue share, floor rules, and ad formats vary.
- Traffic quality: invalid or policy-violating traffic can be excluded or penalized.
Use your own historical network data when it is clean. For a site without ad history, run a broad range and treat the result as a screening question, not value.
Fill rate and impressions require a separate model
For a detailed scenario, choose the unit that earns the payment. A served-impression model can be written as eligible ad opportunities × fill rate × the matching revenue rate per 1,000 served impressions ÷ 1,000. This assumes those input definitions actually align; it is not an alternative name for the page-RPM calculation.
A rate priced per 1,000 viewable impressions instead requires the qualifying viewable-impression count. Apply viewability only when the contract and the count require that conversion. A realized ad RPM already derived from recorded impressions and earnings should not receive a second unexplained viewability discount.
For example, a hypothetical 200,000 matching ad impressions at a realized $4 ad RPM reconstructs $800. Applying a separate 60% viewability factor would reduce that to $480 without a justified change of billing unit. Identify the contract and qualifying count before changing the formula.
Keep requests, served impressions, measurable impressions and viewable impressions distinct. Source the ratios and rate from matching periods and definitions, and avoid combining the detailed estimate with the page-RPM result. Google's ad-RPM definition supplies the relevant ad-impression denominator.
Model seasonality month by month
Multiplying one month by 12 is useful for orientation but weak for a seasonal site. A better annual scenario assigns pageviews and page RPM to each month:
| Month | Pageviews | Page RPM | Modeled revenue |
|---|---|---|---|
| January | 80,000 | $10 | $800 |
| February | 75,000 | $9 | $675 |
| March | 90,000 | $11 | $990 |
Continue through all 12 months and sum the results. Use prior source data where available. If the site lacks history, make the uncertainty visible rather than copying one peak-season RPM across the year.
Run separate traffic and RPM assumptions. A site can gain pageviews while its audience mix shifts toward lower-demand geography or devices, producing less-than-proportional revenue.
Separate ad revenue from website profit
The calculator estimates publisher ad revenue, not profit. To reach normalized operating profit, subtract the costs required to sustain the traffic and implementation, such as:
- content production, editing, and media;
- hosting, CDN, software, analytics, and consent tooling;
- development, ad operations, and performance work;
- email, contractors, and market-rate owner labor;
- refunds, invalid-traffic adjustments, or contractual deductions where applicable.
If ad density slows the site, harms usability, or reduces other conversions, the cost may also appear in lower affiliate, product, lead, or subscriber value. Optimizing one revenue line can weaken the asset as a whole.
Use source reports in an acquisition
For a site purchase, export monthly pageviews, page RPM, estimated earnings, finalized payments, deductions, and geography/device mix for matching periods. Reconcile those reports to bank or payment records and investigate differences between estimated and finalized revenue.
Then ask whether the network account, placements, consent setup, and advertiser relationship will continue under the buyer. If the buyer must apply for a new account, model a transition period and a wider downside range. Platform acceptance and historical RPM should never be represented as included assets unless the provider supports that transfer.
Keep the seller's source report, your normalized schedule, and the calculator scenario as three separate artifacts. That separation makes it clear which values were observed, adjusted, and projected.
Check your inputs and read the result
Enter monthly pageviews and page RPM, then select Calculate scenarios. The calculator accepts pageviews from zero to one billion and page RPM from $0 to $1,000. These broad input bounds catch mistakes; they do not identify a realistic traffic or earnings level.
Correct any displayed input error before calculating. Read the monthly and annualized values beside the stated formula. Annualized is monthly multiplied by twelve; it does not predict seasonal changes, traffic growth or future rates. Use the result as a transparent scenario to compare with source reports.
Do not value a site from ad revenue alone
An ad-revenue scenario is one line in a valuation model. A buyer will also test the operating costs, content rights, traffic durability, concentration, compliance, owner workload, and transferability of the ad account and other assets.
Network participation can be personal or entity-specific. Verify whether the buyer can assume an account, must apply independently, or needs a transition plan. Do not represent a current RPM as transferable when the underlying network relationship is not.
For a deal, reconcile actual revenue with source reports using the website due diligence checklist. Then carry normalized profit—not gross ad revenue—into the website valuation calculator.
Frequently asked questions
What is page RPM?
Page RPM is estimated earnings divided by pageviews and multiplied by 1,000. It normalizes revenue so periods or sites with different traffic levels can be compared.
Is page RPM the same as CPM?
No. Page RPM uses pageviews and publisher earnings. CPM usually refers to a rate per 1,000 ad impressions or another defined ad unit. A page can create multiple impressions.
How does revenue per visitor differ from page RPM?
Revenue per visitor divides a defined revenue amount by a defined visitor or user count for the same period. It is a per-user amount, while page RPM divides earnings by pageviews and multiplies by 1,000. One user can generate several pageviews, so the denominators are not interchangeable.
For an original hypothetical example, assume $20 of ad earnings, 1,000 measured users, and 2,000 pageviews in one month. Ad revenue per measured user is $20 ÷ 1,000 = $0.02. Page RPM is $20 ÷ 2,000 × 1,000 = $10. Both describe the same assumed earnings; neither is a forecast or a customer-value estimate.
Record whether revenue means ads alone or all website revenue, and use matching dates, currency, site scope, and user definition. Google Analytics distinguishes total users from active users; a count labeled “unique visitors” in another system may use different identity and measurement rules. Do not add daily unique counts to invent a monthly unique count. Keep this calculator's pageview input paired with page RPM; calculate the separate per-user measure from its own matching reports. These definitions were checked November 4, 2026.
Does more pageviews always mean proportionally more revenue?
Not necessarily. Audience, geography, device, content, demand, viewability, consent, and traffic quality can change as the site grows.
What RPM should I enter?
Use your own clean historical page RPM where possible. Otherwise, enter a deliberately broad scenario range and label its source and date. No generic number is reliable for every site.
Next step
Use the calculator to expose assumptions, not to manufacture precision. Save the pageview source, RPM source, measurement period, network, and material implementation notes beside each scenario. That evidence will matter more than the highest annualized number.

