Skip to main content
Connecting Google Search Console to VeluraHQ brings organic search performance data — clicks, impressions, click-through rate, and position — into your workspace at the URL level. This powers the Pages module, feeds the Actions opportunity engine, and makes search performance available as a signal inside workflow research steps.

​
What you get

Per-URL Metrics

Clicks, impressions, CTR, and average position for every indexed page in your property — visible directly in the Pages module alongside GA4 and AI citation data.

Position Delta

Track week-over-week and period-over-period ranking changes for each URL so you can spot declines before they become traffic losses.

Query Data

See which search queries drive impressions and clicks to each page — useful for identifying intent gaps and refresh opportunities.

Real-Time Sync

Data syncs automatically. The Pages module stays current without manual CSV exports or scheduled uploads.

​
Connecting Search Console

1

Open the integration settings

Go to Settings > Integrations > Google Search Console in your workspace.
2

Start the OAuth flow

Click Connect with Google.
3

Authenticate

Sign in with the Google account that has access to your Search Console property.
4

Select your property

Choose the Search Console property you want to connect — either a URL-prefix property (e.g., https://example.com/) or a Domain property (e.g., example.com).
5

Set the data range

VeluraHQ imports up to 16 months of historical data on first sync. You can adjust the starting date if you prefer a shorter window.
6

Connect

Click Connect. Data begins appearing in the Pages module within a few minutes.

​
Supported property types

VeluraHQ supports both URL-prefix properties (https://example.com/) and Domain properties (example.com). Domain properties cover all subdomains and protocols — HTTP, HTTPS, and all subdomains under the root — and are recommended for most teams because they give the most complete picture of your organic search footprint.
If you manage multiple sites, you can connect multiple GSC properties in separate workspaces (Enterprise plan) or by using distinct workspace configurations. Each workspace maintains its own property connection independently.

​
How GSC data powers VeluraHQ

Once connected, Search Console data flows into three areas of your workspace:
  • Pages module — GSC data joins with GA4 and AI citations to give a 360° view per URL. You can see clicks, impressions, position, sessions, engagement, and citation count on a single page card.
  • Actions — Position drops and CTR decay trigger automatic Actions with recommended fixes. The Actions engine uses GSC signals to prioritize which pages need attention most urgently.
  • Workflow research steps — Workflows can pull live GSC data for a URL as an input to refresh or audit analysis — no manual lookup required.
VeluraHQ only requests read access to your Search Console data. It does not modify your GSC property settings, search appearance configuration, or any other Search Console data.