Connecting Search Console to DeskSEO: verification, access and position per query

Search Console holds the only first-hand data about how your site performs in Google: which queries show your pages, how many clicks they get, and at what position. DeskSEO connects to it so that this data sits next to your technical checks, is stored day by day, and shows average position per query over time. This guide walks through the connection and explains what you see afterwards. The short illustrated version is on the Search Console connection page.

Before you start

• You need a DeskSEO account with the domain added under Your sites; see getting started.
• You need to be an owner of the site's Search Console property, or ask an owner to do step 2. Only owners can add users.
• A Domain property is best, because it covers every subdomain and protocol; see Domain vs URL-prefix properties.

Step 1: verify that you manage the site

On the site's page in DeskSEO, the Verify section gives you a unique code and two ways to use it:

Method	Where	Good for
Meta tag	Paste into the <head> of the home page. On WordPress, a header-code plugin or the "other verification code" field of an SEO plugin works	Anyone who can edit the site template
TXT record	Add at your DNS provider on the root domain (name @), value as shown	Anyone with DNS access; survives redesigns

Press Check verification. DeskSEO reads the tag or record and marks the site as verified. Leave the tag or record in place afterwards, so the site can be verified again later if needed.

Why this step exists: Search Console data is private, and DeskSEO uses one service account for many customers. Verification ensures that only people who manage a site can see that site's data through DeskSEO. If someone else has already verified the same domain in their own DeskSEO account, you can still verify it if you manage the site too.

Step 2: add the DeskSEO service account in Search Console

1. Open Search Console with the Google account that owns the property, and choose the right property.
2. Go to Settings → Users and permissions → Add user.
3. Paste the service account email shown on your site's page in DeskSEO.
4. Choose the permission Restricted and press Add.

Restricted means read-only: the service account can read performance data but cannot change settings, submit sitemaps or request indexing. No Google password changes hands. If you do not see "Users and permissions", you are not an owner of the property; ask the owner to add the email.

Step 3: check access and fetch data

Back on the site page in DeskSEO, press Check access and fetch data in the Search Console section. DeskSEO looks for the matching property in this order: the Domain property, then the https URL-prefix property without www, then with www. It then fetches daily totals for the last 16 months and query and page detail for the last 90 days straight away, and adds new data every morning. The last five days are fetched again each morning, because Google revises recent days as processing completes.

What you see

• Totals for clicks, impressions, click-through rate and average position, with a choice of date range.
• A chart of clicks per day. Click a day to see the queries for that day.
• Top queries and top pages, each linking to full, sortable, filterable lists.
• One query or one page over time: clicks, impressions and average position day by day, with a chart where position 1 is at the top. Points exist only on days Google showed the result.

Average position in the lists is weighted by impressions, the same way Search Console calculates it. The average position guide explains why a single number can mislead, and why day-by-day positions per query are more useful than a site-wide average.

Why position per query, day by day

Search Console's own interface shows average position for a query over the date range you pick. That single number hides a lot: a query can sit at position 4 for three weeks and at position 14 for one, and the average reads as 6.5. Seeing the position for each day makes the shape visible. A steady climb after a content update, a sudden drop on a specific date, or a page that alternates between two positions every few days (often a sign that two of your pages are competing; see keyword cannibalization) are all obvious in a daily chart and invisible in an average. That is the main reason to look at Search Console data in DeskSEO rather than only in Google's interface.

A worked example

A hypothetical bike repair shop connects Search Console and opens the query "e-bike battery repair". The daily chart shows the query hovering around position 9 for two months, then rising to around 4 within a week. The date matches the day the shop published a rewritten service page with prices and turnaround times. A week later, the page list shows that same page now has the highest click-through rate on the site. Meanwhile, the query "bike service near me" shows a single-day drop to position 30 that recovers the next day; the technical check history shows a server outage that morning. Neither story would have been readable from a 28-day average.

Plan limits

Plan	History shown	Rows
Free	Last 28 days	Top 50 queries
Starter, Pro, Agency	Up to 16 months	Up to 1,000 queries and 1,000 pages per site

DeskSEO keeps about 16 months of data per site, the same window as Search Console itself; for longer history, use exports or Google's bulk export. The general limits of Search Console data, such as anonymised queries, still apply; see Search Console data limits.

Several sites, several properties

Each site in DeskSEO connects to its own property. If you manage many sites, the same service account email can be added to each of their properties; the exact email to use is always shown on each site's page, so copy it from there rather than from memory. For agencies, it is usually cleanest for the client, as property owner, to add the service account, since the client remains in control of who can read their data. The agencies guide covers managing many client sites in one account.

Common problems

Message or symptom	Cause	Fix
Verification fails	Tag not in the served HTML (caching, wrong template) or TXT record not yet propagated	View the page source of the home page; wait for DNS and try again
No access yet	Service account not added, added to a different property, or email mistyped	Check Users and permissions on the right property; paste the email again
Numbers lower than in Search Console	DeskSEO found a URL-prefix property that excludes some hosts	Create a Domain property, add the service account to it, and fetch again
Last days look low	Google's normal data delay	Wait; DeskSEO re-fetches recent days

Removing access

To disconnect Search Console only, remove the DeskSEO service account from Users and permissions in Search Console; new data stops arriving, and you can reconnect later by adding it again. To remove the site from DeskSEO altogether, use Stop tracking this site at the bottom of the site page, which also deletes the Search Console data DeskSEO fetched for it. If you want fresh numbers before the next morning update, Fetch new data now on the same page pulls the latest available days.

Using the data well

• Pick a handful of important queries and open their day-by-day view once a week. Steady climbs, sudden drops and alternating pages are all easy to spot there.
• When a technical check flags a problem, look at the same dates in the clicks chart to see whether traffic was affected.
• Use the page list, sorted by impressions, to find pages that are seen often but clicked rarely; their titles and descriptions may need work. See titles and meta descriptions.