ViablyViably
Search Console and SEO

Your Google Search Console data, turned into work somebody owns.

Reporting is the easy half of search, and every team already has more of it than they read. Viably works the same data every day, finds the pages and phrases that are quietly costing you clicks, and puts each one in front of your team as something to do, with the fix named and the traffic it is worth written beside it.

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

One property free, three on Viably+, and a Restricted grant in Google is the whole setup.

#growth — Slack
Today
Viably square
ViaApp10:42 AM
📈The week in search

Posted with the weekly pulse, in the channel that already receives it.

Clicks
6,240 (up 12%)
Average position
9.1, from 10.4
Worth doing
3 findings, 1 to act on
Connect itAdd Viably's address as a Restricted user on the property, the way you would add a colleague
What you needOwner access to a Search Console property
Up and running in2 minutes
On your planOne property free, three on Viably+
Where it landsThe Search dashboardThe weekly pulse in SlackThe inbox your team triagesThe issue boardReads only
What arrives

Sixteen months of history, then every morning after.

The first sync walks back through everything Google still holds on the property, which takes a few minutes. The sweep that follows runs before your team is awake.

Performance, daily

Held per property, per query and per page, keeping the 250 that carry the traffic for each day.
ClicksImpressionsClick-through rateAverage position

Inspected, page by page

Google's own coverage report has no API, so Viably rebuilds it one inspection at a time and remembers what it said last week.
Index verdictCrawl stateThe canonical Google pickedWhen it last looked

Worth doing

Graded by what each is worth as a share of that property's own traffic, so act, look and note mean the same thing on a four-hundred-page site as on a forty-thousand-page one.
Query shortfallStriking distancePages that stopped being servedWatchlist slips
The clicks you already rank for

Every site is sitting on traffic it earned and never collected.

A query taking twenty thousand impressions at position six and converting a handful of them will never appear on a top-queries list, because that list is sorted by the exact number that is too low. Viably folds the near-duplicate phrases into one row, compares each one against what its rank usually earns, and orders what is left by the clicks the shortfall is worth. Opening a row divides it by intent, which turns a keyword list into a content brief.

Seen, and not clickedathlead.com · last 90 days
Query clusterRankMissed clicks
webhook to slackPosition 6.4 usually earns about 859 clicks at 4.00%, and this took 268.6.4591
Opened, it divides by intent
webhook to slack without zapier4.1K
slack webhook relay self hosted3.9K
send stripe webhooks to a slack channel2.4K
and 9 more phrases folded into this row
search console api rate limitPosition 8.7 usually earns about 340 clicks at 2.80%, and this took 96.8.7244
stripe payment failed alertPosition 4.8 usually earns about 499 clicks at 6.00%, and this took 51.4.8448
1.3K clicks on the table in three rowsRanked by the shortfall rather than by clicks, which is why none of these appear on a top-queries list. Sorting by the number that is too low can only ever hide them.
16 months
Of history, loaded on the first afternoon
2 min
To connect a property, with no code
250
Queries and pages kept per day, per property
Findings, not rows

Every panel here answers a question your team gave up asking.

Search Console hands you a search box and a list of everything, which is why most teams open it once something has already gone wrong. Viably sweeps the same data before your team is awake and does the work nobody has the afternoon for, folding the near-duplicate phrases together, measuring each one against the click-through its rank ought to earn, inspecting the pages that carry real impressions, and remembering what Google said about them last week so this week's answer means something.

What comes out is a short page of panels, and every one of them settles a question that got quietly dropped somewhere around the second quarter: which phrases people see and scroll past, what is sitting on page two close enough to be worth an afternoon, which pages Google has stopped serving and how many clicks left with them, and which of your landing pages have produced paying customers rather than merely traffic.

Automation

A finding that stays a finding was never worth generating.

