Skip to main content
Google Search Console (GSC) is the data source behind WISEPIM’s organic-search features. Connect it once and your real impressions, clicks, CTR, and rankings flow into the SEO & Search report, Product Performance, Search Intent enrichment, keyword opportunities, and the AI’s search-performance context. The connection is read-only and uses your Google sign-in, no API keys. WISEPIM SEO performance with Search Console clicks, impressions and keyword growth WISEPIM SEO performance with Search Console clicks, impressions and keyword growth

​
Before you start

  • A Google account with access to at least one verified property in Google Search Console. Both URL-prefix properties (https://example.com/) and domain properties (sc-domain:example.com) work. You need a verified property before you connect; WISEPIM cannot verify a site for you.
  • Each WISEPIM project connects to one property. Working with several storefronts? Connect each one in its own project.
WISEPIM requests read-only Search Console access. It can never submit or delete sitemaps, request indexing, or change anything in your Search Console account.

​
Connect Google Search Console

1

Open Integrations

Go to Channels → Integrations in the top navigation, filter by the Analytics category, and find the Google Search Console card.
2

Click Connect

The connection dialog explains what you’ll get: search query performance, impressions, clicks, CTR, position metrics, and page-level performance. Click Connect with Google.
3

Sign in with Google

Your browser goes to Google’s own consent screen. Pick the Google account that has Search Console access and grant the read-only permission. You’re brought straight back to WISEPIM.
4

Select a property

WISEPIM lists the verified properties your account can see, each with its permission level. Pick the property this project should monitor and click Select site. WISEPIM verifies your access with Google before accepting the selection.
5

Let the initial import run

Selecting a property queues the initial import automatically, and the dialog follows its progress. The SEO report shows Importing initial Search Console data until the backfill lands, then fills with your history.
The connection is only treated as ready when all three are true: the account is connected, a property is selected, and the connection test passed. If a page still shows a connect prompt after setup, open the card and click Test.

​
What WISEPIM imports

Query-level totals will not add up to the daily totals: Google anonymizes low-volume queries and omits them from query-dimensioned data. WISEPIM pulls both datasets on purpose so the headline numbers stay right. Search-appearance types overlap too, so never sum them into one total.
A few honest boundaries of the data:
  • Sitemap counts are observations, not proof. A URL being submitted in a sitemap does not mean Google indexed it.
  • URL inspection reads Google’s stored index record. It is not a live test and never requests indexing. Inspections are quota-bounded per day, so large catalogs are covered over multiple days, prioritizing never-inspected and product URLs first.
  • Detailed query and page rows are top rows. On very large sites a single day can exceed Google’s row limits; those slices are marked as truncated in the coverage panel rather than passed off as complete.

​
Data coverage panel

The SEO report includes a Search Console data coverage panel that shows the freshness and completeness of each stored dataset: search performance, search appearances, sitemaps, and URL inspection. Each card carries a status chip: Ready, Partial, Error, or Unavailable. Treat it as the report’s honesty layer. If the latest refresh was incomplete or failed, the panel says so while the report keeps showing the last successfully stored data. A failed refresh never blanks data that already synced.

​
How products are matched

WISEPIM ties Search Console data to individual products by matching product URLs against your sitemaps. Every product falls into one of four mapping states, shown in the Product Performance drawer and the product editor’s Search performance card: Matched products get their own clicks, impressions, CTR, average position, top queries, search appearances, and indexed-version evidence, per product.

​
Sync schedule and history

  • Search data trails by about 3 days. Google Search Console itself delays its data, and WISEPIM ends its data at three days ago to match. The last few days looking empty is normal, not a sync problem.
  • Background syncs run daily. They refresh roughly the trailing week and backfill history in batches: about 6 months of search performance, and even longer for the detailed capability datasets.
  • Manual syncs are rate-limited to once every 5 minutes, and only one sync runs at a time.
The SEO report shows when data was last synced and flags it Stale after 24 hours; opening the report when data is stale starts a refresh automatically. The integration card keeps a sync history with the status, duration, date range, and row count of recent runs, using the statuses running, success, partial, and error.

​
Manage the connection

Reopen the Google Search Console card at any time to see the connection status. From there you can:
  • Change the selected property. Data is always scoped to the current property: WISEPIM immediately hides the old property’s data and queues a full backfill for the new one, so numbers from two properties are never mixed.
  • Test the connection.
  • Sync now: fetches only recent data and fills in anything that was missed.
  • Force re-sync: refreshes the full 6-month window while retaining the previous snapshot for recovery.
  • Switch account or Disconnect the integration.

​
What it powers

Sitemap Coverage, Sitemap Gaps, Link Audit, and Link Equity run off your catalog and sitemaps, so they keep working even before Search Console is connected. Only the performance-based views need the connection.

​
Troubleshooting

The Google account you picked has no verified Search Console properties. Verify your site in Search Console first, or click Switch account in the dialog and sign in with the account that owns the property.
Any performance page under Analytics → SEO shows a Go to Integrations button when the connection is missing; it takes you to the flow above. If you did connect, the connection may need attention: open the card and use Test. A selected property with a failed test blocks the report just like a missing connection.
Your property stays selected; you never need to reconnect for a sync problem. Review the sync error shown on the SEO report, then use Sync now to retry safely.
A successful sync with zero clicks and impressions in the selected date range shows a No search activity state rather than fake zero-charts. Try a wider date range if you expected activity, and check you selected the property that actually serves your storefront.
Expected. GSC data trails by about 3 days (see above). If older data is missing too, run Sync now.
The product’s URL is missing from your sitemaps, so search metrics cannot be attributed to it. Open Sitemap gaps to see every affected product and fix your sitemap; attribution picks the products up on the next sync.

SEO & Search report

The command center this connection powers.

Product Performance

See product-attributed search metrics next to sales and quality.

Search Intent

Rewrite descriptions using your real queries.

Google Analytics 4

Add on-site traffic, funnel, and item-level conversion data.