How to read RPM after updating an old article

After updating an old article, read RPM together with the page’s new audience, intent, and ad coverage before deciding whether the update helped or hurt.

An old article update can change more than text quality. A new title can attract different searches. A comparison table can make the page more commercial. A refreshed opening can improve engagement but change which ad units appear above the fold. A new internal link can send more mobile readers into the page. If revenue changes after the update, the creator needs to know which part of the page and audience changed first.

Start by recording the update itself. What sections changed, what date did the page go live, did the URL change, did the title or meta description change, and were affiliate links, ad blocks, images, tables, or schema added? Then compare the same weekday range before and after the update. Split the result by country, device, traffic source, landing page, and ad coverage. If the update gained low-RPM traffic from a broad query, the page may be performing better for reach while earning less per thousand views.

Also check whether reader intent shifted. A tutorial rewritten as a buying guide may raise affiliate clicks but lower display ad RPM. A buying guide rewritten with more informational context may bring search traffic earlier in the decision journey. Those are not simple wins or losses; they are monetization mix changes.

Do not reverse the update from one noisy day. Write a short note: what changed, what moved with it, and what the next smallest test should be. The safe next action might be reviewing mobile ad spacing, adding clearer criteria, strengthening disclosure, or waiting for another weekly comparison.

How to read RPM after updating an old article

// COMMENTS

ON THIS PAGE