SEO work dies in the gap between noticing something and somebody owning it. Viably closes that gap inside the inbox your team already triages: the finding arrives with the endings its own kind is asking for, one click files it where the work actually lives, and the card leaves the list because the thing it was asking for has happened.

ViablyViably
Inbox · SEOathlead.com · swept 2 hours ago
Product snippets markupGoogle reads the Product snippets markup on these pages and reports what is missing or malformed. Where it names a field in quotes, that field is the change, and it goes into the template that renders every page listed rather than into the pages one at a time.
Product snippets: Missing field “aggregateRating”Act now1.2K clicks at stake
Reported as an error.The 12 pages
Draft a fixFile as issueMake it a taskSnoozeDismiss
Pages that have dropped out of the indexGoogle has moved a run of pages into a state it will not serve them from, and each of these held that state across two sweeps rather than being caught while it settled. The state itself names the work.
Crawled, currently not indexedAct now906 clicks at stake
Moved in from “Submitted and indexed”, mostly under /guides.The 31 pages
Draft a fixFile as issueMake it a taskSnoozeDismiss
New links onto pages that have produced contactsA site that was not linking to you last month is now, and what it points at has produced contacts before. This is the one referrer signal that is commercial rather than technical, so it is worth somebody reading the article the week it appears while there is still a conversation to be had.
changelog.devWorth a look214 clicks at stake
Started linking to 2 pages that have produced contacts.The 3 referring URLs
Pin to the boardMake it a taskSend to SlackSnoozeDismiss
Left the inbox this week
Your own links carrying ?amp=Filed as an issue, on the board and mirrored to GitHub, assigned to Jim.
“slack alerting” is seen and not clickedMade a task, due Friday, with the shortfall and the phrases in the brief.
Duplicate without user-selected canonicalSnoozed. It comes back only if the clicks behind it grow by half.
Every finding arrives one click from an ownerand a decision you have already made is not asked for twice
  • It becomes an issue on the board

    The evidence, diagnosis and affected pages go with it. If a repository is connected, the issue is mirrored to GitHub with everything the developer needs.

  • Or a task with a date and an owner

    Content work needs an owner and a deadline. The task lands on the board with both, posts a card in your channel and reminds the owner when it's due.

  • Snoozing waits on the clicks

    Snooze an item and Viably brings it back once the clicks behind it grow by half, when there's something new to decide.

  • Dismiss it once, for good

    Noindex tags, redirects and canonicals all look like pages leaving the index. Dismiss the group once with a reason, and new pages that join it stay quiet.

Every issue, every task on the kanban, and everything that moves the needle for our team goes through Via. It organizes work in a way that is truly only possible because of all the automation hooks that it packs with it. We cannot imagine having to work without it after the third month.

Gerald BryanLead Architect, Sectors Financial AI Suitesectors.app
Being told, rather than remembering to look

The people who need to know are not the people who log in.

Search problems have a habit of going unnoticed for a fortnight, and a dashboard only helps the person who opens it. Viably watches for three things worth interrupting somebody about and stays quiet the rest of the time, which is the only reason the interruptions still work six months in.

  • 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.

  • The week, read back to you

    Search performance joins the weekly pulse in whichever channel already gets it, with buttons that break the week down day by day.

Meet Via, in Slack
#growth — Slack
Revenue

The search that started the relationship, beside the money it ended in.

Search brings somebody to a landing page, and Viably already holds what happened next, because the form they filled in, the enquiry they sent and the payment they made were all captured against one contact record. Putting Search Console in the same system is what makes a search term stop being a vanity metric.

ViablyViably
The Viably contacts dashboard, showing the acquisition funnel, revenue by source, a capture trend, and the contact table
  • Pages linked to the customers they won

    Every contact keeps the source that first brought them in, along with their forms, emails and payments. Each customer traces back to the page that earned them.

  • Revenue by page, beside the clicks

    The Search Console dashboard has a revenue panel built from your actual payments, showing which content pays for itself.

  • Ask about it where your team already is

    Once a property is connected, anyone can ask Via about search performance in any channel. Answers come from your synced numbers with the period stated.

