Integrations

Connect Google Search Console

Bring your search demand data into PIN Hacking so keyword work is based on real queries.

Updated August 15, 2026

Connecting Google Search Console lets PIN Hacking compare the queries people already find you with against the keywords your pins target. You connect through Google's secure sign-in, so your login stays with Google.

Before you start: you need a verified Search Console property for your site, and the Google account you connect with needs access to it.

To connect:

  1. Go to Integrations.
  2. Click Connect Search Console.
  3. Sign in with the Google account that has access to the property.
  4. Approve the read only access PIN Hacking requests.
  5. Choose the property you want to use.
  6. You are returned to PIN Hacking and Search Console shows as connected.

Good to know:

  • This is a separate permission from Google Analytics. Google treats the two as different consents, so if you connect both you will see Google's screens twice. That is expected.
  • Read only. We read your query and page data. We never submit, change, or remove anything in Search Console.
  • Domain and URL prefix properties both work. If you have both, pick the one that covers the pages you pin.
  • Not seeing your property? The Google account you connected may not have access to it. Disconnect, then connect again with the right account.
  • "Google hasn't verified this app"? Click Advanced, then Go to PIN Hacking. That warning is normal while an app is in Google's review queue.

Once Search Console is connected, open the Search Console tool to see which queries are worth pinning against.

Was this article helpful?

Recommended for you

Still need help?

Can't find an answer? Send us a note and a human will get back to you.

Contact support