For end users

gsc

Pull organic search performance from Google Search Console into the keywords table and the gsc_daily time-series.

Type: inbound. The runner calls fetch.ts directly; the model is not invoked at fetch time.

What it fetches

Two grains:

• Aggregated last-28-days per query — impressions, clicks, average position, CTR. Updates the keywords table fields gsc_impressions, gsc_clicks, gsc_position so skills like weekly-analysis can read them inline.
• Daily time-series per query — written to gsc_daily for trend analysis (rising / falling, before / after).

What you need

• A Search Console property (URL-prefix or Domain) the workspace tracks.
• A Google service account with read access to that property. Domain properties (DNS-verified) bypass the per-property user-add and are the recommended setup. URL-prefix properties require manual user-add in the Search Console UI; see the propagation FAQ if Search Console refuses the service account email.
• The Search Console API enabled in your Google Cloud project.

The Google service account section of Set up your accounts covers all three.

Configuration

Per-workspace setting GSC_SITE_URL_PER_WORKSPACE. The CMS Apps surface (/apps/gsc) collects the site URL or sc-domain: prefix, runs a Test connection, and saves the value into integrations.

Interpretation

After fetch, apps/gsc/insights/SKILL.md turns the raw rows into Insights consumed by weekly-analysis and plan-sitemap.

Where it lives

pectusai/apps/gsc/APP.md