How to connect Ahrefs to Google Search Console
Add Search Console data to the right Ahrefs project. Check ownership, match the retail property and keep imported observations separate from estimates.
- Published
- Last updated
Yes, you can connect Ahrefs to Google Search Console by linking a Google account that is an Owner of the property. Match the Ahrefs project’s scope to that property, grant Search Console access and inspect the imported report before using its figures.
Check ownership and the intended project
Ahrefs requires Search Console Owner permission for this connection. A Full user can read Google’s performance data, but that role doesn’t meet Ahrefs’ documented ownership requirement. Both verified and delegated owners qualify.
Open the property in Search Console, then check Settings and Users and permissions. If you’re a Full or Restricted user, an existing owner must grant the required role. Google’s permissions guide explains these roles and who can change access.
The Ahrefs project must cover the same website as the Search Console property. Check its protocol and hostname. If the project covers only a path, check that path too. A familiar store name in the dashboard isn’t proof of a match.
For a Domain property, match the Ahrefs target to the domain with both HTTP and HTTPS and subdomains included. For an HTTPS URL-prefix property, use the matching HTTPS domain or prefix scope. A project covering all subdomains can import incomplete data from a narrower URL-prefix property.
Incorrect example: a retailer connects a property for its HTTPS storefront to an Ahrefs project covering every protocol and subdomain, then treats the result as complete.
Correct example: the retailer matches the project to the HTTPS storefront property, or uses a Domain property that covers the broader project.
Ahrefs also supports ownership verification through DNS or an HTML file or tag. Those methods prove control of a site. They don’t themselves authorise Google to supply Search Console performance. The ownership verification instructions distinguish the methods. Site Audit’s crawl results remain a separate source of evidence from Google’s search performance.
Connect the account and property
Link the owner’s Google account from the Ahrefs dashboard, then check the project that receives the data.
- Open your Ahrefs dashboard and choose the GSC performance tab. Here, GSC means Google Search Console.
- Select Link Google Account if the account isn’t connected. Choose the Google account that owns the intended store property.
- Read the consent screen and allow the requested permissions. The required access includes viewing Search Console data for your verified sites.
- Return to the dashboard and select the matching project with Search Console connected. Open its GSC reports.
- Check the project target and available reporting range. Set the country and device for the store analysis you intend to perform.
Ahrefs’ performance integration guide says the initial import includes up to 16 months of available data. It starts storing data while the account remains connected, so retained history can eventually exceed that range.
Open a completed reporting period in both Ahrefs and Search Console. Compare the same property and filters, then inspect a known page. An authorised account login proves you granted access. The matching project and its populated report establish whether you’re looking at the intended store data.
The consent grants Ahrefs access to Search Console data. Treat it as a data-sharing decision, even when your immediate goal is project verification. Ahrefs says it plans to use collected Search Console data to improve keyword search-volume estimates without identifying your website. That doesn’t make its public traffic estimate a copy of your property’s clicks.
Read and troubleshoot the imported report
Read imported Search Console clicks and impressions as Google’s observations. Read Ahrefs’ Organic traffic metric as an estimate based on its keyword data.
Ahrefs calculates Organic traffic from ranking positions and estimated search volumes, with a click-through-rate model. It sums the estimated traffic across keywords. Different keyword coverage and modelling can produce different totals from Search Console.
Google’s Performance report groups observations by query or page and supports country and device filters. Keep those filters consistent when reconciling an imported view. Click-through rate is clicks divided by impressions. A count of impressions alone doesn’t establish that shoppers reached your site.
Consider a fictional homewares retailer investigating “how to choose a dining rug”. In a completed four-week period, its imported query report shows 800 impressions and 16 clicks from Australia. That is a 2% click-through rate.
The retailer checks the corresponding Search Console query and opens the page receiving those impressions. Its dining-rug guide explains materials but lacks advice about allowing room for chairs. That gives the retailer a specific improvement to make in the existing guide. An Ahrefs traffic estimate can help compare broader opportunities, but it doesn’t turn those 16 observed clicks into orders.
For verification failures, check the signed-in Google account and Owner role first. Then inspect consent. Ahrefs’ verification troubleshooting guide says all permission checkboxes must be selected. If access was omitted, remove the affected integration and repeat authorisation.
If verification succeeds but reports are empty, first check that the source property has data. Then compare the Ahrefs target with the property’s scope. A Domain property and a www-only project can produce dashboard totals while leaving Rank Tracker’s GSC page and keyword reports unavailable.
Ahrefs’ data troubleshooting guide also says imported data can lag Google by a few weeks. It directs delays of several months to support. Compare a completed period available in both systems before diagnosing missing traffic.
For a lost-access error, Ahrefs’ reconnection instructions direct you to Account integrations. Remove the affected Google account, then add it again from the project and grant the required permissions.
To end the connection, remove that Google account from Ahrefs’ integrations. You can also revoke Ahrefs’ access through Google’s third-party app settings. Review which projects depend on the account before removing it. Disconnecting stops further authorised access. It doesn’t delete the Search Console property or your store’s published guides.
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.