Google Search Console integration

Search performance & indexing

11 operationsMarketing

Google-search-console is Google's tool for tracking how a site shows up in Search, from ranking queries to indexing status. The NoClick Google-search-console node calls the Search Console API directly, so a single workflow can query search analytics for clicks, impressions, and average position, inspect individual URLs for index coverage, submit and manage sitemaps, and run a mobile friendly test on any page. It can also add, remove, and list the verified sites on your account. Put it on the canvas to turn SEO monitoring and reporting into scheduled jobs instead of manual dashboard checks.

What you can automate with Google Search Console

Google Search Console operations

Analytics1

URL Inspection1

Sitemaps4

Sites4

URL Testing1

Templates using Google Search Console

SEO Performance Digest Agent

Posts one weekly Slack digest of what your tracked queries actually did in Search Console, logs every number to your sheet, and names the pages worth fixing. Search Console holds the data and almost nobody opens it, so a page that lost half its clicks in March gets noticed in June. Every Monday this agent compares last week to the week before, appends the numbers to your sheet so you keep a history past the 16 months Search Console retains, and posts one Slack message naming winners, losers and the pages earning impressions but no clicks. It is for marketers and agencies who want the movement, not another dashboard to visit. ## What people use it for - **Catch a drop the same week** - A ranking loss shows up in the LOSERS section the Monday after it happens, with both weeks' numbers next to it. That is the difference between a fix and a quarter of missing traffic. - **Keep your own ranking history** - Every run appends a row per tracked query to your sheet, so a year later you can chart what a page did through a redesign or a core update instead of trusting memory. - **Send clients a weekly report** - Agencies run one copy per client property with that client's queries in the variables. Each account gets the same structured digest in its own channel, without anyone building a slide. - **Find pages worth fixing** - PAGES TO LOOK AT lists the pages with impressions but very few clicks, which is usually a title or an intent mismatch rather than a ranking problem. It is the cheapest work on the list. ## Before you fork **What do I need connected before this runs?** A Google account with access to the verified Search Console property, a Google Sheet to log into, and one Slack channel. During setup you describe the site, who reads the digest, and which queries and pages you track. Nothing gets installed on your website. **What does it cost to run?** It runs once a week, so roughly four runs a month regardless of whether your site gets a thousand visits or a million. Each run is a handful of Search Console reads, one sheet append and one Slack message. Moving it to daily simply multiplies that by seven. **Can it be wrong about my traffic?** Every number comes straight from the Search Console API and is written verbatim, so the digest is as right as Search Console is, including its two day reporting lag. It will not forecast, promise a recovery, or explain a movement the data does not explain. If a call fails it says so in the NOT SEEN line rather than quietly leaving the section out.

79515 nodes

Questions

Yes. The Query Search Analytics operation returns clicks, impressions, click-through rate, and average position, and you can group the results by query, page, country, or device. Wire it to a schedule and it runs daily or weekly reports without anyone touching the Search Console dashboard.

The node authenticates with Google through OAuth, so you sign in with the Google account that owns your verified properties and grant access once. After that, it can read analytics, inspect URLs, and manage sitemaps for any site on that account.

Yes. The Inspect URL operation runs the Search Console URL inspection on any page and returns its index and coverage status. Loop it over your key URLs on a schedule and the workflow can alert you when a page falls out of the index.

It can. The node submits a sitemap, deletes one, and lists or gets the sitemaps already registered for a site. A publishing workflow can resubmit your sitemap automatically every time new content goes live.

Search Console does not push events, so this node is request and response only, with no triggers of its own. You schedule it or fire it from another node, then compare the search analytics it returns against a threshold or a previous run to catch drops and send an alert.

Give Google Search Console to an agent

All integrations

Free to start.