AVAIVUVPublisher Lab
Publisher planning tool

Revenue Goal & Traffic Gap Calculator

Turn a monthly revenue goal into an estimated pageview requirement. The result depends on your RPM assumption and is a planning scenario, not a promise of earnings.

Enter your report values

Target revenue for the chosen month, in your reporting currency.
Use pageviews from a representative recent month.
Use an observed page RPM from a comparable reporting period.

Your result

Enter your values and select Calculate to see the result.

Formula used

Required pageviews = revenue goal ÷ assumed page RPM × 1,000

Worked example

A $1,000 goal at a $5.00 assumed page RPM implies 200,000 pageviews. At 80,000 current pageviews, the implied gap is 120,000 views. That is a mathematical scenario, not a forecast that the traffic will arrive.

Use a measured RPM, not a market promise

The calculator translates a revenue target into a traffic requirement using the page RPM you enter. Use your own report where possible. An RPM from another site, country, topic or season may not represent your future results.

Example: make the gap visible

Assume a monthly revenue goal of $1,000, current traffic of 80,000 pageviews, and a recent page RPM of $5.00. The model implies 200,000 pageviews are needed at the same RPM. The current traffic would correspond to $400 in estimated revenue under that assumption, leaving a $600 revenue gap and 120,000 additional pageviews in the simple model.

Why the result is not a traffic forecast

Required pageviews are calculated while holding RPM constant. In practice, adding traffic may change the share of countries, devices, pages, returning visitors, ad formats and search queries. Those changes may raise or lower the observed RPM. Treat the output as one scenario in a planning range, not a target that can be reached by publishing a certain number of pages.

Build a more useful plan

  1. Record a comparable recent period’s earnings, pageviews and page RPM.
  2. Set a revenue target and calculate the gap.
  3. Separate the actions you control (content quality, distribution, technical reliability and useful page experiences) from external factors such as ad demand.
  4. Model more than one RPM scenario instead of assuming the best recent value will persist.
  5. Review actual data after the next period and update assumptions.

What not to do

Do not manufacture traffic, buy invalid visits, encourage ad clicks, or build thin pages solely to chase volume. More pageviews that do not serve user intent are not a reliable business strategy and may create policy risk.

Google defines page RPM as estimated earnings divided by pageviews, multiplied by 1,000. This calculator simply reverses that relationship to solve for pageviews.

Frequently asked questions

Should I use the highest RPM I have ever seen?

Usually not. Use a representative comparable period and model a lower scenario so the plan does not depend on an outlier.

Does this tell me how many articles to publish?

No. Traffic per article varies widely. Focus on useful content and measure actual search and user performance.

Does reaching the pageview number guarantee the revenue target?

No. RPM may change with audience mix, ad demand, seasonality and other factors.

Related tools

These tools summarize the values entered. Check the source report and keep metric definitions consistent before making a publishing decision.