Connect Google Search Console

Why Connect Google Search Console

Google Search Console (GSC) is the single most important SEO tool you can use. It tells you exactly how Google sees your site: which pages are indexed, what queries people search to find you, your click-through rate, your ranking position, and any problems Google finds with your pages.

Pixelesq integrates directly with GSC so you never have to leave the dashboard. You see search performance, indexing status, and URL inspection results right next to your page content. When something ranks, you know. When something drops, you know why.

GSC is free and available on every Pixelesq plan. The only prerequisite is that you have at least one custom domain connected.

Prerequisite: Connect a Custom Domain

Before connecting GSC, you must have at least one custom domain connected and verified in Pixelesq. The integration is blocked otherwise. This is because GSC tracks metrics per domain, and your default Pixelesq subdomain is not a domain you own, so Google cannot grant you access to its search data.

If you have not connected a domain yet, see our guide on connecting a custom domain first. Once your domain shows a green Connected badge, come back here.

Step 1: Start the Connection Flow

In your Pixelesq dashboard, click Settings in the sidebar, then select the App Integrations tab. Find the Google Search Console card and click Connect.

You are redirected to Google's OAuth authorization page. Sign in with the Google account that owns or has access to your site's GSC property. You must have at least Full or Restricted permission on the property in GSC for the integration to work. Read-only permission is not enough because Pixelesq also needs to submit sitemaps.

[Screenshot: GSC integration card with Connect button]

Step 2: Authorize the Requested Scopes

Google asks you to authorize three scopes:

View and manage Search Console data (webmasters, read and write)
View Search Console data (webmasters, read-only)
Verify site ownership (siteverification)

Click Allow. You are redirected back to Pixelesq, where the integration now shows as active.

If the OAuth flow fails or you deny a scope, the integration cannot function. All three scopes are required.

Step 3: Pixelesq Automatically Sets Things Up

Once connected, Pixelesq automatically:

Verifies your site in GSC. If your site was not already verified in the connected Google account, Pixelesq handles verification through the OAuth flow.
Submits your sitemap. Pixelesq sends your yourbrand.com/sitemap.xml URL to GSC so Google knows about all your pages.
Starts syncing search data. Pixelesq begins pulling search performance data, page indexing statuses, and URL inspection results for your domain.

You do not need to do any of this manually. Just connect, and Pixelesq handles the rest.

Step 4: Check the Search Performance Panel

In your Pixelesq dashboard, click Analytics in the sidebar. The analytics page now includes a Google Search Console section with search performance data.

The panel shows:

Total Clicks - how many times people clicked your site in Google results
Total Impressions - how many times your pages appeared in search results
Average CTR - click-through rate (clicks divided by impressions)
Average Position - your average ranking position across all queries

You can view the data across three time periods: last 7 days, last 28 days, or last 90 days. The panel also breaks down metrics by query, page, device, and country.

[Screenshot: GSC performance panel with clicks, impressions, CTR, and position]

What Each Metric Actually Means

Clicks measure actual traffic from Google. This is the bottom-line metric.
Impressions measure how often Google thinks your page is relevant enough to show. Rising impressions with flat clicks usually means your ranking is improving but your title/description is not compelling enough to earn the click.
CTR tells you how compelling your search result is. For position 1, CTR is typically 20-40%. For position 10, it is 2-3%. If your CTR is dramatically below average for your position, your meta title or description probably needs improvement.
Position is your average rank across all queries where your page showed. Position 1 is the very first result. Position 100 is the bottom of page 10. Google shows 10 results per page.

Step 5: Use the URL Inspector

