How to Connect Google Search Console

Why connect GSC

Google Search Console (GSC) is a free service offered by Google that helps you monitor and maintain your site's presence in Google Search results. By connecting your Google Search Console account to LemRank, you integrate real click and impression data directly into your keyword tracking. This integration provides a more complete view of your site's organic performance by showing how your tracked keywords are performing in Google Search.

Without a GSC connection, LemRank provides data collected through its proprietary rank tracking system. With GSC connected, you can overlay Google's own performance data for clicks, impressions, and average position onto your keyword cards. This allows for a deeper analysis of keyword performance, helping you identify opportunities for optimization and assess the real-world impact of your SEO efforts.

The 5-step connect flow

Connecting GSC to LemRank typically takes less than 5 minutes. Follow these steps to establish the connection:

1. Navigate to Integrations: From your LemRank dashboard, click on your profile icon in the top right corner. From the dropdown menu, select "Settings". On the settings page, locate and click on the "Integrations" tab.
2. Initiate GSC Connection: Within the Integrations section, find the Google Search Console integration. Click the "Connect" button associated with it. This will initiate the connection process.
3. Authenticate with Google: A new window or tab will open, prompting you to log in to your Google account. Choose the Google account that has access to your website's Google Search Console properties.
4. Grant Permissions: After logging in, Google will ask you to grant LemRank permission to view your Google Search Console data. LemRank requires permission to "View your Google Search Console data" to retrieve the necessary performance metrics. It's important to understand that LemRank only reads this data and does not modify any settings or data within your Google Search Console account. Click "Allow" to proceed.
5. Select Properties: Once permissions are granted, you will be redirected back to LemRank. A list of your Google Search Console properties associated with the connected Google account will appear. Select the specific properties you wish to integrate with your LemRank projects. If you have multiple websites or subdomains tracked in GSC, you can select all relevant ones. Click "Save" to complete the connection.

LemRank will begin importing data from the selected GSC properties. Initial data syncs may take some time depending on the volume of data.

What data LemRank pulls (and what it doesn't)

When you connect Google Search Console, LemRank pulls specific data points to enhance your keyword analysis:

• Clicks: The number of times users clicked on your site's listing in Google search results for a given query.
• Impressions: The number of times your site's listing appeared in Google search results for a given query, regardless of whether it was clicked.
• Average Position: The average ranking of your site's listing for a given query in Google search results. This metric helps you understand your visibility for specific keywords.
• Query-to-URL Mapping: LemRank correlates specific search queries with the landing pages on your site that received clicks and impressions. This allows you to see which URLs are performing for which keywords.

LemRank does not pull any sensitive or personally identifiable information from your Google Search Console account. It also does not pull data related to sitemaps, core web vitals, manual actions, or security issues. The integration is solely focused on performance data relevant to keyword tracking and analysis.

The data pulled from GSC is subject to Google's data availability and processing times. LemRank refreshes this data daily, with a typical 2-day lag, meaning the most recent two days of data might not yet be fully reflected, mirroring Google's own reporting latency.

Multi-property connections

LemRank supports connecting multiple Google Search Console properties to your account. This is particularly useful if you manage several websites, subdomains, or different versions of the same website (e.g., HTTP vs. HTTPS, www vs. non-www).

During the connection flow (Step 5 above), after granting permissions, you will see a list of all GSC properties accessible by the Google account you authenticated with. You can select multiple properties from this list to connect them to different LemRank projects or to consolidate data for a single project if it spans multiple GSC properties (e.g., a country-specific subdomain and the main domain).

For each LemRank project, you can specify which connected GSC property provides the relevant data. This ensures that the correct performance metrics are associated with the correct website within LemRank.

Troubleshooting connection failures

If you encounter issues during the GSC connection process, consider the following troubleshooting steps:

• Incorrect Google Account: Ensure you are authenticating with the Google account that has verified ownership or full user access to the Google Search Console property you intend to connect. If you manage multiple Google accounts, double-check which one you are logged into.
• Insufficient Permissions: Verify that you have granted LemRank the necessary permissions to "View your Google Search Console data." If you previously denied these permissions or only granted partial access, you may need to revoke LemRank's access in your Google account settings and then re-initiate the connection process.
  • To revoke access: Go to your Google Account > Security > Third-party apps with account access. Find LemRank and remove its access. Then, try connecting again from LemRank.
• Browser Issues: Try clearing your browser's cache and cookies, or attempt the connection in an incognito/private browsing window. Browser extensions can sometimes interfere with authentication flows.
• Network Connectivity: Ensure you have a stable internet connection.
• Google Search Console Property Verification: Confirm that the Google Search Console property itself is properly verified and active within Google Search Console. If the property is not verified or has issues within GSC, LemRank will not be able to pull data from it.
• Temporary Google Issues: Occasionally, Google's APIs may experience temporary outages or delays. If you've tried all other steps, wait a few hours and try again.

If the problem persists after trying these steps, contact LemRank support with details of the issue and any error messages you received.

What to do if data lags

GSC data in LemRank is updated daily, but it typically has a 2-day lag compared to real-time. This means that data from today and yesterday might not yet be fully available in LemRank, mirroring Google Search Console's own latency in reporting. For example, if you are viewing data on October 5th, the most recent GSC data available will likely be from October 3rd.

This lag is inherent to the Google Search Console API and is not a limitation of LemRank. It is important to factor this into your analysis, especially when looking at very recent performance trends.

What you should do:

• Patience is Key: Understand that recent data will appear after the 2-day lag. There is no manual action required on your part to expedite this. LemRank automatically pulls the latest available data daily.
• Focus on Trends: When analyzing GSC data for recent periods, focus on broader trends over several days rather than day-to-day fluctuations, as the most recent data points are still being compiled by Google.
• Cross-Reference (if necessary): If you need absolute up-to-the-minute data for a specific day, you will need to log directly into Google Search Console. However, for most SEO analysis within LemRank, the 2-day lag in GSC data is acceptable and provides sufficient context.
• Verify Connection Status: Ensure your GSC connection is still active and healthy in LemRank's Integrations settings. An 'Error' status would indicate a different problem requiring troubleshooting.

LemRank continually monitors its integrations to ensure data is pulled as efficiently and promptly as possible based on the source API's capabilities.

Related

• How to improve organic CTR