Google logo

Get Google Search Results (Apify)

Google → Get Google Search Results (Apify)

POST/v1/google-search-scraper-sync
texau__google-search-scraper-syncenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/google-search-scraper-sync
{
  "query": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "search_query_term": "sample",
    "search_query_url": "https://acme.com",
    "organic_result_title": "sample",
    "organic_result_url": "https://acme.com",
    "organic_result_displayed_url": "https://acme.com",
    "organic_result_description": "sample"
  }
}

Run the Apify Google Search Scraper synchronously to retrieve search engine results pages (SERPs), including organic results, paid ads, and AI overviews.

Install

Add get google search results (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-sync

When to use this.

The "Get Google Search Results (Apify)" action, also known as google-search-scraper-sync, allows users to run a synchronous query on Google to retrieve comprehensive search engine results pages (SERPs). By inputting specific search terms through the 'queries' parameter, users can extract valuable data, including organic results, paid advertisements, and AI-generated overviews. The output fields provide essential information such as the search query term, associated URLs, titles of organic results, displayed URLs, and detailed descriptions. This action is particularly useful for digital marketers, SEO professionals, and researchers looking to analyze search trends, optimize content strategies, or monitor competitor performance. Categorized under enrichment, this API action delivers structured text and URL data, making it an essential tool for enhancing search-related insights.

Try it

Run a sample request.

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

Get Google Search Results (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
  • search_query_term
    Search Query Term
    string
  • search_query_url
    Search Query Url
    nullablestring
  • organic_result_title
    Organic Result Title
    text
  • organic_result_url
    Organic Result Url
    text
  • organic_result_displayed_url
    Organic Result Displayed Url
    nullabletext
  • organic_result_description
    Organic Result Description
    text

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/google-search-scraper-sync
curl -X POST 'https://v3-api.texau.com/api/v1/google-search-scraper-sync' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"query":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "search_query_term": "sample",
    "search_query_url": "https://acme.com",
    "organic_result_title": "sample",
    "organic_result_url": "https://acme.com",
    "organic_result_displayed_url": "https://acme.com",
    "organic_result_description": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Get Google Search Results (Apify)→Get Google Top Search Result (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 search results (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 Search Results (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 Search Results (Apify) in 60 seconds.

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

Start free →Read the API docs