BillionVerifyGoogle Search Console

Detect content decay from Google Search Console and alert via Slack and email

Pull contacts, verify each address with BillionVerify, and continue to Google Search Console — only deliverable addresses get through.

Download n8n workflow (JSON)Install the n8n node

Why verify before the send

Sending to invalid, risky, catch-all, or disposable addresses spikes your bounce rate and erodes sender reputation. A verification gate before the Google Search Console step removes that risk automatically — only deliverable addresses continue, the rest are flagged.

The workflow

BillionVerify — verification sits right before the send.

+10

n8n steps

Verify Email (BillionVerify)

n8n steps

Node by node

1
Weekly Monday 8AM TriggerTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
2
Calculate Date RangesSource· n8n
Provides or transforms the contact data flowing through the workflow.
3
Fetch GSC Recent 7 DaysSource· n8n
Provides or transforms the contact data flowing through the workflow.
4
Fetch GSC Previous 28 DaysSource· n8n
Provides or transforms the contact data flowing through the workflow.
5
Compare Periods and Detect DecaySource· n8n
Provides or transforms the contact data flowing through the workflow.
6
Filter Only Decaying PagesLogic· n8n
Routes items based on the workflow logic.
7
Log All Results to Decay SheetSource· n8n
Provides or transforms the contact data flowing through the workflow.
8
Build Weekly Decay ReportSource· n8n
Provides or transforms the contact data flowing through the workflow.
9
Check If Any Critical PagesLogic· n8n
Routes items based on the workflow logic.
10
Post Report to SlackSource· n8n
Provides or transforms the contact data flowing through the workflow.
11
Verify Email (BillionVerify)Verify· billionverify
The BillionVerify node verifies the address — status (valid / invalid / risky / catch-all / role / disposable), is_deliverable, and a confidence score — before anything is sent.
12
Generate Fix Tasks for Critical PagesSource· n8n
Provides or transforms the contact data flowing through the workflow.
13
IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
14
Log Fix Tasks to SheetSource· n8n
Provides or transforms the contact data flowing through the workflow.
15
Email Weekly ReportSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.

Workflow JSON

Copy or download this workflow, then import it in n8n (Workflows → Import from File / Paste). Install the BillionVerify community node first, then add your API key credential.

verify-emails-in-google-search-console.json26 KB · n8n workflow

Download

When to use this

Cleaning a list before a Google Search Console send or sync.
Protecting Google Search Console deliverability and sender reputation.
Keeping bounce rates low so your sending is never throttled.

Three ways to connect

n8n node

Install the BillionVerify community node and drop it into this workflow.

Integrately

1-Click connect BillionVerify with 1500+ apps, no code.

REST API

Call the verification API directly from any stack.

FAQ

Why verify before sending in Google Search Console?

Verifying first keeps your bounce rate low, which protects your sender reputation and your results.

How do I import this workflow?

Download the JSON, then in n8n go to Workflows → Import from File (or paste it). Install the BillionVerify community node and add your API key credential.

What happens to risky or catch-all addresses?

They are routed to the false branch and excluded from the send. You decide whether to retry, review, or drop them.

Add verification to your workflow

Create a free account, grab your API key, and stop bounces before they happen.

Get started free