Keyword.com is a digital marketing platform that provides search engine ranking tracking and SEO analytics
Keyword.com is a digital marketing platform that provides search engine ranking tracking and SEO analytics On Nagent, Keyword is exposed as a fully-configurable marketing integration that any agent can call — 20 actions, and API key authentication. No code is required to wire Keyword into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Keyword to automate the kinds of tasks marketing teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Keyword into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Keyword, with input parameters and output schema. Drop these into any step of an agent built in Helix.
KEYWORD_ADD_KEYWORDSTool to add keywords to a Keyword.com project for search ranking tracking. Use when you need to monitor how specific URLs rank for target keywords across different Google regions and devices.
Input parameters
List of keyword objects to add. Each object contains keyword details like the phrase, URL, region, language, device type, and tags. You can add multiple keywords in a single request.
The name or identifier of the project/group to add keywords to. Must match an existing project in your Keyword.com account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_ARCHIVE_PROJECTTool to archive a project in Keyword.com. Sets the project status to Archived. Use when you need to archive a project without permanently deleting it. The project will remain archived until restored or permanently deleted.
Input parameters
The name of the project to archive. This is the project identifier used in the API path.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_CREATE_PROJECTTool to create a new project or group in Keyword.com account. Use when you need to create a new project for organizing keywords or create a group within an existing project. For groups, the category must follow the naming convention with \[sub\] delimiter (e.g., ProjectName\[sub\]GroupName).
Input parameters
Project name or group name. For creating a project, use the project name (e.g., 'MyProject'). For creating a group within a project, use the format 'ProjectName\[sub\]GroupName' (e.g., 'MyProject\[sub\]MyGroup'). The \[sub\] delimiter is required for group creation.
Optional 3-letter currency code for reporting (e.g., 'USD', 'GBP', 'EUR'). If not provided, the account's default currency will be used.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_DELETE_KEYWORDTool to delete a single keyword from a project or group. Use when you need to permanently remove a keyword. Warning: This action cannot be undone and all historic ranking data will be lost.
Input parameters
The unique identifier of the keyword to delete. Warning: This action cannot be undone and all historic ranking data will be lost.
The name of the project or group containing the keyword (e.g., 'composio.dev')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_DELETE_KEYWORDS_BULKTool to bulk delete multiple keywords from a single project by providing keyword IDs. Use when you need to remove multiple keywords at once from a project.
Input parameters
The unique identifier of the project from which keywords will be deleted.
Array of keyword IDs to delete from the project. Each ID must belong to the specified project.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_DELETE_PROJECTTool to delete a single project or group from Keyword.com. Use when you need to permanently remove a project. This action cannot be undone.
Input parameters
The name of the project or group to delete. This action cannot be undone and will permanently remove the project.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_GET_CURRENT_USERTool to retrieve the current authenticated user's account information. Returns user profile details including ID, name, email, onboarding status, and optionally subscription information.
Input parameters
Include subscription details in response
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_GET_KEYWORDTool to retrieve all keyword settings and ranking metrics for a single keyword. Use when you need to get detailed information about a keyword's performance and configuration. Can optionally retrieve data for a specific date.
Input parameters
Optional date to retrieve keyword data for a specific date. Format: YYYY-MM-DD.
The unique identifier of the keyword to retrieve.
The project name (domain) that the keyword belongs to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_GET_PROJECTTool to retrieve a single project's summary from Keyword.com. Returns groups, tags, keyword counts, and the PROJECT AUTH KEY required for detailed data collection. Use when you need project details or the auth key for further API operations.
Input parameters
The project name or domain to retrieve (e.g., 'composio.dev')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_GET_PROJECT_METRICSRetrieve keyword movement metrics for a project, group, or tag. Returns ranking changes (daily, weekly, or monthly) including number of keywords that improved, declined, or remained unchanged, along with detailed movement data for individual keywords.
Input parameters
Timeframe for metrics calculation. Determines the period for ranking changes.
The name of the project, group, or tag to retrieve metrics for (e.g., 'composio.dev')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_GET_RANKING_HISTORYTool to retrieve Google ranking history for specified keywords for up to 180 days. Use when you need to analyze historical ranking trends or track keyword performance over time. Returns daily ranking positions grouped by keyword ID and domain.
Input parameters
Array of keyword IDs to retrieve ranking history for. Each ID should be a valid keyword ID from your Keyword.com account.
Number of days of ranking history to retrieve. Maximum value is 180 days. If not specified, returns the default number of days.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_GET_SOV_HISTORYRetrieve Share of Voice data over time for a specific project. Use when you need historical SOV metrics. Supports ranges of 7, 30, 90, 180, and 365 days with varying data point intervals.
Input parameters
The unique identifier of the project for which to retrieve Share of Voice data
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_GET_TOP_PAGESTool to retrieve Top Pages data for a project showing ranking URLs with keyword counts, average rank, search volume, and cost per click metrics. Use when you need to analyze which pages are ranking for the most keywords in a project.
Input parameters
Page number for pagination. Starts at 1.
Number of results to return per page. Maximum 250.
The name or identifier of the project/group to retrieve top pages for. This is typically the domain name (e.g., 'composio.dev').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_LIST_ACTIVE_PROJECTSTool to retrieve all active projects with their groups, tags, and keyword counts. Returns PROJECT AUTH KEY for each project which is required to collect detailed project and keyword data.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_LIST_ALERTSTool to retrieve all alerts for the Keyword.com account with pagination and sorting options. Use when you need to fetch alerts, check alert status, or monitor notifications. Supports filtering by view type and retrieving only recent alerts.
Input parameters
When true, retrieves only the most recent alerts. Useful for getting latest notifications without pagination.
Page number for pagination (starts at 1). Use with per_page to navigate through alerts.
Number of results per page (e.g., 100). Controls how many alerts are returned in a single request.
Filter alerts by view type (e.g., 'All alerts'). Narrows results to specific alert categories or statuses.
Field to sort results by (e.g., 'created_at', 'updated_at'). Determines the ordering of alerts in the response.
Sort direction for results. Use 'asc' for ascending order (oldest first) or 'desc' for descending order (newest first).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_LIST_KEYWORDSTool to retrieve all keywords and their ranking data in a project or group. Use when you need to get keyword rankings, search volumes, and position changes. Supports pagination with per_page (max 250) and page parameters, and can filter by specific date.
Input parameters
Optional date to retrieve keyword data for a specific date. Format: YYYY-MM-DD.
Page number for pagination. Starts at 1.
Number of keywords to return per page. Maximum 250.
The project name (domain) to retrieve keywords from.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_LIST_PROJECT_REGIONSTool to list all Google regions being tracked in a Keyword.com project. Returns each region with the count of keywords being monitored in that region. Use when you need to see which geographic regions are configured for keyword tracking in a specific project.
Input parameters
The name or identifier of the project (group) to retrieve regions for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_REFRESH_KEYWORDSTool to trigger an on-demand update for all keywords in one or more projects or groups. Use when you need to refresh keyword rankings data immediately instead of waiting for the scheduled update. Returns the number of refreshes remaining for the day.
Input parameters
List of project IDs that need to be refreshed. You must provide at least one project ID.
Set to true to refresh all keywords in the project and its sub-groups. If false, only refreshes keywords in the specified projects.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_RESTORE_PROJECTTool to restore an archived project or group. Use when you need to unarchive a project and resume keyword tracking. Once restored, keywords will automatically update during the next scheduled cycle.
Input parameters
The name of the project or group to restore from archive. Once restored, keywords will automatically update during the next scheduled cycle.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KEYWORD_UPDATE_KEYWORDSTool to update keyword settings in a project. Updates tracking parameters such as device type, tracked URL, Google region, language, and URL tracking method for multiple keywords at once. Use when you need to modify keyword tracking configuration.
Input parameters
JSON:API formatted data containing keyword update information.
The unique identifier of the project containing the keywords to update.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 35 agents privately built on Nagent that already use Keyword.
Build on Nagent
Connect Keyword to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Keyword, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Keyword is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Keyword is connected, you configure its 20 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Keyword steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Keyword event fires, the agent kicks off automatically.
Every Keyword action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Keyword ships with 20 pre-built marketing actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Keyword together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Keyword-based workflows tailored to your business.