Skip to content
covey

A page states in the head of its HTML which address it wants to be found under. An SEO agent can read that canonical there and confirm that https://example.com/blog/agents declares exactly that address. Whether Google followed the declaration is written nowhere on the page.

Google's choice is invisible from outside

Google can pick a different address as canonical than the one declared. The description of the Search Console plugin in the covey plugin pack calls this a fault that is invisible from outside and that quietly costs the address. An agent that reads title, canonical and hreflang therefore sees only the half the page says about itself.

The other half is Google's, and it is reachable through the Search Console URL Inspection API. Its answer carries two fields side by side: userCanonical for the declared address and googleCanonical for the one Google selected. Google's API description says googleCanonical is absent when the page was not indexed, and userCanonical is absent when no canonical was declared.

inspect_url puts both canonicals side by side

In covey the searchconsole plugin calls that API through the action inspect_url, one address per call. The agent sends {"inspection_url":"https://example.com/blog/agents"}. The plugin fills in the property from searchconsole_url unless the agent passes its own site_url. It asks for messages in de-DE unless the call names another language code.

Back come google_canonical and user_canonical, with the indexing verdict, the coverage state, the robots.txt state, the last crawl time, the known sitemaps and a link to the report in Search Console. For one address the agent now has what the page asks for and what Google did with it.

The plugin spells out the mismatch itself

Two fields side by side leave the finding to a comparison the agent would have to make. The comment in the plugin's source asks for the opposite: whoever reads the answer should not be able to miss it. So when both fields are filled and differ, the plugin adds a third field, canonical_abweichung (German for "canonical deviation"). It states the finding as a sentence: Google chose one address, the page declares another, and the address in the index is then a different one from the declared address.

The instructions the plugin puts into the agent's prompt tell it to read this field first.

In the example, if Google picks https://example.com/blog/ai-agents while the page points at https://example.com/blog/agents, that sentence is in the answer and the agent can carry it into its report. The comparison is on the text of both addresses after trimming surrounding whitespace, so a trailing slash on one side already counts as a mismatch.

The price is a quota of 2000 calls a day

The plugin's setup notes put inspect_url at 2000 calls per property per day. A daily run over a 50-page site uses 2.5% of that. An agent that inspects every address of the same site every 15 minutes would make 4800 calls a day. When the quota is gone, the plugin reports HTTP 429 and names the limit in the error text, and the prompt instructions tell the agent to use the action on addresses it has a question about.

Each action is reported under its own name, such as searchconsole:inspect_url. A guard rail can therefore forbid this one action, or put it behind an approval, while the other read actions keep working.

The finding needs both fields, and the only write action submits sitemaps

If either field is missing, there is no canonical_abweichung; for a page that is not indexed, the agent reads the verdict and the coverage state instead. The agent cannot change the canonical through this plugin. Its only write action, submit_sitemap, tells Google about a sitemap.

Access runs through a service account and the read scope

Setup is a service account whose JSON key sits in searchconsole_token and which is added as a user of the property in Search Console, plus the line - system: searchconsole scope: read in the agent's ACCESS.md. That read scope is enough for the canonical question. For https://example.com/blog/agents the agent then holds both addresses and the sentence naming their difference in one answer.

Back to all posts