ViablyViably
SEO monitoring

Bring Google Search Console data into your marketing stack.

Viably reads your Google Search Console data every morning and creates actionable tasks. You hear about a traffic drop in Slack, see which pages are leaking clicks, and propose PR fixes for any broken links. Viably tracks each search query all the way to sign-ups and payments.

Start freeRead the setup guide

Free plan forever with no credit card, and unlimited seats on every plan.

1 property on the Free plan and 3 on Viably+.

A search for “waterproof trail running shoes” followed from Google to revenue: 21.5K people saw the result, 268 clicked, 41 became contacts and 23 have paid $3,496 since. Then every query, ranked by the clicks it is missing.

A
athlead.com › shop › trail-runningWaterproof trail running shoes, free returns for 60 days
#6.4
Paid since the search
waterproof trail running shoes…
stripe payment failed alert…
slack uptime monitor…
From 3 searches$0
SeenAverage position 6.4
0
Clicked1.25% click-through
0
ContactsLanded on that page
0
Paid since23 paying customers
$0

Revenue counts what people who landed from a search have paid since, matched on the page they arrived at. Viably follows every query this way and leaves the conclusion to you.

16 months
Of history on your first day
2 min
To connect a property
0
Lines of code to install
Alerts

Alerts that know what a normal weekend looks like.

When traffic really falls, Viably posts one message in Slack. Later alerts about the same property reply in its thread.

Daily clicks · athlead.comThe last five weeks, Monday first
0
Alerts sent
Week 1Week 2Week 3Week 4This week
Same weekday, four weeks beforeStill settling, skipped by alerts

A fixed threshold fires every weekend, when search traffic always dips. Viably compares each day with the same weekday over the past four weeks, skips the two days Google is still counting, and alerts you on the Tuesday that actually dropped.

  • Traffic really moved

    Viably compares each day with the same weekday over the past four weeks and alerts you when it falls well below the usual.

  • A page you watch slipped

    Star a page or a query and you'll hear about it the day it drops off the first page of results, even when total traffic looks fine.

  • The connection broke

    If someone removes Viably's access or a property stops returning data, Viably posts a single message to your channel.

Setup and weekly crawl

Connected in two minutes. Then it finds what Search Console can’t see.

Share your Search Console property with Viably's email address, the same way you'd add a colleague. That's the whole setup.

Search Console settings
Viably’s Google address
viably-search@…iam.gserviceaccount.comCopy
Use this same address for every property you add.
Users and permissions · athlead.com
Email address
Permission
FullRestricted
Added as a Restricted user
Add
Properties Viably can readCheck access
Your properties show up here once Google lets Viably in
sc-domain:athlead.comDomain property
https://shop.athlead.com/
Loading history16 months of Search Console data

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.

  • Dead links and redirect chains

    Viably follows every internal link and lists dead links, redirect chains and redirects that end in a 404. Search Console reports none of them.

  • Your sitemap against your site

    Viably flags sitemap URLs that 404, redirect, carry a noindex tag or are blocked by robots.txt, since each one sends Google a mixed signal.

  • Google's answer next to ours

    Each finding is checked against Google's own index. The card says whether Google agrees and lists the pages it saw linking there.

  • A pull request when you ask

    When the fix is a URL in your code, Viably drafts a pull request on the repository you name in two clicks. Merged fixes show up in the weekly pulse.

Ask about search from any Slack channel.

Anyone on your team can ask @Via how the site is doing in plain words. The answer comes from your own synced numbers, with the period stated.

  • The weekly pulse

    Search joins Monday's summary in the channel that already gets it, with a button that breaks the week down by day.

  • The Team Inbox

    Every finding becomes a card somebody can own. File it as an issue, make it a task, or snooze it until the clicks behind it grow.

#growth · Slack
Numbers you can trust

The math a spreadsheet usually gets wrong.

Every chart, alert and summary in Viably follows these four rules for reading search data.

  • Position, weighted by impressions

    Average position is weighted by impressions. A query seen thirty thousand times counts for more than one seen three times.

  • Click-through from the totals

    Viably divides total clicks by total impressions to get click-through rate. Spreadsheets often average each query's rate instead, which inflates it.

  • Recent days held back

    Google revises the last two days of the data Viably syncs while it finishes counting. Charts dim those days and alerts skip them.

  • A blocked crawl says so

    If bot protection blocks our crawler, the board says so and names the fallback. When the whole site is down, uptime monitoring posts it in Slack.

1 property free. 3 on Viably+.

Reporting, alerts, the weekly crawl and @Via come with every plan. Viably+ tracks 3 properties and drafts pull requests for the fixes it finds. Every plan includes unlimited seats for your whole team.

1
Property on the Free plan
3
Properties on Viably+
Seats on every plan
$7
per day, billed annually
FAQ

Questions about SEO monitoring

What does SEO monitoring in Viably include?
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.
Do I still need Google Search Console?
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.
How do I connect Google Search Console to 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.
Do I need a developer to set this up?
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.
How much history do I get?
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.
How many websites can I track?
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.
Will I get an alert every weekend?
No. Viably compares each Saturday with the four Saturdays before it, and does the same for every other day.
Why do the numbers change after a day has passed?
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.
How does Viably connect a search query to revenue?
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.
Can Viably fix SEO problems for me?
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.
Viably says it can't read my site. What now?
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.
Is my Search Console data safe?
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.
Read the full guideGoogle Search Console for Teams
Ready when you are

See which searches are paying for themselves.

Start free and share one property with Viably. Sixteen months of history load right away, and your first report is ready this afternoon.

Start freeSee pricing
SignalRecordOwned work
  • Free to start
  • No credit card required
  • Powers on when you need them