Priced per workspace, so the whole team can read the numbers.

Every other tool in this category charges by the seat, which is how SEO ends up being one person's job and everybody else's blind spot. Viably is billed per workspace with unlimited seats, the free plan carries a full property, and Viably+ raises that to three alongside everything else the workspace runs.

14 days
Viably+ trial.
Seats on every plan
$7
per day, billed annually
3,000
Events each month
The Search Console opportunities panel, ranking query clusters by the clicks their shortfall is worth
The striking-distance panel, listing the pages parked on the second page of results
The findings panel, folding hundreds of inspected pages into a short list of fixes
The coverage panel, showing what Google says about every page that earns impressions
The watchlist panel, tracking the queries and pages a team has starred
The search revenue panel, pairing landing pages with the customers they produced
The searches you already rank for and still lose the click on, ordered by what the shortfall is worth in traffic rather than by the number that is too low to notice.
FAQ

Questions about the Google Search Console integration

What does Viably do that Google Search Console does not?
Search Console reports, and Viably decides. It reads the same performance data every day, measures each query cluster against what its rank usually earns, inspects the pages that actually get impressions, and turns the result into a short list of things worth doing with a click figure beside each one. Every item on that list can be filed as an issue or a task that somebody owns, and taking it off the list is what makes it go away.
Does this replace Ahrefs or Semrush?
No. Those tools crawl the whole web to tell you about keywords you do not rank for and links you do not have, and Viably has no crawler and no keyword database. What Viably does is work on the data Google already gives you about your own property, and carry the conclusions into the place where your team assigns work. Plenty of teams run both, and the teams who have never bought either tend to find this is the layer they were missing.
How is this different from a Looker Studio dashboard?
A Looker Studio report shows you the same numbers arranged more attractively, and it still asks somebody to open it, notice something, and then translate what they noticed into work. Viably does the noticing on a schedule, applies the arithmetic that turns an observation into a priority, and hands the result to your issue board and your Slack channel. Nobody has to remember to look.
Can it open a GitHub issue for an SEO problem?
Yes. An SEO finding files as an issue on the Kanban board, and where a repository is connected it is mirrored into GitHub with the diagnosis, the affected URLs and what the fix is worth already written into the body. Content work usually goes the other way and becomes a task with a due date and an owner, which posts a card into the channel you pick.
How does Viably decide what to show first?
By what the finding is worth as a share of that property's own traffic, so a tier means the same thing on a four-hundred-page site as it does on a forty-thousand-page one. A problem whose fix is named outranks one that only describes a symptom, and an item that has sat untouched for six weeks quietly drops a tier rather than shouting louder, because a surface that escalates the longer it is ignored teaches people to stop reading it.
Will this flood our Slack channel?
It should not, and most of the design went into making sure. Alerts fire at most once a day per property per kind, they are measured against the same weekday over four weeks so the weekend dip never triggers one, days Google is still restating are excluded entirely, and a repeat about the same property replies in the existing thread. Everything that does not meet the bar stays in the dashboard where you can go and find it.
How many websites can we connect, and what does it cost?
One property on the free plan and three on Viably+. A domain property counts once and covers every subdomain and both protocols beneath it, so a single grant on your domain usually brings the blog, the marketing site and the app subdomain in together. Viably is billed per workspace rather than per seat, so the whole team reads the same numbers at no extra cost.
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.
How long before it finds something?
The first sync backfills sixteen months of history, which takes a few minutes, and the query shortfall table is answerable as soon as it lands. The page inspections build up over the first sweep and the findings layer stays quiet until a full pass has been round, because a surface that reports every pre-existing problem on day one as though it were news is one nobody trusts on day two.
Ready when you are

Stop reading the report. Start working the list.

Add Viably's address to your property in Google, and sixteen months of history plus the first findings are waiting by the time you get back.

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