Connect your data

A project can begin with only a domain. Connecting first-party data makes prioritization and measurement reliable; connecting a CMS gives the engine a safe way to apply supported changes.

Recommended setup

1. Choose Add project on the Projects page and enter the domain. The name defaults to the hostname.
2. Open Settings → Integrations and Connect Google. One Google sign-in grants read-only access to Search Console and, if you approve it on the consent screen, Google Analytics.
3. When a Search Console property matches the project domain it is attached automatically and the first sync starts; the last four weeks land first and the remaining history backfills over the following hours. A matching GA4 property is attached the same way.
4. Optionally connect Wix so the engine can read and update published pages, and Cloudflare to see which AI crawlers fetch your pages.
5. In Project Settings, describe the business, audience, conversion goals, brand constraints, and competitors, and confirm the included and excluded paths.
6. Choose the autonomy mode. Copilot is the default.

SERPclimber manages the providers used for crawling, backlinks, keyword data, AI answers, and language models. There are no keys to paste for them; paid evidence is governed by the project's monthly budget in Settings.

The first audit

The first audit starts on its own after the project is created and repeats weekly. It crawls the site, checks crawl and index access, on-page signals, internal linking, structured data, AI crawler access, and citation gaps, and files its findings under Audit. The most useful findings are promoted into Tasks; the rest stay in Audit until they become relevant.

Search Console evidence appears on Performance → SEO as soon as the first sync lands, and the first AI answer scan starts automatically once queries are available.

No connection grants unlimited authority. Project scope, autonomy rules, action risk, spend limits, and required approvals still apply to every operation.