Search Console

Connect Google Search Console so the agent can read your organic-search performance — clicks, impressions, average position, and top queries — to power SEO ranking stats and the SEO audit loop. The connection is read-only (webmasters.readonly) and you choose which verified property to track.

Prerequisites

• A Google account with access to a verified property in Search Console.
• The server must have Search Console enabled. If the card shows "Search Console isn't enabled on the server", the operator needs to set GSC_ENCRYPTION_KEY plus GOOGLE_CLIENT_ID/GOOGLE_CLIENT_SECRET and register the OAuth redirect URI — this is a one-time server config, not something you do per product.

Connect Search Console

1. Open Integrations and find the Organic search (Google Search Console) card.
2. Click Connect Google Search Console. You're sent through Google's OAuth consent for the read-only webmasters.readonly scope.
3. Approve. Google redirects you back, and 1mn loads the list of properties your account can see.
4. Pick the property to track — choose the verified site (e.g. https://yourdomain.com/ or a sc-domain: property). The card then shows Connected ✓.

You can re-open the picker any time to switch which property the SEO loop reads.

Example: what you get

Once a property is selected, the SEO loop and dashboard read query-level performance such as:

Query                 Clicks  Impr.   CTR   Pos.
ai media buying agent     210  4,800  4.4%   6.1
autonomous ad agent       150  3,100  4.8%   7.3

The SEO audit pairs this with Core Web Vitals and crawlability to produce a prioritized, recommend-only action plan — nothing on your site changes.

Notes & limits

• Read-only. The webmasters.readonly scope means 1mn can read Search Console data but cannot submit sitemaps, change settings, or otherwise modify your property.
• Data lags ~2–3 days. Search Console itself reports with a delay, so the freshest day or two won't appear yet.
• One property per product. The selected property is what every SEO read uses; switch it from the card.
• Disconnect to stop the agent reading organic-search data and remove the stored tokens.