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.

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 clicked
athlead.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 monthsOf history, loaded on the first afternoon
2 minTo connect a property, with no code
250Queries 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.

Everything is graded by what it is worth as a share of your own traffic, so these three words mean the same thing on a four-hundred-page site as they do on a forty-thousand-page one.

Act nowWorth a lookFor information
See every panel in the guide
Visual representation for tip: 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.
Visual representation for tip: Everything parked on page two, where one honest afternoon of work moves more traffic than a month spent writing something new.
Visual representation for tip: Hundreds of inspected pages folded into the handful of fixes worth taking into this week, each one carrying the clicks that are riding on it.
Visual representation for tip: What Google actually says about every page that earns impressions, rebuilt one inspection at a time because its own indexing report has no API.
Visual representation for tip: Star the queries and the pages you cannot afford to lose, and hear about it the morning one of them slips off the first page.
Visual representation for tip: The landing pages that have produced paying customers, sitting in the same table as the search traffic that brought them in.
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.
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 · SEO
athlead.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 now
12 pages, reported as an error.The 12 pages
1.2Kclicks at stake
File as issueMake it a taskPin to the boardSnoozeDismiss
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 now
31 pages moved in from “Submitted and indexed”, mostly under /guides.The 4 sections
906clicks at stake
File as issueMake it a taskPin to the boardSnoozeDismiss
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 look
Started linking to 2 pages that have produced contacts.The 3 referring URLs
214clicks at stake
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 owner·and a decision you have already made is not asked for twice
  • It becomes an issue on the board

    The evidence, the diagnosis and the pages travel with it, and where a repository is connected the issue is mirrored into GitHub so whoever picks it up never has to come back here to find out what was meant.

  • Or a task with a date and an owner

    Content work wants a person and a deadline rather than a bug report. The task lands on the board with both, posts a card into the channel you choose, and chases its own owner when the day arrives.

  • Snoozing waits on the number, not the calendar

    A date snooze brings back something identical to what you put away, and the second look is exactly as uninformative as the first. Viably wakes an item when the clicks behind it grow by half, so it returns only once the situation has changed enough to deserve a new decision.

  • Dismissing it once dismisses it for good

    A noindex, a redirect and a canonical are all deliberate acts that Google reports as a page leaving the index. Say so once, with a reason that stays on the record, and the sweep stops raising it however many pages join the group later.

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

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 moved, measured against the right baseline

    Search traffic falls every weekend on almost every site, so a threshold against a flat average fires each Saturday and is muted by the end of the month. Viably compares a day against the same weekday over the previous four weeks and ignores days Google has not finished restating.

  • Something you watch has slipped

    Star a query or a page and you hear about it when it falls off the first page of results. Nothing else in the long tail can set this off, which is what keeps the notification meaningful a year later.

  • The week, read back to you

    Search performance joins the weekly pulse in whichever channel already receives it, with buttons that break the week down day by day without anybody leaving the thread. Repeats about the same property reply under the original message rather than starting a fresh one.

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
  • The landing page already knows who it converted

    Viably captures forms, enquiry email, in-app events and payments against one contact record, and every contact keeps the source that first named them. The page that earned the click and the customer who followed it are the same row.

  • Revenue by page, beside the clicks that produced it

    The Search Console dashboard carries a revenue panel drawn from the payments themselves, so the question of which content pays for itself is arithmetic over the event log rather than a guess assembled from two tools that have never met.

  • Ask about it where your team already is

    Once a property is connected, @Via answers questions about search performance in whatever channel somebody happens to be standing in, grounded in the numbers already collected and 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 daysViably+ trial.
Seats on every plan
$7per day, billed annually
2,000Events each month
FAQ

Questions about Search Console in Viably

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
  • The free plan needs no card
  • Powers on when you need them