Search Console connection

A one-click Google grant that resolves the right property, resubmits the sitemap programmatically, and pulls the real query and page performance for the last 28 days.

What it is

An OAuth connection through the platform's existing Google app, sharing the same callback as calendar and lead sources, distinguished by a state key. Tokens are stored encrypted on the site record and refreshed automatically. The connection resolves which property matches the domain, stores it, submits the sitemap by PUT, and queries search analytics for top queries and top pages.

Also called: GSC · google search console · submit sitemap to google · search queries

See it
Search Console connection
Area
Integrations
Group
Search engine plumbing
System
Marketing Site
Solves
3 named problems
01The grant asks for the webmasters scope with offline access and a forced consent prompt so a refresh token is always issued.
02Access and refresh tokens are encrypted before storage in the site's settings.
03gscToken() returns a live access token, refreshing and re-storing it when it is within a minute of expiry.
The Settings Search Console card showing the connected account and property, with the top-queries and top-pages tables beneath. Sample data — no customer information appears here.
How it works
  1. 1The grant asks for the webmasters scope with offline access and a forced consent prompt so a refresh token is always issued.
  2. 2Access and refresh tokens are encrypted before storage in the site's settings.
  3. 3gscToken() returns a live access token, refreshing and re-storing it when it is within a minute of expiry.
  4. 4gscResolveProperty() lists the account's properties, prefers the domain property, and reports plainly when none matches.
  5. 5gscSubmitSitemap() PUTs the sitemap URL against the resolved property.
  6. 6gscPerformance() pulls 25 rows each of queries and pages for the last 28 days with clicks, impressions, CTR and average position.
Why we built it

Search Console is the half of announcement Google actually reads — as the engines module puts it, "Google ignores IndexNow — it wants the sitemap resubmitted instead." Sharing the platform's existing Google app rather than adding a second one keeps one consent screen and one callback. Resolving the property rather than asking for it removes the most common setup mistake, and when it can't be resolved the error is actionable: 'No leads2build.com property on this Google account — add/verify it in Search Console first.'

The problem
  • Sitemap resubmission was manual.
  • Real query data lived in a separate tool nobody opened.
  • Choosing the right property is the most common setup mistake.
Sound familiar?
What you get
The sitemap is resubmitted automatically on every real change
Actual search queries and page performance in the same panel as everything else
The property is resolved for you, with a plain error when it can't be

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →