> ## Documentation Index > Fetch the complete documentation index at: https://docs.crakseo.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > For SEO data and indexing, start with /seo-mcp/overview.md and /seo-mcp/connect.md, then read the focused server reference. > The documentation search MCP at https://docs.crakseo.com/mcp searches documentation only. Product tools use https://crakseo.com/mcp/. > Check tool availability and API credit balance before paid calls. Request owner approval for paid indexing. Never invent prices, indexing guarantees or directory approval. # Keywords > Research, track and assign target keywords, and see where you rank. **Research > Keywords** (`/app/keywords`) holds the project's keyword list. * **Add** keywords manually or from **Research**, which suggests ranked ideas with Google Ads volume, competition and CPC (plus Semrush difficulty when available). * **Fill numbers** for keywords missing metrics. * **Assign** keywords to an account's posting campaign or to the website's article queue. * **Scan SERPs** for the keywords you tick, to see Google page 1, your rank, competitor ranks and parasite opportunities (see [Parasites](https://docs.crakseo.com/product/seo-toolkit/parasites.md)). Keyword metrics come from the first configured provider: Semrush, then DataForSEO, then Google Ads Keyword Planner. ## The keyword list | Column | What it shows | | - | - | | Keyword | The phrase, with icons for the SERP features on its page 1: AI Overview, map pack, People also ask, forums. | | Tags | Your own labels for the keyword, such as `money`, `informational` or `pillar`. Click a tag to filter the list by it. | | Page | The page on your site that targets this keyword. Click the pencil to set the page or edit the tags. | | Opportunity, Volume | Opportunity score (0-100, high searches and low difficulty score highest) and monthly searches. | | KD | Keyword difficulty, with a badge for where the number came from (Semrush, DataForSEO or Google Ads). | | Intent, Priority | What the searcher wants, and how important the keyword is to you. | | Our rank | Your page-1 position from the latest scan. Past page 1 it shows your Google Search Console average position, marked **GSC avg**, or **10+** when neither found you. The change since the previous scan sits next to it. | | Trend | A sparkline of your rank over the last 12 scans. | | Competitor 1 to 4 | Each tracked competitor's page-1 position, or **10+** when it is not on page 1. | | Parasites | How many third-party pages you could publish on rank on page 1. | Sort by **Our rank** or by **Trend** (the change since the last scan) as well as by the metric columns. Bulk actions work on the ticked rows, including adding or removing a tag. A keyword can carry up to 10 tags, and tags are matched without regard to case. Filter the list by a tag, or by **Has page** and **No page** to find keywords that still need a page. The page must be on your site's domain or a subdomain; you can enter a full URL or just the path, like `/peptides/bpc-157`. Agents connected over MCP can set tags and pages too, when adding keywords or later through `update_keywords`. Views above the list read the stored scans: * **Movers**: the biggest rank gains and losses since each keyword's previous scan. * **Competitor gap**: keywords where a competitor is on page 1 and you are not. * **Page vs page**: each mapped competitor page next to your page, with both ranks over time. * **Cannibalization**: keywords where two or more of your pages are on page 1. * **AI Overview**: which AI Overviews cite you, a competitor or a parasite site. ## Keyword SERP page Click a keyword to open its SERP page (`/app/keywords/{keywordId}`). The page uses the full width of the window and reads top to bottom: * **Header**: the keyword with its volume, KD and source, intent, tags and our page (click the pencil to change the page or tags). The scan picker and **Refresh now** sit on the right; pick an older scan to see that day's page. * **At a glance**, five tiles: * **Our rank**: position, change since the last scan, a trend line and the ranking URL. Past page 1 it shows the Search Console average. * **Who owns page 1**: one square per position, coloured by owner (you, competitor, parasite, other). Click a square to jump to that result. * **Competitors**: how many are on page 1, with each one's position and change. * **AI Overview**: whether it cites you, and how many competitors and parasites it cites. * **Parasite opportunities**: how many there are and on which platforms. * **On page 1**: one chip per SERP feature present (AI Overview, map pack, People also ask, forums, videos and so on). Click one to jump to it. * **Google page 1** in Google's order, one compact row per result with a coloured bar for its owner. Results that belong to nobody you track are dimmed, and **Focus** hides them. Click a row to see its snippet and actions (**Send to profile**, **Draft answer** for Reddit and Quora threads, **Mark as...** to correct a label). Features such as People also ask fold into sections with a one-line summary; the AI Overview starts open. * **Side panel**: parasite opportunities grouped by type with their actions, competitors with their moves, and your rank over time (with the Search Console average dashed, and each competitor). ## Where your rank comes from Scans read Google page 1 only (the top 10 results, plus the AI Overview). When your site is on page 1, that position is your rank. When it is not, your rank is the average position from your synced Google Search Console data, at no extra cost. Connect Search Console in **Results** to get ranks past page 1; without it, keywords you don't rank on page 1 for show **10+**. Competitors are tracked on page 1 only. Add up to four in **Settings > Project > Competitors** (see [Parasites](https://docs.crakseo.com/product/seo-toolkit/parasites.md#competitors-and-weekly-tracking)). **Results > Searches that show your site** (`/app/growth/keywords`) is different: it lists the real Search Console queries your site already appears for. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.