> ## Documentation Index
> Fetch the complete documentation index at: https://velurahq.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Google Search Console to VeluraHQ for page data

> Link Google Search Console to VeluraHQ to sync clicks, impressions, CTR, and position data into Pages and Actions — backed by live GSC signals.

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

<CardGroup cols={2}>
  <Card title="Per-URL Metrics" icon="file-lines">
    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.
  </Card>

  <Card title="Position Delta" icon="arrow-trend-down">
    Track week-over-week and period-over-period ranking changes for each URL so you can spot declines before they become traffic losses.
  </Card>

  <Card title="Query Data" icon="keyboard">
    See which search queries drive impressions and clicks to each page — useful for identifying intent gaps and refresh opportunities.
  </Card>

  <Card title="Real-Time Sync" icon="rotate">
    Data syncs automatically. The Pages module stays current without manual CSV exports or scheduled uploads.
  </Card>
</CardGroup>

## Connecting Search Console

<Steps>
  <Step title="Open the integration settings">
    Go to **Settings > Integrations > Google Search Console** in your workspace.
  </Step>

  <Step title="Start the OAuth flow">
    Click **Connect with Google**.
  </Step>

  <Step title="Authenticate">
    Sign in with the Google account that has access to your Search Console property.
  </Step>

  <Step title="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`).
  </Step>

  <Step title="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.
  </Step>

  <Step title="Connect">
    Click **Connect**. Data begins appearing in the Pages module within a few minutes.
  </Step>
</Steps>

## 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.

<Tip>
  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.
</Tip>

## 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.

<Note>
  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.
</Note>