Google Search Console

Loomaly scans your pages on its own; Search Console is optional. Connecting it adds real Google search data, so issues on pages that actually get traffic rank higher, and it lets you manage sitemaps from chat (google) or /account. It's also the quickest way to verify your site, which turns on the weekly re-scan.

What connecting unlocksCopy Anchor Link

Title gapsCopy Anchor Link

A title gap is a query people already use to find a page, with enough impressions to trust (50 or more over 28 days) and an average position of 20 or better, that the title and the H1 never mention. Loomaly lists up to three per page. Setting your own target phrase does not suppress them. Brand queries are not chosen as the target phrase; a brand query can still be a title gap when it is not that phrase.

The same list appears on visibility with view: google as titleGaps. Each striking-distance row also says whether the query is in the title (inTitle) and the H1 (inH1).

Search opportunitiesCopy Anchor Link

On Pro and Agency, todo with view: opportunities surfaces pages from the latest 28 days of Search Console data. Three kinds:

• Almost page one: average position 5–20, at least 100 impressions.
• Low click-through: position 1–20, at least 50 impressions, and a click-through rate under 60% of the usual rate at that position. The usual change is a new title and description.
• Falling clicks: clicks down at least 30% versus the previous 28 days, while impressions are still at least 70% of that previous window.

Each item shows the queries, impressions, clicks and position behind it, and what to change. set_goals can set that page as the focus page. The same page and kind is not raised again for 90 days unless the numbers get clearly worse.

This week's plan can take the top one or two of these pages on Pro and Agency. They are ordered by weight: impressions times the click-rate lift toward a typical position-8 result, impressions times how far the click-through sits under the usual rate, or the clicks lost versus the previous 28 days. Focus-page keyword issues come first, then these, then the rest of the queue. Free and Starter see how many there are and a nudge to Pro, not the rows.

History is kept for 90 days. A connected site catches up in slices of 14 days, one slice per day, and days already stored are not rewritten.

Before you connectCopy Anchor Link

Connect a Google account that already owns a verified Search Console property for this site: a Domain property, or an https URL-prefix for the site. Loomaly uses that property and can submit the sitemap. If the account has no property yet, connecting also asks Google for site verification. Loomaly then returns a homepage meta tag (often as a handoff), and confirms it after the tag is live.

To submit sitemaps from Loomaly, and for connecting to count as verifying your site, you need Owner or Full permission on the property in Search Console. Read-only (restricted) access is enough for the search data.

ConnectCopy Anchor Link

Right after connecting, Loomaly imports the last 28 days of search data in the background, so visibility fills in shortly. After that it pulls new data once a day. Page and site totals include searches Google keeps anonymous, which never show up in the list of queries: on a small site they can be most of the traffic. Search Console data is usually 2–3 days behind, so the most recent days fill in over the following days.

The connection belongs to the site, not to you personally. Everyone on the project sees the same data, and any project member can connect or disconnect it.

Connecting verifies your siteCopy Anchor Link

A Search Console property for the domain, where you're an owner or full user, is the same proof of ownership as a DNS record. It has to be a Domain property, or a URL-prefix property for the root of the site (not a sub-path such as /blog/). If the account already has one, connecting verifies the site. The weekly re-scan and the weekly report then switch on by themselves, with the first re-scan a week later, and the deploy webhook becomes available. If it does not, Loomaly asks for the site verification permission (included in a new Search Console connect) and returns a homepage meta tag to add — often via google with action: verify and a handoff. With restricted (read-only) access, or only a sub-path property, the connection still brings in search data but doesn't verify the site. See Verify your site.

PermissionsCopy Anchor Link

Connecting Search Console asks Google for two things. Signing in to Loomaly asks only for email, profile and openid, and does not include Search Console.

• Search Console (webmasters scope): view and manage Search Console data for your verified sites. Loomaly asks for the full scope rather than read-only because submitting and removing sitemaps needs write access.
• Your email address: only to show which Google account is connected.

A Search Console connect asks for webmasters, email, and https://www.googleapis.com/auth/siteverification.verify_only. Google's Site Verification guide describes that scope as the ability to verify new sites, with no read access to sites you already verified. The API discovery document allows it on webResource.getToken and webResource.insert, which are the two calls that issue a meta tag and confirm it. Listing or editing sites you already verified needs the wider siteverification scope, which Loomaly does not request. Sign-in stays email, profile and openid. An older Google connection that lacks verification can be upgraded from /account with one extra Google prompt.

With the access requested today, Loomaly makes only these calls:

• reads search analytics (queries, pages, dates, with clicks, impressions, CTR and position),
• lists your properties when you connect, to pick the one that matches the site,
• lists your sitemaps, and submits or removes one when you ask via google or after a sitemap fix is verified.

Loomaly never requests indexing on your behalf and doesn't use Google's Indexing API. Google only allows that API for job postings and livestreams. Google tokens are stored encrypted.

Requesting a re-crawlCopy Anchor Link

After you fix a page, you can ask Google to crawl it again sooner. Open Search Console's URL Inspection for that exact page in the right property and choose Request indexing there yourself. Loomaly's own re-check of your fix (check with target: fix) is separate and doesn't depend on Google re-crawling.

SitemapsCopy Anchor Link

Ask your assistant to submit the sitemap with google, or manage it under /account. You can:

• see each sitemap with its status (Active, Pending, Warnings or Errors) and when it was last submitted and fetched,
• submit a new one (a path such as /sitemap.xml or a full URL),
• remove one from Google.

Google can take hours to days to process a new sitemap.

Reconnect when access expiresCopy Anchor Link

If Loomaly can no longer read your data, visibility / google return a recoverable error pointing you to reconnect. This happens, for example, when you remove Loomaly's access in your Google account. Re-authorize from the handoff URL or from /account.

DisconnectCopy Anchor Link

Under /account, disconnect Google Search Console for the site. Loomaly deletes the stored Google tokens, forgets the property and stops the daily import. The site stays verified, and the weekly re-scan keeps its setting.

Disconnecting in Loomaly doesn't remove the grant on Google's side. To revoke that too, remove Loomaly at myaccount.google.com/permissions.

If connecting failsCopy Anchor Link

Common messages and what to do:

Search Console and MCPCopy Anchor Link

When you connect an assistant over MCP, the consent screen lists gsc:read and gsc:write. Both start ticked.

• gsc:read — visibility with view: google: clicks and impressions for 7, 28 or 90 days, movers, striking-distance queries and title gaps. Without it, the assistant still sees focus-page numbers via focus.
• gsc:write — google with action: connect, verify or submit sitemap. Verify uses an existing property when one exists; otherwise it returns a handoff URL and a homepage meta tag.

If the token is missing a scope, reconnect at /account/agents and keep both Search Console boxes checked.