Resources · Make integration

Google Search Console Make integrationAutomate Google Search Console with Make.

Tired of opening Search Console to check the same pages by hand? The Google Search Console Make integration gives you 7 modules for sitemaps, URL inspection and traffic reports. This guide shows how to link your account and build a first scenario that does the checking for you.

Try the Google Search Console integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Google Search Console Make integration do for you?

The integration lets Make read and update your Search Console property without you opening it. You build a scenario, which is the automation itself: a chain of modules, each module being one brick that performs one job, like inspecting a URL or submitting a sitemap. Make then runs that chain on a schedule or when another app calls it.

Know whether a fresh article is indexed. A content writer publishes a post, the URL lands in a spreadsheet, and Inspect a URL returns what Google has on file for that page. The answer can go straight to the editor who asked.

Keep sitemaps under control. After a site migration, List Sitemaps shows every sitemap the property knows about, Get a Sitemap opens the details of one, and Submit a Sitemap or Delete a Sitemap cleans up the list without a trip to the dashboard.

Feed traffic numbers into your own reports. Run a Report searches traffic data for a URL, so a marketing lead can push it into a table used by the whole team.

There is no trigger in this app: Make cannot be woken up by Search Console itself, so every scenario starts from another app or from the Make schedule. What the 7 modules do not cover can go through Make an API Call. The same app often has an n8n node too; the n8n vs Make comparison helps you pick, and the Make training walks through scenarios like these step by step. If a run fails, Make troubleshooting lists the usual fixes.

Connect

How do you connect Google Search Console to Make?

  1. 01

    Add a module and open the connection

    In your scenario, add any Google Search Console module and click Create a connection. A connection is your Google account linked to Make once, then reused by every module of this app. You need a Google account with access to the property.

  2. 02

    Name it so you can find it later

    The Connection name field is optional, but a clear name like the site or the client helps when you manage several properties. Leave Show advanced settings off unless you plan to use your own Google Cloud credentials.

  3. 03

    Sign in and approve access

    Click Sign in with Google, choose the account that owns or manages the property, and confirm the access Google asks for. Back in Make, the connection appears in the module and the fields can now list what your account can read.

First scenario

Your first scenario: check the index status of a new page

GoalWhen a new page URL appears in the tool where your team lists published content, Make asks Google Search Console whether that page is in the Google index.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. It belongs to the app where your published URLs land, since Search Console has no trigger of its own.

  2. 02

    Set the starting module

    Pick that app, create its connection, and point it at the place where new URLs are written. Each new URL becomes one bundle, meaning one item that flows to the next module.

  3. 03

    Add Inspect a URL

    Click the + on the right, search Google Search Console, pick Inspect a URL and select your connection. Map the URL from the first module so every bundle is checked on its own.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and confirm the status returned by Google matches the page you expected.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Keep it or change it, then switch the scenario on.

Modules

What each Google Search Console module does

Google Search Console gives you 7 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Sitemap

4 modules
Google Search Console1

List Sitemaps

Search

In Make“Lists the sitemaps-entries submitted for this site, or included in the sitemap index file (if sitemap index is specified in the request).”

Gives you every sitemap already submitted for a site, or those included in a sitemap index when you point it at one. Each sitemap comes out as its own bundle, ready to be checked or logged.

When to use it
right after a redesign, to see which sitemaps Google still holds before you tidy anything up.
Watch out
as a search module it can return zero, one or many bundles, so every module after it runs once per sitemap.
Google Search Console2

Get a Sitemap

Action

In Make“Retrieves information about a specific sitemap.”

Pulls the information Search Console keeps about one specific sitemap, so you can read its state without browsing the dashboard. You get a single result for the sitemap you name.

When to use it
after a submission, to confirm Google has the file on record, or behind List Sitemaps when one entry deserves a closer look.
Watch out
it reads one sitemap at a time; to cover them all, place it after List Sitemaps rather than duplicating the module.
Google Search Console3

Submit a Sitemap

Action

In Make“Submits a sitemap for a site.”

Hands a sitemap to Google for a given site, the same move you would make by pasting its address in Search Console. The result is a sitemap Google now knows about.

