Keywords Everywhere API

Interact with Keyword Engine API

Actions11

Keyword Data Actions
Traffic Metrics Actions
- Get Domain Traffic Metrics
- Get URL Traffic Metrics
Backlink Data Actions

Overview

This node integrates with the Keywords Everywhere API to retrieve keyword-related data. Specifically, for the "Keyword Data" resource and the "Get Related Keywords" operation, it fetches keywords related to a given input keyword. This is useful in SEO, content marketing, and keyword research scenarios where users want to expand their keyword lists or discover semantically connected terms.

Practical examples include:

Generating a list of related keywords to optimize website content.
Finding alternative search terms for paid advertising campaigns.
Exploring keyword variations to improve organic search rankings.

Properties

Name	Meaning
Keyword	The base keyword for which related keywords will be retrieved.
Number of Results to Retrieve	The maximum number of related keywords to return (e.g., 5).

Output

The node outputs an array of JSON objects, each containing:

status: A string indicating the request status, typically "success".
data: The actual response from the Keywords Everywhere API containing the related keywords data.

The exact structure inside data depends on the API response but generally includes the list of related keywords along with associated metrics or metadata.

No binary data output is produced by this node.

Dependencies

Requires an active connection to the Keywords Everywhere API.
Users must provide valid API credentials (an API key) configured in n8n credentials.
The node makes authenticated HTTP GET requests to the API endpoint specified in the credentials.

Troubleshooting

No credentials got returned!
This error occurs if the API credentials are missing or not properly configured. Ensure that the API key credential is set up correctly in n8n before running the node.
HTTP request failures or empty results:
Verify network connectivity and that the API key has sufficient permissions and quota. Also, check that the input keyword is valid and non-empty.
Unexpected API response format:
If the API changes its response structure, the node might fail to parse results correctly. In such cases, verify the API documentation and update the node or contact support.