Search Console connected, sitemap submitted

One consent connects Search Console, resolves which verified property matches the site, submits the sitemap, and pulls real query and page performance.

What it is

Tokens stored encrypted in the site settings, refreshed on demand. Property resolution picks the domain property matching the site and stores it. Sitemap submission is a direct API call. Performance reads return the top queries and pages for the last 28 days with clicks, impressions, click-through rate and average position.

Also called: GSC · Google search data · submit sitemap · search rankings from Google

See it
Search Console connected, sitemap submitted
Area
Integrations
Group
Google
System
Search Engines
Solves
3 named problems
01The connect flow uses the shared platform Google app with a search-console kind marker in the state.
02The callback checks the required permission was actually granted and refuses clearly if not.
03Tokens are encrypted into the site settings and the property is resolved.
A connection card reading 'Search Console connected (sc-domain:…) — sitemap submitted', above a top-queries table. Sample data — no customer information appears here.
How it works
  1. 1The connect flow uses the shared platform Google app with a search-console kind marker in the state.
  2. 2The callback checks the required permission was actually granted and refuses clearly if not.
  3. 3Tokens are encrypted into the site settings and the property is resolved.
  4. 4The sitemap is submitted immediately on connection.
  5. 5Performance queries run per dimension for the last 28 days.
Why we built it

The engines module records the division of labour: instant-ping protocols cover several engines, but 'Google ignores IndexNow; it discovers through the sitemap + Search Console instead.' The connect flow gives useful refusals rather than silent failure — when the permission is not ticked, it returns 'Search Console access wasn't granted — tick the permission', and when no matching property exists, 'No leads2build.com property on this Google account — add/verify it in Search Console first.'

The problem
  • Search performance data was invisible.
  • Sitemaps had to be submitted by hand in a separate console.
  • A partially granted consent failed silently.
Sound familiar?
What you get
Real query and page performance in the platform.
The sitemap is submitted the moment the connection is made.
Missing permissions and missing properties are named explicitly.
What's inside

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 →