FetchSERP

Interact with the FetchSERP API
Join our community

Actions20

Overview

This node integrates with the FetchSERP API to perform various web data retrieval operations, including scraping webpages that require JavaScript execution and proxy usage. Specifically, for the "Scrape Webpage JS & Proxy" operation, it sends a POST request to fetch webpage content rendered with JavaScript through a proxy, which is useful when dealing with dynamic websites or sites that block direct scraping.

Common scenarios where this node is beneficial include:

  • Extracting content from modern websites that rely heavily on client-side JavaScript.
  • Bypassing IP-based restrictions by routing requests through proxies.
  • Collecting SEO-related data or SERP (Search Engine Results Page) information.
  • Automating data gathering for competitive analysis or market research.

Practical example:

  • Scraping product details from an e-commerce site that loads content dynamically via JavaScript.
  • Gathering search engine results with full page rendering to capture all visible elements.

Properties

Name Meaning
Operation The specific API action to perform. Options include: Check Page Indexation, Get Backlinks, Get Domain Emails, Get Domain Info, Get Domain Ranking, Get Keywords Search Volume, Get Keywords Suggestions, Get Long Tail Keywords, Get Moz Analysis, Get SERP AI Mode, Get SERP HTML, Get SERP Results, Get SERP Text, Get User Info, Get Webpage AI Analysis, Get Webpage SEO Analysis, Scrape Domain, Scrape Webpage, Scrape Webpage JS, Scrape Webpage JS & Proxy. Default is "Get Backlinks".
Query Parameters (JSON) JSON object representing query parameters for the API call (e.g., {"domain":"example.com"}). Used as URL query string for GET requests.
Request Body (JSON) JSON object representing the body of the POST request. Only applicable for "Scrape Webpage JS" and "Scrape Webpage JS & Proxy" operations.

Output

The node outputs an array of items, each containing a json field with the parsed response from the FetchSERP API corresponding to the requested operation.

  • For scraping operations involving JavaScript and proxy, the output JSON contains the fully rendered webpage content or structured data extracted by the API.
  • No binary data output is indicated in the code; all responses are handled as JSON.

Example output structure (simplified):

{
  "json": {
    // API response data, varies by operation
  }
}

Dependencies

  • Requires an API key credential for authenticating with the FetchSERP API.
  • The base URL defaults to https://www.fetchserp.com but can be overridden in credentials.
  • Network access to the FetchSERP service endpoint.
  • Proper configuration of the API key credential within n8n.

Troubleshooting

  • Unknown operation error: If an invalid operation name is provided, the node throws an error indicating the unknown operation. Ensure the operation value matches one of the supported options.
  • Invalid JSON input: The node parses the "Query Parameters" and "Request Body" fields as JSON. Malformed JSON will cause parsing errors. Validate JSON syntax before running.
  • API request failures: Network issues, invalid API keys, or rate limits may cause HTTP request errors. The node can be configured to continue on failure, returning error messages in the output JSON.
  • Missing credentials: The node requires a valid API key credential. Failure to provide this will result in authentication errors.

Links and References

Discussion