Google logo

Get Google Top Search Result (Apify)

Google → Get Google Top Search Result (Apify)

POST/v1/google-search-scraper-top-result
texau__google-search-scraper-top-resultenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/google-search-scraper-top-result
{
  "queries": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "searchQueryTerm": "sample",
    "searchQueryUrl": "https://acme.com",
    "organicResultsTitles": "sample",
    "organicResultsUrls": "https://acme.com",
    "organicResultsDisplayedUrls": "https://acme.com",
    "organicResultsDescriptions": "sample"
  }
}

Get Google Top Search Result

Install

Add get google top search result (apify) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__google-search-scraper-top-result

When to use this.

The "Get Google Top Search Result (Apify)" action enables users to efficiently retrieve the top organic search result from Google based on specified search queries. By inputting one or more search terms through the "queries" parameter, users can obtain valuable insights into search engine results. The action outputs essential data fields, including the search query term, the corresponding search query URL, and detailed information about the top organic result, such as its title, URL, displayed URL, and description. This action falls under the enrichment category and is particularly useful for SEO professionals, marketers, and content creators looking to analyze search trends, optimize web content, or gather competitive intelligence. With data types including text and URL, this API action streamlines the process of acquiring relevant search result information for various applications.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Get Google Top Search Result (Apify)

Try it

The search term(s) to query on Google.

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • searchQueryTerm
    Search Query Term
    string
  • searchQueryUrl
    Search Query URL
    string
  • organicResultsTitles
    Result Title
    text
  • organicResultsUrls
    Result URL
    text
  • organicResultsDisplayedUrls
    Result Displayed URL
    text
  • organicResultsDescriptions
    Result Description
    text

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/google-search-scraper-top-result. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/google-search-scraper-top-result
curl -X POST 'https://v3-api.texau.com/api/v1/google-search-scraper-top-result' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"queries":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "searchQueryTerm": "sample",
    "searchQueryUrl": "https://acme.com",
    "organicResultsTitles": "sample",
    "organicResultsUrls": "https://acme.com",
    "organicResultsDisplayedUrls": "https://acme.com",
    "organicResultsDescriptions": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Get Google Top Search Result (Apify)→Get Google Search Results (Apify)→Get Google Maps Places Using Search Url (Apify)

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → get google top search result (apify) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Get Google Top Search Result (Apify)Google action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit30 / min
  • Per-day limit5,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Light tier

Pricing tier on /pricing. Per-action credit cost is private.

Related

More Google actions.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__google-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Get Google Top Search Result (Apify) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs