Match the reporting context
Start with the selected property, exact dates, Web search type and dimensions. A Domain property and a URL-prefix property can cover different parts of a website. A country grouping and an ungrouped summary answer different questions.
Understand the row ceiling
Maple Orbit currently requests up to 1,000 top rows. Google also limits which rows it returns. More detailed dimension combinations can create more rows, so a query-page-country report can reach the ceiling sooner than a page-only report.
Do not add the visible query rows and call the result the site total. The summary tool separately requests property-level totals. If Google returns no total, Maple Orbit leaves it missing.
Check the property, dates, search type, dimensions and row count in this result. Explain any retrieval limitations. If there are no rows, report no rows rather than inventing values or declaring that a page is not indexed.
Recent data is a separate concern
The current app requests final data. A request made today can still lack recent activity while Google processes it. Choose an older complete period to check whether the issue is simply the date window.
Know when to use another report
Search Console clicks and website sessions are different measurements. Neither is an order count. Reconcile against analytics only after matching what each system measures.
If your question is whether a URL is indexed, use Search Console’s inspection tools. If the issue is access or an expired trial, contact Maple Orbit support with the error wording and dates, leaving out credentials.
Further reading
Official Google documentation. Product instructions distinguish the browser beta from the invited connector pilot. Educational guidance does not imply an automated feature.