Page RPM is a way to summarize estimated publisher earnings relative to pageviews. It is useful because traffic volumes differ: a site with 100,000 views and a site with 20,000 views cannot be compared fairly by looking only at total earnings. RPM puts earnings on a common per-thousand-pageviews basis.
The page RPM formula
Keep the earnings and pageviews from the same date range and the same reporting source. Use pageviews in the denominator—not ad impressions—when calculating page RPM. Google’s AdSense help defines page RPM using this same relationship. Read Google’s Page RPM definition.
Worked example
Suppose the report shows 450 in estimated earnings and 100,000 pageviews. Divide 450 by 100,000, then multiply by 1,000: the page RPM is 4.50 in the report’s currency.
The 4.50 value is a ratio for the period that has already happened. It does not mean every future thousand pageviews will generate exactly 4.50. Demand, visitor geography, ad formats, viewability, content, seasonality, consent signals and policy compliance can all affect actual results.
Page RPM versus impression RPM
Page RPM uses pageviews. Impression RPM uses ad impressions. A page can generate more than one ad impression, so these metrics answer different questions. Check the label in the reporting product before comparing values across dashboards.
How to compare periods fairly
- Use the same reporting platform and currency.
- Compare equivalent days or weeks, accounting for seasonality.
- Segment pages or traffic sources only when the sample is large enough to avoid over-interpreting noise.
- Compare revenue alongside pageviews, engagement and content changes.
- Record the dates and any changes to ad setup so the comparison has context.
Use RPM as a diagnostic, not a target by itself
A higher RPM is not automatically evidence of a better experience. Do not encourage accidental clicks, misleading layouts or content created only to chase high-value traffic. Focus first on accurate, useful content and a clear user journey. Treat RPM as one measure in a wider view of publisher performance.
Calculate your own page RPM
Use the AIVUV Page RPM Calculator with matching earnings and pageviews. The result stays an estimate of a historical ratio; it cannot forecast a future payout by itself.
Example: revenue can rise while RPM falls
Imagine one month had 20,000 pageviews and 110 in earnings. Page RPM was 5.50. The following month had 40,000 pageviews and 180 in earnings, making page RPM 4.50. Total earnings increased, but earnings per thousand pageviews decreased. Neither number alone explains why. The second month may have had a different article mix, visitor geography, device mix, ad demand or viewability.
This is why a good comparison asks two questions: what happened to total outcomes, and what changed in the ratio? Use the report breakdowns available to you to investigate, rather than guessing based only on the headline RPM.
Quick data-quality checklist
- Confirm the report uses pageviews rather than ad impressions.
- Confirm earnings and pageviews use the same dates and property.
- Check whether reporting delays or adjustments affect the period.
- Note major changes in traffic sources, page types or ad setup.
- Compare more than one period before treating a movement as a trend.
Sources and further reading
The sources below support definitions or general methods discussed in this guide. AIVUV's examples are illustrative and do not replace platform-specific reporting or professional guidance.