When to use it
when your CMS or a teammate creates a new sitemap, for example for a new language section, and you want Google told without a manual step.
Watch out
test it with Run once on a real sitemap address before switching the scenario on.
Google Search Console4

Delete a Sitemap

Action

In Make“Deletes a sitemap from the specified site.”

Removes a sitemap from a site in Search Console, which keeps the property free of old files that no longer match your structure. It only acts on the sitemap you point it to.

When to use it
when a section of the site is retired and its sitemap should disappear from the list Google checks.
Watch out
a deletion does not come back by itself; check with Run once that the sitemap address it receives is the one you mean to remove.

Other

3 modules
Google Search Console5

Inspect a URL

Action

In Make“Views the indexed or indexable status of the provided URL. Presently only the status of the version in the Google index is available; you cannot test the indexability of a live URL.”

Tells you whether a page is indexed, or can be, according to the version Google holds in its index. That answer is what an SEO lead usually looks up by hand, page after page.

When to use it
when a new article or product page goes live and someone wants to know if Google has picked it up.
Watch out
it cannot test the live URL; a page you just fixed may still show the old indexed state.
Google Search Console6

Run a Report

Search

In Make“Searches traffic data for the specified URL.”

Brings back the traffic data Search Console has for the URL you specify, so the figures can land in a spreadsheet, a database or a message instead of staying in the dashboard.

When to use it
when a client deck or an internal dashboard needs Search Console data that someone currently copies by hand.
Watch out
it is a search module and may return several bundles; an aggregator can merge them into one table row.
Google Search Console7

Make an API Call

Action

In Make“Makes an arbitrary authorized API call.”

Lets you call any endpoint of the Google Search Console API from your scenario with the connection you already set up. It is the way out when none of the six other modules does exactly what you need.

When to use it
once you have checked the listed modules and found a gap, and you are comfortable reading the API documentation.
Watch out
you write the request yourself, so Make no longer fills the fields or lists options for you.
Need help

Need help automating Google Search Console with Make?

A person reads every message.

FAQ

Google Search Console and Make: common questions

01Is the Google Search Console Make integration free?
Yes. Google Search Console is a standard app, so it works on the Make Free plan along with 3,000+ other standard apps. The Free plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, and 5 minutes of execution per run at most. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one operation being one module run on one bundle, so a report that returns many rows uses more of your monthly allowance.
02What do you need to connect Google Search Console to Make?
A Google account is the only prerequisite named by the Make documentation. Add a Google Search Console module, click Create a connection, give it a name if you like, then click Sign in with Google and confirm access. Pick the Google account that can see the property you want to automate. The advanced settings are optional: they let you use your own Google Cloud client, which requires enabling the Google Search Console API, configuring the OAuth consent screen and adding the Make redirect URI. Most people can skip that part and use the default sign in.
03Does Google Search Console trigger a Make scenario in real time?
No. The app has no trigger at all, neither scheduled nor instant, so Search Console never starts a scenario by itself. You have two ways to start one. The first is the schedule: the clock on the first module, set to every 15 minutes by default, runs the scenario at regular intervals. The second is to begin with a module from another app, for example the tool where your team logs new URLs, and let its bundles flow into Inspect a URL or Run a Report. Either way, your Search Console modules act only when the scenario runs.
04What if a Google Search Console module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Google Search Console API with the same connection, so you are not stuck with the six ready-made modules for sitemaps, URL inspection and reports. The trade-off is that you write the request yourself, guided by the API documentation, instead of filling labelled fields. The Make documentation gives no numeric limit for this app, so the main constraints come from your Make plan, such as the execution time per run and the operations you have left for the month.
05Make or n8n for Google Search Console?
It depends on how you like to work. In Make, Google Search Console comes with 7 modules, a guided connection through Sign in with Google and a visual editor where you test with Run once, all available on the Free plan. The same app often has an n8n node as well, so the choice usually rests on which tool your team already runs its other automations in, and which editor feels clearer to the person who will maintain the scenario. Try the first scenario on this page in Make, then compare with what the n8n side offers for your case.
Same platform

Other docs you might need on this stack.

Browse all integrations