Retrieve two labelled page reports
Ask for page rows for two explicit, equal-length periods. Maple Orbit’s property comparison gives the overall change; page-level changes require two row requests and analysis by your assistant.
Get page rows for each of the two complete 28-day periods we are comparing. Match URLs present in both returned lists and show click and impression changes. Keep URLs missing from either list separate; do not treat missing values as zero.
Check what is actually comparable
Use the same property and dimensions. Start with URLs returned in both periods. If a page falls out of a click-ranked list, that does not establish its current performance. Inspect the page in Search Console when the bounded result cannot answer the question.
Look beyond a rewrite
For a declining product collection, check the selection, stock and shopping experience as well as the text. For a guide, check whether the advice and linked products are still relevant. For a city delivery page, confirm its practical information is useful and accurate. None of those checks is performed by a performance API response.
Search changes can reflect demand, competitors, technical changes or a new mix of queries. Write these as possibilities to investigate. A comparison does not assign causation.
Choose the right next tool
A suspected indexing problem belongs in Search Console’s URL Inspection or Pages report. Maple Orbit currently retrieves performance data only. Do not remove a URL or add noindex solely because it had no returned clicks.
Related: missing rows and report differences.
Further reading
Official Google documentation. Product instructions distinguish the browser beta from the invited connector pilot. Educational guidance does not imply an automated feature.