You can now see whether the SERP's dominant retrieval intent matches your page's structure, directly in the analysis header — along with an AIO indicator when Google is serving an AI Overview for your keyword.
ContentGrapher fetched SERP data and used it to sharpen recommendations, but users had no visibility into what that data revealed. A mismatch between the page's structural role and what the SERP rewards was the most actionable signal in the system — and it was invisible.
The PRR verdict in the analysis header told users how their page was structured, but not whether that structure matched what Google was rewarding for the keyword. When those diverge, the page is built for a different job than the one the SERP is optimising for — a structural decision, not a ranking one.
The three SERP fields needed (prrConsensus, prrAmbiguous, aioPresent) were already computed and in client state. Surfacing them required only a UI change, with no backend work.