DocsTools
Google Search Console
Queries, pages, clicks and index status.
- Category
- Analytics
- How you connect
- Sign in, read only unless you allow writing. You sign in with your account. Homla never sees your password.
- Time to set up
- About 1 minutes
- Actions
- 6 read, 2 write
Connect it#
In Homla, open Connectors, then Google Search Console. The Setup guide button walks you through the same steps, with fields to paste into.
Who can do it. Anyone with a Google account that has the property in Search Console. Owner or Full user sees every report; a Restricted user sees most data but cannot submit sitemaps.
- Check which Google account has the propertyOpen Search Console and look at the property picker, top left. The account you are signed in with is the one to connect. No property there? Ask the owner to add you in Settings → Users and permissions. Open it.
- Click Connect in HomlaIn Homla, open Connectors → Google Search Console and click Connect my Google account. Tick Also allow editing only if you want your assistant to submit sitemaps. Open it.
- Pick the account and allowGoogle asks to View Search Console data for your verified sites (plus Manage it if you ticked editing). That is all it asks: connecting Search Console never touches your Analytics, Tag Manager, Gmail, Drive or Calendar connections.
Signed in to several Google accounts? Pick the one from step 1. The wrong account connects fine but shows no properties.
- Ask your assistantTry: "Which keywords are on page 2 for example.com?" If it says the property is not found, it lists the properties your account has: use one of those, or check step 1.
"Unverified site" or no data: the property must be verified in Search Console, and new properties take a few days to collect data.
What your AI can do#
These are the actions Homla gives your AI. Your role decides which ones you get. Write actions are a dry run until confirmed, see Approvals and dry runs.
Read#
Looks things up, never changes anything.
| Action | What it does |
|---|---|
google-search-console_sites_list | List the Search Console properties this Google account can see, with permission level. |
google-search-console_search_analytics_query | Clicks, impressions, ctr, position by dimensions, date range and ANDed filters (country is ISO-3). |
google-search-console_striking_distance | Keywords ranking just off the top (default avg position 8-20) with real impressions: the quickest SEO wins. |
google-search-console_declining_pages | Pages (or queries) that lost the most clicks vs the previous period of equal length. |
google-search-console_url_inspect | How Google sees one URL: index verdict, coverage, canonical, last crawl, robots.txt, rich results. |
google-search-console_sitemaps_list | Sitemaps submitted for a property with last submit/download, errors, warnings and URL counts. |
Write#
Creates or changes things, as the account owner.
| Action | What it does |
|---|---|
google-search-console_sitemap_submit | Submit or resubmit a sitemap URL to a property so Google recrawls it. |
google-search-console_request | Any Search Console API call without a tool (site get/add/delete, sitemap delete). |
Disconnect it#
In Homla, open the account menu on the tool's page and choose Disconnect. Anyone it was shared with loses access at once. To cut it off on the tool's side too:
To cut Homla off, remove Homla from your Google account's third-party connections: the token stops working at once. Or click Disconnect on your account in the Homla card. Reconnecting is one click.
Generated from the product code. Action names are what the CLI and the API use.