Lead Lock Systems LLC uses the Google Search Console API to retrieve organic search performance data, indexing status, crawl health, and URL inspection results for verified website properties. User data is accessed only with explicit OAuth authorization from verified property owners.
This tool is a web application developed and operated by Lead Lock Systems LLC that connects to the Google Search Console API via OAuth 2.0. It enables authorized property owners to view, analyze, and act on search performance and indexing data for websites they own and have verified in Google Search Console.
The application provides a unified dashboard that surfaces organic search metrics, keyword performance, index coverage issues, crawl errors, and URL-level inspection data — data that is already available to property owners inside Google Search Console, presented here in a format optimized for analysis and decision-making.
Access to Search Console data is granted exclusively by the property owner through Google's OAuth 2.0 authorization flow. The application never accesses any property without explicit user authorization, and access can be revoked at any time through the user's Google Account settings.
Retrieves clicks, impressions, click-through rate (CTR), and average position for queries, pages, countries, devices, and search appearance types over custom date ranges.
Surfaces the top organic search queries driving traffic to a verified property, including performance breakdowns by device type, country, and search appearance (web, image, video, news).
Retrieves organic performance metrics at the individual URL level, allowing property owners to identify top-performing pages and pages with declining visibility.
Accesses index coverage reports to identify which pages are indexed, excluded, or blocked. Surfaces error types including server errors, redirect issues, and crawl anomalies.
Uses the URL Inspection API to retrieve the live and indexed status of individual URLs, including last crawl date, canonical URL, mobile usability, and rich result eligibility.
Lists and retrieves submitted sitemaps for verified properties, including submission status, last downloaded date, and the number of URLs discovered versus indexed.
Retrieves mobile usability data for verified properties to identify pages with mobile rendering issues that may affect Google's mobile-first indexing evaluation.
Retrieves the list of Search Console properties that the authorized user owns or has access to, allowing them to select which property to analyze without manual input.
Surfaces crawl error data including 404s, soft 404s, server errors, and DNS errors detected by Googlebot during crawling of the verified property.
Full transparency on every data type accessed, why it is accessed, whether it is stored, and what OAuth scope enables it. No data outside the scope of the table below is ever requested or processed.
webmasters.readonlywebmasters.readonlywebmasters.readonlywebmasters.readonlywebmasterswebmasters.readonlyOAuth 2.0OAuth 2.0openid / emailWe request the minimum permissions necessary to deliver the functionality of this tool. The breakdown below is explicit and exhaustive.
The following describes the complete flow from the moment a user accesses the tool to when data is displayed and the session ends.
The user clicks “Connect with Google” and is redirected to Google's OAuth 2.0 authorization screen. At this point, no data has been accessed. The user reviews the requested permissions and either grants or denies access.
Upon user approval, Google redirects back to our application with a short-lived authorization code. This code is exchanged server-side for an access token and, if applicable, a refresh token. Tokens are never exposed to the client browser.
The application calls the Search Console API to retrieve the list of properties the user has access to. The user selects which property to analyze.
Based on the selected property and chosen date range, the application queries the Search Analytics API, Index Coverage API, and URL Inspection API using the user's access token. All requests are made server-side.
API responses are parsed and rendered into the application dashboard. The user sees their own Search Console data — the same data available to them directly inside Google Search Console — presented in our interface.
Search performance data retrieved during the session is not stored in our databases. Each session loads fresh data directly from the Google Search Console API. Cached results, if any, are discarded within 24 hours.
The user can revoke this application's access at any time via their Google Account permissions page and removing Lead Lock Systems LLC from authorized applications. Upon revocation, all stored tokens are immediately invalidated.
This application's use of Google API Services, including data obtained via the Search Console API, strictly adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data is used solely to provide and improve the functionality of this tool.
Data obtained through Google API Services is used only to provide the features described on this page. We do not use this data to develop, improve, or train generalized AI or ML models, serve advertising, or transfer data to third parties except as necessary to operate this application and only with user consent.
All data handling related to this application is governed by the Lead Lock Systems LLC Privacy Policy. As stated in that policy, we do not sell, trade, or monetize user data of any kind. Users may request deletion of any retained data by contacting contact@leadlocksystems.io.
This application requests only the OAuth scopes necessary to deliver its stated functionality. We request webmasters.readonly as the primary scope and webmasters only where sitemap submission functionality is enabled. No additional Google API scopes are requested under any circumstances.
Users may request full deletion of any data associated with their account by contacting contact@leadlocksystems.io. Retained tokens are deleted immediately upon revocation through Google Account settings. Session data is discarded automatically and not retained beyond 24 hours.
Use of this application is subject to the Lead Lock Systems LLC Terms of Service. Users must be the verified owner or authorized delegate of any Search Console property they connect to this application. Unauthorized use of third-party properties is strictly prohibited.
If you have questions about what data this application accesses, how your Search Console data is handled, or how to revoke access, contact Lead Lock Systems LLC directly.
contact@leadlocksystems.io · Lead Lock Systems LLC, 312 W 2nd St, Unit #A9309, Casper, Wyoming 82601, United States