Skip to main content

​
Executive Overview (DBX v4.1 Release)

Starting with YPYM DBX v4.1, integrating Google Search Console (GSC) is completely frictionless. You no longer need to navigate Google Cloud Console, enable APIs, or generate complex RSA private key files. By delegating property access to the official YPYM DBX Service Account, your domain immediately begins ingesting verified first-party search telemetry alongside organic SERP positions and AI Overview citations:
  • Organic Search Clicks & Impressions (Yesterday, 3-day, 7-day, and 30-day aggregates).
  • Average Organic Click-Through Rate (CTR) across all tracked keywords.
  • Average Google Search Console Position mapped directly against crawled SERP rankings.
  • Zero Extra Crawl Cost: GSC telemetry executes via official Google APIs at $0 DataForSEO expenditure.
This is the standard, 2-minute setup for all YPYM DBX users and enterprise clients.

​
Step 1: Invite YPYM DBX in Google Search Console

  1. Log in to Google Search Console.
  2. From the top-left property selector, choose the property corresponding to your website (e.g. sc-domain:ypym.app or https://ypym.app/).
  3. In the left navigation menu, scroll down and click Settings.
  4. In the Settings dashboard, click Users and permissions.
  5. Click the blue Add user button in the top-right corner.
  6. In the dialog, enter the official YPYM DBX Service Account email:
  7. Set the Permission dropdown to Full (or Owner if you manage domain-level DNS properties).
  8. Click Add.
[!TIP] Why Full Permissions? Google Search Console API requires Full permissions to list performance search queries and query aggregate impressions programmatically across your property. YPYM DBX accesses the property strictly in read-only mode to pull analytics telemetry.

​
Step 2: Configure the Property in YPYM DBX

  1. Log in to your YPYM DBX dashboard at https://dbx.ypym.app/.
  2. Select your domain from the Domains dashboard.
  3. In the domain action toolbar, click the Settings (Gear/Wrench icon) to open Domain Settings.
  4. Switch to the Search Console tab.
  5. In the Property URL / Identifier field, enter your exact Google Search Console property name:
    • For Domain Properties (DNS-verified):
    • For URL-Prefix Properties (HTTP/HTTPS):
      (Ensure the trailing slash matches your GSC property definition).
  6. Toggle Enable Search Console Synchronization to ON.
  7. Click Save Settings.

​
Step 3: Verification & Ingestion

Once saved, YPYM DBX performs an automated handshake with the Google Search Console API:
  1. Navigate to your domain’s SERP + AIO tab.
  2. Ensure the Search Console column is enabled in the table header options.
  3. Within minutes, real-time Google search telemetry (Clicks, Impressions, CTR, Average Position) will populate directly next to each tracked keyword.
  4. Open the Search Console Insight view (/domain/console/[slug]) to inspect query trends, landing page distributions, and country device splits.

​
2. Advanced Method: Custom Enterprise Google Cloud Credentials

For corporations that mandate private infrastructure governance where third-party service account delegation is restricted by corporate security policy, YPYM DBX supports custom private key integration.

​
2.1 Create Custom Service Account in Google Cloud

  1. Open Google Cloud Console.
  2. Create or select your organization project (e.g., company-search-telemetry).
  3. Enable the Google Search Console API (Search Analytics API v1) under APIs & Services → Library.
  4. Under IAM & Admin → Service Accounts, create a service account and generate a new JSON key.
  5. Open the downloaded .json file and copy the client_email and private_key fields.

​
2.2 Add Custom Key in YPYM DBX

  1. In DBX Domain Settings → Search Console, select Use Custom Service Account.
  2. Paste your custom service account email.
  3. Paste the entire private key block:
  4. Click Update Settings. The key is encrypted with AES-256 into your tenant partition.
[!NOTE] Key Masking Guarantee: For security, YPYM DBX masks the private key (••••••••) upon subsequent visits to prevent credential snooping.

​
3. Frequently Asked Questions

Search Console data is refreshed automatically during the daily scheduled crawling cycle (11:00 AM WIB), as well as on-demand whenever you trigger manual domain refreshes.
No. Google Search Console sync uses direct Google Cloud API communication and incurs $0 API cost with zero consumption of DataForSEO credits.
Google Search Console data inherently runs on a 24 to 48-hour data lag from Google’s reporting pipeline. If a keyword is brand-new or was added today, Google Search Console will typically reflect impressions once Google processes the trailing aggregate.