Skip to main content
Search Console tells Weelkit how Google Search shows your site. Once it’s connected, Performance and Analytics show clicks, impressions, click-through rate, positions, queries, sitemaps and each article’s index status. The same data suggests prompts to monitor in AEO & GEO, and it tells Weelkit which site is yours when it checks your site’s speed, AI access and, with an Ahrefs or Semrush account, backlinks. Weelkit only reads from Search Console. It never submits or changes anything there.

Before you start

  • Who can connect it: an Admin or a Managing Editor. A custom role can connect it when it includes the permission to create, configure and remove organization integration connections. See Roles and permissions.
  • Who sees the data: every role that can see Metrics: Editors, Managing Editors and Admins.
  • What you need: a site that is verified in Search Console, either as a domain property or as a URL-prefix property, and a Google account that can open it. Sites you haven’t verified aren’t offered. An organization has one Search Console connection.

Connect

1

Start the connection

Open Organization settings → Integrations (Managing Editors open Integration). In the Analytics section, find Google Search Console and choose Connect.
2

Approve access in Google

Weelkit sends you to Google. Sign in with the Google account that can open your site in Search Console, and approve the read-only access Google lists. Approve everything it asks for. Start again from Weelkit if you wait more than 10 minutes.
3

Choose the site

Back in Weelkit, a message says Integration connected successfully. On the Google Search Console card, choose Configure Search Console (or open the card’s ⋯ menu and choose Configure). Under Search Console site, choose your site.
4

Import your first data

In the same window, choose Sync to save the site and import the last 30 days now, or Save Configuration to save it and wait for the next import. The card then shows Source with your site, and Latest sync with the rows it imported.
Until you choose a site, nothing is imported, and the metrics pages ask you to select one in Settings → Integrations.

What Weelkit reads

  • The verified sites you can open, so you can choose one.
  • For the site you choose: clicks, impressions, click-through rate and average position by date, search query, page, country, device and search appearance.
  • The sitemaps Google knows for the site, and their status.
  • The index status Google reports for your published articles. Weelkit asks about each article daily for two weeks after it goes live, then weekly.
Sync imports the last 30 days. After that Weelkit keeps importing in the background, reading the most recent days again each time, and fills in older history, newest first, up to 16 months. Days still missing from that history stay unavailable. Google reports Search Console data with a delay, so the newest days can be missing for a few days.

Where you see it

Limits and what you control

  • One site at a time. The metrics pages use the site you selected last. To change it, open Configure on the card and choose another.
  • Google’s own limits apply. Search Console keeps about 16 months of data, and some of its reports keep only their largest rows. Weelkit says so and shows — instead of guessing. See How metrics work.
  • Access is read-only. Weelkit asks Google only to read your Search Console data.

Disconnect

On the card, open the ⋯ menu, choose Disconnect, then choose Disconnect to confirm. Keep connection cancels.
  • Weelkit stops importing and deletes the access tokens it stored.
  • Figures already imported stay in your workspace, so your history isn’t lost. The metrics pages keep showing them and say they are no longer updating.
  • Connecting the same site again fills in the days you missed.
  • To remove the imported figures, delete the organization, or email privacy@weelkit.com. See the Privacy policy.
  • Disconnecting doesn’t remove Weelkit from your Google account. To do that, open your Google Account permissions and remove Weelkit.

Troubleshooting