Because the page changes and the data does not remember. Somebody rewrites it in March; in June nobody can say whether June's numbers are better than they would have been.
Page performance is one URL's history of search, traffic and outcomes, with its own edit history marked on it.
Every edit is a marked point on the timeline. Impressions, position, clicks and enquiries run across it, so a change and what followed are readable together.
A page rewritten to answer three missing questions shows impressions flat and clicks up forty per cent six weeks later — a title and relevance win rather than a ranking one.
It will not prove causation. Seasonality, algorithm updates and competitors all move at once, and Growth shows the sequence without claiming the mechanism.
Search Console, Bing, GA4, the cluster's position, the technical issues raised and cleared, and any enquiries produced.
Content changes are detected on crawl; you can also mark a change deliberately.
Yes — algorithm updates, campaigns, site migrations.
Yes, within a cluster or by template.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.