FetchSERP

Interact with the FetchSERP API

Actions20

Overview

This node integrates with the FetchSERP API to retrieve search engine results page (SERP) data and other SEO-related information. It supports multiple operations such as fetching backlinks, domain info, keyword suggestions, SERP results, and more. The "Get SERP Results" operation specifically allows users to query the API for search results based on custom parameters.

Typical use cases include:

  • Automating SEO analysis workflows by retrieving live SERP data.
  • Monitoring keyword rankings or competitor backlinks.
  • Extracting domain-related metrics for marketing insights.
  • Integrating SERP data into reporting dashboards or CRM systems.

For example, a user can input a JSON object specifying a search query and receive structured SERP results to analyze ranking positions or featured snippets.

Properties

Name Meaning
Operation The specific API action to perform. For this context: "Get SERP Results".
Query Parameters (JSON) JSON object containing query parameters for the API request, e.g., {"domain":"example.com"}. These parameters define the search or filter criteria sent to the API.

Output

The node outputs an array of items where each item contains a json field holding the parsed response from the FetchSERP API for the requested operation.

For the "Get SERP Results" operation, the json output includes the structured search engine results data returned by the API. This typically contains details like organic results, ads, featured snippets, and other SERP elements depending on the query parameters.

No binary data output is produced by this node.

Dependencies

  • Requires an active FetchSERP API key credential configured in n8n.
  • The node makes HTTP requests to the FetchSERP API endpoint (default base URL: https://www.fetchserp.com).
  • Proper internet connectivity and valid API credentials are necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API token will cause authentication errors.
    • Malformed JSON in the "Query Parameters (JSON)" property may lead to parsing errors.
    • Using unsupported or incorrect operation names will throw an "Unknown operation" error.
    • Network connectivity problems can cause request failures.

  • Error messages:

    • "Unknown operation \"<operation>\"": Indicates the specified operation is not recognized; verify the operation name.
    • HTTP errors from the API (e.g., 401 Unauthorized, 400 Bad Request) usually indicate credential or parameter issues.
    • JSON parsing errors suggest invalid JSON syntax in input properties.

  • Resolutions:

    • Ensure the API key credential is correctly set up and has required permissions.
    • Validate JSON inputs using external tools before pasting.
    • Select the correct operation from the provided options.
    • Check network access and proxy settings if applicable.

Links and References

Discussion