Skip to main content
Search Console is available to every workspace under Connections -> Integrations -> Analytics & Search. It asks Google for one read-only permission, webmasters.readonly. Connecting it changes what the SEO agent can say. Without it, an audit can tell you a page’s title is too long. With it, the audit can tell you that page has 4,000 impressions at 0.9% click-through and rank the fix by the traffic actually at stake.

​
What daoco can read

  • Search performance. Clicks, impressions, click-through rate, and average position, broken down by search query, page, country, device, or date.
  • Accessible properties. The Search Console properties the connected Google account can read, whether it verified them or was granted access by an owner.
  • Sitemap status. What you submitted, when Google last downloaded it, and any errors or warnings.
  • Index coverage for a URL. Whether Google has indexed a page, why not if it hasn’t, and whether Google chose a different canonical than the page declares.
The connection is read-only. daoco cannot submit or remove sitemaps, request indexing, change property settings, or add and remove users.

​
Before you start

The Google account you connect must have access to the Search Console properties you want to read. A verified owner can grant that access, or you can verify ownership through Google directly. Daoco’s read-only connection cannot add or verify a property. If you connect an account with no accessible properties, the connection succeeds and returns an empty property list. Add or verify the website in Search Console, or ask its owner to grant access to the same Google account, then ask Daoco to list sites again.

​
Connect Search Console

1

Open Search Console

Open Connections -> Integrations, choose Add integration, and pick Google Search Console under Analytics & Search.
2

Choose Connect

Choose Connect. A Google authorization window opens.
3

Approve read-only access

Sign in with a Google account that has access to the properties you want, and approve read-only Search Console access.
4

Verify from chat

Ask the agent which Search Console properties it can see. It should list them by their exact property name.

​
Domain properties and URL-prefix properties

Search Console keys a property one of two ways, and they are different resources:
  • Domain property (sc-domain:example.com) covers every subdomain and both http and https.
  • URL-prefix property (https://example.com/) covers only that exact prefix.
The agent uses whichever name Search Console returned. If a report looks like it is missing traffic, check which of the two you verified. A URL-prefix property will not show data for a subdomain.

​
Data is about three days behind

Search Console settles its data on a delay, so the last few days of any range are incomplete. daoco ends its default reporting windows where the data actually ends and says so in the report, specifically so a partial final day is not read as a traffic collapse. If you ask for a range ending today, expect the last entries to be low. A newly added property can show “Processing data” in Search Console while its API returns no performance rows. That is not proof of zero traffic. Wait for Google to populate the report before drawing conclusions; property discovery, sitemap status, and URL inspection can still work in the meantime.

​
What you can ask for

  • “Which queries am I close to ranking for?”
  • “Find pages Google isn’t indexing and tell me why.”
  • “Run an SEO analysis on my site”. The audit uses search performance to rank its recommendations once this is connected.
  • “How did organic search do last month compared to the month before?”

​
Disconnecting

Disconnecting removes the agent’s access immediately: the Search Console tools stop being offered in chat, and recurring tasks that read them, such as the weekly SEO review, stop pulling search data. Audits you already ran keep their history; they just stop refreshing.