Choose how your app reads search data
Direct clients call Google or Bing. Hosted clients read gscdump data. Choose the source for your first request.
What data do you need?
| Path | Use it for | Credential | Package |
|---|---|---|---|
| Direct Google and Bing | Live Search Console or Bing Webmaster calls | Google OAuth access token or Bing credential | gscdump |
| Hosted gscdump data | Analytics rows, Reports, saved Indexing Evidence, sitemaps, realtime | gscdump user API key | @gscdump/sdk |
Choose access
Direct Google and Bing
Your server calls the Search Engine API. You manage OAuth, quotas, and saved history. Start by listing your Google Sites. The direct client reference lists imports.
Hosted gscdump data
Your server calls gscdump with an API key. Hosted data can include synced history and Site observations. Start with hosted analytics rows. The hosted HTTP reference names each operation.
Check credentials and ownership
The direct path needs a Google grant for a Site or a Bing credential. The hosted path needs a user API key and authorization for the exact siteId. Keep each credential on a server.
If hosted access fails, check keys and scopes. If a direct Site list is empty, check the Search Console grant and Site permissions.
The read data guides show the next method after your first request.