Actions11
- Keyword Data Actions
- Traffic Metrics Actions
- Backlink Data Actions
Overview
This node integrates with the Keywords Everywhere API to fetch keyword-related data, traffic metrics, backlink data, and miscellaneous information. Specifically, for the "Keyword Data" resource and the "Get People Also Searched For Keywords" operation, it retrieves keywords that users commonly search for in addition to a given keyword. This is useful for SEO specialists, content creators, and marketers who want to discover related keyword opportunities and understand user search behavior.
Practical examples include:
- Expanding keyword lists for SEO campaigns by finding related search terms.
- Enhancing content strategy by targeting additional relevant keywords.
- Analyzing competitor keyword strategies by exploring associated search queries.
Properties
| Name | Meaning |
|---|---|
| Keyword | The main keyword to retrieve related or "people also searched for" keywords for. |
| Number of Results to Retrieve | The maximum number of related keywords to return (e.g., top 5 related keywords). |
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, which includes the list of related keywords or "people also searched for" keywords depending on the operation.
The exact structure inside data depends on the API response but generally contains keyword strings and possibly additional metadata such as search volume or competition metrics.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Keywords Everywhere API via an API key credential.
- The node expects the API base URL and authentication details to be configured in the credentials.
- Internet access is necessary to make HTTP requests to the external Keywords Everywhere service.
Troubleshooting
- No credentials got returned!: This error occurs if the API key credential is missing or not properly configured. Ensure that the API key is set up correctly in n8n credentials.
- HTTP request failures: Network issues or invalid API keys can cause request errors. Verify internet connectivity and API key validity.
- Empty or unexpected data: If the API returns no results or malformed data, check the input keyword for correctness and ensure the API service is operational.