FetchSERP

Interact with the FetchSERP API

Overview

This node integrates with the FetchSERP API to retrieve search engine results page (SERP) data and related SEO information. Specifically, the "Get SERP HTML" operation fetches the raw HTML content of a SERP for given query parameters. This is useful for users who want to analyze or scrape the exact HTML structure of search results for SEO research, competitive analysis, or custom parsing.

Practical examples include:

  • Extracting the full HTML of Google search results for a keyword to perform custom scraping.
  • Monitoring changes in SERP layout or ads by comparing HTML snapshots over time.
  • Feeding the raw SERP HTML into other tools or workflows for further processing.

Properties

Name Meaning
Query Parameters (JSON) JSON object specifying query parameters for the SERP request, e.g., {"domain":"example.com"}

Output

The node outputs an array of items where each item contains a json field holding the response from the FetchSERP API. For the "Get SERP HTML" operation, this json field contains the raw HTML content of the requested SERP as returned by the API.

No binary data output is produced by this operation.

Example output snippet:

{
  "json": {
    "html": "<!DOCTYPE html><html>...</html>"
  }
}

Dependencies

  • Requires an API key credential for the FetchSERP service.
  • The node makes HTTP requests to the FetchSERP API endpoint https://www.fetchserp.com/api/v1/serp_html.
  • The user must configure the API key credential in n8n before using this node.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • Malformed JSON in the "Query Parameters (JSON)" property can cause parsing errors.
    • Network connectivity problems may lead to request timeouts or failures.
  • Error messages:

    • "Unknown operation": Indicates the selected operation is not supported; ensure "Get SERP HTML" is chosen.
    • HTTP errors from the API (e.g., 401 Unauthorized) usually mean invalid credentials.
    • JSON parsing errors suggest incorrect formatting in input parameters.
  • Resolutions:

    • Verify the API key is correctly set up and has necessary permissions.
    • Validate JSON syntax in the input parameters.
    • Check network access and proxy settings if applicable.

Links and References

Discussion