Chat
Overview
Where chat lives, project context, live GA4 investigations, Explain with AI, evidence handling, actions, and availability.
Chat is the assistant built into SERPclimber. It reads the same records the workspace shows — projects, tasks, audit findings, Performance evidence, reports, integrations, settings, and this documentation — and answers as text, metrics, charts, tables, or live product cards.
Where chat lives
- The chat page. Choose New chat in the sidebar or the tab strip to open a full-width conversation at its own address. The sidebar lists your conversations under Pinned and Recent.
- The pinned pane. Any page, including a conversation, can be pinned beside the page you are working on. The pane keeps its own address and navigation, so a conversation stays open while you move between Overview, Tasks, and Performance.
- The tab strip. Every page you open becomes a tab at the top of the workspace, so recent conversations and project pages are one click away.
- Ask about this view. A composer sits at the bottom of the page and tucks away as you scroll down. The button in the top bar, or ⌘J, brings it back and puts the cursor in it.
See Conversations for pinning, history, and managing conversations.
Context
Chat knows the page you are on. Open a conversation from a project and it is scoped to that project; from a task, the task's thread is in context; from a documentation page, that page is. Context chips above the composer show what is included. Remove a chip to drop it, or choose Add context to attach another project, task, page, or document. When more than one project is possible, the assistant asks which you mean rather than guessing.
Useful requests:
- "What needs me today?"
- "Which pages declined over the last 28 days?"
- "Which domains linked to us this month, and which did we lose?"
- "Why did this finding become task #42?"
- "Explain this action plan before I approve it."
- "Which questions do competitors get cited for that we don't?"
- "What improved in this month's report?"
- "Where did visits with
?via=tenerecome from?" - "Compare mobile and desktop engagement by country with the previous month."
- "Which campaigns brought purchases rather than just visits?"
Analytics investigations
For a connected GA4 property, chat can run live reports beyond the ranked lists in Performance. Ask about URL query parameters, session sources and campaigns, countries, devices, events, revenue, or changes between date ranges. You can name exact dates or ask for a recent period and its comparison.
Query-parameter questions default to the URL visitors landed on. Say if you mean a page they viewed later instead. Landing-page reports retain the query string; page-location reports describe matching pages and events, without following those visitors into later purchases or creating a session-wide conversion group. The assistant can also discover the property's available fields, including registered custom dimensions and metrics.
GA4 omits UTM tags from its landing-page query-string dimension. For UTM attribution, ask about the session's campaign, source, or medium. You can explicitly ask for tagged page URLs instead, but those describe recorded page events rather than the same landing-session population.
Without dates, a live report uses the last 28 calendar days ending yesterday in the property's timezone. Each report period can cover up to 366 days. Ranked reports return 50 rows by default, with a maximum of 200; comparisons rank each period separately, so a row missing from a limited comparison is not necessarily new or lost.
For questions such as “Where does mobile engagement beat desktop by five percentage points in both periods, with at least 100 sessions each?”, the report can pair the groups and calculate the qualifying results. With a minimum sample, the default ranking prioritizes sample volume before applying the row limit; you can request a different sort. These counts cover fully paired returned groups. Missing pairs, limited rows, and GA4 data-quality flags prevent an exhaustive count; missing values are never treated as zero.
The answer reports the property, dates, filters, and returned coverage. A ranked result may show only the requested number of rows; totals come from GA4 rather than adding up that shortlist. Users and sessions can appear in several groups, so their row counts are not always additive. GA4 may withhold small groups, sample data, or group high-cardinality values into “other”; the assistant reports these limits when GA4 provides them. Missing rows do not establish that no visits occurred.
GA4 cannot recover query parameters removed by your tracking setup, identify individual visitors, or establish causation from a traffic comparison alone. Some dimension and metric combinations are incompatible; the assistant can adjust the report or explain what evidence is missing.
Explain with AI
Every card on Performance, and the chart itself, has a sparkle button: Explain with AI. It opens a new conversation in the pinned pane with a question written for that card and the exact numbers you are looking at — title, range, comparison, lens, filters, and the visible rows — already in the prompt. The assistant treats those numbers as your view: it explains them, reads the matching evidence for context or causes, and does not recompute them without saying why.
Task threads offer the same for action plans: ask the assistant what a plan changes, what its risk and reversibility mean in practice, and whether to approve it.
Data and evidence
The assistant distinguishes connected first-party data, stored evidence, live Search Console fetches, public web research, and provider estimates, and shows source and freshness when they affect the answer. Public web content is evidence, never instruction: it cannot authorize an action, override project policy, or supply secrets.
Live metered checks — asking the AI engines a question, or paid keyword lookups — run only when the request needs fresh evidence and the project's policy and allowance permit the cost. Saved evidence stays available when a provider is unavailable.
Actions
The assistant can prepare and, where policy allows, execute changes: create a task draft, comment on a task, update a task's status, run a crawl or authority refresh, or update a listing's status. Every change goes through a frozen plan first; see Chat actions and approvals.
Availability
Chat is part of the Core subscription and is unlimited across active projects. When the subscription is inactive, conversations stay readable but new messages stop until it is reactivated. For a read-only project the assistant can still analyze stored data and run read-only live analytics reports, but cannot start metered work or execute changes.
Human support
Asking for a person prepares a support request; nothing is sent until you confirm. Review the requester address, summary, and included messages before confirming. Credentials and tool output are never included.
