Search performance beside delivery work
Review organic results in the same place as project tasks and client context, making it easier to connect performance changes to the work a team shipped.
AppsGoogle Search Console
[v1.0]Overview
Connect Google Search Console to bring clicks, impressions, click-through rate, average position, and top search dimensions into Kato Project records.
How it works
A workspace owner or admin authorizes Kato with read-only Search Console access. Workspace members then link one verified Search Console property to each Project and view a cached 90-day performance dashboard without exposing Google credentials in the browser.
Configure
- 01In Kato, open Settings → Integrations → Google Search Console and click Connect.
- 02Sign in to the Google account that can access the properties your workspace manages.
- 03Open a Project, add the GSC tab, and explicitly choose the property to link.
- 04Use the date presets or Refresh control to review current search performance.
Last updated Aug 17, 2026
Why connect Google Search Console to Kato
The Google Search Console integration brings organic-search performance into Kato project records. Connect the Google account that can access the relevant property, link that property to a project, and give delivery teams a shared view of clicks, impressions, search terms, landing pages, devices, and countries.
Multiple useful dimensions
Move from headline clicks and impressions into queries, pages, devices, and countries without requiring every stakeholder to navigate the full Search Console interface.
Property-level authorization
Google remains the source of truth for verified properties and permissions. Kato can only present properties and data available to the connected Google account.
Ways teams use Google Search Console
Monthly SEO reporting
Open the client's project record, review the reporting period, and use the visible search trends when preparing a meeting summary or next-month task plan.
Landing-page investigation
Compare page-level performance and queries after a launch, then assign content or technical follow-ups with the affected project still in view.
Audience and device checks
Use country and device breakdowns to spot meaningful differences before proposing mobile improvements, localization work, or a deeper specialist analysis.
Google Search Console integration questions
Which Search Console properties can Kato use?
Kato can list properties the connected Google account is allowed to access. If a property is missing, confirm its verification and permissions in Google Search Console first.
Does Kato change Search Console data?
No. The integration reads reporting data for connected properties. Property verification, indexing controls, sitemaps, and other Search Console administration remain in Google.
Can different projects use different properties?
Yes. Link the appropriate Search Console property to each Kato project so the reporting view reflects the website associated with that client or initiative.
How Kato handles connected tools
Kato keeps the original service in charge of its specialist data and permissions. The integration brings the context needed for planning, review, and follow-up into the workspace where your team already manages client and project work. Authorize only the accounts and resources your workspace needs, review access when responsibilities change, and use the provider's own administration tools for detailed configuration.
Before installing any integration, confirm which Kato record should own the relationship and who will review its output. Revisit the connection whenever a client engagement, account owner, or provider permission changes, so the context remains accurate and access stays intentional.
