Ubersuggest

Get content ideas for keywords: top-performing pages by social shares, estimated visits, and backlinks.

content_ideas

Create a new tracked project for a domain. Requires login. Use location_suggest tool to find valid loc_id values.

create_project

Find the main organic competitors of a domain. The backend runs this as an async report: the tool starts the job and polls every 5s for up to ~40s, so a ready report comes back in one call. If the response has 'pendingData: true' the report is still building — call the tool again in a moment.

competitors

Get the organic or paid keywords ranking for a domain, with search volume, position, and difficulty.

domain_keywords

Get a comprehensive overview of a domain including traffic, organic keywords count, domain authority, and backlinks summary.

domain_overview

Get the top countries where a domain gets organic traffic. Pass one or more language+location pairs in 'lang_locs' (format: 'languageCode:locationId', e.g. 'en:2840' for US-English, 'pt:2076' for Brazil-Portuguese). Use 'location_suggest' to find location IDs.

domain_top_countries

Get the top pages of a domain ranked by estimated traffic.

domain_top_pages

Estimate monthly click-through traffic for each SERP result, given its search volume, position, and result type. This is a calculator — it does NOT look up rankings. For each entry you already know (volume + current position + type), it returns the projected clicks. Use it to model scenarios like "if I ranked #3 for kw X (10k volume), how many clicks would I get?". To discover positions for a keyword, use 'serp_analysis' or 'domain_keywords' first.

estimate_serp_clicks

Get the estimated traffic value of a domain in USD.

traffic_value

Returns real-time SEO data from Ubersuggest including exact monthly search volume, cost-per-click (CPC), SEO difficulty score, and paid difficulty for keyword ideas. Use this tool whenever the user needs actual keyword metrics, search volume numbers, or data-driven keyword research — this provides live data that cannot be answered from training knowledge alone. Only call this tool with a keyword the user explicitly provided or clearly implied; never invent, guess, or use a placeholder keyword. If the user has not specified a keyword, ask them which keyword they want to research before calling this tool.

ubersuggest.fetch_keyword_ideas

Get details of a specific project including tracked keywords and settings. Requires login.

get_project

Expand keywords into Google autocomplete suggestions, grouped the way the Ubersuggest web app groups them. Each seed keyword is fanned out into ~60 autocomplete queries (question words, prepositions, comparison words, alphabet and digit suffixes), so this returns hundreds of real long-tail variations per keyword rather than only what autocomplete shows for the bare term. At most 10 keywords are expanded per call. These are raw autocomplete phrases with no metrics attached — use 'keyword_overview' or 'match_keywords' to get search volume, CPC and difficulty for the ones worth pursuing.

google_suggestions

Recalculate a specific metric for a keyword: search difficulty or search intent. Runs an async report on the backend and waits for the result (may take ~30s; search_difficulty consumes the monthly keyword metrics update quota).

keyword_metrics

Get search volume, CPC, SEO difficulty, and paid difficulty for a keyword.

keyword_overview

Get related keyword suggestions with metrics for seed keywords, as a flat list. For paginated or custom-sorted keyword research, use match_keywords instead.

keyword_suggestions

Get referring domains that a target domain recently gained or lost. 'filter_by' selects the set: 'new' (gained, default) or 'lost'. There is no "full live list" option — for totals use 'backlinks_overview' instead. Date range ('begin_date'/'end_date') narrows the gained/lost window (the data source limits this to roughly the last 60 days). For "domains acquired in May 2026", use filter_by='new' with that month's begin/end dates.

linking_domains

List all your tracked projects/domains. Requires login.

list_projects

Search for location IDs by name. Useful to find the locId parameter for other tools.

location_suggest

Get details (name, type, parent hierarchy) for one or more location IDs. Accepts a list so you can resolve several at once.

location_details

Find keywords matching seed terms with volume, difficulty, and CPC data. Great for keyword research.

match_keywords

Get the keywords that a specific page ranks for.

page_keywords

Get an overview of a specific page including its organic keywords and traffic.

page_overview

Get social media share counts + backlink/traffic metrics for a batch of page URLs. Supports multiple URLs in a single call.

page_shares

Run a PageSpeed audit on a domain to check Core Web Vitals and performance.

