How to connect Semrush to Google Search Console

Connect Search Console in your Semrush tool. Match the retail property and distinguish Google’s observed reports from Semrush’s estimated search data.

Yes, Semrush connects to Google Search Console through individual tools. Start with SEO Dashboard for store performance, or import queries into Position Tracking to monitor selected keywords. Connecting one destination doesn’t configure every other tool.

Choose the Semrush destination

Choose the destination by the data you need. Semrush’s Google integration directory lists the supported connections, including On Page SEO Checker and Organic Traffic Insights.

DestinationWhat the connection doesWhere you start
SEO DashboardDisplays your property’s Google search performance beside Semrush metricsOpen the project’s dashboard and connect Google
Position TrackingImports Search Console queries into a campaign’s tracked keywordsOpen the Keywords window and choose the Search Console import
My ReportsAdds Google search metrics and breakdowns to a reportAdd Search Console widgets in the report builder
Backlink AuditAdds Google’s reported backlinks to the auditOpen the campaign’s Google Search Console integration

These connections have different jobs. Importing keywords doesn’t turn Position Tracking into a Search Console performance report. Site Audit’s Google integration uses Google Analytics, so compare its crawl findings with Search Console indexing reports separately.

Backlink Audit also has a different permission requirement. Semrush specifies Owner or Full user access for that connection. Its project-specific email must receive Full access through Search Console’s user settings. Keep that setup separate from authorising a dashboard to read performance data.

Connect and match the store property

For SEO Dashboard, connect the Google account that can access the store’s Search Console property, then select that property in the connection wizard.

A Search Console Full user can view all property data. Owners can manage other users, while Restricted users have narrower rights. Google’s permissions guide shows the differences. The Backlink Audit Owner-or-Full requirement doesn’t establish a minimum role for every Semrush tool.

  1. Open SEO, then SEO Dashboard, and select your store’s project.
  2. Choose Connect Google, or open the Google Search Console tab and choose Connect.
  3. Sign in to the Google account that has access to the intended property. Review the Google permissions screen before granting access.
  4. Select the matching Search Console property in the wizard. Google Analytics is optional for this connection.
  5. Open the Search Console chart and compare its property and reporting period with the source report in Google.

Semrush’s dashboard guide distinguishes its Google data from Semrush data. A widget being present doesn’t mean it uses the same source as its neighbour.

Check the property’s scope as well as its name. An HTTPS URL-prefix property for the main storefront differs from a subfolder property or another hostname. A Domain property covers a broader set of URLs. Match the scope to the store you intend to analyse.

Incorrect example: selecting a property for the store’s old www hostname because its label looks familiar.

Correct example: selecting the property that covers the project’s actual storefront, then checking a known product-guide URL in the source report.

For Position Tracking, set the campaign’s target location and device first. In its Keywords window, choose Import from, then Google Search Console. Review the proposed queries before adding them to the campaign. Semrush’s Position Tracking setup guide explains targeting and keyword imports. Imported keywords use the campaign’s keyword allowance.

For My Reports, open Integrations in the report builder and add a Google Search Console widget. Choose the account and property in its settings. You can authorise an account there if needed. The My Reports instructions cover query and page tables as well as single metrics. Set the period and country for the report you intend to compare.

Interpret the combined evidence

Use Search Console to establish what Google recorded for your store. Use Semrush’s market estimates to investigate the wider search opportunity.

Google reports clicks and impressions for the selected property. Click-through rate is clicks divided by impressions. Average position summarises the positions of your results across impressions. The Performance report lets you change the query or page grouping and reporting filters.

Semrush’s organic traffic estimate uses ranking positions, search volumes and expected click-through rates. Its keyword database and a Position Tracking campaign also cover different keyword sets. A connected Search Console widget still contains Google data. It doesn’t convert Semrush’s estimates into measured store visits.

Compare matching periods and countries, with the same device and search type where available. Google’s average position across impressions can differ from a tracked ranking for one location and device. A difference alone doesn’t prove an integration failure. Semrush explains the separate roles in its comparison with Google’s reporting tools.

Consider a fictional outdoor retailer investigating “how to choose a hiking backpack”. Semrush suggests demand for the topic, but the retailer first opens Search Console’s Web performance report. They select Australia and a completed four-week period, then filter the exact query.

Suppose that fictional report shows 1,200 impressions and 24 clicks, a 2% click-through rate. The Pages tab identifies an existing backpack guide receiving those impressions. The retailer opens that guide and finds that it explains capacity but gives little help with torso length.

That evidence supports improving the existing guide’s sizing advice before commissioning another general backpack article. Semrush can supply related query ideas for the revision. Neither the estimated demand nor those 24 clicks establish that customers bought a backpack.

Repair or remove the connection

Repair the account or property selection before treating a blank chart as a loss of search traffic.

  • If Semrush reports that no properties match the campaign scope, compare the project domain with the Google property. Check the www version and the signed-in account.
  • If the property is missing, open it directly in Search Console with that account. An owner must grant access if you don’t have it.
  • If Backlink Audit reports a missing account, copy the email from that campaign again. Have a property owner add that exact address with Full access.
  • If authorisation stops working, remove the affected Google connection and reconnect the correct account. Refresh Semrush after completing authorisation.

Semrush’s Search Console connection guide covers scope errors and Backlink Audit’s separate access checks.

To remove access, follow Semrush’s Google account disconnection procedure. Open your Google account’s third-party connections, select the relevant Semrush app and confirm removal. Read the connection’s name and scope before confirming, because other reports can depend on that grant.

Google’s app access instructions distinguish removing access from deleting an account. Revoking Semrush’s access stops that connection from reading Google data. It doesn’t delete the Search Console property or remove your store’s pages. Reconnect only the destination and property you want to use.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup