Google Search Console appears in the Data Sources tab on https://lengrowth.com/integrations. Like the other source cards, it only attaches to a selected company workspace, so the page asks you to choose a company before connection continues. If there is no company yet, LenGrowth asks you to create one first. That is not a special Search Console rule; it is the normal integration pattern for all company-linked sources in the app.

LenGrowth treats Search Console as a source of search demand, visibility, and page or query opportunity signals. The integration metadata in the backend describes it as search demand, visibility, and page/query opportunity signals, and the usage copy says it feeds founder reporting search sections and search-backed recommendation and task evidence. That means the integration is part of the reporting and recommendation system rather than a separate SEO dashboard. The product uses the source to add confidence and context to the same workflow that already handles reporting, tasks, and recommendations.

The user-facing setup flow is OAuth-based. On the integrations page the card action uses the same Google sign-in pattern as Google Analytics, so the visible button label is Sign in with Google. After authorization, LenGrowth shows a list of verified sites and asks you to pick one. The selection label on the page is Selected site. The code maps each site to the site URL and permission level, so the user is choosing a specific verified property rather than a broad account. That distinction matters because Search Console data is property-specific and LenGrowth stores the chosen site for a company.

Before connecting, make sure the website is already verified in Google Search Console and that the Google account has the right access. The backend guidance says you need Owner or Full permissions for the site property. The setup text also reminds the user that the site should already be verified in search.google.com/search-console. If the site is not verified, the connection flow can still reach the Google login step, but it cannot complete the site selection in a meaningful way because there is no valid property to attach.

The integration page gives two clues about what happens after setup. First, the card displays the connected site and sync summary when the source is healthy. Second, the page uses the connected source in the reporting workspace instead of in a dedicated Search Console screen. That means Search Console is not meant to become a separate product inside LenGrowth. It fills in the reporting and recommendation layers that already exist. The backend metadata also says the connection unlocks SEO visibility and keyword ranking data in the report and helps identify low-hanging-fruit search opportunities.

There is a second reason Search Console matters here. It supports evidence for recommendations and tasks. In LenGrowth, a recommendation is more useful when it can cite actual search behavior or visibility data instead of only using generic heuristics. That is why the backend says the source is used in search-backed recommendation and task evidence. If the site is disconnected, the app should avoid pretending it has live Search Console information. If the source is connected, then the report can use it to explain why a search-related recommendation exists.

The actual backend routes follow the same structure you see in the interface. Search Console authorization begins at /integrations/gsc/auth, the site list is retrieved from /integrations/gsc/sites, the selected property is stored through /integrations/gsc/select-site, the connection status is checked with /integrations/gsc, and the source can be disconnected through the same base route. Those routes are internal implementation details, but they confirm that the user flow on the integrations page is real and company-specific.

If setup fails, the first thing to check is whether the site property is actually verified and whether the Google account used for authorization matches the account that has Search Console access. That is the most common mismatch. Another issue is selecting the wrong property when multiple sites are visible. Because LenGrowth stores the chosen site URL, the connection should match the exact website the company wants to measure. If the site is a different domain, or if the user only has partial access, the property list may not contain the expected option.

Once connected, the practical result is straightforward. Founder reporting can use live search demand and visibility context, and SEO-related recommendations can reference the connected source instead of staying generic. If the site changes, the company can disconnect and reconnect with the correct Search Console property. The integrations page is designed for that workflow, and the selected site label makes it clear which property is currently driving the connection.

The selected site label is also the final confirmation that the Google account, the verified property, and the company workspace all line up before the user leaves the modal.

Related pages: