SearchDock in the Lab

What a SearchDock report can and cannot tell you

A SearchDock report combines finalized search performance, returned sitemap status and optional indexed-URL inspections. It is an evidence bundle for a defined question, not a complete site audit or an indexing action.

By Xplormity Collective. Source reviewed November 14, 2026. We maintain SearchDock. This guide uses source inspection and a synthetic request, not a live customer report or an independent security audit.

Start with a question and an explicit date range

For example: what finalized search data was returned for one property in September, and what does Google report about the indexed version of one guide? This keeps a performance question separate from a live-page check.

The following JSON is input for searchdock_report in an already-connected MCP client. The reserved example domain is illustrative. No command was executed and no access to that property is implied.

{
  "site": "sc-domain:example.com",
  "start": "2026-09-01",
  "end": "2026-09-30",
  "limit": 1000,
  "urls": [
    "https://example.com/guide"
  ]
}

The Google adapter requests three analytics views: totals, queries and pages. It also reads sitemaps, then inspects each supplied URL. Omitting urls skips inspections. The MCP schema accepts at most 20 explicit URLs per report.

Dates are inclusive and use Pacific Time. Without explicit dates, the adapter defaults to a 28-day window ending three days before today in Pacific Time. It requests dataState: final; it does not expose hourly fresh-data reporting. Include both start and end when comparing fixed periods.

The row limit defaults to 1,000 for an analytics view, with pagination and a supported maximum of 100,000. A higher limit is not the same as complete coverage. Google's omissions and top-row behavior still apply.

Read each result at its actual scope

Keep an observation, its limitation and the next check together. That makes a report more useful than an unexplained score.

What the reviewed adapter establishes
ResultWhat it establishesWhat it does not establishNext check
Query or page rowsReturned top rows for the requested dates, search type and dimensions.An exhaustive keyword inventory, or zero demand for a missing query.Keep the report range and dimensions with the result. Separate missing data from measured zero.
limitReached: trueThe adapter stopped at the requested row limit without establishing a short final page.That a larger limit will recover anonymized or otherwise omitted data.Increase the limit only when the task needs it and the added data is appropriate to share.
Sitemap issuesErrors, warnings and pending status in the returned sitemap records.A complete inventory of every excluded page, or proof that every submitted URL was indexed.Inspect a specific URL. Use Search Console's Page indexing report for broader exclusion investigation.
URL inspectionGoogle's indexed-version result for the explicit URL.A live fetch test, a request to index, or a promise of future indexing.Check current HTTP response and canonical separately. A live page and a stored index result answer different questions.
Empty issues arrayNo issue was added from returned sitemaps and the URLs explicitly inspected.An all-clear for the entire site. A report without URLs performs no URL inspections.Record which URLs were checked and which were not. Do not label unexamined pages healthy.

A summary can be null when no total row is returned. Do not turn that absence into a measured zero. The report also warns that average position cannot be interpreted when impressions are zero. Search Console omits some anonymized queries, so summing visible query rows need not reproduce a chart total.

The optional brand input is an exact, case-insensitive query filter in this revision. It is not an automatic classifier of all brand-related searches. A filter for a brand name will not automatically include misspellings, product names or longer queries containing that name.

A saved property is a default, not an allowlist

The selection implementation chooses an explicitly supplied site before the stored default. Saving one property therefore does not confine every future tool call to that property. Google authorization still applies, but a separate per-agent property restriction would need enforcement in a reviewed wrapper or host configuration.

In the reviewed release, OAuth requests the Search Console read-only scope. The five MCP tools list sites, read analytics, read sitemaps, inspect indexed URLs and assemble reports. There is no live URL test or request-indexing tool. Read-only tool annotations communicate intent; they do not restrict the host's shell, file editor or publishing tools.

A proposed host policy for the example above is: permit only the chosen profile, exact property and supplied inspection URL; return a summary; do not publish, edit files or invoke unrelated tools. This is a policy to implement and verify, not a built-in guarantee of SearchDock. Test explicit argument overrides when reviewing enforcement.

Local credentials are JSON protected with filesystem permissions, not an encrypted credential vault. Returned queries and page paths can also be sensitive. Review the receiving agent client's storage and model settings before sharing results. Local logout deletes the selected profile file; provider-side revocation is separate.

Make the handoff reproducible without publishing private data

Download the reusable report handoff worksheet (plain text). It includes a synthetic MCP request, exact property and date scope, observation and unknown fields, next checks and a redaction checklist. Fill it in privately; no report has been run for the example.

  1. Record the tool version, date range, search type, dimensions and whether a brand filter was used.
  2. List the explicit URLs inspected. State that other URLs were not checked.
  3. Separate returned observations from hypotheses: a missing row is an unknown, not proof that a topic has no audience.
  4. Assign a next check to each open question. Use a live HTTP/canonical check for today's page and indexed inspection for Google's stored result.
  5. Remove credentials, private query text and property identifiers before sharing outside the intended audience. Use synthetic examples for public explanations.

For a no-data example handoff: “The request covers September and one supplied URL. No authenticated request was run for this example. Sitemap and index status remain unknown.” A clear unknown is more actionable than a fabricated pass.

Install and configure SearchDock in the Lab, then review the release you actually use. This page covers source revision 28b39813308ae834e606c9290a1e68b35e788ceb; later versions may differ. It makes no promise of rankings, traffic, full indexing coverage or security certification.