pagespeed_audit

Get ranking positions for the tracked keywords of a project (rank tracking report). Requires login. Returns the full report. How to read the response: - "done": true — the report is FINAL. Treat it as a definitive answer; do not retry expecting different data. - A keyword's "status": "ok" with "old_position.position": null and "new_position.position": null means the domain does NOT rank in the top 100 for that keyword. This is a final answer ("not ranking"), NOT a "still loading" state. The "binned.not_ranking" bucket counts these. - A keyword's "status": "pending" only appears for brand-new projects whose first SERP collection hasn't run yet (no "updated_at"). In that case, ranking data typically appears 5-60 minutes after project creation; the caller should retry then. - "average_positions.positions": [] simply means there's no historical ranking series to plot — consistent with "not ranking". Polls briefly (HTTP 200/202) for the rare cached-report regeneration path. If the backend errors persistently the tool throws — retry in a few minutes. Filter by lang/location/device; pick one combo you track in the project.

project_position_info

Starts (or re-starts) a site audit crawl for a domain AND returns the initial crawl status. Requires a paid account. This is STEP 1 of the site audit flow. Internally the tool: a) calls the backend to register the crawl task (without this step, later status calls fail with "Task has not been set"); b) immediately reads 'site_audit_status' once so the response tells you whether the crawl just started, is already in progress, or a cached report is already available. Response is the same shape as 'site_audit_status': result.done === true -> a report is ready (cached or freshly finished). Inspect 'result.report'. result.done === false -> crawl is running. Start polling 'site_audit_status' every ~5 seconds with the same 'domain' / 'path' / 'crawlMaxPages' until 'result.done' is true. Then, to list URLs affected by a specific issue id from 'result.report.issues_per_category.{errors|warnings|recommendations}[].id', call 'site_audit_results'. Use 'path' only when auditing a single URL (page audit) rather than the whole domain. Set 'recrawl' to true to force a fresh crawl ignoring any cached result.

site_audit

Get SEO improvement opportunities for a project. Requires login.

seo_opportunities

Analyze the SERP (Search Engine Results Page) for a keyword, showing top ranking URLs with metrics.

serp_analysis

Search articles from Neil Patel's blog. Filter by category server-side and/or refine with query keywords. Returns matching articles with full content as markdown. Provide at least one of: query, category.

search_neilpatel_blog

Lists every URL that was crawled during a completed site audit, with HTTP status and index state. Requires a paid account. Use this after 'site_audit_status' returns 'result.done === true' when the user wants the full list of discovered pages (not issue breakdown). For issue-specific URLs use 'site_audit_results' instead.

site_audit_pages

Gets the list of pages affected by a specific SEO issue from a completed site audit. Requires a paid account. This is STEP 3 of the site audit flow — call it AFTER 'site_audit_status' returned 'result.done === true'. You do not need this tool to get the issue summary (that already lives in the status response's 'result.report.issues_per_category'). Pick the 'issue' id from 'result.report.issues_per_category.{errors|warnings|recommendations}[].id' in the status response (e.g. 'seo_missing_h1', 'seo_broken_links', 'seo_duplicate_titles'). Response contains: result.breakdown -> affected URLs with status + recommendation result.ignored -> URLs the user previously ignored result.diff -> change vs. previous audit

site_audit_results

Checks the progress/result of a site audit previously started with 'site_audit'. Requires a paid account. This is STEP 2 of the site audit flow. Poll this tool repeatedly (every ~5 seconds) until 'result.done' is true. Response shape: result.done -> false while crawling, true when finished result.crawl_count -> pages crawled so far result.crawl_max_pages -> total pages the crawl will visit result.report -> partial (while crawling) or final (when done) audit report, including: overview -> totals + health score issues_per_category: { errors, warnings, recommendations } each with list of issue ids + counts result.extended_status -> 'no_errors' on success, otherwise the crawl failed When 'result.done' is true, stop polling and inspect 'result.report.issues_per_category' for issue ids. To list the affected URLs for a given issue id, call 'site_audit_results'. Pass the same 'domain' / 'path' / 'crawlMaxPages' you used when calling 'site_audit'.

site_audit_status

Validate if a domain or URL is reachable and can be analyzed by Ubersuggest.

validate_site