Your Google Search Console data, beside the revenue it produced
- Trigger
- Search
- Lands in
- Dashboard, with a weekly Slack summary
- Setup
- 2 min
- Needs
- Nothing else
Search traffic is up 22% week over week
example.com, seven days to Monday
- Clicks
- 1,840 (up 22%)
- Average position
- 8.4, from 11.1
Most of the gain came from one guide finally reaching the first page of results.
Search, next to the revenue
Viably already captures the form someone filled in, the payment that followed and the conversations your team had with them. What it couldn’t see was the moment before all that, when they typed something into Google and picked your result.
Connecting Search Console fills that in. The query that started a customer relationship now sits in the same system as the revenue at the end of it. That lets you ask which search terms earn money instead of just visits, whether a page that lost traffic slipped in the rankings or people stopped searching for it, and how long a new post takes to start pulling its weight.
Impressions show how many people were looking for something you could have answered. That number moves before your traffic does.
Search sends people to a landing page, and Viably already knows which landing pages produce sign-ups. Put the two together and a search term stops being a vanity metric.
If clicks in Search Console and sessions in your analytics drift apart, something broke between the click and the page. Usually a redirect, a consent banner or a tag that stopped firing.
Two minutes, no code
Google lets you share a property with a colleague by email address. Viably has an address, so you share it the same way. There's nothing to install and no API credentials to manage. For what Viably does with the data once it's connected, see Google Search Console automation.
Viably shows you a Google service address in its Search Console settings. It is the same one for every property you add, so you only ever need to find it once.
In Search Console, open Settings, then Users and permissions, and add that address as a Restricted user. Restricted is deliberate, because reading performance data is all Viably ever does.
Come back and press Check access. Viably lists everything Google will now let it read, you choose what to track, and the sixteen months of history start loading straight away.
sc-domain:example.com and covers every subdomain and both protocols. Granting access there usually replaces four or five separate grants on URL prefixes, and it counts as one property on your plan.What your team sees
One page per workspace, covering every property you've connected. Anyone can read it, not just whoever owns SEO.
Clicks, impressions, click-through rate and average position, each shown against the previous period so you can see the direction as well as the level.
The search terms people used and the pages they landed on, filterable by country and device, so you can see which page slipped instead of just that the site did.
Loaded when you connect, so last year's seasonal peak is there to compare against on day one.
Search performance joins your weekly pulse, with a button that breaks the week down day by day.
Average position is weighted by impressions. A query seen thirty thousand times counts for more than one seen three times.
Viably divides total clicks by total impressions to get click-through rate. Spreadsheets often average each query's rate instead, which inflates it.
Alerts and the weekly crawl
Viably alerts you when traffic drops, when a page you’ve starred slips, or when the connection breaks. Once a week it also crawls your site for dead links. Alerts go to the channel that gets your weekly pulse, and the SEO monitoring page covers what each one does.
viably-seo-crawl/1, follows robots.txt and requests one page every 200ms. If bot protection blocks it, add a skip rule for that user agent. Cloudflare, Vercel and AWS WAF all support this. Until you do, Viably says so on the board and falls back to your repository if you’ve named one, or to your sitemap and Google’s index if you haven’t.Ask about it in Slack
Most people will never open an SEO dashboard, and they shouldn't have to. Once Search Console is connected, @Via can answer questions about it in whatever channel you're in.
“Is the site doing better than last month?” works fine. Nobody has to know what impressions means to get a useful reply.
Answers come from the data Viably has already collected for your properties, with the period stated.
Viably connects to Google Search Console and tracks clicks, impressions, click-through rate and average position for each property. It alerts your team in Slack when traffic really drops, ranks the queries that are missing clicks, crawls your site weekly for broken links, and shows the revenue that followed each query.
Yes. Search Console is still where you submit sitemaps and inspect URLs. Viably reads the performance data and shares it with the rest of your team in Slack.
Open the Search Console settings in Viably, copy the address it shows, and add it as a Restricted user on your property in Google. Then pick a Slack channel. Alerts and the weekly summary land there, repeats reply in the original thread, and anyone can ask @Via about search performance.
You need someone who owns the property in Search Console, since only an owner can add users. Everything after that takes a few clicks in Viably.
Sixteen months, which is all Google Search Console stores. Viably loads all of it when you connect, and you can compare this month with the same month last year on day one.
1 property on the free plan and 3 on Viably+. A domain property counts once and covers every subdomain and protocol under it. One grant on example.com usually brings in your blog, app and marketing site together.
No. Viably compares each Saturday with the four Saturdays before it, and does the same for every other day.
Google keeps revising recent days for about 48 hours. Viably re-reads the last week on every sync and marks days that are still settling. Charts dim them and alerts skip them entirely.
Viably already records the page each new contact landed on and what they've paid since. Search Console shows which queries sent people to that page. Viably puts the query and the revenue side by side and leaves the conclusion to you.
If the fix is a link in your code, Viably can draft it as a pull request on the repository you name. You confirm twice before anything is written, and drafts only happen when you ask. Drafted fixes need Viably+ and the GitHub power.
Bot protection is almost always the reason. The crawler identifies itself as viably-seo-crawl/1, follows robots.txt and requests one page every 200ms. Add a skip rule for that user agent in Cloudflare, Vercel or your WAF and it's fixed. Until then Viably works from what it can reach: the repository you named for the property, or failing that your sitemap checked against Google's index. It always says which one it used.
Viably only reads. Restricted is the lowest access level Google offers that still returns performance data, and it can't change settings, submit sitemaps or add users. You can remove it in Search Console any time, and Viably will notice on the next sync and tell you.
Add Viably’s address to your property in Google Search Console and sixteen months of history load on their own. One property is included on the free plan.
Add Viably to Slack