Publisher planning tool
Model display ad revenue by traffic mix, page type, and ad density. Use this simulator before a site has enough AdSense history, or when you need to explain why revenue changed even though pageviews looked stable.
Model how country mix, page intent, and ad density can change display ad revenue before you have stable AdSense data.
A simple revenue calculator asks for pageviews and one RPM number. That is useful, but it hides the reason RPM changes. A website can have the same number of pageviews in two months and still earn very different revenue if the traffic mix, topic mix, device mix, or ad layout changes. This simulator separates a few of those assumptions so you can reason about the drivers instead of staring at one blended number.
The model starts with three traffic groups: tier-one traffic, tier-two traffic, and rest-of-world traffic. You can set both the share of traffic and the RPM assumption for each group. The tool normalizes the percentages, calculates a blended base RPM, then applies a page type factor and an ad density factor. The result is a planning estimate, not a promise. Its value is in comparison: what changes if tier-one traffic rises, if a page becomes more commercial, or if ad density is reduced?
Use the simulator when planning a new publisher site, reviewing a sudden RPM drop, or deciding which page cluster deserves more work. For example, a pure informational article may get impressions but low ad value. A tool page or a comparison page may have fewer pageviews but stronger intent. The simulator makes that tradeoff visible without pretending that every visitor is worth the same amount.
It also helps avoid a common mistake: adding more ads before checking traffic quality. If revenue is low because the country mix changed or the page topic has weak advertiser demand, adding more placements may hurt user experience without fixing the real problem. In that case, a better next action may be improving internal links to high-intent pages, refreshing titles to attract better queries, or building a calculator, checklist, or template that gives users a reason to visit.
The conservative scenario applies a lower multiplier to the adjusted RPM. Use it for planning cash flow, especially before AdSense approval or before the site has stable organic traffic. The base scenario uses the assumptions you entered. The upside scenario shows what the same traffic volume could produce if intent, geography, seasonality, and implementation improve. If the business only works in the upside case, the site probably needs a second revenue line such as templates, affiliate recommendations, sponsorships, or a lightweight paid tool.
This simulator does not connect to AdSense, GA4, Search Console, or a server log. It does not know your actual fill rate, viewability, ad formats, invalid traffic filtering, seasonality, policy status, or audience behavior. It also uses broad country tiers, which are only a planning shortcut. Real RPM can differ sharply by niche, query intent, advertiser demand, device type, and page layout. Treat the output as a decision aid, not a financial forecast.
Use the AdSense Revenue Calculator for a direct PV x RPM estimate. Next in the roadmap are the AdSense Approval Auditor, Invalid Traffic Checklist, and GSC Query Opportunity Finder.
Website RPM is a planning metric for revenue per thousand pageviews. It can be calculated across a whole site, a page type, or a traffic segment. This simulator estimates a blended Page RPM from country mix, page intent, and ad density assumptions.
Advertiser demand is different by country, language, niche, and purchase intent. A site with mostly high value English traffic may earn a different RPM from a site with broad global traffic, even when pageviews are equal.
Heavy ad density can increase short-term ad inventory, but it can also reduce engagement, make the site feel low quality, slow down pages, and create review risk. Use heavy density only after checking user experience and policy quality.
No. It is a planning simulator, not an account forecast. Actual AdSense revenue depends on auction demand, ad formats, fill, viewability, invalid traffic filtering, policy status, seasonality, and many other signals.