Actions28
- Backlink Actions
- SERP Actions
- Business Data Actions
- On Page Actions
- Keywords Data Actions
- Labs Actions
Overview
The "Get Keyword Suggestions" operation in the Labs resource of this node fetches keyword suggestions related to a given input keyword. It is useful for SEO specialists, digital marketers, and content creators who want to discover relevant keywords to target for search engine optimization or paid advertising campaigns.
Typical use cases include:
- Expanding a list of keywords for content planning.
- Finding new keyword opportunities based on seed keywords.
- Analyzing keyword metrics such as search volume, cost per click, and keyword difficulty.
- Filtering and sorting keyword suggestions to prioritize the most valuable terms.
For example, a user might input the keyword "running shoes," specify a location and language, and receive a list of suggested keywords like "best running shoes," "running shoes for flat feet," etc., along with associated metrics.
Properties
| Name | Meaning |
|---|---|
| Keyword | The main keyword string for which suggestions are requested. |
| Location | Full name of the geographic location to tailor keyword suggestions (e.g., "United States"). Supported locations can be found in the DataForSEO documentation. |
| Language | Full name of the language to tailor keyword suggestions (e.g., "English"). Supported languages are listed in the DataForSEO documentation. |
| Ignore Synonyms | Boolean flag to exclude highly similar keywords (synonyms). If true, only core distinct keywords are returned, filtering out near-duplicates. |
| Include SERP Info? | Boolean flag indicating whether to include Search Engine Results Page (SERP) information alongside keyword suggestions. |
| Limit (up to 1000) | Maximum number of keyword suggestions to return. Must be between 1 and 1000. Defaults to 100. |
| Offset | Number of keyword suggestions to skip before starting to collect results. Useful for pagination. Defaults to 0. |
| Sort | Up to three sorting rules to order the keyword suggestions by various metrics. Options include: Search Volume (asc/desc), Cost Per Click (asc/desc), Low/High Top Of Page Bid (asc/desc), Keyword Difficulty (asc/desc). |
| Filters | String containing filter expressions to narrow down keyword suggestions based on supported fields. Refer to DataForSEO documentation for syntax and available filters. |
Output
The output is a JSON array where each element represents a keyword suggestion object. Each object typically contains:
- The suggested keyword text.
- Keyword metrics such as search volume, cost per click (CPC), top of page bid ranges, and keyword difficulty.
- Optionally, SERP information if requested, providing details about the current search results for that keyword.
If binary data is included (not typical for this operation), it would represent associated files or media, but this operation primarily returns structured JSON data.
Dependencies
- Requires an active API key credential for the DataForSEO service.
- The node makes HTTP POST requests to the DataForSEO v3 API endpoint (
https://api.dataforseo.com/v3). - Users must configure the API key credential within n8n prior to using this node.
- Supported locations and languages must be valid as per DataForSEO's documented lists.
Troubleshooting
- Invalid Location or Language: Using unsupported or misspelled location/language names will cause API errors. Verify values against the official DataForSEO documentation.
- API Authentication Errors: Missing or incorrect API credentials will result in authentication failures. Ensure the API key is correctly configured in n8n.
- Limit Exceeded: Requesting more than 1000 keyword suggestions will be rejected. Adjust the limit parameter accordingly.
- Malformed Filters: Incorrect filter syntax may cause the API to reject the request. Consult the DataForSEO filters documentation for correct usage.
- Empty Results: If no keyword suggestions are returned, try broadening filters, changing the keyword, or verifying the location/language parameters.
Common error messages usually indicate issues with parameters or authentication and can be resolved by checking inputs and credentials.