Website Ad Revenue Calculator

Estimate website ad revenue from pageviews and planning Page RPM, with optional fill-rate and sensitivity adjustments.

Example: 250,000
Example: $18
$
Advanced assumptions Optional fees, reserves, and planning targets
Example: 100%
%
Example: 0.8
Example: 1.2
Example: $10,000
$

Review the result

Monthly revenue
--
Range
--
Per 10k views
--

How to use this calculator

Start with observed Page RPM when possible

Google defines Page RPM as estimated earnings divided by pageviews, multiplied by 1,000. A historical Page RPM already reflects the actual mix of filled and unfilled inventory, so leave the optional fill adjustment at 100% when using it.

Use fill rate only for a forward-looking inventory assumption

If your RPM assumption represents the value of fully filled inventory, lower the fill-rate adjustment to model unfilled requests. Do not apply it again to an observed Page RPM.

  • Observed Page RPM: use 100% fill adjustment.
  • Quoted RPM for filled inventory: apply a forecast fill rate.
  • Keep pageviews, RPM, and revenue target in the same monthly period.

AdSense vs total website revenue

AdSense is one monetization source. Use an AdSense-only Page RPM for an AdSense estimate, or a blended Page RPM calculated from total publisher revenue for a whole-site estimate.

What affects website ad revenue

Revenue changes with geography, content category, device mix, seasonality, ad density, direct sponsorships, header bidding, viewability, and traffic quality.

AdSense vs header bidding vs direct ads

AdSense is one network. Header bidding can increase competition for impressions, while direct sponsorships can change the revenue model entirely.

Why calculators are estimates

Generic revenue calculators cannot know advertiser demand, user intent, refresh rules, policy status, or sold direct inventory. Use ranges and update assumptions from real reports.

Formula quick reference

  • Observed Page RPM model: revenue = pageviews / 1,000 x Page RPM
  • Inventory forecast model: revenue = pageviews / 1,000 x planning RPM x fill rate
  • Target pageviews = target revenue x 1,000 / (planning RPM x fill rate)

Worked example

Observed Page RPM example

Inputs: 250,000 monthly pageviews, $18 observed Page RPM, and 100% fill adjustment

Result: $4,500 base monthly revenue and a $3,600 to $5,400 sensitivity range

Note: Because the RPM is historical, the optional fill adjustment stays at 100%.

Common mistakes

  • Applying fill rate to a historical Page RPM and discounting unfilled inventory twice.
  • Mixing ad-impression eCPM with pageviews; use Page RPM for pageviews and eCPM for ad impressions.
  • Treating an RPM benchmark as a guaranteed rate across geographies, devices, or seasons.

What the result means

  • Use your own matched historical Page RPM before using an industry estimate.
  • Model a low-to-high range because traffic mix, demand, viewability, and seasonality change publisher revenue.

Website Ad Revenue Calculator FAQ

How much ad revenue can a website make?

It depends on pageviews, RPM, niche, geography, device mix, viewability, advertiser demand, and the monetization setup.

What is Page RPM?

Page RPM is estimated earnings divided by pageviews, multiplied by 1,000. A blended Page RPM can use total revenue from all included monetization sources.

Should I apply fill rate to historical Page RPM?

Usually no. Historical Page RPM already reflects the revenue and pageviews actually observed. Keep the fill adjustment at 100% unless your RPM assumes fully filled inventory.

Should I use this for YouTube or Twitch?

No. This page is scoped to website publisher revenue.

What affects website ad revenue the most?

Traffic volume, geography, niche, device mix, viewability, ad setup, fill rate, and advertiser demand usually matter most.

Is AdSense the same as total website ad revenue?

No. A site can earn from AdSense, header bidding, direct ads, sponsorships, or other ad networks.

Should I use sessions or pageviews?

Use pageviews when you have them. If you only have sessions, multiply sessions by pages per session before applying Page RPM.

Why is a generic ad revenue estimate unreliable?

It cannot know your geo mix, ad stack, policy status, viewability, or direct sales, so it should be treated as a planning range.