The URL Inspector lets you check any specific URL to see exactly how Google sees it. In the analytics page, find the URL Inspection input, paste a full URL from your site (e.g., https://yourbrand.com/about), and click Inspect.

You get a detailed report:

Verdict: PASS (indexed and fine), NEUTRAL (some issues), or FAIL (serious problems)
Coverage State: whether the page is indexed, excluded, or has errors
Indexing State: the detailed status
Last Crawled: when Google last visited the page
Robots.txt State: whether robots.txt is allowing or blocking the URL
Google Canonical: which URL Google treats as the canonical version
Rich Results Types: any structured data schemas Google detected

Use the URL Inspector to debug why a specific page is not appearing in search results. The verdict and coverage state usually tell you exactly what is wrong.

[Screenshot: URL Inspector with a URL entered and detailed results]

Step 6: Check Page Indexing Status

Every Pixelesq page has a GSC status panel in its SEO view (on the Web tab). This panel shows:

Current indexing verdict for this specific page
Last crawl time
Core Web Vitals score
Any rich results detected

If a page shows a bad verdict (FAIL or errors), the panel explains why. Common issues: the page is noindexed, robots.txt is blocking it, or Google found duplicate content.

There is also a Refresh Status button. Clicking it asks GSC to re-inspect the page right now. Use this after fixing an indexing issue to see if Google has picked up the change.

Understanding the 3-Day Data Delay

GSC data is always about 3 days old. This is not a Pixelesq limitation. It is how Google reports search data. Google aggregates queries for privacy reasons and publishes them to GSC on a ~72-hour delay.

If you publish a new page today, expect:

Indexing status updates within 1-7 days (varies by site authority)
Search performance data to start showing 3-5 days after the first impressions
Query-level data to stabilize after 14 days (short-term data is volatile)

Do not panic if a new page shows zero clicks 48 hours after publishing. That is normal. Check again after a week.

Pro Tips

Check GSC weekly, not daily. Daily fluctuations in search data are noise. Weekly trends are signal. Pick a weekly review cadence and stick to it.
Focus on queries with rising impressions but low CTR. These are pages Google thinks you could rank for, but your title and description are not compelling enough to earn the click. Rewriting them is the highest-leverage SEO work you can do.
Use URL Inspection after every significant content change. If you rewrite a page, use the URL Inspector and click Request Indexing. This tells Google to re-crawl the page within a day or two instead of waiting weeks.
Pay attention to the Coverage report in GSC itself. Pixelesq shows the key data, but GSC's own interface has a Coverage report that lists every indexing issue across your entire site. Check it monthly.
Verify that GSC sees the canonical version you expect. The URL Inspector's Google Canonical field tells you which URL Google treats as canonical. If it is different from what you expect, you may have a canonical tag issue or duplicate content problem.

Troubleshooting

GSC says "No custom domain" when I try to connect: Pixelesq requires at least one verified custom domain. Go to Settings > Domain and connect your domain first. Once it shows a green Connected badge, come back to App Integrations and try again.

OAuth redirects me back with an error: Most common cause is insufficient permission on the GSC property. Make sure the Google account you used has Full or Restricted permission on the property in GSC itself. Users with Read-only permission cannot authorize the scopes Pixelesq needs.

Connected but no data showing: Data takes 24-48 hours to start flowing after the initial connection. If you just connected, wait a day. Also confirm that your site has actually appeared in Google search results at least once; if it has zero impressions, the panel will be empty because there is literally nothing to show.

Search performance numbers are way lower than expected: GSC only counts clicks where Google was the referrer. Traffic from other search engines, direct visits, and social shares are not counted here. Check Pixelesq's built-in analytics for a full traffic picture. GSC is a subset showing only Google organic.

"Needs reconnection" badge appears: Google OAuth tokens expire periodically. If Pixelesq shows "Needs reconnection" on the GSC integration card, click it to re-authorize. You do not lose any historical data during reconnection.

My page shows as not indexed even though it has been live for weeks: Common causes: the page is noindexed, robots.txt is blocking it, it is a duplicate of another page, or Google just has not gotten to it yet. Use URL Inspection to see the specific reason. If it is a new site with no authority, indexing can take 2-4 weeks.

FAQ

Is Google Search Console free to use with Pixelesq?

Yes. GSC itself is free from Google. The Pixelesq integration is also available on every plan, including Free. There are no usage limits beyond Google's own API limits, which are high enough that you will never hit them as a normal user.

Does connecting GSC to Pixelesq give Pixelesq access to my entire Google account?

No. The OAuth scopes requested are scoped specifically to Google Search Console (webmasters and siteverification). Pixelesq cannot access your Gmail, Drive, Analytics, or any other Google service. You can revoke access at any time in your Google Account permissions page.

Can I connect multiple GSC properties to a single Pixelesq project?

Pixelesq's GSC integration tracks one property per project. If you have multiple custom domains in the same project, Pixelesq uses the primary verified domain as the tracked property. For tracking multiple properties separately, use separate Pixelesq projects.

How is this different from just using GSC directly on google.com?

Functionally, you can do most things directly in GSC. The value of the Pixelesq integration is context: you see search data next to the specific Pixelesq page it relates to, so you can edit the page and see indexing status in the same workflow. You save time switching between tabs and can act on data faster.

Will Pixelesq start syncing historical GSC data after I connect?

Pixelesq fetches the last 90 days of search performance data on connection. Anything older than 90 days is not pulled, even if GSC has it. Google Search Console itself keeps 16 months of data in its own interface, so you can always view the full history in GSC if needed.

Can I export GSC data from Pixelesq?

Direct CSV export from the Pixelesq GSC panel is not currently supported. For data export, use GSC's native export feature at search.google.com/search-console. Your GSC data is always available through Google's own interface, regardless of the Pixelesq integration.

How to Connect Google Search Console and Monitor Performance