# Welcome to SEO Utils

### Overview

SEO Utils is a desktop application that provides a set of essential tools and utilities for your SEO tasks, including Backlink Analytics, Traffic Analytics, Keyword Clustering, etc.

### Get Started

New to SEO Utils? Start here: let your AI app set it up for you (recommended), or follow a step-by-step checklist yourself.

{% content-ref url="/pages/GqD7yfCJEAcnnA8SlAGP" %}
[Set Up SEO Utils](/guide/set-up-seo-utils)
{% endcontent-ref %}

### Supported Platforms

* macOS Monterey 12.0+ (Intel and Apple Silicon)
* Windows 10/11 (AMD64)
* Windows 10/11 (ARM64)
* Linux — Ubuntu 22.04 and above, or any distribution with GTK 3 and WebKit2GTK 4.1

### Features

| Feature                                                                   | Description                                                                                                                                                                                                                                                            | DataForSEO Required (\*)? |
| ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------- |
| Backlinks Analytics                                                       | Provides detailed insights into the backlink profile of any website, including the number, quality, and sources of backlinks.                                                                                                                                          | Yes                       |
| Traffic Analytics                                                         | Unleash your marketing potential! Uncover rivals' traffic stats, identify growth opportunities, organic keywords, and supercharge your strategy.                                                                                                                       | Yes                       |
| [Semantic Keyword Clustering](/guide/semantic-keyword-clustering)         | Do you often wonder if two keywords can be targeted together on a page or struggle with a large list of keywords that ChatGPT or other tools can't cluster due to token limits or cost? This tool resolves all those issues.                                           | No                        |
| [SERP Clustering](/guide/serp-clustering)                                 | Same as Semantic Clustering, but use SERP data to cluster keywords.                                                                                                                                                                                                    | No (or Yes)               |
| Sitemap Extractor                                                         | Extract all URLs from a sitemap                                                                                                                                                                                                                                        | No                        |
| SERP Similarity                                                           | Quickly shows the overlap between two keywords, helping to decide if they can be targeted together on the same page.                                                                                                                                                   | Yes & No                  |
| [SERP UULE](/guide/local-serp-checker)                                    | Check Google Search Results for different locations.                                                                                                                                                                                                                   | No                        |
| [SERP Extractor](/guide/serp-extractor)                                   | Extract detailed SERP data including titles, URLs, featured snippets, and other SERP features for any keyword.                                                                                                                                                         | Yes & No                  |
| Keyword Explorer                                                          | Comprehensive solution for researching and analyzing keywords. It helps you discover relevant keywords, understand their search volume, competition level, and trends, and rank competitors on SERP.                                                                   | Yes                       |
| Ads Vision                                                                | See which Google Ads appear for any keyword, grouped by placement (top, bottom, sidebar, middle), together with keyword metrics and a SERP preview.                                                                                                                    | Yes                       |
| Content Gap                                                               | Easily pull and bulk check all mentions of your keywords with a single click, helping you understand and enhance their ranking.                                                                                                                                        | Yes                       |
| Bulk Analysis                                                             | Run backlink, traffic analysis on 1,000 URLs per time.                                                                                                                                                                                                                 | Yes                       |
| Bulk Keyword Metrics                                                      | Check search volume, CPC, and keyword difficulty for a large list of keywords at once, using the keyword metrics source you choose.                                                                                                                                    | Yes                       |
| [Google Search Console Integration](/guide/google-search-console)         | Providing advanced features such as checking if a keyword appears in the title, headings, and body of a page.                                                                                                                                                          | No                        |
| [GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker)         | Track the keywords you care about for free from your own Search Console data: 16 months of daily positions the moment you add a keyword, movers, alerts by email or webhook, and AI that explains why a keyword moved.                                                 | No                        |
| [Indexing Dashboard](/guide/google-search-console/indexing-dashboard)     | See which of your pages Google has indexed, which it hasn't and why, checked page by page with Google's URL Inspection API and tracked over time.                                                                                                                      | No                        |
| [Topic Clusters](/guide/google-search-console/topic-clusters)             | Group related Search Console queries by meaning with AI embeddings, then see each topic's combined performance and content opportunities.                                                                                                                              | No                        |
| [Google Analytics 4](/guide/google-analytics-4)                           | Sync organic sessions, users, bounce rate, and Key Events from GA4 to see which tracked keywords drive conversions in the Organic Rank Tracker.                                                                                                                        | No                        |
| Bulk Google PAA                                                           | Automatically extract information from the "People Also Ask" section by clicking through multiple layers for a large number of keywords all at once.                                                                                                                   | No                        |
| [Bulk Autocomplete](/guide/bulk-autocomplete)                             | Extract Google/Bing Autocomplete suggestions for many seed keywords with letters, question modifiers, excluded words and `*` patterns. Generate extra seeds with AI or fill a template with a list.                                                                    | No                        |
| [Auto Indexing](/guide/auto-indexing-tool)                                | Use your personal Google Service Account to automatically submit many URLs for indexing.                                                                                                                                                                               | No                        |
| [IndexNow](/guide/indexnow)                                               | Automatically submit URLs to Bing, Yandex, Naver, Seznam.cz, and Yep.                                                                                                                                                                                                  | No                        |
| [Bulk SEO Metadata Optimizer](/guide/bulk-seo-metadata-optimizer)         | Allows you to optimize **titles, meta descriptions, and H1 headings** across multiple pages using AI models (Cloud or Local). This tool is perfect for SEOs looking to save time while enhancing metadata for better search engine visibility and click-through rates. | No                        |
| [Content Struct](/guide/content-struct)                                   | Scrapes all headings, metadata, and main content from the top 20 URLs on the SERP, and allows you to generate a content outline using either cloud-based AI or local AI models.                                                                                        | No                        |
| Backlink Gap                                                              | Compares your website's backlink profile with those of your competitors, identifying opportunities where you can build more backlinks to improve your site's search engine ranking.                                                                                    | Yes                       |
| [GMB Rank Tracker](/guide/google-my-business-rank-tracker)                | This tool tracks your Google Business profile's ranking on Google Maps, and optionally in the Local Pack and the Local Finder, from a grid of spots around your business. It also shows your competitors, so you can plan how to improve your ranking.                 | Yes & No                  |
| [GMB Report Groups](/guide/google-my-business-rank-tracker/report-groups) | Combine multiple GMB Rank Tracker reports into one dashboard with aggregated visibility and ranking changes. Ideal for multi-location businesses.                                                                                                                      | Yes & No                  |
| [N.A.P Finder](/guide/n.a.p-finder)                                       | Automates citation tracking by scanning the web for variations of a business’s name, address, and phone number, making it easy to spot inconsistent or rogue listings.                                                                                                 | Yes & No                  |
| [Google Business Reviews Fetcher](/guide/google-business-reviews-fetcher) | Collect Google reviews for a business on a schedule, see which reviews are new, missing, or reinstated, and get alerts for low-rating reviews through Automations.                                                                                                     | Yes                       |
| [Organic Rank Tracker](/guide/organic-rank-tracker)                       | Keep track of how keywords rank on desktop, mobile, and local search results. Also, include an analysis of competitor performance.                                                                                                                                     | No (or Yes)               |
| [NLP Text Analysis](/guide/nlp-text-analysis)                             | Extract key topics and entities from text or URLs, powered by Google NLP, TextRazor, and Dandelion, supporting 20+ languages.                                                                                                                                          | No                        |
| [Share Reports with Clients](/guide/white-labeled-client-report)          | Publish a read-only copy of a GMB, Organic or LLM Rank Tracker report to a link your client opens in any browser, with an optional password. No sign-in needed, and it stays available while your computer is off.                                                     | No                        |
| [Log File Analysis](/guide/log-file-analysis)                             | Track and optimize for these AI bots, alongside traditional search engine crawlers like Googlebot and Bingbot.                                                                                                                                                         | No                        |
| [LLM Rank Tracker](/guide/llm-rank-tracker)                               | Monitor your brand’s visibility, sentiment, and citations in AI search results like Google AI Overview, AI Mode, ChatGPT. Track mentions, analyze competitors, and measure trends over time.                                                                           | Yes                       |
| [AI Visibility](/guide/ai-visibility)                                     | See how often Google AI Overviews and ChatGPT name your brand next to your competitors, the real prompts where rivals win, and the sites AI cites. No prompt list to write first.                                                                                      | Yes                       |
| [SEO Tests](/guide/google-search-console/seo-tests)                       | *Time-based, URL Switch, and Split Tests* — to run controlled experiments and see the real impact of your changes with Google Search Console data.                                                                                                                     | No                        |
| [Internal Links](/guide/google-search-console/internal-links)             | Find the pages that need more links pointing to them, get the exact sentence and link text for each new link, and apply accepted links to WordPress (or revert them).                                                                                                  | No                        |
| [Saved Keywords](/guide/saved-keywords)                                   | Create keyword lists, import metrics from CSV/Excel, check search volume and difficulty, and organize keywords with tags.                                                                                                                                              | No                        |
| [Bulk Check Mentions](/guide/bulk-check-mentions)                         | Import a list of keywords and URLs, then bulk check if each keyword is mentioned in the title, headings, meta description, and body of each page.                                                                                                                      | No                        |
| Search Intent Bulk Check                                                  | Label any list of keywords with its search intent without spending DataForSEO credits. Uses a TypeSafe API key, which you can add in Settings.                                                                                                                         | No                        |
| [Automations](/guide/automations)                                         | Automate actions when rank tracking completes. When an Organic Rank Tracker or Google Business Rank Tracker snapshot finishes, you can automatically export PDFs, send emails to clients, or trigger webhook URLs.                                                     | No                        |
| [Workspace](/guide/workspace)                                             | Organize and separate your projects, clients, or different SEO campaigns. Each workspace maintains its own set of data.                                                                                                                                                | No                        |
| [Embedding Database](/guide/embedding-database)                           | Convert text into mathematical representations (embeddings) that capture semantic meaning                                                                                                                                                                              | No                        |
| [MCP Server (AI Integration)](/guide/mcp-server)                          | Connect AI assistants like Claude Desktop, Claude Code, or any MCP client to query your SEO data using natural language. Run reports, analyze rankings, fetch backlinks — all with plain English prompts.                                                              | No                        |
| [Remote Access](/guide/remote-access)                                     | Open your SEO Utils from any browser through a private address. Pair your computer once, sign in from your phone or another computer, and share seats with your team — the desktop app keeps doing the work and your data stays on your computer.                      | No                        |
| [Team](/guide/team)                                                       | Invite the people you work with to use your SEO Utils from their own browsers, each with a role and only the workspaces you give them, and see who did what and what their paid calls cost. Part of the Remote Access + Agency plan.                                   | No                        |
| [Backups & Restore](/guide/backups-and-restore)                           | Back up SEO Utils by hand or on a schedule to an S3 / R2 bucket or a folder such as an external drive, optionally encrypted, and restore it on this computer or a new one.                                                                                             | No                        |
| [DataForSEO Task Monitor](/guide/dataforseo-task-monitor)                 | See what your paid DataForSEO tasks are doing (waiting, collected, recovering, or stuck) and whether anything needs your attention.                                                                                                                                    | Yes                       |
| Site Integrations                                                         | Connect your WordPress site so the Bulk SEO Metadata Optimizer and Internal Links can publish changes directly to your pages.                                                                                                                                          | No                        |

(\*) You are required to use your own [DataForSEO account](/guide/seo-data-source) or [rent an API Key from SEO Utils](/guide/rent-dataforseo-api-key).

### Download Links & License Key

After you [purchase a license key](https://larseo.lemonsqueezy.com/checkout/buy/630311af-3d08-47e3-9e29-9531b7ea60e0), you will see the download app links for all platforms and the license key on the checkout page or in your email inbox.

### App Updates

One license key allows you to use the current app version indefinitely. They are also eligible for one year of free updates.

If you don't want to renew the license after one year, you can continue to use the last version of the app that you have access to.

### Troubleshooting

Need help? Visit our [Troubleshooting page](/troubleshooting) for easy solutions and quick fixes to common problems.

### Support

* Facebook Group: <https://www.facebook.com/groups/seoutils>


# Feature Demo

Here is a demo that quickly showcases some of the current features of SEO Utils.

### Keyword Clustering

I ran keyword clustering on over 8,000 keywords, and it only took 2 minutes to finish.

{% embed url="<https://drive.google.com/file/d/1NLTe2JVi8TF3pbyJUKd-c6Uflqr5umxW/view?usp=drive_link>" fullWidth="true" %}

### SERP Similarity

{% embed url="<https://drive.google.com/file/d/13EmxhG2xlwQWL_7D8D03KH60LI1PHUiy/view?usp=drive_link>" fullWidth="true" %}

### Traffic Analytics

{% embed url="<https://drive.google.com/file/d/1F-XI_Sv_JKLPiXLHMHsic3EWAFA1ixuZ/view?usp=drive_link>" fullWidth="true" %}

### Backlinks Analytics

{% embed url="<https://drive.google.com/file/d/13cLdKNs0W6BcPRd5OM9DXW4WsOy2_2rs/view?usp=drive_link>" fullWidth="true" %}

### Bulk Google PAA Scrapping

{% embed url="<https://www.youtube.com/watch?v=qa4GTnMxcE8>" %}


# Troubleshooting

Encountering issues? Our Troubleshooting Hub is here to help. Find quick fixes, step-by-step guides. Let's get you back on track!

### macOS

When installing the app on macOS, if you see this kind of message:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-18f79045c0fc64a017ac6550d5c38967e3361bb2%2FXnapper-2024-01-24-12.27.54.png?alt=media" alt="" width="375"><figcaption><p>“SEO Utils” can’t be opened because Apple cannot check it for malicious software.</p></figcaption></figure>

1. Please open the **System Settings**
2. Go to the **Privacy & Security** menu
3. Hit the **Open Anyway** button

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-02267046d00e83293035dd8bcae68a1220078a0e%2FCleanShot%202024-01-24%20at%2012.31.18%402x.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

If you cannot upgrade the app, please move the SEO Utils app to the **Applications** folder

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-87f8be67e54768e8842650645dd58bd440a43ee2%2F471607863_8910071832395299_4952853912844482308_n.jpg?alt=media" alt="" width="563"><figcaption><p>Move the SEO Utils app to the Applications to folder</p></figcaption></figure>

And please make sure you allow SEO Utils to access your Downloads folder.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a4b16d4d6199bef135885ff7fe867d6ea3505c22%2FCleanShot%202024-05-06%20at%2012.13.03%402x.png?alt=media" alt="" width="375"><figcaption><p>Allows SEO Utils to access the Downloads folder in macOS</p></figcaption></figure>

### Windows

If you encounter a permission error or the program exits when clustering keywords on Windows, please ensure that you run SEO Utils as an administrator. This will allow the app to write the cluster data into a CSV file on your machine.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8da8f6e83dc8eb482241412a27b9a053661e2a17%2F53db0b2010303a3571c40e969cd8623b.png?alt=media" alt=""><figcaption><p>Permission denied</p></figcaption></figure>

You can do that by right-clicking on the SEO Utils shortcode, going to the **Compatibility** tab, and selecting "**Run this program as an administrator**." So, each time you run it, it will always run as an administrator.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0c8e6f5693bb71715ec8447d17fb5ce57d23e4ed%2Fimage-1.png?alt=media" alt=""><figcaption><p>Run "SEO Utils" as an administrator</p></figcaption></figure>

### Linux

If you can't open the app and see an alert like this.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8f89b084909f4e7fbf90308efbf7771568125f69%2FCleanShot%202024-08-06%20at%2010.51.50%402x.png?alt=media" alt="" width="563"><figcaption><p>Cannot open the app in Linux</p></figcaption></figure>

Right-click on the app > **Properties** > **Permissions** > Check "**Allow executing file as program"**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3292820565a8bc793543acb5274179a7c13ea87f%2FXnapper-2024-08-06-11.15.47.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

***

If you're running Ubuntu 24.04 (or similar distro) and the app doesn't launch, try running it from the terminal. If you see this error:

```
./SEO Utils: error while loading shared libraries: libwebkit2gtk-4.0.so.37: cannot open shared object file: No such file or directory
```

This happens because Ubuntu 24.04 ships with WebKitGTK 4.1 instead of 4.0. The `libwebkit2gtk-4.0-dev` package is not available in the default repositories for this distro version.

**Solution:** Create symbolic links to alias version 4.1 to version 4.0:

```bash
sudo ln -sf /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.1.so.0 /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
sudo ln -sf /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.1.so.0 /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
```

Credit: [BambuStudio GitHub Issue #3973](https://github.com/bambulab/BambuStudio/issues/3973#issuecomment-2097651206)

***

If the app crashes on launch with an error like:

```
Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal
...
fatal error: non-Go code set up signal handler without SA_ONSTACK flag
```

This is a signal-handling conflict between WebKit and the Go runtime, most commonly seen on Ubuntu 26.04 and other distros shipping a newer WebKitGTK.

{% hint style="success" %}
**Fixed in SEO Utils 1.48.0 and later.** The app now reconfigures these signal handlers automatically at startup. If you see this crash, update to the latest version and relaunch — no environment variables required.
{% endhint %}

<details>

<summary>Workaround for older versions (pre-1.48.0)</summary>

If you can't update right now, set an environment variable before launching the app to tell WebKit to use a non-conflicting signal:

```bash
JSC_SIGNAL_FOR_GC=SIGUSR2 ./SEO\ Utils
```

Or export it for the session:

```bash
export JSC_SIGNAL_FOR_GC=SIGUSR2
./SEO\ Utils
```

</details>


# Changelog

### v2.16.0

*Released Nov 13, 2026*

* Added [AI apps from anywhere](/guide/mcp-server/connect-ai-apps-from-anywhere): Claude, ChatGPT, Claude Code, Codex, Cursor, Perplexity, Grok and the Gemini app can use the SEO Utils on your computer through your Remote Access address, from your phone or the cloud, and read your reports' results. Turn on Allow AI apps over Remote Access in Settings › Remote Access, then follow your app's steps under Settings › MCP Server › Connect an AI app › From anywhere.
* Added [Local Pack and Local Finder](/guide/google-my-business-rank-tracker/local-pack-and-local-finder) results to every part of the GMB Rank Tracker: a list switcher moves the report page, its history, Compare, report groups and exports between Google Maps, the Local Pack and the Local Finder.
* Added [Publish to client](/guide/white-labeled-client-report) to the GSC Rank Tracker. Share a tracker with a client through the same link and password as the Organic, GMB and LLM trackers, updated after every sync that brings new data.
* Added Import from Semrush to the Organic Rank Tracker. It builds a tracker from a Semrush Position Tracking Rankings Overview CSV, with every day's rank and ranking page and each keyword's search volume, CPC, intent and tags; for a project with competitors, you choose the domain to import.
* Improved the [GMB Rank Tracker](/guide/google-my-business-rank-tracker), rebuilt around one report page: the map fills the page, with a keyword list, a timeline of runs, run controls and a drawer for each spot, its history and sharing, and Compare shows two runs side by side or with a slider. New reports are created in four steps with a live cost bar, and report groups get a dashboard with headline figures, the locations that need attention and a keyword × location table.
* Improved getting started with the GMB Rank Tracker: until it is set up, the page lists the missing steps beside a sample report, and the New report form says when DataForSEO isn't set up or is in Sandbox Mode and keeps what you entered while you set it up.
* Improved the built-in bot list of Log File Analysis: Claude-SearchBot is built in, ClaudeBot counts as AI Training instead of AI Answer, also in existing reports, and Google-Extended is no longer listed, because Google crawls with Googlebot.
* Fixed Log File Analysis counting Claude-User and Perplexity-User visits as human traffic, and never verifying Claude's or Perplexity's bots. They are now checked against Anthropic's and Perplexity's published IP lists.
* Fixed GA4 syncs failing on every dataset with "Client.Timeout exceeded" after the computer slept or changed Wi-Fi or VPN. SEO Utils now drops a stalled connection to Google and tries a failed GA4 page once more.
* Fixed deleting a workspace after deleting its reports: it was refused because the workspace still "contains Dfs Task Runs", even after a restart. Finished runs no longer block the delete, and a run still in progress says so.

### v2.15.0

*Released Nov 10, 2026*

* Added [GA4 Traffic](/guide/google-analytics-4/ga4-traffic) under Your Sites: every Google Analytics 4 channel, not only organic search, with sessions, key events and revenue by channel, search engine, source and month, compared with an earlier period. SEO Utils now syncs 16 months of GA4 history, and a computer that was off at the daily sync catches up when the app starts.
* Added [GA4 traffic next to your clicks](/guide/google-search-console#ga4-traffic-next-to-your-clicks) in Search Console: sessions on a property's chart, an organic share card and GA4 columns on the Pages table. The GSC Rank Tracker shows the sessions and key events of each keyword's page.
* Added [Site traffic (GA4)](/guide/organic-rank-tracker#show-site-traffic-in-the-report) to Organic Rank Tracker and GSC Rank Tracker reports: choose a GA4 property in the report's settings and its PDF, manual or scheduled, shows the site's traffic by channel. A published Organic Rank Tracker client report gains a Traffic tab.
* Added a renewal notice for your license key. From 30 days before it expires, the license row at the foot of the sidebar shows the date, and in the last 7 days a banner appears on every page. [Renew license key](/guide/manage-license-key#renew-your-license-key) now opens the renew page already on your license.
* Added Ask your AI app to the What's New window, and an Ask AI what's new button to the Dashboard's Version card. They copy a prompt that has your AI app explain what changed since the version you last saw.
* \[Agent Skills]: Added [Google Analytics tools](/guide/mcp-server#google-analytics-tools). AI apps can read your synced GA4 traffic by channel, key events, sources, months and pages, compare GA4 organic sessions with Search Console clicks, and start a sync.
* \[Agent Skills]: Added a tool that tells AI apps what's new in SEO Utils: the latest releases, or every release since a version you name, with links to their guides.
* Improved the error AI apps show when their connection to SEO Utils is cut mid-request. It now says that antivirus web protection, such as AVG or Avast Web Shield, often does this and that adding SEO Utils as an exception fixes it. Settings › MCP Server says the same.
* Improved what happens when your computer's disk is full: SEO Utils shows one Disk Full notice at most every 30 minutes instead of an error for every failed save, and the Organic Rank Tracker keeps collected results and imports them once there is space again.
* \[Agent Skills]: Fixed AI apps creating a second report, such as a SERP Clustering report, when they retried an action while SEO Utils was busy saving data. Actions that change data now answer "The app is busy saving data. Try again in a moment." within the call, instead of finishing up to an hour later.
* Fixed Edit Tracker in the Organic Rank Tracker saving nothing, without saying why, for some reports, such as reports with no DataForSEO priority saved. When a save is refused, the message now names the field and its tab.
* Fixed Google Analytics 4 page data: sessions and key events of a page reached through several addresses, such as with tracking parameters, were undercounted, days read as the day before in time zones west of UTC, and a first sync that failed never fetched the history. SEO Utils syncs the pages again to correct them.
* Fixed Export as PDF in an Organic Rank Tracker report doing nothing while the Insights tab was open.
* Fixed closing a file dialog without choosing a file: on Windows it showed an error, and Browse for the embedding model or a Google Drive service account cleared the saved file.

### v2.14.2

*Released Nov 8, 2026*

* Added the [Pages tab](/guide/google-search-console/gsc-rank-tracker/opportunities-per-page) to the GSC Rank Tracker: one row per page Google shows for your tracked keywords, with its clicks, impressions, total Opportunity and Split or Wrong page flags. Click a page's keyword count to work through its keywords, sorted by Opportunity. Reports and the automation PDF gain a Top pages by opportunity section.
* Added clickable counts to SERP Analysis, Traffic Analytics and Backlink Analytics. A count such as Backlinks, Referring Domains, Keywords or a chart slice now opens the rows behind it, already filtered, and a Back button returns you to where you were without a new paid lookup.
* Added a Shared mode to Content Gap: the keywords your site and one competitor both rank for in Google's top 10. In Traffic Analytics, a competitor's Shared Keywords number now opens this list.
* Added Load from sitemap to the URLs tab of Text Analysis: enter a sitemap or sitemap index and its pages are added to the URL list, so you can remove the ones you don't need before analyzing.
* Added Compare in Backlink Gap to the row menu of Backlink Analytics' Competitors tab.
* Improved the [Money Map](/guide/google-my-business-rank-tracker/map-tools#money-map) in the GMB Rank Tracker: a report can now show up to 10 RingTonic campaigns together, such as your Website Tracker campaign and your static tracking numbers, and you can turn each one off on the map.
* Improved the Indexing tools on large sites. URLs that no sitemap has listed for 14 days (you can change this in the property's settings) are no longer inspected or submitted, so Google's daily inspection quota goes to your live pages, and indexed pages are checked again regularly. The Log Analyzer labels these URLs Out of Sitemaps.
* Improved the GSC Rank Tracker's Opportunity: a keyword with no search volume that ranks on page 1 now gets an Opportunity from its impressions. The Keywords table can also filter by page and select all matching keywords across pages for a bulk action.
* Improved the errors AI apps show when they can't reach SEO Utils: they now say why, for example that SEO Utils was closed or that another program uses its port. Settings › MCP Server shows each AI app's latest failure.
* Improved the message Remote Access shows on a computer that sends its traffic through a proxy: it now says what to allow instead of "could not reach the hub".
* Fixed Organic Rank Tracker reports set to a town with no geo target, such as reports created by AI apps, showing another town's rankings. Each town now gets its own results.
* Fixed the Organic Rank Tracker leaving some keywords without a position, or with yesterday's position marked stale, when another report had already checked the same keyword that day.
* Fixed scheduled Automation exports failing when the Mac was locked.
* Fixed automation emails not reaching their CC recipients.
* Fixed backups refused for lack of space on a Mac with plenty of space available. SEO Utils now counts the space macOS frees on demand, as Finder does, and Maintain checks for free space before it starts and uses less memory.
* Fixed Connect for Claude Desktop on Windows with newer versions of Claude Desktop, which keep their settings in a new folder.
* Fixed Organic Keywords in Traffic Analytics listing paid ads among the organic results.
* Fixed the Search Console date range's custom Start and End dates opening no calendar.
* Fixed long property URLs being cut off at both ends in Search Console's Rankings view. A long URL now ends in "…" and shows in full on hover.
* Fixed the Referring IPs card in Backlink Analytics showing the referring domains count, the TLD chart titled Semantic Locations, and the Platform filter.

### v2.14.1

*Released Nov 3, 2026*

* Added [AI to the GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker/ai), on your own AI key: Why did it move? explains a keyword's ranking change from the tracker's own data, an optional weekly summary appears in a This week card, in reports and in automation emails, and Group with AI sorts your keywords into topic tags.
* Added [Keywords in the top 1, 3 and 10](/guide/google-search-console/gsc-rank-tracker/top-1-3-10) to the GSC Rank Tracker. It charts how many keywords Search Console puts in the top 1, 3 and 10 over time, with clicks and impressions, and draws the linked Organic Rank Tracker report beside it so you can see where the two differ. The position bands chart now splits #1 from 2–3 and shows the average position, and the KPI strip has a Top 1 tile.
* Added a [printable report](/guide/google-search-console/gsc-rank-tracker/print-and-pdf) to the GSC Rank Tracker: choose Export PDF & HTML… in the tracker's title menu, or add Export PDF to a GSC Rank Tracker Alerts automation. The preview shows the PDF's real A4 pages.
* Added the [Before / after](/guide/google-search-console/gsc-rank-tracker/before-after) tab to the GSC Rank Tracker. Pick a day, such as a page rewrite or a Google update, and see how each keyword's position moved in the 7, 14 or 28 days before and after it.
* Added the [CTR gap](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#ctr-gap) badge and the Volume and Opportunity columns to the GSC Rank Tracker's Keywords table. CTR gap flags keywords whose clicks are low for where they rank, and Opportunity estimates the extra clicks a keyword would get in the top 3.
* Added the [Rankings view](/guide/google-search-console#rankings-across-properties) to the Search Console properties page: every GSC Rank Tracker in one table, with its average position, Top 3 and Top 10, movers, unread alerts and a 90-day trend.
* \[Agent Skills]: Added [GSC Rank Tracker actions](/guide/mcp-server#try-these-prompts-with-the-gsc-rank-tracker). AI apps can read your trackers' daily positions, movers and alerts, explain why a keyword moved, and create trackers and add keywords to them.
* Improved Search Console syncs on properties with Branded Keywords. After each sync, SEO Utils now marks the branded queries of the synced days only, one day at a time, so saves elsewhere in the app no longer wait behind it, sometimes for over an hour.
* Improved the LLM Rank Tracker so it no longer pays Google again to score the sentiment of a brand mention it has already scored.
* Fixed scheduled LLM Rank Tracker reports starting again every 15 minutes, and spending AI and DataForSEO credit each time, after a run in which an AI engine gave no answer. A report now runs on its own once per period whatever the outcome; if one ever tries to run more often, its automatic runs pause, you get a notification, and Resume automatic runs on the report starts them again.

### v2.14.0

*Released Oct 30, 2026*

* Added [Automatic Backups](/guide/backups-and-restore#automatic-backups): back up SEO Utils on a schedule to an S3 or R2 bucket or to a folder such as an external drive, with optional encryption. A backup can now be restored on this computer or on a new one.
* Added Import from ProRankTracker to the Organic Rank Tracker. It builds a tracker from a ProRankTracker ranking export, with its full daily history and its Snack Pack (Local Pack) positions.
* Removed Share (Legacy) from the GMB Rank Tracker, along with its Shareable Reports (Legacy) settings. Share reports with clients through Publish to client instead.
* Fixed the Organic Rank Tracker marking sites as not ranked when they rank, after a change at Google left many DataForSEO results without their site. In the GSC Rank Tracker, Check live SERP also lost the Your site badge on those results.
* Fixed IndexNow Import URLs failing with "no URLs found in sitemap" on sites whose firewall blocks visitors claiming to be Googlebot. The Sitemap Extractor and the Search Console sitemap checks had the same problem.

### v2.13.0

*Released Oct 29, 2026*

* Added a guided [setup of SEO Utils](/guide/set-up-seo-utils) to Onboarding, with a video: let your AI app walk you through it, or follow a checklist yourself.
* Added [Connect Google](/guide/set-up-seo-utils#connect-google-automatically), which creates your Google service account and Places API key for you.
* Added a short guide to every tool, and [Copy error](/guide/mcp-server#troubleshooting) on error messages so your AI app can help you fix them.
* \[Agent Skills]: Added tools to start Connect Google, read run logs and recent failures, and explain how a tool works.
* Improved the layout: the sidebar groups tools by job and can be hidden, every page shows its name in the top bar, and a report's actions are in the menu under its name.
* Improved the [Location field](/guide/seo-data-source#refresh-the-location-lists): one field for country, region, city or postal code, with lists kept up to date from DataForSEO.
* Improved Settings, the Dashboard on small screens, the Team page before Remote Access is set up, and run logs, which now name the keywords that failed.
* Fixed freezes on the Indexing page of very large properties, and on Windows during GMB Rank Tracker automated exports.
* Fixed the MCP server and Remote Access not starting on Windows when their port was reserved. They now move to a free port.
* Fixed an expired license key that could not be removed, and a rejected Renting API key showing a 401 error on Home.
* Fixed SERP Data Importer imports of external data not showing in any tool, and its Desktop Devices switch.

### v2.12.1

*Released Oct 26, 2026*

* Added a new setup flow to Onboarding. Tell SEO Utils what you do, then choose **Set up with your AI app**: one **Connect** button adds SEO Utils and its skill to your AI app, and the AI walks you through the rest. Or choose **Set up myself** to get the steps your tools need, in order, each with a short how-to.
* Added a [Connect button for each AI app](/guide/mcp-server#connecting-to-ai-assistants) in the MCP Server settings, with the AI apps that used SEO Utils listed as Used recently, and an AI assistant card on the Dashboard. Pages that need DataForSEO, Google Places or a service account also offer **Set up with your AI app**.
* \[Agent Skills]: Added setup tools. AI apps can see which SEO Utils tools fit your work, check what each one still needs, and open the right settings page in SEO Utils for you. They work with every license, so you can turn on the MCP server to get set up even without the MCP add-on.
* Improved the [SEO Utils skill](/guide/mcp-server#install-the-seo-utils-skill-recommended) for AI apps. It now comes with the app, so **Install skill** works offline, every copy you installed is brought up to date when SEO Utils starts, and the Dashboard shows whether each copy is current. Claude Code now gets the skill in its own skills folder, like the other apps.
* Improved [connecting a Google account to Search Console](/guide/google-search-console#method-1-google-oauth-token). **Add Search Console Property** now connects the account in place and loads its properties, the browser page says whether it worked (and how to fix it when Search Console access was not ticked), and SEO Utils comes back to the front when you are done.
* Improved the DataForSEO step in Onboarding. It now checks your login with DataForSEO and shows your balance, or says why the login does not work.
* Improved Remote Access security. The secure connection that Remote Access uses now rejects certificates that were recently reported as compromised. The update installs by itself the next time Remote Access starts.
* Fixed Onboarding not showing on a fresh install. Users without a license landed on the license key page instead.
* Fixed log imports from a browser over Remote Access failing on a slow or busy computer.

### v2.12.0

*Released Oct 23, 2026*

* Added [Team](/guide/team) to the Remote Access + Agency plan. Invite the people you work with to use your SEO Utils from their own browsers, each with a role (Viewer, Analyst, Manager or Custom) and only the workspaces you give them, while your computer still does the work and keeps your data.
* Added [Team Activity and Spend](/guide/team/activity-and-spend) and Online now to Settings → Team, so you see who did what, what each person's paid calls cost and who is signed in. Saved reports also show who created them and who ran them last.
* Added [Re-check results that look poisoned](/guide/organic-rank-tracker#possibly-poisoned-results) to the Organic Rank Tracker. When most of a keyword's usual sites vanish from its results, SEO Utils fetches it once more, and a page that still looks wrong keeps the previous position, labelled Possibly poisoned.
* Added View log to the Organic Rank Tracker report's … menu, so you can read what each run did and why a keyword failed.
* Added a [background color](/guide/google-my-business-rank-tracker/exports-and-client-reports#branding) to GMB Rank Tracker exports. Pick it in the export Settings; it applies to the PDF, HTML and printed report, automated exports and the Progress view export.
* Improved the GMB Rank Tracker Progress view PDF. Maps are sized to fit the page by how many there are, the grid fills each map, the area the grid covers replaces the distance, a new switch shows the summary numbers above the maps, and one export takes up to 100 keywords instead of 15.
* Fixed SEO Utils on Mac slowing down badly while its window was hidden, minimized or covered on a busy Mac. Scheduled runs, DataForSEO collection, Remote Access pages and the MCP server could wait up to a minute at a time.
* Fixed a red "database is locked" error every minute, and screens that stopped loading, on large databases. Screens now keep loading while the database is busy, and one notice with Show details says when it is.
* Fixed sitemap checks and crawls being blocked by some hosts' firewalls because SEO Utils presented itself as an outdated Chrome. A sitemap that bot protection still blocks now says so on the Indexing page, with advice to ask the host to allowlist your IP, instead of "server returned HTTP 202".
* Fixed the Indexing Overview chart in Search Console counting URLs not yet inspected as Not indexed. It now agrees with the Not indexed count, past days included.
* Fixed the Search Console Performance chart in Week view splitting the week that spans New Year into two points, drawn as a false dip. Comparisons on hover also matched some weeks with the wrong week of the other period.
* Fixed gaps in the Search Console Performance chart lines wherever an annotation or Google update pin sat in Week and Month view. Clicking a pin now opens the annotations of that whole week or month.
* Fixed blank maps in GMB Rank Tracker report exports and automated exports, and pins overlapping each other on dense grids.
* Fixed saving a GMB Rank Tracker report clearing its export logo, heading, subheading and description.

### v2.11.0

*Released Oct 20, 2026*

* Added Japanese, Polish and Vietnamese to the app. Choose one in Settings → General → Language and the window reloads in that language. The Export PDF action of an automation has a new Report language setting, so a report PDF can be in another language than the app. Client reports and Remote Access in the browser stay in English.
* Added the [comparison with an Organic Rank Tracker report](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker) to the GSC Rank Tracker. Link a tracker to a report in its Settings to see the rank tracker's position and its gap to Google's average position for each keyword, filter for big gaps or keywords only one side has, and read a hint about what likely causes each gap.
* Added [Check live SERP](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#check-a-live-serp) to the GSC Rank Tracker. It checks a keyword's Google results right now on your DataForSEO login, at most $0.02 per keyword, shows the price before anything is spent, and keeps every result of each check with the keyword.
* Added [Send to rank tracker](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#send-keywords-to-the-rank-tracker) and a Not seen by Google filter to the GSC Rank Tracker. Find the keywords Google never showed your site for in this market, and send them to the linked Organic Rank Tracker report to learn where they rank.
* Added [Duplicate tracker](/guide/google-search-console/gsc-rank-tracker/manage-trackers#duplicate-a-tracker) to the GSC Rank Tracker. The copy keeps the keywords, rules, tags and targets, and can use another country, device or search type, for example Image instead of Web.
* Added a [Tags for these keywords](/guide/google-search-console/gsc-rank-tracker/create-a-tracker#keywords) field to the GSC Rank Tracker's Paste / Import tab. Every pasted keyword gets the tags, including keywords the tracker already has.
* Improved the LLM Rank Tracker so large runs finish several times faster. SEO Utils now finds the brands in each AI answer with GPT-6 Luna, which costs about 8 times less per answer on your AI key, and works on up to 16 answers at once.
* Improved AI Visibility so large explorations send fewer DataForSEO requests and cost less to load and refresh. Overview counts that said "Too many conditions for this count" now load.
* Improved the license screen when every device your license allows is already activated. It now says so and has a Manage Devices button to free one, instead of a short error.
* Improved the business search in the GMB Rank Tracker. When Google Places refuses your API key or its quota is used up, it now says so, instead of "No results found."
* Fixed GMB Rank Tracker keywords your business ranks for at no grid point showing "—" in the Keywords table and missing from Ranking Keywords, the report preview and the dashboard. They now show Not in top 20 and count as rank 21.
* Fixed a new Search Console property waiting in the sync queue behind properties your Google account can no longer read. Such a property now fails at once, says how to fix its access, and is tried again once a day.
* Fixed connecting Google Search Console with OAuth when "View Search Console data for your verified sites" was left unticked on Google's screen. SEO Utils now asks you to tick it, and reconnecting an account now replaces its old sign-in.
* Fixed Bulk Analysis CSV exports: the Lost Date column was always empty, two exports started together mixed their rows, and on Windows every export left a temporary file behind.
* Fixed an HTML or PDF report export sometimes containing part of an earlier export that did not finish.
* Fixed emoji in long report exports turning into two "�" symbols.
* Fixed Open tracker, after Track in Rankings, opening the GSC Rank Tracker tab you used last instead of Keywords, where the new keywords are.

### v2.10.0

*Released Oct 15, 2026*

* Added the [GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker), a free rank tracker built on your own Search Console data: open a property and choose Rankings. The moment you add keywords, or rules that match queries or pages, you get up to 16 months of daily positions, with a position bands chart, a Grid view and a detail panel for each keyword.
* Added Movers and Alerts to the GSC Rank Tracker. Movers lists the keywords that really moved, an alert fires for each confirmed change with a desktop notification on Mac and Windows, and the new GSC Rank Tracker Alerts automation trigger sends them [by email or webhook](/guide/google-search-console/gsc-rank-tracker/alerts#send-alerts-by-email-or-webhook).
* Added Gemini as an engine in the [LLM Rank Tracker](/guide/llm-rank-tracker#ai-engines-selection). It asks the Gemini app, and each answer shows the Gemini model that wrote it, marked Model changed when the model differs from the previous check.
* Added Edit to the [search terms](/guide/llm-rank-tracker#managing-search-terms) of an LLM Rank Tracker report, so you can fix a typo without losing the term's tags. Past results stay under the old wording. You can now also add, edit and delete search terms from a browser over Remote Access.
* \[Agent Skills]: Added [AI Visibility actions](/guide/mcp-server#available-tools). AI apps can read your explorations' share of voice, the prompts where competitors win and the sources AI cites, and they show the price before any paid load.
* Improved the Location and Language fields of the [LLM Rank Tracker](/guide/llm-rank-tracker#location-and-language). They list every country and language an engine answers for, show which of your engines answer there, and turn off an engine that doesn't. The Track in LLM Rank Tracker dialog in AI Visibility uses the same fields.
* Improved Organic Rank Tracker reports with a Business Name so every rank, Diff and average is the organic one, with the [Local Pack position](/guide/organic-rank-tracker#local-pack-tracking) beside it in a green badge. Before, a Local Pack position replaced the organic rank on days the business was in the map results. A new Local pack column, filter and summary show where the business sits in the map results, and the CSV, PDF and webhook carry both positions.
* Fixed the Organic Rank Tracker dashboard and the Rankings Distribution keyword list taking minutes to load for large reports.
* Fixed an LLM Rank Tracker engine stopping for the rest of a run after one temporary error from the AI provider, such as a rate limit or a server error. Every AI feature now retries such errors, and the tracker keeps collecting the other answers.
* Fixed the SEO Utils window turning blank on Windows after it was restored from minimized, when Auto Index ran on a Search Console property with a very large number of URLs.
* Fixed Remote Access sign-in failing when several browser tabs were open, mostly on a plan with one seat. A sign-in that does not finish now shows a page with a Sign in again link instead of "invalid login callback".

### v2.9.0

*Released Oct 14, 2026*

* Added [CSV exports](/guide/ai-visibility#exporting-to-csv) to AI Visibility for prompts, shares & gaps, and citations. Each export shows its price first and reuses the results you already loaded.
* Added a branded [client report](/guide/ai-visibility#client-report) to AI Visibility, laid out on A4 pages. Export it as HTML or download a PDF on the desktop, or print it from the browser.
* Added AI Visibility to [Remote Access](/guide/ai-visibility#using-ai-visibility-in-the-browser), for the owner of the installation.
* Added the choice to run AI Visibility on your [rented DataForSEO credits](/guide/rent-dataforseo-api-key#use-your-credits-for-ai-visibility) instead of your own DataForSEO login. Turn on the AI Visibility API switch in the Renting DataForSEO API Key card.
* Added links to the AI Visibility help guide on its start page, in the exploration header and in onboarding.
* Added [keyword weights](/guide/organic-rank-tracker#keyword-weights) to Organic Rank Tracker, so the keywords that matter most to a client count for more. Average position, ranking coverage, visibility and the competition map count each keyword by its weight, and a keyword set to Track only is still tracked but no longer counted.
* Added a live progress bar to the GMB Rank Tracker, Organic Rank Tracker and LLM Rank Tracker report lists, so you can see which reports are running and how far along they are.
* Added Move to workspace to [GA4 properties](/guide/workspace#moving-data-between-workspaces). A moved property keeps its synced data and keeps syncing.
* Added a Usage Statistics card to Settings → General. SEO Utils now shares which tools you open and the days you use the app, never keywords, domains, URLs or report content, so we know what to improve next. It is on by default, and you can turn it off there at any time.
* \[Agent Skills]: Added keyword weights to the Organic Rank Tracker tools. AI apps can give keywords a weight when they [add them to a report](/guide/mcp-server#available-tools), and change the weight of keywords already in a report.
* Improved AI Visibility so Share over time is [kept for up to 2 weeks](/guide/ai-visibility#how-long-share-over-time-is-kept), which makes a Refresh in the following week much cheaper. A note under the chart gives the date of its numbers.
* Improved the brand review in AI Visibility: a brand name that is also a [common phrase](/guide/ai-visibility#review-the-brands-and-competitors), such as New Balance or Best Buy, now gets the suggestion to add a context term, so only answers about the brand are counted.
* Improved the AI model pickers so they list the models your own API key can use, read live from OpenAI, Anthropic, Gemini, OpenRouter and Ollama, and new models appear without an app update. A saved model the provider no longer lists or is retiring shows a warning and keeps working.
* Improved the expired license banner: Renew License Key now opens the [renewal page](/guide/manage-license-key#renew-your-license-key) with its renewal price, instead of the page for a new purchase.
* Fixed AI Visibility failing with "Try again later" on most of the [Overview](/guide/ai-visibility#overview) when an exploration had a topic or brands with several terms. Requests now stay within DataForSEO's size limit, and a count that would still be too large says "Too many conditions for this count" instead.
* Fixed the competition map in [Competitors Discovery](/guide/organic-rank-tracker#competitors-discovery-tab) being empty for Organic Rank Tracker reports with pixel tracking turned on.
* Fixed the Average Position chart on the [Organic Rank Tracker dashboard](/guide/dashboard/organic-rank-tracker#average-position-chart) moving later points to the wrong dates when a day had no data, and counting a keyword twice when it held the same best position in the organic results and the local pack.
* Fixed the reasoning effort you chose for OpenAI's GPT-5 models being ignored.
* Fixed the [DataForSEO Post Tasks](/guide/dashboard) card missing from the Dashboard when no task needed attention. It now always shows the total, collected and pending tasks.

### v2.8.0

*Released Oct 10, 2026*

* Added [AI Visibility](/guide/ai-visibility) under AI Era. It shows how often Google AI Overviews and ChatGPT name your brand next to its competitors, with the real prompts and answers where rivals win and the sites AI cites for each brand. It runs on your own DataForSEO login, shows the price before every paid load, and a repeat in the same week is free.
* Added [Saved SERP Pages](/guide/saved-serp-pages-storage#moving-your-saved-pages) to Settings → Storage & Sharing. You can move the saved SERP pages, which can take up many gigabytes, to another folder, an external drive or an S3 / R2 bucket. SEO Utils now also saves these pages compressed, about 70% smaller, and compresses the older ones in the background.
* Added [S3 / R2 Connections](/guide/s3-r2-connections) to Settings → Storage & Sharing. You enter a bucket's keys once, then pick the connection in S3 Cache, Saved SERP Pages and Log File Analysis instead of typing the keys in each place.
* Added your own domain to client report links. When your account has a [report domain](/guide/white-labeled-client-report#use-your-own-domain-for-client-reports), the Publish to client dialog shows the client link on that domain, plus the SEO Utils address, which always works.
* Added tag filtering to [Organic Rank Tracker exports](/guide/organic-rank-tracker#export-reports). The PDF and HTML export and the Overview chart follow the report's tag filter, and an automation's new Only Keywords Tagged setting lets a scheduled report cover only the keywords tagged for one client.
* Added OpenCode to Settings → MCP Server → [Connect an AI app](/guide/mcp-server#connecting-to-ai-assistants), with an Add to OpenCode button.
* \[Agent Skills]: Added a workspace choice to every action. AI apps can pass a workspace ID to run one action in another workspace, and an X-SEO-Utils-Workspace header keeps a connection in [one workspace](/guide/mcp-server#working-across-client-workspaces), also after it reconnects. Before, a reconnect followed the desktop app's workspace, so reports could be created in the wrong client's workspace.
* Improved Publish to client so the first publish of a large report takes about half the time, and a client who opens the report again downloads only the parts that changed. Large Organic reports also [open faster](/guide/white-labeled-client-report#keeping-the-report-up-to-date) for your clients.
* Improved Export as CSV in [Organic Rank Tracker](/guide/organic-rank-tracker#export-reports) so it lists exactly the keyword rows the Overview shows, with every filter applied: search, Tags, SERP Features, Search Intent, Competitors and the date range. On the Insights tab it exports the selected insight's list.
* Improved the Settings page so the menu on the left stays in place while you scroll through a long group of settings.
* Fixed every Gemini request failing in the AI features. SEO Utils now offers Gemini 3.8 Flash and Gemini 3.5 Flash-Lite, and reports and settings that used an older Gemini model now use Gemini 3.8 Flash.
* Fixed long SEO Utils tools being stopped after 60 seconds in Codex. [Add to Codex](/guide/mcp-server#connecting-to-ai-assistants) now gives them up to 15 minutes.
* Fixed the Add Property form in [Search Console](/guide/google-search-console#method-1-google-oauth-token) showing Google's raw error when Google refused your saved sign-in. It now asks you to reconnect your Google account, and reconnecting always gives SEO Utils a fresh sign-in.
* Fixed a [GMB Rank Tracker](/guide/google-my-business-rank-tracker/run-and-schedule#when-a-run-does-not-finish) run staying Running for up to a day, and skipping scheduled runs, when DataForSEO never created some of its grid searches. The run now stops after an hour without progress, and results that still arrive are imported into the snapshot.
* Fixed an error when you added competitors to an [Organic Rank Tracker](/guide/organic-rank-tracker#manage-competitors) report with a double click or from two places at once. The button now shows Adding... until it finishes.
* Fixed accented and non-Latin search terms in [N.A.P Finder](/guide/n.a.p-finder#manage-search-term-lists) lists showing garbled when you edited a list, for example café as cafÃ©.
* Fixed an automation's [Export PDF](/guide/automations#action-1-export-pdf) action being marked Failed about 20 minutes after it had already created the PDF, when the export window did not close. The PDF is now kept and the action succeeds.

### v2.7.0

*Released Oct 6, 2026*

* Added YouTube and Amazon as search engines in [Bulk Autocomplete](/guide/bulk-autocomplete#running-bulk-autocomplete). YouTube returns what people type in YouTube's search box, and Amazon returns what shoppers type in the Amazon store of the country you choose.
* Added [Check Amazon Volume](/guide/bulk-autocomplete#checking-amazon-volume) to Amazon reports in Bulk Autocomplete. It fills an Amazon Volume column with each suggestion's monthly search volume on Amazon, which you can sort, filter and export.
* Added Import from Search Atlas to [GMB Rank Tracker](/guide/google-my-business-rank-tracker/your-reports#import). It turns a Search Atlas Local Heatmaps CSV export into a new report with the same business, keywords and grid, ready for its first scan in SEO Utils.
* Added support for [Cloudflare Logpush files](/guide/log-file-analysis#getting-logs-from-cloudflare) to Log File Analysis, for sites on Cloudflare Workers or Pages that have no server access log. You can upload the files, or let SEO Utils fetch them on a schedule from your Cloudflare R2, Amazon S3 or other S3-compatible bucket.
* Added Stop waiting to SERP Clustering and LLM Rank Tracker reports whose run is only [waiting for DataForSEO results](/guide/dataforseo-task-monitor#late-results-are-imported-automatically). It finishes the report with the results that already arrived, so you can run it again right away.
* \[Agent Skills]: Added [Internal Links actions](/guide/google-search-console/internal-links#use-it-from-an-ai-assistant). AI apps can read Internal Links opportunities and suggestions with `read_action`. With `write_action` they can start Find links, accept or reject suggestions, and apply or revert links on WordPress.
* Improved Import from True Ranker in [Organic Rank Tracker](/guide/organic-rank-tracker) so it also accepts the CSV that a single True Ranker campaign exports, not only the account-wide keywords export.
* Improved Publish to client so you can [add a password](/guide/white-labeled-client-report#adding-a-password) before the first publish. The first version your client can open is then already protected.
* Improved Publish to client so [Publish now](/guide/white-labeled-client-report#publishing-a-report), Unpublish and Delete published copy no longer wait behind other reports' automatic publishes.
* Improved [Content Struct](/guide/content-struct) to use the newest saved SERP of a keyword when its new search fails or DataForSEO can't deliver the result. Before, the report failed or waited up to 2 hours. The run's output log says which day's SERP was used.
* Improved [N.A.P Finder](/guide/n.a.p-finder) so a search term whose new search failed keeps its newest earlier results, and the run says how many terms show results from an earlier scrape. Terms that were searched again show only that run's results.
* Improved [SERP Extractor](/guide/serp-extractor) and Bulk Google PAA so you can delete a report while its run is still going or being recovered. Before, you were asked to wait for the run to finish. The run now stops.
* Improved Run and Cancel in a browser over [Remote Access](/guide/remote-access#what-works-in-the-browser) while SEO Utils is busy saving data, restarting, or pausing background work during a backup or an update. The browser now waits longer and then asks you to try again in a moment, instead of showing an error such as "database is locked".
* Improved error messages across the app: they no longer start with "RuntimeError:".
* Fixed SEO Utils closing at startup without any message when part of its database was damaged, as some Windows users saw after updating to 2.6.0. The app now opens with the rest of your data and shows a banner that explains what to do. An error it can't recover from now shows a message before the app closes.
* Fixed a [N.A.P Finder](/guide/n.a.p-finder) run that finished with a few gaps showing as Failed. It now shows Completed with gaps, and a failed run tells you to run the N.A.P Finder again only once.
* Fixed SERP Clustering and LLM Rank Tracker reports staying locked for up to 3 days when DataForSEO failed one of their tasks on its side. Such a task now [fails](/guide/dataforseo-task-monitor#task-states) at once, and the run finishes with the results that arrived.
* Fixed [Google Business Reviews](/guide/google-business-reviews-fetcher#snapshots-history-table) fetches staying in Processing for up to 30 days when DataForSEO failed the check or never returned it. The snapshot now fails with the reason so you can fetch again, and SEO Utils downloads results that DataForSEO still holds for up to 30 days instead of about 3.
* Fixed [automation runs](/guide/automations#monitoring-automation-history) staying Running forever when SEO Utils was closed during the run or an Export PDF action never finished. An interrupted run is now marked Failed at the next start, and an export that doesn't finish within about 20 minutes fails with the reason, so you can retry it.
* Fixed a burst of error messages, one per URL, when Google refused a Search Console property's saved sign-in during the [automatic URL inspection](/guide/google-search-console/indexing-dashboard#url-inspection). The inspection now stops and shows one message asking you to reconnect your Google account.
* Fixed problems with a published report that you moved with Move to Workspace. The [Publish to client](/guide/white-labeled-client-report#publishing-status) dialog showed Not shared while the client link stayed live, and new runs were not published. The publication now moves with the report.
* Fixed a published report that was held after you restored a backup having no way to publish again. [Publish now](/guide/white-labeled-client-report#publishing-status) now replaces the published copy with this computer's data.
* Fixed the Publish to client dialog showing an old [client link](/guide/white-labeled-client-report#sharing-the-link) after you rotated or revoked the link in your cloud account. It now shows the current link, or no link.
* Fixed saved filters with accented or non-Latin characters coming back garbled after a reload, so they no longer filtered anything. One example is an ignored domain such as café.com in Organic Rank Tracker's [Competitors Discovery](/guide/organic-rank-tracker#competitors-discovery-tab). Published client reports also apply these filters correctly now.
* Fixed the Daily Mentions by Top Domain chart on the [LLM Rank Tracker](/guide/llm-rank-tracker#citation-analysis-charts) Citations tab showing its days out of order.
* Fixed the [SERP Extractor](/guide/serp-extractor) reports list showing Pending after a restart for a report that was still waiting for its DataForSEO results, while the report's page showed it running.
* Fixed a [GMB Rank Tracker](/guide/google-my-business-rank-tracker) run that kept sending its grid searches to DataForSEO, and spending credits, after you deleted its report or snapshot during the run. The run now stops.
* Fixed the run panel in a browser over [Remote Access](/guide/remote-access#what-works-in-the-browser) offering Cancel after a run had already sent its paid DataForSEO request, when clicking it only showed an error. Cancel now shows only while the run can still be cancelled.
* Fixed an [Organic Rank Tracker](/guide/organic-rank-tracker) run started in a browser over Remote Access looking idle while it waited in line. The report now shows the run in progress, with Cancel run in the browser, and the desktop app no longer starts a second run of the same report, which made the browser run fail.

### v2.6.0

*Released Sep 27, 2026*

* Added **Publish to client** to Organic Rank Tracker, GMB Rank Tracker and LLM Rank Tracker reports. It [puts a read-only copy of a report online at a private link](/guide/white-labeled-client-report) that your client opens in any browser, optionally with a password, and can publish a new version automatically after each run. It needs Remote Access with the Agency plan.
* Added Import from Local Brand Manager to [GMB Rank Tracker](/guide/google-my-business-rank-tracker/your-reports#import), which turns one or more Local Brand Manager CSV exports into a new report with its geogrid scan history, competitors and ranking metrics.
* Added more ways to build seeds in [Bulk Autocomplete](/guide/bulk-autocomplete#running-bulk-autocomplete): letters a–z and question words per seed group, excluded words, a filter that keeps only suggestions matching your `*` pattern, and an estimate of the lookups before you run. Reports show which kind of seed each suggestion was found from, and you can filter by it.
* Added [Generate seeds with AI](/guide/bulk-autocomplete#generating-seeds-with-ai) to Bulk Autocomplete: get related keyword ideas for a topic, or fill a template such as "best {breed} food" with a list from AI or your own.
* Added a Connect an AI app picker to the [MCP Server](/guide/mcp-server#connecting-to-ai-assistants) settings. It shows how to connect SEO Utils and add its skill for Claude Desktop, Claude Code, OpenAI Codex, Cursor, VS Code, Google Antigravity, Grok Build, OpenClaw, Perplexity, ChatGPT and other apps, with one-click installs where the app supports them.
* Added a Delete Reports bulk action to the [GMB Rank Tracker](/guide/google-my-business-rank-tracker/your-reports#row-and-bulk-actions) reports list.
* Added quick actions to the Cmd+K search: switch workspace, theme or sidebar layout, start a new report in most tools, add proxies and more, without leaving the keyboard.
* \[Agent Skills]: Added the `delete_gmb_rank_tracker_reports` action (run with `write_action`), which deletes up to 100 GMB Rank Tracker reports in one call.
* Improved the Cmd+K search to rank results by how well they match and tolerate small typos, to find every setting, and to find your saved reports, projects and properties by name.
* Improved [LLM Rank Tracker](/guide/llm-rank-tracker#brand-variants) to show your brand as one "(You)" row in competitors, sentiment and citations, whichever of its names an answer used, and to let you choose the main brand name. A brand name now matches only as whole words, and an answer that names your brand twice counts once.
* Improved Install in Claude Desktop (formerly Auto Install) in the [MCP Server](/guide/mcp-server#connecting-to-ai-assistants) settings: it no longer needs Node.js, Claude Desktop reconnects by itself when it was opened before SEO Utils, and rotating the MCP auth token no longer breaks it. Click Install in Claude Desktop again to switch an existing setup.
* Improved how DataForSEO results are downloaded: several tasks are now fetched at once, so a large run, such as a [SERP Clustering](/guide/serp-clustering) report of thousands of keywords, no longer stalls behind other tools' results.
* \[Agent Skills]: Improved the MCP server to offer its actions through a searchable catalog instead of 76 separate tools, so AI apps load about 2,800 tokens before your first question instead of about 40,000. Agents find an action with `search_actions` and `describe_action`, and run it with `read_action` (reads your data, free), `lookup_action` (may spend DataForSEO credits) or `write_action` (changes your data), so your AI app can run reads without asking and ask before a paid lookup or a change.
* \[Agent Skills]: Improved the SEO Utils skill: it's rewritten for the new actions and is now a Claude plugin. Add it with `/plugin marketplace add seoutilsapp/seo-utils-skills` in Claude Code, or from Customize → Plugins in Claude. Other apps get it from Install skill in the [MCP Server](/guide/mcp-server#connecting-to-ai-assistants) settings, and Update skill copies in What's New refreshes the copies on your computer.
* Fixed DataForSEO results that arrived after a run was interrupted (the app was closed, crashed or stopped waiting) never being imported in GMB Rank Tracker, Google Business Reviews, LLM Rank Tracker, SERP Clustering, SERP Extractor, Google PAA and N.A.P Finder. They are now imported automatically, SERP Clustering finishes its clusters after a restart, and tasks that can no longer be imported are cleared from the [DataForSEO Task Monitor](/guide/dataforseo-task-monitor).
* Fixed the [DataForSEO Task Monitor](/guide/dataforseo-task-monitor#the-four-counters) showing results that had already arrived as Waiting on DataForSEO or Needs confirmation, and reporting a collector that was still working as not running.
* Fixed Claude Desktop disconnecting from the [MCP Server](/guide/mcp-server#troubleshooting) with "SSE stream disconnected" when it was idle or a tool call ran longer than 5 minutes.
* Fixed the Search Intent filter on the [Organic Rank Tracker](/guide/organic-rank-tracker) Overview being ignored, so every keyword was still listed. The Positions CSV export now follows it too.
* Fixed [Search Console](/guide/google-search-console) showing a site's sub-folder properties under the same domain name. URL-prefix properties now show their full URL, as Google Search Console does.
* Fixed sitemaps served as a file download, as Shoper stores do, failing to load in the Sitemap Extractor and the [Indexing Dashboard](/guide/google-search-console/indexing-dashboard).
* Fixed Search Console embeddings failing without saying why. The error now names the cause, for example that Ollama could not be reached or the provider rejected the [embedding](/guide/embedding-database) API key.
* Fixed a [GMB Rank Tracker](/guide/google-my-business-rank-tracker/read-a-report) report saying "There are no snapshots in this report" while its snapshots were loading or none was selected.
* Fixed the "Updated" tooltip on scheduled [LLM Rank Tracker](/guide/llm-rank-tracker#understanding-the-report-header) reports failing to show the next run.
* Fixed the Sentiment Analysis by Brand table in [LLM Rank Tracker](/guide/llm-rank-tracker#sentiment-analysis-by-brand-table) stopping at 50 brands, and a competitor's latest position counting results from other reports.
* Fixed wildcard seeds in [Bulk Autocomplete](/guide/bulk-autocomplete) that contain accented or non-Latin letters.
* Fixed links in the app failing to open on some Macs with "Failed to open URL … executable file not found".

### v2.5.0

*Released Sep 22, 2026*

* Added [Internal Links](/guide/google-search-console/internal-links) to Google Search Console. It finds the pages that need more links pointing to them, suggests the exact sentence and link text for each new link, and can apply accepted links to WordPress and revert them.
* Added Search Intent Bulk Check under Utilities, which labels any list of keywords with its search intent without spending DataForSEO credits. It uses a TypeSafe API key, which you can add in Settings.
* Added a keyword data source selector to Keyword Explorer, so you can [search with Google Ads live](/guide/keyword-metrics-data-source#the-keyword-explorer-search) and get search volumes and keyword ideas the DataForSEO Labs database does not have.
* Added Import from True Ranker, Import from SEO PowerSuite and Import from Agency Analytics to [Organic Rank Tracker](/guide/organic-rank-tracker), bringing over rank history, ranking pages and Local Pack positions where the export includes them.
* Added [Reuse SERPs for Word-Order Twins](/guide/serp-clustering#reuse-serps-for-word-order-twins) to SERP Clustering. When it is on, keywords with the same words in a different order, such as "laravel horizon" and "horizon laravel", share one scraped SERP to save costs.
* Added an "Update available" button in the sidebar, so you can see that a new version is out without opening the Dashboard.
* \[Agent Skills]: Added an optional source parameter to the `get_keyword_suggestions` tool, allowing agents to search with Google Ads live.
* \[Agent Skills]: Added a `reuse_word_order_twins` option to the `create_serp_clustering_report` and `run_serp_clustering` tools.
* Improved SERP Clustering so re-clustering the same keywords with the same SERP data and settings always [gives the same clusters](/guide/serp-clustering#consistent-results).
* Improved the [SERP Clustering](/guide/serp-clustering) progress bar to move as each keyword is scraped, instead of jumping only at the end.
* Improved adding [Search Console](/guide/google-search-console) properties: you no longer have to wait for one property's first sync to finish before adding the next. New properties wait in line for their first sync, and the Performance page shows their place in the queue.
* Improved [Search Console](/guide/google-search-console) background tasks (data sync, embeddings, keyword metrics checks and branded queries) to show their progress and whether they finished or failed, including over Remote Access.
* Improved Search Console property settings with a section menu, so every setting has one place.
* Improved rank history imports in [Organic Rank Tracker](/guide/organic-rank-tracker) to ask for the target domain, pre-filled from the file, and to warn when the chosen SERP depth is lower than the imported rankings.
* Improved the [Custom Polygon Grid](/guide/google-my-business-rank-tracker/create-a-report#draw-an-area) in GMB Rank Tracker to show how many pins fit at the chosen spacing, and to suggest a spacing when none or too many fit.
* Fixed Keyword Explorer showing a "No keyword data!" error and cards that never finished loading for keywords the [DataForSEO Labs database](/guide/keyword-metrics-data-source#the-keyword-explorer-search) does not have. Each card now shows the data that is available.
* Fixed the "keywords lack SERP data" alert appearing in [SERP Clustering](/guide/serp-clustering) while a run was still in progress.
* Fixed Generate Pins placing one pin or none on a [Custom Polygon Grid](/guide/google-my-business-rank-tracker/create-a-report#draw-an-area) after switching from Radius, and Random placing pins unevenly.
* Fixed the [Search Console](/guide/google-search-console) properties table showing only the first 25 properties. The Rankings in Top 3/10/20/100 tables in Organic Rank Tracker had the same limit.
* Fixed [Search Console](/guide/google-search-console) charts that could show figures from before the latest sync for up to a day, and a re-added property that could show the deleted property's data.
* Fixed the [SERP features](/guide/organic-rank-tracker#serp-features-tracking) column in Organic Rank Tracker showing a dash, and the SERP panel opening empty, when the date range started in imported SE Ranking history.
* Fixed the [DataForSEO Balance](/guide/dashboard#dataforseo-balance) card on the Dashboard showing a wrong, large negative balance when Sandbox Mode is on. It now shows your live balance and reminds you that Sandbox Mode returns dummy data.
* Fixed a finished [Bulk Check Mentions](/guide/bulk-check-mentions) report showing as Failed after the app was restarted.
* Fixed Test Provider in the [LLM Rank Tracker](/guide/llm-rank-tracker) extraction settings failing with "no response received" for GPT-5 Mini, even when the API key was valid.
* Fixed a [licence](/guide/manage-license-key) check on Windows and Linux that could refuse a valid licence after the computer was renamed or moved to a new server, and the MCP server telling customers with a valid licence to renew.
* Fixed keyword metrics from a paid check sometimes not being saved when the app was busy writing other data.

### v2.4.0

*Released Sep 16, 2026*

* Added the ability to choose from [six DataForSEO sources for keyword metrics](/guide/keyword-metrics-data-source), including DataForSEO Labs, Google Ads Live, clickstream-normalized, Bing-normalized, DataForSEO Search Volume, and Clickstream Bulk.
* Added a default keyword metrics source setting, with descriptions and pricing for each source.
* Added the ability to choose the keyword metrics source for each check, including Bulk Keyword Analysis.
* Added the ability to set a different keyword metrics source for each Google Search Console property.
* Added source and month labels to search volume data, including “No data” when the selected source has no data and “Imported” for manually imported volumes. Missing search volume now displays as a dash instead of 0.
* Added the ability to filter and sort keywords by volume source across Organic Rank Tracker, Saved Keywords, SERP Clustering, SERP Extractor, Bulk Autocomplete, Check Mentions, Keyword Explorer, and Search Console.
* Added a Volume Source column to CSV and Excel exports.
* \[Agent Skills]: Added an optional source parameter to the `check_keyword_metrics` tool, allowing agents to choose which keyword metrics source to use.
* Added automatic saving of keyword metrics received by Content Gap and Ads Vision, making the data available across other SEO Utils tools.
* Improved Search Console automatic keyword metrics checks by spreading them throughout the month, with each keyword rechecked every 30 days instead of checking everything on the first day of the month.
* Improved LLM Rank Tracker performance by loading citation URLs page by page when expanding a domain, preventing domains with thousands of URLs from slowing down the app.
* Fixed a `goto URL` issue caused by a Google change where Organic Rank Tracker and SERP tools using a proxy or your own IP could report keywords as not ranked, skip search results, or save People Also Ask questions without source URLs.
* Fixed an issue on Windows where the app could silently close on every launch after a failed update restart. Opening SEO Utils while it is already running now brings the existing window to the front.
* Fixed recent searches in Keyword Explorer, Traffic Analytics, Backlink Analytics, Content Gap, and Backlink Gap appearing across different workspaces instead of staying within their own workspace.
* Fixed date filters in LLM Rank Tracker and Organic Rank Tracker showing incorrect days or missing snapshots.
* Fixed unchecked Search Console keywords incorrectly showing a keyword difficulty of 0.
* Fixed the “Only Check Keywords Missing Search Volume Data” option in SERP Clustering and Check Mentions to correctly include keywords with imported search volume.
* Fixed keyword metrics checks removing existing data from keywords that are too long to check.
* Fixed Organic Rank Tracker page links saved without `https://` opening the wrong website.

### v2.3.0

*Released Sep 10, 2026*

* Added [custom domains for Remote Access](/guide/remote-access#using-your-own-domain) with the Agency plan.
* Added a [Progress view for GMB Rank Tracker](/guide/google-my-business-rank-tracker/history#date-ranges) to compare grid rankings across multiple date ranges.
* Fixed Organic Rank Tracker runs getting stuck when DataForSEO credentials are missing.
* Fixed Remote Access reaching its rate limit earlier than intended.
* Fixed unnecessary error alerts on Macs when the computer is sleeping or temporarily busy.

### v2.2.0

*Released Sep 9, 2026*

* Added [Remote Access](/guide/remote-access), allowing you to open SEO Utils from a browser on your phone or another computer while your data stays on your machine and runs keep going.
* Added per-report run logs with a View Log button for long-running tools. Logs are automatically removed after 30 days.
* Added a shared run-status panel across tools, including LLM Rank Tracker and GMB Rank Tracker. GMB Rank Tracker runs are now more reliable and can recover properly from interruptions.
* Added progress feedback for bulk actions and the Content Struct fetching process.
* Added the ability to deactivate your licence directly from the desktop app, including a warning when the licence has expired.
* Improved the SERP Data Importer to run in the background and correctly replace existing SERP data by local day.
* Improved SERP Clustering so creating a report and running it are handled as a single background job.
* Improved action menus across reports with one primary action and the remaining options grouped under an Actions menu.
* Improved the N.A.P Finder detail panel with Check SERP and Analyze actions on desktop.
* Fixed OpenRouter provider verification when configuring or onboarding an AI provider.
* Fixed an issue where ChatGPT and ChatGPT Web Search results in LLM Rank Tracker could overwrite each other’s responses, positions, and citations.
* Fixed an issue where LLM Rank Tracker could incorrectly show a run as completed when its configured AI engine was missing.
* Fixed Keyword Fluctuation comparisons for the past 1, 7, and 30 days. The 1-day comparison could incorrectly compare a keyword against itself and show a 0 change.
* Fixed Past N Days comparisons that could incorrectly use only a single day for trackers running on a weekly schedule.
* Fixed empty snapshots being left behind when a rank-tracking run failed because of issues such as insufficient DataForSEO balance, scraping errors, or the app being closed during a run.
* Improved failed rank-tracking runs to show the specific cause in the run panel, including insufficient funds, invalid credentials, and rate limits.
* Fixed the LLM Rank Tracker search-term tag filter.
* Fixed the Organic Rank Tracker SERP ID handling used by N.A.P Finder.

### v2.1.1

*Released Aug 31, 2026*

* Added ranked-page HTML tracking and comparison to the Organic Rank Tracker, making it easier to see how a ranking page changes over time.
* \[Agent Skills]: Added the ability for AI agents to compare ranked-page HTML changes through the Organic Rank Tracker.
* Added additional security protections for automation webhooks, workspace access, and Google Search Console authentication.
* Added support for the standard macOS shortcut to close the app window.
* Improved SERP data handling to automatically resolve Google `goto` URLs to their actual destination URLs.
* Improved Organic Rank Tracker reliability when reports are interrupted or encounter unexpected lifecycle issues.
* Improved database reliability when multiple operations are running at the same time.
* Fixed GMB Rank Tracker demographic grid exports not always matching the correct grid data.
* Fixed OpenRouter provider verification.
* Fixed indexing data issues that could occur when records were deleted while an indexing operation was still running.
* Fixed an issue where stale macOS app bundles could cause problems after an update.

### v2.1.0

*Released Aug 10, 2026*

* Added the ability to [recover already-paid DataForSEO SERP results](/guide/manage-serp-data#dataforseo-serp-data-getter) directly into Organic Rank Tracker reports, restoring missing rankings to their original dates without paying to run the keywords again.
* Added a new [DataForSEO Task Monitor](/guide/dataforseo-task-monitor).
* Added a live Organic Rank Tracker run-status panel showing the run status, trigger, reference date, and progress for each keyword, including completed, failed, capped, and still-processing keywords.
* Improved Organic Rank Tracker DataForSEO runs so already-paid tasks are preserved and can continue collecting results even when the standard queue takes several hours.
* Improved protection against duplicate DataForSEO charges by limiting automatic submissions, preserving uncertain submissions instead of automatically retrying them, and requiring confirmation before an additional paid retry.
* Improved recovery from app restarts and interrupted DataForSEO runs. Pending tasks can resume automatically instead of losing already-paid results.
* Improved SERP data settings layout for smaller windows.
* Improved the Organic Rank Tracker date filter so it automatically follows newly completed snapshots while preserving manually selected or historical date ranges.
* Fixed an issue where zero-result SERPs could cause Organic Rank Tracker keywords to be repeatedly submitted.

### v2.0.4

*Released Aug 6, 2026*

* Improved the update process when reports or bulk actions are still running. SEO Utils now shows which tasks are active and lets you choose to wait for them or update immediately and re-run any interrupted tasks afterward.
* Fixed tasks that failed early sometimes remaining marked as running indefinitely.
* Fixed newly added competitor domains in Organic Rank Tracker getting stuck on “Calculating…” after their data finished syncing.
* Fixed an issue where pausing background work for an update, backup, or restore could accidentally resume another paused operation too early.

### v2.0.3

*Released Aug 5, 2026*

* Added bulk actions for the Organic Rank Tracker list. You can now delete multiple trackers at once or add the same keywords to multiple trackers in a single step.
* Fixed an issue where switching workspaces while the app was busy could occasionally cause data to be read from or saved to the wrong workspace.
* Fixed an issue where deleting an Organic Rank Tracker did not remove all of its associated data.

### v2.0.2

*Released Aug 5, 2026*

* Fixed an issue where the MCP server could stop responding about 15 minutes after startup. Tool requests now either complete successfully or return a clear timeout instead of hanging indefinitely.
* Fixed an issue where Google Search Console, Google Analytics, Google Drive, and Google Docs requests could hang indefinitely if Google stopped responding.
* Fixed an issue where app settings could be left partially saved if a disk write was interrupted.
* Fixed an issue where sending an email could hang indefinitely when an attachment was unavailable.
* Fixed an issue where requesting autocomplete keywords with an invalid limit could return the entire database instead of a single page of results.
* Fixed an issue where the app could freeze on macOS with an unresponsive “Move to Applications” prompt on first launch after downloading.
* Improved license validation so a temporary network issue no longer signs you out.

### v2.0.1

*Released Aug 4, 2026*

{% hint style="warning" %}
**macOS users: please download this version manually — one time only.** The updater in earlier versions cannot install v2 releases on macOS. Get the new version from [your downloads page](https://app.seoutils.app/downloads?key=%5Byour-license-key%5D), install it, and automatic updates will work again from then on. Windows and Linux users can update from inside the app as usual.
{% endhint %}

* Fixed macOS updates breaking the app when a release changed more than the app's core file. The updater now downloads the complete app, verifies it is genuine and correctly signed before installing, and keeps your previous version as a backup until the new one starts successfully.
* Improved update safety on all platforms. The app now refuses updates that would install an older version, and rejects downloads that fail verification.

### v2.0.0 🎉🎉🎉

*Released Aug 4, 2026*

* Added the SEO Utils v2's foundation 🔥.
* Added business-hours scheduling for the [Organic Rank Tracker](/guide/organic-rank-tracker). You can now choose the tracking time window, timezone, and days of the week for each report, just like the GMB Rank Tracker.
* Added the ability to rotate the MCP Server authentication token.
* Added bulk bot classification for the [Log File Analysis tool](/guide/log-file-analysis). Review all newly detected bots in one dialog, paste an AI-generated classification, and confirm the entire batch with a single click.
* Added the ability to manually refresh sitemap URLs with the new Fetch URLs action.
* Added a Last Fetched column to the Sitemaps page so you can quickly see when each sitemap was last updated.
* Improved the data freshness widget so the Refresh button is no longer shown immediately after data has been updated, helping prevent accidental paid re-fetches.
* Fixed the Sitemap tool so URLs are fetched immediately after adding a sitemap instead of waiting until the next day.

### v1.48.1

*Released July 24, 2026*

* Added the ability to rename saved keyword lists.
* Added a "Track disappearing reviews" option to Review Fetcher. Turn it on to fetch a business's complete review list on every run so removed reviews can be detected. It can also be set when creating a business through the MCP server.
* Added a Visibility Status column to Review Fetcher exports, showing whether each review is new, visible, missing or reinstated.
* Fixed an issue where Organic Rank Tracker could show the wrong page URL when a keyword ranked with multiple pages.
* Fixed an issue where some Google Business Profile reviews were incorrectly reported as disappeared from Google.
* Fixed Review Fetcher exports ignoring the filters and view toggle shown on screen, so the downloaded file did not match the table.
* Fixed reviews collected earlier disappearing from the Review Fetcher review list after a later, smaller fetch.
* Fixed a review that was edited or retranslated after it was first collected being reported as a brand new review, which triggered new-review alerts and automations.
* Fixed an issue where Organic Rank Tracker and GMB Rank Tracker reports could get stuck on “Running…” with an empty log and no new data.

### v1.48.0

*Released July 7, 2026*

* Added the ability for AI assistants to run NLP text and entity analysis through the MCP server.
* Added the ability for AI assistants to create and run SERP Clustering reports through the MCP server.
* Added the ability for AI assistants to create Content Struct reports and generate AI content outlines through the MCP server.
* Added workspace support for MCP tools. AI assistants can now work inside a selected workspace, and that workspace applies to every MCP tool, report list, and status check.
* Added the ability to set up and run Google Business Profile review tracking through the MCP server.
* Added the ability to identify businesses by pasting a Google Maps link when setting up review tracking.
* Added the ability to create and run LLM Rank Tracker reports through the MCP server.
* Added the ability to edit Brand Variants on an existing LLM Rank Tracker report. Historical data is recalculated automatically without re-querying AI engines.
* Fixed automations and exports only running for reports in every workspace, not just the currently opened one.
* Fixed Review Fetcher hanging forever when DataForSEO fails to return results.
* Fixed the MCP server always returning an empty list for LLM Rank Tracker reports.
* Fixed MCP report-list errors being silently ignored.
* Fixed LLM Rank Tracker running while DataForSEO sandbox mode is enabled, which could save test data into snapshot history.
* Fixed LLM Rank Tracker citation metrics undercounting brand citations when AI responses spell the brand differently from the configured variants.

### v1.47.7

*Released Jun 29, 2026*

* Added search in the workspace switcher so you can quickly find the workspace you need.
* Added alphabetical sorting in the workspace switcher to make long workspace lists easier to manage.
* Fixed the “View on Google” links in Review Fetcher reviews not opening when clicked.
* Fixed Search Console properties repeatedly syncing when using multiple workspaces. They now sync once per day as expected.
* Fixed Scheduled Organic Rank Tracker reports re-running every day when using multiple workspaces. They now follow the configured “Rerun Every X days” schedule correctly.
* Fixed the demographics layer on the Google Business map not showing data for US locations.

### v1.47.6

*Released Jun 11, 2026*

* Added support for timestamp-first access log formats in the [Log File Analysis tool](/guide/log-file-analysis).
* Improved the Sitemap Extractor tool with a new results view that shows extracted URLs directly in the app, including stats, site section breakdowns, filtering, copy, and CSV export options.
* Fixed an issue where People Also Ask and SERP scraping could freeze the app until Force Quit.
* Fixed an issue where disabling the MCP Server could show a false error when a client was still connected.
* Fixed internal error handling warnings to improve app stability.

### v1.47.5

*Released Jun 9, 2026*

* Fixed the GMB Rank Tracker map editor showing only “Failed to load Google Maps” after Google removed the Maps Drawing library.
* Restored the map drawing tools in GMB Rank Tracker, including Shift + drag to select grid points and Polygon mode for drawing custom areas.
* Improved the Google Maps error message to explain common setup issues, such as an invalid Google Places API key, Maps JavaScript API not being enabled, inactive billing, or referrer restrictions.

### v1.47.4

*Released Jun 4, 2026*

* Added the ability to filter Organic SERP Extractor results by domain.
* Improved the app update warning when bulk operations are still running. The message now shows which reports are still running instead of only showing a generic warning.
* Fixed the Submit Index action showing “Successfully submitted 0 out of N URLs for indexing” without explaining why no URLs were submitted.
* Fixed grouped table headers in reports such as the Organic Rank Tracker Overview, where domain heading rows like “Pos. example.com” did not display correctly.
* Fixed Bing index checks incorrectly reporting every page as “Not Indexed” when using the Bing Webmaster Tools API.
* Fixed sitemap extraction failing on Cloudflare-protected sites with the “invalid exec pool flag” error.
* Fixed the formatting issue in the “What’s new in v…” modal where bullet points with inline links were displayed incorrectly.

### v1.47.3

*Released May 27, 2026*

* Added a drag-and-play [timeline scrubber to the Organic Rank Tracker Competitors Discovery map](/guide/organic-rank-tracker#competitors-discovery-tab).
* Added drag-and-drop card reordering on the Google Search Console Insights tab.
* Added undo and redo for marker edits on the GMB Rank Tracker grid map.
* Added native desktop notifications support.
* \[Agent Skills]: Added the ability to remove keywords from Organic Rank Tracker reports via Claude Desktop or any MCP client.
* Redesigned the Settings → Services page with left navigation and instant search.
* Improved DataForSEO error messages and retry behavior across tools that use the DataForSEO API.
* Fixed SEO Utils hanging on startup on Windows, causing very high CPU usage and sometimes filling the C: drive with temporary files.
* Fixed Organic Rank Tracker reports with pixel tracking enabled running a full SERP rescan every day instead of following the report schedule.
* Fixed two crashes when sorting tables in the LLM Rank Tracker.
* Fixed the first-time setup error in Embedding Settings when loading the embedding model list.
* Fixed shrunken icons and clipped category labels in the global command palette when item titles are very long.
* Fixed IndexNow failing when Bing Webmaster Tools has not crawled a URL yet.

### v1.47.2

*Released May 15, 2026*

* Added the ability to [create and update Organic Rank Tracker reports](/guide/mcp-server#create-and-update-organic-rank-trackers) from Claude Desktop or any MCP client.
* Added the ability to [create, update, and run GMB Rank Tracker reports](/guide/mcp-server#create-and-update-gmb-rank-trackers) from Claude Desktop or any MCP client.
* Added the ability to [create and update SEO Tests](/guide/mcp-server#seo-tests) from Claude Desktop or any MCP client.
* Added the ability to [create and rename workspaces](/guide/mcp-server#workspaces) from Claude Desktop or any MCP client.
* Added a test connection button on the MCP Server settings page.
* \[Agent Skills]: Added GMB Rank Tracker grid visualization support with Leaflet maps for MCP clients.
* Fixed the UULE Geo Target encoding issue when using certain location names in in-app SERP scraping.
* Fixed GMB Rank Tracker grid queries in Claude Desktop showing the “no such column: disabled” error.
* Fixed “Last updated” timestamps not refreshing after saving edits.
* Fixed exported PDF and HTML reports missing maps or lazy-loaded content.
* Fixed automated GMB Rank Tracker exports failing on the first attempt or generating incomplete reports.
* Fixed the app crash or launch failure when the network is slow during startup or on some Linux systems.

### v1.47.1

*Released May 12, 2026*

* Added the ability to [track pixels from the top in Organic Rank Tracker](/guide/organic-rank-tracker#pixels-from-top-display) to measure real on-screen visibility, not just ranking position.
* Added a copy service account email button on the GA4 add property page.
* Improved the N.A.P Finder run form to open as a full page instead of a cramped modal.
* Improved the Organic Rank Tracker create and edit forms to open as full pages instead of cramped modals.
* Fixed the Indexing Pages “Select all” and CSV export actions ignoring active filters.
* Fixed the average position change in SEO Test time-based performance overview showing as an improvement when the position got worse.
* Fixed the confusing database error when adding a GA4 property that already exists in another workspace.
* Fixed the issue where Google AI Mode could not be deselected in LLM Rank Tracker when a non-English language is selected.
* Fixed Linux WebKit signal override issue.
* Fixed links in the “What’s new” release notes popup not opening.
* Fixed the updater restart and progress state.

### v1.47.0

*Released May 5, 2026*

* Added [People Also Ask source tracking](/guide/organic-rank-tracker#paa-source-tracking) for the Organic Rank Tracker.
* Added a new card view for GMB Rank Tracker reports and report groups.
* Added workspace support for Google Analytics (GA4) properties.
* Added [Recent Searches and Local Cache](/guide/recent-searches-and-cache) for DataForSEO tools.
* Added a macOS prompt on first launch to move SEO Utils to the Applications folder.
* Added a Geo Target field in SERP Similarity when adding a keyword.
* Added bulk export for NLP Text Analysis reports, allowing users to download all items as a ZIP file with per-article Excel files.
* Added an onboarding page with a guided setup checklist.
* Added a “What’s new” release notes popup on the Dashboard with Agent Skills updates.
* Added [Organic Rank Tracker write tools](/guide/mcp-server#organic-rank-tracker) for MCP.
* Added [Log Analyzer AI ](/guide/mcp-server#ai-log-analysis-aeo-geo)upgrade support for MCP.
* Added a custom Chrome executable path setting.
* Improved [Log File Analysis with AI View](/guide/log-file-analysis), robots.txt compliance, better bot buckets, source management, auto-import, and AEO dashboard data.
* Improved Log File Analysis by filtering static-asset noise and clarifying empty states.
* Improved Log File Analysis with persistent import logs, better error-log detection, CSV exports, and more reliable import recovery.
* Improved Log File Analysis parser support for Combined-format logs.
* Fixed LLM Rank Tracker scheduled runs repeating across workspaces.
* Fixed sitemap imports failing when URLs have empty, zero, or RFC1123 date values.
* Fixed IndexNow failing with an “invalid date format” error for users in positive UTC timezones.
* Fixed empty space below the MCP Server section when opening Settings via deep link.
* Fixed “-752 minutes ago” showing in Bot Activity Details.
* Fixed saving tags failing with a “database is locked” error under heavy activity.
* \[Agent Skills]: Updated the MCP guide so LLM pick the right tool and table when answering questions about the new [Log Analyzer AI features](/guide/mcp-server#ai-log-analysis-aeo-geo) — bot categories, log sources, AI request stats, robots.txt compliance, and AI traffic trends.

### v1.46.1

*Released Apr 17, 2026*

* Added the ability to select a Log Analyzer report for each property in the Indexing dashboard, with automatic matching as a fallback.
* Improved the initial scan experience in the Indexing dashboard with clearer live progress updates.
* Improved the link crawler to handle slow-loading websites more reliably.
* Changed the URLs button on the Sitemaps page to open the new Indexing dashboard.
* Fixed the sitemap errors banner showing an outdated 200 status.
* Fixed the repeated toast notification issue on the Sitemaps page.

### v1.46.0

*Released Apr 17, 2026*

* Added [GMB Report Groups](/guide/google-my-business-rank-tracker/report-groups) for multi-location businesses.
* Added the new [GSC Indexing Dashboard](/guide/google-search-console/indexing-dashboard).
* Added [MCP indexing support](/guide/mcp-server#url-indexing).
* Added MCP GMB Report Groups support.
* Added a collapsible filter panel mode for tables.
* Fixed tab switching flicker across all Tabs components.
* Fixed an issue where Insights Content and Topic Clusters cards only showed up to 6 rows.
* Fixed a silent validation error in polygon mode in the GMB Rank Tracker form.

### v1.45.0

*Released Mar 30, 2026*

* Added [Keyword Insights](/guide/organic-rank-tracker#insights-tab) with GA4 Key Events integration.
* Added [Google Analytics 4 integration](/guide/google-analytics-4)
* Added the [MCP Keyword Insights tools](/guide/mcp-server#keyword-insights) to get insight counts (trending up/down, pogo sticking, flickering, key events) for a organic rank tracker report.
* Added the MCP send email tool for sending emails via SMTP.
* Added the ability to import historical rank tracking data from SERanking.
* Added a [Manage Devices button](/guide/manage-license-key) on the license page with your license key and email prefilled.
* Improved Google Search Console property list loading speed.
* Fixed PDF export in Automations failing on Windows because of broken file paths.
* Fixed the Sitemap Extractor working on sites with bot protection such as Cloudflare.
* Fixed Windows detection for the Claude Desktop MSIX config path during Auto Install.
* Fixed the Keyword Fluctuation table columns not sorting correctly.
* Fixed Bing Keyword Explorer crashing with non-US locations.
* Fixed US/Canada demographics overlap for border locations.

### v1.44.1

*Released Mar 23, 2026*

* Fixed Windows Claude Desktop Install button.

### v1.44.0

*Released Mar 23, 2026*

* Added [MCP Server](/guide/mcp-server) with automation support and integrations across SEO tools.
* Added demographics support for Google Business Rank Tracker in [Canada, Australia, and the UK](/guide/google-my-business-rank-tracker/map-tools#demographics-layer).
* Fixed DataForSEO task collectors randomly stopping.

### v1.43.3

*Released Mar 16, 2026*

* Added [custom polygon grid shape](/guide/google-my-business-rank-tracker/create-a-report#draw-an-area) for the GMB Rank Tracker with support for random and grid-based pin distribution.
* Added automation support for Content Struct outline generation with Markdown and ZimmWriter export.
* Added [automatic detection and disabling of grid markers placed in uninhabited areas](/guide/google-my-business-rank-tracker/create-a-report#the-four-steps) in the GMB Rank Tracker.
* Fixed the issue where tabs on the Automation detail page did not switch properly between Execution History and Actions.

### v1.43.2

*Released Feb 20, 2026*

* Fixed an issue where content clusters could be created even when no matching pages were found.
* Fixed scheduled background tasks not running for reports in non-active workspaces.

### v1.43.1

*Released Feb 18, 2026*

* Added the [SERP Extractor tool](/guide/serp-extractor) for extracting and analyzing search engine results.
* Added SERP Item metric filters to help you find keyword opportunities inside SERP Extractor.
* Improved the error message when the S3 bucket region is incorrect.
* Fixed an issue where interactive map HTML exports did not respect marker size, color variants, and glow effect settings.
* Fixed unranked grid points showing as green instead of gray in HTML exports.
* Fixed an issue where filter inputs lost focus after the data table refreshed.

### v1.43.0

*Released Feb 13, 2026*

* Added [S3-compatible storage](/guide/data-sharing-with-s3) for caching DataForSEO API responses (supports Amazon S3, Cloudflare R2, DigitalOcean Spaces, MinIO).
* Added [Interactive Maps option when exporting HTML reports](/guide/google-my-business-rank-tracker/exports-and-client-reports#interactive-maps-in-html-exports) in the GMB Rank Tracker.
* Added Copy to Clipboard bulk action for Saved Keywords lists.
* Added CSV export for Keyword Fluctuation view in Rank Tracker.
* Improved page loading speed in SEO Test creation with Load More pagination.
* Improved helpful tip when searching for homepage in SEO Test page filters.
* Fixed unclear error message when Google Maps API key is invalid in Rank Tracker.
* Fixed Control Period and Test Period cards showing no data in time-based SEO Tests.
* Fixed issue where Search Console property could not be added when using Google OAuth tokens.
* Fixed Annotation date picker not allowing selection of past dates.
* Fixed clickable links not opening when URL contains special characters.

### v1.42.0

*Released Feb 2, 2026*

* Added a new [Keyword Fluctuation tab](/guide/organic-rank-tracker#keyword-fluctuation-tab) in the Organic Rank Tracker to track ranking changes over time.

  You can see start vs current position, 1-day, 7-day, 30-day, and lifetime changes, with quick rank filters like Top 3, Top 10, and Top 20. Local Pack rankings are highlighted with a map pin.
* Added [Saved Keywords](/guide/saved-keywords) feature to organize keywords into lists.

  Save keywords from Keyword Explorer, Google PAA, Autocomplete, Organic Keywords, and Ads Vision into named lists by location and language. You can add tags, import metrics from CSV/Excel, export to CSV, and bulk check keyword metrics.
* Added [annotations support for Google Search Console](/guide/google-search-console/annotations) performance charts.
* Added automatic keyword metrics caching when browsing Organic Keywords or Keyword Suggestions.

  This helps reduce repeated API calls and lowers DataForSEO costs.
* Improved error reporting by filtering out user-side issues.
* Improved AI token usage for the LLM Rank Tracker and other AI-powered features, helping reduce token consumption and costs.
* Improved the property selector when adding Google Search Console properties by adding search support.
* Fixed browser autosuggestion showing up in dropdown search fields.
* Fixed the issue where the annotations list did not refresh after deleting an annotation.

### v1.41.3

*Released Jan 14, 2026*

* Added a sticky table header to the SERP Clustering report so column headers stay visible while scrolling.
* Added phone numbers and caller names to the Money Map tooltips.
* Added the ability to add keywords to the Rank Tracker directly from the Organic Keywords and Keyword Suggestions tables, removing the need to copy and paste.
* Fixed the Sitemap Extractor so it works correctly with sites that have bot protection enabled.
* Fixed an SQLite error when saving large numbers of reviews by batching inserts to avoid the “too many SQL variables” limit.
* Improved database stability by adding retry logic when saving ChatGPT cache during temporary database locks.

### v1.41.2

*Released Jan 10, 2026*

* Added bulk action to fetch reviews for multiple Google Business profiles at once.
* Added rating and total review count columns to the Google Business Reviews list page.
* Added review visibility tracking for Google Business Reviews, allowing you to see when reviews are new, visible, missing, or reinstated.
* Added bulk delete keywords by entering or pasting a list of keyword names.
* Added daily schedule option for GMB Rank Tracker reports.
* Added the ability to export multiple rank tracker reports as a single combined PDF from the dashboard.
* Added manual business coordinate adjustment by dragging the marker directly on the map.
* Improved the delete keyword confirmation to clearly warn about permanent loss of historical ranking data.
* Improved the Organic Rank Tracker dashboard to show the report name instead of the target domain when available.
* Fixed empty stars in rating displays now showing as filled gray instead of outline only.
* Fixed tab labels overflowing in the GMB Rank Tracker form.
* Fixed PDF export crashing when generating reports.

### v1.41.1

*Released Dec 31, 2025*

* Fixed SERP UULE search not working with multi-word keywords.

### v1.41.0

*Released Dec 30, 2025*

* Added census data overlay layers to the GMB Rank Tracker map, including population density, median household income, homeowner percentage, and median age.
* Added Ring Tonic API integration to display visits and calls data on the Money Map inside the GMB Rank Tracker.
* Optimized the GMB Rank Tracker database by only storing the top 20 results.
* Improved settings links so they scroll directly to the relevant section.
* Fixed the issue where auto indexing settings were not saved when reopening the settings modal.
* Fixed the GMB Rank Tracker schedule day selection for monthly and twice-per-month frequencies.

### v1.40.2

*Released Dec 18, 2025*

* Made Ads Vision consistently return ads on the SERP.
* Added ad placement detection and grouped display in the Ads Vision tool, allowing ads to be organized by Top, Bottom, Sidebar, and Middle positions.
* Added a contextual empty state message in the SERP data slide-over, based on what actions are available to the user.
* Improved the UI for the Organic Rank Tracker domain column.
* Fixed an issue where SERP HTML filenames could conflict by ensuring unique filenames using timestamps.
* Fixed a crash on Linux caused by a WebKitGTK signal conflict.

### v1.40.1

*Released Dec 16, 2025*

* Added support for more LLM models, including Claude Opus 4.5, Sonnet 4.5, Haiku 4.5, GPT-5.1, and GPT-5.2.
* Added a report name field for the Organic Rank Tracker so reports are easier to recognize.
* Added a business name filter for the Organic Rank Tracker tool.
* Added a location column to the Google Business Reviews list page.
* Added a scheduling logger for the GMB Rank Tracker.
* Added the Google Local Finder API endpoint.
* Switched the extraction process to use gpt-5-mini for better performance and lower cost.
* Fixed an issue where the LLM Rank Tracker showed outdated Google AI data from the wrong date.
* Fixed an issue where the position domain column visibility could not be toggled in the Organic Rank Tracker.
* Fixed a “too many variables” issue when loading content clusters in the GSC integration.

### v1.40.0

*Released Dec 4, 2025*

* Added Ads Vision tool.
* Added the “New” badge for keywords that appear in the current period but not in the comparison period in the GSC Integration.
* Added SERP features for the Organic Keywords tool.
* Added the ability for CSV exports in the Organic Rank Tracker to include the position type (Organic or Local Pack) and all detected SERP features.
* Added workspace support for the Google Business Reviews Fetcher tool.
* Added the ability to backup SERP HTML files and prune old SERP HTML files.
* Added the ability to force fresh SERP data within the same date/snapshot.
* Added Manage Snapshots for the Organic Rank Tracker tool.
* Added the Analyze SERP button for the Organic Rank Tracker tool.
* Added the Google Business Reviews Fetcher instruction link.
* Fixed the ranking display issue when tracking Local Pack in the Organic Rank Tracker tool.
* Fixed a style issue on the Workspace Switcher.
* Fixed the Average Position chart tooltip not appearing in the Organic Rank Tracker tool.

### v1.39.0

*Released Nov 25, 2025*

* Added [Google Business Reviews Fetcher tool](/guide/google-business-reviews-fetcher).
* Added review count over time chart in the GMB Rank Tracker tool.
* Added total/disabled/enabled keyword columns to the GMB Rank Tracker Reports.
* Added support for shortened Google Maps URLs in the GMB Tank Tracker tool.
* Added "Check on Google" button for Organic Rank Tracker tool.
* Added the copy button for Response Body and colored status codes for Webhook actions in the Automations tool.
* Improved Search Console property validation to check across all workspaces and show the workspace name when duplicate domains exist.
* Fixed an issue that prevented using the SERP Comparison tool.
* Fixed an issue when fetching Google Maps URL in the GMB Rank Tracker tool.

### v1.38.7

*Released Nov 10, 2025*

* Added the ability to run Organic Rank Tracker on selected keywords ([partial scan](/guide/organic-rank-tracker#run-partial-scan))
* Added Depth columns to the Organic Rank Tracker reports page.
* Fixed the Search Volume Trend chart to display data from oldest to newest.

### v1.38.6

*Released Nov 5, 2025*

* Added the ability to bulk update schedules for both Organic Rank Tracker and GMB Rank Tracker tools.
* Made the Google Drive service account portable in app configuration backups.
* Fixed the wrong folder ID issue when exporting Content Struct reports to Google Drive.
* Fixed the error when calculating total earned CTR.
* Fixed the arrow up/down keys not working in the Automation tool.

### v1.38.5

*Released Oct 27, 2025*

* Fixed an issue when deleting DataForSEO Post Tasks.
* Improved stability by skipping “file not found” errors when collecting DataForSEO Post Tasks.

### v1.38.4

*Released Oct 25, 2025*

* Added the ability to add Google Search Console queries to the Organic Rank Tracker.
* Added a disk full alert on the dashboard to warn users before running out of storage.
* Improved keyword metric checking — now it only re-checks keywords that haven’t been checked in the last 30 days and allows you to only check metrics for queries that have at least x impressions.
* Disabled spellcheck, autocorrect, and autocapitalize for the Command Palette on macOS.
* Updated the new app icon.

### v1.38.3

*Released Oct 15, 2025*

* Added the ability to run your GMB Rank Tracker twice per month.
* Added the ability to disable auto-sync for specific GSC properties.
* Added tags for Google Business Rank Tracker keywords.
* Added title and domain details in the SERP Analysis report.
* Added “Check for Updates” menu option for macOS.
* Added the ability to re-check branded keywords after auto-pull in Google Search Console integration.
* Improved data loading in Google Search Console integration.
* Improved initial sync speed for Google Search Console integration, now up to 10× faster.
* Updated DataForSEO SERP API estimation price in the Organic Rank Tracker tool.
* Fixed the issue where newly added site domains were not updated in IndexNow.
* Fixed crash on embedding database settings when no GSC data is available.
* Fixed chart display issue on Google Search Console site with big data.
* Fixed title bar display issue on macOS Tahoe v26.0.
* Fixed “tail command not found” error on Windows.
* Disabled spellcheck, autocorrect, and autocapitalize for input fields on macOS.

### v1.38.2

*Released Sep 22, 2025*

* Added support for Workspaces in the SEO Tests tool.
* Added Ranking Coverage and Visibility Score metrics to the Performance chart in Organic Rank Tracker.
* Fixed the issue where the SERP Clustering tool returned a *“too many SQL variables”* error in some cases.
* Fixed the tooltip not appearing on Organic Rank Tracker charts.
* Show a “—” symbol when there’s no data available on the Organic Rank Tracker Dashboard chart.

### v1.38.1

*Released Sep 17, 2025*

* Added a progress indicator for the clustering step in the SERP Clustering tool, so you can track progress when running large batches.
* Updated Automation variables and improved email formatting.
* Fixed an issue where long descriptions in the Rank Tracker tool did not display well on small screens.

### v1.38.0

*Released Sep 17, 2025*

* Added Automations allows you to send an email, export a PDF, and call a webhook URL when the [Organic Rank Tracker ](/guide/organic-rank-tracker)or [GMB Rank Tracker](/guide/google-my-business-rank-tracker) snapshot is finished tracking.
* Added ChatGPT Scrapper.
* Added **ChatGPT** as an AI engine in LLM Rank Tracker.
* Added **ChatGPT – Web Search** as an AI engine in LLM Rank Tracker.
* Added the ability to merge competitor brands in LLM Rank Tracker.
* Made total URLs clickable in SERP Clustering to view all ranked URLs.
* Added the Depth field across multiple tools.
* Made clusters collapsible in SERP Clustering for easier navigation.
* Improved dark mode display in SERP Clustering tool.
* Show all AI engines in tooltips on the LLM Rank Tracker page.
* Auto-refresh enabled for DataForSEO Post Tasks card.
* Made Excluded Domains optional.
* Fixed Next Run date issue in Organic Rank Tracker.
* Fixed styling issues in the SERP Clustering keywords sheet.
* Fixed issue when cleaning up DataForSEO tasks.

<mark style="color:red;">**Critical Update and Required Action:**</mark>

**Google dropped the num parameter** recently, and it hit almost every SERP API and rank tracker out there, even the big guys like DataForSEO, SEMrush, and Ahrefs. In **SEO Utils v1.38.0**, I've rolled out updates to adapt to DataForSEO’s new SERP API changes.

**What’s changing on DataForSEO SERP API after September 19, 2025 (10:00 UTC)**

* **Base coverage now = Top 10 results (first page)**
* **Additional pages = 25% off** the base price
* Base price **stays the same**, but only for page 1 (10 results):
* $0.002 → Live
* $0.0006 → Normal queue
* $0.0012 → High queue

Extra pages cost less (25% off):

* $0.0015 → Live
* $0.00045 → Normal
* $0.0009 → High

👉 Example: Instead of paying **$0.60** for scraping 100 results × 1,000 keywords, you’ll now pay **$4.65**.

🧰 **Tools affected in SEO Utils**:

1. Organic Rank Tracker
2. SERP Clustering
3. NAP Finder
4. Content Struct
5. Keyword Explorer
6. SERP Similarity

{% hint style="info" %}
Read **update details and my suggestions on the Depth parameter** at <https://www.facebook.com/groups/seoutils/posts/1190999032863701/>
{% endhint %}

### v1.37.3

*Released Sep 9, 2025*

* Added an alert in the LLM Rank Tracker tool when AI extraction is not configured.
* Fixed an issue where the vector database migration was not found on Windows.

### v1.37.2

*Released Sep 9, 2025*

* Fixed vector database is not loaded in macOS.

### v1.37.1

*Released Sep 8, 2025*

* Fixed vector database is not loaded in macOS.

### v1.37.0

*Released Sep 8, 2025*

* Added [SEO Tests](/guide/google-search-console/seo-tests).
* Added tags to the Organic Rank Tracker exported file.
* Fixed vector database initialization issue.
* Fixed the embedding database guide link.
* Fixed an issue where HTML exports didn’t include all Organic Rank Tracker keywords.
* Fixed styles in the exported PDF file for GSC Insights.

### v1.36.0

*Released Sep 1, 2025*

* Added [Embedding Database](/guide/embedding-database).
* Added [Topic Clusters](/guide/google-search-console/topic-clusters) for the GSC integration.
* Added the ability to check keyword metrics for GSC queries (including volume, CPC, KD, intents, and trends).
* Added the ability to analyze SERP for GSC queries.
* Added export option for LLM Rank Tracker reports.
* Added native dark mode support for Google Maps.
* Added glow effect for markers in the GMB Rank Tracker tool.
* Added download button for Queries Overtime charts and Traffic Sources cards.
* Improved delete flow for GSC properties.
* Fixed display issues when exporting GMB Rank Tracker reports in dark mode.
* Fixed dark mode issue in the Competition Map chart.
* Fixed display error in GSC performance chart tooltips.
* Showed a more friendly error message when no results are found, plus added debug handling for over-token-limit errors.

### v1.35.2

*Released Aug 18, 2025*

* Improved the recent page titles in the Command Palette to make them more user-friendly.
* Fixed an issue in the LLM Rank Tracker where results could exceed the context limit.
* Removed unnecessary error alerts in the GMB Rank Tracker when no results are found.

### v1.35.1

*Released Aug 16, 2025*

* Added a command palette (Cmd/Ctrl + K) for quick tool access.
* Added a search bar in the sidebar for easier navigation.
* Added table view for Google Search Console integration.
* Added query word count filter for GSC integration.
* Made the Update Modal content scrollable.
* Fixed the issue where GMB Rank Tracker reports could disappear after updating.
* Fixed several display issues and made various styling improvements.

### v1.35.0

*Released Aug 14, 2025*

* Added [Workspace](/guide/workspace).
* Improved GMB Rank Tracker cloud sync.
* Fixed an issue where a specific grid point in the GMB Rank Tracker didn’t load the correct data.
* Fixed display issue on the Google Search Console average position metric.
* Fixed table appearance in dark mode.

### v1.34.6

*Released Aug 12, 2025*

* Fixed reactive issues on the GMB Rank Tracker keywords page.
* Fixed minor display glitches in the GMB Rank Tracker tool.

### v1.34.5

*Released Aug 12, 2025*

* Fixed an issue in the GMB Rank Tracker where snapshots and competitor lists might not appear in some cases.

### v1.34.4

*Released Aug 11, 2025*

* Added Content Cluster feature for Google Search Console integration.
* Added a copy button for keywords in the Bulk Autocomplete tool.
* Enhanced the display for GSC Insights and Preview pages.

### v1.34.3

*Released Aug 8, 2025*

* Added a SoLV column to the competitors list in the GMB Rank Tracker tool.
* Added an empty state message for the Overview tab when the selected keyword has no data for the current snapshot.
* Hide no ranking keywords from the GMB Rank Tracker preview report.
* Improved the display style of the GMB Rank Tracker preview report.
* Improved the website favicon fetching process.
* Prevented cloud syncing when the snapshot is empty.
* Fixed broken documentation links.
* Fixed an issue where the Organic Rank Tracker export did not include competitors’ data.
* Fixed the cost estimation button triggering form submission unexpectedly.

### v1.34.2

*Released Aug 7, 2025*

* Added GPT-5 models for all AI tools.
* Increased waiting time for DataForSEO post tasks.

### v1.34.1

*Released Aug 6, 2025*

* Added an AI Filter to the Google Search Console integration to let you filter data using natural language queries.
* Automatically switches to the *Queries* tab when clicking on the branded column.
* Prevents multiple initial syncs from running at the same time in the GSC integration.
* Fixed "database is locked" in the GSC integration.

### v1.34.0

*Released Aug 5, 2025*

* Added Google Search Console integration v2.
* Supported [Google OAuth flow](/guide/google-oauth-token): You can now connect using a Google OAuth Token or a Service Account to pull your site’s GSC data.
* Added thinking mode for Ollama provider.
* Added a Refresh Location button in the Services page to fetch updated location data from DataForSEO.

{% hint style="info" %}
Make sure to export data from GSC v1 before updating. After updating, double-check the site access of each Google Service Account used for submitting index requests in the Google Services Account page.

<img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cc501c47290e3982137c84c678eb7ce3ac662332%2FXnapper-2025-08-05-22.45.03.png?alt=media" alt="" data-size="original">
{% endhint %}

### v1.33.7

*Released Aug 4, 2025*

* Improved the GMB Rank Tracker to automatically resync if a report is missing.
* Cleaned up unused fields in GMB Rank Tracker cloud sync.
* Fixed the tag filter not working on the GMB Rank Tracker compare page.
* Fixed an issue where tag filters didn’t load properly on the first visit.
* Fixed the sorting issue on the Traffic Competitors page.
* Hid the measuring tool on the GMB Rank Tracker compare page.

### v1.33.6

*Released Aug 3, 2025*

* Added support for showing existing tags when using the bulk update tags action in the LLM Rank Tracker and Organic Rank Tracker tools.
* Added an empty state message for the competitors list tab in the GMB Rank Tracker tool.
* Added the Latest Rank column to the keywords management page in the GMB Rank Tracker tool.
* Prevented multiple instances of the app from running at the same time.
* Optimized table loading performance.
* Improved performance when saving metadata.

### v1.33.5

*Released Aug 3, 2025*

* Added an example template link for the map keyword data feature.
* Improved bulk update tags action to display existing tags.
* Fixed the issue where the GMB Rank Tracker Keywords page didn’t show total count and pagination.
* Fixed the bug where the keywords slide-over panel in GMB Rank Tracker couldn’t be opened.
* Fixed the “No Search Results” error.
* Fixed the “database is locked” error.

### v1.33.4

*Released July 30, 2025*

* Added a tags filter to the keyword list slide-over in the GMB Rank Tracker’s map view.
* Added the ability to [map external keyword metrics](/guide/organic-rank-tracker#map-external-keyword-data) (search volume, CPC, KD, search intents) and tags for Organic Rank Tracker keywords.
* Added “Previous Position” and “Position Difference” columns to the CSV export of Organic Rank Tracker reports.
* Added a Page filter to the Top Pages by Traffic view.
* Tags filter is now preserved when navigating reports in both the Organic Rank Tracker and GMB Rank Tracker.
* Improved the disk full check.
* Fixed an issue in the Keyword Explorer tool that could cause the app to crash.
* Minor style improvements.

### v1.33.3

*Released July 26, 2025*

* The Organic Rank Tracker dashboard chart now displays disconnected line segments between tracking periods to avoid showing misleading ranking drops.
* Added internal logger for ready tasks to improve tracking and debugging.
* Fixed some minor issues in the DataForSEO Post/Ready/Get task system.

### v1.33.2

*Released July 25, 2025*

* Added autocomplete keyword suggestions for the Keyword Explorer tool.
* Added support for using OpenRouter as the extraction model in the LLM Rank Tracker tool.
* Added the ability to tag keywords in the GMB Rank Tracker.
* Added stuck task detectors and a collector status to help identify and resolve processing issues.
* Improved timezone handling across tools for more accurate data display.
* Improved GSC integration by skipping unverified sites when fetching data.
* Improved handling of disk full situations by showing an alert in the DFS Post Tasks page.

### v1.33.1

*Released July 23, 2025*

* Added the DFS Post Task list page.
* Added the ability to check internet connection status.
* Added support for pasting multiple values into the Brand Variants field.
* Added pagination and improved the UI for the Organic Rank Tracker dashboard.
* Fixed the issue where the backup database process gets stuck.
* Fixed timezone comparison issues by ensuring UTC consistency with the database.
* Improved error handling by ignoring certain OpenAI errors.
* Removed the old Post Task model.

### v1.33.0

*Released July 22nd, 2025*

* Added [LLM Rank Tracker](/guide/llm-rank-tracker).
* Added Bing as a supported search engine in the Keyword Explorer tool.
* Added a log file feature to help track internal activity and debugging info.
* Improved the Task Post/Ready/Get system to reduce stuck tasks when using the DataForSEO queue.
* Removed the unnecessary srsltid parameter from URLs in the Organic Rank Tracker tool.
* Fixed the issue where the Entities and Topics tab couldn’t be opened in the Text Analysis tool.
* Fixed the bulk update tags form not allowing users to add new tags.
* Fixed a bug where the migration screen ran multiple times during app startup.
* Fixed the issue where Anthropic model responses were cut off and returned incomplete data.
* Fixed the timezone mismatch on the Organic Rank Tracker Pages tab and the IndexNow feature.

### v1.32.3

*Released June 23rd, 2025*

* Added the ability to prevent time from crossing midnight when syncing SERP data.
* Set the GMB Rank Tracker export preview sheet to be scrollable.
* Fixed organic rank tracker dashboard doesn't set a fallback date when having only one snapshot.
* Fixed the timezone issue on the scheduled GMB Rank Tracker report.
* Fixed the "Desktop" text on the Organic Rank Tracker Dashboard page.

### v1.32.2

*Released June 20th, 2025*

* Fixed the DataForSEO priority issue.

### v1.32.1

*Released June 20th, 2025*

* Fixed the issue when the organic rank tracker could not find the correct position for the keyword from SERP data.

### v1.32.0

*Released June 19th, 2025*

* Added [SERP Features](/guide/organic-rank-tracker#serp-features-tracking) for the Organic Rank Tracker tool.
* Added [Local Pack position tracking](/guide/organic-rank-tracker#basic-fields).
* Added the ability to resync the organic rank tracker report when the Include Subdomains field is updated.
* Added the ability to customize the number of exported keywords in the PDF organic rank tracker report.
* Added the ability to include/exclude search volume from the PDF of the organic rank tracker report.
* Added another format for Export Grid Points With Businesses action.
* Added the ability to remember selected date range across tabs in the Organic Rank Tracker tool.
* Fixed timezone issues.
* Fixed the issue when unable to toggle the Include Subdomains field.
* Fixed the issue when the sync GMB Cloud is still running without an API key.
* Fixed issue where default data was not populating on the Bulk Autocomplete modal re-open.
* Fixed some style issues on the organic rank tracker dashboard.
* Fixed text and docs link.
* Removed reports that don't have data from the organic rank tracker dashboard chart.

### v1.31.2

*Released June 12th, 2025*

* Added Bot Distribution chart for the Log File Analysis tool.
* Added the ability to export competitors for the Top Performing Business for the Keyword table.
* Added the ability to export all businesses found at each grid point location for detailed\
  geographic competitor analysis.
* Added reasoning models across all AI tools.
* Updated app icon for Windows.
* Fixed the auto theme mode issue in macOS.

### v1.31.1

*Released June 10th, 2025*

* Added the ability to delete the cloud report.
* [Log File Analysis](/guide/log-file-analysis) tool is free to access without a license key.

### v1.31.0

*Released June 9th, 2025*

* Added [Log File Analysis](/guide/log-file-analysis) tool.
* Fixed average position column sorting in competitors discovery.

### v1.30.0

*Released May 30th, 2025*

* Added SERP API: [Larseo](https://api.larseo.app/)
* Added [Organic Rank Tracker Dashboard](/guide/dashboard/organic-rank-tracker) — get a quick overview of all your reports in one place.
* Added [measuring tool](/guide/google-my-business-rank-tracker/map-tools#measure-a-distance) for GMB Rank Tracker.
* Added [Strict Algorithm](/guide/serp-clustering#clustering-algorithm) for SERP Clustering tool.
* Added [annotation feature](/guide/google-my-business-rank-tracker/manage-reports#notes) for GMB Rank Tracker.
* Rebuilt the GMB Rank Tracker snapshot timeline UI.
* Added report type filter for annotation list.
* Fixed the issue that prevented pulling new Google Updates.

### v1.29.2

*Released May 7, 2025*

* Added the ability to copy competitor coordinates in Google Business Rank Tracker.
* Enhanced web scraping functionality with retry logic to improve reliability.
* Refactored heading extraction logic in Content Struct to exclude style and script tags during text processing.
* Fixed the issue where the user dropdown could not be opened when the sidebar was not pinned.
* Fixed an issue accessing metadata properties in Content Struct to prevent potential errors.

### v1.29.1

*Released April 28, 2025*

* Added the ability to delete cloud snapshot.
* Added the ability to delete cloud GMB Rank Tracker report.
* Added the ability to update the business coordinates in the GMB Rank Tracker tool.
* Added a message when the cloud database is not setup when sharing the report.
* Added the ability to allow users to import a mismatched version backup file.
* Fixed optional chaining for Geo Target value in Content Struct form.
* Fixed the check index using Google Webmaster Tool doesn’t work properly in some cases.

### v1.29.0

*Released April 24, 2025*

* Dropped support for Linux 20.04.
* Added [shareable link for GMB Rank Tracker tool](/guide/white-labeled-client-report).
* Added global settings for the Content Struct tool.
* Fixed the format issue in the "copy headings as the Zimmwriter" button.

### v1.28.3

*Released April 7, 2025*

* Fixed the issue on Bulk Google PAA tool when it doesn't return content when using UULE.
* Fixed the Content Struct's exclude domain field doesn't work with the www version.
* Fixed the issue when the target is not removed spaces before sending to DataForSEO.
* Fixed the worker validation errors on the cloning organic rank tracker report.

### v1.28.2

*Released Mar 31, 2025*

* Used the new endpoint for the Check Keyword Metrics tool.
* Added the ability to include clickstream data for the Check Keyword Metrics tool.
* Added search intents for keyword metrics data.
* Added the ability to sort by the indexed column in GSC sites.
* Added the ability to asynchronously load historical traffic data in the Traffic Analytics tool.
* Removed impressions info data because it's not maintained by DataForSEO anymore.
* Fixed the issue when cannot press backspace or delete on the form in GMB Rank Tracker.
* Fixed the traffic format number.
* Fixed the search intents filter when it doesn't show the selected value when re-opening the Sheet.

### v1.28.1

*Released Mar 28, 2025*

* Added excluded domains setting for Content Struct tool.
* Fixed the performance issues when scraping URLs in the Content Struct tool.
* Fixed the excluded domain field doesn't add new value in the N.A.P Finder tool.

### v1.28.0

*Released Mar 27, 2025*

* Added [Content Struct](/guide/content-struct) tool.
* Added NLP Text Analysis instruction link.
* Added a schedule filter for the GMB Rank Tracker reports list page.
* Added the ability to paste multiple URLs in NLP Text Analysis.
* Added 2 more multiple languages for Semantic Clustering tool.
* Enhanced the multiple marker movement feature in the GMB Rank Tracker tool allows you to see all selected markers move in real-time while dragging.
* Updated new assets for GMB Rank Tracker Bird View.
* Added rate limiting for Text Razor driver.
* Added an alert to show NLP text analysis error message in the report detail page when an API request fails.
* Fixed an issue in the GMB Rank Tracker tool where drawing mode could get stuck if the mouse was released before the Shift key when selecting multiple markers.
* Fixed the issue of not being able to find the seed keyword in the Google PAA tool.
* Fixed cannot edit the organic rank tracker report.

### v1.27.2

*Released Mar 14, 2025*

* Added the report name to the filename when saving the NLP Text Analysis report.
* Fixed the tag issue when exporting organic rank tracker report.
* Fixed language mapping in TextRazor API Driver.
* Removed Dutch from Google NLP because Google doesn't support it for the Entities Extractor endpoint.

### v1.27.0 + v1.27.1

*Released Mar 13, 2025*

* Added [NLP Text Analysis](/guide/nlp-text-analysis) (including Entities + Topic Extractor).
* Rebuilt tags system.
* Added DataForSEO Post Task stat card.
* Added the documentation link for the Delete DataForSEO Post Tasks action.
* Fixed the phones input doesn't accept new values in the N.A.P Finder tool.
* Removed the time from the snapshot in the exported GMB Rank Tracker report.
* Ensured all the maps are loaded before exporting the GMB Rank Tracker report.

### v1.26.5

*Released Mar 9, 2025*

* Fixed the date issue when viewing SERP data in the Organic Rank Tracker tool.
* Skip keywords without SERP data when syncing.

### v1.26.4

*Released Mar 4, 2025*

* Added the ability to disable/enable GMB Rank Tracker keywords.
* Added the ability to select the DataForSEO priority queue for GMB Rank Tracker tool.
* Fixed the issue when the URL is not exported in the SERP Clustering and Organic Rank Tracker tools.

### v1.26.3

*Released Feb 26, 2025*

* Added the ability to include subdomain when tracking organic keywords.
* Added the ability to save multiple positions when a domain ranks for multiple pages for a keyword.
* Added the Competitor Discovery report for the Organic Rank Tracker tool.
* Remember the selected domain in the Organic Rank Tracker Pages tab.
* Fixed the issue where the snapshot date could not be fetched in the rankings distribution tab.
* Fixed an issue when parsing date in SERP exporter/importer.
* Fixed the SERP importer/exporter validation.
* Fixed the other traffic card of the Traffic Analytics tool that does not show data in some cases.
* Added validation rule: Request Delay must be at least 3 seconds when scraping with own IP.
* Fixed the error in fetching the trends chart in the GMB Rank Tracker tool.

### v1.26.2

*Released Feb 9, 2025*

* Added fetch business detail button for the N.A.P Finder tool.
* Bypass the new Google bot detection when using the own IP or proxy method in Organic Rank Tracker, SERP Clustering, N.A.P Finder tool.
* Fixed the user agent not respecting device type.
* The fixed output log is not printing when using its own IP or proxy method.

### v1.26.1

*Released Feb 4, 2025*

* Bypass the new Google bot detection to scrape Google PAA.
* Added DataForSEO SERP API for Bulk Google PAA.
* Added the ability to show all breaking changes when upgrading.
* Added total seed keywords and total keywords for the Google PAA reports page.
* Added the ability to remember Click Depth & Scrape SERP With fields on Bulk Google PAA form.
* Added RSS Sitemap support for the Sitemap Extractor tool.
* Added favorite geo targets for the SERP UULE tool.
* Added the ability to select country & language in the SERP UULE tool.
* Fixed seed keywords filter doesn't show options on the Google PAA detail page.
* Fixed the issue where the completed PAA report cannot be seen when another report is in process.

### v1.26.0

*Released Jan 19, 2025*

{% hint style="danger" %}
**Encryption Algorithm Update**

In previous versions, SEO Utils utilized encryption for sensitive data, which inadvertently caused some antivirus software and Apple Gatekeeper to flag the application as malware. To address these issues, the encryption feature has been removed.
{% endhint %}

<mark style="color:red;">**Action Required:**</mark>

Before upgrading to this version, please visit the Services page and copy all the API keys & passwords including Google Places, IndexNow, OpenAI, DataForSEO password, Open Router, and Anthropic.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-976087930ddc46b581843d6d2d6de1dd9a884841%2FCleanShot%202025-01-19%20at%2014.48.24%402x.png?alt=media" alt=""><figcaption><p>Backup API keys and passwords.</p></figcaption></figure>

After upgrading to version 1.26.0, please re-enter your license key by following [this guide](https://help.seoutils.app/guide/manage-license-key#deactivate-the-license-key-from-a-device). If you previously used any of these keys—Google Places, IndexNow, OpenAI, DataForSEO password, Open Router, or Anthropic—please re-enter them as well.

***

* Removed the encryption code that inadvertently caused some antivirus software and Apple Gatekeeper to flag the application as malware.
* Notarized the app with Apple.
* Added the ability to show break changes alert before updating to a new version.

### v1.25.5

*Released Jan 15, 2025*

* Fixed SERP clustering; it doesn't re-cluster keywords when the number of keywords to scrape is 0.

### v1.25.4

*Released Jan 15, 2025*

* Added a German embedding model for the Semantic Clustering tool.
* Fixed an issue when fetching backlinks metric in the SERP analysis card.
* Fixed all issues that caused the SERP Clustering tool to crash on a huge keyword list.

### v1.25.3

*Released Jan 8, 2025*

* Added Portuguese models (PT-PT & PT-BR) for the Semantic Clustering tool.
* Added more logs for the Free GMB Pending Snapshots action.

### v1.25.2

*Released Jan 7, 2025*

* Added the "Free stuck organic SERP tasks" action.
* Fixed the SERP Clustering tool; it is stuck at the step of checking keyword metrics.

### v1.25.1

*Released Jan 7, 2025*

* Fixed Google Drive cache issue.
* Fixed an issue on the Google Business Rank Tracker Trends view.

### v1.25.0

*Released Jan 5, 2025*

* Added Windows ARM64 support.
* Added the Rankings Distribution report to the Organic Rank Tracker tool.
* Added the ability to export the Organic Rank Tracker report as PDF or HTML.
* Added the ability to preserve keyword cases in the SERP Clustering tool.
* Added the ability to disable snapshot dates in the Date Range picker when unavailable.
* Updated update source.
* Fixed some issues that cause SERP Clustering to crash.

### v1.24.3

*Released Dec 28, 2024*

* Added the ability to bypass site protection for the Sitemap Extractor tool.
* Added the ability to bypass site protection for the Bulk SEO Metadata Optimizer tool.
* Fixed a chart issue in the GMB Rank Tracker Trends view.
* Fixed the issue with sorting by keyword metrics in the Organic Rank Tracker tool.
* Fixed an issue where the Get Metrics modal cannot be opened multiple times in the SERP Analysis tool.

### v1.24.2

*Released Dec 20, 2024*

* Added the ability to clean up temporary files after checking keyword mentions.
* Fixed the Bulk SEO Metadata Optimizer tool; it couldn't find HTML files on Windows.

### v1.24.1

*Released Dec 17, 2024*

* Added the ability to run the optimizer with multiple workers, making it faster to optimize SEO metadata.
* Add a bulk action for deleting items for the Bulk SEO Metadata Optimizer tool.
* Added loading indicator publishing action in the Bulk SEO Metadata Optimizer tool.
* Added a button to refresh the AI model list.
* Updated message to support only post, page, and WooCommerce product types for WordPress integration.
* Updated guide link for the Bulk SEO Metadata Optimizer tool.
* Fixed the HTML file is not found in some cases when optimizing SEO metadata.
* Fixed the issue when GSC sites are not showing up.
* Fixed a style issue in the Bulk SEO Metadata Optimizer tool.

### v1.24.0

*Released Dec 16, 2024*

* Added new tool: [Bulk SEO Metadata Optimizer](/guide/bulk-seo-metadata-optimizer).
* Added site integrations.
* Added a device indicator on the Organic Rank Tracker detail page.
* Add a column to show the month-over-month percentage change in search volume compared to the previous month on the Keyword Suggestions page.
* Added the ability to break the page when the keyword list is long in the GMB Rank Tracker export.
* Added the ability to select all keywords in the Organic Rank Tracker Keywords page.
* Added the ability to show the matched URL in the SERP clustering tool.
* Set the color to green when the average rank metric is down since it's a good sign in the GMB Rank Tracker tool.
* Fixed a timezone issue in the Organic Rank Tracker tool.
* Fixed the sorting issue that doesn't work in some cases in the Organic Rank Tracker tool.
* Fixed an issue that caused crashes in the Organic SERP data collector.
* Fixed the app crash when estimating SERP clustering costs in some cases.
* Fixed a chart issue in the GMB Rank Tracker Trend view.
* Fixed the traffic analytics; it doesn't work with Thai URLs in some cases.
* Updated documentations.

### v1.23.5

*Released Dec 5, 2024*

* Added the ability to redact sensitive information on the GMB Rank Tracker’s comparison page.
* Added the ability to adjust the previous snapshot date when comparing 2 GMB Rank Tracker snapshots by setting comparison days.
* Added previous snapshot info to the GBM Rank Tracker preview export.
* Added metric cards: DataForSEO Organic SERP Ready Tasks & DataForSEO Google Maps SERP Ready Tasks.
* Added Database Fragmentation card and the ability to maintain the database.
* Added the ability to remember keyword metric sort field in the Organic Rank Tracker Overview page.
* Added the ability to suppress toggle table columns dropdown close when selecting.
* Added the ability to run the process to optimize the database in the background.
* Added recommended text for the embedding model.
* Updated documentation links.
* Optimized loading for the organic rank tracker keywords page and overview page.
* Removed the database connection limitation.
* Fixed the "too many SQL variables" issue when exporting organic rank tracker reports and SERP Data.
* Printed meaningful error messages when semantic clustering failed.
* Trimmed empty spaces of keywords before running semantic clustering.

### v1.23.4

*Released Dec 3, 2024*

* Fixed an issue when the "Free Stuck GMB Rank Trackers" tool didn't work when ready tasks is over 1,000 items.

### v1.23.3

*Released Dec 2, 2024*

* Added the ability to generate a grid centered on a specific point with a defined radius in the GMB Rank Tracker tool.
* Added SoLV metric for GMB Rank Tracker tool.
* Add a search bar for Competitors and Ranking Keywords tabs in the GMB Rank Tracker tool.
* Added breadcrumbs for all pages.
* Added trend view for the GMB Rank Tracker tool.
* Added a tool to unstick stuck GMB Rank Tracker snapshots.
* Fixed the issue when the sort field doesn't work as expected when the domain contains "-" in the Organic Rank Tracker.
* Removed the down arrow icon when the average rank change was 0.0.
* Fixed a display issue to show the correct color for ranking in the GMB Rank Tracker.
* Fixed the change indicator background color in dark mode for the GMB Rank Tracker tool.
* Improved sitemap extractor to detect more content types.
* Forced to use Semantic Keyword Clustering version 2 on Linux.
* Forced UTF-8 encoding on keyword suggestions exported file.

### v1.23.2

*Released Nov 26, 2024*

* Added Semantic Keyword Clustering v2.
* Added the ability to select all check mentions items.
* Added the ability to export the comparison page in the GMB Rank Tracker tool.
* Added the ability to collect uncollected tasks before starting a new tracker in the Organic Rank Tracker tool.
* Added the back to the report button on the Google PAA visual graph page.
* Add subtitle for Geo-target combobox.
* Added Bulk Delete Organic Rank Tracker Keywords.
* Fixed the retry action of GMB Trank Tracker, which didn't work correctly.

### v1.23.1

*Released Nov 22, 2024*

* Added the ability to re-check mentions on selected items.
* Fixed the organic rank tracker overview chart doesn't show data.
* Fixed the GMB Rank Tracker comparison tool doesn't show competitors.
* Fixed link style issues in Organic Keywords & Top Pages By Traffic pages.

### v1.23.0

*Released Nov 21, 2024*

* Added Bulk Check Mentions tool.
* Added the ability to run the organic rank tracker in bulk.
* Added the ability to run the GMB rank tracker in bulk.
* Added filters "index checked at" and "index submitted at" for the Google Search Console Indexing tool.
* Added the ability to sort "index checked at" and "index submitted at" columns.
* Added the ability to sort "first seen" and "last seen" dates in the Backlinks view.
* Added the ability to check if any reports are running before updating the app.
* Added the ability to pause all background tasks before updating the app.
* Added the ability to save preset filters in the GMB Rank Tracker tool.
* Setting the light mode is the default value for the new installation.
* Changed the behavior of retry action in GMB Rank Tracker to collect ready tasks instead of creating new post tasks.
* Fixed Google Search Console index indication is not correct in some cases.
* Fixed the total URL count issue in the "URLs indexed on Bing" metric card when filtering.
* Fixed the filter style issue in GMB Bird View.
* Fixed the GMB Rank Tracker Comparison tool doesn't show enough info.
* Fixed an issue when the Organic Rank Tracker can cause duplicated snapshots in different time zones.
* Only allow to select ready snapshot when comparing in GMB Rank Tracker tool.

### v1.22.3

*Released Nov 18, 2024*

* Fixed in-app update issue in v1.22.2 that doesn't allow you to open the app after upgrading. Please visit the download page to download the latest version.

### v1.22.2

*Released Nov 17, 2024*

* Added the ability to clone the Organic Rank Tracker report
* Added the ability to remove extra spaces from URLs taken from the sitemap.
* Fixed an issue where the app cannot be opened on macOS Sequoia 15.1.
* Fixed an issue when decrypting license key status.
* Fixed the Thai URI issue on Top Pages by Traffic.
* Fixed the Thai URI issue on the Traffic Analytics tool.
* Fixed the Page tab in the Organic Rank Tracker tool when it sometimes doesn't show ranking keywords.
* Updated dependencies
* Updated app info & copyright.

### v1.22.1

*Released Nov 14, 2024*

* Added more context on restore backup error.
* Fixed dark mode style issues on the SERP Data table.
* Fixed a security issue on macOS installation.

### v1.22.0

*Released Nov 13, 2024*

* Added Backup Database tool.
* Added Backup App Configuration tool.
* Added SERP Comparison.
* Added the ability to view historical SERP data.
* Added the ability to analyze SERP for keywords in the Organic Rank Tracker tool.
* Added a mechanism to prevent getting stuck at the database migration screen.
* Added the ability to remember the selected keyword in GMB Rank Tracker report.
* Added the ability to pause background jobs.
* Encrypted sensitive app configuration.
* Fixed the validation rule of the "Rerun Every" field in the Organic Rank Tracker tool.
* Fixed an issue that cannot export the organic rank tracker report in the Pages tab.
* Fixed an issue when the keyword is not displayed in the SERP data table.
* Fixed the issue when seed keywords are not shown in the Autocomplete filter.
* Fixed an issue that caused the app to crash when checking search volume for autocomplete keywords.
* Changed the website icon for Google business.
* Moved the Check Metrics action to the Bulk Actions in the Organic Rank Tracker Keywords page.
* Do not insert a newline in the textarea when pressing a comma in the Thai keyboard layout.
* Decoded Thai URI.
* Optimized database settings.

### v1.21.3

*Released Nov 6, 2024*

* Added the ability to export keyword metrics in the Organic Rank Tracker tool.
* Added the ability to sort the keyword metrics in the Organic Rank Tracker tool.
* Improved “Expand” button to view the full map and ranking grid on one screen without scrolling.
* Optimized database settings.
* Fixed Bulk Google PAA doesn't click if the IP is from the EU.
* Fixed the center coordinate is not pulling ranking data when selecting the circle shape in the GMB Rank Tracker tool.
* Added "enter license key" menu item to the user dropdown.
* Added renew button.

### v1.21.2

*Released Nov 2, 2024*

* Added the ability to estimate the cost when re-running the cluster.
* Added the ability to include uncollected tasks when estimating the cost of SERP clustering.
* Added export button for the Organic Rank Tracker tool.
* Added the ability to check keyword metrics for keywords in the Organic Rank Tracker tool.

### v1.21.1

*Released Oct 31, 2024*

* Hotfix: The app crashed on the new installation.

### v1.21.0

*Released Oct 31, 2024*

* Made modal scrollable when content is too long.
* Added device indicator for the Organic Rank Tracker tool.
* Added geo-target indicator for Organic Rank Tracker tool.
* Added tagging support for Organic Rank Tracker reports.
* Added a validation rule for the "Saved Serp Days" field.
* Added the ability to exclude domains in the N.A.P Finder tool.
* Added the ability to add multiple phone number formats in the N.A.P Finder tool.
* Added the ability to set grid shape to Circle in the GMB Rank Tracker (square or circle).
* Added the ability to import SERP Data from external sources.
* Added the ability to delete DataForSEO Post Tasks.
* Added SERP Database Overview & Retention Settings to manage SERP Data.
* Added the cost estimation for the SERP Clustering tool.
* Added the ability to set marker size smaller in the GMB Rank Tracker grid.
* Added a search bar for the Organic Rank Tracker overview page.
* Improved DataForSEO balance loading on the Dashboard page.
* Improve PAA to work with other languages.
* Removed the date at the end of description when exporting PAA reports.
* Optimized SERP Clustering algorithm to run faster.
* Optimized SERP Clustering exporting to run faster.
* Optimized page load for GMB Rank Tracker report.
* Fixed some bugs in PAA that sometimes prevent questions from being found.
* Fixed the Keyword Explorer doesn't export all keywords in some cases.
* Fixed the "database is locked" issue in some spots.

### v1.20.2

*Released Oct 24, 2024*

* Added city, state, and postal code fields for the N.A.P Finder tool.
* Fixed the UTF-8 encoding issue on GMB Rank Tracker.
* Fixed the mapping columns UI when the column is too long in the SERP clustering tool.
* Fixed "database is locked" in the SERP Clustering tool.
* Fixed Google Update annotations issue cannot be loaded.

### v1.20.1

*Released Oct 23, 2024*

* Added a visual graph for the Google PAA report.
* Added Google Update annotations.
* Added annotation types filter for Organic Rank Tracker chart.
* Fixed the user dropdown being hidden by the Log Panel on some screens.
* Fixed the issue where the "Scrape SERP With" selection isn't saved properly in the N.A.P Finder tool.
* Fixed the N.A.P Finder instruction link.
* Fixed the Google PAA description is not extracted correctly when depth > 0.
* Fixed an issue when adding over 10,000 keywords in the Organic Rank Tracker.
* Fixed the "max run" issue in the SERP Clustering tool.
* Fixed the "min updated date" issue in the SERP Data Exporter.

### v1.20.0

*Released Oct 21, 2024*

* Add N.A.P Finder.
* Added the ability to bulk add Google Search Console queries to Organic Rank Tracker.
* Added a section to manage license key.
* Added validation rules for SERP data importer.
* Forced UTF-8 encoding for Semantic Keyword Clustering tool.
* Fixed a glitch in the combobox filter.

### v1.19.8

*Released Oct 15, 2024*

* Added an "Export SERP Data" option has been added to allow you to choose whether or not to include SERP data.
* Updated sitemap extractor user-agent.
* Dropped geo targets table.
* Enhanced the error message for an invalid API key rental.
* Enforced UTF-8 encoding when exporting Google PAA reports.
* Enforced UTF-8 encoding when exporting Google/Bing Autocomplete reports.

### v1.19.7

*Released Oct 14, 2024*

* Fixed an issue that caused the app to crash.

### v1.19.6

*Released Oct 14, 2024*

* Fixed Geo Target issue on Google PAA.
* Fixed tag issue.
* Added an error alert when failing to fetch ready tasks from DataForSEO.
* Added a mechanism to prevent the ready tasks endpoint from being full.

### v1.19.5

*Released Oct 11, 2024*

* Added SERP Data Exporter & Importer.
* Added preset filters for Organic Rank Tracker.
* Added new sidebar layout setting: Full - No Dropdown.
* I updated the Geo Target list to include more locations and fix incorrect location names.
* The default sort has been changed to the Last Run At column when loading GMB Rank Tracker reports.
* Fixed an issue that caused the rank tracker reports to be stuck.
* Fixed the "too many SQL variables" issue when exporting a SERP clustering report.

### v1.19.4

*Released Oct 7, 2024*

* Optimized database settings.
* Fixed ranking keywords do not appear on the initial load.
* Fixed additional countries are not selected.
* Fixed some sidebar UI issues.
* Fixed "too many SQL variables" error when exporting SERP Clustering report.

### v1.19.3

*Released Oct 5, 2024*

* Added a new full sidebar layout and an option to change the sidebar layout.
* Added the option to hide the form on the GMB Rank Tracker tool.
* Added sorting for Organic Rank Tracker - Overview tab.
* Included Guernsey and Jersey as countries in the GSC site editing modal.
* Corrected an incorrect location name.
* Ensure Windows users run the app as an admin when updating.
* Fixed the issue with SERP clustering not working without geo-targeting.

### v1.19.2

*Released Oct 1, 2024*

* Fixed timezone issue on the Organic Rank Tracker tool.

### v1.19.1

*Released Sep 30, 2024*

* Fixed issue where rank tracker could not be created without a geo target.

### v1.19.0

*Released Sep 30, 2024*

* Added Organic Rank Tracker.
* Added the ability to save historical SERP data.
* Added Jersey and Guernsey as countries when adding Google Search Console sites.
* Fixed the Geo Target's default value not being fetched.
* Set the timeout for the sitemap extractor to 60 seconds.
* Fixed the auto zoom not working well on the preview page.
* Fixed the incorrect display of the lack of SERP data alert after clustering.

### v1.18.3

*Released Aug 30, 2024*

* Added tagging feature for GMB Rank Tracker reports.
* Added a switch button to display additional color variants for the ranking grid points.
* Added loading state for Competitors and Ranking Keywords table.
* Added opening hours for competitors table in GMB Rank Tracker tool.
* Added a button to open Google Business's website.
* Fixed some glitches in table filters.
* Fixed row action dropdown is not centered vertically.
* Fixed issue when exporting SERP data in the Keyword Explorer tool.
* Fixed some spacing issues.
* Fixed Created At column is updated to an empty value when updating the GMB Rank Tracker report.

### v1.18.2

*Released Aug 25, 2024*

* Added the ability to show or hide ranking changes indicator on the grid points.
* Added the ability to export grid points of the current snapshot.
* Added [comparison tool](/guide/google-my-business-rank-tracker/compare) for GMB Rank Tracker tool.
* Added "Last Run" column for the GMB Rank Tracker Reports table.
* Added "Clone" action for GMB Rank Tracker report.
* Fixed an issue where cannot set a timezone for the GMB Rank Tracker report.
* Fixed the GMB Rank Tracker report is not refreshed when the last snapshot is deleted.
* Fixed an issue where cannot edit the GMB Rank Tracker report when the schedule is not set.

### v1.18.1

*Released Aug 21, 2024*

* Added database migration loader.

### v1.18.0

*Released Aug 21, 2024*

* The new UI supports color changes and dark mode 🔥🔥🔥.
* Optimized queries to work with large reports.
* Allow to name the exported files.
* Added pagination and search input for all data tables.
* Only show 1000 lines of log.
* Fixed "database is locked" in some spots.
* Fixed Geocoding failed when editing the GMB Rank Tracker reports with Service Area Businesses.
* Fixed an issue where can't decode the Google Maps URL when no rating service API is added.
* Fixed minor issues.

{% hint style="warning" %} <mark style="color:orange;">**Important**</mark>

After upgrading, the app will run some migrations to optimize the database. During this time, the app may appear blank for 30 seconds to 2 minutes, depending on the size of your database. **Please don't close the app.**

Also, when upgrading to this version, all preset filters will be deleted. You'll need to re-add them because I’ve changed their format for better performance.
{% endhint %}

### v1.17.9

*Released Aug 7, 2024*

* Improve how the app manages "database is locked" issues when processing a huge amount of Google Maps SERP tasks.
* Improve how the app manages "database is locked" issues when counting uncollected SERP tasks.

### v1.17.8

*Released July 31, 2024*

* Improve how the app manages "database is locked" issues when processing SERP Clustering for over 100,000 keywords.

### v1.17.7

*Released July 26, 2024*

* Fixed the "database is locked" error when visiting a SERP Clustering report with over 60,000 clustered keywords.
* Only check the DataForSEO and Renting API service balance when credentials are filled out.

### v1.17.6

*Released July 20, 2024*

* Fixed the GMB Rank Tracker tool cannot export report on Windows.

### v1.17.5

*Released July 12, 2024*

* Fixed an issue when exporting a large list of keyword clusters (over 40,000 keywords).

### v1.17.4

*Released July 10, 2024*

* Fixed the exported GMB Rank Tracker report doesn't show the correct ranking.
* Fixed ranking data is not updated when changing keywords or when the report has a new snapshot.
* Fixed an issue when exporting a GMB Rank Tracker report after visiting the Bird's Eye view.
* Show unranked keywords when exporting GMB Rank Tracker report.

### v1.17.3

*Released July 9, 2024*

* Fixed the exported GMB Rank Tracker report doesn't show correct stats.
* Fixed the "file already closed" issue when exporting the GMR Rank Tracker report.

### v1.17.2

*Released July 7, 2024*

* Added the ability to export selected snapshot instead of the latest snapshot.
* Add the "Ranking Keywords" tab for the GMB Rank Tracker tool.
* Fixed the snapshot is stuck when using DFS API in GMB Rank Tracker tool.
* Fixed styles are not loaded in exported GMB Rank Tracker reports.
* Fixed the competitors are not loaded when clicking on a grid point.
* Fixed the average rank badge color is not shown correctly.

### v1.17.1

*Released July 3, 2024*

* Fixed the markers that are not loaded.

### v1.17.0

*Released July 3, 2024*

* Added the ability to export the GMB Rank Tracker report as PDF and HTML.
* Added Bird's Eye View for the GMB Rank Tracker report.
* Added the ability to schedule specific days to run the GMB Rank Tracker reports.
* Added the ability to retry stuck snapshots in the GMB Rank Tracker tool.
* Added log to show how many tasks are left from DataForSEO API.
* Added the center map button.
* Fixed cannot delete the current snapshot when pending.

### v1.16.3

*Released June 26, 2024*

* Added the ability to bulk check search intents of keywords.
* Fixed an issue when saving a large list of backlinks and traffic data.
* Fixed an issue when determining keywords to scrape SERP in the SERP Clustering tool.

### v1.16.2

*Released June 25, 2024*

* Added the ability to check the index of URL using [Bing Webmaster Tools API](/guide/indexnow#two-checking-index-methods).
* Fixed the position is not set correctly when using proxies to scrape SERP.
* Added View Google Drive Folder button.
* Fixed the "Analyze SERP" action that doesn't work when the domain count is over 100.

### v1.16.1

*Released June 24, 2024*

* Fixed an issue that caused the app to crash.

### v1.16.0

*Released June 24, 2024*

* Added the ability to distribute keywords to existing clusters in the SERP Clustering tool.
* Added the ability to view ranking for a target domain in the SERP Clustering tool.
* Added SERP Clustering Ranking metric cards.
* Added the ability to set the primary keyword of a cluster by using CPC.
* Added the ability to map CPC and Search Intent columns in the SERP Clustering tool.
* Added HTML sitemap support for the sitemap extractor tool.
* Added a help text about the HTML sitemap limitation.
* Added the ability to delete the current snapshot of the GMB Rank Tracker tool.
* Added rank changes for each marker on the GMB Rank Tracker map.
* Added cards to the Dashboard page that show your current balances with DataForSEO and the Renting API Service.
* Show cluster count and non-clustered keyword count, and update the algorithm to not group clusters that have one keyword.
* Handle auto-zoom better to fit the grid inside the GMB Rank Tracker map.
* Fixed the query and performance issues when running SERP clustering on a huge set of keywords.
* Fixed the SERP table doesn't show the correct ranking for child keywords.
* Fixed the Google Autocomplete tool does not return all keywords in non-UTF-8 charset.

### v1.15.4

*Released June 14, 2024*

* Fixed unknown time zone issue in some systems

### v1.15.3

*Released June 13, 2024*

* Added the ability to set a time window for running scheduled GMB rank tracker reports.
* Added the ability to add businesses via Google Maps URL.
* Added validation rule for "Scrape Data With" field.
* Added the ability to view competitor's ranking on the map.
* Added the ability to delete multiple selected markers.
* Added the ability to move one or many markers.
* Fixed Average Rank calculation.
* Fixed SERP data is not exported all in the SERP Clustering tool.
* Fixed an issue that caused the app to crash when scraping data from DataForSEO API.

### v1.15.2

*Released June 9, 2024*

* Fixed another issue that causes the GMB rank tracker to run multiple times when the Schedule field is set to Weekly.

### v1.15.1

*Released June 9, 2024*

* Fixed the GMB rank tracker running multiple times when the Schedule field is set to Weekly.
* Added SERP clustering and SERP analyzing loading indicator on the reports page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f6d8b842ca0663cdd232ec29db3d318df0227ffd%2FCleanShot%202024-06-08%20at%2010.59.24%402x.png?alt=media" alt=""><figcaption><p>Loading indicators</p></figcaption></figure>

* Fixed the organic keywords filter that doesn't work with URL.
* Added the ability to clear cache after saving settings.

### v1.15.0

*Released June 7, 2024*

* Added Google My Business Rank Tracker tool.
* Moved out the "Analyze SERP" action from the other actions button.

### v1.14.2

*Released May 20, 2024*

* Improved the textarea field when copying data.
* Do not send a request to DataForSEO if there is no SERP clustering report running.
* Added a loading indicator for SERP clustering report when running.
* Added a loading indicator for the Bulk Analysis tool.
* Added the ability to split requests if the domain count is over 100.
* Only save organic SERP items when clustering for consistency.
* Use the new filter syntax from DataForSEO for the include/exclude filters.
* Renamed Keyword Bulk Analysis to Bulk Keyword Metrics.

### v1.14.1

*Released May 17, 2024*

* Fixed the SERP position is saved as "0".

### v1.14.0

*Released May 17, 2024*

* Added SERP API.
* Fixed the external search volume that was not ordered correctly when exporting the SERP clustering report.
* Fixed numbers are exported as a string on the SERP Clustering report.

### v1.13.1

*Released May 15, 2024*

* Fixed the issue where data was not cached correctly in some tools.

### v1.13.0

*Released May 15, 2024*

* Added bulk delete proxies.
* Added a loading indicator when adding GSC sites.
* Added default filters for backlinks, traffic, and keyword tools.
* Added sorting, filtering, and an export button for the backlinks tools.
* Hide alert: "No available Google service accounts. Stopping further submissions.". Only show it in the log panel.
* Added Geo Target (UULE) for Bulk Google PAA tool.
* Removed the draggable attribute from clickable elements in the sidebar and header.
* Added the ability to clear cached data on Google Drive.

### v1.12.3

*Released May 10, 2024*

* Fixed: The app crashed on the new installation.

### v1.12.2

*Released May 10, 2024*

* Fixed: The volume history chart does not appear in the Bulk Autocomplete report.
* Added the Legacy Bulk Analysis back.
* Added back-off time for SERP Clustering tool.
* Improved UX of set column header button when importing keywords.
* Fixed the issue when the SERP data sheet is blank.
* Updated SERP Clustering view to view clusters easily.
* Added the ability to map external search volume when importing keywords.
* Added the ability to sort/filter on external search volume.
* Added the ability to remember the last selection of the check search volume field.
* Improved the SERP Clustering report export.
* Fixed the issue where the "Enter License Key" dropdown is not displayed.
* Added intersection mode for Backlink Gap.

### v1.12.1

*Released May 6, 2024*

* Added an alert message when a keyword is missing SERP data in the SERP clustering report.
* Added the ability to set the delay time between requests when scraping SERP data for keywords.

### v1.12.0

*Released May 4, 2024*

* Added SERP Clustering tool.
* Bulk analysis tool and SERP analysis of Keyword Explorer now utilize the Pages Summary endpoint from DataForSEO, which offers an affordable price.
* Added the ability to enter multiple keywords with an include/exclude filter.
* Filtered out invalid keywords before checking search volume.
* Fixed: The Indexed URLs page doesn't refresh the site data after updating the site.
* Added enter license key menu item.
* Added pagination for SERP Clustering, Autocomplete, and Google PAA reports.

### v1.11.1

*Released April 24, 2024*

{% hint style="danger" %}
This version will delete all the **autocomplete keywords** due to the database structure changes. If you wish to retain these keywords, please ensure you export them prior to the update. Otherwise, no action is needed.
{% endhint %}

* Fixed an issue where some Autocomplete keywords are not saved due to changes in the database structure.

### v1.11.0

*Released April 22, 2024*

* Added Backlink Gap tool.
* Added the ability to override the re-check & re-submit index behavior of IndexNow.
* Added the ability to override the re-check & re-submit index behavior of Google Search Console API.
* Added the ability to set names for Google Service Accounts.
* Improved UI/UX for editing the GSC site modal and GSC site listing page.
* Fixed the indexed count indicator is not updated when changing the site.

### v1.10.1

*Released April 17, 2024*

* Fixed an issue where the app crashed due to changes in the database structure.

### v1.10.0

*Released April 17, 2024*

* Added the ability to export and filter the top pages by traffic of a website.
* Added the ability to import proxies in bulk and enable/disable them.
* Added a metric card to indicate how many URLs are indexed on Bing.
* Added the ability to connect many Google Service Accounts for Google Search Console integration.
  * If you have already added a site from Google Search Console, you will need to take [this extra step](/guide/google-search-console#supports-multiple-google-service-accounts-updated-on-april-17-2024) after upgrading to v1.10.0 to continue pulling your keyword data.
* Added the ability to assign tasks for Google Service Accounts.
* Added the ability to check keyword search volume, CPC, and keyword difficulty for the Bulk Autocomplete tool.
* Added the ability to sort the data by clicking on the table column in the Traffic Analysis tool.
* Validate and fix the date-time error when adding a sitemap URL.
* Fixed the issue where traffic competitor filters didn't work with the Renting API Key service.
* Fixed the keyword includes/excludes filters didn't work right when adding multiple keywords.

### v1.9.0

*Released Mar 31, 2024*

* Add the ability to extract keywords from Google/Bing Autocomplete with multiple keyword modifiers and seed keywords.
* Fix an issue where URLs cannot be imported if the sitemap LastMod date field doesn't include time.
* Include a "Refresh Site Domains" button for the Google Search Console tool.
* Add a loading indicator when adding a Google Search Console Site page.
* Fix the issue where URLs are not displayed when adding a sitemap URL.
* Allow free users to access the app and use free tools.
* Implement sitemap URL validation.

### v1.8.0

*Released Mar 22, 2024*

* Added [IndexNow](/guide/indexnow) tool for submitting index to Bing, Yandex, Naver, Seznam.cz, and Yep.
* Added [Page view for Google Search Console integration](/guide/google-search-console#pages-view-updated-on-may-22-2024).
* Added OpenAI integration.
* Added "Insert keywords with AI" tool.
* Added the ability to [set which Google Service Accounts you want to use on specific sites](/guide/auto-indexing-tool#updates-on-march-22-2024).
* Bunches of fixes and improvements.

### v1.7.3

*Released Mar 4, 2024*

* Sanitized the URL to prevent unexpected formatting errors.
* Added Google UULE tool.
* Implemented a new index-checking method using the Google Search Console URL Inspection API.
* Included filters for the Indexed URLs page.
* Executed three concurrent requests when checking an index using the "site:url" operator and proxies.
* Removed the "required" rule for username and password fields when adding a proxy.
* Provided the option to enable/disable Google Service Accounts.
* Fixed an issue where the app crashed when entering a license key.

### v1.7.2

*Released Feb 26, 2024*

* Fixed an issue where the app crashed on the new computer.

### v1.7.1

*Released Feb 25, 2024*

* Fixed an issue where sitemap URLs could not be saved if the Last Mod field is empty.

### v1.7.0

*Released Feb 25, 2024*

* Added Auto Indexing tool
* Automatically check if your sitemap is an index. It will start with the /sitemap\_index.xml file and then go through all other XML files to extract every URL.
* Added Proxy supporting
* The bulk check mentions feature applies the current filters, allowing you to check mentions for specific keywords instead of checking all keywords.
* The Page filter in the Google Search Console now loads data asynchronously, preventing the app from freezing when loading more than 10k pages.

### v1.6.0

*Released Feb 4, 2024*

* Added Google PAA Scrapper
* Add an export button for the Traffic Competitors page
* Add filters for the Traffic Competitors page
* Added Avg Position metric for Traffic Competitors page
* Fixed "Invalid filters" issue for Content Gap

### v1.5.0

*Released Jan 24, 2024*

* Added Content Gap feature
* Added a new Bulk Analysis feature. Now, you can perform all your bulk analyses in one convenient location
* Added Linux support
* Added Word Count filter for Organic Keywords page
* Added User-Agent "SEO Utils Headless Chrome" when scraping HTML content
* Made the keyword clustering script downloadable to reduce the app size
* Fixed the issue where the title extraction functionality returned an incorrect title when checking mentions.

### v1.4.3

*Released Jan 15, 2024*

* Fixed the issue with no windows appearing
* Fixed the issue that caused the app to crash when there was no backlink data from DataForSEO when checking bulk backlinks

### v1.4.2

*Released Jan 15, 2024*

* Added 15 fresh filters for Organic Keywords.
* Added 24 new filters for Backlinks.
* Added a button to export all backlinks.
* The app now remembers your window size and position for next time.
* Show a friendly message when there's no DataForSEO data during bulk processes.
* Added an option to hide "Chat with GSC Data Analyzer".
* Added "Check Mentions Workers" setting.
* Added "New Update" badge for latest version alerts.

### v1.4.1

*Released Jan 10, 2024*

* Added *Not Mentioned In Title* filter for Google Search Console keywords
* Added *Not Mentioned In Meta Description* filter for Google Search Console keywords
* Added *Not Mentioned In Headings* filter for Google Search Console keywords
* Added *Word Count* column and *Word Count* filter for Google Search Console keywords
* Added the ability to export all organic keywords instead of the current page
* Added a button to chat with the GSC Data Analyzer GPT

### v1.4.0

*Released Jan 9, 2024*

* Added [Google Search Console integration](https://help.seoutils.app/guide/google-search-console)
* Fixed some localhost links

### v1.3.2

*Released Dec 28, 2023*

* Fixed the issue where it doesn't allow users to use traffic and keyword tools without entering DataForSEO credentials.

### v1.3.1

*Released Dec 27, 2023*

* Added [Renting API for Traffic + Keyword tools](https://help.seoutils.app/guide/rent-dataforseo-api-key#updated-dec-27-2023-added-api-endpoints-for-traffic-and-keyword-tools)
* Added Ranked Keyword Info on the Backlinks page

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e22865eae8010a6fa7658b0135bf2ffd8174ceba%2FXnapper-2023-12-27-16.03.44.png?alt=media" alt="" width="375"><figcaption><p>Ranked Keyword Info</p></figcaption></figure>

* Fixed the route could not be found issue
* Fixed the issue when links are not clickable in some places

### v1.3.0

*Released Dec 26, 2023*

* Added Keyword Explorer
* Added Links card on the Dashboard page
* Trimmed spaces in the domain/URL before running bulk analysis.

### v1.2.0

*Released Dec 10, 2023*

* Added Bulk Backlinks Analysis
* Added Bulk Referring Domains Analysis
* Added Bulk Traffic Analysis
* Added Bulk Keywords Analysis
* Fixed the issue when cannot disable the Renting Backlinks API

### v1.1.1

*Released Nov 30, 2023*

* Show the backlink search bar when using renting API Key
* Added data-sharing support for other endpoints

### v1.1.0

* Added Renting API Key for Backlinks API. [Read instruction](/guide/rent-dataforseo-api-key).
* Added Google Drive for sharing data. [Read instruction](/guide/data-sharing-with-s3).
* Added changelog link
* Added error monitor

### v1.0.1

* Added self-update button

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-777b3eabe2e2a31b292f8a97ddd0fb5e36e0b8c0%2FXnapper-2023-11-21-14.22.50.png?alt=media" alt="" width="188"><figcaption></figcaption></figure>

### v1.0.0

Added the following features:

* Backlinks Analytics
* Traffic Analytics
* Semantic Keyword Clustering
* Sitemap Extractor
* SERP Similarity


# Contributors

The people whose ideas and feedback shaped SEO Utils. Thank you.

SEO Utils grows from the ideas and feedback of the people who use it. This page thanks those whose suggestions became part of the app.

| Contributor                                                                                        | Contribution                                                                                                                                          |
| -------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Piotr Piekarski](https://piotrpiekarski.com/en/), SEO, GEO and AEO specialist from Poznań, Poland | Suggested the [GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker), a free rank tracker built on your own Search Console data (v2.10.0). |

## Share your idea

Have an idea or feedback for SEO Utils? Post it in the [Facebook Group](https://www.facebook.com/groups/seoutils) or on the [Roadmap](https://seoutils.canny.io/). Suggestions that ship are credited on this page.


# Set Up SEO Utils

Most SEO Utils tools need something set up first: a DataForSEO account, a Google service account, an AI provider key. The **Onboarding** page works out what your tools need and gets you there two ways: your AI app (Claude, ChatGPT, Cursor and others) walks you through each step (recommended), or you follow a checklist yourself.

{% hint style="info" %}
**What you need:** SEO Utils with an active license key, and for the AI path an AI app on the same computer. The [MCP add-on](/guide/mcp-server#setting-up-the-mcp-server) is **not** required: without it, your AI app can set up SEO Utils but cannot run its other tools (the AI path shows **Setup mode** instead of **Full access**).
{% endhint %}

## Start the Onboarding Page

A new install opens the Onboarding page by itself. To come back to it later, click **Finish setup** on the Dashboard, or choose **Onboarding** in the **Quick Links** menu. Once every tool is set up, the Dashboard button is called **Onboarding** instead. Until your license key is active, both stay locked behind **Enter your license key to start**.

{% stepper %}
{% step %}

#### Tell SEO Utils What You Do

Under **What do you do?**, pick every answer that fits: **Agency**, **Local SEO**, **Content & affiliate sites**, **In-house SEO**, **Technical SEO** or **AI search (AEO / GEO)**. Your answers choose the tools to set up and what each one needs.
{% endstep %}

{% step %}

#### Choose How to Set Up

Under **How do you want to set up?**, pick one:

* **Set up with your AI app** (recommended): click **Set up with AI**
* **Set up myself**: click **Set up manually**

You can switch between the two at any time.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-244f7f53066c62d219838971b4f1329e5b5539a0%2Fsetup-ai-onboarding-choose.png?alt=media" alt=""><figcaption><p>Onboarding with two answers picked: the goals (1) and the two ways to set up (2)</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Set Up with Your AI App (Recommended)

{% embed url="<https://youtu.be/d1W2C1KIohI>" %}
Setting up SEO Utils with your AI app (shown with Claude Desktop)
{% endembed %}

{% stepper %}
{% step %}

#### Choose Your App

Under **Which AI app do you use?**, pick **Claude Desktop**, **Claude Code**, **ChatGPT / Codex**, **Cursor**, **VS Code**, **OpenCode** or **Another app**. Apps SEO Utils has heard from before show **Connected before** and skip the next step.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-dad95ae9e10710f7c3cd43b1cda5d14a6dc5edbd%2Fsetup-ai-choose-app.png?alt=media" alt=""><figcaption><p>The three setup steps (1) and the apps to choose from (2)</p></figcaption></figure>
{% endstep %}

{% step %}

#### Connect and Check

Click the **Connect** button with your app's name, for example **Connect Claude Code**. One click does three things:

* Turns on the SEO Utils MCP server
* Adds SEO Utils to your app
* Installs the SEO Utils skill where the app reads one (Claude Desktop takes it as a plugin: the page shows the marketplace to add in Claude)

The list shows **What Connect did**. Then restart your app so it loads SEO Utils:

| App             | What to do                                                                                                |
| --------------- | --------------------------------------------------------------------------------------------------------- |
| Claude Desktop  | Quit it from the menu bar (closing its window is not enough), then open it again                          |
| Claude Code     | Start a new session: run `claude` in any folder                                                           |
| ChatGPT / Codex | In the ChatGPT desktop app, select **Restart** in its MCP settings. In the Codex CLI, start a new session |
| Cursor, VS Code | Confirm adding SEO Utils in the app                                                                       |
| OpenCode        | Restart OpenCode                                                                                          |
| Another app     | Add the connection settings in your app, then restart it. **Open the MCP settings** shows them            |

SEO Utils notices the moment your app loads it: the page turns green by itself and moves on. If nothing happens after 30 seconds, it shows a tip for your app. If you changed anything, click **Connect again**. If it still doesn't work, see [Troubleshooting](#troubleshooting).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-aa9445b5147148be3ff0c05078eb6aa5b527db07%2Fsetup-ai-connect.png?alt=media" alt=""><figcaption><p>Connect Claude Code (1), what the button does (2), and the restart SEO Utils waits for (3)</p></figcaption></figure>
{% endstep %}

{% step %}

#### Set Up Your Tools

The page now reads **Set up your tools with** your app. Click **Copy prompt** under **Paste this into** your app's name and paste it into a new chat. The prompt names your answers from the first screen, for example: "Help me set up SEO Utils for: Local SEO, Content & affiliate sites. Start with what my tools need most, and tell me what to set up next."

Your AI app checks what is already set up, explains what each missing step is for and what it costs, opens the right page in SEO Utils for you, checks again after you save, and suggests the next tool. It also reads the pages of this help site to explain a step.

Prefer one tool at a time? **Or set up one tool at a time** lists your tools as **Ready to use** or **Needs** with the missing steps. **Copy prompt** on a row asks the AI for just that tool, and each row updates by itself. **Extras** and **More tools for your goals** are optional.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5477036766459c074ab3ae64501c82d0c48623d7%2Fsetup-ai-tools.png?alt=media" alt=""><figcaption><p>The starter prompt to paste into your app (1) and the tools it will set up (2)</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Keys and passwords go in SEO Utils, never in the chat.** When a step needs an API key, your AI app opens the right settings page and you paste the value there and click **Save**. If you paste a secret into the chat by mistake, the AI tells you to enter it in SEO Utils instead.
{% endhint %}

## Set Up Yourself

**Set up manually** opens **Set up SEO Utils yourself**: the things your tools need, in order, with the next one already open. The counter (1), for example **2 of 4 done**, updates as you go. Each step offers:

* **Connect Google** (2): creates the Google service account or the Places API key for you (see [Connect Google Automatically](#connect-google-automatically))
* **Open settings** (3): takes you to the right settings page and highlights the field to fill
* **Set up with your AI app** (4): hands that one step to your AI app
* **Read the guide**: opens the help page for the step

**Your tools** below the steps shows each tool as **Ready to use** or **Needs** with what is missing.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e916bc14d1937563b2689f3ad7fa3dda9a678733%2Fsetup-ai-manual-checklist.png?alt=media" alt=""><figcaption><p>The manual checklist: the counter (1) and the buttons of the Google Places API key step (2 to 4)</p></figcaption></figure>

The checklist lists only what your answers need. Each step has a guide:

| Step                        | What to do                                                                                                                                  | Guide                                                                                                                                                              |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| License key                 | Paste the key from your purchase email and activate it                                                                                      | [Manage License Key](/guide/manage-license-key)                                                                                                                    |
| DataForSEO API              | Create an account, top up at least $50 (or rent a key for a smaller budget), paste the API login and password in the DataForSEO card        | [SEO Data Source](/guide/seo-data-source#how-to-connect-your-dataforseo-account-to-seo-utils), [Rent DataForSEO API Key](/guide/rent-dataforseo-api-key)           |
| Google service account      | Create it in Google Cloud and add its key on the Google Service Accounts page, then add its email to your Search Console and GA4 properties | [Google Service Accounts](/guide/google-service-accounts)                                                                                                          |
| Google Places API key       | Create a key for the Places, Maps JavaScript and Geocoding APIs and paste it in the Google Business Rank Tracker settings                   | [GMB Rank Tracker](/guide/google-my-business-rank-tracker/set-up#google-places-api-key)                                                                            |
| AI key for LLM Rank Tracker | Paste an OpenAI or OpenRouter key in the AI Settings card                                                                                   | [LLM Rank Tracker](/guide/llm-rank-tracker)                                                                                                                        |
| SMTP credentials            | Add your mailbox's host, port, user and password on the SMTP page                                                                           | [SMTP Credentials](/guide/smtp-credentials)                                                                                                                        |
| IndexNow key                | Create the key, upload its file to your site and paste the key in IndexNow                                                                  | [IndexNow](/guide/indexnow)                                                                                                                                        |
| Chrome or Edge              | Install one of them on this computer                                                                                                        | —                                                                                                                                                                  |
| **Extras**                  | Workspaces, the S3 cache, Remote Access and the MCP add-on are optional                                                                     | [Workspace](/guide/workspace), [S3 Cache for DataForSEO Data](/guide/data-sharing-with-s3), [Remote Access](/guide/remote-access), [MCP Server](/guide/mcp-server) |

Other keys (an AI provider, TypeSafe, NLP and so on) appear only when a tool you picked needs them, and each step names the card to paste the key in.

## When a Tool Is Not Set Up

A tool that still misses something lists each missing step with the same buttons, including **Set up with your AI app**. On a run form the panel reads **Set up** the tool **to start**. On a tool that already has reports, a notice above them reads **New runs are paused: a setup step needs you** and your reports stay. A team member sees whom to ask instead.

If an AI app used SEO Utils recently, **Set up with your AI app** copies the prompt for that step and tells you where to paste it. Otherwise it opens the AI path above.

After you leave Onboarding, a **Resume Onboarding** pill with a count such as **4/9 tools** appears on other pages until every tool is ready. Click it to come back, or click **×** to hide it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a99523c83f37685515eee7347de2eddffa09f256%2Fsetup-ai-tool-panel.png?alt=media" alt=""><figcaption><p>The setup notice on a tool page (1), its Set up with your AI app button (2) and the Resume Onboarding pill (3)</p></figcaption></figure>

## Connect Google Automatically

A Google service account (Search Console, Indexing, Google Analytics 4, SEO Tests) and the Places API key (GMB tools) normally take a long visit to the Google Cloud console. **Connect Google** does it for you. Start it from any of these:

* **Connect Google** on the [Google Service Accounts](/guide/google-service-accounts) page, next to **Add Account**
* **Connect Google** on the Google service account and Google Places API key steps of Onboarding and of a tool's setup panel
* **Create a key automatically**, under the Google Places API Key in the Google Business Rank Tracker settings: it opens Connect Google with the Google Maps tools switched on

Your AI app can start it too when you ask it to set up the Google service account.

{% stepper %}
{% step %}

#### Choose What to Set Up

**Search Console, Indexing and Google Analytics 4** are always included, and free. Switch on **Google Maps tools** to add a Places API key for GMB Rank Tracker, GMB Reviews and NAP Finder. Click **Connect Google**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d67727894b00d895a4232009b4db2a672d72cc33%2Fsetup-ai-connect-google.png?alt=media" alt=""><figcaption><p>The Connect Google page: what it sets up (1) and the Connect Google button (2)</p></figcaption></figure>
{% endstep %}

{% step %}

#### Let It Run

SEO Utils works through these steps and shows each one under **Progress**:

1. **Get Google's Cloud CLI**: downloads Google's own command-line tool if needed (about 0.5 GB while it runs, removed afterwards). Your own Google Cloud CLI is left alone
2. **Sign in to Google**: your browser opens Google's sign-in page. Sign in and click **Allow**. SEO Utils never sees your password
3. **Create a Google Cloud project** for SEO Utils, or reuse the one an earlier setup made
4. **Turn on the Google APIs** SEO Utils uses
5. **Create the service account** and **add it to SEO Utils**. Its key goes straight into SEO Utils, never through the chat or a log
6. With **Google Maps tools** on: **Create a Google Places API key** that works only with the Maps APIs, then **Billing for the Maps APIs**

It takes about 3 minutes. You can leave the page: a pill in the corner shows **Google setup** with the progress, turns amber with **Google setup needs you** when it has a question, and brings you back. **Stop setup** cancels it.
{% endstep %}

{% step %}

#### Answer Its Questions

When a **Needs you** card appears, answer it in SEO Utils: Google Cloud's terms, a project you already have, a temporary organization role (only when a Workspace organization blocks a step) or a billing account for the Maps tools. SEO Utils changes nothing in your organization or billing until you say yes. Each question is explained in [Troubleshooting](#troubleshooting).
{% endstep %}

{% step %}

#### Finish in Google

The page now reads **Google is connected** and shows the project, the service account and the Places API key. Under **Finish in Google**, do the two steps only you can do, once for each property (Google does not let any program do them):

* **Search Console**: **Settings → Users and permissions → Add user**, paste the service account email (**Copy email**) and choose **Owner**
* **Google Analytics 4**: **Admin → Property access management → Add users**, paste the email and choose **Viewer**
  {% endstep %}
  {% endstepper %}

SEO Utils cleans up after itself: the downloaded tool, its sign-in and any temporary organization role are removed when the run ends. **Delete SEO Utils projects you no longer use** removes projects it made earlier (Google keeps them for 30 days). To do it all by hand, click **Add a service account by hand** and follow [Google Service Accounts](/guide/google-service-accounts).

## Troubleshooting

<details>

<summary>Google Cloud setup asks a question or stops</summary>

Answer on the **Connect Google** page; the **Google setup needs you** pill follows you to other pages. Your AI app can explain a step but never answers for you.

| Question or problem                                     | What to do                                                                                                                                                                                                                         |
| ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Accept Google Cloud's terms**                         | Click **Open Google Cloud console**, sign in as the account shown, choose your country, accept the terms (no free trial needed) and click **Done** in SEO Utils                                                                    |
| **Sign in to Google in your browser**                   | Click **Open the Google sign-in page** if no window opened, then **Allow**. After 10 minutes SEO Utils stops: start again                                                                                                          |
| Your account can't create projects in your organization | A Google Workspace organization limits it. An administrator can let SEO Utils grant the Project Creator role for at most one hour. Otherwise ask your administrator or use a personal Google (Gmail) account                       |
| Your organization blocks service-account keys           | Same fix with the Organization Policy Administrator role, which allows keys in the SEO Utils project only                                                                                                                          |
| **Use a project you already have?**                     | **Use this project** keeps a billing slot free. **Create a new project** starts fresh                                                                                                                                              |
| **Link a billing account for the Maps tools?**          | Optional: business search works without it, addresses and the map need it. Pick an account, or **Skip for now** and use **Turn on billing for Maps** later                                                                         |
| Google refused the billing account                      | Full account: pick another, click **Unlink billing from a project I no longer use**, or free a slot on the billing page (**Open Google Cloud billing**). Closed account: reopen it there or pick another. None open: add one there |
| A Free Trial sign-up fails with `OR_BACR2_59`           | Google refused the payment verification. Try another card or Google billing support                                                                                                                                                |
| Not enough disk space                                   | About 0.5 GB must be free while it runs. Free some space and click **Try again**                                                                                                                                                   |
| The project can no longer be changed by this account    | Sign in with the account that created it, or click **Run the setup again**                                                                                                                                                         |

For any other stop, click **Try again**, or **Add a service account by hand**.

</details>

<details>

<summary>Your AI app does not see SEO Utils</summary>

After **Connect**, your app loads SEO Utils only when it starts. Check these in order:

1. **Restart the app the way the page says** (see the table in step 2 above), then click **Connect** again if you changed anything
2. **Open SEO Utils.** The app can start first, but SEO Utils must be running when you ask
3. **Check the MCP server:** in **Settings → Services → MCP Server**, the badge reads **Running (port …)**. If it doesn't, see [MCP Server → Troubleshooting](/guide/mcp-server#troubleshooting)
4. **Check the app itself:**

| App             | Check that SEO Utils is there                                                         |
| --------------- | ------------------------------------------------------------------------------------- |
| Claude Desktop  | **Settings › Developer**: `seo-utils` is running                                      |
| Claude Code     | Run `/mcp`: `seo-utils` is listed as connected                                        |
| ChatGPT / Codex | Run `codex mcp list`: `seo-utils` is listed                                           |
| Cursor          | **Settings › MCP**: switch `seo-utils` on                                             |
| VS Code         | Run **MCP: List Servers** and start `seo-utils`                                       |
| OpenCode        | Run `opencode mcp list`: `seo-utils` is listed                                        |
| Another app     | Add the connection settings in the app's MCP settings again; some apps need a restart |

On Windows, fully quit Claude Desktop (tray icon or Task Manager) before reopening it.

</details>

<details>

<summary>Your AI app says it couldn't reach SEO Utils</summary>

Your app sees SEO Utils, but its requests don't get through. The AI's error says why, and so does **Settings → Services → MCP Server**: an amber box there names each AI app whose last request failed. The box clears once that app reaches SEO Utils again.

| The error says                                                                   | What to do                                                                                             |
| -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| Nothing answers on the port                                                      | Open SEO Utils and turn on the MCP server, then ask again                                              |
| There is no MCP token in a folder                                                | SEO Utils keeps its data in another folder. Click **Connect** for that app again                       |
| The connection was closed before SEO Utils answered, or it dropped during a call | Antivirus web protection is the usual cause. Add SEO Utils as an exception (below)                     |
| Another program answers on the port                                              | Another app uses that port. Change the port in **Settings → MCP Server**, then click **Connect** again |

**Add SEO Utils as an antivirus exception.** Antivirus web protection (such as AVG or Avast Web Shield) can drop the local connections your AI app uses to reach SEO Utils. In AVG or Avast on Windows:

1. Open the antivirus, click **Menu**, then **Settings**
2. On the **General** tab, open **Exceptions** and click **Add exception**
3. Add the SEO Utils program: `C:\Program Files\SEO Utils\SEO Utils\SEO Utils.exe`
4. Fully quit your AI app, open it again with SEO Utils running, and ask again

On a Mac, add `/Applications/SEO Utils.app` to the antivirus's exceptions. Other antivirus apps (Norton, Kaspersky, ESET, Bitdefender) have a similar exception list for their web protection. To check that the antivirus is the cause, turn its protection off for a minute and ask again: if it works, add the exception and turn the protection back on.

</details>

<details>

<summary>ChatGPT: use Work or Codex mode</summary>

In the ChatGPT desktop app, **Chat** mode can't use tools on this computer, so it can't see SEO Utils. Switch to **Work** or **Codex** mode.

</details>

<details>

<summary>Only setup actions work</summary>

If **Access** on the Dashboard's AI assistant card reads **Setup only**, the MCP add-on isn't active. Your AI app can still connect and set up SEO Utils, but every other action answers that it needs the add-on.

Before it does such a task by hand, for example by clicking through SEO Utils, your AI app recommends the add-on with its purchase link. With the add-on it is much faster than clicking through the app, it works in the background without taking over your screen, and it has all of SEO Utils' data to answer from. If you prefer to do the task by hand, tell the AI and it still helps.

To buy it, click **Get the MCP add-on** on the card, then click **Refresh** in **Settings → Services → MCP Server**.

</details>

The MCP server not starting or moving to another port, and getting help from the AI with **Copy error**, are in [MCP Server → Troubleshooting](/guide/mcp-server#troubleshooting). For install and runtime problems of the app itself, see [Troubleshooting](/troubleshooting).


# Manage License Key

### Access the License Key Manager

You can access the License Key Manager from the user dropdown in the app.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e00ec32dc56a555813871e913a2634ba33355453%2FXnapper-2025-01-18-21.36.22.png?alt=media" alt=""><figcaption><p>License Key Manager</p></figcaption></figure>

{% hint style="success" %}
**Important:** You can also access the License Manager via this URL <https://app.lemonsqueezy.com/my-orders>.
{% endhint %}

### Deactivate the License Key From a Device

There are two ways to deactivate a device from your license key.

#### Option 1: Manage Devices Page

Visit <https://app.seoutils.app/manage-devices> to view and deactivate all devices activated on your license — even devices you no longer have access to.

{% stepper %}
{% step %}
**Enter Your License Key and Email**

Enter your license key and the **email address used to purchase** the license, then click **"Continue"**.
{% endstep %}

{% step %}
**Verify Your Email**

A verification link will be sent to your email. Click the link in the email to verify ownership. The link expires in 10 minutes.

{% hint style="info" %}
Your session is remembered for 30 days, so you won't need to verify again on the same browser.
{% endhint %}
{% endstep %}

{% step %}
**Deactivate Devices**

You'll see a list of all devices activated on your license. Click **"Deactivate"** next to any device you want to remove.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Only the license key owner (the email used during purchase) can access the Manage Devices page. This prevents unauthorized deactivation.
{% endhint %}

{% hint style="info" %}
**Expired license:** the page lists your devices under a **This license has expired** notice. Lemon Squeezy does not release the devices of an expired license, so **"Deactivate"** works again once you [renew it](#renew-your-license-key). To use another license key on one of these computers now, deactivate the license from the app on that computer ([Option 3](#option-3-from-the-app-on-this-computer)).
{% endhint %}

#### Option 2: From the Lemon Squeezy Dashboard

To deactivate the license key from your current device and activate it on a new one, go to the [License Key Manager](#access-the-license-key-manager) and follow these steps.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7a14b92dd17ece6b9626eed201d0405f155179dd%2FXnapper-2025-01-18-21.43.50.png?alt=media" alt=""><figcaption><p>Deactivate a device</p></figcaption></figure>

#### Option 3: From the App on This Computer

Open the user menu, choose **License Manager**, and find **Deactivate license on this computer**. This frees the activation slot so the license can be used on another computer; SEO Utils stops working here until a license key is activated again.

Click **"Deactivate license"** to confirm, or **"Keep it activated"** to go back. Your reports and data on this computer are not deleted.

{% hint style="info" %}
If Remote Access is on for this computer, the dialog also reminds you that browser access ends immediately and that your Remote Access plan is not cancelled. See [Remote Access](/guide/remote-access#deactivating-your-license-on-this-computer).
{% endhint %}

{% hint style="danger" %}
**An expired license key cannot be activated again until it is renewed.** If your license has expired, the dialog shows a red warning and asks you to tick **I understand this license key cannot be activated again, here or on another computer, until it is renewed** before **"Deactivate anyway"** becomes available. Use **"Renew license key"** first if you plan to keep using SEO Utils.
{% endhint %}

For an expired license, **"Deactivate anyway"** removes the key from this computer so you can enter another license key right away. Lemon Squeezy still counts this computer as one of the license's devices until the license is renewed.

If the expired key cannot open your version of SEO Utils, the app shows **You Don't Have Access to This Version!** instead. Click **"Deactivate the expired license key"** on that page to open the License Manager.

### Renew Your License Key

To renew your license key please visit this URL <https://app.seoutils.app/renew-license-key>.

{% hint style="danger" %}
You can re-activate your license on new devices as long as it’s valid. However, once it expires, re-activation is no longer possible due to Lemon Squeezy’s system.
{% endhint %}

{% hint style="success" %}
**Renewed a license you deactivated from the app?** Enter the same license key on the same computer. SEO Utils takes back the device that computer had, so you do not need to free it in Manage Devices first.
{% endhint %}


# Workspace

Workspaces in SEO Utils allow you to organize and separate your projects, clients, or different SEO campaigns. Each workspace maintains its own set of data, making it easy to manage multiple projects without mixing information.

## What are Workspaces?

Workspaces act as separate containers for your SEO data. When you switch between workspaces, you're essentially switching between different databases of:

* [Organic Rank Tracker reports](/guide/organic-rank-tracker)
* [GMB Rank Tracker reports](/guide/google-my-business-rank-tracker)
* [LLM Rank Tracker reports](/guide/llm-rank-tracker)
* [Content Structs](/guide/content-struct)
* [Google Search Console properties](/guide/google-search-console)
* And many more...

### Default Workspace

Every SEO Utils installation comes with a **Default** that cannot be deleted. This ensures you always have at least one workspace to work with.

## Managing Workspaces

### Accessing Workspaces

You can access the workspace switcher from the sidebar. The current active workspace is displayed with its logo (if set) or a default icon.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cdbd5010ef19c5d7171b64e42ac0efe6fa862a8b%2FXnapper-2025-08-14-23.05.36.png?alt=media" alt=""><figcaption><p>Workspace switcher in the sidebar</p></figcaption></figure>

### Creating a New Workspace

#### Step 1

Click on the workspace switcher in the sidebar to open the dropdown menu.

#### Step 2

Click on the **"Add workspace"** button at the bottom of the dropdown.

#### Step 3

Enter a **name** for your workspace and optionally add a **logo URL** to help identify it visually.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9de4bdcf420b1cbb2d56276680132556cc2a6931%2FXnapper-2025-08-14-23.09.26.png?alt=media" alt="" width="563"><figcaption><p>Create workspace modal</p></figcaption></figure>

Click **"Create"** to create the workspace, or **"Create & Switch"** to create and immediately switch to the new workspace.

### Editing a Workspace

To edit an existing workspace:

1. Open the workspace dropdown
2. Hover over the workspace you want to edit
3. Click the **pencil icon** that appears
4. Update the name or logo URL
5. Click **"Save"** to apply changes

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c4f6b273a91a3c3d6cd8a77efcd0deca916caa78%2FCleanShot%202025-08-14%20at%2023.10.22%402x.png?alt=media" alt="" width="288"><figcaption><p>Edit workspace by clicking the pencil icon</p></figcaption></figure>

### Deleting a Workspace

{% hint style="warning" %}
You can only delete workspaces that contain **no data**. If a workspace has any reports, tracked keywords, or other data, you must first delete or move that data before deleting the workspace.
{% endhint %}

To delete a workspace:

1. Open the workspace dropdown
2. Hover over the workspace you want to delete
3. Click the **trash icon** that appears
4. Confirm the deletion in the modal

{% hint style="info" %}
The **Default Workspace** cannot be deleted.
{% endhint %}

## Switching Between Workspaces

### Using the Dropdown

Click on any workspace in the dropdown to switch to it. The app will reload with the selected workspace's data.

### Using Keyboard Shortcuts

You can quickly switch between workspaces using keyboard shortcuts:

* **Mac**: `⌘1` through `⌘9`
* **Windows/Linux**: `Ctrl+1` through `Ctrl+9`

The number corresponds to the workspace's position in your list. For example, `⌘1` switches to the first workspace, `⌘2` to the second, and so on.

### Reordering Workspaces

You can reorder workspaces to customize your keyboard shortcuts:

1. Open the workspace dropdown
2. Hover over a workspace to see the **drag handle** (grip icon)
3. Click and drag the workspace to your desired position
4. Release to save the new order

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2242d4efc94b43cad74e5944566532b4beeea1f5%2FCleanShot%202025-08-14%20at%2023.10.22%202%402x.png?alt=media" alt="" width="288"><figcaption><p>Drag workspaces to reorder them</p></figcaption></figure>

## Moving Data Between Workspaces

You can move existing data from one workspace to another using the bulk move feature:

### Moving Multiple Records

1. Select the records you want to move (using checkboxes in any data table)
2. Click on **"Bulk Actions"** button
3. Select **"Move to Workspace"**
4. Choose the target workspace from the dropdown
5. Click **"Execute"** to move the selected records

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-80bcc5e73fd80619c6d482dc368f9b68fbd7efe4%2FXnapper-2025-08-14-23.12.54.png?alt=media" alt=""><figcaption><p>Bulk move records to another workspace</p></figcaption></figure>

## Use Cases for Workspaces

### Client Management

Create separate workspaces for each client to keep their SEO data isolated:

* **Client A Workspace**: Contains all rank tracking, backlinks, and reports for Client A
* **Client B Workspace**: Separate data for Client B
* **Personal Projects**: Your own website's SEO data

### Project Organization

Organize different projects or websites:

* **E-commerce Site**: Track product page rankings and organic traffic
* **Blog Network**: Monitor multiple blog sites
* **Local Business**: Track Google Business rankings and local SEO

### Team Collaboration

Different teams or departments can have their own workspaces:

* **Content Team**: Focus on content analysis and optimization
* **Link Building Team**: Track backlink campaigns
* **Technical SEO**: Monitor site health and technical metrics

## Important Notes

* Each workspace maintains completely **separate data**
* Switching workspaces will **refresh the current view** to show the new workspace's data
* Workspace settings are **saved locally** and persist between app sessions
* The active workspace is **remembered** when you close and reopen the app
* All API keys and service accounts are **shared across all workspaces**

## Best Practices

1. **Name workspaces clearly**: Use descriptive names like "Client - ABC Corp" or "Project - Summer Campaign"
2. **Add logos**: Upload client logos or project icons to quickly identify workspaces visually
3. **Organize by priority**: Place your most-used workspaces at the top for quick keyboard access
4. **Regular cleanup**: Delete empty workspaces you no longer need to keep your list organized
5. **Move data carefully**: Double-check the target workspace before moving important data


# SEO Data Source

What is the source of backlinks and traffic data in SEO Utils?

First, you need to know that, SEO Utils is just a desktop application that provides you with a set of SEO tools including Backlinks Analytics and traffic Analytics. SEO Utils doesn't have a backlinks or keyword database.

The main database is from DataForSEO.

## What is DataForSEO

[DataForSEO](https://try.dataforseo.com/nz7sp2xfvovq) is a solution that provides comprehensive SEO and digital marketing data via API. Currently, DataForSEO database has over 9 billion keywords (Google + Bing) and over 2.81 trillion backlinks

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-493b98d5aa53d1efa3643cc5cb46ab55dc607608%2FXnapper-2023-11-18-13.49.50.png?alt=media" alt=""><figcaption><p>Source: <a href="https://dataforseo.com/our-data/?aff=134458">https://dataforseo.com/our-data</a></p></figcaption></figure>

Ahrefs boasts the most extensive backlink database in the market, while SEMrush leads with the largest collection of keywords. DataForSEO stands out for its highly competitive pricing, complemented by a database that is equally formidable.

You **don't need a subscription**. With DataForSEO, you pay only for the individual services you consume. The **pay-as-you-go** pricing model is designed to help you minimize costs, increase resource efficiency, and build operational resilience.

{% hint style="info" %}
DataForSEO's smallest top-up is $50. To start with $10 or $20 instead, [rent a DataForSEO API key](/guide/rent-dataforseo-api-key) from SEO Utils.
{% endhint %}

If you're seeking a budget-friendly alternative to Ahrefs or SEMrush, this option is ideal. Even for those already using Ahrefs or SEMrush, adding an additional data source can significantly enhance your SEO insights. A rich keyword database helps in identifying trending topics, enabling you to create content that better resonates with your audience and aligns with their interests.

{% hint style="info" %}
**Read more:** [Backlink APIs: An In-Depth Comparison of DataForSEO, Ahrefs, and Semrush](https://dataforseo.com/blog/backlink-api-comparison-dataforseo-ahrefs-semrush/?aff=134458)
{% endhint %}

### What Are the Roles of SEO Utils?

You might wonder why you need SEO Utils when you can directly access data from DataForSEO. The key difference is that DataForSEO only offers data through an API, without the user-friendly interface (UI) you see in tools like Ahrefs or SEMrush. So, if you don't have coding skills or are not familiar with using APIs, SEO Utils steps in to fill this gap.

Understanding the importance of data presentation, SEO Utils provides a smart and clean UI to help you interact with the data effectively.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6cd80149e1fccb2585a03fdb01230425ffe98fc4%2FCleanShot%202023-11-18%20at%2014.37.24%402x.png?alt=media" alt=""><figcaption><p>SEO Utils</p></figcaption></figure>

Also, SEO Utils adds a cache layer to help you save costs when pulling data from DataForSEO.

For example, when you check a website's backlinks, SEO Utils saves the first page's data in the cache. If you go to the second page and then come back to the first, it uses the saved data instead of making another API request. This way, you don't end up pulling the same data twice for the same page or filters, saving both time and resources.

Besides Backlinks and Traffic Analytics, SEO Utils offers more handy tools. This includes [Keyword Clustering](/guide/semantic-keyword-clustering) for grouping a million keywords, a Sitemap Extractor to easily understand website structure, and an AI Content Writer to help you create great content quickly and easily.

### How to Connect Your DataForSEO Account to SEO Utils?

1. First, you need to register a DataForSEO account at: <https://try.dataforseo.com/nz7sp2xfvovq>
2. Visit <https://app.dataforseo.com/api-access> to grab your API login & API password

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-bf73f152c9e9f08c72911e1948dd28b6100cba1d%2FXnapper-2023-11-18-14.31.30.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
API login and API password are **NOT** the username and password you use to log in to the DataForSEO dashboard.
{% endhint %}

3. Open SEO Utils on your computer, and click on the App dropdown in the top-left of the app.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-95dadf2d06463d59075fcc2c5723e462bcb1d1b5%2FXnapper-2023-11-18-14.33.14.png?alt=media" alt=""><figcaption></figcaption></figure>

4. Scroll down to the DataForSEO section, and enter your login + password.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4640b62ac7e670170b908692382fdc1f5640ff3e%2FXnapper-2023-11-18-14.34.19.png?alt=media" alt=""><figcaption></figcaption></figure>

5. Start using SEO Utils to pull backlinks, traffic, and keyword data.

{% hint style="info" %}
**Your API credentials will be saved locally, nothing leaves your computer.**
{% endhint %}

### Refresh the Location Lists

The **Location** and **Language** fields in the tools offer the lists that DataForSEO publishes. SEO Utils downloads them for you and refreshes them on its own, and you don't need a DataForSEO account for this. The lists are free to download.

To download the latest lists right now, for example when a new city or postal code is missing, go to **Settings > Services > DataForSEO API** and click **Refresh location lists**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ddb8e9f03a5d5dcb621587db63a51a824b51a91b%2Fseo-data-source-refresh-location-lists.png?alt=media" alt=""><figcaption><p>(1) Click Refresh location lists to download the latest lists now</p></figcaption></figure>

{% hint style="info" %}
The first time you start SEO Utils, the lists download in the background. Until they arrive, the Location field says they are still downloading and fills in by itself.
{% endhint %}


# Keyword Metrics Data Source

Choose where SEO Utils gets search volume from, see which source every number came from, and tell "no data" apart from a real zero.

Search volume, the monthly trend, CPC and competition all come from DataForSEO — but DataForSEO does not have one set of numbers. It has several, gathered in different ways, priced differently, and they do not always agree.

You choose which of them each check uses. Every checked number carries a label saying where it came from, and a keyword the source has no figure for says so, rather than showing zero searches.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FDLo7IWrxFZG5lrTTbKZb%2FXnapper-2026-09-16-12.54.19.png?alt=media&amp;token=e13cfa0c-b552-4f0f-b480-29bdfacc663e" alt="The keyword metrics source dropdown open, showing six sources in three groups with their descriptions and prices"><figcaption><p>Six sources in three groups, each with what it does and roughly what it costs</p></figcaption></figure>

## Where a Search Volume Comes From

A search volume in SEO Utils is not a fact about the keyword. It is the answer one particular DataForSEO source gave, for that keyword, in that location and language, on the day you asked.

The sources do not all know the same keywords. The default is a database rebuilt monthly from Google Ads data — cheap, broad, and not complete. A keyword that is not in it comes back with **no figure at all**, which is a different thing from a figure of zero. Other sources ask Google Ads directly, or estimate from clickstream panels, and they cover keywords the database does not.

So two things decide what you see against a keyword:

* **Which source you asked.** You set a default, and you can override it for any single check.
* **Whether that source had anything to say.** No source covers everything, and a keyword one source has never heard of may have real demand according to another.

The rest of this guide is about choosing a source, reading its answer correctly, and telling at a glance which source produced any number in front of you.

## The Six Sources

The sources fall into three groups. The difference between the groups matters more than the difference between the rows inside a group, so start there.

| Source                                 | Best for                                                                                 | About $ per 700 keywords | Who can pay                    |
| -------------------------------------- | ---------------------------------------------------------------------------------------- | ------------------------ | ------------------------------ |
| **DataForSEO Labs database** (default) | Everyday checking. The cheapest source, and the one every tool starts from.              | $0.10                    | Rented key or your own account |
| **Google Ads live**                    | Keywords the database has never heard of, and figures that match Google Keyword Planner. | $0.19                    | Your own account only          |
| **Labs, clickstream-normalized**       | Separating close variants that the database lumps together.                              | $0.11                    | Rented key or your own account |
| **Labs, Bing-normalized**              | The same split, estimated from Bing data instead.                                        | $0.11                    | Rented key or your own account |
| **DataForSEO Search Volume**           | Split figures for *any* keyword, not only those already in the database.                 | $0.28                    | Your own account only          |
| **Clickstream (bulk)**                 | A second opinion from real browsing panels, independent of Google.                       | $0.19                    | Your own account only          |

{% hint style="info" %}
Prices are DataForSEO's list prices, shown for orientation. The estimate counts every keyword you send, so the real cost can be lower.
{% endhint %}

### Google Ads Numbers (Grouped, Rounded)

These are Google's own figures, as Google reports them to advertisers: rounded, and with close variants counted together. This is what most SEO tools show, and what your client will recognise.

* **DataForSEO Labs database** — Google Ads figures from DataForSEO's monthly database. The cheapest source, and the default. Its weakness is coverage: some keywords are simply not in it, and those come back with no figure.
* **Google Ads live** — the same kind of number, fetched from Google Ads at the moment you ask. It answers for keywords the monthly database misses, which is the usual reason a keyword that looked dead turns out to have real demand. It costs about twice the database price and needs your own DataForSEO credentials.

### Google Ads Numbers, Split Per Variant

Google reports one figure for a group of close variants. These three sources take that figure apart and estimate how much of it belongs to each individual keyword.

Use them when you are choosing between near-identical keywords and the grouped figure hides the difference.

* **Labs, clickstream-normalized** — the database figures, re-split using clickstream data.
* **Labs, Bing-normalized** — the same idea, re-split using Bing data. It covers fewer locations, and a location Bing does not cover comes back with no figure.
* **DataForSEO Search Volume** — re-split figures for any keyword, not only those already in the database. The most expensive of the six, and it needs your own DataForSEO credentials.

### Clickstream Numbers (Different Scale)

* **Clickstream (bulk)** — an independent estimate built from clickstream panels: what people were actually observed searching for, rather than what Google reports to advertisers. It needs your own DataForSEO credentials.

{% hint style="warning" %}
**Clickstream figures are not comparable with Google Ads figures.** They are measured differently and are not rounded, so they will not line up with anything else in your reports. For one real keyword, the clickstream estimate was **113,360** where Google Ads reported **135,000**.

Neither number is wrong — they answer slightly different questions. Compare clickstream volumes with other clickstream volumes, and try not to mix the two scales inside one report.
{% endhint %}

## Who Pays for Each Source

Three of the six sources can only be reached with **your own DataForSEO credentials**:

* Google Ads live
* DataForSEO Search Volume
* Clickstream (bulk)

The three Labs sources also work with a [rented DataForSEO key](/guide/rent-dataforseo-api-key), billed to your SEO Utils credits.

If you only have a rented key, those three sources cannot be selected. They appear in the dropdown with a lock icon and the reason underneath:

> Needs your own DataForSEO credentials. The rented key cannot reach this endpoint.

If you have no DataForSEO credentials at all, every source is locked with **"Add DataForSEO credentials to use this source."** until you add some.

{% hint style="info" %}
**If you have both a rented key and your own credentials**, each source uses whichever can reach it: the three Labs sources go through the rented key and are billed to your SEO Utils credits, and the other three use your own DataForSEO account. The cost line always names which one is about to pay.
{% endhint %}

{% content-ref url="/pages/gwYT1OgDY4moZ5jr2WTJ" %}
[Rent DataForSEO API Key](/guide/rent-dataforseo-api-key)
{% endcontent-ref %}

## Choosing a Source

You set a default once, and override it per check whenever you want something different.

### Set the Default

{% stepper %}
{% step %}

#### Open the Setting

In SEO Utils, go to **Settings → Services** and select **Keyword Metrics Source**, under **DataForSEO** in the settings sidebar.
{% endstep %}

{% step %}

#### Pick a Source

Open the **Default source** dropdown, choose a source and click **Save**.

Every check in every tool starts from this source unless you change it for that run.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FOyW3Y9nmSl7lOzbiMoFg%2FXnapper-2026-09-16-12.55.05.png?alt=media&amp;token=fa2f2f39-8cd8-4938-b0f5-687fdd4db280" alt="The Keyword Metrics Source settings card with a default source selected and its cost explanation beneath"><figcaption><p>The default source, with what it fetches per batch and who pays for it</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Only the workspace owner can set the default. Everyone else sees the current value and the note "The default keyword metrics source is set by the workspace owner." They can pick a different source for an individual check.
{% endhint %}

### Choose a Source for One Check

Wherever you check keyword metrics, a **Keyword metrics source** dropdown sits at the top of the form, pre-filled with your default. Pick something else and only that run uses it; the default is untouched.

| Tool                     | Where the picker is                                                                                                                      |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
| **Organic Rank Tracker** | Select keywords, then **Bulk Actions > Check Keyword Metrics**                                                                           |
| **Saved Keywords**       | Select keywords, then **Bulk Actions > Check Keyword Metrics**                                                                           |
| **SERP Extractor**       | Select keywords, then **Bulk Actions > Check Keyword Metrics**                                                                           |
| **SERP Clustering**      | The **Check Metrics** dialog, and the run form while its **Check Metrics** switch is on                                                  |
| **Bulk Check Mentions**  | The **Check Metrics** button, and the run form while its **Check Metrics** switch is on                                                  |
| **Bulk Autocomplete**    | The **Check Metrics** button on the report                                                                                               |
| **Keyword Explorer**     | The **Keyword data source** dropdown on the search itself (see below), and the **Check Metrics** button on the autocomplete keywords tab |
| **Bulk Keyword Metrics** | The **Data source** dropdown on the Bulk Keyword Analysis card                                                                           |

**Google Search Console** works a little differently. Its source is saved per property rather than chosen per check, so two properties can use different sources. Set it under the property's **Keyword Metrics** card, in the **Keyword Metrics Source** field — the property's manual checks and its automatic checks both use it. Leave it alone to follow the global default.

{% content-ref url="/pages/caypbM1HCIZmcBDOjEO9" %}
[Keyword Metrics](/guide/google-search-console/keyword-metrics)
{% endcontent-ref %}

### The Keyword Explorer Search

The Keyword Explorer is different again, because its source decides the **search**, not just a metrics check. A **Keyword data source** dropdown sits under the search bar, and the same control appears in the header of the overview and suggestions pages so you can switch without starting over.

It offers **two** of the six sources rather than all of them:

| Source                       | What you get                                                                                               | About $ per search |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------- | ------------------ |
| **DataForSEO Labs database** | Suggestions with search volume, keyword difficulty, search intent and backlink data on every row.          | $0.04              |
| **Google Ads live**          | Fresh volumes, and keyword ideas the database has never heard of. Volume, trend, CPC and competition only. | $0.10              |

Only these two can **find** keywords. The other four price a list of keywords you already have; they cannot produce one, so the Keyword Explorer does not offer them.

{% hint style="info" %}
Pick **Google Ads live** when a keyword returns no search volume but you believe it has demand — that is usually the database not holding the keyword, rather than nobody searching for it.
{% endhint %}

#### What Changes in Google Ads Mode

Google Ads reports volume, monthly trend, CPC and competition, and nothing else. So in that mode:

* The **Keyword Difficulty**, **Intent**, **Backlinks** and **Results** columns are hidden from the suggestions table, rather than shown empty.
* The **seed keyword you searched for** still gets its difficulty, intent and backlinks — those come from the Labs database, and only that one keyword is looked up there. If the database has never heard of it, those cards say so and the volume is still there.
* Paging through the results and re-sorting them cost nothing. A Google Ads search is paid for once, however many keywords come back.

To get difficulty for particular suggestions, select them in the table and use **Bulk Actions**, which checks them properly.

### Read the Cost Line

Under the dropdown, one line tells you what the check will cost and who pays for it:

> About **$0.19** for 700 keywords · Billed to your DataForSEO account

It updates the moment you change the source, so you can compare two sources before committing to either. The payer is always one of **"Billed to your DataForSEO account"** or **"Billed to your SEO Utils credits"**.

Above it, a short note explains what the source actually does for the money — for Google Ads live, for example:

> Makes two requests per batch of 700 keywords: one to Google Ads (about $0.09) for volume, CPC and competition, one to DataForSEO Labs (about $0.10) for keyword difficulty and search intent. About $0.19 per 700 keywords, versus about $0.10 with the Labs database.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FVHINNg3OKHXx7J9sbh2c%2FXnapper-2026-09-16-12.55.47.png?alt=media&amp;token=cc13ff86-b287-4b36-813b-1b53a6be8895" alt="The Bulk Check Keyword Metrics dialog showing the source picker, the cost line with its payer, and the missing-data switch"><figcaption><p>The cost line names the price and the payer, and updates as you change source</p></figcaption></figure>

{% hint style="info" %}
Keyword difficulty and search intent always come from the DataForSEO Labs database, whichever source you choose — no other endpoint provides them. That is why three of the six sources make a second request per batch, and why their price includes it.
{% endhint %}

## A Dash Is Not a Zero

Two very different situations can sit in a Search Volume column, and telling them apart is the difference between discarding a keyword and discovering one.

* **A dash (—)** means the source was asked and had no figure for this keyword. It says nothing about demand. A different source may well have a number for it.
* **A `0`** means the source answered, and the answer was zero. Nobody is searching for it.

In CSV and Excel exports, a keyword with no figure gets an **empty cell**, not a `0`. A column full of zeros drags your averages down and turns unknown keywords into dead ones; an empty cell is ignored by the same formulas.

{% hint style="success" %}
A dash is an invitation to try a different source. It is the main reason to run **Google Ads live** or **DataForSEO Search Volume** over a list — both answer for keywords the monthly database has never seen.
{% endhint %}

## Where Every Number Came From

### The Label Under the Number

Every checked search volume carries a small coloured label beneath it, naming its source and the month the figure describes:

> ● **Labs · Aug 26**

The colour of the dot tells you the group at a glance — one colour for the Google Ads numbers, another for the split-per-variant sources, another for clickstream — so a report that mixes two scales is visible row by row.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FAfh9pKWokZCCtcOeFqQ7%2FXnapper-2026-09-16-12.58.54.png?alt=media&amp;token=13c1a5b9-c08c-4466-bc41-947f7389d0f6" alt=""><figcaption></figcaption></figure>

The label has four forms:

| What you see             | What it means                                                                      |
| ------------------------ | ---------------------------------------------------------------------------------- |
| **Labs · Aug 26**        | The source answered with a figure, and the figure describes that month.            |
| **No data · Google Ads** | The source was asked and had nothing for this keyword. The number above is a dash. |
| **Imported**             | The number is one you imported yourself, so no source is credited for it.          |
| *(no label)*             | The keyword has never been checked.                                                |

Hover the label for the full story, written out in full names:

> Volume, trend and CPC: Google Ads · Difficulty and intent: DataForSEO Labs · Checked 9 Sep 2026

{% hint style="info" %}
The label uses a short name to keep the Volume column narrow; the tooltip uses the full name. So the label may read **DFS Volume** where the tooltip, the exports and the dropdown all say **DataForSEO Search Volume**. They are the same source.
{% endhint %}

The Keyword Explorer's suggestions carry the same label, naming the source the **search** used. Every row there shows the same one, because they all came from a single search — unlike a keyword table, where each row was checked separately and the labels can differ. It is worth reading anyway: the autocomplete keywords sitting beside the suggestions are stored results from earlier checks, and can easily be on a different source from the search you just ran.

### In Exports

Exports built from your stored keyword metrics carry a **Volume Source** column immediately after **Search Volume**, written with the full source name — because a spreadsheet has no tooltip to hover, and the person who opens it may not have SEO Utils at all.

It carries the same four states: the source name, `No data · <source name>`, `Imported`, or an empty cell for a keyword that was never checked.

You will find it in the Organic Rank Tracker keyword positions and keyword fluctuation exports, Saved Keywords, both sheets of the SERP Clustering export, Bulk Check Mentions items, Bulk Autocomplete keywords, the Keyword Explorer autocomplete keywords export, and Bulk Keyword Metrics.

The Keyword Explorer **keyword suggestions** and **keyword overview** exports carry it too, with one difference: every row names the same source, because all of the figures came from the one search you ran rather than from separate checks.

{% hint style="info" %}
A few exports still have no source column: Ads Vision, Traffic organic keywords, Content Gap, and the Keyword Explorer Bing related keywords export. Their figures come from places none of the six sources describes, so there is no source to name.
{% endhint %}

The Organic Rank Tracker printable report shows the same thing as a muted second line under each number, so a PDF you send a client says where its figures came from.

### Filter and Sort By Source

Tables that show keyword metrics have a **Source** filter in their toolbar. It lists the six sources plus **Imported** and **No source**, so you can isolate exactly the rows you want — for example, every keyword in a report that is not on the source you have settled on.

The Volume column header menu also offers **Source Asc** and **Source Desc** for sorting.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FFKr1vdRzHM7X3qORhMhc%2FXnapper-2026-09-16-12.56.33.png?alt=media&amp;token=ec95212c-ffcf-47b2-9517-48b1c6dae3a1" alt="A keywords table with source labels under each volume and the Source filter open, listing the six sources plus Imported"><figcaption><p>The Source filter, over a table showing both a real figure and a "No data" dash</p></figcaption></figure>

## Stored Results, and Moving a Report to Another Source

A check writes results for the keywords in that check, and for nothing else. Each keyword holds one stored result — its figure, the source that produced it, and when it was checked — and that result stays put until you check that keyword again.

Two consequences worth knowing:

* **Changing the default source does not recalculate anything.** It decides what the *next* check asks for. Every figure already stored keeps the source it was checked with, and the source label under it keeps saying so.
* **A stored figure stays even when you disagree with it.** A `0` a source genuinely returned is a result like any other, and it persists until you re-check that keyword with the source you would rather trust.

Moving a report onto a different source is therefore something you do on purpose, not something that happens to you. SEO Utils never prompts you to do it — re-checking costs money, and when to spend it is your decision. When you decide to, [Keeping the Cost Down](#keeping-the-cost-down) explains how to pay only for the keywords that need it.

## Keeping the Cost Down

Checking metrics from a keyword table gives you a switch called **Only Check Keywords Missing Search Volume Data**, on by default. Leave it on and SEO Utils sends only the keywords that actually need a check:

* never checked
* checked with a different source than this check uses
* no figure from the source yet, and not retried this month
* a figure from an earlier month — DataForSEO publishes new figures monthly, so a keyword checked recently can be sent again once its data refreshes
* for Google Ads live and the clickstream sources only: a figure that arrived with another tool's results, so the difficulty and intent those sources fetch separately were never collected — and not retried this month

Turn it off to re-check every selected keyword, whatever state it is in.

The "not retried this month" wording is what stops you paying over and over for a keyword nobody has data for. It is tried again once per calendar month, not on every run.

{% hint style="success" %}
**This is how you move a report onto a different source.** Select the source, run a check with the switch on, and you pay only for the keywords that are not on that source yet. Run it again straight afterwards and nothing is fetched at all.
{% endhint %}

{% hint style="info" %}
SERP Clustering and Google Search Console have no such switch, and neither does the **Check Metrics** step inside a run form. They always check only the keywords with missing or out-of-date metrics, so re-running them costs nothing for keywords that are already current.
{% endhint %}

{% content-ref url="/pages/aMKQGvTre3Yi5VDxt9Pv" %}
[How to Save Costs when Using DataForSEO](/guide/how-to-save-costs-when-using-dataforseo)
{% endcontent-ref %}

<details>

<summary>How the estimated cost is calculated</summary>

The estimate on the cost line is built from DataForSEO's list prices and the number of keywords you are about to check.

1. Keywords are sent in batches of **700**, whichever source you pick.
2. Each batch costs a fixed amount per request, plus — for some sources — a small amount per keyword.
3. **Google Ads live**, **DataForSEO Search Volume** and **Clickstream (bulk)** make **two requests per batch**: one to the source for the volume and trend, and one to the DataForSEO Labs database for keyword difficulty and search intent. Both are included in the price shown.
4. **Labs, clickstream-normalized** and **Labs, Bing-normalized** make a single request, but asking for clickstream data doubles the per-request part of its price. That is why they cost a little more than the plain Labs database rather than twice as much.
5. The estimate counts every keyword you send, so the real cost can be lower.

</details>

<details>

<summary>Why clickstream volumes look so different from Google Ads volumes</summary>

Google Ads figures are built for advertisers. They are:

* **Rounded** to tidy numbers — 135,000 rather than 134,812.
* **Grouped**, so close variants of a keyword share one figure.

Clickstream figures are built from panels of observed browsing activity. They are:

* **Unrounded**, because they are a measured estimate rather than a reported bracket.
* **Per keyword**, with no grouping.

That is why the two scales do not line up, and why a clickstream figure of 113,360 can sit beside a Google Ads figure of 135,000 for the same keyword without either being wrong.

The practical rule: pick one scale per report and stay on it. The coloured source label under every volume makes a mixed report easy to spot.

</details>

## Related Guides

{% content-ref url="/pages/UGEP7HzFTFJgu8RC3A14" %}
[SEO Data Source](/guide/seo-data-source)
{% endcontent-ref %}

{% content-ref url="/pages/gwYT1OgDY4moZ5jr2WTJ" %}
[Rent DataForSEO API Key](/guide/rent-dataforseo-api-key)
{% endcontent-ref %}


# Semantic Keyword Clustering

Do you frequently question if two keywords can be targeted together on a page, or struggle with a large list of keywords that ChatGPT or other tools can't cluster due to token limits or cost?

### What Are the Differences Between SEO Utils' Keyword Clustering and Other Tools?

Here are 2 of the main differences:

#### Flexible to Switch the Embedding Model

Embedding models in Natural Language Processing (NLP) are designed to convert words, phrases, sentences, or entire documents into numerical vectors. These vectors represent the linguistic features of the text, allowing machines to process and analyze language in a meaningful way.

To do keyword clustering well, you need a good model that's already been trained. With AI growing fast, new models are coming out almost every day. You can visit [HuggingFace](https://huggingface.co/), a website, to get a free model and use it with SEO Utils to find one that's best for your type of business.

You can also take one of these models and train it more on words specific to your niche or industry. Then, use this customized model in SEO Utils for even better keyword clustering, which can improve your SEO results.

#### Unlimited Keywords for Clustering

With SEO Utils, you're not restricted in the number of keywords you can cluster. This is a big advantage over other tools that limit you to clustering between 5,000 to 10,000 keywords at a time. Since SEO Utils runs on your computer, it can handle as many keywords as you need, going way beyond these limits.

There's also no credit-based system, meaning you don’t have to pay extra no matter how many keywords you cluster. This can mean big savings, especially in large niches like Gym or Fitness where you might need to cluster a million keywords.

You might think, "*Can't I just cluster keywords with ChatGPT or the OpenAI API?*" While it's true you can cluster a few hundred keywords with these tools, they hit a limit when you try more than 10,000 keywords due to token limitations. Even with GPT-4 Turbo, which allows more tokens, the quality of clustering decreases with more keywords. It often loses context, doesn't follow instructions well, and misses keywords because you cannot control the `temperature` parameter in ChatGPT. You can do it with OpenAI API, but the cost is too high.

That's where a dedicated keyword clustering tool like SEO Utils makes a big difference.

### Semantic Clustering vs SERP Clustering

In my experience, SERP Clustering always gives you the best result of clustering. However, it comes with many technical issues like proxy rotation, time-consuming, server resources, etc.

Take [Larseo's SERP Clustering](http://larseo.app/), for example. It lets you cluster unlimited keywords, but clustering 1 million keywords takes a really long time and can cost about $2,900 (at 0.5 credit per keyword).

On the other hand, using the Semantic Clustering feature in SEO Utils is a different story. You don't have to pay extra, and you can get results as good as SERP Clustering. You can achieve this by fine-tuning your model to suit your specific needs.

{% hint style="info" %}
SEO Utils will support fine-tuning soon!
{% endhint %}

### How to Download Embedding Models and Use It on SEO Utils?

{% hint style="danger" %}
This documentation is for Semantic Clustering v1. For a better experience and improved performance, please refer to the [documentation for Version 2](#updated-nov-26-2024-semantic-keyword-clustering-v2).

Also, version 1 is not available for Linux.
{% endhint %}

{% embed url="<https://drive.google.com/file/d/1XckX_Or6LZDeDk7rLjWQY3v-QgrFV8Zc/view?usp=sharing>" fullWidth="true" %}
SEO Utils - How to use Semantic Keyword Clustering
{% endembed %}

1. First, you can visit this leaderboard: <https://huggingface.co/spaces/mteb/leaderboard>
2. Click on the "Clustering" tab, and then select the language that matches your keywords.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-89a2513ea990995156a05aefc348d6c572d89dd3%2FXnapper-2023-11-18-18.38.59.png?alt=media" alt=""><figcaption><p>List of top embedding models</p></figcaption></figure>

3. You will see the top embedding models based on their clustering task performance.
4. Select one model, for example, <https://huggingface.co/thenlper/gte-large>

{% hint style="warning" %}
Only select the mode that can be used with **Sentence Transformers**.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-31fb9fba32df4f7be17585af36eabe4bf68ead66%2FXnapper-2023-11-18-18.47.05.png?alt=media" alt=""><figcaption><p>Example a model can be used with Sentence Transformers.</p></figcaption></figure>

5. Click on the Clone repository to download a model with GIT `git-lfs`

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-97573ceec5579173adf91b31f4a9bddbc99e53dd%2FXnapper-2023-11-18-18.48.24.png?alt=media" alt=""><figcaption><p>Download a model</p></figcaption></figure>

```
# Make sure you have git-lfs installed (https://git-lfs.com)
git lfs install
git clone https://huggingface.co/thenlper/gte-large

# if you want to clone without large files – just their pointers
# prepend your git clone with the following env var:
GIT_LFS_SKIP_SMUDGE=1
```

{% hint style="info" %}
I will provide a [list of popular models on Google Drive](#popular-models) so that you can easily download them.
{% endhint %}

5. After downloading a model, open SEO Utils on your machine.
6. Click on the App dropdown, and go to the Settings page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-95dadf2d06463d59075fcc2c5723e462bcb1d1b5%2FXnapper-2023-11-18-14.33.14.png?alt=media" alt=""><figcaption></figcaption></figure>

7. Scroll down to the **Keyword Clustering** section and enter the path to the downloaded model on your machine. Then hit the Save button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-127b0f35cbcf09cf4d20d0e945af53a77e553302%2FXnapper-2023-11-18-19.09.33.png?alt=media" alt=""><figcaption></figcaption></figure>

8. That's all. Now, you can go to the Keyword Clustering page and kick off the process.

### Popular Models

<details>

<summary>English</summary>

**thenlper/gte-large**

* Download: <https://drive.google.com/file/d/1O4lm4hnqXoCDloqaw_exWiz9a-Vy0ZZK/view?usp=sharing>
* More info: <https://huggingface.co/thenlper/gte-large>

**BAAI/bge-large-en-v1.5**

* Download: <https://drive.google.com/file/d/1e3C2t3r1UrYgiAJf8GipmEUpXFK7zThz/view?usp=sharing>
* More info: <https://huggingface.co/BAAI/bge-large-en-v1.5>

**sentence-transformers/sentence-t5-xl**

* Download: <https://drive.google.com/file/d/15ijnzpEfbZG0dTiXq6Gyyesqj5DCDaEU/view?usp=sharing>
* More info: <https://huggingface.co/sentence-transformers/sentence-t5-xl>

</details>

<details>

<summary>Dutch</summary>

**NetherlandsForensicInstitute/robbert-2022-dutch-sentence-transformers**

* Download: <https://drive.google.com/file/d/1sbQ60drQeuqVTFYlbeuDp-Ds8Eoxts8D/view?usp=sharing>
* More info: <https://huggingface.co/NetherlandsForensicInstitute/robbert-2022-dutch-sentence-transformers>

**textgain/allnli-GroNLP-bert-base-dutch-cased**

* Download: <https://drive.google.com/file/d/1MKDmybaQihStFcV6N4hxaRz3TINZ5B_4/view?usp=sharing>
* More info: <https://huggingface.co/textgain/allnli-GroNLP-bert-base-dutch-cased>

</details>

<details>

<summary>Swedish</summary>

**KBLab/sentence-bert-swedish-cased**

* Download: <https://drive.google.com/file/d/1-eyV7KURYSd16pJeTWgMg9Sm_2DeEyDG/view>
* More info: <https://huggingface.co/KBLab/sentence-bert-swedish-cased>

</details>

<details>

<summary>Spanish</summary>

**hiiamsid/sentence\_similarity\_spanish\_es**

* Download: <https://drive.google.com/file/d/1a59Ld6LA_HCWwcEd7PQPogSCGr8_8yRU/view?usp=sharing>
* More info: <https://huggingface.co/hiiamsid/sentence_similarity_spanish_es>

</details>

<details>

<summary>Japanese</summary>

**colorfulscoop/sbert-base-ja**

* Download: <https://drive.google.com/file/d/1IMLy6YlVM1irIFwS3eNTrL9GZEdwfcJC/view?usp=sharing>
* More info: <https://huggingface.co/colorfulscoop/sbert-base-ja>

**sonoisa/sentence-bert-base-ja-mean-tokens**

* Download: <https://drive.google.com/file/d/1VmRKpCjnEpY-jY6o_6SYsqUPFajGhbmN/view?usp=sharing>
* More info: <https://huggingface.co/sonoisa/sentence-bert-base-ja-mean-tokens>

</details>

<details>

<summary>Filipino</summary>

**meedan/paraphrase-filipino-mpnet-base-v2**

* Download: <https://drive.google.com/file/d/1PToqNZKmc1GrrNxPIf2yDR9pC05kyfoD/view?usp=sharing>
* More info: <https://huggingface.co/meedan/paraphrase-filipino-mpnet-base-v2>

**danjohnvelasco/filipino-sentence-roberta-v1**

* Download: <https://drive.google.com/file/d/1GVzkYOCRuL2QHFOLCDKPRZlQqbGH5wqZ/view?usp=sharing>
* More info: <https://huggingface.co/danjohnvelasco/filipino-sentence-roberta-v1>

</details>

<details>

<summary>Chinese</summary>

**uer/sbert-base-chinese-nli**

* Download: <https://drive.google.com/file/d/16d_5UUxM8cUGy7TXCE0FJitg2NQNnpVc/view?usp=sharing>
* More info: <https://huggingface.co/uer/sbert-base-chinese-nli>

</details>

<details>

<summary>Thai</summary>

**mrp/simcse-model-m-bert-thai-cased**

* Download: <https://drive.google.com/file/d/16AukQ0XCBbWyBTTPl7mh6bTb7_chQtjz/view?usp=sharing>
* More info: <https://huggingface.co/mrp/simcse-model-m-bert-thai-cased>

</details>

<details>

<summary>Vietnamese</summary>

**keepitreal/vietnamese-sbert**

* Download: <https://drive.google.com/file/d/1xMx7x78Dgyv7HcFOYZJALDDEMX3p3an3/view?usp=sharing>
* More info: <https://huggingface.co/keepitreal/vietnamese-sbert>

</details>

<details>

<summary>Arabic</summary>

**medmediani/Arabic-KW-Mdel**

* Download: <https://drive.google.com/file/d/1dtvn7L4ItcCr3G5M0SOYIKyR4k8hkz1C/view?usp=sharing>
* More info: <https://huggingface.co/medmediani/Arabic-KW-Mdel>

</details>

<details>

<summary>Indonesia</summary>

**firqaaa/indo-sentence-bert-base**

* Download: <https://drive.google.com/file/d/1W6df3Ij-NPCgmdwgv9DyBO7XEe2-MBvM/view?usp=sharing>
* More info: <https://huggingface.co/firqaaa/indo-sentence-bert-base>

</details>

<details>

<summary>Universal</summary>

These models are pre-trained in multiple languages. If you cannot find a model that is pre-trained in a specific language, you can use these universal models.\
\
**sentence-transformers / all-mpnet-base-v2**

* Download: <https://drive.google.com/file/d/15ijnzpEfbZG0dTiXq6Gyyesqj5DCDaEU/view?usp=sharing>
* More info: <https://huggingface.co/sentence-transformers/all-mpnet-base-v2>

</details>

### Updated Nov 26, 2024: Semantic Keyword Clustering v2

With the release of [SEO Utils v1.23.2](https://help.seoutils.app/guide/pages/FYHJNu9cAi74Qc90ALo7#v1.23.2), I’ve introduced Semantic Keyword Clustering v2, which leverages a consistent [Docker environment](https://www.docker.com/) for running the clustering Python script. Here’s how this upgrade improves your experience:

* **Streamlined Model Selection:** No more manual downloads from HuggingFace—simply select your model from a dropdown menu, and SEO Utils takes care of the rest.
* **Faster Clustering with GPU Support:** Speed up keyword clustering with GPU support for Windows and Linux. While macOS only supports CPU, version 2 still delivers faster clustering compared to version 1!
* **Polished Output:** All formatting issues in the output file have been resolved.
* **Improved Reliability:** Minimize unexpected issues with a more stable setup.
* **Simplified Updates:** Updating the clustering script is now easier for me, as I no longer need to build separate executable scripts for each platform.

{% hint style="info" %}
**Why do I still keep version one?**\
\
Some users run SEO Utils on VPS, and not all VPS can support Docker. That’s why version 1 is still available as a backup option. If your setup supports Docker, I highly recommend using version 2!
{% endhint %}

#### How to Install Docker

* Visit <https://www.docker.com/>, download it, and install it as you normally would.
* Open Docker and follow the app’s instructions to start it as recommended.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-626c4f3850537714249a89edc4e32c0f0eef4d91%2FXnapper-2024-11-26-17.53.28.png?alt=media" alt="" width="375"><figcaption><p>Docker will be run in the background</p></figcaption></figure>

{% hint style="info" %}
You can close Docker if you’re not using Semantic Clustering version 2 anymore.
{% endhint %}

#### Switch to Version 2

**Step 1:** Go to Settings > Services from the left sidebar.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-544ca33839d7cde8c9e8df16d1e242d16cd3e7d1%2FXnapper-2024-11-26-17.56.11.png?alt=media" alt="" width="375"><figcaption><p>Settings > Services</p></figcaption></figure>

**Step 2:** Select **Version 2** from the dropdown and click the Save button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5d750d0bbdb1f818aa6d6d3c1939b3c112ed7059%2FXnapper-2024-11-26-19.28.49.png?alt=media" alt=""><figcaption><p>Select "Version 2" option</p></figcaption></figure>

**Step 3:** Open the Semantic Clustering tool as you normally would. You’ll notice a new field called “**Embedding Mode**l”. Simply choose a model from the dropdown based on your language to start clustering keywords.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-084b8710841532fd1d2052b3fcc30cfd8b46b9ba%2FXnapper-2024-11-26-19.30.12.png?alt=media" alt=""><figcaption><p>Select an ebmedding model from dropdown.</p></figcaption></figure>

No more complicated setups or manual downloads! SEO Utils will automatically download the model and **cache it** for future use, so you won’t need to wait for it to re-download every time.


# SERP Clustering

### How Does the SERP Clustering Tool Work?

SEO Utils will cluster your keywords by scraping the search engine results page (SERP). If two keywords share more than four pages in search engine results (**similar results** on SERP), it will group them into a cluster.

Of course, you can adjust the **similar results number** from 3 to 7; the larger the number, the more relevant keywords are in a cluster.

The advantage of this method is that it leverages Google's ability to discern users' search intent. If Google shows many similar pages for two keywords, it indicates that Google recognizes these keywords as having the same search intent.

The only drawback is that it can be time-consuming for large keyword lists, as scraping SERPs is a detailed and cumbersome task.

### How to Cluster Keywords Using SERP Clustering Tool

There are two main processes when the SERP Clustering tool runs:

1. Scraping SERP data for all keywords.
2. Running the [clustering algorithm](#clustering-algorithm) after scrapping all SERP data.

To get started, head to the SERP Clustering in the left sidebar. Then, click the Cluster Keywords button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-93dcdad10e67de7efccfbde36d175de9198349af%2FXnapper-2024-05-17-21.23.45.png?alt=media" alt=""><figcaption><p>Access the SERP Clustering tool in the left sidebar</p></figcaption></figure>

A modal will be opened; it should look like this. We will go over each setting one by one.

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-06d84bc2dfc26700e73f16bbe618f8c9a68461bc%2Fserp-clustering-modal.png?alt=media" alt=""><figcaption><p>SERP Clustering modal. (1) Location. (2) Language</p></figcaption></figure></div>

#### Keyword Files

SERP Clustering tool that lets you upload multiple files. It automatically combines the keywords and removes any duplicates. No need to mess with Excel anymore. This will save you some time.

After uploading files, you need to map the columns

* **Keyword column:** This column is required.
* **Search Volume column:** This is optional. You can map your external search volume, so you don't have to re-check the search volume for your keywords.

To map columns, click on the Column dropdown.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-80e3bdd14d2916c29cc7c0f283d27b1fdfb253ab%2FXnapper-2024-05-17-21.35.41.png?alt=media" alt=""><figcaption><p>Map the keyword column</p></figcaption></figure>

{% hint style="info" %}
SEO Utils also automap columns if your files have a guessable column name.
{% endhint %}

{% hint style="success" %}
**Updated:** Since version 1.6.0, you can also map CPC and search intents columns.
{% endhint %}

#### Location and Language

Pick the **Location** that you want to target and the **Language** of your keyword lists. A country targets the whole country. To scrape the SERP for a more precise place, type a city, region or postal code and pick it from the list. SEO Utils uses the same selection for checking keyword search volume in most cases.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6c94151f0348095d37d7df41a91084b833067d21%2Fserp-clustering-location-search.png?alt=media" alt=""><figcaption><p>(1) Type a city, region, postal code or country. (2) Pick the place from the list</p></figcaption></figure>

{% hint style="info" %}
While **Check Metrics** is on, the lists only offer the locations and languages your keyword metrics source supports.
{% endhint %}

#### Desktop Devices

SEO Utils will check search results for desktop devices. If you want to check for mobile devices, please disable this setting.

#### Check Keyword Metrics

SEO Utils will use DataForSEO to check keyword metrics. This helps determine the **primary keyword** for a cluster, so it's recommended to enable this setting.

However, if your uploaded files already have search volume data and you mapped the Volume or CPC column, you can turn off this setting to save money.

{% hint style="info" %} <mark style="color:blue;">**Tip**</mark>: If your uploaded files don't have enough search volume data for all keywords, you can turn on the "Check Search Volume" field. SEO Utils only check the search volume for **keywords that are missing data**.
{% endhint %}

#### Cluster Strategy

When setting the primary keyword for clusters, SEO Utils will use the keyword that has the most search volume in a cluster, however, some users have mentioned that setting the primary keyword for a cluster based on Cost Per Click (CPC) provides better results when your keywords are transactional or commercial. You can now select the Cluster Strategy to use CPC instead.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5f6567f31af78099f8d0af7b40a997789531feda%2FXnapper-2024-06-20-15.58.20.png?alt=media" alt=""><figcaption><p>Using CPC to set the primary keyword for clusters.</p></figcaption></figure>

#### Clustering Algorithm

Since [version 1.30.0](https://help.seoutils.app/changelog#v1.30.0), SEO Utils offers three different clustering algorithms to suit different needs:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-59ff9382ca49cc2a3aa345f02da9299a5c3c1c28%2FCleanShot%202025-05-28%20at%2012.01.49%402x.png?alt=media" alt=""><figcaption><p>Select the clustering algorithm that best fits your needs</p></figcaption></figure>

**Default Algorithm**

* Groups keywords if they share X URLs with the primary keyword (highest search volume/CPC)
* Creates broader topic clusters
* Best for content hubs and category planning
* Fastest processing speed

**Strict Algorithm**

* Groups keywords only if ALL keywords in the cluster share X URLs with each other
* Creates very tight, highly relevant clusters
* Best for precise content targeting
* **Limitation**: May result in many single-keyword clusters due to "first-mover advantage"

**Balanced Strict Algorithm**

* Solves the Strict algorithm's limitation by using progressive thresholds
* Small clusters (2-5 keywords): requires 100% match (like Strict)
* Medium clusters (6-10): requires 80% match
* Large clusters (11+): requires 60% match
* **Why it's needed**: Prevents clusters from becoming "too strict" as they grow larger
* Best balance between quality and natural cluster growth

{% hint style="info" %} <mark style="color:blue;">**Why Balanced Strict was created**</mark>: The original Strict algorithm has a "first-mover advantage" problem where early keywords easily join clusters, but later keywords struggle to match ALL members in larger clusters. This often results in many single-keyword clusters. Balanced Strict solves this by relaxing requirements as clusters grow, allowing natural expansion while maintaining quality.
{% endhint %}

{% hint style="info" %} <mark style="color:blue;">**How to Choose**</mark>:

* **Default**: When you need broad topic grouping or have 100,000+ keywords
* **Strict**: When you need very precise clusters for competitive niches
* **Balanced Strict**: When you want quality clusters that can still grow naturally (recommended for most users)
  {% endhint %}

**Processing Time Comparison**

The more advanced algorithms take longer to process due to additional quality checks:

| Dataset Size     | Default Algorithm | Strict/Balanced Strict | Time Difference |
| ---------------- | ----------------- | ---------------------- | --------------- |
| 1,000 keywords   | 1-2 seconds       | 3-5 seconds            | 2-3x slower     |
| 10,000 keywords  | 5-10 seconds      | 15-30 seconds          | 2-3x slower     |
| 50,000 keywords  | 1-2 minutes       | 5-10 minutes           | 3-5x slower     |
| 100,000 keywords | 5-10 minutes      | 20-40 minutes          | 4-5x slower     |

{% hint style="warning" %} <mark style="color:orange;">**Performance Note**</mark>: Strict and Balanced Strict algorithms require more processing time but produce higher quality clusters. For very large datasets (100,000+ keywords), consider using the Default algorithm or breaking your keywords into smaller batches.
{% endhint %}

{% hint style="success" %}
SEO Utils' clustering algorithm is designed to handle large-scale keyword datasets efficiently. You can cluster between 50,000 to 200,000 keywords at once—a capability not many tools on the market offer. Most other tools typically allow clustering of only 5,000 to 10,000 keywords at a time.
{% endhint %}

#### Similar Results on SERPs

The value range is from **3 to 7**. For example, if you set this field to 4, SEO Utils will group 2 keywords into a cluster if they have at least **4 common URLs on SERPs**. The larger the number, the more relevant keywords are in a cluster.

{% hint style="info" %} <mark style="color:blue;">**Tip**</mark>: The recommended value is 4, but you are free to test a different value by using the ["Re-cluster keywords" button](#re-cluster-keywords).
{% endhint %}

#### Use Saved SERP Data For X Days

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d208a3b081a9949f3e57a2861ee33b7b2603a718%2FXnapper-2024-05-17-22.01.13.png?alt=media" alt=""><figcaption></figcaption></figure>

Enter the number of days you wish to use previously saved SERP data. By setting this duration, you can speed up the clustering process and save money as SEO Utils will reuse existing data without the need to re-scrape.

Choose a number that best balances freshness of data with processing speed.

Set '0' to always scrape fresh SERP data.

{% hint style="info" %} <mark style="color:blue;">**Tip**</mark>: This field is a great method for testing **Similar Results on SERPs** value since you don't have to re-scrape SERP data for all keywords.
{% endhint %}

#### Reuse SERPs for Word-Order Twins

Some keywords use the same words in a different order, for example **"laravel horizon"** and **"horizon laravel"**. We call them **word-order twins**. Google usually shows almost the same results for both, so SEO Utils can scrape the SERP once and reuse it for the twin.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FxHeQumoBbRMkq3z7w8wm%2FXnapper-2026-09-18-16.36.23.png?alt=media&amp;token=25d8f96f-da5f-41eb-ae7b-2b6b8fb5bc30" alt="The Reuse SERPs for word-order twins switch in the Cluster Keywords modal" width="563"><figcaption><p>Turn on "Reuse SERPs for word-order twins" to scrape one SERP per twin group</p></figcaption></figure>

When this setting is on:

* In each group of twins, SEO Utils scrapes the SERP for **one keyword only**. The other keywords in the group use that SERP for clustering.
* If a twin already has recent saved SERP data (see **Use Saved SERP Data For X Days**), it keeps its own data. SEO Utils reuses a SERP only instead of scraping a new one.
* The setting works with every scraping method. With the SERP API it saves money; with your own IP or proxies it sends fewer requests.

The setting is **off by default**. Turn it on for each run where you want to use it.

**Should you turn it on?**

|               |                                                                                                                                                         |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Savings**   | In our tests, 6–16% of keywords were twins. That saves roughly **$0.60–$1.70 per 10,000 keywords** at normal priority, and twice that at high priority. |
| **Accuracy**  | 136 of 137 tested twins really did share their Google results.                                                                                          |
| **Trade-off** | On a 1,503-keyword list, about **18 in 100 keywords** ended up in a slightly different cluster than when every SERP was scraped.                        |

{% hint style="warning" %} <mark style="color:orange;">**Word order can change the meaning**</mark>: This is rare, but it happens. For example, "keychron numpad" shows videos and DIY posts, while "numpad keychron" shows the brand's shop pages. If exact clusters matter more than the savings, keep this setting off.
{% endhint %}

{% hint style="info" %}
A reused SERP is used for clustering only. SEO Utils never shows it as the twin's own Google results. See [Reused SERPs in Your Report](#reused-serps-in-your-report).
{% endhint %}

#### Scrape SERP With

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-99a76fe75585b8b0fb0692c21a85d73afeb33b9b%2FXnapper-2024-05-17-22.03.02.png?alt=media" alt=""><figcaption><p>Select a method to scrape SERP</p></figcaption></figure>

There are 3 options for now:

* **My IP:** SEO Utils use your IP to scrape SERP data. This is not recommended if you have over 100 keywords.
* **Proxies:** Use proxies to scrape SERP data. See how to set up a proxy [here](/guide/how-to-use-proxies).
* **SERP API: DataForSEO:** Use SERP API from DataForSEO to scrape SERP data.

We will focus on Proxies & SERP API, so you can determine which method is best fit for you.

**SERP API Method**

DataForSEO provides a reliable API to scrape SERP data with 3 modes:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d6e6a4aa0effc3cbf528b89f3f88e2397b57d460%2FXnapper-2024-05-17-22.10.22.png?alt=media" alt=""><figcaption><p>3 modes</p></figcaption></figure>

Since the Live mode is expensive, so SEO Utils doesn't support it. After selecting the SERP API method, you will able to select the mode in the **Priority** field.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cf4afaa5a4acb399e0804627d4a00492e1f9bf87%2FXnapper-2024-05-17-22.11.57.png?alt=media" alt=""><figcaption><p>Select a mode</p></figcaption></figure>

I recommend using the **normal execution priority (Standard Queue)** option. I have tested to cluster 2,000 keywords, and it only took about 12 minutes to finish all processes. [See the video here](#video-running-serp-clustering-on-2-000-keywords-with-serp-api).

It only costs **$0.6 to scrape SERP & cluster 1,000 keywords**. This rate is much cheaper when compared to other tools on the market, which usually cost **$7-$12 for 1,000 keywords**.

Yes, you read that right! It's 11 times cheaper:v:.

{% hint style="info" %}
In v1.21.0, I added a cost estimation tool for the SERP API, allowing you to see the actual cost after deducting keywords that use saved SERP data. Please [click here](#cost-estimation-tool-for-serp-api-method) to learn more about it.
{% endhint %}

{% hint style="warning" %}
**Important:**

To use the SERP API, you must have your own DataForSEO account. [Renting API key services](/guide/rent-dataforseo-api-key) isn't viable because DataForSEO restricts certain endpoints that I utilized to implement the Queue mode. If multiple users rely on a rented API key from my account, it will slow down the process for everyone. For the quickest results, using your own DataForSEO account is the best approach.
{% endhint %}

**Proxies Method**

If you need to cluster 1 million keywords per month, using the SERP API Method would indeed be costly, amounting to $600.

This is where the Proxies method becomes valuable. By using your own proxies, you can significantly reduce the costs associated with such large-scale keyword clustering.

You can pay about **$80-$100** per month for a rotating residential proxy and you can cluster **millions of keywords**.

However, this method has more fields to set up.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-723be5926171b2b048e8d413de228026e10a1b9e%2FXnapper-2024-05-17-22.50.14.png?alt=media" alt=""><figcaption><p>3 important fields for Proxies method</p></figcaption></figure>

**Workers**

This is the number of concurrent requests SEO Utils will scrape SERP. You can enter from 1-50. If you have a good proxy provider, you can set it to 50 (my setting), so SEO Utils can send 50 requests in one second to scrape SERP data. This will increase the clustering process a lot.

If you are unsure about your proxy quality, go with 5-10 workers first.

**Request Delay**

Enter the number of seconds you wish to have between each request to scrape SERP data for keywords. The more delay time you set, the slower the process will be, but it will help you avoid being blocked by Google.

Set '0' to scrape SERP data without any delay.

{% hint style="success" %}
For example, if you set **Workers** to 10 and **Request Delay** to 1 second. SEO Utils will send 10 requests and then sleep for one second before sending another 10 requests.
{% endhint %}

**Back-off Time**

Enter the number of seconds you wish to wait before retrying the failed scraping request. SEO Utils retries the request up to 3 times before skipping a keyword. The more back-off time you set, the slower the process will be, but it will help you avoid being blocked by Google.

{% hint style="success" %}
For example, if you set **Workers** to 10, **Request Delay** to 1 second, and **Back-off Time** to 2 seconds. SEO Utils will send 10 requests and then sleep for one second before sending another 10 requests.\
\
However, while processing, if one request in 10 requests is failed, it will sleep for **2 seconds (back-off time)** before retrying the failed request.
{% endhint %}

{% hint style="info" %}
SEO Utils will retry a maximum of **three times** before skipping scraping a keyword. That keyword will end up with no SERP data.
{% endhint %}

{% hint style="info" %}
If you set the **Back-off Time** to '0', SEO Utils will use the default back-off time:

* 1 second for the 1st attempt
* 2 seconds for the 2nd attempt.
* 3 seconds for the 3rd attempt.
  {% endhint %}

Feel free to experiment with different settings for your proxies and usage. When testing these settings, as long as you don't encounter a "Too Many Requests" error message, it should indicate that your setup is functioning correctly.

\
Since SEO Utils automatically retries each request up to three times, you might see a message like:

`Attempt 1 failed to scrape SERP for keyword 'keyword': failed to visit URL: Too Many Requests.`

Don't worry if you see this message. SEO Utils will try two more times, so everything is still fine unless you see a failure message on the third attempt.

| SERP API                                                | Proxies                                                |
| ------------------------------------------------------- | ------------------------------------------------------ |
| Use when clustering **thousands** of keywords per month | Use when clustering **millions** of keywords per month |
| Less configuration and testing                          | More configuration and testing                         |

### Re-cluster Keywords

After clustering keywords, you can visit the report and re-cluster keywords.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-87d3c06f68c85f46e3c4f6c6a86f7f386a4e242e%2FXnapper-2024-05-17-23.20.37.png?alt=media" alt=""><figcaption><p>Click the Re-cluster Keywords button to re-cluster all keywords in the report</p></figcaption></figure>

You might need to re-cluster keywords in the following situations:

* When testing the **Similar Results field on SERPs** field.
* If you're adding more keywords to a report and need to cluster them with existing ones.
* To monitor the clusters before and after Google Core Updates to observe any impact.
* If some keywords are missing SERP data because some SERP scraping requests were failed.

SEO Utils will show this message if some keywords in your report are missing SERP data, so you know to re-run the clustering process.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fd9b960abadcb843384f44a9edabdef7ae1202f0%2FXnapper-2024-05-17-23.28.20.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
When re-clustering keywords, make sure you use the "[**Use Saved SERP Data For X Days**](#use-saved-serp-data-for-x-days)" field. This ensures that SEO Utils won't re-scrape SERP data, saving time and resources.
{% endhint %}

#### Consistent Results

Re-clustering the same keywords with the same SERP data and the same settings always gives the same clusters. This is true for all three [clustering algorithms](#clustering-algorithm).

When two keywords have the same search volume (or CPC) and the same number of words, the keyword that comes **first in your keyword list** becomes the primary keyword of the cluster.

#### Distribute Keywords into Existing Clusters (Available since v1.16.0)

When re-clustering keywords, you'll be able to distribute new and non-clustered keywords into existing clusters, rather than rebuilding all clusters from scratch.

This is particularly useful if you've already used clusters to create articles on your website and you just want to add new keywords to existing articles (clusters).

A **"New" badge** will highlight these newly added keywords, and a **"Run #" label** will indicate which clustering run they were added in.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d25093551ef46742a80feaeab2e644d55c676ae4%2F448666243_7699027523499742_768845294393561290_n.jpg?alt=media" alt=""><figcaption><p>Enable the setting to distribute keywords into existing clusters</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a022a013fa2bae135fdea290f0edfea0aa0b1114%2F448646536_7699027720166389_2702349076745059710_n.jpg?alt=media" alt=""><figcaption><p>The "New" badge will help you determine the latest keywords just added to a cluster.</p></figcaption></figure>

### Reused SERPs in Your Report

When a run uses [Reuse SERPs for Word-Order Twins](#reuse-serps-for-word-order-twins), the report tells you clearly which keywords did not get their own SERP.

#### Report Summary

A line above the table shows how many keywords reused a twin's SERP, and so how many fewer SERPs were scraped.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-486a4dd84596dedfa3ce169175452e79e79b6332%2Fserp-clustering-reused-serp-summary.png?alt=media" alt="The reused SERP summary line above the clusters table"><figcaption><p>The summary line shows how many keywords reused a twin's SERP</p></figcaption></figure>

#### The "Reused SERP" Badge

Each keyword that reused a SERP has a **Reused SERP** badge next to its name. The badge also shows on the cluster row when a reused keyword is the primary keyword of the cluster.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-97c5299a01f9094a583a4d6ef00ad1c4c2e94ef3%2Fserp-clustering-reused-serp-badges.png?alt=media" alt="Keywords with the Reused SERP badge in the clusters table"><figcaption><p>Reused keywords have a badge, and their SERP-based columns show a dash</p></figcaption></figure>

Hover over the badge to see which keyword's results were used.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f6054e75010024856f2fc90ea174021f3262e82b%2Fserp-clustering-reused-serp-tooltip.png?alt=media" alt="Tooltip of the Reused SERP badge"><figcaption><p>The badge tooltip names the twin whose results were used</p></figcaption></figure>

For a reused keyword, these columns show a dash (**—**), because the keyword has no SERP of its own:

* Intersections
* Avg Rank
* Highest Rank
* Ranked URLs

Reused keywords are also left out of the cluster's **Avg Rank**, **Ranked Kws** and **Ranked URLs** totals, so one SERP is never counted twice.

#### Viewing a Reused Keyword

Click a reused keyword to expand it. Instead of a SERP table, you see a **"No SERP bought for this keyword"** message that names its twin.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-59a699adc93d8695cffc6673c3dc7593ac183782%2Fserp-clustering-no-serp-bought-panel.png?alt=media" alt="The No SERP bought for this keyword message"><figcaption><p>A reused keyword shows a message instead of a SERP table</p></figcaption></figure>

Click **Show "\<twin keyword>"** to go to the twin's own row. SEO Utils expands it, scrolls to it and highlights it for a moment, so you can see the SERP that was used for clustering.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1ce85c58d536953d5695bab894e2bcaee3116a7e%2Fserp-clustering-show-source-row.png?alt=media" alt="The twin&#x27;s row expanded with its SERP"><figcaption><p>The twin's row opens with its own Google results</p></figcaption></figure>

{% hint style="info" %}
If the twin is not in the list you are viewing (for example, it is on another page, hidden by your search, or in another cluster), SEO Utils opens a panel with that keyword only. Click **Show all keywords** in the panel to see the rest of its cluster.
{% endhint %}

{% hint style="success" %}
To get a keyword's own SERP again, re-cluster the report with **Reuse SERPs for word-order twins** turned off. SEO Utils then scrapes a SERP for every former twin (unless it has recent saved data) and removes the badges.
{% endhint %}

### Analyzing SERP

After clustering your keywords, you can analyze the SERPs of the clustered keywords to see how your competitors are performing. This analysis can show you their monthly traffic, the keywords they rank for, and how many backlinks they have.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-efd836eabbf0ab7e219e4e1994974a03f4fb4f61%2FXnapper-2024-05-18-12.34.29.png?alt=media" alt=""><figcaption><p>Click the vertical three dots icon to start analyzing SERP</p></figcaption></figure>

You can choose the type of metric and specify the number of URLs on the SERP for each keyword you want to run the analysis for.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-729bca15ce07540fb7784f60943031f998710165%2FXnapper-2024-05-18-12.38.31.png?alt=media" alt=""><figcaption><p>Analyze SERP for selected keywords</p></figcaption></figure>

After analysis, you can click on a keyword to view the SERP data with all metrics including traffic, backlinks, referring domains, spam score, keywords, etc for that keyword.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e4577ba59fb61b64f984b0fa18d3bc668cbc01cf%2FXnapper-2024-05-18-12.44.50.png?alt=media" alt=""><figcaption><p>SERP data for the keyword "vodka cocktails," including backlinks and traffic data</p></figcaption></figure>

The analyzed data is also included in the exported file under the second tab labeled "SERP Data."

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ab1352bc9e0ca8208b7fce4fe013fd27827ef585%2FXnapper-2024-05-18-12.54.08.png?alt=media" alt=""><figcaption><p>All backlinks &#x26; traffic data are included in the SERP data sheet</p></figcaption></figure>

{% hint style="info" %}
Keywords that [reused a twin's SERP](#reused-serps-in-your-report) are skipped by the analysis and are not counted in its cost, because they have no SERP of their own. Their twin is analyzed as usual.
{% endhint %}

In the exported file, reused keywords work the same way:

* The **Keyword Clusters** and **Non-Clustered Keywords** sheets have a **SERP Source** column. It is empty for a keyword with its own SERP, and shows the twin's keyword for a reused keyword.
* For a reused keyword, the intersection and rank cells are empty.
* The **SERP Data** sheet has no rows for reused keywords.

### Ranking Data

You can add a target domain to a SERP Clustering report. This will show you the ranking data of that domain across all clusters, helping you identify which clusters you are ranking well in and which ones need improvement. This feature allows you to prioritize your efforts to boost your rankings effectively.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c2aa888d480ff7ae83d971dee3a611312136e59e%2FXnapper-2024-06-21-16.48.38.png?alt=media" alt=""><figcaption><p>Ranking data will be shown in the table after adding a target domain</p></figcaption></figure>

When viewing the SERP of a keyword, the target domain will be marked in green color.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-827bba9675bbfe6c1aa516048455951e1188819b%2FXnapper-2024-06-21-16.49.10.png?alt=media" alt=""><figcaption><p>Target domain in SERP table</p></figcaption></figure>

{% hint style="success" %}
**Tip:** You can also change the target domain to a competitor's domain to see how well they are performing across different clusters. This can help you identify their strengths and areas where you might have an advantage.
{% endhint %}

SEO Utils also provides some metric cards to show you the cluster's key ranking data at a glance:

* View and filter the number of ranking clusters.
* View and filter the number of clusters without rankings.
* See and filter the rank distribution across clusters.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9fee993b06494fbf1f26de946783f38409b109dd%2FCleanShot%202024-06-23%20at%2022.35.45%402x.png?alt=media" alt=""><figcaption><p>Metric cards and filters</p></figcaption></figure>

You can watch the video below to see the "Ranking Data" feature in action.

{% embed url="<https://drive.google.com/file/d/1se5GGf6U5Fzrhuv3GlZBAzPCrSBMlG25/view?usp=drive_link>" fullWidth="true" %}

### Cost Estimation Tool for SERP API Method

When using the SERP API to scrape SERP data, you can click the “Estimate Cost” button to view the actual cost. SEO Utils will read all keywords in your uploaded file, remove duplicates, and exclude keywords that already have saved SERP data, providing you with an accurate final cost.

In the screenshot below, I uploaded over **18,000 keywords** and used SERP data from the past 7 days. The cost came to just **$0.0390**, saving me **$11.2470**! SEO Utils only sent **65 keywords** to the SERP API for new data, as most of the keywords already had recent SERP data within 7 days.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fc3800a5525db616bd73013b49b0287268edced0%2F464919090_8563919223677230_7461303937806986891_n.jpg?alt=media" alt=""><figcaption><p>Cost estimation tool for SERP API.</p></figcaption></figure>

The estimate also counts the **word-order twins** in your list, even when [Reuse SERPs for Word-Order Twins](#reuse-serps-for-word-order-twins) is off. Use it to decide whether to turn the setting on for this list:

* **Setting off:** the estimate shows how many twins your list has and how much turning the setting on would save.
* **Setting on:** the saving is already taken out of the **Total Cost**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0b84077f094b2b57b88e96b59d1ae6c0cb599811%2Fserp-clustering-word-order-twins-estimate.png?alt=media" alt="Cost estimate with the Word-Order Twins line"><figcaption><p>The estimate shows the twins in this list and what reusing their SERPs saves</p></figcaption></figure>

{% hint style="info" %}
The cost estimate is available in the desktop app. In a remote browser, the report shows the real number of reused SERPs after the run.
{% endhint %}

### Video Running SERP Clustering on 2,000 keywords with SERP API

{% embed url="<https://drive.google.com/file/d/1UJr9PD-t2XNjRmaKL1VP840XajQoStV7/view?usp=sharing>" %}
Demo on clustering 2000 keywords
{% endembed %}


# SERP Extractor

SERP Extractor lets you extract Google search results for your keywords and analyze the competitor URLs found in those results. Use it to evaluate competitor strength, find keyword opportunities with weak competition, and export the data for further analysis.

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FnOnyxYljvJtPZ5ECAkdE%2FXnapper-2026-02-16-18.01.00.png?alt=media&amp;token=015f0ad1-0a6c-4562-9844-fbce8ee8089a" alt=""><figcaption><p>SERP Extractor</p></figcaption></figure></div>

## How It Works

The SERP Extractor follows a three-step workflow:

1. **Extract SERPs** — Scrape Google search results for each keyword to collect the top-ranking URLs.
2. **Analyze SERP URLs** — Run bulk analysis on the extracted URLs to get backlink and traffic metrics (Page Rank, Domain Rank, Backlinks, Referring Domains, Organic Traffic, Organic Keywords).
3. **Filter & Explore** — Use the SERP Item filter to find keywords where competitors match specific metric criteria, then drill into the expanded view to see individual SERP items with highlighted matches.

## Creating a Report

{% stepper %}
{% step %}
**Navigate to SERP Extractor**

Go to **SERP Extractor** in the sidebar and click the **"Extract SERPs"** button.
{% endstep %}

{% step %}
**Enter Keywords**

Type or paste your keywords into the text area, one keyword per line.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6ba11955ade824171be0743528fcdb49d5f6a0e5%2Fserp-extractor-form.png?alt=media" alt=""><figcaption><p>Enter keywords to extract SERP data. (1) Keywords. (2) Location. (3) Language</p></figcaption></figure>
{% endstep %}

{% step %}
**Configure Settings**

* **Location** — Pick a country, or a city, region or postal code inside it, for localized SERPs.
* **Language** — Select the language of the search results.
* **Desktop Device** — Toggle on for desktop results, toggle off for mobile results.
* **SERP Depth** — Choose how many top results to extract per keyword (10 to 100).
  {% endstep %}

{% step %}
**Select Scraping Method**

Choose how SEO Utils will scrape Google search results:

| Method              | Best For                                | Notes                                                                             |
| ------------------- | --------------------------------------- | --------------------------------------------------------------------------------- |
| Own IP              | Small batches (under 100 keywords)      | Request delay must be at least 3 seconds                                          |
| Proxies             | Large-scale extraction (thousands+)     | Requires proxy configuration. See [How to Use Proxies](/guide/how-to-use-proxies) |
| DataForSEO SERP API | Reliable extraction without proxy setup | Requires a DataForSEO account                                                     |

When using **Proxies**, you can configure **Workers** (concurrent requests), **Request Delay**, and **Back-off Time** — similar to the [SERP Clustering](/guide/serp-clustering) tool.

When using **DataForSEO SERP API**, you can choose between normal and high execution priority, and view a cost estimate before starting.
{% endstep %}

{% step %}
**Start Extraction**

Click **"Extract SERPs"** to begin. You will be redirected to the report detail page where you can monitor the progress.
{% endstep %}
{% endstepper %}

## Report Detail Page

After extraction completes, the report detail page shows a table of all keywords. If keyword metrics have been checked, you will also see Search Volume, Trend, Keyword Difficulty, and CPC columns.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FggFE60TMgEQRt15a4i96%2FXnapper-2026-02-16-18.33.26.png?alt=media&amp;token=0158027e-ba8e-4ab7-ba78-58cd10ab4ea8" alt=""><figcaption><p>SERP Extractor report detail showing keywords with their metrics</p></figcaption></figure>

## Analyzing SERP URLs

After extracting SERPs, you can analyze the URLs found in search results to get backlink and traffic data for each competitor page.

{% stepper %}
{% step %}
**Analyze All SERPs**

Click the **"Analyze All SERPs"** button in the top-right corner of the report detail page. Select which analysis types to run (backlinks, traffic, or both) and click **"Analyze SERP"**.

You can click **"Estimate Cost"** to see the DataForSEO cost before starting.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FhXkqPg3rc4w16DMkSsO2%2FXnapper-2026-02-16-18.34.14.png?alt=media&amp;token=6242cbdb-bfad-4301-a243-5d4ddd92048f" alt=""><figcaption><p>Analyze all SERPs with cost estimation</p></figcaption></figure>
{% endstep %}

{% step %}
**Analyze Selected Keywords**

Alternatively, select specific keywords using the checkboxes, then use **Bulk Actions > Analyze SERP** to analyze only the selected keywords.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FLn2FxvS9WnhnfjcpcpWt%2FXnapper-2026-02-16-18.35.19.png?alt=media&amp;token=d3ece1dd-687e-4e90-89a3-d6f6c47169a5" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Analysis runs in the background. You'll see a notification when it completes.
{% endhint %}

## Checking Keyword Metrics

To get search volume, keyword difficulty, and CPC data for your keywords:

1. Select the keywords you want to check using the checkboxes.
2. Click **Bulk Actions > Check Keyword Metrics**.
3. Review the cost and click **"Execute"**.

{% hint style="info" %}
DataForSEO won't charge you for keywords that don't have search volume data, so the actual cost will be lower than the estimation.
{% endhint %}

## Viewing SERP Items

Click the **eye icon** on any keyword row to expand it and see the individual SERP items (competitor pages) for that keyword.

The expanded view shows the following metrics for each URL:

| Column    | Description                                                                                 |
| --------- | ------------------------------------------------------------------------------------------- |
| Pos       | Position in Google search results                                                           |
| Page      | The URL and page title                                                                      |
| PR        | Page Rank (0–1000) — the authority score of the specific page based on its backlink profile |
| DR        | Domain Rank (0–1000) — the authority score of the root domain                               |
| Backlinks | Total number of backlinks pointing to the page                                              |
| RD        | Referring Domains — number of unique domains linking to the page                            |
| Traffic   | Estimated monthly organic traffic to the page                                               |
| Keywords  | Number of organic keywords the page ranks for                                               |

{% hint style="info" %}
PR and DR scores range from 0 to 1000, where 0 means no backlinks and 1000 indicates extensive quality backlinks. Higher scores require exponentially more effort to achieve.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FDGCjcoUjcTsD37Ck1lMS%2FXnapper-2026-02-16-18.36.17.png?alt=media&amp;token=994538d9-4430-4930-8ee5-4b796a95d127" alt=""><figcaption><p>Expanded SERP items showing competitor metrics with tooltips on column headers</p></figcaption></figure>

## Filtering by SERP Item Metrics

The **SERP Item** filter is one of the most powerful features. It lets you filter keywords based on the metrics of their competitor pages — helping you find opportunities where competition is weak.

### How It Works

Click the **"SERP Item"** filter button in the toolbar to open the filter popover.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FIh6g4gAr8UKtxlGtdhOm%2FXnapper-2026-02-16-18.37.06.png?alt=media&amp;token=812a221a-c03f-437c-9e63-c9030d4b60c1" alt=""><figcaption><p>SERP Item metric filter with range inputs for each metric</p></figcaption></figure>

### Filter Settings

| Setting      | Description                                                                                           |
| ------------ | ----------------------------------------------------------------------------------------------------- |
| Condition    | **AND** — a SERP item must match all metric ranges. **OR** — matching any single metric range counts. |
| Min. results | The minimum number of SERP items that must match for the keyword to appear.                           |
| Page Rank    | Filter by page authority score (0–1000).                                                              |
| Domain Rank  | Filter by domain authority score (0–1000).                                                            |
| Backlinks    | Filter by number of backlinks.                                                                        |
| Ref. Domains | Filter by number of referring domains.                                                                |
| Traffic      | Filter by estimated monthly organic traffic.                                                          |
| Keywords     | Filter by number of organic keywords.                                                                 |

Each metric has a **From** and **To** field. Leave a field empty to skip that bound.

### Example Use Cases

**Find keywords with weak competitors:**

* Set **Domain Rank** to 0–200, **Backlinks** to 0–100, **Condition** to AND, **Min. results** to 3
* This shows keywords where at least 3 of the top results have low page authority and few backlinks

**Find keywords with high-value SERPs:**

* Set **Traffic** from 10000, **Condition** to OR, **Min. results** to 1
* This shows keywords where at least one competitor gets significant organic traffic

### Highlighting

When a SERP Item filter is active and you expand a keyword row, matching SERP items are highlighted:

* **Row highlight** — Rows where all active conditions match (with AND) or any condition matches (with OR) get a colored background.
* **Cell highlight** — Individual metric cells that match their respective filter range are shown in green.

This makes it easy to quickly spot which competitors meet your criteria.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FQ2O2x4GozHFmoWCcc2sf%2FXnapper-2026-02-16-18.37.58.png?alt=media&amp;token=3aae6d29-5a22-4610-a550-b0d52d3f540f" alt=""><figcaption><p>Expanded SERP items with filter highlighting showing matched metrics in green</p></figcaption></figure>

## Exporting to CSV

Click the **"Export CSV"** button in the top-right corner to download the report data. The export includes all keywords with their metrics and SERP item data.

## Best Practices

* **Start with extraction, then analyze** — Extract SERPs first, review the results, then run the analysis only on the keywords you care about to save costs.
* **Use the SERP Item filter to find opportunities** — Look for keywords where multiple competitors have low Page Rank and few backlinks — these are easier to rank for.
* **Combine keyword and SERP filters** — Use Volume and KD filters alongside SERP Item filters to find high-volume, low-competition keywords.
* **Use OR condition for broad discovery** — Switch to OR when you want to cast a wider net and find keywords where any single metric condition is met.
* **Check Min. results carefully** — Setting a higher minimum (e.g., 3–5) ensures the weak competition pattern is consistent across multiple results, not just one outlier.


# Rent DataForSEO API Key

Your own [DataForSEO](/guide/seo-data-source) account is pay as you go and works with every tool in SEO Utils, Backlinks included. Its smallest top-up is $50.

To start with less, rent a DataForSEO API key from SEO Utils instead. You purchase credits of $10, $20 or $50 and pay as you go, and the credits never expire.

### How to Purchase Credits?

**Step 1:** Visit <https://app.seoutils.app/register> and register an account. You will need to verify your email address.

**Step 2:** After logging in, click the user dropdown in the top-right corner and select "Purchase Credits."

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-278381c8101cd442fe3ff4ac4dfa00a1f36d8ddc%2FXnapper-2023-11-30-16.43.22.png?alt=media" alt="" width="375"><figcaption><p>Click Purchase Credits</p></figcaption></figure>

**Step 3:** Select the credit package that you would like to purchase and click the "Purchase" button. You will be redirected to the checkout page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ea73c6df969b6cc7cbe5405b723520b83d3e75ec%2FXnapper-2023-11-30-16.50.57.png?alt=media" alt=""><figcaption><p>Select a credit package</p></figcaption></figure>

### How to Access Backlinks API on SEO Utils by Using Credits?

To access the Backlinks API, you will need an SEO Utils API Key.

**Step 1:** Visit <https://app.seoutils.app/> and click the user dropdown in the top-right corner and select "API Tokens".

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-bed1442f82dfb2098a868fc7f90251855b5670b1%2FXnapper-2023-11-30-16.56.27.png?alt=media" alt="" width="375"><figcaption><p>Select "API Tokens" menu item.</p></figcaption></figure>

**Step 2:** Enter the "Token Name" and ensure that you check the "Backlink" permission so that the Token can have access to the Backlinks API.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1fcb93102844aebe82002b936fa6e0d9892b7d75%2FXnapper-2023-11-30-16.57.27.png?alt=media" alt=""><figcaption><p>Enter Token Name</p></figcaption></figure>

**Step 3:** Click on the "Create" button, and the system will display the API Token. Copy the token before clicking the "Close" button, as the token will never be displayed again.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-16fa3113d3ae896af866b99b1de50401ecfd08b2%2FXnapper-2023-11-30-16.59.24.png?alt=media" alt=""><figcaption><p>Copy the API Token</p></figcaption></figure>

**Step 4:** Open the SEO Utils app on your machine (Ensure that it is version 1.1.0 or newer). Go to the Settings page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ce200d09cb1187ad47fcadf238ea7d8981ddec73%2FXnapper-2023-11-30-17.26.48.png?alt=media" alt="" width="365"><figcaption><p>Go to Settings page in SEO Utils app</p></figcaption></figure>

**Step 5:** Go to **Settings > Services** and scroll to the **Renting DataForSEO API Key** card.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-de65aa22f69b6f594f70e448fa8da0f0f3ec8760%2Frent-dataforseo-api-key-settings-card.png?alt=media" alt="The Renting DataForSEO API Key card in Settings > Services"><figcaption><p>Paste the key (1), turn on Backlink API (2) and click Save (3)</p></figcaption></figure>

Paste the API token you copied in Step 3 into **API Key** (1). Under **Use On**, turn on the **Backlink API** switch (2), so the app uses the token for the Backlinks API instead of your DataForSEO account. Click **Save** (3).

Backlinks requests are now paid from your credits.

{% hint style="info" %}
You can use the API token on multiple devices, or you can create multiple API tokens for multiple devices.
{% endhint %}

{% hint style="warning" %}
You cannot use the sandbox mode when using an API token to access the Backlinks API.
{% endhint %}

You can also delete an API Token by clicking the "Delet&#x65;**"** button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6dcd22cadd97671728048ec17e423663b91bc1c8%2FXnapper-2023-11-30-17.10.11.png?alt=media" alt=""><figcaption><p>Delete API Token</p></figcaption></figure>

### View Credit Transactions

You can view all credit transactions by clicking the Transactions menu from the user dropdown menu.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-be1ea04408556d26e833be974ebf3ff26b523a7e%2FXnapper-2023-11-30-17.15.36.png?alt=media" alt="" width="360"><figcaption><p>View Transactions</p></figcaption></figure>

Use the "Type" filter to show the In/Out transactions. You can even search the transaction by "Note" or "Transaction ID".

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-54745731193239c35d3548daca0d880d83c857db%2FXnapper-2023-11-30-17.24.34.png?alt=media" alt=""><figcaption><p>View All Credit Transactions</p></figcaption></figure>

{% hint style="success" %}
You can also [share the data](/guide/data-sharing-with-s3) with your teammates so that they can access the same information without incurring any extra fees.
{% endhint %}

### Why Do I Have to Pay $10.89 to Get $10?

While building this feature, I always wanted to keep the price as low as possible, so you will have seamless access to the Backlinks API. However, I have to pay the credit fee, server cost, API maintenance fee, etc., so you have to pay a little extra. Here is the breakdown:

* Stripe charges 2.9% + 30¢ per successful card charge.
* Stripe charges 0.5% per transaction when registered to collect taxes.
* SEO Utils charges 2.5% per transaction to maintain API and server.

### Updated Dec 27, 2023: Added API Endpoints for Traffic & Keyword Tools

Before December 27, 2023, SEO Utils only supported the Backlinks API for the renting service. However, now you can use credits from SEO Utils to pull traffic and keyword data.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3a68b2560c170af7e6290559f2336939576d8387%2FXnapper-2023-12-27-16.13.18.png?alt=media" alt=""><figcaption><p>Settings page</p></figcaption></figure>

{% hint style="info" %}
Make sure your **old API Key** has "**traffic-keyword"** permission on <https://app.seoutils.app/> (the new API Key will be included by default).

<img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fcb3cfc817c9040b250c0858636e79bfc571ed0c%2FXnapper-2023-12-27-16.10.40.png?alt=media" alt="" data-size="original">
{% endhint %}

### Use Your Credits for AI Visibility

You can also run [AI Visibility](/guide/ai-visibility) on your credits instead of your own DataForSEO login. The prices are the same as DataForSEO's, taken from your credits, and every paid action shows its price first.

**Step 1:** Visit <https://app.seoutils.app/api-tokens>, enter a "Token name" and keep the **ai-visibility** permission checked (every permission is checked by default). Create the token and copy it.

**Step 2:** In the SEO Utils app, go to **Settings > Services** and open the **Renting DataForSEO API Key** card. Paste the key, turn on the **AI Visibility API** switch and click "Save".

{% hint style="warning" %}
A key created before AI Visibility does not include it. To add it, open [API Tokens](https://app.seoutils.app/api-tokens), click **Edit permissions** on the key, tick **ai-visibility** and click "Save". Creating a new key also works, and new keys have **ai-visibility** ticked by default.
{% endhint %}

* While the **AI Visibility API** switch is on, AI Visibility uses the rental key instead of your own DataForSEO login, even if you also saved one. Turn it off to go back to your login.
* Without a DataForSEO login, the credentials card on the AI Visibility start page shows **…or rent a key from SEO Utils**. It opens this card.
* A rental key sends at most 2 requests at a time, so a large load can take a little longer.

You may see these messages from the rental service:

* **Your SEO Utils rental balance is too low.** Purchase more credits, as in [How to Purchase Credits?](#how-to-purchase-credits)
* **Your SEO Utils rental key does not include AI Visibility.** Add the **ai-visibility** permission to this key on [app.seoutils.app](https://app.seoutils.app/api-tokens) > API Tokens > **Edit permissions**, or create a new key.
* **The SEO Utils rental service is busy right now. Try again in a moment.** Nothing is charged.
* **DataForSEO did not answer the SEO Utils rental service in time.** Nothing is charged. Try again.


# S3 / R2 Connections

An S3 / R2 connection holds the address and keys of your cloud storage: Amazon S3, Cloudflare R2, or any S3-compatible service. You enter the keys once, and every feature that uses a bucket picks the connection from a list.

Four features use connections:

| Feature                                                                    | What it does with the bucket                          | Access the key needs   |
| -------------------------------------------------------------------------- | ----------------------------------------------------- | ---------------------- |
| [S3 Cache for DataForSEO Data](/guide/data-sharing-with-s3)                | Shares DataForSEO results with your team              | Read, write and delete |
| [Log File Analysis](/guide/log-file-analysis#getting-logs-from-cloudflare) | Reads Cloudflare Logpush files                        | Read only              |
| [Saved SERP Pages Storage](/guide/saved-serp-pages-storage)                | Keeps your saved Google results pages                 | Read, write and delete |
| [Backups & Restore](/guide/backups-and-restore#where-backups-can-go)       | Keeps your database backups, by hand or on a schedule | Read, write and delete |

Each feature chooses its own bucket, so one connection can serve all four.

## Adding a Connection

{% stepper %}
{% step %}

#### Open the connections card

Go to **Settings > Services > Storage > S3 / R2 Connections** and click **Add connection**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1222490000b853b8f5e05aac87049f230a533abd%2Fs3-r2-connections-card.png?alt=media" alt="S3 / R2 Connections card with one connection and the features that use it"><figcaption><p>The connections card lists each connection and what uses it</p></figcaption></figure>
{% endstep %}

{% step %}

#### Enter the storage and keys

* **Name** — a name you will recognize in the lists, for example `Agency R2`.
* **Storage** — choose your provider, then fill in its fields:

{% tabs %}
{% tab title="Cloudflare R2" %}

* **Cloudflare account ID** — paste the account ID, or the bucket's **S3 API** URL from its settings page.
* **Jurisdiction** — **EU** for a bucket created in the EU jurisdiction, otherwise **Default**. Pasting the bucket's S3 API URL sets it for you.
  {% endtab %}

{% tab title="Amazon S3" %}

* **Region** — the bucket's AWS Region, for example `us-east-1`.
  {% endtab %}

{% tab title="Other S3-compatible storage" %}

* **Endpoint** — the provider's S3 endpoint, for example `https://s3.example.com`.

* **Region** — the bucket's region. Leave it empty if the provider has none.
  {% endtab %}
  {% endtabs %}

* **Access key ID** and **Secret access key** — from your provider. See the table above for the access each feature needs.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-58023279a288d69c4f67a599e1ce743f8521ce8b%2Fs3-r2-connections-new-dialog.png?alt=media" alt="New S3 / R2 connection dialog with Storage, Cloudflare account ID, keys and Test connection"><figcaption><p>A new Cloudflare R2 connection</p></figcaption></figure>
{% endstep %}

{% step %}

#### Test and save

Enter a bucket name under **Test with bucket** and click **Test connection**. SEO Utils checks that the keys can reach that bucket.

Click **Add connection** to save.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The secret access key is stored in your system keychain (Keychain on macOS, Credential Manager on Windows, Secret Service on Linux), never in SEO Utils' settings file.
{% endhint %}

{% hint style="warning" %}
Log sources, saved SERP pages and backups need an `https://` endpoint. An `http://` endpoint, such as a MinIO server on your local network, works for the S3 cache only.
{% endhint %}

## Editing and Deleting a Connection

* **Edit** (pencil icon) — change the name, storage or keys. Leave **Secret access key** empty to keep the saved secret. Every feature that uses the connection picks up the change.
* **Delete** (trash icon) — removes the connection and its secret. A connection that a feature still uses cannot be deleted; choose another connection in that feature first.

{% hint style="warning" %}
If your saved SERP pages are in a bucket, SEO Utils refuses an edit that would point their connection at a different account or bucket, because the pages would no longer be reachable. You can still rename it. To move the pages somewhere else, [bring them back to this computer](/guide/saved-serp-pages-storage#bringing-pages-back) first.
{% endhint %}

## Keys Saved Before Connections

If you entered S3 keys in the **S3 Cache Settings** card or in an S3 / R2 log source before this update, SEO Utils turns them into connections automatically the next time it starts. They are named after their feature, for example **DataForSEO cache** or **R2 my-logs-bucket**, and everything keeps working as before.


# S3 Cache for DataForSEO Data

SEO Utils can cache DataForSEO API responses using S3-compatible storage, so your teammates can access the same data without paying any extra fees.

For example, if you check the backlink data of site A, SEO Utils will upload that data to your S3 bucket. When your teammate also checks the backlink data for that site, it will pull data from S3 instead of requesting the DataForSEO API.

{% hint style="info" %}
S3 cache supports **AWS S3** (Recommended), **Cloudflare R2**, **DigitalOcean Spaces**, **MinIO**, and any other S3-compatible storage service.
{% endhint %}

{% hint style="success" %}
**S3 is the third of three cache tiers.** Each search first checks your in-memory cache, then your local SQLite database, then S3, and only then calls the DataForSEO API. See [Recent Searches & Cache](/guide/recent-searches-and-cache) for details on the local tiers and the search history list.
{% endhint %}

## Setting Up S3 Cache

{% stepper %}
{% step %}
**Create a Bucket**

{% tabs %}
{% tab title="AWS S3 (Recommended)" %}

1. Log in to [AWS Console](https://console.aws.amazon.com/)
2. Go to **S3** → **Create bucket** (search "S3" in the header search bar if you can't find it)
3. Enter a bucket name (e.g., `my-seo-cache`)
4. Select your preferred region (e.g., `us-east-1`)
5. Keep **Block all public access** enabled
6. Click **Create bucket**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f0ce09ed0d723d9eab67cac0569ac2f6cb46d8bb%2Fs3-create-bucket.png?alt=media" alt=""><figcaption><p>Create a S3 bucket on AWS</p></figcaption></figure>
{% endtab %}

{% tab title="Cloudflare R2" %}

1. Go to your Cloudflare dashboard
2. Navigate to **R2** and click **Create Bucket**
3. Enter a bucket name and select a location
   {% endtab %}

{% tab title="DigitalOcean Spaces" %}

1. Go to your DigitalOcean dashboard
2. Navigate to **Spaces** and click **Create Space**
3. Select a region and enter a name
   {% endtab %}

{% tab title="MinIO" %}
Run `mc mb myminio/my-seo-cache` from the MinIO client.
{% endtab %}
{% endtabs %}

{% hint style="warning" %}
The bucket should be **private**. SEO Utils authenticates using Access Key and Secret Key — no public access is needed.
{% endhint %}
{% endstep %}

{% step %}
**Get Your Access Credentials**

You'll need an **Access Key ID** and **Secret Access Key** with read/write permissions to the bucket.

{% tabs %}
{% tab title="AWS S3 (Recommended)" %}
**Create an IAM Policy**

1. Go to **IAM** in the AWS Console (search "IAM" in the header search bar)

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-17007f6723f915632250a9721178fd166ae5ac14%2Fs3-iam-search.png?alt=media" alt=""><figcaption><p>Search for IAM in the AWS Console</p></figcaption></figure>

2. Go to **Policies** → **Create policy**
3. Select **S3** as the service

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f95f524529a2aff241b6b34aaaad54245ca813b6%2Fs3-iam-select-service.png?alt=media" alt=""><figcaption><p>Select S3 as the service</p></figcaption></figure>

4. Click the **JSON** tab and paste:

```json
{
   "Version": "2012-10-17",
   "Statement": [
      {
         "Effect": "Allow",
         "Action": [
            "s3:GetObject",
            "s3:PutObject",
            "s3:DeleteObject",
            "s3:ListBucket"
         ],
         "Resource": [
            "arn:aws:s3:::YOUR-BUCKET-NAME",
            "arn:aws:s3:::YOUR-BUCKET-NAME/*"
         ]
      }
   ]
}
```

5. Replace `YOUR-BUCKET-NAME` with your actual bucket name
6. Click **Next** → Name it `SEOUtilsS3Access` → **Create policy**

**Create an IAM User**

1. Go to **IAM** → **Users** → **Create user**
2. Enter a name: `seo-utils-s3` → Click **Next**
3. Select **Attach policies directly**
4. Search for `SEOUtilsS3Access` and check the box
5. Click **Next** → **Create user**
6. Open the user → **Security credentials** tab
7. Click **Create access key** → Select **Third-party service**
8. Click **Create access key** → **Save both keys**

{% hint style="warning" %}
**Save your keys now.** The Secret Access Key is only shown once. Store it in a password manager.
{% endhint %}
{% endtab %}

{% tab title="Cloudflare R2" %}

1. Go to **R2 > Manage R2 API Tokens** in your Cloudflare dashboard
2. Click **Create API Token**
3. Select **Object Read & Write** permission
4. Copy the **Access Key ID** and **Secret Access Key**
   {% endtab %}

{% tab title="DigitalOcean Spaces" %}

1. Go to **API > Spaces Keys** in your DigitalOcean dashboard
2. Click **Generate New Key**
3. Copy the **Key** and **Secret**
   {% endtab %}
   {% endtabs %}
   {% endstep %}

{% step %}
**Configure S3 Cache in SEO Utils**

Open SEO Utils and go to **Settings > Services > Storage**.

1. In **S3 / R2 Connections**, click **Add connection** and enter the keys from the previous step. Choose **Amazon S3** with the bucket's region, **Cloudflare R2** with your account ID, or **Other S3-compatible storage** with the endpoint (DigitalOcean Spaces, MinIO). See [S3 / R2 Connections](/guide/s3-r2-connections) for each field.
2. In **S3 Cache Settings**, choose that **Connection** and enter the **Bucket Name**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2d489b27da06e0b87b6da10e6fdbdb43a972dd22%2Fs3-cache-connection.png?alt=media" alt="S3 Cache Settings with a connection, bucket name, Test Connection and Save"><figcaption><p>The S3 cache uses a connection and its own bucket</p></figcaption></figure>

{% hint style="info" %}
Keys you entered in S3 Cache Settings before connections existed move to a connection named **DataForSEO cache** automatically, and the cache keeps working.
{% endhint %}
{% endstep %}

{% step %}
**Test the Connection**

Click the **"Test Connection"** button to verify that SEO Utils can connect to your bucket. You should see a success message.

{% hint style="info" %}
You don't need to save the settings before testing. The Test Connection button uses the values currently entered in the form.
{% endhint %}
{% endstep %}

{% step %}
**Save Settings**

Click the **"Save"** button to save your S3 cache settings.

From now on, every time you pull data from DataForSEO, it will automatically upload the data to your S3 bucket.
{% endstep %}
{% endstepper %}

## Sharing with Your Team

To share cached data with your teammates:

1. Share the **Access Key ID**, **Secret Access Key**, **Bucket Name**, and the region or endpoint with your team
2. Each teammate adds an [S3 / R2 connection](/guide/s3-r2-connections) with the same keys, then chooses it and the same bucket in **S3 Cache Settings**

Once configured, everyone on the team will read from and write to the same S3 bucket, avoiding duplicate DataForSEO API requests.

## Automatic Cache Cleanup

SEO Utils automatically deletes cached data older than **7 days**, so you always get fresh data. If you want fresh data sooner, you can:

* Click the **"Purge Cache"** button in S3 Cache Settings to delete all cached data from your S3 bucket immediately
* Or delete specific files directly from your S3 bucket
* Click **Refresh** on any DataForSEO result page — this invalidates that specific search's cache on all three tiers (memory, local DB, **and S3**) so teammates also see fresh data on their next visit

{% hint style="info" %}
**Purge Cache vs. Clear Cache & History.** The **"Purge Cache"** button here only affects the shared S3 bucket. The **"Clear Cache & History"** button in the **DataForSEO Local Cache** settings card only affects your local machine. They're intentionally separate so one user can't wipe the team's shared cache by accident. See [Recent Searches & Cache](/guide/recent-searches-and-cache) for the local version.
{% endhint %}

{% hint style="warning" %}
If you delete the S3 bucket or revoke the access credentials, click **Turn off the cache** in S3 Cache Settings to avoid errors.
{% endhint %}

## Migrating from Google Drive Cache

If you were previously using Google Drive to cache DataForSEO data, simply configure your S3 cache settings as described above. SEO Utils will start using S3 for all new cache operations. Your old Google Drive cache data will no longer be used.

{% hint style="info" %}
The Google Drive settings in SEO Utils are now only used for [exporting content outlines to Google Docs](/guide/content-struct#setup-google-drive-api-integration). If you don't use that feature, you can remove your Google Drive settings.
{% endhint %}


# Saved SERP Pages Storage

Every SERP check keeps a copy of the Google results page: the **HTML** tab of a SERP and the ranked-page captures of the Organic Rank Tracker. Over months of rank tracking these copies can take tens of gigabytes. You can move them to an external drive, another folder, or an S3 / R2 bucket, and keep using them as before.

{% hint style="success" %}
**Saved pages are now compressed.** New pages are saved compressed, and pages saved before are compressed once in the background, even if you never move them. On a sample of saved pages this made them about 73% smaller.
{% endhint %}

## Before You Start

Choose where the pages will go:

* **Folder or external drive** — any folder outside the SEO Utils data folder, for example on a USB or network drive. Keep the drive connected while SEO Utils runs.
* **S3 / R2 bucket** — a bucket and an [S3 / R2 connection](/guide/s3-r2-connections) whose key can read, write and delete in that bucket. The connection needs an `https://` endpoint.

Your rankings, keywords and SERP results stay in the database on this computer. Only the saved page copies move.

## Moving Your Saved Pages

{% stepper %}
{% step %}

#### Open the Saved SERP Pages card

Go to **Settings > Services > Storage > Saved SERP Pages**. The card shows how many saved pages are on this computer and how much space they take.
{% endstep %}

{% step %}

#### Choose where to keep them

{% tabs %}
{% tab title="Folder or external drive" %}

1. Select **Folder or external drive**.
2. Click **Choose folder…** and pick a folder on the drive.
3. Check the line below: it shows how much will move and how much space the drive has free.

SEO Utils creates a folder named **SEO Utils saved pages** followed by a short code inside the folder you chose, and keeps the pages there.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d2019829071c44a8fd42ef0ce9eda200f208067f%2Fsaved-serp-pages-choose-target.png?alt=media" alt="Saved SERP Pages card with Folder or external drive selected, a folder chosen, and Start moving"><figcaption><p>Moving the saved pages to an external drive</p></figcaption></figure>
{% endtab %}

{% tab title="S3 / R2 bucket" %}

1. Select **S3 / R2 bucket**.
2. **Connection** — choose a connection, or click **New connection** to add one.
3. **Bucket** — the bucket that will hold the pages.
4. **Folder in the bucket (optional)** — the folder inside the bucket, `seo-utils/` by default.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-bb487087493be3fc52f4809c90f031fdaf3abb50%2Fsaved-serp-pages-bucket-target.png?alt=media" alt="Saved SERP Pages card with S3 / R2 bucket selected, a connection, bucket and folder"><figcaption><p>Moving the saved pages to a Cloudflare R2 bucket</p></figcaption></figure>
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

#### Start moving

Click **Start moving**. SEO Utils first checks that it can write to the folder or bucket, then moves the pages in the background. The card shows the progress, and you can keep working meanwhile.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d66570f33e48a5aadd1b97596a253eb5af07f8ca%2Fsaved-serp-pages-moving.png?alt=media" alt="Saved SERP Pages card showing Connected and Moving: 46,970 done"><figcaption><p>Pages moving to the bucket</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## After the Move

* **New SERP checks** save their page on this computer first. SEO Utils moves it within a few minutes.
* **Opening a saved page** (the HTML tab, a ranked-page capture or its comparison) reads it from wherever it is. From a bucket it can take a moment longer.
* **Retry now** checks the folder or bucket again and moves any waiting pages straight away.

## When the Drive or Bucket Is Not Available

If the drive is unplugged or the bucket cannot be reached, the card shows **Not available** and the reason.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-612763739b4251e409c4ed0c3c864b6d3cf2457d%2Fsaved-serp-pages-not-available.png?alt=media" alt="Saved SERP Pages card showing Not available with Locate folder and Retry now"><figcaption><p>The drive that holds the pages is not connected</p></figcaption></figure>

SERP checks keep working while it is away: new pages wait on this computer and move once it is back. Pages already moved cannot be opened until then.

To fix it:

* **The drive is unplugged** — connect it and click **Retry now**.
* **The drive has a new name or drive letter** — click **Locate folder…** and pick the **SEO Utils saved pages** folder, or the folder that holds it.
* **The connection is missing**, for example after restoring a database backup — choose the connection, bucket and folder again and click **Use this connection**.

## Bringing Pages Back

To keep every page on this computer again:

1. Click **Bring everything back to this computer** and confirm.
2. SEO Utils checks that this computer has enough free space, then copies the pages back and removes them from the folder or bucket.
3. When the last page is back, the card shows **Kept on this computer**.

You can click **Stop bringing back** at any time. The pages already back move out again.

While [automatic backups](/guide/backups-and-restore#automatic-backups) are on, the confirmation also warns you that a backup restored on another computer will not have the pages once they are back here.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a70cef8ad33917d39addb7f97ffc68164305fbd2%2Fbackups-recall-warning.png?alt=media" alt="Bring every saved page back confirmation with the automatic backups warning"><figcaption><p>The confirmation warns that a backup restored on another computer will not have the pages</p></figcaption></figure>

{% hint style="info" %}
To switch to a different drive or bucket, bring the pages back first, then start a new move.
{% endhint %}

## Backups and Moving to a New Computer

Only a backup **to a file** can include the saved pages that are on this computer. Backups to a bucket or a folder, including automatic backups, never do. To protect your pages next to your backups, keep them in the backup bucket too. See [Saved Pages and Backups](/guide/backups-and-restore#saved-pages-and-backups).

{% hint style="warning" %}
**Moving SEO Utils to another computer?** Either keep the pages in the backup bucket and copy them during the restore, or bring them back to this computer before you make a backup to a file with the saved pages included. See [Restore on Another Computer](/guide/backups-and-restore#restore-on-another-computer).
{% endhint %}

## Automatic Cleanup

Once a day, SEO Utils removes saved pages that no SERP record uses any more, for example after you delete a report. It only removes pages that are at least 7 days old, and it waits 14 days after you restore a database backup, so you can still restore a different backup and keep its pages. It also keeps every page that a backup you still keep needs.

## FAQ

<details>

<summary>Can my team share one bucket for saved pages?</summary>

* Yes. Add a connection with the same keys on each computer and choose the same bucket.
* Each computer keeps its pages in its own folder inside the bucket, so computers never read or remove each other's pages.
* To share DataForSEO results with your team, use the [S3 Cache](/guide/data-sharing-with-s3) instead.

</details>

<details>

<summary>Does moving the pages change my rankings or reports?</summary>

No. Rankings, keywords, SERP results and reports stay in the database on this computer. Only the copies of the Google results pages move.

</details>


# Recent Searches & Cache

SEO Utils remembers every DataForSEO search you run across Keyword Explorer, Traffic Analytics, Backlink Analytics, Content Gap, and Backlink Gap. You can re-open past searches in one click, see how fresh the data is, and refresh it when you need the latest numbers — all without paying extra API credits for data you've already pulled.

{% hint style="success" %}
Every search is stored locally in your SQLite database, so your history survives app restarts, machine reboots, and navigation away to other tools. No data leaves your machine unless you've also configured [S3 Cache for DataForSEO Data](/guide/data-sharing-with-s3).
{% endhint %}

## Recent Searches List

Under every DataForSEO tool's search bar, you'll see a **"Recent searches"** card listing your past searches for that tool.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FFdbglupHGqf6WFd03ob5%2FXnapper-2026-04-23-10.47.12.png?alt=media&amp;token=17a040b4-d242-4018-a368-98ef46abee4a" alt="" width="563"><figcaption><p>Recent searches list below the Backlink Analytics search bar</p></figcaption></figure>

Each row shows:

* **Target**: the domain, URL, or keyword you searched
* **Context badges**: for Content Gap and Backlink Gap, the number of competitors; for Keyword Explorer, the search engine (Google or Bing)
* **Last accessed**: when you last opened this search

Click any row to re-open it instantly — no API call is made if the data is still cached.

### Managing History

| Action                              | How to do it                                                 |
| ----------------------------------- | ------------------------------------------------------------ |
| **Open a past search**              | Click the row                                                |
| **Delete one entry**                | Hover over the row and click the X that appears on the right |
| **Clear all entries for this tool** | Click the ⋯ menu in the card header → **Clear all**          |
| **Show more entries**               | Click "Show N more" at the bottom (up to 25 rows)            |

{% hint style="info" %}
Only your **100 most recent searches per tool** are kept. Older entries are automatically pruned. Deleting a history row does **not** delete the underlying cached data — re-typing the same search will still hit the cache.
{% endhint %}

### Keyword Explorer Entries Name Their Source

A Keyword Explorer search that used **Google Ads live** and the same search on the **DataForSEO Labs database** are two different searches, with different figures and different prices. They get **one entry each**, and each entry carries a badge naming its source, so two rows for the same keyword are easy to tell apart.

Re-opening an entry uses the source it was run with, not your current default. Entries from before this feature existed re-open on the Labs database, which is what they were run with.

{% content-ref url="/pages/9ZN2hqv3w3x3TElty4OK" %}
[Keyword Metrics Data Source](/guide/keyword-metrics-data-source)
{% endcontent-ref %}

## Freshness Widget

While viewing any DataForSEO result page, a small widget anchors to the bottom-right corner showing when the data was last fetched and a Refresh button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FHL3H2SrFLNQsgFpvGD4I%2FXnapper-2026-04-23-10.48.36.png?alt=media&amp;token=ff636157-d93a-4045-b6a9-976caed85d2f" alt=""><figcaption><p>Freshness widget showing "Data updated 14 hours ago" and a Refresh button</p></figcaption></figure>

### Color Coding

The widget changes color to signal how stale the data is:

| Age         | Color                        | Meaning                              |
| ----------- | ---------------------------- | ------------------------------------ |
| Under 1 day | Green                        | Fresh — recently fetched             |
| 1–14 days   | Default (muted)              | Normal working range                 |
| 14–30 days  | Amber                        | Stale — consider refreshing          |
| 30+ days    | Red (with "Stale · " prefix) | Very stale — data is likely outdated |

### Collapsing the Widget

Click the chevron (›) to collapse the widget into a small clock icon. Click the icon to expand it again. Your preference is remembered across sessions and tools.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FsMXXFuPnl734uOTAPOYw%2FXnapper-2026-04-23-10.49.27.png?alt=media&amp;token=d651ac0d-0b76-4f03-8fc1-aa096f657c23" alt="" width="323"><figcaption><p>Collapsed widget shown as a small clock icon in the bottom-right corner</p></figcaption></figure>

## Refresh Button

Clicking **Refresh** forces a fresh fetch from the DataForSEO API, bypassing all caches (local memory, local database, and your S3 shared tier if configured).

### How Refresh Works Across Tabs

Backlink Analytics and Traffic Analytics have multiple tabs for the same target (Overview, Backlinks, Referring Domains, Organic Keywords, etc.). When you click Refresh on any tab:

{% stepper %}
{% step %}
**All tabs' cached data is invalidated**

The cache is wiped for **every tab** of that target — Overview, Backlinks, Referring Domains, Anchor Texts, Competitors, Organic Keywords, etc. If you have the S3 shared cache configured, matching S3 objects are also removed so your teammates see fresh data on their next visit.
{% endstep %}

{% step %}
**Only the current tab re-fetches immediately**

To save API credits, only the tab you're currently viewing actively re-fetches.
{% endstep %}

{% step %}
**Other tabs re-fetch lazily on visit**

When you switch to another tab (e.g., from Overview to Backlinks), that tab will hit the API because its cache is empty. This avoids spending credits on tabs you don't actually open.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Refreshing a paginated result resets pagination to page 1 and refetches only page 1. Other pages are re-fetched individually when you navigate to them.

A Keyword Explorer search on **Google Ads live** is not paginated, so refreshing it renews the whole set at once and paging through the refreshed results costs nothing. Refresh only affects the source you are looking at; the same keyword's results on the other source are left alone.
{% endhint %}

## Settings

Go to **Settings > Services** and scroll to the **DataForSEO Local Cache** section.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FSgee63xkgiodOgXs1ZBo%2FXnapper-2026-04-23-10.50.42.png?alt=media&amp;token=bb4c0a73-bc21-4e12-ad9a-32e3ef932f38" alt=""><figcaption><p>DataForSEO Local Cache settings card with stats and Clear button</p></figcaption></figure>

The card shows:

* **Cached responses** — how many API responses are stored locally
* **Search history entries** — how many distinct past searches are in your history list
* **Storage used** — approximate disk footprint

### Auto-invalidate Cache After X Days

Set how long cached DataForSEO responses are kept in your local database before they are removed and refetched from the API on the next request. The default is **14 days**.

| Value                                          | Behavior                                                                                                                             |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Any positive number** (e.g. `7`, `14`, `30`) | Cached responses older than this many days are removed automatically. Cleanup runs hourly while the app is open and once at startup. |
| **`0`**                                        | Auto-cleanup is disabled. Cached responses are kept indefinitely until you click **Clear Cache & History** below.                    |

{% hint style="info" %}
Only the **cached responses** are removed — your "Recent searches" list is preserved. Clicking a history entry whose cache has expired triggers a fresh API request and rebuilds the cache automatically.
{% endhint %}

{% hint style="warning" %}
This setting only affects your **local** database. The shared S3 cache (if configured) is governed by its own 7-day rolling cleanup and is unaffected.
{% endhint %}

### Clear Cache & History

The **Clear Cache & History** button removes every cached response and every search history entry from your local database at once. Use it if you want a completely clean slate — the next time you use any DataForSEO tool, data will be fetched fresh from the API.

{% hint style="danger" %}
This action cannot be undone. Any future searches that would have hit the cache will consume API credits instead.
{% endhint %}

## Relationship with S3 Cache

If you've set up [S3 Cache for DataForSEO Data](/guide/data-sharing-with-s3), it works alongside the local cache as a third tier:

| Tier          | Storage                                                | Who sees it                               |
| ------------- | ------------------------------------------------------ | ----------------------------------------- |
| Memory        | RAM (24h)                                              | You only, this session                    |
| Local DB      | Your SQLite file (14-day TTL by default, configurable) | You only, persists across restarts        |
| S3 (optional) | Your configured S3 bucket (7-day TTL)                  | You + teammates with the same credentials |

When a tool needs data, SEO Utils checks the tiers in order and falls through to the DataForSEO API only if all tiers miss.

{% hint style="info" %}
**Clear Cache & History** in this card only affects your **local** tiers. To clear the shared S3 cache, use **Purge Cache** in the S3 Cache Settings card instead.
{% endhint %}

## Tips

* **Let the widget guide your refresh habits.** If it's green, your data is fresh; if it's amber or red, consider refreshing before drawing conclusions.
* **Collapse the widget** if you prefer more screen space — the clock icon still shows the age via tooltip on hover.
* **Use history instead of re-typing** a domain. Clicking a history row reloads instantly and won't burn API credits on cached pages.
* **Tune the auto-invalidate setting** to match how often you need fresh data. Lower it (e.g., 3–7 days) if you track fast-moving competitors, or raise it (e.g., 30 days) if you mostly review historical reports and want to minimize API usage.
* **For team workflows**, pair this with [S3 Cache for DataForSEO Data](/guide/data-sharing-with-s3) so your teammates also benefit from your API calls.


# Google Service Accounts

SEO Utils uses Google Service Accounts for multiple tasks like submitting index, checking/submitting index for URLs, or pulling data from Google Search Console (GSC) to do some advanced tasks that the GSC dashboard doesn't provide to you.

### Create a Google Service Account

#### Step 1

Visit the Google Cloud Console at <https://console.cloud.google.com/> and create a Project if you don't have one.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fed3ebd0e873d1eb361254ecf4c04de3847767f1%2FXnapper-2023-11-30-17.42.13.png?alt=media" alt=""><figcaption><p>Create a project on Google Cloud Console</p></figcaption></figure>

#### Step 2

In your [Google Cloud Console](https://console.cloud.google.com/) dashboard, search for "**Service Accounts**" and click on it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a1cc74a736cda2c0440b1e8b9ab41c553e091718%2FXnapper-2023-11-30-17.51.43.png?alt=media" alt=""><figcaption><p>Click on "Service Accounts" from the search results</p></figcaption></figure>

Hit the "**Create Service Account**" button, and enter a service account name. Then, hit the "**Done**" button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-25f938df748c78cbfa2b6e28a69370b4d45db02f%2FXnapper-2023-11-30-17.56.52.png?alt=media" alt=""><figcaption><p>Enter service account name</p></figcaption></figure>

<mark style="color:green;">**Copy the email of the service account**</mark>. You will need that email to invite the service account to your Google Search Console so it can access data from Google Search Console.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9785e7daf49d21a78bdaf7b770179cbb9c158ef6%2FXnapper-2023-11-30-17.58.38.png?alt=media" alt=""><figcaption><p>Copy the email</p></figcaption></figure>

#### Step 3: Create a Google Service Account key file

Click on the **Service Account's email,** select the "**KEYS**" tab, then click the "**Create new key**" button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4c8c4f49958bb72884c7a528d8baf1e336277a61%2FXnapper-2023-11-30-18.08.28.png?alt=media" alt=""><figcaption><p>Create a key for your service account</p></figcaption></figure>

A model will pop up. Select "JSON" and click the "Create" button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e7e6a767e843707a70f32c22e7d663f5ec465d19%2FXnapper-2023-11-30-18.10.57.png?alt=media" alt=""><figcaption><p>Select JSON in Key type field.</p></figcaption></figure>

After creating the key, Google will download it to your machine. Keep that file. You will need it when adding the Google Service Account to SEO Utils.

### Add the Google Service Account to SEO Utils

Open the SEO Utils app on your machine, and locate the App dropdown menu in the top-right corner. You will see the Google Service Accounts menu.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-32225513a998ac71511023f6547d93c854837cee%2FXnapper-2024-12-12-09.45.57.png?alt=media" alt="" width="375"><figcaption><p>Click on Google Service Accounts menu to create one</p></figcaption></figure>

Hit the "Add Account" button and select the key file you downloaded in the previous step.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-92590d2a67edf3384471354527570471f1946048%2FXnapper-2025-08-28-11.54.47.png?alt=media" alt=""><figcaption><p>Select the downloaded key file after cliking the "Add Account" button</p></figcaption></figure>

Congratulations! You have successfully added a Google Service Account to SEO Utils!

### Connect to Google Search Console

After adding the service account to SEO Utils, you need to grant it access to your Google Search Console properties to pull performance data and submit indexes.

#### Grant Access in Google Search Console

1. **Copy the Service Account Email**: After adding the JSON file, you'll see the service account email displayed (e.g., `seoutils-237@gpapp-1312935720840.iam.gserviceaccount.com`)

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fedbeaffb5c8a2b01c6a9f11e173ce2f0290bef5%2FXnapper-2025-08-28-11.55.17.png?alt=media" alt=""><figcaption><p>Copy the Google Service Account email</p></figcaption></figure>

2. **Add to Google Search Console**:

* Go to your [Google Search Console Dashboard](https://search.google.com/search-console)
* Select your property
* Navigate to Settings → Users and permissions
* Click "Add user"
* Paste the service account email
* Select permission level:
  * **Owner**: Required for submitting indexes via Google Indexing API
  * **Full**: Sufficient for pulling performance data only

{% hint style="warning" %}
**Important**: To submit indexes, the service account must have **Owner** permission in Google Search Console. Full permission is only adequate for reading performance data.
{% endhint %}

### Configure Properties for Index Submission

You can configure which properties each service account can submit indexes for. This setting only affects index submission, not performance data access.

#### Property Configuration Options

**All Properties (Default)**

* When enabled, the service account can submit indexes for all properties in your SEO Utils account
* This is the default setting for new service accounts

**Specific Properties**

* When disabled, you can select specific properties that this service account can access
* Toggle off "All Properties" to reveal a list of available properties
* Check the properties you want this service account to submit indexes for

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7e6c5e015b3b2f078634a1c19e012ecee4fd4b62%2FXnapper-2025-08-28-11.58.33.png?alt=media" alt=""><figcaption><p>Select specific properties for this service account to access</p></figcaption></figure>

{% hint style="info" %}
**Note**: This property configuration is for index submission only. The service account can still pull performance data from all properties where it has been granted access in Google Search Console.
{% endhint %}


# Google OAuth Token

SEO Utils uses Google OAuth Tokens to securely connect to your Google accounts and access Google Search Console data. This allows you to pull GSC data directly into SEO Utils for advanced analysis and reporting that the standard GSC interface doesn't provide.

## Connect Your Google Account

### Step 1: Access Google OAuth Tokens

Open the SEO Utils app on your machine, and locate the Settings menu in the left sidebar. You will see the Google OAuth Tokens menu.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-31d3820c9706b803d13517057000ee9d8d300cd7%2FXnapper-2025-08-05-22.48.22.png?alt=media" alt="" width="375"><figcaption><p>Click on Google OAuth Tokens menu to manage your connections</p></figcaption></figure>

### Step 2: Connect Your Google Account

Click the "**Connect**" button in the top-right corner of the Google OAuth Tokens page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e77c6d5e18f229079480303248d77b260baeba8b%2FXnapper-2025-08-05-22.48.57.png?alt=media" alt=""><figcaption><p>Click the Connect button to start the authorization process</p></figcaption></figure>

### Step 3: Authorize SEO Utils

After clicking Connect, your default web browser will open with Google's authorization page. Follow these steps:

1. **Select your Google account** that has access to Google Search Console
2. **Review the permissions** that SEO Utils is requesting
3. Click "**Allow**" to grant SEO Utils access to your Google Search Console data

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8c67ab7f335593035e6daffa6424270a1ea644d2%2FXnapper-2025-08-05-22.49.34.png?alt=media" alt=""><figcaption><p>Review and allow the requested permissions</p></figcaption></figure>

{% hint style="info" %}
SEO Utils only requests read-only access to your Google Search Console data. It cannot modify or delete any data in your GSC account.
{% endhint %}

### Step 4: Authorization Complete

Once you've authorized access, you'll see a success message in your browser. You can close the browser tab and return to SEO Utils.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-74a1088b39595f6663df43099643f9a963361aef%2FXnapper-2025-08-05-22.50.43.png?alt=media" alt=""><figcaption><p>Authorization successful - you can close this tab</p></figcaption></figure>

Your connected Google account will now appear in the Google OAuth Tokens list with your email address and profile picture.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-09929a247777a0daca5df66fd559b97e7ed97b6d%2FXnapper-2025-08-05-22.51.09.png?alt=media" alt=""><figcaption><p>Your connected Google account</p></figcaption></figure>

## Managing Multiple Google Accounts

You can connect multiple Google accounts to SEO Utils. This is useful if you manage GSC properties across different Google accounts.

Simply click the "**Connect**" button again and follow the same authorization process with a different Google account.

### Remove a Google Account

To disconnect a Google account:

1. Find the account you want to remove in the list
2. Click on the three-dot menu on the right side of the account row
3. Select "**Delete**" from the dropdown menu
4. Confirm the deletion when prompted

{% hint style="warning" %}
Removing a Google account will disconnect all associated Google Search Console properties from SEO Utils. You'll need to reconnect the account to access that GSC data again.
{% endhint %}

## Using Google OAuth with GSC Integration

Once you've connected your Google accounts, you can use them with various [Google Search Console integration](/guide/google-search-console) features in SEO Utils:

* **Performance Analytics**: Complete search data with advanced regex filtering and more than 16 months of history
* **Keyword Cannibalization Detection**: Identify when multiple pages compete for the same keywords, hurting your rankings
* **Bulk Mentions Analysis**: Check if target keywords appear in critical SEO elements:
  * Page titles and meta descriptions
  * H1, H2, and other headings
  * Body content and paragraphs
  * Image alt text and captions
* **Optimization Opportunities**: Data-driven insights showing:
  * Pages ranking 4-10 that need small tweaks to reach top 3
  * High-impression keywords missing from your content
  * Title/meta description improvements for better CTR
  * Quick wins based on position and mentions analysis
* **Bulk URL Indexing**: Submit multiple URLs to Google for indexing at once
* **Sitemap Management**: Monitor and manage your XML sitemaps directly

## Troubleshooting

### Authorization Failed

If the authorization process fails:

1. Make sure you're selecting a Google account that has access to Google Search Console
2. Check that you're allowing all the requested permissions
3. Try clearing your browser cache and cookies, then attempt the connection again

### Account Not Showing GSC Properties

If your connected account doesn't show any GSC properties:

1. Verify that the Google account has been added as a user in Google Search Console
2. Check that the account has at least "Read" permissions for the properties (needs "Owner" permissions to check index status if using the [Auto Indexing tool](/guide/auto-indexing-tool)).
3. Try disconnecting and reconnecting the account

### Token Expired

Google OAuth tokens may occasionally expire. If you see errors about expired tokens:

1. Simply delete the affected account from the list
2. Click "**Connect**" to re-authorize the account

## Privacy & Security

* SEO Utils stores OAuth tokens securely on your local machine
* Tokens are never transmitted to any external servers except Google's APIs
* You can revoke access at any time by deleting the account from SEO Utils


# Google Analytics 4

SEO Utils integrates with Google Analytics 4 (GA4) to sync your site's traffic into your local database: sessions, engaged sessions, key events (conversions) and revenue for every channel, not only organic search. You read it on the [GA4 Traffic](/guide/google-analytics-4/ga4-traffic) page, next to your search data in Search Console and the rank trackers, and in your client reports. The organic landing pages also power the **Key Events** insight in the Organic Rank Tracker, showing you which tracked keywords are driving conversions.

{% embed url="<https://youtu.be/2Zp7VLg9dDs>" %}
Connecting GA4 and using its traffic across SEO Utils
{% endembed %}

{% hint style="info" %}
GA4 data is synced automatically once per day, and SEO Utils catches up when it starts if a day was missed. It is stored locally. Your data never leaves your machine.
{% endhint %}

## Prerequisites

Before setting up GA4 integration, you need:

* A **GA4 property** with your website configured
* A **Google service account** in SEO Utils with **Viewer** access to that property. Steps 1 and 2 below create it and give it access

## Step 1: Connect Google

The service account needs the Google Analytics Data API (to sync your metrics) and the Google Analytics Admin API (to find your GA4 properties). Pick one way to set it up:

{% tabs %}
{% tab title="Connect Google (Recommended)" %}
SEO Utils creates the service account for you, with both GA4 APIs turned on.

1. In the sidebar, open **Settings → Google Service Accounts** and click **Connect Google**, at the top right next to **Add Account**
2. On the **Connect Google** page, click **Connect Google**. **Search Console, Indexing and Google Analytics 4** are always included, and free
3. Your browser opens Google's sign-in page: sign in and click **Allow**

It takes about 3 minutes. When the page reads **Google is connected**, keep it open for Step 2. If SEO Utils asks a question on the way, see [Connect Google Automatically](/guide/set-up-seo-utils#connect-google-automatically).
{% endtab %}

{% tab title="With Your AI App" %}
When your AI app is connected to SEO Utils (see [Set Up with Your AI App](/guide/set-up-seo-utils#set-up-with-your-ai-app-recommended)), ask it to set up Google Analytics 4 in SEO Utils. It checks what is missing, starts Connect Google for you and explains each step. You sign in to Google and answer its questions in SEO Utils.

On the **Add GA4 Property** page, when you have no service account yet, **Set up with your AI app** copies the prompt for this step.

Your AI app cannot give the service account access to GA4: do Step 2 yourself.
{% endtab %}

{% tab title="By Hand" %}
Use this when you already have a service account (see [Google Service Accounts](/guide/google-service-accounts)). Turn on both APIs in the Google Cloud project it belongs to:

1. Go to the [Google Cloud Console](https://console.cloud.google.com/) and select the project of your service account
2. Open **APIs & Services → Library**
3. Search for **"Google Analytics Data API"** and click **Enable**
4. Search for **"Google Analytics Admin API"** and click **Enable**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F1emLf5jqz6MeD6xIxPBv%2FXnapper-2026-03-30-21.26.11.png?alt=media&amp;token=666fc2ca-a4eb-4e39-831a-cc6f6c112f01" alt="" width="563"><figcaption><p>Enable the Google Analytics Data API in Google Cloud Console</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FrIMngPkIVRkpnnGaLIPN%2FXnapper-2026-03-30-21.26.50.png?alt=media&amp;token=2ab78459-04ad-4980-899a-3a643aaf9e02" alt="" width="563"><figcaption><p>Enable the Google Analytics Admin API in Google Cloud Console</p></figcaption></figure>

{% hint style="warning" %}
Both APIs must be enabled in the **same Google Cloud project** that your service account belongs to. APIs are enabled at the project level, not per service account.
{% endhint %}
{% endtab %}
{% endtabs %}

## Step 2: Grant Service Account Access to GA4

Your service account needs permission to read data from your GA4 property. Google lets only you do this step.

{% stepper %}
{% step %}
**Copy Your Service Account Email**

After Connect Google, click **Copy email** on the **Google Analytics 4** card under **Finish in Google**, then **Open Google Analytics**.

Otherwise, go to the **Google Service Accounts** page in SEO Utils and copy the service account email (e.g., `project-932@project-1608918721837.iam.gserviceaccount.com`).
{% endstep %}

{% step %}
**Add the Service Account to GA4**

You can grant access at the **property level** or **account level**:

{% tabs %}
{% tab title="Property Level (Single Property)" %}

* Go to [Google Analytics](https://analytics.google.com/)
* Click the **gear icon** (Admin) at the bottom-left
* Under **Property**, click **Property Access Management**
* Click the **+** button → **Add users**
* Paste your service account email
* Set the role to **Viewer**
* Click **Add**
  {% endtab %}

{% tab title="Account Level (All Properties)" %}
If you want the service account to access **all properties** under your GA4 account:

* Go to [Google Analytics](https://analytics.google.com/)
* Click the **gear icon** (Admin) at the bottom-left
* Under **Account**, click **Account Access Management**
* Click the **+** button → **Add users**
* Paste your service account email
* Set the role to **Viewer**
* Click **Add**

This grants access to all current and future properties under that account.
{% endtab %}
{% endtabs %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FzgnAFCmtSnQi25nDzaIs%2FXnapper-2026-03-30-21.28.22.png?alt=media&amp;token=5861239b-6f3f-4fa9-a36d-87b7494c1392" alt=""><figcaption><p>Add the service account email as a Viewer in GA4 Property Access Management</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Viewer** permission is sufficient. SEO Utils only reads data from GA4 — it never modifies your analytics configuration.
{% endhint %}

## Step 3: Add a GA4 Property in SEO Utils

{% stepper %}
{% step %}
**Navigate to Google Analytics 4**

In the sidebar, under **Your Sites**, open **Google Analytics 4** and click **Add Property** at the top right.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FW0xUcuhyE7qv6K9z6m6o%2FXnapper-2026-03-30-21.29.43.png?alt=media&amp;token=c433f2b3-ca09-469b-9a1b-c98f56826f68" alt="" width="375"><figcaption><p>Google Analytics 4 section in the sidebar</p></figcaption></figure>
{% endstep %}

{% step %}
**Select a Service Account**

Choose the Google Service Account that has access to your GA4 property. SEO Utils will fetch all GA4 properties the account can access.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F0XQze7Y9Lf1P41N6TAJY%2FXnapper-2026-03-30-21.30.28.png?alt=media&amp;token=70a97f45-b3c1-4612-9044-fead283c78c3" alt=""><figcaption><p>Select a service account to list accessible GA4 properties</p></figcaption></figure>
{% endstep %}

{% step %}
**Select a GA4 Property**

Pick your GA4 property from the dropdown. The **Mapped Domain** field will auto-fill based on the property's website URL — this links the GA4 data to your Organic Rank Tracker reports.

Set the **Initial Backfill** to choose how many days of organic landing-page history to import on first sync (default: 90 days). GA4 free tier retains 2 months of data by default, or up to 14 months if you've enabled extended retention in your GA4 property settings. The channel, source and monthly traffic always import 16 months.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FI3ELOwZd2qdbku9dLGOM%2FXnapper-2026-03-30-21.31.51.png?alt=media&amp;token=1036a6d8-7f80-42dc-b7ac-41887a35e07f" alt=""><figcaption><p>Select a GA4 property, confirm the mapped domain, and set the backfill period</p></figcaption></figure>

{% hint style="info" %}
The mapped domain should match the target domain in your Organic Rank Tracker report. For example, if your rank tracker tracks `example.com`, the mapped domain should also be `example.com`.
{% endhint %}
{% endstep %}

{% step %}
**Manage Your Properties**

After adding a property, SEO Utils will automatically start syncing historical data. You can see it in the **GA4 Properties** list. From here you can:

* **Read the Status** — **Synced**, **Syncing...**, **Not synced yet**, or **Failed**. Hover **Failed** to see which data did not sync
* **Open GA4 Traffic** — Click the property's name to see its [traffic by channel](/guide/google-analytics-4/ga4-traffic)
* **Enable/disable sync** — Toggle whether this property syncs automatically once per day
* **Sync Now** — Trigger an immediate data sync
* **Edit domain** — Click the domain to change the mapped domain
* **Remove** — Delete the property and all synced GA4 data. You can re-add the property later to sync again

{% hint style="warning" %}
Removing a GA4 property deletes all synced metrics data for that property. Key Events badges in the Organic Rank Tracker will no longer appear for keywords associated with this property. The data can be re-synced by adding the property again.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FfIEysAWqe1PAtoXLLLW6%2FXnapper-2026-03-30-21.33.28.png?alt=media&amp;token=ec730c5d-713f-423a-8423-35f755819081" alt=""><figcaption><p>GA4 Properties list showing connected properties with sync status</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-17243729caa6fcaa7cc73040fd34f7752a3882a4%2Fga4-properties-status.png?alt=media" alt="The GA4 Properties list with a property in the Synced status"><figcaption><p>The Status column (1) shows the result of the last sync</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Syncing Data

GA4 data syncs automatically **once per day**, and SEO Utils catches up when it starts if a day was missed, for example when your computer was off. You can also click **"Sync Now"** in the GA4 Properties list to trigger an immediate sync.

The first sync downloads **16 months** of history, newest month first, so the recent months are ready before the older ones. SEO Utils syncs these datasets:

| Dataset                      | What it holds                                                                                   |
| ---------------------------- | ----------------------------------------------------------------------------------------------- |
| **Traffic by channel**       | Sessions, engaged sessions, key events and revenue per day, for every GA4 default channel group |
| **Organic search by engine** | Organic Search split by Google, Bing, DuckDuckGo and the other search engines                   |
| **Source / medium**          | Sessions, key events and revenue per day for every source, such as `google / organic`           |
| **Key events by channel**    | Each key event, by channel and day                                                              |
| **Monthly users**            | Users and new users per month, per channel and for the whole site                               |
| **Organic landing pages**    | Per page and day, organic search only (below)                                                   |

### Organic landing pages

For each organic landing page, per day:

| Metric               | Description                                                     |
| -------------------- | --------------------------------------------------------------- |
| Sessions             | Number of organic search sessions                               |
| Engaged Sessions     | Sessions with meaningful engagement                             |
| Bounce Rate          | Percentage of single-page sessions                              |
| Avg. Engagement Time | Average time users spent on the page                            |
| Users                | Total unique users from organic search                          |
| New Users            | First-time visitors from organic search                         |
| Key Events           | Conversion events (purchases, sign-ups, form submissions, etc.) |
| Revenue              | Total revenue from organic search sessions                      |

## How GA4 Data Powers Key Events

The primary use of GA4 data is the **Key Events** insight in the [Organic Rank Tracker](/guide/organic-rank-tracker). When GA4 data is synced, the rank tracker can show you which keywords are associated with pages that generate conversions.

For example, if the keyword "deep cleaning cambridge" ranks on your `/cambridge` page, and that page had 3 conversions in GA4, the keyword will display a **"3 Key Events"** badge in the rank tracker.

This helps you:

* **Identify revenue-driving keywords** — See which keywords are associated with actual business outcomes
* **Prioritize SEO efforts** — Focus on keywords that drive conversions, not just traffic
* **Correlate rank changes with conversions** — Spot when a ranking improvement leads to more conversions

{% hint style="info" %}
Key Events attribution works by matching the rank tracker's keyword → page mapping with GA4's landing page → conversion data. For the most accurate results, also connect [Google Search Console](/guide/google-search-console) to provide authoritative keyword-to-page click data.
{% endhint %}

## Where You See the Data

| Where                                                                                                                                                                                                           | What you get                                                                                               |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| [GA4 Traffic](/guide/google-analytics-4/ga4-traffic)                                                                                                                                                            | Every channel, compared with the previous period or last year, with top sources and 13 months              |
| [Search Console](/guide/google-search-console#ga4-traffic-next-to-your-clicks)                                                                                                                                  | Google organic sessions on the performance chart, an organic share card and GA4 columns on the Pages table |
| [GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#page-sessions-and-key-events)                                                                                               | The sessions and key events of each keyword's page                                                         |
| [Organic Rank Tracker](/guide/organic-rank-tracker#show-site-traffic-in-the-report) and [GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker/print-and-pdf#show-site-traffic-in-the-report) reports | A Site traffic section in the PDF                                                                          |
| [Client reports](/guide/white-labeled-client-report#the-traffic-tab)                                                                                                                                            | A Traffic tab in the published Organic report                                                              |
| [MCP server](/guide/mcp-server#google-analytics-tools)                                                                                                                                                          | The same data for your AI assistant                                                                        |

## Troubleshooting

<details>

<summary>"Google Analytics Data API has not been used in project" error</summary>

You need to enable the **Google Analytics Data API** in your Google Cloud project. Visit the link in the error message to enable it, then wait a minute and try again.

</details>

<details>

<summary>"Google Analytics Admin API has not been used in project" error</summary>

You need to enable the **Google Analytics Admin API** in your Google Cloud project. This is a separate API from the Data API — both need to be enabled. Visit the link in the error message to enable it.

</details>

<details>

<summary>No properties found after clicking "Discover Properties"</summary>

Your service account doesn't have access to any GA4 properties. Grant the service account **Viewer** access in GA4's Property Access Management (or Account Access Management for all properties).

</details>

<details>

<summary>Data syncs successfully but shows 0 rows</summary>

This is normal if your site has very low organic search traffic, or if GA4 data hasn't finished processing yet (24-72 hour delay). The sync will pick up the data on the next run.

</details>

<details>

<summary>Sync failed with authentication error</summary>

* Verify your service account still has access to the GA4 property
* Check that the service account key hasn't expired or been deleted in Google Cloud Console
* Re-upload the service account key file if needed

</details>


# GA4 Traffic

The **GA4 Traffic** page shows where a site's visitors come from, for every Google Analytics 4 channel and not only organic search: sessions, key events and revenue, compared with the previous period or the same period last year. It reads the data SEO Utils has already synced from [Google Analytics 4](/guide/google-analytics-4), so it opens without waiting for Google.

## Open the page

Open **Your Sites > GA4 Traffic** in the sidebar. If several GA4 properties are connected, click the property's name in the page bar to switch to another one. The owner can also click a property's name in the **GA4 Properties** list.

{% hint style="info" %}
A [team member](/guide/team) with access to reports, a Viewer or above, can open this page and read it. Only the owner can sync, edit the domain or remove a property, and exporting needs the **Export data** permission.
{% endhint %}

## Read the overview

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-80f39f9b4bd32bdfffd92f795a8b093f85475bd7%2Fga4-traffic-overview.png?alt=media" alt="The GA4 Traffic page with the date range, the comparison, six KPI cards and the sessions by channel chart"><figcaption><p>The date range (1), the comparison (2), the KPI cards (3) and the sessions by channel chart (4)</p></figcaption></figure>

* **Date range (1).** The page starts with the last 28 days that GA4 has settled. GA4 can still change its last three days, so they are drawn dashed on the chart and left out of every comparison.
* **Compare with (2).** Choose **Previous period**, **Same period last year** or **No comparison**. When the comparison period is not fully synced, the card says **No data** instead of a percentage.
* **KPI cards (3).** Sessions, Engaged sessions, Engagement rate, Key events, Session key event rate and Revenue, each with its change against the comparison. Rates change in percentage points (pp). Revenue appears only when the property records it. Hover the (?) on a card for its definition.
* **Chart (4).** Sessions stacked by channel, one colour per channel. Switch it to **Key events** to see which channels produce them.

## Channels and search engines

The **Channels** table lists every GA4 default channel group, such as Organic Search, Direct, Referral, Paid Search, Email and Organic Social, with its sessions, share of all sessions, change, engaged sessions, engagement rate, key events, session key event rate and revenue.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-919a697dde8621a558fe0f879e35f75dd67d00e7%2Fga4-traffic-channels.png?alt=media" alt="The Channels table with Organic Search expanded to show Google, Bing, DuckDuckGo, Yahoo and Ecosia"><figcaption><p>Click the arrow (1) to split Organic Search by search engine. The line above the table (2) gives organic search's share</p></figcaption></figure>

Organic Search is highlighted. Click the arrow next to it to split it by search engine, for example Google, Bing and DuckDuckGo. The line above the table gives organic search's share of all sessions and of all key events.

## Key events, sources and months

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-105235f458c6a304a4baeb3274a07b16606909c5%2Fga4-traffic-sources.png?alt=media" alt="The Key events by channel table and the first rows of the Top sources table"><figcaption><p>Key events by channel (1) and Top sources (2)</p></figcaption></figure>

| Section                   | What it shows                                                                                                                                                                                |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Key events by channel** | One row per key event, with its total and a column for each channel.                                                                                                                         |
| **Top sources**           | The sources that sent the most sessions, such as `google / organic` or `newsletter / email`, with their channel, sessions, share, engaged sessions, engagement rate, key events and revenue. |
| **Last 13 months**        | One row per month with sessions, key events, revenue, **Users (GA4)** and **New users (GA4)**. The month still running is marked **(so far)**.                                               |

GA4 estimates users, and the same person can visit through several channels, so users are never added up across months or channels. They are shown only in the monthly table.

{% hint style="info" %}
When GA4 withheld small counts or grouped rows, a note appears above the cards, for example **Subject to GA4 thresholds; small counts may be withheld**. The figures are GA4's own.
{% endhint %}

## Sync and export

* **Sync now** (top right, owner only) syncs the property immediately. The page refreshes when the sync ends. The property also syncs by itself every day.
* **Export CSV** is in the menu under the property's name. It saves the Channels table for the selected range.

## Where else the numbers appear

GA4 traffic also sits next to your search data and in your client reports:

* On a [Search Console](/guide/google-search-console#ga4-traffic-next-to-your-clicks) property: sessions on the chart, an organic share card and GA4 columns on the Pages table.
* In the [GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#page-sessions-and-key-events): the sessions and key events of each keyword's page.
* In the [Organic Rank Tracker](/guide/organic-rank-tracker#show-site-traffic-in-the-report) and Rankings reports, and in the [published client report](/guide/white-labeled-client-report#the-traffic-tab).
* Through the [MCP server](/guide/mcp-server#google-analytics-tools).


# Google Search Console

SEO Utils' Google Search Console integration provides a powerful alternative to the standard GSC interface. By connecting your GSC account, you get access to all your search data with advanced features like unlimited historical data storage, natural language filtering, bulk operations, and AI-powered insights - all while maintaining the familiar GSC functionality you already use.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-10a0c4a86973464b4aaeb7b6c25c7107166a9362%2FXnapper-2025-08-28-21.47.11.png?alt=media" alt=""><figcaption><p>See how the keyword is mentioned in your content.</p></figcaption></figure>

### Setup the Integration

There are two methods to connect SEO Utils to your Google Search Console data:

1. **Google OAuth Token** (Recommended for most users)
2. **Google Service Account** (Advanced option for automation)

***

## Method 1: Google OAuth Token

The Google OAuth Token method is the simplest way to connect your Google Search Console data to SEO Utils. This method uses your own Google account credentials.

### Benefits of OAuth Token Method

* **Quick setup** - No need to create service accounts or manage API keys
* **Direct access** - Uses your existing Google account permissions
* **Multiple accounts** - Easily connect multiple Google accounts
* **Automatic permissions** - Access all GSC properties your account can see

### Setup Steps

1. Open SEO Utils and navigate to **Settings menu in the left sidebar > Google OAuth Tokens**
2. Click the **Connect** button
3. Authorize SEO Utils to access your Google Search Console data
4. Your Google account will be connected and ready to use

For detailed setup instructions, see the [Google OAuth Token guide](/guide/google-oauth-token).

{% hint style="info" %}
The OAuth Token method is perfect for individual users and small teams who want a simple, secure way to access their GSC data.
{% endhint %}

***

## Method 2: Google Service Account

The Google Service Account method provides more control and is suitable for advanced users who need programmatic access or specific permission management.

### Benefits of Service Account Method

* **Granular control** - Manage permissions for specific properties
* **Automation-ready** - Ideal for scheduled tasks and API automation
* **No expiration** - Service account keys don't expire like OAuth tokens
* **Team sharing** - Share service account across team without sharing personal credentials

### Setup Steps

#### **Step 1: Enable Google Search Console API**

Visit the [Google Cloud Console](https://console.cloud.google.com/) and create a project if you don't have one. Then search for "**Google Search Console API**" in the top search bar, click on it, and hit **Enable**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-36957c4cdf5e19ba5d3e16315dfca84df4f0dad5%2FXnapper-2024-01-08-21.51.21.png?alt=media" alt=""><figcaption><p>Google Search Console API is enabled</p></figcaption></figure>

#### Step 2: Create and Add a Google Service Account

Follow the comprehensive guide to create and add a Google Service Account to SEO Utils:

1. **Create the Service Account**: Follow [this guide](/guide/google-service-accounts#create-a-google-service-account) to create a service account and download the JSON key file
2. **Add to SEO Utils**: Follow [this guide](/guide/google-service-accounts#add-the-google-service-account-to-seo-utils) to add the service account to SEO Utils
3. **Important**: Copy the service account email address - you'll need it in the next step

#### Step 3: Grant Service Account Access in GSC

Now you need to grant the service account access to your Google Search Console properties:

1. Go to your [Google Search Console Tool](https://search.google.com/search-console)
2. Select the property you want to integrate
3. Navigate to **Settings → Users and permissions**
4. Click **Add user**
5. Enter the **service account email** (e.g., `gpapp-932@gpapp-1607908720839.iam.gserviceaccount.com`)
6. Select permission level:
   * **Full**: For pulling performance data only
   * **Owner**: Required if you want to use the [Auto-indexing tool](/guide/auto-indexing-tool) to submit indexes

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ef2a8f9a1fdc1517dd28332fff930e4531b22967%2FXnapper-2024-01-08-22.11.53.png?alt=media" alt=""><figcaption><p>Add the service account email with appropriate permissions</p></figcaption></figure>

{% hint style="warning" %}
**Important**: To submit indexes via the Google Indexing API, the service account must have **Owner** permission. Full permission is sufficient for reading performance data only.
{% endhint %}

Once you complete this step, the Google Service Account will gain full access to the website data in your Google Search Console. With this, you're all set to utilize this integration on SEO Utils 🎉

***

## Data Storage and Retention

After connecting your properties, SEO Utils will pull all data from the Google Search Console API and store it locally on your machine.

{% hint style="success" %}
The application automatically pulls new data every day, which means you can view and analyze data for **more than the standard 16-month limit** imposed by Google Search Console.
{% endhint %}

### Key Benefits of Local Storage

* **Extended Historical Data**: While Google Search Console only provides 16 months of data, SEO Utils stores everything locally, allowing you to build an unlimited historical archive
* **Daily Automatic Updates**: New data is automatically fetched every day without any manual intervention
* **Offline Access**: Your data is available even without an internet connection since it's stored locally
* **No API Limits**: Browse and analyze your data without worrying about API rate limits

## Available Features

The SEO Utils integration contains all features from the Google Search Console dashboard, plus advanced features that GSC doesn't provide. Whatever you can do on the GSC dashboard, you can do in SEO Utils - and more.

### Standard GSC Features Available in SEO Utils

* Performance reports with clicks, impressions, CTR, and position data
* Search analytics with query and page filtering
* Date range comparisons
* Country, device, and search appearance filtering
* Sitemap management
* URL inspection and indexing status

### Advanced Features Not Available in Standard GSC

* Extended data retention beyond 16 months
* Filter data using Natural Language
* Bulk mention checking across all content
* Keyword cannibalization detection
* AI-powered insights and opportunities
* Bulk URL indexing submission
* Complete data export without sampling limitations
* Multi-account management in a single dashboard
* SEO Tests: Time-based Test, URL Switch Test, Split Tests
* Chart annotations with automatic Google algorithm update tracking
* Internal link suggestions: find the pages that need links and the sentence to add each one to
* GSC Rank Tracker: free daily keyword rankings with 16 months of history, movers, alerts, AI explanations and reports, from your own Search Console data
* GA4 traffic next to your clicks: organic sessions on the performance chart, an organic share card and GA4 columns on the Pages table

Please follow the guides below to learn how to use these features:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Annotations</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FKtff0oA3eDtd6EHn8OA8%2FXnapper-2026-01-31-11.44.00.png?alt=media&amp;token=0e06fbe8-d577-4a62-955d-0e357917611d">Xnapper-2026-01-31-11.44.00.png</a></td><td><a href="/guide/google-search-console/annotations">Annotations</a></td></tr><tr><td>Topic Clusters</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5c10bef4f945ccd81d22657da6e407519d354a4d%2FXnapper-2025-08-28-21.55.51.png?alt=media">Xnapper-2025-08-28-21.55.51.png</a></td><td><a href="/guide/google-search-console/topic-clusters">Topic Clusters</a></td></tr><tr><td>Keyword Metrics</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cb34e488f71b3795019b989cdb3fe81c61809a3c%2FCleanShot%202025-09-01%20at%2022.18.29%402x.png?alt=media">CleanShot 2025-09-01 at 22.18.29@2x.png</a></td><td><a href="/guide/google-search-console/keyword-metrics">Keyword Metrics</a></td></tr><tr><td>SEO Tests</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-273f9ee846bb6f8351acefcb9052b19a4d0b7226%2FCleanShot%202025-09-08%20at%2013.18.11%402x.png?alt=media">CleanShot 2025-09-08 at 13.18.11@2x.png</a></td><td><a href="/guide/google-search-console/seo-tests">SEO Tests</a></td></tr><tr><td>Internal Links</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-23706452980da93a610748dc3288e115c241b73c%2Fplaceholder.png?alt=media">placeholder.png</a></td><td><a href="/guide/google-search-console/internal-links">Internal Links</a></td></tr><tr><td>GSC Rank Tracker</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-48b4e5790222b9cfd29c3ff039ef5a5b3cc5bada%2Fgsc-rankings-overview.png?alt=media">gsc-rankings-overview.png</a></td><td><a href="/guide/google-search-console/gsc-rank-tracker">GSC Rank Tracker</a></td></tr></tbody></table>

## GA4 traffic next to your clicks

When a [Google Analytics 4](/guide/google-analytics-4) property is mapped to the same site, the property's **Performance** page shows what happened after the click. Open **Your Sites > Search Console** and click the property.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7d38f38c803e0c6204ec6cede5fb8688269533d1%2Fgsc-property-ga4-chart.png?alt=media" alt="The Performance chart with a Google organic sessions line, the metrics menu with its Google Analytics group and the organic share card"><figcaption><p>The Google Analytics group in the metrics menu (1), the Google organic sessions line (2), the organic share card (3) and View GA4 traffic (4)</p></figcaption></figure>

* **Chart lines (1, 2).** Open the **metrics** button above the chart. Its **Google Analytics** group has **Google organic sessions** (on by default), **All organic sessions** and **Organic key events**. Google organic sessions is the line to compare with clicks, because Search Console only covers Google. All organic sessions also counts the other search engines. A click is not always a session, so sessions run lower than clicks: hover the (?) next to the line to see why.
* **Organic share card (3).** **Organic share of sessions** is the part of all GA4 sessions that came from organic search, and **Google share of organic sessions** is Google's part of those. **View GA4 traffic (4)** opens [GA4 Traffic](/guide/google-analytics-4/ga4-traffic).
* **When the lines are off.** GA4 cannot apply Search Console's filters, so the lines are disabled, with the reason, while the chart uses a query, page, country or device filter, a search type other than **Web**, or a search-type comparison.
* **Which GA4 property.** If several GA4 properties match the site, the chart asks you to choose one. SEO Utils remembers your choice for the Pages table and the [Rankings](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#page-sessions-and-key-events) tab, and **Change GA4 property** lets you pick again.

A property that covers only part of a site, such as a URL prefix with a path, has no chart line or share card, because GA4 cannot split a site's traffic by path.

### GA4 columns on the Pages table

Open the **Pages** tab under **Dimension Analytics** to see **GA4 sessions** and **GA4 key events** next to each page's clicks and impressions: the organic sessions and key events GA4 recorded for pages that visitors landed on. Click a GA4 column's header to sort all pages by it, not only the ones on screen. A page with no GA4 traffic counts as 0. The sort is unavailable, with the reason in the header menu, when the date range starts before GA4's page data does: choose a range that starts on or after the date the menu gives. Hide the other columns with the column button to make room.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fae363b2793ce35a7b86ca641f89c3769dee93aa%2Fgsc-property-ga4-pages.png?alt=media" alt="The Pages tab with Clicks, Imp., CTR and Pos. columns followed by GA4 sessions and GA4 key events"><figcaption><p>GA4 sessions (1) and GA4 key events (2) on the Pages table</p></figcaption></figure>

## Rankings across properties

If you track keywords with the [GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker), the properties page can show every tracker in one table. Open **Your Sites > Search Console** in the sidebar and switch from **Properties** to **Rankings** (1).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-202057a97951f1e45840d15edabe9cc8ab9e2541%2Fgsc-rankings-portfolio.png?alt=media" alt="The Rankings view of the Search Console properties page with three trackers"><figcaption><p>The Rankings switch (1) and a tracker's property link (2)</p></figcaption></figure>

Each row is one tracker, with its market and these figures:

* **Items**, **Avg position**, **Top 3** and **Top 10**, with the change over 7 days.
* **Movers · 7 days**: how many keywords improved and declined, confirmed on two days.
* **Unread alerts**, **Bands** (how many keywords sit in each position band) and a **90-day trend** of the average position.

The figures match the tracker's [KPI strip](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#kpi-strip) with its default date range. Click the property name (2) to open that tracker. Sort by a column, search by domain or tracker name, and use **View** to choose the columns. The **Rankings** tab shows a badge with the unread alerts of every tracker in the workspace. A figure that shows "…" is being recalculated and fills in after the next refresh.

***


# Annotations

Annotations let you mark important events directly on your Google Search Console performance charts. Use them to track algorithm updates, content changes, technical fixes, or any event that might impact your search performance.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FKtff0oA3eDtd6EHn8OA8%2FXnapper-2026-01-31-11.44.00.png?alt=media&amp;token=0e06fbe8-d577-4a62-955d-0e357917611d" alt=""><figcaption><p>Annotations appear as triangle markers on the chart timeline</p></figcaption></figure>

## Why Use Annotations?

When analyzing search performance changes, it's crucial to understand what happened and when. Annotations help you:

* **Correlate changes**: See how content updates or technical fixes affected your traffic
* **Track algorithm updates**: Google algorithm updates are automatically added as annotations
* **Document your work**: Keep a record of SEO changes for future reference
* **Share context**: When reviewing data with others, annotations explain what happened

## Viewing Annotations

Annotations appear as small triangle markers at the bottom of your GSC performance chart.

{% stepper %}
{% step %}
**Enable Annotations**

Click the **notebook icon** in the chart toolbar to open the annotations menu. Annotations are shown by default.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FLjPNRxizfN6rYTyYAe9d%2FXnapper-2026-01-31-11.44.59.png?alt=media&amp;token=135530de-9c07-48a9-9998-6cab052d8832" alt="" width="563"><figcaption><p>Annotations dropdown menu</p></figcaption></figure>
{% endstep %}

{% step %}
**Filter by Type**

Use the checkboxes to show or hide specific annotation types:

| Type          | Description                                    |
| ------------- | ---------------------------------------------- |
| Custom        | Annotations you create manually                |
| Google Update | Automatically tracked Google algorithm updates |
| System        | System-generated annotations                   |
| {% endstep %} |                                                |

{% step %}
**View Annotation Details**

Hover over any triangle marker to see a tooltip with the annotation details. Click the marker to open the full annotations panel for that date.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Ft3UTmFG5hUGPomcCqzKJ%2FXnapper-2026-01-31-11.45.48.png?alt=media&amp;token=c187d462-db2d-4ae2-8db2-bfa7beed90f4" alt=""><figcaption><p>Click an annotation marker to see details</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Adding Annotations

{% stepper %}
{% step %}
**Open the Annotations Menu**

Click the **notebook icon** in the chart toolbar.
{% endstep %}

{% step %}
**Click Add Annotation**

Select **"Add annotation"** from the dropdown menu.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FDFJStvZYJf3EohT5SRYT%2FXnapper-2026-01-31-11.46.27.png?alt=media&amp;token=f5c8793b-276f-472a-bbb0-7af9d19b5208" alt="" width="563"><figcaption><p>Add annotation option in the menu</p></figcaption></figure>
{% endstep %}

{% step %}
**Fill in the Details**

* **Title**: A short description of the event
* **Date**: When the event occurred
* **Description** (optional): Additional context or notes

Click **"Save"** to add the annotation.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Annotations are linked to the GSC property, so they'll appear whenever you view that property's performance chart.
{% endhint %}

## Managing Annotations

### View All Annotations

Click **"View all annotations"** in the annotations menu to open a panel showing all annotations for the current property.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FuKtNDO0QpMrp1Mqm1yyB%2FXnapper-2026-01-31-11.47.45.png?alt=media&amp;token=e3a7fe21-96e4-4cb7-a06f-e1fe4356b105" alt=""><figcaption><p>Annotations panel with filtering options</p></figcaption></figure>

### Available Actions

| Action | Description                        |
| ------ | ---------------------------------- |
| View   | See full annotation details        |
| Edit   | Modify title, date, or description |
| Delete | Remove the annotation              |

{% hint style="warning" %}
Google Update and System annotations cannot be edited or deleted—they are automatically maintained by SEO Utils.
{% endhint %}

### Filtering Annotations

Use the filters in the annotations panel to find specific annotations:

* **Date Range**: Filter by when annotations occurred
* **Type**: Show only custom, Google updates, or system annotations
* **Search**: Find annotations by title or description

## Google Algorithm Updates

SEO Utils automatically tracks confirmed Google algorithm updates and adds them as annotations. This helps you understand if traffic changes correlate with known algorithm updates.

{% hint style="success" %}
Google Update annotations are added automatically—you don't need to track them manually.
{% endhint %}

## Best Practices

* **Be specific**: Use clear titles like "Published new pricing page" instead of "Content update"
* **Add context**: Use the description field to include links or additional details
* **Annotate promptly**: Add annotations when you make changes, not weeks later when you've forgotten the details
* **Review regularly**: When analyzing performance drops or gains, check annotations first to understand what changed


# Topic Clusters

Topic Clusters is an AI-powered feature that groups semantically related search queries together, allowing you to analyze their collective performance and identify content opportunities at scale. By leveraging the [Embedding Database](/guide/embedding-database), this feature goes beyond simple keyword matching to understand the actual meaning and intent behind queries.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5c10bef4f945ccd81d22657da6e407519d354a4d%2FXnapper-2025-08-28-21.55.51.png?alt=media" alt=""><figcaption></figcaption></figure>

## Why Use Topic Clusters?

Traditional keyword analysis looks at queries individually, missing the bigger picture of how related searches contribute to your overall performance. Topic Clusters solves this by:

* **Revealing Hidden Patterns**: Discover groups of queries that share semantic meaning but use different words
* **Measuring Topic Performance**: See aggregated metrics (clicks, impressions) for entire topic areas
* **Identifying Content Gaps**: Find clusters of queries where you're underperforming
* **Streamlining Optimization**: Focus on improving entire topics rather than individual keywords
* **Understanding User Intent**: Group queries by what users actually mean, not just what they type

## Prerequisites

Before you can create topic clusters, you need to set up the embedding system:

### Step 1: Enable Embedding Database

1. Navigate to **Settings** → **Embedding** in the left sidebar
2. Toggle on **"Enable Embeddings"** master switch
3. Under **Google Search Console Queries**, ensure it's enabled
4. Select an embedding model (see [Choosing the Right Model](/guide/embedding-database#how-to-choose-the-right-model))
5. Click **"Update settings"**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-377f78a2675d15b886abdfacb08885de75f43c5b%2FXnapper-2025-08-27-21.47.02.png?alt=media" alt=""><figcaption><p>Enable embeddings for Google Search Console Queries</p></figcaption></figure>

### Step 2: Generate Query Embeddings

1. Go to **Google Search Console > Properties** in the left sidebar
2. Select your property
3. Navigate to the **Settings** tab

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ae88c7c815bb62184db983041cca301a226ec1d5%2FXnapper-2025-08-28-22.53.40.png?alt=media" alt="" width="563"><figcaption><p>Go to Property Settings page</p></figcaption></figure>

4. Scroll down to the **"Query Embeddings"** section
5. Click **"Generate Embeddings"** to process all your queries

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3920e35582d74c3f96f23697bf197e225acff0cd%2FXnapper-2025-08-28-22.52.59.png?alt=media" alt=""><figcaption><p>Generate embeddings for your search queries</p></figcaption></figure>

{% hint style="info" %}
**Auto-Embed New Queries**: Toggle this on to automatically generate embeddings when new search queries are synced from Google Search Console, ensuring your clusters stay up-to-date.
{% endhint %}

The embedding process runs in the background. Processing time depends on:

* Number of queries (1,000 queries ≈ 1-2 minutes)
* Selected model (local models are slower but free)
* Your computer's specifications

## Creating Topic Clusters

Once embeddings are generated, you can start creating clusters:

### Step 1: Access Topic Clusters

1. Navigate to your GSC property's **Insights** page
2. Scroll down to the **Topic Clusters** card
3. Click **"Create Cluster"** to begin

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-82ab9f3bb80169af9f727b879ed95f4f7c720025%2FXnapper-2025-08-28-22.55.43.png?alt=media" alt=""><figcaption><p>Topic Clusters card</p></figcaption></figure>

### Step 2: Search for Related Queries

1. **Enter Topics**: Type one or more seed topics to find similar queries
   * Single topic: Finds queries similar to that specific topic
   * Multiple topics: Finds queries similar to the centroid (average) of all topics
2. **Set Similarity Threshold**: Adjust the threshold to control how closely queries must match
   * Higher values (0.8-0.9): Stricter matching, fewer but more relevant results
   * Lower values (0.6-0.7): Broader matching, more results with varying relevance
   * See [Understanding Similarity Scores](/guide/embedding-database#understanding-similarity-scores) for details
3. **Click Search**: SEO Utils will return all semantically related queries

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-902f695373e2e1a63a2992822dd6cc0f965bb6af%2FXnapper-2025-08-27-22.04.18.png?alt=media" alt=""><figcaption><p>Search for semantically similar queries using AI</p></figcaption></figure>

### Step 3: Select Queries

Review the search results and select queries to include in your cluster:

* **Individual Selection**: Click checkboxes for specific queries
* **Select All on Page**: Use the header checkbox to select visible queries
* **Select All Results**: Click "Select all X queries" to include all matching queries across pages
* **Review Similarity Scores**: Higher scores indicate stronger semantic relationships

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9d1f23c1d7f1dd475ae97ec606d011420768c147%2FXnapper-2025-08-28-22.58.08.png?alt=media" alt=""><figcaption><p>Select queries to include in your cluster</p></figcaption></figure>

### Step 4: Configure Cluster Details

After selecting queries, click **"Next"** to configure your cluster:

1. **Cluster Name**: Give your cluster a descriptive name (e.g., "SEO Best Practices", "Local Coffee Shops")
2. **Description** (Optional): Add notes about what this cluster represents
3. **Color**: Choose a color for visual identification in charts and reports

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a09ca5e77a38c66d98171531fd74c1e67968e1b1%2FXnapper-2025-08-28-22.58.55.png?alt=media" alt=""><figcaption><p>Configure your topic cluster details</p></figcaption></figure>

Click **"Create Cluster"** to save your new topic cluster.

## Managing Topic Clusters

### Viewing Cluster Performance

Once created, clusters appear in the Topic Clusters card, showing:

* **Total Clicks**: Aggregated clicks from all queries in the cluster
* **Total Impressions**: Combined visibility across all cluster queries

### Editing Clusters

Click on any cluster to:

* **Add/Remove Queries**: Refine your cluster by adjusting included queries
* **Update Details**: Change name, description, or color
* **Re-run Search**: Find new related queries with a different threshold

### Deleting Clusters

To remove a cluster:

1. Click on the cluster to open edit mode
2. Click the **"Delete"** button
3. Confirm deletion (this only removes the cluster, not the underlying queries)

### Exporting Cluster Data

Export your clusters for further analysis:

* **Download CSV**: Click the download button to export cluster metrics
* **PDF Reports**: Clusters appear in exported PDF Insights reports

## Advanced Features

### Multi-Model Flexibility

The embedding database stores vectors from different models separately, allowing you to:

* **Experiment with Models**: Try different embedding models to find the best for your content
* **Compare Results**: See how different models group your queries
* **Switch Without Loss**: Change models without losing previously generated embeddings

To switch models:

1. Go to **Settings** → **Embedding**
2. Select a different model for Google Search Console Queries
3. Generate new embeddings with the selected model
4. Create clusters using the new embeddings

### Managing Embeddings

Control your embedding data from the GSC Settings page:

* **View Status**: See how many queries have embeddings
* **Delete Embeddings**: Remove embeddings for a specific model to free space or start fresh

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-73f23a04d029cc9d0f012588c766547f7d4bf989%2FXnapper-2025-08-28-22.59.44.png?alt=media" alt=""><figcaption><p>Manage embedding data per model</p></figcaption></figure>

## Best Practices

### Choosing Seed Topics

* **Be Specific**: "coffee brewing methods" works better than just "coffee"
* **Use Natural Language**: Write topics as users would search
* **Combine Related Terms**: Use multiple seeds to capture topic variations
* **Consider Intent**: Mix informational, commercial, and navigational terms

### Setting Similarity Thresholds

Start with these recommended thresholds:

* **Tight Clusters (0.85-0.95)**: For very specific topics or branded queries
* **Balanced Clusters (0.75-0.85)**: Good for most content topics
* **Broad Clusters (0.65-0.75)**: For exploratory analysis or finding opportunities

### Organizing Clusters

* **Avoid Overlap**: Check that queries don't appear in multiple similar clusters
* **Create Hierarchies**: Build parent topics with broader themes, child clusters for specifics
* **Use Consistent Naming**: Develop a naming convention for easy identification
* **Document Purpose**: Use descriptions to explain each cluster's optimization goal

## Use Cases

### Content Gap Analysis

1. Create clusters for topics you want to rank for
2. Identify clusters with high impressions but low clicks
3. Analyze which queries need better content
4. Develop content strategies for entire topic areas

### Competitor Comparison

1. Build clusters around competitor brand terms
2. Find topics where competitors are mentioned
3. Identify opportunities to create comparison content
4. Track performance improvements over time

### Seasonal Planning

1. Create clusters for seasonal topics
2. Monitor performance trends throughout the year
3. Plan content calendars based on cluster seasonality
4. Optimize existing content before peak seasons

### User Intent Mapping

1. Group queries by search intent (informational, transactional, navigational)
2. Ensure content matches the dominant intent in each cluster
3. Identify intent gaps in your content strategy
4. Optimize conversion paths for each intent type

## Troubleshooting

### No Queries Found

* **Lower the threshold**: Try 0.6-0.7 for broader matching
* **Use different seed topics**: Try synonyms or related terms
* **Check embeddings**: Ensure queries have been embedded with the current model

### Too Many Irrelevant Queries

* **Increase threshold**: Use 0.85+ for stricter matching
* **Refine seed topics**: Be more specific with your search terms
* **Manual curation**: Remove irrelevant queries after initial search

### Embeddings Not Generating

* **Check model configuration**: Ensure the embedding model is properly selected
* **Verify API keys**: For cloud models, check API key validity
* **Local model issues**: Ensure Ollama is running and the model is downloaded


# Keyword Metrics

The **Keyword Metrics** feature enriches your Google Search Console queries with valuable SEO data like search volume, CPC, keyword difficulty, and competition metrics. You can also analyze SERP data to understand your competition better.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7ebe6d50861f4718ba0ac18e44bc393ef79f1d2b%2FXnapper-2025-08-31-21.42.18.png?alt=media" alt=""><figcaption><p>Keyword Metrics</p></figcaption></figure>

### Configure Keyword Metrics Settings

Before checking metrics, you need to configure the location and language settings. Navigate to your Search Console property settings and find the "Keyword Metrics" section.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2fb3ded33a3bf6d7e381840886b75adb877e9962%2FXnapper-2025-09-01-22.14.06.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

**Required Settings:**

* **Location:** Select your target country (e.g., United States). Pick a city, region or postal code instead to give the SERP analysis a more precise place.
* **Language:** Select the language of your queries (e.g., English).
* **Auto-check:** Toggle this on to automatically check metrics for new queries pulled from GSC

Only the locations and languages your keyword metrics source supports are listed.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4e825bd1bef7b529a4ba1b05978f02102defaedb%2Fgsc-keyword-metrics-settings.png?alt=media" alt=""><figcaption><p>Configure keyword metrics settings. (1) Location. (2) Language. (3) Auto-check</p></figcaption></figure>

### Check Keyword Metrics

Once configured, click the "**Check Metrics**" button to start checking metrics for your queries.

{% hint style="info" %}
**Cost Note:** DataForSEO won't charge for keywords without search volume data, so actual costs will be lower than the estimation. SEO Utils only checks metrics for queries with missing or outdated data.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-99badfc3774395b46ca9e8dfa577cea8975e734d%2FXnapper-2025-09-01-22.15.29.png?alt=media" alt="" width="563"><figcaption><p>Review estimated cost before checking</p></figcaption></figure>

{% content-ref url="/pages/9ZN2hqv3w3x3TElty4OK" %}
[Keyword Metrics Data Source](/guide/keyword-metrics-data-source)
{% endcontent-ref %}

### View Queries with Metrics

After checking completes, visit the "Keyword Metrics" page from the main dropdown to see your enriched query data.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d754bd7ce50a0ea83e10239c4615e0aff0eb582a%2FXnapper-2025-09-01-22.16.47.png?alt=media" alt="" width="563"><figcaption><p>Access Keyword Metrics page</p></figcaption></figure>

You can:

* Sort by any column (clicks, impressions, search volume, CPC, keyword difficulty)
* Filter using range filters for numeric values
* Search for specific queries

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7ebe6d50861f4718ba0ac18e44bc393ef79f1d2b%2FXnapper-2025-08-31-21.42.18.png?alt=media" alt=""><figcaption><p>Keyword metrics table with enriched data</p></figcaption></figure>

{% hint style="info" %}
You can click the **View** button on the table to see more columns.
{% endhint %}

### Analyze SERP Data

Click the "**Live SERP**" button next to any query to pull live SERP data. This shows the top-ranking pages for that keyword.

For deeper analysis, select SERP URLs and click "**Analyze SERP**" to view:

* **DR** (Domain Rating)
* **UR** (URL Rating)
* **RD** (Referring Domains)
* **Backlinks** count
* **Traffic** estimates
* **Ranked Keywords** count

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-40c21350dbdcc0fbe5c6396ebec4caf231bf2690%2FXnapper-2025-08-31-21.47.57.png?alt=media" alt=""><figcaption><p>SERP analysis showing competitor metrics</p></figcaption></figure>

This data helps you understand the competition level and identify opportunities to improve your rankings.


# SEO Tests

SEO Utils allows you to run controlled experiments to measure the impact of your SEO changes using real [Google Search Console data](/guide/google-search-console). The tool automatically tracks metrics like clicks, impressions, CTR, and rankings to help you make data-driven decisions.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5bda6d7de192b02507a8904894c663acce2f52ca%2FXnapper-2025-09-08-12.34.53.png?alt=media" alt=""><figcaption><p>SEO Tests: URL Switch Test.</p></figcaption></figure>

You can test whether your SEO changes actually improve performance before rolling them out across your entire site. The tool supports three different test types, each designed for specific testing scenarios.

### Test Types

SEO Utils supports three types of SEO tests:

1. **Time-based Test**: Compare performance before and after implementing a change
2. **URL Switch Test**: A/B test by alternating between two versions of the pages
3. **Split Test**: Run simultaneous tests on different page groups

### How to Create an SEO Test

To get started, head to the SEO Tests in the left sidebar. Then, click the Create Test button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0d1c2311e508f159b560537a39aab2db4a072ec9%2FXnapper-2025-09-08-12.35.59.png?alt=media" alt=""><figcaption><p>Access the SEO Tests tool in the left sidebar</p></figcaption></figure>

The test creation process has three steps. We'll go through each step and explain the different fields for each test type.

#### Step 1: Configure Test

First, you need to set up the basic test information.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-649d3556e5a70f8b5f04bb537d9dd41df5a9099c%2FXnapper-2025-09-08-12.37.51.png?alt=media" alt=""><figcaption><p>Configure your test settings</p></figcaption></figure>

**Common Fields (All Test Types):**

* **Domain**: Select the Google Search Console property you want to test
* **Test Type**: Choose between Time-based, URL Switch, or Split Test
* **Test Name**: Give your test a descriptive name
* **Description**: Optional field to add more context about your test
* **Hypothesis**: Clearly state what you expect to happen

**Test Type Specific Fields:**

For **Time-based Tests**:

* **Change Implemented Date**: When the SEO change will be implemented. This date separates the "before" and "after" periods for comparison

For **URL Switch Tests**:

* **Switch Interval**: How often to switch between versions (1-30 days)
* **Starting Version**: Which version to show first (original or variant)

For **Split Tests**:

* **Traffic Split**: Percentage of traffic for the variant group (10-90%)

{% hint style="info" %}
Your hypothesis should be specific and measurable. For example: "Adding FAQ schema will increase CTR by 10%" instead of "Schema will help rankings".
{% endhint %}

#### Step 2: Select Pages

Next, you'll select which pages to include in your test.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6dc904211b5fc2a56605e68eedd0b7bdb44ac339%2FXnapper-2025-09-08-13.03.25.png?alt=media" alt=""><figcaption><p>Select and validate pages for testing</p></figcaption></figure>

**Page Selection Process:**

1. **Add Filters**: Use filters to find pages that match your criteria
2. **Date Range**: Select the date range for baseline data validation
   * This ensures your selected pages have enough historical data
   * Recommended: Use at least 30 days of baseline data
3. **Find Pages**: Click to search for matching pages in your GSC data

**For Time-based Tests:**

* You can select or remove pages using checkboxes

**For URL Switch Tests:**

* Configure URL pairs (original vs. alternate versions)
* Example: `/product` (original) vs. `/product-v2` (alternate)
* The tool will automatically switch between these URLs based on your interval

**For Split Tests:**

* Pages are automatically divided into Control and Variant groups
* You can manually move pages between groups if needed
* The tool ensures both groups have similar baseline performance

{% hint style="success" %}
**Tip**: For Split Tests, SEO Utils automatically balances the groups to ensure similar baseline metrics, reducing test bias. If the current split isn't well-balanced, use the **Shuffle** button to generate a different distribution of pages between control and variant groups until you find a balanced split.
{% endhint %}

#### Step 3: Schedule Test

Finally, set when your test should run.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-00bf7c557778af7efd678cb2a8fa39558cb66283%2FXnapper-2025-09-08-13.05.15.png?alt=media" alt=""><figcaption><p>Schedule your test duration</p></figcaption></figure>

**Scheduling Fields:**

* **Start Date**: When to begin tracking test metrics
* **End Date**: Optional - when to stop the test (leave empty for ongoing tests)

For **Time-based Tests** only:

* **Change Implemented Date**: When you plan to implement (or have implemented) the SEO change
  * This separates the "before" and "after" periods
  * Must be between the start and end dates

{% hint style="warning" %}
Allow at least 2-4 weeks for your test to gather statistically significant data. Google Search Console data has a 2-3 day delay, so factor this into your timeline.
{% endhint %}

### When to Use Each Test Type

#### Time-based Test

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-63ca26799fa5fbdb58898196f07ea225c89b6331%2FXnapper-2025-09-08-13.10.17.png?alt=media" alt=""><figcaption><p>Time-based Test</p></figcaption></figure>

**Use when:**

* Making site-wide changes (like updating all title tags)
* Testing changes that can't be reversed easily
* You want to compare "before" and "after" performance
* Historical comparison is more important than simultaneous testing

**Example scenarios:**

* Adding schema markup to all product pages
* Changing the URL structure site-wide
* Implementing Core Web Vitals improvements

#### URL Switch Test

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5bda6d7de192b02507a8904894c663acce2f52ca%2FXnapper-2025-09-08-12.34.53.png?alt=media" alt=""><figcaption><p>URL Switch Test</p></figcaption></figure>

**Use when:**

* You have two versions of the same page
* You can programmatically switch between versions
* You want to minimize the impact of external factors
* Testing significant page redesigns

**Example scenarios:**

* Testing two different page layouts
* Comparing long-form vs. short-form content
* Testing different internal linking structures

#### Split Test

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-88dc56507cb7d0374e7db79acffb32ea08b4e9b0%2FXnapper-2025-09-08-13.11.52.png?alt=media" alt=""><figcaption></figcaption></figure>

**Use when:**

* You have many similar pages (like product or category pages)
* You want to test changes on a subset before full rollout
* You need results faster than sequential testing
* Testing template-level changes

**Example scenarios:**

* Testing new title tag templates on product pages
* Adding FAQ sections to half of your blog posts
* Testing different meta description formats

### Understanding Statistical Terms

SEO Utils uses statistical analysis to ensure your test results are reliable. Here are the key terms:

#### 1. Confidence Score / Statistical Significance

**What it means**: The probability that the observed difference is real and not due to random variation.

* **95% confidence** = Only 5% chance the results are due to randomness
* **99% confidence** = Only 1% chance the results are due to randomness

**How to use it**: Wait for at least 95% confidence before making decisions based on test results.

#### 2. P-Value

**What it means**: The probability of seeing these results if there was actually no difference between versions.

* **p < 0.05**: Statistically significant (less than 5% chance of random occurrence)
* **p < 0.01**: Highly significant (less than 1% chance of random occurrence)

**How to use it**: A p-value below 0.05 indicates your results are statistically significant.

#### 3. Z-Score

**What it means**: How many standard deviations the test results are from the mean. It measures the magnitude of difference.

* **|z| > 1.96**: Significant at 95% confidence level
* **|z| > 2.58**: Significant at 99% confidence level

**How to use it**: Larger absolute z-scores indicate stronger evidence of a real difference.

#### 4. Uplift

**What it means**: The percentage change in performance between control and variant groups.

* **Positive uplift**: Variant performs better than control
* **Negative uplift**: Control performs better than variant

**Calculation**: `(Variant Metric - Control Metric) / Control Metric × 100`

{% hint style="warning" %}
**Important**: High uplift doesn't always mean statistical significance. Always check the confidence score before making decisions.
{% endhint %}

### Interpreting Results Correctly

#### When to Trust Your Results

✅ **Reliable results when:**

* Statistical significance is 95% or higher
* The test has run for at least 2-4 weeks
* You have sufficient sample size (usually 1000+ clicks per group)
* No major external events occurred during the test

⚠️ **Be cautious when:**

* Significance is between 90-95%
* Sample size is small (< 500 clicks)
* Test duration is less than 2 weeks
* Major algorithm updates occurred during testing

❌ **Don't trust results when:**

* Significance is below 90%
* Very small sample size (< 100 clicks)
* Test ran for less than a week
* Site had technical issues during the test

### Monitoring Test Progress

SEO Utils provides real-time monitoring features:

1. **Daily Metrics Updates**: See how metrics change day by day
2. **Trend Charts**: Visualize performance trends over time
3. **Pause/Resume Capability**: Exclude problematic periods from analysis
4. **Export Options**: Download detailed results for further analysis

{% hint style="info" %} <mark style="color:blue;">**Pro Tip**</mark>: Check your test results weekly, but avoid making decisions too early. Early results can be misleading due to small sample sizes.
{% endhint %}

### Best Practices

1. **Define clear hypotheses**: Be specific about what you expect to change and by how much
2. **Ensure sufficient sample size**: Include enough pages and traffic for reliable results
3. **Run tests for adequate duration**: At least 2-4 weeks, accounting for weekly patterns
4. **Monitor external factors**: Note any algorithm updates or seasonal changes during your test
5. **Document your changes**: Keep detailed records of exactly what was changed

{% hint style="success" %}
SEO Tests integrate directly with your [Google Search Console data](/guide/google-search-console), so there's no need for additional tracking setup. Just connect your GSC account and start testing!
{% endhint %}


# Indexing Dashboard

The **Indexing Dashboard** gives you a complete view of how Google indexes your website. It uses the Google URL Inspection API to check each page individually, tracks status changes over time, and shows you exactly which pages are indexed, which aren't, and why.

The dashboard has **three tabs**:

* **Overview** — High-level indexing status, trends, and recent movements
* **Visual Diagnostics** — Charts that expose structural site issues (velocity, directory health, crawl budget, internal links, funnel)
* **Log Analyzer** — A combined data table merging GSC data, internal links, and server log hits with actionable insights

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FYXl3apkSdO8iAevHTp1a%2FXnapper-2026-04-16-16.00.54.png?alt=media&amp;token=2ad4cc7f-80f4-462d-bcd5-917f703f97be" alt=""><figcaption><p>Indexing Dashboard with three tabs: Overview, Visual Diagnostics, and Log Analyzer</p></figcaption></figure>

***

## Getting Started

To use the Indexing Dashboard, you need a Google Search Console property connected to SEO Utils with at least one sitemap added.

{% stepper %}
{% step %}
**Connect a GSC Property**

If you haven't already, connect your Google Search Console property using either a **Google OAuth Token** or a **Google Service Account**. See the [Google Search Console setup guide](/guide/google-search-console) for instructions.
{% endstep %}

{% step %}
**Add a Sitemap (if needed)**

When you connect a GSC property, SEO Utils automatically detects and adds sitemaps from Google Search Console. If sitemaps were found, you can skip this step.

If no sitemaps were detected, or you want to add a different sitemap, navigate to **Sitemaps** from the property dropdown and add your sitemap URL (e.g., `https://yoursite.com/sitemap.xml`). SEO Utils will automatically fetch URLs from your sitemap daily.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FBB3EzzBvPo8gQlEaiRDn%2FXnapper-2026-04-16-16.02.04.png?alt=media&amp;token=40de28ce-fd9a-43a0-b098-f2efa9f07abe" alt="" width="563"><figcaption><p>Add a sitemap</p></figcaption></figure>
{% endstep %}

{% step %}
**Open the Indexing Dashboard**

Select your property from the dropdown, then click **Indexing** in the navigation menu. The dashboard will begin collecting data automatically.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
On first visit, the dashboard shows "Based on 0/N URLs inspected" because no URLs have been inspected yet. Click **Run Initial Scan** in the top-right to start the first inspection batch, or wait for the automatic inspection to run (every 4 hours).
{% endhint %}

***

## Shared Controls

These controls appear at the top of the dashboard and apply across all three tabs:

### Date Filter

The date dropdown in the top-right controls the time range for the chart, table impressions/clicks, movements, funnel, and velocity data.

Available presets: **7 days, 14 days, 30 days, 2 months, 3 months, 6 months, 12 months**. The default is 30 days.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FrxuUJagTgb2twhwzzkq2%2FXnapper-2026-04-16-16.15.20.png?alt=media&amp;token=0e9bd141-9482-47fb-871b-6bce1d7a76ee" alt="" width="563"><figcaption><p>Date range filter and the settings icon.</p></figcaption></figure>

### Sitemap Errors Banner

If any sitemap has a fetch error (e.g., HTTP 404, timeout), a dismissible banner appears at the top showing the errors. This is visible on all tabs.

### Settings

Click the **cog icon** in the top-right to open the property's settings page at its **Indexing API** section. See the [Settings](#settings) section below for details.

***

## Tab 1: Overview

The Overview tab shows your high-level indexing status, historical trends, and recent status changes.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fg2XnSGJUtvwjAUkoU5CU%2FXnapper-2026-04-16-16.16.57.png?alt=media&amp;token=adcdb0fa-f7dc-43eb-a9ae-891ae3dc749a" alt=""><figcaption><p>Overview tab with status tabs, trend chart, and pages table</p></figcaption></figure>

### Status Tabs & Chart

Three tabs at the top — **All**, **Indexed**, **Not indexed** — filter both the chart and pages table. Use the **Show %** toggle to switch between counts and percentages.

When you select **Not indexed**, clickable sub-status chips appear (e.g., "Crawled - currently not indexed", "Not found (404)") to drill down by reason. Select multiple chips to combine filters.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FfHa3PyQ5CBogVld5eiBC%2FXnapper-2026-04-16-16.17.45.png?alt=media&amp;token=5e87c541-6068-4a82-ba2c-26999ac5fdae" alt=""><figcaption><p>Sub-status chips filter the chart and table by specific indexing reason</p></figcaption></figure>

The **Indexing Overview Chart** shows a stacked bar trend over time — green for indexed, orange/multi-color for not indexed sub-statuses.

### Pages Table

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FdOuKOjPFPNDX7ts26H5w%2FXnapper-2026-04-16-18.55.30.png?alt=media&amp;token=ffce6ad2-ae61-4323-a0d9-93ffd26fc8d0" alt=""><figcaption><p>Pages table with filters, bulk actions, and per-URL indexing details</p></figcaption></figure>

Shows every URL from your sitemap with columns for **URL**, **Clicks**, **Impressions**, **Status** (coverage state badge), **Last Crawl**, **Rich Results**, and **Last Inspection**.

**Filters:** Page URL search, Status, Content Group, and "Pages at risk of de-indexing" (indexed pages not crawled in 90+ days). Click **Advanced** for Clicks/Impressions range filters and Last Crawl date picker.

**Actions:** Click **...** on any row to **Check Index** (re-inspect via API) or **Request Indexing** (submit to Google). Select multiple rows for bulk Check Index or Submit Index.

### Recent Movements

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FXI0D84bgLclfL9iHLTJx%2FXnapper-2026-04-16-19.00.24.png?alt=media&amp;token=48a91da7-dcd9-40b9-9da2-e080e2bda64b" alt=""><figcaption><p>Recent Movements tracking status changes across coverage, robots, and canonical fields</p></figcaption></figure>

Tracks indexing status changes over time across three tabs:

* **All Movements** — Every status change with a Type column (Coverage, Indexing, Robots, Canonical)
* **Indexing Changes** — Only coverage and indexing state changes
* **Recently Published & Not Indexed** — New URLs still not indexed within the date range

***

## Tab 2: Visual Diagnostics

The Visual Diagnostics tab shows five charts that help you identify structural indexing problems at a glance. Data is loaded only when you navigate to this tab.

### Internal Link Crawler

The same crawler feeds the [Internal Links](/guide/google-search-console/internal-links) tool, which turns this data into specific link suggestions.

At the top of the Diagnostics tab, a **Crawler Progress Card** shows the status of the internal link crawler:

* **Not run yet** — "Internal link crawler has not been run yet." with a **Run Link Crawler** button
* **Running** — "Crawling... X/Y URLs" with live progress updates
* **Completed** — "Last crawl: Apr 5, 2026 — 2000 URLs"

Click **Run Link Crawler** to start a manual crawl. The crawler uses headless Chrome to visit each sitemap URL, extract all internal `<a>` links, and store the link graph (anchor text, rel attributes, follow/nofollow). This data powers the scatter plot and the inlink counts in the Log Analyzer table.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FsOLeIKnYJa8aaPjL7HJG%2FXnapper-2026-04-16-19.03.02.png?alt=media&amp;token=ff6f7448-95af-4d4e-a249-ca89ba53eb21" alt=""><figcaption><p>Crawler progress card showing last crawl date and Run Link Crawler button</p></figcaption></figure>

{% hint style="info" %}
The crawler processes up to **2,000 URLs per cycle**, prioritizing uncrawled URLs first. For larger sites, the full site is covered over multiple weekly cycles. You can configure the crawl rate and schedule in [Settings](#internal-link-crawler-settings).
{% endhint %}

### Indexing Velocity

This chart answers: **"Is Google getting faster or slower at indexing my new content?"**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F3oxU6U2WI0CeGL9YIi5E%2FXnapper-2026-04-16-19.19.45.png?alt=media&amp;token=a9e151a3-cf89-43c9-8273-f07eb35227a3" alt=""><figcaption><p>Indexing Velocity chart showing median time-to-index with P90 band over weeks</p></figcaption></figure>

* **Blue line** — Median (P50) time-to-index in days
* **Red shaded area** — 90th percentile (P90) band, showing how long the slowest 10% of URLs take

The X-axis shows weeks. Each data point represents all URLs published that week and how long they took to reach "Submitted and indexed" status.

{% hint style="info" %}
This is a **forward-looking metric**. It only tracks URLs discovered after you set up SEO Utils, so the data won't include historical pages that existed before your first sitemap sync. New users will see an empty state: *"Awaiting new content. Velocity tracking begins when you publish new URLs to your sitemap."*
{% endhint %}

### Directory Health

Horizontal stacked bars showing the **indexed vs. not-indexed ratio** for each subdirectory of your site.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FVzsxOMrHtGMMk9A5JPOs%2FXnapper-2026-04-16-19.20.20.png?alt=media&amp;token=e4b05dd1-f89f-4994-9867-ebc63053380b" alt=""><figcaption><p>Directory Health chart showing indexed percentage per directory with green/red stacked bars</p></figcaption></figure>

* **Green** = indexed percentage
* **Red** = not-indexed percentage
* Shows the **top 10 directories** by URL count, with an "Other" bucket for the rest
* Root-level pages (like `/about`, `/contact`) are grouped into the `/` bucket

Use the **Group By** dropdown (top-right of the chart) to switch between:

* **Directory Path (Auto)** — Groups by first URL path segment (default)
* **Content Groups** — Groups by the content groups you've created in the [Insights tab](/guide/google-search-console) (using URL filters or manual page selection)

### Crawl Budget by Directory

A bar chart showing how **Googlebot allocates its crawl budget** across your site's directories.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FIHpy2rnrjiaVUyE65SBT%2FXnapper-2026-04-16-19.27.25.png?alt=media&amp;token=3793180b-38f0-4061-a8b6-b18efd8cd3fe" alt=""><figcaption><p>Crawl Budget chart showing Googlebot hit distribution by directory</p></figcaption></figure>

This chart is only available when you have a **log report linked** to this domain. If no log report is linked, you'll see: *"Link a log report to see crawl budget allocation by directory."*

{% hint style="success" %}
**The "aha moment"**: Compare the Directory Health chart with the Crawl Budget chart side by side. If `/search/` is only 15% indexed but consumes 75% of all Googlebot hits, you've found a crawl trap that needs fixing.
{% endhint %}

### Internal Links vs. Indexation

A scatter plot that shows the **correlation between internal link count and indexation success**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FijT3QKQmSJFpAKZkgQb2%2FXnapper-2026-04-16-19.27.59.png?alt=media&amp;token=8e005905-b025-4eb5-b31f-248ed64ac038" alt=""><figcaption><p>Scatter plot showing internal links vs indexation with two horizontal bands</p></figcaption></figure>

* **X-axis** — Number of internal inlinks (from the local crawler)
* **Y-axis** — Two bands: "Indexed" (top) and "Not Indexed" (bottom)
* **Green dots** = indexed URLs, **Red dots** = not-indexed URLs
* Dot sizes are uniform (no bubble chart)

You'll typically see orphan pages (low inlinks) clustered in the "Not Indexed" band, visually proving that pages need internal links to get indexed.

To act on what this chart shows, open [Internal Links](/guide/google-search-console/internal-links) — its **Orphans** list names the pages, and a run proposes the sentence to link each one from.

When log data is available, a **Hide Zero-Hit Pages** toggle appears to filter out URLs that Googlebot hasn't visited.

{% hint style="warning" %}
This chart requires the internal link crawler to have run. If the crawler hasn't been run yet, you'll see: *"Run the internal link crawler to see this chart."*
{% endhint %}

### Indexing Funnel

A horizontal bar chart showing **where your URLs currently sit** in the indexing pipeline. Each bar's width is proportional to the total sitemap count, so you can instantly see the distribution.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F7X1K5NfIgiN90TNTXVv5%2FXnapper-2026-04-16-19.28.27.png?alt=media&amp;token=23747360-ef5e-4d85-beed-231b83298621" alt=""><figcaption><p>Indexing Funnel showing distribution of URLs across pipeline stages with color-coded bars</p></figcaption></figure>

| Stage           | Color  | What it means                                                                     |
| --------------- | ------ | --------------------------------------------------------------------------------- |
| **In Sitemap**  | Gray   | Total URLs from your sitemap (baseline — always 100%)                             |
| **Discovered**  | Amber  | URLs Google knows about but hasn't crawled yet — may need better internal linking |
| **Crawled**     | Red    | URLs Google crawled but rejected — content quality or technical issues            |
| **Indexed**     | Green  | Successfully indexed and eligible to appear in search                             |
| **Impressions** | Violet | Indexed pages that received at least 1 impression in the selected period          |

Each bar shows the count and percentage of total. Hover over any bar for a description of what the stage means.

**Intentional Exclusions** are listed below the bars as a text summary:

* **Blocked by robots.txt** — URLs your robots.txt prevents Google from crawling
* **Excluded (noindex / duplicate canonical)** — URLs intentionally excluded from the index

{% hint style="info" %}
A large red "Crawled" bar relative to the green "Indexed" bar means Google is visiting your pages but rejecting the content. This is usually the most actionable insight — check those pages for thin content, duplicate issues, or soft 404s.
{% endhint %}

***

## Tab 3: Log Analyzer

The Log Analyzer tab combines data from **three sources** into a single actionable table:

1. **GSC URL Inspection API** — Coverage state for each URL
2. **Internal Link Crawler** — Inlink count per URL
3. **Server Log Files** — Googlebot hit counts from your server logs

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FoNAJnoLtxIvu4yXdVqS8%2FXnapper-2026-04-16-19.29.02.png?alt=media&amp;token=96c9e952-f8f9-4ec7-a714-a3ea3851a756" alt=""><figcaption><p>Log Analyzer table showing URL, GSC Status, Inlinks, Log Hits, and Actionable Insight columns</p></figcaption></figure>

### Columns

| Column                 | Source             | Description                                                                  |
| ---------------------- | ------------------ | ---------------------------------------------------------------------------- |
| **URL**                | Any                | The page path (click to open in browser)                                     |
| **GSC Status**         | URL Inspection API | Coverage state badge. Shows **"Not in Sitemap"** for URLs found only in logs |
| **Inlinks**            | Local Crawler      | Internal link count. Shows "—" if crawler hasn't run                         |
| **Log Hits (30d)**     | Server Logs        | Googlebot hit count. Shows "—" if no log report linked                       |
| **Actionable Insight** | Computed           | Color-coded badge based on the rules below                                   |

### Actionable Insights

Each URL gets an automatically computed insight based on its data:

| Insight              | Color  | Condition                                                                     |
| -------------------- | ------ | ----------------------------------------------------------------------------- |
| **Healthy**          | Green  | URL is indexed                                                                |
| **High Crawl Waste** | Red    | High log hits + not indexed (Googlebot keeps visiting but Google won't index) |
| **Low Crawl Waste**  | Orange | Moderate log hits + not indexed                                               |
| **Orphan Page**      | Amber  | Few or zero internal links + not indexed (needs internal links)               |
| **Not in Sitemap**   | Purple | URL found in server logs but not in your sitemap                              |

The thresholds for "high" and "low" crawl waste and the orphan inlink threshold are configurable in [Settings](#actionable-insight-thresholds).

### Filters

* **URL search** — Text search across all URLs
* **GSC Status** — Faceted filter (select one or more coverage states, or "Not in Sitemap")
* **Insight** — Faceted filter (Healthy, High Crawl Waste, Orphan, etc.)
* **Inlinks** — Range filter (from/to)
* **Log Hits** — Range filter (from/to)

### CSV Export

Click the **Export CSV** button to download the full merged dataset as a CSV file. The export includes all columns and all rows (not just the current page).

{% hint style="info" %}
The Log Analyzer table works with whatever data is available. If you haven't run the crawler, the Inlinks column shows "—". If no log report is linked, the Log Hits column shows "—". The table is still useful with just GSC data alone.
{% endhint %}

***

## Settings

Click the **cog icon** in the top-right to open the property's settings page, where these settings live as cards in the sidebar. Each one is edited in exactly one place.

| Card                   | Group    | Covers                                                |
| ---------------------- | -------- | ----------------------------------------------------- |
| **Indexing API**       | Data     | Auto-submit and the resubmission cooldown             |
| **URL normalization**  | Crawling | Trailing slashes and which query parameters to keep   |
| **Insight thresholds** | Crawling | The Log Analyzer's crawl-waste and orphan sensitivity |
| **Link crawler**       | Crawling | Crawl rate, Chrome tabs and the auto-crawl schedule   |

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FVIZPImGC5ZrYSZ2QAXH5%2FXnapper-2026-04-16-19.29.46.png?alt=media&amp;token=91588804-584f-47d5-ba0d-c5cbf7e6c075" alt="" width="563"><figcaption><p>Indexing Settings modal with auto-submit, normalization, thresholds, and crawler settings</p></figcaption></figure>

### Auto Submit for Indexing

| Setting                      | Description                                                                                                                                 |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **Auto Submit for Indexing** | When enabled, automatically submits not-indexed URLs to Google via the Indexing API. URL inspection always runs regardless of this setting. |
| **Resubmission Cooldown**    | Minimum days between resubmission attempts for the same URL. Default: 7 days. Only shown when auto-submit is on.                            |

### URL Normalization

These settings control how URLs are normalized for matching across GSC data, server logs, and crawler results.

| Setting             | Description                                                                                                                                                                       |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Trailing Slash**  | How to handle trailing slashes: **Follow Sitemap** (default — strips trailing slashes), **Always Add**, or **Always Strip**                                                       |
| **Keep Parameters** | Query parameters to preserve (e.g., `p`, `page`, `id`, `lang`). Type a parameter name and press Enter to add it as a tag. All other parameters (including UTM tags) are stripped. |

The **Recalculate Normalized Paths** button recomputes all normalized paths when you change these settings. This affects how URLs are joined across the three data sources.

### Actionable Insight Thresholds

Configure the sensitivity of the Log Analyzer's insight engine:

| Setting                       | Default | Description                                                          |
| ----------------------------- | ------- | -------------------------------------------------------------------- |
| **High Crawl Waste (hits >)** | 20      | Log hits above this trigger "High Crawl Waste" for not-indexed pages |
| **Low Crawl Waste (hits >)**  | 5       | Log hits above this trigger "Low Crawl Waste" for not-indexed pages  |
| **Orphan Page (inlinks <)**   | 2       | Pages with fewer inlinks than this are flagged as orphan pages       |

### Internal Link Crawler Settings

| Setting                 | Default | Description                                                                                          |
| ----------------------- | ------- | ---------------------------------------------------------------------------------------------------- |
| **Requests per Second** | 1       | How fast the crawler visits your pages. Range 1–3. Keep it low to avoid overwhelming your server.    |
| **Max Chrome Tabs**     | 3       | How many pages load at once, within the rate above. Range 1–3.                                       |
| **Auto-Crawl Schedule** | Weekly  | How often the crawler runs automatically: **Weekly**, **Bi-weekly**, **Monthly**, or **Manual Only** |

{% hint style="warning" %}
The crawler uses headless Chrome to render pages, so it captures links added by JavaScript. Throughput is governed by the request rate, not the tab count: at the default of 1 request per second it processes about **60 pages per minute**, so a 2,000-URL batch takes roughly half an hour.
{% endhint %}

***

## How It Works Behind the Scenes

### URL Inspection

SEO Utils automatically inspects your URLs using the Google URL Inspection API every 4 hours. URLs are prioritized in this order:

1. **Never inspected** — New URLs from sitemap
2. **Content updated** — URLs where the sitemap lastmod changed
3. **Not indexed** — URLs that aren't indexed yet
4. **Indexed** — Re-checked on a rotating basis (lowest priority)

{% hint style="info" %}
Google enforces a limit of **2,000 URL Inspection API requests per day per property**. For sites with more URLs, SEO Utils automatically spreads inspections across multiple days.
{% endhint %}

### URL Normalization Pipeline

To join data from GSC (full URLs), server logs (request paths only), and the crawler (full URLs), all URLs pass through a normalization pipeline:

1. Strip protocol and hostname → `/blog/post`
2. Standardize trailing slashes (based on your setting)
3. Remove tracking parameters (UTM, gclid, fbclid, etc.)
4. Keep only configured structural parameters
5. Lowercase the path

This produces a `normalized_path` used for exact-match joins across all three data sources.

### Googlebot Verification

When importing server logs, SEO Utils verifies Googlebot requests using **Google's officially published IP ranges** (CIDR blocks). This prevents spoofed Googlebot user agents from polluting your data. IP ranges are refreshed daily from Google's public endpoint.

***

## Troubleshooting

<details>

<summary><strong>Chart shows "No chart data available"</strong></summary>

The chart requires at least one inspection batch to complete. Either:

* Click **Run Initial Scan** in the top-right to start an immediate inspection
* Wait for the automatic inspection cycle (runs every 4 hours)

Chart data is generated from inspection results, so URLs must be inspected before the chart has data to display.

</details>

<details>

<summary><strong>Dashboard shows "Based on 0/N URLs inspected"</strong></summary>

This means URLs have been discovered from your sitemap but haven't been inspected yet. This is normal on first setup. Click **Run Initial Scan** or wait for the automatic cycle.

</details>

<details>

<summary><strong>"No sitemaps found" error</strong></summary>

Your property doesn't have a sitemap configured in SEO Utils. Navigate to **Sitemaps** from the property navigation and add your sitemap URL.

</details>

<details>

<summary><strong>Velocity chart is empty</strong></summary>

The velocity chart only tracks URLs discovered **after** you set up SEO Utils. If all your URLs were already in the sitemap when you first connected, the chart has no data to show. Publish new content to your sitemap and the chart will populate as those URLs get indexed.

</details>

<details>

<summary><strong>Scatter plot says "Run the internal link crawler"</strong></summary>

The Internal Links vs. Indexation chart requires crawl data. Go to the **Visual Diagnostics** tab and click **Run Link Crawler** at the top. The scatter plot will populate once the crawl completes.

</details>

<details>

<summary><strong>Crawl Budget chart says "Link a log report"</strong></summary>

The Crawl Budget chart requires server log data. Create a log report in the **Log Analyzer** section of the sidebar, import your server logs, and make sure the report's domain matches your GSC property domain.

</details>

<details>

<summary><strong>Log Analyzer columns show "—"</strong></summary>

A dash means no data is available from that source:

* **Inlinks showing "—"** → Run the internal link crawler
* **Log Hits showing "—"** → Link a log report with server log data for this domain

The table still works with partial data — you don't need all three sources to use it.

</details>

<details>

<summary><strong>Inspection seems slow</strong></summary>

Each URL requires a network call to Google's API. Large sites with hundreds or thousands of URLs may take several minutes to complete a full inspection cycle. This is normal.

</details>

<details>

<summary><strong>Quota exceeded — inspections stopped</strong></summary>

Google limits URL Inspection API to 2,000 requests per day per property. When the quota is reached, remaining URLs are scheduled for the next day. The dashboard shows partial data based on what was inspected.

</details>

<details>

<summary><strong>Clicks and Impressions show 0 for all URLs</strong></summary>

Clicks and impressions come from Google Search Console performance data, which requires the GSC data sync to be running. Make sure your property has synced data (check the Performance page). The indexing dashboard joins with the performance data for the selected date range.

</details>


# Internal Links

**Internal Links** finds the pages on your site that would benefit from more links pointing at them, then proposes a specific sentence on a specific page to add each link to. You review every suggestion, and nothing reaches your site until you accept it.

The tool works in three stages:

* **Read your pages** — a crawler visits the URLs in your sitemap and records every link, where it sits on the page, and the text it could suggest links from
* **Prepare the topics** — each page becomes a vector, so the tool can tell which pages cover the same subject
* **Find the links** — for each page you choose, the closest pages are read again and one sentence per link is proposed, with the exact words to turn into the link

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fz2dFd0w7cGASJFoBZXBu%2FXnapper-2026-09-22-19.08.43.png?alt=media&amp;token=6256b62a-99b3-43f0-bc22-a0b152fb19c4" alt=""><figcaption><p>The Internal Links page showing the Opportunities and Suggestions tabs</p></figcaption></figure>

{% hint style="info" %}
Only links in the **main content** count as body links. Menus, headers, footers and sidebars are recorded but never counted as an editorial link, because they appear on every page and tell search engines nothing about a specific page.
{% endhint %}

***

## What You Need Before You Start

| Requirement                                                          | Why it is needed                                    | Cost                                                |
| -------------------------------------------------------------------- | --------------------------------------------------- | --------------------------------------------------- |
| A connected Google Search Console property with at least one sitemap | The crawler reads the URLs listed in your sitemaps  | Free                                                |
| **Embeddings** turned on for Internal Links                          | Lets the tool tell which pages cover the same topic | A few cents for a whole site, once per changed page |
| A **TypeSafe API key**                                               | Chooses the sentence and the words to link          | A few cents per run                                 |
| A **WordPress connection** (optional)                                | Writes accepted links into your pages automatically | Free                                                |

Without a TypeSafe key you can still crawl your site, embed your pages, and read every list in the Opportunities tab. Only the link suggestions need it.

***

## Getting Started

When you open Internal Links on a property that has never been crawled, the page shows three numbered steps instead of empty tables. Work down them in order.

{% stepper %}
{% step %}

#### Read your pages

Click **Run the crawler**. The crawler opens each URL in your sitemap and records its links and its text.

Progress appears at the top of the page as **"Crawling… 24/99 URLs"**. The crawler paces itself so it never overloads your server — at the default of one request per second, expect roughly **60 pages per minute**, so a 2,000-page site takes about half an hour.

You can leave the page while it runs.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F6b3OqlfmycZVC5JQw6vR%2FXnapper-2026-09-22-19.18.35.png?alt=media&amp;token=93b9123c-b0a7-43ae-ac10-25aeda3396c4" alt=""><figcaption><p>The three-step get-started panel on a property that has not been crawled</p></figcaption></figure>
{% endstep %}

{% step %}

#### Prepare the topics

If embeddings are not yet on for Internal Links, click **Choose a model** and turn them on.

Go to **Settings → Embeddings**, enable the master switch, then enable **Internal Links pages** and pick a model. Your choice here is independent of the model used for Search Console queries — the two features never share vectors.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FKjzG0IbTcSOgaxia0FIH%2FXnapper-2026-09-22-19.11.22.png?alt=media&amp;token=45f103c0-6f32-40b2-8bc8-e0c89062b9c7" alt=""><figcaption><p>Embedding settings with Internal Links pages enabled</p></figcaption></figure>
{% endstep %}

{% step %}

#### Find the links

Click **Find links** to open the run dialog, choose the pages you want links pointing at, and start the run.

Suggestions appear in the **Suggestions** tab when the run finishes.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Pull your query data first.** Use **Pull query data** when the page offers it. With the searches each page ranks for, the tool prefers source pages that rank for the same searches, offers those searches as link text, and tells you which search a sentence matches. Without it, the run works on page similarity alone.
{% endhint %}

***

## The Opportunities Tab

Five lists, each answering a different question about your internal linking. Every list can be searched, sorted and paged.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FLXB8qhMJBp8e7tfAVanA%2FXnapper-2026-09-22-19.09.09.png?alt=media&amp;token=63cd8b79-bc59-4380-8d94-b1299331d096" alt=""><figcaption></figcaption></figure>

### Priority targets

Pages ranking between **position 4 and 20** with enough impressions and few body links pointing at them — the pages where one more internal link is most likely to move something. A page on page two of the results needs a smaller push than a page nobody can find.

| Column                | Meaning                                                   |
| --------------------- | --------------------------------------------------------- |
| **Page**              | The page that could use more links                        |
| **Position**          | Its average position over the last 28 days                |
| **Impressions (28d)** | How often it appeared in results                          |
| **Body links in**     | Links pointing at it from the main content of other pages |
| **Top query**         | The search it gets the most impressions for               |

Each row carries two controls:

* **Page type** — set what kind of page this is. Marking a page **legal**, **contact** or **utility** keeps it out of suggestions entirely, in both directions.
* **Sources** — opens a panel listing the pages whose content is closest to this one, with a similarity score for each. This costs nothing and needs no TypeSafe key.

{% hint style="info" %}
If no page on your site has enough Search Console data yet, this list changes to **Fewest links in** and ranks by how few body links each page receives instead.
{% endhint %}

### Orphans

Crawled pages that **no other page links to from its main content**. A menu or footer link does not save a page from this list — those appear on every page and carry no editorial signal.

Orphan pages are the clearest internal linking problem you can fix, and they are often pages that were published and then forgotten.

### Anchors

How varied the link text pointing at each page is. **Low diversity** means most links to that page use the same words.

| Column               | Meaning                                         |
| -------------------- | ----------------------------------------------- |
| **Body links in**    | Total editorial links pointing at the page      |
| **Distinct anchors** | How many different phrases are used             |
| **Diversity**        | Distinct anchors as a percentage of total links |
| **Most used anchor** | The phrase used most, and how often             |

Below it, a second table lists **the same anchor used more than three times for one page**. Repeating one exact phrase across many links looks deliberate rather than natural.

### Too many links

Pages with more body links than your cap allows. These pages are **never used as link sources** — the tool will not add an eleventh link to a page already carrying ten.

### Duplicate links

Pages that link to the same page more than once from their main content. The first link is the one readers use; the rest add nothing.

***

## Finding Links

Click **Find links** to open the run dialog. It answers two questions: **which pages** get links pointed at them, and **what that costs**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FU1eOh78rnzce6ci8aOBX%2FXnapper-2026-09-22-19.12.43.png?alt=media&amp;token=915fc935-17fc-474b-9ecf-4dd5f6302a6c" alt=""><figcaption><p>The Find internal links dialog with target pages chosen and the cost estimate</p></figcaption></figure>

### Choosing the target pages

Two lists to choose from:

{% tabs %}
{% tab title="Best opportunities" %}
The priority targets — pages ranking in your chosen position range with enough impressions. This is the default, and the right choice most of the time.

Quick picks (**First 10**, **First 25**) appear when the list is long enough for them to mean something.
{% endtab %}

{% tab title="Every page" %}
Every crawled page that can receive links, with the ones receiving the fewest first.

Use this for a page with **no search data yet** — a page you published last week can never reach the priority list, however much it needs links. A filter box helps you find it by title or path.
{% endtab %}
{% endtabs %}

One run takes at most **50 target pages**. The header tells you how many you have chosen, and the checkbox beside it selects or clears everything listed.

### Reading the cost

The estimate leads with the total you might spend:

| Line                            | What it covers                                                                                 |
| ------------------------------- | ---------------------------------------------------------------------------------------------- |
| **Embedding pages**             | Turning page text into vectors. Happens once per page, then only again when that page changes. |
| **Reading pages for sentences** | Reading the shortlisted source pages and choosing the sentences. This is the larger half.      |

{% hint style="warning" %}
The figure is quoted as **"up to"** on purpose. It is the most a run of this size has cost in testing; the real price depends on how much text your pages have, and shorter pages come in well under it. Recent runs have landed at roughly **half** the quoted ceiling.
{% endhint %}

The cost grows with the number of target pages, because each target has its own shortlist of source pages to read. Choosing 25 pages costs roughly five times what choosing 5 does.

### Embed pages only

This button runs the **first stage alone** and stops: your pages are embedded, no suggestions are made, and nothing is spent at TypeSafe. It appears only when there are pages left to embed.

Use it to prepare a large site now and find links later, or to work before you have a TypeSafe key.

{% hint style="info" %}
You never have to press it to keep things current. **Every** Find links run embeds whatever is new or changed before it starts looking, so a page you edited last night is re-read automatically.
{% endhint %}

***

## Reviewing Suggestions

The **Suggestions** tab groups proposals by the page they link **to**. Each one shows the source page, the exact sentence, the words that would become the link, and why the tool chose it.

The reason is highlighted under each sentence. When the target has search data, it names the search the page ranks for, with its position and impressions — for example *Ranks #2.5 for "serving per container" (28 impressions, 31 days to Sep 20)*.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FtQ9M6D1Xcr4Xg37iTkCv%2FXnapper-2026-09-22-19.13.41.png?alt=media&amp;token=cb875b38-aeac-4a66-aa97-a8623a794e0f" alt=""><figcaption><p>Suggestions grouped by target page, each with its sentence and proposed anchor</p></figcaption></figure>

### Available actions

Every suggestion has an **Actions** menu. It lists only the actions that fit the suggestion's current state.

| Action                  | What it does                                                                                                                |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Accept & apply**      | Accepts the suggestion and writes the link into the page on WordPress in one step. Needs a WordPress connection.            |
| **Accept**              | Reserves the link against your caps. Nothing is written to your site yet.                                                   |
| **Apply to WordPress**  | Writes an accepted link into the page.                                                                                      |
| **Change link text**    | Choose different words from the same sentence. The sentence itself is never rewritten.                                      |
| **Back to review**      | Returns an accepted, rejected or reverted suggestion to the **To review** tab.                                              |
| **Reject**              | Moves it to the **Rejected** tab. That sentence is not suggested again for the same pair of pages unless you bring it back. |
| **Revert on WordPress** | Removes an applied link from the page.                                                                                      |
| **Apply again**         | Writes a reverted link back into the page.                                                                                  |

The three tabs — **To review**, **Accepted** and **Rejected** — hold suggestions at each stage:

| Tab           | Actions in the menu                                                                                                                                         |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **To review** | **Accept & apply**, **Accept**, **Change link text**, **Reject**                                                                                            |
| **Accepted**  | **Apply to WordPress**, **Change link text**, **Back to review**, **Reject** — then **Revert on WordPress** once applied, or **Apply again** after a revert |
| **Rejected**  | **Accept**, **Back to review** — a rejection is never final                                                                                                 |

To act on several suggestions at once, tick their checkboxes. The buttons above the list change to match: **Accept**, **Accept & apply** and **Apply** for the selected rows, or **Revert** for applied ones.

{% hint style="info" %}
Accepting is not publishing. An accepted link waits in the **Accepted** tab until you write it to WordPress or export it.
{% endhint %}

{% hint style="warning" %}
Anything that changes your live site asks first. **Accept & apply**, **Apply to WordPress**, **Apply again** and **Revert** each open a confirmation that lists every link it will change, as the source page and the link text.
{% endhint %}

### Changing the link text

Choose **Actions → Change link text** to pick different words from the same sentence. You choose the link text with two clicks: its first word, then its last word.

1. Click the **first** word of the link text.
2. Click the **last** word. Every word in between is included. To link a single word, click the same word twice.
3. Click **Save**.

A line above the words always tells you which click comes next. To start over, click a new first word. The link text can have up to the **Maximum words in the link text** setting (6 by default); a last word further away than that is refused.

You can also pick one of the **Suggested** phrases instead.

### More suggestions for the same page

Each target page shows its three best source pages first. The others wait in a queue and are not shown yet. The group header says how many are queued — for example **3 suggestions · 12 more waiting**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FfZ2JId1J5I3AfsIodmZJ%2FXnapper-2026-09-22-19.14.18.png?alt=media&amp;token=4103b0a0-85c1-4cdc-90f0-ee0da7f73aaa" alt=""><figcaption></figcaption></figure>

A queued suggestion appears **only when you accept or reject** a suggestion shown for the same target page:

1. Click **Accept** or **Reject** on a suggestion.
2. It leaves the **To review** tab.
3. The next source page from the queue appears at the bottom of the group, and the "more waiting" count goes down by one.

When you reject a sentence and the same source page has another good sentence, that sentence is offered first, before the queue moves.

{% hint style="info" %}
Queued suggestions are not revealed any other way. Review the ones shown to see the next ones.
{% endhint %}

***

## Applying Links to WordPress

If your property has a WordPress connection, accepted links can be written into your pages directly.

{% stepper %}
{% step %}

#### Connect WordPress

Open **Actions → Rules** and choose this property's WordPress connection under **WordPress connection for applying links**.
{% endstep %}

{% step %}

#### Accept the suggestions you want

Work through the **To review** tab. Accepted suggestions collect in the **Accepted** tab.

To accept and publish in one step, choose **Actions → Accept & apply** instead and skip the next step.
{% endstep %}

{% step %}

#### Apply

In the **Accepted** tab, choose **Actions → Apply to WordPress** on a suggestion, or tick several and click **Apply** above the list. Confirm, and each chosen sentence has its link text wrapped in a link. Nothing else on the page is touched.
{% endstep %}
{% endstepper %}

### Reverting

Every applied link can be reverted. The sentence returns to exactly what it was before the link was added.

To revert, choose **Actions → Revert on WordPress** on an applied link, or tick several and click **Revert** above the list.

A reverted link stays in the **Accepted** tab. Choose **Actions → Apply again** to write it back into the page, or **Back to review** to reconsider it. Applying again re-checks your caps first, so it is refused if the page has since reached its link limit or already links to the same page.

{% hint style="warning" %}
If the page changed on your site after the link was applied, the status becomes **Page changed** and the link is not reverted automatically — the tool will not edit a sentence it no longer recognises. Fix those by hand.
{% endhint %}

### When an apply or revert is not confirmed

If a write to WordPress is cut off — the connection drops, or the app closes mid-way — the tool cannot tell whether the change reached your site. The link's status then reads **Apply not confirmed** or **Revert not confirmed**, and a **Check N unconfirmed** button appears above the **Accepted** list.

Click it to read those pages on WordPress and settle each link's status. Nothing is sent to your site. The button only appears when there is something to check.

***

## Settings

All settings for this tool live on the property's settings page. Open **Actions → Rules** from the Internal Links page, or go to the property's settings and use the sidebar.

### Internal link rules

| Setting                                     | Default | What it controls                                                                          |
| ------------------------------------------- | ------- | ----------------------------------------------------------------------------------------- |
| **Maximum body links per page**             | 10      | Pages at this number are not used as link sources                                         |
| **Same anchor to the same page, site-wide** | 3       | An anchor already used this often for a page is not suggested again                       |
| **Paragraphs to skip at the top**           | 1       | No link is suggested in the opening paragraphs                                            |
| **Source pages shortlisted per target**     | 25      | How many related pages are read for each target. **Lower this to cut the cost of a run.** |
| **Priority position from / to**             | 4 to 20 | The ranking range that makes a page a priority target                                     |
| **Minimum queries per page**                | 3       | Fewer than this counts as too little search data                                          |
| **Minimum impressions per page (28 days)**  | 10      | Fewer than this counts as too little search data                                          |

Each field shows its allowed range under it. A value outside the range is marked in red, and **Save** stays disabled until it is fixed.

Three rules cannot be changed:

* One link per target page on each source page
* Anchors are words already in the sentence — the text is never rewritten
* Pages built with a page builder (Elementor and similar) are never edited

### Advanced settings

Click **Advanced** at the bottom of the rules card to open these. The defaults suit most sites; change them when the suggestions are consistently too many, too few, or use link text you do not like.

| Setting                              | Default | Range | What it controls                                                                                                                                                 |
| ------------------------------------ | ------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Minimum sentence confidence (%)**  | 50      | 10–95 | How sure the AI must be that a sentence is a good place for the link. Lower it to see more suggestions; raise it to see only the clearest ones.                  |
| **Minimum link text confidence (%)** | 50      | 0–95  | How sure the AI must be of the words it picked as the link text. Unsure picks are usually words about a broader topic than the page. **0** turns this check off. |
| **Minimum words in the link text**   | 1       | 1–10  | Set **2** or more to never get a one-word link text.                                                                                                             |
| **Maximum words in the link text**   | 6       | 1–10  | The longest link text the AI may pick. Also the most words you can choose when you edit a link text.                                                             |

**Reset numbers to defaults** puts these four back. It does not clear your own rules below.

{% hint style="info" %}
Settings apply to the **next** Find links run. Suggestions already in the list keep the settings they were made with — run **Find links** again for the same pages to see the effect.
{% endhint %}

### Your rules for the AI

Below the numbers, two boxes let you give the AI rules of your own, written as plain sentences:

* **Your rules for choosing the sentence** — where a link may go.
* **Your rules for choosing the link text** — which words may become the link.

Write one rule per line, up to 5 rules per box and 200 characters per rule. Your rules are added to the tool's built-in rules; they never replace them.

Examples of useful rules:

* ✅ Never use a broader topic as link text, e.g. "nuts" for a page about cashews.
* ✅ Brand names are always two words.
* ✅ Do not put a link in a sentence that is a question.

Rules that do not work well:

* ❌ Always suggest a link. *(The AI still drops sentences that do not fit; a rule cannot force a link.)*
* ❌ Write a better sentence. *(The tool never rewrites your text, so the AI cannot follow it.)*

{% hint style="warning" %}
A rule can make suggestions better or worse, and the app cannot tell which. Your rules are also sent with every question the AI is asked, so each run costs a little more — one rule of about 100 characters adds roughly 3%, and the estimate in the Find links dialog includes it. Try a new rule on a few pages first and compare the results before running it on many.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FOLnTfsaRpcgsxFW4ugfu%2FXnapper-2026-09-22-19.15.05.png?alt=media&amp;token=57210c74-ee57-4040-849a-a17f2b549722" alt=""><figcaption><p>The Advanced section of the Internal Links rules, with the confidence and link text settings and your own rules for the AI</p></figcaption></figure>

### Link crawler

Under **Crawling** on the same settings page:

| Setting                 | Default | What it controls                                                                                           |
| ----------------------- | ------- | ---------------------------------------------------------------------------------------------------------- |
| **Requests per Second** | 1       | How fast the crawler visits your pages. Range 1–3. Raise it for your own site; keep it low for a client's. |
| **Max Chrome Tabs**     | 3       | How many pages load at once, within the rate above. Range 1–3.                                             |
| **Auto-Crawl Schedule** | Weekly  | How often the crawler runs by itself: Weekly, Bi-weekly, Monthly, or Manual Only                           |

{% hint style="info" %}
A scheduled crawl updates your page text but does not embed it. The new text is embedded the next time you run **Find links**, so a scheduled crawl never spends money on its own.
{% endhint %}

You can also start a crawl at any time from **Actions → Run link crawler**.

***

## Use It From an AI Assistant

If you connected an AI app such as Claude or ChatGPT through the [MCP Server](/guide/mcp-server), you can ask it to do this work for you. It reads the same lists and suggestions as this page and follows the same rules.

Ask in plain words, for example:

* "Which pages on example.com need internal links first?"
* "Find links for my five best priority targets. Tell me the cost first."
* "Show me the new suggestions for /coffee-grinders and accept the good ones."
* "Apply the accepted links to WordPress."

{% hint style="warning" %}
**Find links costs money, and applying changes your live site.** SEO Utils tells the AI to quote the cost before a run and to ask you before it writes to WordPress, and most AI apps ask you to approve each change. Check the cost and the list of links before you say yes.
{% endhint %}

***

## Troubleshooting

<details>

<summary>The Find links dialog only offers a handful of pages</summary>

The default list is **priority targets**, not every page. A page only reaches it by ranking between positions 4 and 20 with enough impressions, so a site with little Search Console data will have very few.

Two ways forward:

1. Switch to **Every page** in the dialog to choose from every crawled page.
2. Widen the range in **Rules** — lower **Minimum impressions per page** or stretch the **Priority position** range.

</details>

<details>

<summary>"Turn on embeddings for Internal Links"</summary>

The tool cannot tell which pages share a topic without page vectors.

1. Go to **Settings → Embeddings**.
2. Turn on the master switch.
3. Enable **Internal Links pages** and choose a model.
4. Return to Internal Links and run again.

</details>

<details>

<summary>"No TypeSafe API key"</summary>

Link suggestions need a TypeSafe key. Add one under **Settings → Services → AI Era**.

Everything else — crawling, embedding, all five Opportunities lists and the Sources panel — works without it.

</details>

<details>

<summary>A page I want links for is not in any list</summary>

Check these in order:

1. **Is it in your sitemap?** The crawler only reads URLs listed there.
2. **Has it been crawled?** The **Pages crawled** tile shows the count.
3. **Is its page type excluded?** Legal, contact and utility pages are never used as sources or targets. Change the type from the **Page type** control on a Priority targets row.
4. **Is it over the link cap?** Pages with too many body links are excluded as sources, though they can still receive links.

</details>

<details>

<summary>The estimate says a run will cost more than expected</summary>

The cost is driven by **source pages read**, not target pages chosen. Each target has its own shortlist — at the default of 25, choosing 10 targets means reading up to 250 pages.

Lower **Source pages shortlisted per target** in Rules to reduce it. Dropping it from 25 to 10 cuts the reading cost by about 60%, at the price of fewer candidate sources per page.

</details>

<details>

<summary>A suggestion shows "No search data"</summary>

That suggestion was chosen on page similarity alone, without the searches each page ranks for.

Use **Pull query data** on the Internal Links page, then run again. Suggestions will then prefer source pages that rank for the same searches and explain which search each sentence matches.

</details>

<details>

<summary>Link text uses a word that is too broad</summary>

For example, "nuts" as the link text for a page about cashews. This usually means the AI was unsure of its pick.

1. Keep **Minimum link text confidence** at 50 or raise it. Most broad picks fall below 50.
2. Add a rule under **Your rules for choosing the link text**, such as *Never use a broader topic as link text.*
3. Run **Find links** again for the same pages.

</details>

<details>

<summary>Too few suggestions, or a page gets none</summary>

The AI only suggests sentences and link text it is sure enough about.

1. Lower **Minimum sentence confidence** (for example to 40) to allow more sentences.
2. Lower **Minimum link text confidence**, or set it to 0 to turn that check off.
3. Check **Minimum words in the link text** — a high minimum removes many choices.
4. Review your own rules — a strict rule can remove most choices.

</details>

<details>

<summary>A one-word link text</summary>

Set **Minimum words in the link text** to 2 in the Advanced settings. For a single suggestion, click the edit button and pick more words from the same sentence.

</details>

***

## Related Guides

{% content-ref url="/pages/GEScTVAkP5gZtYV3mNYz" %}
[Embedding Database](/guide/embedding-database)
{% endcontent-ref %}

{% content-ref url="/pages/Ow9upwg0tyWfwpI0MBPb" %}
[Indexing Dashboard](/guide/google-search-console/indexing-dashboard)
{% endcontent-ref %}

{% content-ref url="/pages/eWCdj5l65f7zEfzXnaBt" %}
[MCP Server (AI Integration)](/guide/mcp-server)
{% endcontent-ref %}


# GSC Rank Tracker

The GSC Rank Tracker turns your own [Google Search Console](/guide/google-search-console) data into a daily ranking history for the keywords you care about. It costs nothing per check, because it reads data Google already gives you instead of scraping search results.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-48b4e5790222b9cfd29c3ff039ef5a5b3cc5bada%2Fgsc-rankings-overview.png?alt=media" alt="The Rankings tab with the tracker selector, KPI strip, position bands chart and Keywords table"><figcaption><p>The Rankings tab of a Search Console property</p></figcaption></figure>

## What you get

* **16 months of history at once.** The moment you add a keyword, SEO Utils downloads its past positions, so you do not wait weeks for a trend.
* **No cost per check.** There are no credits, proxies or DataForSEO calls involved.
* **One tracker per market.** A tracker covers one country (or Worldwide), one device group and one search type, so its numbers are not mixed across markets.
* **Alerts and movers.** See which keywords really moved, get an alert for each real change, and send it by email or webhook.
* **Comparison with the Organic Rank Tracker.** Link a report to see where its positions differ from Google's, and run a paid live SERP check when you want to look at one results page.
* **Top 1, 3 and 10 over time.** A chart counts your keywords in the top 1, 3 and 10, next to their clicks and impressions, and with a linked report adds the rank tracker's counts as dashed lines.
* **Clicks and search volume.** A CTR gap badge shows keywords that get fewer clicks than their position should, and Volume and Opportunity show what the next step up is worth.
* **Opportunities per page.** The Pages tab adds up the Opportunity of each page's keywords and opens the list of keywords to work on for it.
* **Before / after.** Pick a date, such as a page change or a Google update, and see how each keyword moved around it.
* **AI helpers.** Ask why a keyword moved, get a weekly summary and sort keywords into topics, with your own AI key or a local model.
* **Reports.** Open a printable report of the tracker and save it as a PDF, or have an automation create it.
* **All trackers in one table.** Switch the Search Console properties page to **Rankings** to compare every tracker at a glance.

## How the numbers work

Search Console reports an **average position** for each query, per day. The tracker keeps the exact value and shows it as a whole number; hover a position to see the decimals.

The position shown for a keyword is your site's **best spot** for that query: the average position of your highest result on that day, across all your pages. You can also set a **target page** for a keyword and see how that one page does.

| Term              | What it means                                                                                                                                                                             |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Final data**    | Data Google has finished processing. It runs about 2-3 days behind today. All averages, changes, movers and alerts use final data only.                                                   |
| **Fresh data**    | The newest days, which Google can still revise. They are shown with a hatched mark and are replaced when they become final.                                                               |
| **Low data day**  | A day with fewer impressions than the tracker's **thin threshold** (5 by default). Low data days are faded and left out of averages, so a handful of impressions cannot swing a position. |
| **Pacific dates** | Search Console dates follow Pacific Time. The tracker uses the same calendar days, and its header says so: "Final through Oct 11 · fresh through Oct 14 (Pacific)".                       |

{% hint style="info" %}
A keyword that Google shows no impressions for has no position that day. The tracker shows a dash and never counts it as 0.
{% endhint %}

## How it differs from the Organic Rank Tracker

Both tools answer "where do I rank?", with different data.

|                 | GSC Rank Tracker                                                       | [Organic Rank Tracker](/guide/organic-rank-tracker)                                         |
| --------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| **Source**      | Your Search Console data: Google's average position over real searches | A search result check at one location and time                                              |
| **Cost**        | Free                                                                   | Depends on the scrape method: your own IP or proxies, or DataForSEO, which bills each check |
| **History**     | 16 months of past data as soon as you add a keyword                    | Starts with your first check, unless you import past data                                   |
| **Competitors** | Your own site only                                                     | Can track competitors                                                                       |
| **Keywords**    | Only queries Google showed your site for                               | Any keyword you add                                                                         |
| **Freshness**   | 2-3 days behind, plus provisional fresh days                           | As recent as your last check                                                                |

Use the GSC Rank Tracker for ongoing, free tracking of keywords you already rank for. Use the Organic Rank Tracker to check keywords you do not rank for yet, or to compare against competitors. You can start a GSC tracker from an Organic Rank Tracker report to reuse its keywords, and [compare the two](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker) once they are linked.

## Where to find it

Open **Your Sites > Search Console** in the sidebar, open a property and choose **Rankings** in the page menu of the top bar, right after Performance. The first visit opens the tracker wizard. To see every tracker in one table, use the **Rankings** view of the properties page: see [Rankings across properties](/guide/google-search-console#rankings-across-properties).

## Team Members

[Team members](/guide/team) you invite can use the tracker in the browser too, in the workspaces you gave them. Their [role](/guide/team/inviting-your-team#roles) decides what they can do:

| Role        | In the GSC Rank Tracker                                                                                                                                                           |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Viewer**  | Read the tracker, its Keywords table and Grid, Movers, Alerts and the keyword details, including the comparison with a linked report and the stored live checks.                  |
| **Analyst** | Everything a Viewer does, plus tag keywords, add chart notes, export CSV, use **Refresh now** and start live SERP checks.                                                         |
| **Manager** | Everything an Analyst does, plus add keywords, create, duplicate and delete trackers, change settings and targets, archive keywords, link a report and send keywords to a report. |

Whatever downloads data from Google through your connected account also needs **Can use the owner's machine and accounts**: creating a tracker, adding keywords, **Refresh now** and **Pull new ORT keywords**. So does a live SERP check, which spends your DataForSEO credit. Without it, the button is greyed out with **Ask {your name} for run access**. Connecting a Search Console property stays with you.

{% hint style="info" %}
What each role can do with the comparison and the live checks, and where their cost shows up, is in [Compare with Organic Rank Tracker](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#team-members).
{% endhint %}

## Guides

{% content-ref url="/pages/j9lG7KqTEFkzZUwXZntV" %}
[Create a Tracker](/guide/google-search-console/gsc-rank-tracker/create-a-tracker)
{% endcontent-ref %}

{% content-ref url="/pages/Bn1IVfGSbBaUHCd6i2Rq" %}
[Read Your Rankings](/guide/google-search-console/gsc-rank-tracker/read-your-rankings)
{% endcontent-ref %}

{% content-ref url="/pages/TqUFskX5cnbQ2EoHpubr" %}
[Keywords in the Top 1, 3 and 10](/guide/google-search-console/gsc-rank-tracker/top-1-3-10)
{% endcontent-ref %}

{% content-ref url="/pages/sTqMBrSBDInu9iayavd6" %}
[Keyword Details](/guide/google-search-console/gsc-rank-tracker/keyword-details)
{% endcontent-ref %}

{% content-ref url="/pages/f946Aq07JOQURBDuZXrL" %}
[Compare with Organic Rank Tracker](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker)
{% endcontent-ref %}

{% content-ref url="/pages/MC7PP6WMXpUvBAizRawp" %}
[Opportunities per Page](/guide/google-search-console/gsc-rank-tracker/opportunities-per-page)
{% endcontent-ref %}

{% content-ref url="/pages/c1EyDOIcF5zDc6pbOUFH" %}
[Movers](/guide/google-search-console/gsc-rank-tracker/movers)
{% endcontent-ref %}

{% content-ref url="/pages/YZwPnKjUgXFtCYxLvFQm" %}
[Alerts](/guide/google-search-console/gsc-rank-tracker/alerts)
{% endcontent-ref %}

{% content-ref url="/pages/EEDLzw4nsAEcV3WXovoK" %}
[Before / After](/guide/google-search-console/gsc-rank-tracker/before-after)
{% endcontent-ref %}

{% content-ref url="/pages/phfBll1eZup13KfAWZEd" %}
[AI: Explanations, Summary and Topics](/guide/google-search-console/gsc-rank-tracker/ai)
{% endcontent-ref %}

{% content-ref url="/pages/o2nzeEjngWTGZX8NRamw" %}
[Report and PDF](/guide/google-search-console/gsc-rank-tracker/print-and-pdf)
{% endcontent-ref %}

{% content-ref url="/pages/3jpKBIKHe2K28pa31OTo" %}
[Manage Trackers](/guide/google-search-console/gsc-rank-tracker/manage-trackers)
{% endcontent-ref %}


# Create a Tracker

A tracker follows a list of keywords in one market. The wizard walks you through it in five steps, and the first one opens by itself the first time you visit **Rankings** on a property.

{% hint style="info" %}
You need a connected Search Console property. See [Google Search Console](/guide/google-search-console) to connect one.
{% endhint %}

## Open the wizard

Open a property and choose **Rankings** in the page menu of the top bar (the name of the current page, right after the domain). To add another tracker later, open the tracker selector next to the page title and choose **New tracker**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2b3c1f69c609d416e37754120f475e72b7c8fa86%2Fgsc-rankings-property-menu.png?alt=media" alt="The page menu in the top bar with the Rankings item after Performance"><figcaption><p>Rankings (1) sits right after Performance in the page menu</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d8983b5e72b7866251f600418acfe13da5590cf9%2Fgsc-rankings-tracker-selector.png?alt=media" alt="The tracker selector listing two trackers and a New tracker item"><figcaption><p>Add more trackers from the selector</p></figcaption></figure>

## The five steps

{% stepper %}
{% step %}

#### Start

Choose how to begin:

* **Blank tracker**: pick a market, then add keywords yourself.
* **Duplicate a tracker**: shown when the property already has a tracker. Pick the tracker, then click **Next** to open the [Duplicate dialog](/guide/google-search-console/gsc-rank-tracker/manage-trackers#duplicate-a-tracker), where you name the new tracker and can choose another country, device or search type. The new tracker gets the keywords, rules and thresholds of the one you picked, and the remaining steps are skipped.
* **Start from an Organic Rank Tracker report**: copy the keywords and the market of an [Organic Rank Tracker](/guide/organic-rank-tracker) report for this site, and link it. Click **Copy keywords** next to the report. The option is disabled, with its reason, when no report matches the site.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-866e8b37d9939c58cf3b56eea16371af33b6c22e%2Fgsc-rankings-wizard-start.png?alt=media" alt="Wizard step 1 with Blank tracker, Duplicate a tracker and Start from an Organic Rank Tracker report"><figcaption><p>Step 1: start blank, from a tracker or from a report</p></figcaption></figure>
{% endstep %}

{% step %}

#### Market

A tracker covers one market, so its numbers are never mixed across countries or devices.

* **Country**: sorted by clicks in the last 90 days, with each country's share of your impressions. Choose **Worldwide** for all countries.
* **Device**: **All devices**, **Desktop** or **Mobile + tablet**, each with its share of impressions.
* **Search type**: **Web**, **Image**, **Video** or **News**.

The box under the options tells you how much of your traffic the market covers and how many of your top 100 keywords would have mostly low data days there. The top country and **All devices** are selected for you.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e54fa437367835d8701c7ea4c06b034e930eeb73%2Fgsc-rankings-wizard-market.png?alt=media" alt="Wizard step 2 with country, device and search type"><figcaption><p>Step 2: choose the market</p></figcaption></figure>
{% endstep %}

{% step %}

#### Keywords

The **Keywords** step has three tabs. A bar at the bottom always shows what your tracker holds, for example "100 keywords · 2 rules".

**Paste / Import**

* Paste one keyword per line and click **Add**. Duplicates are skipped.
* Or click **Choose CSV file**. Use the columns `keyword`, `target_url` and `tags` (up to 8 MB).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2d9eddd5f4cfbffcd028201bb56c55b157946dac%2Fgsc-rankings-wizard-keywords-paste.png?alt=media" alt="The Paste / Import tab with a keyword box, a tags field and a CSV button"><figcaption><p>Paste keywords or import a CSV file</p></figcaption></figure>

**Tags for these keywords** (optional, 1) sits under the paste box. Type a tag and press Enter or a comma, and every keyword of that paste gets the tag, including keywords the tracker already has. Tags are only added, never removed. You can use up to 20 tags per paste, and the field keeps them for your next paste until you remove them.

After you click **Add** (2), a message says how many keywords were added and how many existing ones were tagged, for example "Added 2 · 1 existing keyword tagged". The same field is in **Add keywords** on an existing tracker.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6eedbd3e1dd42a98b01104c27ba81af4ede5db49%2Fgsc-rankings-wizard-keywords-tags.png?alt=media" alt="The Paste / Import tab with three keywords and the tag Competitors"><figcaption><p>Tag the pasted keywords</p></figcaption></figure>

**Suggestions**

Four lists built from your last 90 days of Search Console data. Tick queries, or click **Add all** to add the whole list.

| List                  | What it shows                                                                                    |
| --------------------- | ------------------------------------------------------------------------------------------------ |
| **Top by clicks**     | The 100 queries with the most clicks in this market over the last 28 days.                       |
| **Striking distance** | Queries averaging between position 7.5 and 20.5 with many impressions: close to the top results. |
| **New this month**    | Queries whose first impression came in the last 30 days, with at least 20 impressions since.     |
| **Volatile**          | Queries whose daily position moved a lot over the last 28 days.                                  |

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-de498f8888207cd68a31c817e93e81db7e456911%2Fgsc-rankings-wizard-keywords-suggestions.png?alt=media" alt="The Suggestions tab with its four lists"><figcaption><p>Add suggestions one by one or all at once</p></figcaption></figure>

**Rules**

A rule is **one row** in your tracker that follows every query it matches, including queries that appear later, as a group with one combined position. Build it with a **Type**:

* **Query rule**: the query **contains**, **starts with**, **ends with** or **matches regex** a value.
* **Page rule**: the page URL **equals**, **starts with**, **contains** or **matches regex** a value. Use full URLs, for example `https://harborpine.example/blog/`.

Then choose how to add it:

* **As one rule** adds a single row.
* **As keywords** adds one row for each matching query: a fixed list that does not grow.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e1a99e47d8e6b07193a4258c1c8dd2a396293005%2Fgsc-rankings-wizard-keywords-rules.png?alt=media" alt="The rule builder with the As one rule and As keywords options"><figcaption><p>A rule can be one group row or a list of keywords</p></figcaption></figure>

{% hint style="info" %}
A rule picks up new matching queries by itself. You can track any query of a rule on its own later. See [Rules in Read your rankings](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#rules).
{% endhint %}
{% endstep %}

{% step %}

#### Targets

Optional. A **target page** is the page you want a keyword to rank with. SEO Utils flags the days Google shows another page instead.

Click **Suggest targets** to pre-fill each keyword with the page that got the most impressions for it, then **Accept all** or edit any row. The target must belong to the property. Click **Skip** to set targets later.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-10f235b0e57cc6ad33ca440274320770f454305d%2Fgsc-rankings-wizard-targets.png?alt=media" alt="Wizard step 4 with suggested target pages"><figcaption><p>Step 4: accept or edit suggested target pages</p></figcaption></figure>
{% endstep %}

{% step %}

#### Review and create

* **Name**: defaults to the market, for example "US · All devices · Web".
* **Thin threshold**: days with fewer impressions than this are faded and left out of averages. Default 5.
* **Move threshold**: how many positions a keyword must move to count as a move. Default 5. See [Alerts](/guide/google-search-console/gsc-rank-tracker/alerts).
* **Desktop notifications**: show a notification when a refresh finds new alerts.
* **Weekly AI summary**: off by default. Turn it on for a short AI write-up of the tracker every Monday. See [AI](/guide/google-search-console/gsc-rank-tracker/ai#weekly-summary).
* **Rank tracker report**: link an [Organic Rank Tracker](/guide/organic-rank-tracker) report to compare it with Search Console. SEO Utils suggests the first compatible report for the market. See [Compare with Organic Rank Tracker](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#in-the-new-tracker-wizard).

Click **Create tracker**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2384bf5950c7eaf05f09e3a4105537170788b3f1%2Fgsc-rankings-wizard-review.png?alt=media" alt="Wizard step 5 with name, thresholds, notifications, the Weekly AI summary switch and the Rank tracker report link"><figcaption><p>Step 5: review and create. The Weekly AI summary switch (5) names the model it will use</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## After you click Create

SEO Utils downloads 16 months of history for every keyword and rule. A progress panel shows the batches as they are saved, and the numbers on the page fill in while it runs.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-32f766247c0a205aebad6d2496660db80a0202ed%2Fgsc-rankings-run-progress.png?alt=media" alt="The refresh progress panel showing batches being saved"><figcaption><p>The progress bar (1): history downloads in batches, and positions appear as each batch lands</p></figcaption></figure>

The tracker then refreshes itself every 6 hours while the property's **Auto-sync Enabled** setting is on. You can refresh at any time with **Refresh now**.

{% hint style="info" %}
Keywords you add later get their own 16 months of history. New trackers never create alerts for the past: alerts start from the moment a keyword's history is complete.
{% endhint %}


# Read Your Rankings

The tracker page answers three questions: how are my rankings overall, what changed over time, and which keywords need attention. This page explains each part of the screen.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-48b4e5790222b9cfd29c3ff039ef5a5b3cc5bada%2Fgsc-rankings-overview.png?alt=media" alt="The tracker page with the top bar, tracker selector, KPI strip, position bands chart and Keywords table"><figcaption><p>The tracker page: the tracker selector (1), the KPI strip (2), the position bands chart (3) and the tabs (4)</p></figcaption></figure>

## Header

* **Tracker selector**: switch between trackers or add a new one. A dot or number shows trackers with unread [alerts](/guide/google-search-console/gsc-rank-tracker/alerts).
* **Market chips and freshness line**: the market of this tracker and how current the data is, for example "Final through Oct 11 · fresh through Oct 14 (Pacific)".
* **Refresh now**, at the right end of the top bar: download the newest data right away.
* **The tracker's name** in the top bar opens a menu with **Settings**, **Export PDF & HTML…** (a printable [report](/guide/google-search-console/gsc-rank-tracker/print-and-pdf); **Export PDF…** in a browser), **Export CSV…**, **View log** (what the last refreshes did) and **Duplicate tracker…**. See [Manage trackers](/guide/google-search-console/gsc-rank-tracker/manage-trackers).

## This week

When the weekly AI summary is on, a **This week** card above the KPI strip writes up the week's confirmed moves and alerts. See [AI: Explanations, Summary and Topics](/guide/google-search-console/gsc-rank-tracker/ai#weekly-summary).

## KPI strip

The strip sums up your tracked keywords and rules as of the end of the date range, compared with 7 days earlier. A positive change is always an improvement.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0d7e88a2e4ee80b6d47c9d552ab5bf250ea3a624%2Fgsc-rankings-kpi-strip.png?alt=media" alt="The KPI strip with the Positions and Activity blocks"><figcaption><p>The KPI strip: Positions, Activity and the tracked count</p></figcaption></figure>

| Block         | Figure              | What it tells you                                                                                                                         |
| ------------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Positions** | **Avg position**    | The average position of your tracked keywords and rules, weighted by their impressions.                                                   |
|               | **Top 1**           | How many have an average position that rounds to 1.                                                                                       |
|               | **Top 3**           | How many have an average position of 3 or better. Top 1 keywords are included.                                                            |
|               | **Top 10**          | How many have an average position of 10 or better. Top 3 keywords are included.                                                           |
| **Activity**  | **Movers · 7 days** | Confirmed moves in the last 7 days: ▲ improved, ▼ declined. Click to open [Movers](/guide/google-search-console/gsc-rank-tracker/movers). |
|               | **Unread alerts**   | Alerts you have not read yet. Click to open [Alerts](/guide/google-search-console/gsc-rank-tracker/alerts).                               |

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-639bc6bf8e1e87fe5e26368c1a88028a3f75e421%2Fgsc-rank-tracker-kpi-top1.png?alt=media" alt="The Positions block with Avg position, Top 1, Top 3 and Top 10"><figcaption><p>The Top 1 tile (1) sits between Avg position and Top 3</p></figcaption></figure>

Under the strip, the caption names the date the figures are as of, and the line on the right counts what you track, for example "Tracking 100 keywords · 2 rules". While history is still downloading, it also says how many items are "pulling history".

## Position bands chart

The chart counts your tracked keywords and rules by position band for each day: **#1**, **2–3**, **4–10**, **11–20**, **21–50**, **51–100**, **101+** and **No data**. A bar that grows at the bottom means more keywords at #1 and in the top 3. For long ranges, bars group days into weeks or months.

A black line runs over the bars: the **average position** of the same keywords, read on the axis at the right. Better, lower positions are at the top, so a line that climbs means your average position improves. Hover a bar to see its bands and **Avg position**. Click **Avg position (right axis, lower is better)** in the legend to hide or show the line. SEO Utils remembers your choice for each tracker.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f2f1b93aeb1667cac98d6efa3bb8699c2d2e8146%2Fgsc-rank-tracker-band-chart-top1.png?alt=media" alt="The position bands chart with a separate #1 segment and the average position line on a right-hand axis"><figcaption><p>The <strong>#1</strong> segment (1) and the average position line (2), which you can hide from the legend</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9d2df55dd241d22ec6cfb000bfa308908a06d8f2%2Fgsc-rankings-band-chart.png?alt=media" alt="The position bands chart with a Google update line and a note"><figcaption><p>Position bands with Google update markers and your notes</p></figcaption></figure>

Use the **Markers** switch to show what else happened:

* **A vertical line** marks a Google update.
* **A hatched band** marks a period when Search Console data had a known problem. Compare numbers across it with care.
* **A small triangle** at the bottom of the chart marks a note. Click **Add note** to record a change you made, such as a new page template. Notes belong to the property, so they also appear on the Performance chart. Click a triangle to read, edit or delete the notes of that day.

Hover a line or a band for its name, its dates and a link to read more. The arrow at the top right of the card hides the chart.

### Filter the charts by page

The **Page** picker in the chart's header narrows the chart to one page: it counts only the keywords Google shows for that page on the last day of the date range. The **Keywords in the top 1, 3 and 10** card below has the same picker. Both charts always show the same page, so a pick in either one changes both. The Pages tab's **Show in charts** does the same for the page of a row.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5cb4fe2c735e48bdd269279fb4c2c1c26fa61b67%2Fgsc-rank-tracker-band-chart-page-filter.png?alt=media" alt="The position bands chart with the Page picker set to one page and a description that names it"><figcaption><p>The Page picker (1) sets the chart to one page, and its description names that page</p></figcaption></figure>

* **What is counted.** The bars count that page's keywords only, and rules are left out because a rule has no page. Positions stay your site's best position for each keyword, so earlier days show where your site ranked then, whichever page Google showed.
* **Back to everything.** Choose **All pages** in a picker. The tracker does not remember the page: reloading it shows the whole tracker again. The KPI strip, the other tabs and the [report](/guide/google-search-console/gsc-rank-tracker/print-and-pdf) ignore the page.
* **A page with no keyword.** When no tracked keyword shows the page on the last day, for example after you move the date range, the chart says "No tracked keyword shows this page on {date}." with a **Show all pages** button.

## Keywords in the top 1, 3 and 10

Under the band chart, the **Keywords in the top 1, 3 and 10** card counts how many keywords are in the top 1, top 3 and top 10 over time, next to their clicks and impressions. With a linked Organic Rank Tracker report it adds that report's counts as dashed lines and shows how far the two sources are apart. See [Keywords in the Top 1, 3 and 10](/guide/google-search-console/gsc-rank-tracker/top-1-3-10). Its **Page** picker works like the band chart's.

## Date range

The range picker above the table sets the dates for the charts, the table and the grid. The default is **Last 30 days**. Choose **Last 7 days**, **Last 90 days**, **Last 6 months**, **Last 16 months** or **Custom**. The Movers tab has its own range, and the Alerts tab lists every alert. The **Before / after** tab compares positions around a date you pick: see [Before / after](/guide/google-search-console/gsc-rank-tracker/before-after).

## Keywords table

The **Keywords** tab lists every active keyword and rule of the tracker.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-09831592d5c269ba6ddd6c32ad3bc34094a73042%2Fgsc-rankings-keywords-table.png?alt=media" alt="The Keywords table with Pos, 7d, 30d, Trend, Page and Target columns"><figcaption><p>The Keywords table</p></figcaption></figure>

| Column                                 | What it shows                                                                                                                                                                             |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Keyword**                            | The keyword or rule, with its tags and flags. Click it to open the [keyword details](/guide/google-search-console/gsc-rank-tracker/keyword-details).                                      |
| **Pos**                                | The position as a whole number: the weighted average of the last 7 days with enough impressions. Hover it for the decimal and the days behind it.                                         |
| **7d** and **30d**                     | The change against 7 and 30 days earlier. Green is an improvement, red a decline, and an arrow means under half a position, which is not a move. A dash means too little data.            |
| **Trend**                              | 12 weekly points ending at the end of the range. Every row uses the same scale, with position 1 at the top, 100 at the bottom and a faint line at position 10.                            |
| **Page**                               | The page that got the most impressions for this keyword on its latest day with enough impressions.                                                                                        |
| **Target**                             | The page you want the keyword to rank with, if you set one.                                                                                                                               |
| **Impr., Clicks, CTR (28d)**           | Impressions, clicks and click-through rate over the last 28 days. A **CTR gap** badge marks a keyword whose clicks are low for its position: see [CTR gap](#ctr-gap).                     |
| **Volume**                             | The keyword's monthly Google searches in the tracker's market, with the source and the date of the check. See [Volume and Opportunity](#volume-and-opportunity).                          |
| **Opportunity**                        | The extra clicks a month the keyword could get in the top 3, for example **+405 est. clicks/mo**. A page-1 keyword without a search volume uses its impressions instead.                  |
| **Page sessions**, **Page key events** | The organic sessions and key events GA4 recorded for the keyword's page. They appear once the site has a GA4 property: see [Page sessions and key events](#page-sessions-and-key-events). |

Click **View** to choose the columns. The **⋯** menu of a row offers **Set target…**, **Open in Performance** and **Archive**.

While an Organic Rank Tracker report is linked, the table also has **SERP** and **Gap** columns and a **Compare** filter (**All**, **Big gaps**, **Only in GSC**, **Only in ORT**). See [Compare with Organic Rank Tracker](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#compare-in-the-keywords-table).

{% hint style="info" %}
A small hatched mark next to a position means newer, not yet final data exists for it. It is shown in the hover text but not used in the number until Google finalizes it.
{% endhint %}

### Page sessions and key events

When the tracker's site has a connected [GA4 property](/guide/google-analytics-4), the table gets **Page sessions** and **Page key events**: the organic sessions and key events GA4 recorded for the keyword's page over the table's date range.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-04ee35004623be3decf26a43cbf5f48e29c7a79e%2Fgsc-rankings-page-traffic-columns.png?alt=media" alt="The Keywords table with Pos, 7d, 30d and Page columns followed by Page sessions and Page key events"><figcaption><p>Page sessions (1) and Page key events (2) beside the keyword's page</p></figcaption></figure>

* **Which page.** The keyword's target page when you set one, otherwise the page in the **Page** column. A keyword with no page yet shows a dash, and so does a rule.
* **Whole page, not one keyword.** GA4 has no keyword data, so the figures count the page's organic traffic from every keyword it ranks for. Hover the (?) on the header to see this.
* **Sort by them.** Click a header to sort all keywords by it, not only the ones on screen. Rules and keywords with no page sort last, and a page with no GA4 traffic counts as 0. The sort is unavailable, with the reason in the header menu, when the date range starts before GA4's page data does.
* **Show or hide them.** They appear by default once the site resolves to a GA4 property, and **View** hides them. If several GA4 properties match the site, choose one on the [Search Console chart](/guide/google-search-console#ga4-traffic-next-to-your-clicks) first.

### Flags

| Flag                         | Meaning                                                                                                                                   |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Orange flag next to the page | Google showed a page other than your target on at least 2 days with enough impressions in the last 7 days of final data.                  |
| **Split** badge              | A second page of yours got a quarter or more of the impressions on at least 2 such days. Impressions are split between two pages.         |
| Low data icon                | Some days had fewer impressions than the thin threshold and were left out of the averages.                                                |
| **Pulling history…**         | The keyword was just added and its 16 months are still downloading.                                                                       |
| **Not seen by Google yet**   | Google recorded no impressions for it in this market. It may not rank, may rank beyond about position 100, or may be an anonymised query. |
| **CTR gap** badge            | The 28-day CTR is under half of what your site usually gets at that position. See [CTR gap](#ctr-gap).                                    |

### Search, filters and bulk actions

* **Search** finds keywords and rules by name.
* **Tags** (1) and **Band** (2) sit next to the search box. Band shows only items in one position band. Tags you add when you paste keywords (see [Create a tracker](/guide/google-search-console/gsc-rank-tracker/create-a-tracker)) appear here too, so you can, for example, compare your keywords with your competitors'. Topics made by [Group with AI](/guide/google-search-console/gsc-rank-tracker/ai#group-with-ai) have their own **Topics** group.
* **Page** sits after Band. Pick one page to list only the keywords Google shows for it. The list starts with **All pages**, then the 20 pages with the most keywords, each with its keyword count. Type part of an address to find any other page: when more pages match, a line under the list says "Showing 20 of 61 pages. Type to narrow the list." The filter also applies to the Grid view and to **Export CSV…**, so an export from a page's list holds only its keywords. The Pages tab sets it for you with **Show keywords**: see [Opportunities per Page](/guide/google-search-console/gsc-rank-tracker/opportunities-per-page).
* **Advanced** (3) holds **Flags** (4: **Split**, **Wrong page**, **Low data**, **Fresh**, **Not seen by Google**, **CTR gap**, and **Big gap** while a report is linked), **Type** (**Keywords** or **Rules**), **Archived** and **Source** (5, the source of a keyword's volume). The button shows how many of them are active.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-72bdef19cf3e4bc736b51f7468b64b7fd35500d1%2Fgsc-rankings-keywords-filters.png?alt=media" alt="The Advanced filters panel with Flags set to CTR gap, Type, Archived and Source, and the filtered keywords below"><figcaption><p>Advanced filters: the Flags (4) and Source (5) filters, here showing only keywords with a CTR gap</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-253f99801e7d8cdf6b2300c84daa300d3d683501%2Fgsc-rank-tracker-page-picker.png?alt=media" alt="The Page filter open on the Keywords tab with a search field, pages with their keyword counts and the line Showing 20 of 61 pages"><figcaption><p>The Page filter: its search field (1), a page with its keyword count (2) and the line that appears when more pages match (3)</p></figcaption></figure>

Tick rows to use the bulk actions: **Tag…**, **Set target…**, **Archive**, **Check live SERP…**, **Send to rank tracker**, **Export selected…**, **Group with AI…** and **Check metrics**. **Check live SERP…** and **Send to rank tracker** are explained in [Compare with Organic Rank Tracker](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#check-a-live-serp), which also lists [what a team member needs](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#team-members) for each. Archiving keeps the history, and you can restore items from the **Archived** filter. In the archived view you can also **Restore** or **Delete permanently…**. Use **Add keywords** above the table to add more keywords or rules with the same tabs as the wizard. Its arrow also holds **Group with AI…** (see [AI](/guide/google-search-console/gsc-rank-tracker/ai#group-with-ai)) and **Check metrics for missing…**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6be281d22c5ddd25b7809931d3b61e9bf77c1d7a%2Fgsc-rankings-add-keywords-dialog.png?alt=media" alt="The Add keywords dialog with the paste, suggestions and rules tabs"><figcaption><p>Add keywords to a tracker later</p></figcaption></figure>

Keywords the tracker already has stay ticked in the dialog. To stop tracking one, archive it in the table.

### CTR gap

A **CTR gap** badge next to a keyword's CTR says its clicks are low for where it ranks: the 28-day CTR is under half of the CTR your site usually gets at that position, with at least 100 impressions in 28 days. It is a hint to look at the page's title and snippet.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2542b172737e6f12e3fa2c9d0c0a5c8584c0d828%2Fgsc-rankings-ctr-gap.png?alt=media" alt="Keywords with a CTR gap badge and the tooltip that explains it"><figcaption><p>The badge (1) and its tooltip (2)</p></figcaption></figure>

* Each tracker works out its own expected CTR for every position from the last 90 days of your queries in that market, leaving out branded queries. It is refreshed about once a week, at the end of a refresh. Until the first one exists, no badge shows and the CTR tooltip says "CTR curve not computed yet".
* Hover the badge for the numbers, for example "At position 21+ your site usually gets 1.3 % CTR; this keyword gets 0.6 %". When a position has too few queries to measure, the tooltip says "estimated from neighbouring positions" or "generic curve", a standard curve SEO Utils uses instead.

### Volume and Opportunity

**Volume** is the keyword's monthly Google searches in the tracker's market, with the source and the date it was checked, for example "Labs · Oct 26". **Opportunity** estimates the extra clicks a month if the keyword reached the top 3: its volume times the CTR your site usually gets in the top 3, minus the clicks it gets now. Hover it to see the sum. A keyword already in the top 3 shows +0, and a rule shows a dash because both figures apply to single keywords.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c2bb0c6af3c4f3cdb664c603094812ee11e5870f%2Fgsc-rankings-volume-opportunity.png?alt=media" alt="The Keywords table sorted by Opportunity, with the Volume and Opportunity columns"><figcaption><p>Volume (1) with its source (3), and Opportunity (2)</p></figcaption></figure>

Volumes come from your keyword metrics, so a keyword you already checked elsewhere shows a figure. **Check metrics** fills the missing ones and spends credit.

{% stepper %}
{% step %}

#### Start the check

Tick keywords and choose **Check metrics** in the bulk actions, or open the arrow beside **Add keywords** and choose **Check metrics for missing…** to cover every active keyword.
{% endstep %}

{% step %}

#### Confirm the price

Choose the **Keyword metrics source** (1), read the estimate (2) and click **Check metrics** (3). **Only Check Keywords Missing Search Volume Data** is on by default, so only keywords without a volume are checked. See [Keyword Metrics Data Source](/guide/keyword-metrics-data-source) for the sources and their prices.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c7598dc66e0dde0f523fc3b9977c45e04b8dff74%2Fgsc-rankings-check-metrics-dialog.png?alt=media" alt="The Bulk Check metrics dialog with the source, the estimate and the Check metrics button"><figcaption><p>Source (1), estimate (2) and the button that spends credit (3)</p></figcaption></figure>
{% endstep %}
{% endstepper %}

The dialog names the market it checks, for example "United States · English". A country tracker uses that country with the property's language. A Worldwide tracker uses the property's own country and language. Sort by **Volume**, **Opportunity** or the source, and filter by source in **Advanced**. The CSV export adds a **Volume Source** column next to the volume.

### Opportunity without a search volume

A keyword with no search volume still gets an Opportunity when it is on page 1: its **Pos** is 10 or better, counted from days with enough impressions. SEO Utils then uses the keyword's impressions over 28 days in place of the volume. The cell reads the same, and its **Volume** keeps its dash. Hover the Opportunity to see which figure it used: the tooltip starts "Estimated from impressions, because this keyword has no search volume:".

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f5c70fb04102a8bdca029f462856235fe1ec18c7%2Fgsc-rank-tracker-opportunity-impressions-tooltip.png?alt=media" alt="The tooltip of an Opportunity that is estimated from impressions, on a keyword whose Volume is a dash"><figcaption><p>An Opportunity (1) on a keyword without a Volume, and the tooltip that names its source (2)</p></figcaption></figure>

* **Below page 1**, a keyword without a volume still shows "—", because impressions understate the demand there.
* **A search volume always wins.** A keyword with one uses it on any page.
* **The CSV export** adds an **Opportunity Source** column after **Opportunity**, reading "Search volume" or "Impressions".

### Rules

A rule appears as one row with a **Query rule** or **Page rule** badge. Click the arrow to open its member queries.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3d5616076a0167a9271ec06428ef142253ae127d%2Fgsc-rankings-keywords-rule-members.png?alt=media" alt="An expanded page rule listing member queries with a Track individually button"><figcaption><p>Open a rule to see its queries and track any of them on its own</p></figcaption></figure>

The list shows each query's position, impressions, first and last seen dates and, for a page rule, the matching pages. Click **Track individually** to give a query its own row with its own history. A rule lists a query once it has enough impressions in 28 days; change that minimum in the tracker [settings](/guide/google-search-console/gsc-rank-tracker/manage-trackers#settings).

## Grid view

Switch from **Table** to **Grid** to see each keyword's position day by day, like a heat map. Choose **Auto**, **Day**, **Week** or **Month** for the columns. Auto uses days for ranges up to 60 days, weeks up to a year, and months beyond that.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1ec271c6d783212fe406a7310bb3210a9d198baf%2Fgsc-rankings-keywords-grid.png?alt=media" alt="The Grid view with the colour legend and daily positions"><figcaption><p>The Grid: one cell per keyword per day</p></figcaption></figure>

The legend above the grid explains the cells:

* The colour shows the position band: **1**, **2–3**, **4–6**, **7–10**, **11–15**, **16–20**, **21–50**, **51–100** and **101+**.
* A faded cell with a dashed outline is a **Low data** day.
* A hatched cell is **Fresh**, provisional data.
* A dash means no impressions that day.
* An orange dot means **Page differs**: Google showed another page than your target.
* A coloured stripe above a column marks a Google update or one of your notes.

The **Δ** column shows the change over the range.

## Best practices

* Read the **Pos** number together with its **Trend**. One bad day matters less than a steady slide.
* Treat low data keywords with care. Their position can swing on a few impressions.
* Set a **target page** on keywords that matter, so a page swap shows up as a flag.


# Keywords in the Top 1, 3 and 10

The **Keywords in the top 1, 3 and 10** card sits under the [position bands](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#position-bands-chart) chart. It counts how many of your keywords are in the top 1, the top 3 and the top 10 over time, next to the clicks and impressions of the same keywords. Link an [Organic Rank Tracker](/guide/organic-rank-tracker) report and the card draws the same counts from that report too, so you can see how far the two sources agree.

{% hint style="info" %}
The **rank tracker** is the report linked to the tracker, whether it collects positions with DataForSEO, proxies or your own IP. Reading the card costs nothing.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2b9c9d909779c0c44567e83ff224f7a4cb5ab2f8%2Fgsc-rank-tracker-top-counts-card.png?alt=media" alt="The Keywords in the top 1, 3 and 10 card with solid and dashed lines, the Clicks and Impressions bars, the legend and the four gap tiles"><figcaption><p>The card: the keyword picker (1), the Clicks &#x26; impressions switch (2), the newest final figure of a strip (3) and the legend (4)</p></figcaption></figure>

## Read the chart

* **Lines.** Each line counts keywords: Top 1, Top 3 and Top 10. Top 3 includes Top 1, and Top 10 includes both.
* **Solid or dashed.** Search Console is solid and the rank tracker is dashed, so you can tell them apart without colour.
* **Same keywords on both sides.** With a link, both sources count only the keywords that are in both. Without one, the card counts every active keyword of the tracker. Rules are not counted.
* **Same dates as the band chart.** The card uses the page's date range and groups days into weeks or months the way the band chart does. The band chart's **Markers** switch also shows Google updates and your notes here.
* **Recent days.** The Search Console lines stop at the last final day instead of dropping to zero. A day without impressions counts as No data, never as a low position.
* **Gaps in the dashed line.** A period with no check from the report leaves a gap. A report that checks weekly shows one ring per check while the chart is by day. Choose a longer range, such as **Last 90 days**, to draw dashed lines.

Hover a period for its Top 1, Top 3 and Top 10 for each source, its clicks and impressions, **Keywords with data** and, for the rank tracker, how many keywords it checked and the date of its latest check.

### Clicks and impressions

The **Impressions** and **Clicks** bars sit under the chart on the same dates. The number beside each title is the newest final figure with its date, for example **1,240 (Oct 28)**. It reads a dash when no day in the range has final data. Turn off the **Clicks & impressions** switch to hide the bars.

## Choose what you see

| Control                    | What it does                                                                                                                                                                                                                                                                                                                                  |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **All keywords**           | Pick a tag or topic to count only the keywords that have it.                                                                                                                                                                                                                                                                                  |
| **Page**                   | Pick a page to count only the keywords Google shows for it. The position bands chart uses the same page: see [Filter the charts by page](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#filter-the-charts-by-page). With a linked report, the **Rank tracker** lines count only the page's keywords that the report tracks. |
| **Legend**                 | Click Top 1, Top 3, Top 10, **Search Console** or **Rank tracker** to hide it, and again to show it. One line always stays visible. **Show all** brings everything back.                                                                                                                                                                      |
| **Arrow** at the top right | Hides the card.                                                                                                                                                                                                                                                                                                                               |

The card remembers these choices for you, tracker by tracker, except the page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-74ef41201605ccb864f9ede30c59c7db25f1e4b9%2Fgsc-rank-tracker-top-counts-page-filter.png?alt=media" alt="The card with the Page picker set to one page, solid and dashed lines for its keywords and the gap tiles"><figcaption><p>The Page picker (1) with a page chosen, the dashed Rank tracker lines (2) and the tile that says how many of the page's keywords the report tracks (3)</p></figcaption></figure>

## Compare the two sources

While a report is linked, four tiles under the chart sum up how far the sources are apart. Hover the **?** of a tile for its definition and the date it is measured at.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b41fdfee252cde647dba51cab7cda5cfdf1668fd%2Fgsc-rank-tracker-top-counts-gaps.png?alt=media" alt="The four gap tiles and the Why do the lines differ popover"><figcaption><p>The gap tiles (1–4) and the explanation that <strong>Why do the lines differ?</strong> opens</p></figcaption></figure>

| Tile                     | What it tells you                                                                                                                         |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Average gap** (1)      | Search Console's position minus the rank tracker's, averaged over the keywords that have both. Positive means Search Console reads worse. |
| **Typical gap** (2)      | The middle distance between the two positions, whichever source reads better.                                                             |
| **Same order** (3)       | How alike the two rankings are, from 1 (the same order) through 0 (no relation) to −1 (reversed). It needs at least 5 keywords.           |
| **Keywords in both** (4) | For example **45 of 60**, with how many keywords are not in the report.                                                                   |

The tiles use the same **Pos** and **SERP** numbers as the **Gap** column of the [Keywords table](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#compare-in-the-keywords-table), over every keyword of the card rather than one page of rows.

**Why do the lines differ?** explains it in three sentences. Search Console averages every search that showed your site, from every city and every searcher. The rank tracker checks one results page per keyword, signed out, for the report's location. A gap is normal, and the rank tracker often reads better, so compare each line with itself over time.

## Add rank tracker lines

A tracker without a usable link shows the Search Console lines and an invitation to link a report. **Link a report** opens the tracker's settings at **Rank tracker link**; see [Link a report](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#link-a-report).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2a4c3c2c68fd657e0b6e432fdb1e6e44d700e248%2Fgsc-rank-tracker-top-counts-unlinked.png?alt=media" alt="The card of a tracker without a link, with the invitation and the Link a report button"><figcaption><p>The invitation (1) and the <strong>Link a report</strong> button (2)</p></figcaption></figure>

* The button shows only to people who can open **Settings**; everyone else sees the sentence alone.
* Image, Video and News trackers show Search Console lines only, with a note that the comparison covers Web results only.
* If the linked report was deleted or no longer matches the tracker's market, the card says **Compare is off** and gives the reason.

## In the report

The [report and PDF](/guide/google-search-console/gsc-rank-tracker/print-and-pdf#what-the-report-holds) include this card as a section after the position bands.


# Keyword Details

Click a keyword in the Keywords table, a row in [Movers](/guide/google-search-console/gsc-rank-tracker/movers), or **Open** on an [alert](/guide/google-search-console/gsc-rank-tracker/alerts) to open its details panel. It shows how one keyword moved day by day, which pages Google showed for it, and the numbers behind every day.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6ab2d475c04dc73a5aeccbec37ee836fcaac3c77%2Fgsc-rankings-drawer-chart.png?alt=media" alt="The keyword details panel with the header strip, the chart and the day card"><figcaption><p>The details panel: header strip, chart and a day card</p></figcaption></figure>

## Header

The top line names the keyword's market. Under the keyword, **Open in Performance** opens the same keyword in the Performance report, and **Why did it move?** asks AI to explain the position (see [below](#why-did-it-move)).

{% hint style="info" %}
Performance shows page-level data, so its average can differ from this tracker's number.
{% endhint %}

A strip of three figures sits below. Each label has a (?) that explains it, and the coloured dash in front of **Position** and **Target page** is the colour of that line in the chart.

| Figure           | What it shows                                                                                                                    |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Position**     | The average of the keyword's best spot over its last 7 days with enough impressions, up to the end of the chosen period.         |
| **7-day change** | How much the position changed against 7 days earlier. An arrow means under half a position, which is not a move.                 |
| **Target page**  | The one page you chose to rank for this keyword, with **Set target…** to change or remove it. It shows "None" until you set one. |

If Google now shows a different page than your target, a notice says so and offers **Make target** to switch the target to that page in one click.

## Why did it move?

The **Why did it move?** panel sits above the chart. Click **Explain** and AI writes two or three sentences from this keyword's own data: its positions, confirmed moves, page changes, Google updates and your notes. Each sentence is backed by an evidence line with a date chip, and a click on a chip shows that day on the chart.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6537d7c891a6e175d6cabcdf4bf9bb06d5563bd7%2Fgsc-rankings-ai-why-answer.png?alt=media" alt="An AI answer in the keyword details with three evidence lines and the Written by AI footer"><figcaption><p>The answer (1), its evidence (2) and who wrote it (3)</p></figcaption></figure>

The answer is saved, and asking again when nothing has changed sends nothing. It works for rules too. See [AI: Explanations, Summary and Topics](/guide/google-search-console/gsc-rank-tracker/ai#why-did-it-move) for the model, the cost and the details.

## Chart

The chart plots the position for each day, with position 1 at the top. Choose the period with **30 days**, **90 days**, **6 months**, **16 months** or **All**.

* **Best spot** is your keyword's best position that day across all your pages, whichever one Google showed. It is the number the Keywords table is built from.
* **Target page** is the position of the page you chose as the target, from Google's page-level data. It only appears when the keyword has a target. Choose **Best spot**, **Target page** or **Both** to compare them. The (?) next to the toggle explains the two lines.
* **Clicks & impressions** adds two small bar charts under the chart.
* **Markers** shows Google updates and your notes, and **Add note** adds a new one.
* **Rank tracker** and **Live checks**, in the legend, appear when the linked report tracks the keyword, or after a live check. They plot the Organic Rank Tracker's positions as orange dots and the live checks as violet diamonds. See [Compare with Organic Rank Tracker](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#keyword-drawer).

With a connected [GA4 property](/guide/google-analytics-4), two small bar charts, **Page sessions** and **Page key events**, sit under the chart with the page's organic traffic for each day. A line above them names the page they read: the target page, otherwise the page Google shows. GA4 counts each day in the property's time zone, while the chart's days are Pacific time. As in the [Keywords table](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#page-sessions-and-key-events), the figures cover every keyword the page ranks for, not only this one.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-40cad83cc60e54f0c9aee36d889c7de7e2111347%2Fgsc-rankings-drawer-page-traffic.png?alt=media" alt="The keyword details chart with the Page sessions and Page key events bar charts under the position line"><figcaption><p>The page that is read (1), its Page sessions (2) and its Page key events (3)</p></figcaption></figure>

On a line, a solid stretch is final data, faded dots are low data days, a dashed stretch is fresh data that Google can still revise, and a hatched area is a period Google no longer provides. The legend under the chart names every mark, each with its own (?).

Hover a day to open its card. It shows the **Best spot** and **Target page** positions with their impressions and clicks, and **Page Google showed**: the page that got the most impressions that day. If Google showed a page other than your target, the card says so with an orange dot.

{% hint style="info" %}
Google counts a page's impressions separately, so the Target page impressions can differ slightly from the Best spot impressions.
{% endhint %}

## Pages

The **Pages** tab lists every page Google showed for the keyword in the period.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a83afe4492d9a7e9a3711c2eb731da17ec96ed23%2Fgsc-rankings-drawer-pages.png?alt=media" alt="The Pages tab listing two pages with position, share and clicks"><figcaption><p>The Pages tab</p></figcaption></figure>

| Column                        | What it shows                                               |
| ----------------------------- | ----------------------------------------------------------- |
| **Page**                      | The page path. Your target page carries a **Target** badge. |
| **Pos**                       | Its average position.                                       |
| **Share**                     | Its share of the keyword's impressions.                     |
| **Clicks**                    | Clicks it received.                                         |
| **First seen**, **Last seen** | The first and last day Google showed it.                    |

Click **Make target** on a row to use that page as the keyword's target.

## Days

The **Days** tab lists every day of the period, newest first.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8f8dd1f5c0dfccd15efdde12e4e69fcd045c78a4%2Fgsc-rankings-drawer-days.png?alt=media" alt="The Days tab with one row per day and Fresh labels on the newest days"><figcaption><p>The Days tab</p></figcaption></figure>

| Column                         | What it shows                                                                      |
| ------------------------------ | ---------------------------------------------------------------------------------- |
| **Date**                       | The day in Pacific Time, with labels such as **Fresh** or low data for those days. |
| **Best spot**                  | The keyword's best position that day. Hatched cells are fresh data.                |
| **Target**                     | The target page's position, when you set a target.                                 |
| **Page**                       | The page Google showed most that day.                                              |
| **Impr.**, **Clicks**, **CTR** | Impressions, clicks and click-through rate.                                        |

Each of **Best spot**, **Target** and **Page** has a (?) with its definition. Sort any column, for example by **Best spot** to find the best and worst days.

## SERP checks

The **SERP checks** tab lists the paid **Live checks** of the keyword and the **Rank tracker snapshots** of the linked Organic Rank Tracker report. **Check live SERP**, next to **Open in Performance**, starts a live check on a Web tracker. See [Compare with Organic Rank Tracker](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#check-a-live-serp). A team member of any role can read the tab; starting a check needs **Run reports** and **Can use the owner's machine and accounts** (see [Team members](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#team-members)).

## Set a target page

A target tells the tracker which page should rank for a keyword. It then flags the days Google shows another page, and can send a **Wrong page** alert.

{% stepper %}
{% step %}

#### Open Set target

Use **Set target…** in the details panel, in the row menu of the Keywords table, or tick several keywords and use **Set target…** in the bulk actions.
{% endstep %}

{% step %}

#### Enter the page

Enter the full URL of a page of the property. The page must belong to the property. Leave the field empty to remove the target. Click **Set target**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-51f3f694d1d8bbf06be6186cbcb6bc96a635c2de%2Fgsc-rankings-set-target-dialog.png?alt=media" alt="The Set target dialog with a page URL"><figcaption><p>Set the page you want to rank</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Rules

A rule opens with the same panel. The chart shows the rule's combined **Group position**. A rule has no pages list of its own: its pages are listed per member query, so use **Track individually** on a member query to give it a row and see its pages.


# Compare with Organic Rank Tracker

Search Console tells you where Google says you rank on average. An [Organic Rank Tracker](/guide/organic-rank-tracker) report tells you where a search result check found you. Link a report to a tracker to see both numbers side by side, spot the keywords where they disagree, and run a paid live SERP check when you want to look at one results page yourself.

{% hint style="info" %}
You need an Organic Rank Tracker report in the same workspace that tracks the same site. It can collect positions with DataForSEO, proxies or your own IP: the comparison reads its stored checks and works the same way for all three. Linking and comparing cost nothing. [Check live SERP](#check-a-live-serp) always spends DataForSEO credit, and it asks first. [Team members](#team-members) can compare and, with the right role, link a report and run live checks.
{% endhint %}

## Link a report

{% stepper %}
{% step %}

#### Open the link section

On the Rankings page, click the tracker's name at the top, choose **Settings** and scroll to **Rank tracker link**. On a tracker without a link, the **Link a report** button of the [**Keywords in the top 1, 3 and 10** card](/guide/google-search-console/gsc-rank-tracker/top-1-3-10#add-rank-tracker-lines) opens the same place.
{% endstep %}

{% step %}

#### Choose a report

Click **Link a report…** (1). The list shows every report of the workspace for this site, with the keywords it tracks and when it last ran. Pick one.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-828ee980871c5549159387cb5f6455392e74555a%2Fgsc-rankings-ort-link-picker.png?alt=media" alt="The report picker with a compatible report, a City-level ORT chip and a refused report with its reason"><figcaption><p>Each report is compatible, partly compatible or refused</p></figcaption></figure>
{% endstep %}
{% endstepper %}

SEO Utils checks the report against the tracker's market:

| Result                    | What you see                                                                                               | What it means                                                                                                    |
| ------------------------- | ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Compatible** (2)        | The report name                                                                                            | Same site, country, device and search engine, and the tracker is a Web tracker.                                  |
| **Partly compatible** (3) | An amber chip, such as **All devices**, **Worldwide tracker**, **City-level ORT** or **Narrower property** | You can compare, but the two sources do not measure exactly the same thing. Hover a chip to read why.            |
| **Refused** (4)           | The report is greyed out with a reason                                                                     | For example: the tracker is not a Web tracker, the report tracks another search engine, site, country or device. |

Once linked, the section shows the report with **Change…** (1), **Unlink** (2, it asks first) and **Pull new ORT keywords** (3). A chip next to the market chips in the page header, **Compared with** followed by the report name, shows the link at all times.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-eaffb4381f38e073b016d56b0a70c499306ddb6c%2Fgsc-rankings-ort-link-settings.png?alt=media" alt="The linked report in the settings sheet with Change, Unlink and Pull new ORT keywords"><figcaption><p>A linked report</p></figcaption></figure>

**Pull new ORT keywords** adds the report's keywords that the tracker does not have yet and downloads their history. Archived keywords stay archived.

{% hint style="warning" %}
If the report is deleted or moved to another workspace, the header chip turns red and says **Linked report missing**, and the comparison stops. Link another report or click **Unlink**.
{% endhint %}

### In the New tracker wizard

On the first step, **Start from an Organic Rank Tracker report** copies a report's keywords and market and links it. On the **Review** step, **Rank tracker report** (1) shows the link: SEO Utils suggests the first compatible report for the market, and you can **Change…** (2) or **Unlink** (3) it before you click **Create tracker**. A refused report blocks **Create tracker** until you change or unlink it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1d1fc96963cfe5b53b8501e41998292f25d722bc%2Fgsc-rankings-wizard-review-link.png?alt=media" alt="The Review step with a compatible Organic Rank Tracker report, Change and Unlink"><figcaption><p>The Review step of the wizard</p></figcaption></figure>

## Compare in the Keywords table

While a usable report is linked, the [Keywords table](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#keywords-table) gains a **Compare** filter (1) beside **Tags** and **Band**, and two columns, **SERP** (2) and **Gap** (3).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-baf76f6866c2c11a8b4dfda79b8dcf807e9b0290%2Fgsc-rankings-compare-table.png?alt=media" alt="The Keywords table with the Compare filter and the SERP and Gap columns"><figcaption><p>The Compare filter and the SERP and Gap columns</p></figcaption></figure>

| Item                          | What it shows                                                                                                                                                                                                                                                                                                        |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Compare** > **All**         | Every keyword, as without the filter.                                                                                                                                                                                                                                                                                |
| **Compare** > **Big gaps**    | Only the keywords with a big gap. The **Big gap** option in **Advanced > Flags** does the same.                                                                                                                                                                                                                      |
| **Compare** > **Only in GSC** | Keywords with a Google position that the report's newest check did not find.                                                                                                                                                                                                                                         |
| **Compare** > **Only in ORT** | Keywords the report found but that have no Google position, usually because of too few impressions.                                                                                                                                                                                                                  |
| **SERP**                      | The report's position for the keyword on its newest check. **NR** (not ranked) means the report did not find your site; hover it to read **Not in top 100**, the report's depth. A dash means there is nothing to compare: the report does not track the keyword, or the row is a rule. Hover the dash to see which. |
| **Gap**                       | The distance between **Pos** and **SERP**. It is highlighted (4) when it is a big gap: at least 5 positions and at least 30 % of the position, on both of the last two checks of the report.                                                                                                                         |

Both sources can be days apart, so open a column's menu and hover **What is this?** (1): the tooltip states the report's check date (your time) and the Search Console date (Pacific). The comparison uses the newest check of the report on or before the last final Search Console day.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fde3b2ac0fe77b9dbf5467d77e8af5dae2740f13%2Fgsc-rankings-compare-column-help.png?alt=media" alt="The What is this tooltip of the SERP column with both dates"><figcaption><p>The tooltip names both dates</p></figcaption></figure>

### Gap hints

Small icons beside a gap mean SEO Utils found a likely reason, and each kind of hint has its own icon. The cell shows at most two, then **+n** for the rest. Click the cell (1) to read them all. They are plain rules, not AI guesses.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ff8fa10ca3dfdc18172626317244e3bbe8f2140d%2Fgsc-rankings-compare-gap-hints.png?alt=media" alt="The Gap popover with Different page, Low GSC data and Features above you hints"><figcaption><p>Click a Gap cell to read its hints</p></figcaption></figure>

| Hint                       | What it tells you                                                                                          |
| -------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **SERP layout**            | The features the report recorded in the results, such as a local pack or People also ask.                  |
| **Different page** (2)     | The report ranked another page than the one Google showed most.                                            |
| **Markets differ**         | The link is partly compatible, for example the report checks one device and the tracker mixes all of them. |
| **Low GSC data** (3)       | Some Search Console days had too few impressions to count.                                                 |
| **Features above you** (4) | A [live check](#check-a-live-serp) found SERP features above your result.                                  |

## Compare over time

The table compares one keyword at a time. The **Keywords in the top 1, 3 and 10** card under the band chart compares the whole keyword set over time: how many keywords each source puts in the top 1, 3 and 10, next to clicks and impressions. Four gap tiles sum up the **Gap** column for the whole set. See [Keywords in the Top 1, 3 and 10](/guide/google-search-console/gsc-rank-tracker/top-1-3-10).

## Keyword drawer

The [keyword details](/guide/google-search-console/gsc-rank-tracker/keyword-details) chart adds the report's checks as orange dots, plotted by date. A hollow ring at the bottom means **Not in top 100**. The **Rank tracker** entry in the legend (1) switches the dots on and off. Live checks appear as violet diamonds, named by **Live checks** (2) in the legend. **SERP checks** (3) opens the data behind them, and **Check live SERP** (4) starts a paid check.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-67840e0df088e3e9e62a640e72e8b248b588775a%2Fgsc-rankings-drawer-compare-chart.png?alt=media" alt="The keyword chart with orange rank tracker dots, a violet live check diamond and the legend"><figcaption><p>Rank tracker dots and a live check diamond</p></figcaption></figure>

The **SERP checks** tab lists **Live checks** (1), the paid checks of this keyword, and **Rank tracker snapshots** (3), one row per check of the report with its position and page. Click the date of a live check (2) to open it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-86af9369e6b46425300574dfbd57b6770eb72fe0%2Fgsc-rankings-drawer-serp-checks.png?alt=media" alt="The SERP checks tab with one live check and the rank tracker snapshots"><figcaption><p>The SERP checks tab</p></figcaption></figure>

## Check a live SERP

A live check reads the Google results for one keyword right now through DataForSEO and tells you where your site stands and what surrounds it. It is useful for a keyword with a big gap.

{% stepper %}
{% step %}

#### Start the check

Click **Check live SERP** in the keyword drawer (also under "No live checks yet." on its **SERP checks** tab) or in the row menu. To check several keywords, tick them and use **Bulk Actions > Check live SERP…** (up to 500 at a time).

On an **All devices** tracker the dialog asks you to choose **Desktop** or **Mobile**, because a live check looks at one device. Other trackers use their own device.
{% endstep %}

{% step %}

#### Read the estimate

The dialog shows the location, language and device it will use, and the estimated cost (1, 2). Nothing is spent until you click the button at the bottom (3), which names the maximum cost, such as **Check 1 keyword live (up to …)**. **Cancel** sends nothing.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-26c869590345500271c6483f036c470b58e5bc2f%2Fgsc-rankings-live-check-dialog.png?alt=media" alt="The Check live SERP dialog with the price line, the estimated total and the confirm button"><figcaption><p>The estimate comes first</p></figcaption></figure>
{% endstep %}

{% step %}

#### Read the result

A message tells you the position and the cost DataForSEO charged. The result is also a diamond on the chart, a row in **Live checks** and, when there are SERP features above you, the **Features above you** hint.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**What it costs.** DataForSEO's list price (October 2026) is about $0.002 per 10 results, so a check at the default depth of 100 results costs at most **$0.02** per keyword. A keyword with a search operator such as `site:` or `intitle:` costs 5 times as much, and the dialog says so. DataForSEO refunds the result pages Google does not return, so the real charge can be lower. It is recorded on each check.
{% endhint %}

Live checks work on **Web** trackers only: on an Image, Video or News tracker the action is not offered, and the keyword drawer shows it greyed out. You also need DataForSEO credentials in SEO Utils, as described in [SEO Data Source](/guide/seo-data-source#how-to-connect-your-dataforseo-account-to-seo-utils).

### Read a live check

In **SERP checks > Live checks**, each row shows the date, device, **Position**, **Absolute** (the place on the page counting every element, not only organic results), the page, **Features above**, **Cost** and **Status**. Click a date to open the check. In these tables, a position your site did not reach reads **NR**, with **Not in top 100** on hover; the chart and the details keep the full text. In the Keywords table, **Latest live check** in a row's **⋯** menu opens the newest check of that keyword; it is greyed out until you have run one.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b886e0a9289329b973ed9b1250018d6cb908ed6c%2Fgsc-rankings-live-check-detail.png?alt=media" alt="A live check with Your result, SERP features marked above you and the top 10 organic results"><figcaption><p>The details of one live check</p></figcaption></figure>

* **Your result** (1) is your position and page, with its title, or "not in the top 100".
* **SERP features** (2) lists each feature with its place on the page. **above you** marks the ones that push your result down.
* **Top 10 organic results** lists the first results of the check, each with its title above its domain and path (a long title is cut, and hovering shows all of it). Your own row is highlighted and marked **Your site**. **Show all** (3) expands the list to every result the check kept, up to 100, with your row highlighted even beyond the tenth; **Show top 10** collapses it. A check made before this option existed kept only the top 10; the detail says so when your site is not among them.
* **Check again** starts a new check, with its own estimate and confirmation.

If a check ends as **Answer lost**, DataForSEO's answer did not reach SEO Utils and the check may have been charged. It is never sent again automatically.

## Send keywords to the rank tracker

A keyword Google has not shown your site for recently has no Search Console position. To find out where it ranks, send it to an Organic Rank Tracker report.

{% stepper %}
{% step %}

#### Find them

Open **Advanced** and choose **Not seen by Google** in **Flags**. It lists keywords with no impressions in this market in the last 28 days. The (?) beside it lists the usual causes: the site does not rank for it, it ranks beyond about position 100, or Google anonymises the query.
{% endstep %}

{% step %}

#### Send them

Tick the keywords, open **Bulk Actions** and choose **Send to rank tracker**, then click **Send to rank tracker** (4) in the dialog. The linked report is already selected (1). Without a link, pick the report yourself.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1a6b6e12cba53f38db809fe637f2ad3b97d845c8%2Fgsc-rankings-send-to-rank-tracker.png?alt=media" alt="The Send to rank tracker dialog with the report, the keywords and the rerun switch"><figcaption><p>Send the selected keywords to a report</p></figcaption></figure>

* You can edit the keyword list (2) in the dialog.
* A selected rule is not sent, because the rank tracker checks single keywords. A note at the top of the dialog names the rule and tells you to expand it and use **Track individually** first. Keywords that contain a comma are left out too, and the note counts them.
* **Rerun Tracker After Adding Keywords** (3) is off. Switch it on to check the new keywords now; for a report that scrapes with DataForSEO this is a paid check of every keyword that is not up to date.
  {% endstep %}
  {% endstepper %}

Once the linked report has checked them, the keywords show their **SERP** position in the table.

## Team Members

[Team members](/guide/team) use the comparison in the browser, in the workspaces you gave them. Their [role](/guide/team/inviting-your-team#roles) decides how far:

| What                                                                                                                                                                                                                           | What it needs                                                                                                                             |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| See the **Compared with** chip, the **Compare** filter, the **SERP** and **Gap** columns, the rank tracker lines and gap tiles of the top 1, 3 and 10 card, the chart dots, the **SERP checks** tab and the stored live checks | Any role, from Viewer up                                                                                                                  |
| **Link a report…**, **Change…** and **Unlink**                                                                                                                                                                                 | A Manager, or a Custom role with **Create and edit reports**                                                                              |
| **Send to rank tracker**                                                                                                                                                                                                       | The same. Its **Rerun Tracker After Adding Keywords** switch also needs **Run reports** and **Can use the owner's machine and accounts**. |
| **Pull new ORT keywords**                                                                                                                                                                                                      | The same, plus **Run reports** and **Can use the owner's machine and accounts**, because it downloads history from Google.                |
| **Check live SERP**, to see the estimate                                                                                                                                                                                       | **Run reports**: an Analyst or a Manager                                                                                                  |
| **Check live SERP**, to confirm and send                                                                                                                                                                                       | **Run reports** and **Can use the owner's machine and accounts**: by default an Analyst or a Manager                                      |

A control a person cannot use is greyed out with the reason, such as **Needs Manager access** or **Ask {your name} for run access**. **Settings** is greyed out for a Viewer or an Analyst, so the link section is for editors; everyone else still sees the **Compared with** chip. The card's **Link a report** button shows only to people who can open **Settings**.

A team member's live check shows the same estimate first and uses your DataForSEO account. You see who started it in two places:

* **Spend.** The charge goes to that person; see the [Spend tab](/guide/team/activity-and-spend#spend).
* **Activity.** A **Ran a report** row names the person, with **Checked the live SERP of N keywords** in its details; see [Activity](/guide/team/activity-and-spend#activity).

SEO Utils checks the person's access again before each check is sent. If you take their access away while a batch is waiting, the checks not yet sent are not sent.

## Best practices

* Start with **Big gaps** and read the hints before you decide that one of the numbers is wrong.
* Link a **Compatible** report where you can, and keep live checks for the keywords that matter.


# Opportunities per Page

The **Pages** tab groups your tracked keywords by the page Google shows for them and adds up their [Opportunity](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#volume-and-opportunity). It answers two questions: which of your pages has the most to gain, and which keywords should you work on for it. Reading it costs nothing, because every figure comes from data the tracker already holds.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7091839565479b8bb0ed0074c520a58591251a0a%2Fgsc-rank-tracker-pages-tab.png?alt=media" alt="The Pages tab with the summary line, one row per page, the Opportunity with its second line, the Top opportunity and a Wrong page flag"><figcaption><p>The Pages tab: the summary line (1), an Opportunity with its second line (2), the Top opportunity (3) and a page flag (4)</p></figcaption></figure>

## Read the Pages tab

Open the **Pages** tab, between **Keywords** and **Movers**. It has one row per page of your site that Google shows for your tracked keywords, as of the end of the date range. Change the range above the table and every figure moves with its end date.

* A keyword sits in the row of the page in its **Page** column in the Keywords table. Variants of one address, such as a `?utm=` tail or a trailing slash, share a row.
* Rules are not listed, because a rule has no single page. Archived keywords are left out.
* On a domain property a page reads as host and path, for example `shop.example.com/pricing` and `www.example.com/pricing`, so pages on two subdomains never look alike.

Above the table, a line counts what the rows hold, for example **100 keywords on 61 pages · Opportunity from 63 of them (21 from impressions)**. It adds **6 keywords without a page** when Google showed no page of your site for some keywords in the 59 days before the end date, or their history is still loading. Those keywords are in no row.

| Column                               | What it shows                                                                                                                                                                                                                                         |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Page**                             | The page's path, or host and path on a domain property.                                                                                                                                                                                               |
| **Keywords**                         | How many tracked keywords the page has. It is also a link: click it to open the page's focus list.                                                                                                                                                    |
| **Clicks (28d)** and **Impr. (28d)** | The clicks and impressions of those keywords over the last 28 days, added up. They are the keywords' figures on every page of your site, not only on this one.                                                                                        |
| **Opportunity**                      | The sum of the keywords' [Opportunity](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#volume-and-opportunity), for example **+2,796 est. clicks/mo**, with a second line that says where it comes from.                             |
| **Top opportunity**                  | The keyword with the largest Opportunity: the first one to work on. It shows **+N**, or **+N · from impressions** when its Opportunity is estimated from impressions.                                                                                 |
| **Flags**                            | **Split ×n** and **Wrong page ×n**: how many of the page's keywords have the [flag](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#flags). Both count only days with enough impressions, so a site with few impressions shows none. |

The second line under **Opportunity** tells you how many keywords the figure covers:

| It reads                                  | It means                                                                                        |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------- |
| No second line                            | Every keyword has an Opportunity from its search volume.                                        |
| from 1 of 2 keywords                      | Only some keywords have an Opportunity. The others have no search volume and are not on page 1. |
| 1 of them from impressions                | Every keyword has an Opportunity, and that many are estimated from impressions.                 |
| from 3 of 5 keywords (1 from impressions) | Both of the above.                                                                              |

A **—** means none of the page's keywords has a search volume or a page-1 position, and pages like that sort last. Hover it for the hint, then use **Check metrics** in the Keywords tab to fill the missing volumes.

**Search pages** finds a page by part of its address, and **Tags** keeps the keywords that have any of the tags you pick. Click **Keywords**, **Clicks (28d)**, **Impr. (28d)**, **Opportunity** or **Page** to sort. The default is **Opportunity**, largest first.

With no keywords the tab says "No keywords yet. Add keywords in the Keywords tab." When Google showed no page for your keywords in the 59 days before the end date, it says so instead of listing rows.

## Work on one page's keywords

{% stepper %}
{% step %}

#### Open the page's focus list

Click the **Keywords** count of the row, or open its **⋯** menu and choose **Show keywords**.
{% endstep %}

{% step %}

#### Read the list

The **Keywords** tab opens in the Table view with a **Page** chip for that page. Your **Tags** filter from the Pages tab comes along, and the table is sorted by **Opportunity**, largest first. The number of rows equals the page's **Keywords**, and the first keyword with an Opportunity is its **Top opportunity**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a0ebc0442c8320440d57e75b248842fca02f7785%2Fgsc-rank-tracker-pages-show-keywords.png?alt=media" alt="The Keywords tab with a Page chip, a Tags chip and the table sorted by Opportunity"><figcaption><p>The focus list of a page: the Page chip (1), the Tags chip (2) and the table sorted by Opportunity (3)</p></figcaption></figure>
{% endstep %}

{% step %}

#### Work from the list

The list has every column and bulk action of the Keywords table, such as **Tag…**, **Set target…** and **Check metrics**. **Export CSV…** exports only this page's keywords. Remove the **Page** chip to see every keyword again.
{% endstep %}
{% endstepper %}

## The row menu

The **⋯** menu of a row has three items.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-81b0758676320fe279d3af56307fa2164c1e2db0%2Fgsc-rank-tracker-pages-row-menu.png?alt=media" alt="The row menu with Show keywords, Show in charts and Open page"><figcaption><p>Show keywords (1), Show in charts (2) and Open page (3)</p></figcaption></figure>

| Item               | What it does                                                                                                                                                                                                                                                                                         |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Show keywords**  | Opens the page's focus list. The **Keywords** count of the row does the same.                                                                                                                                                                                                                        |
| **Show in charts** | Shows only this page's keywords in the position bands chart and in the **Keywords in the top 1, 3 and 10** card, opens them if they were hidden and scrolls up to them. See [Filter the charts by page](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#filter-the-charts-by-page). |
| **Open page**      | Opens the page in your browser.                                                                                                                                                                                                                                                                      |

## In the report

The [report and PDF](/guide/google-search-console/gsc-rank-tracker/print-and-pdf#what-the-report-holds) list the ten pages with the largest Opportunity in a **Top pages by opportunity** section.


# Movers

The **Movers** tab lists the keywords and rules whose position really changed between two days: one list for those that improved and one for those that declined. Open it with the **Movers** tab or by clicking **Movers · 7 days** in the [KPI strip](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#kpi-strip).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fccec8820f6596760c60712ad63380afa9444c62%2Fgsc-rankings-movers-tab.png?alt=media" alt="The Movers tab with the Improved and Declined lists"><figcaption><p>Improved and Declined lists for the last 7 days</p></figcaption></figure>

## What counts as a move

Search Console positions jump around from day to day, so one odd day should not count. A move is **confirmed** only when two separate days agree:

* The position crosses the edge of the top 3, top 10 or top 20, or it moves at least your **move threshold** (5 positions by default) away from where the keyword usually sat in the days before.
* The latest **two** days with enough impressions both show the new position.
* Days with low data are skipped.

{% hint style="success" %}
A keyword that sits at position 20, jumps to 1 for one day and falls back never appears here. A keyword that sits at 2.4, then shows 3.6 and 3.7 on the next two days, is confirmed as leaving the top 3.
{% endhint %}

Change the move threshold in the tracker settings. See [Alerts](/guide/google-search-console/gsc-rank-tracker/alerts#move-threshold).

## Choose the range

The range button above the lists shows the dates it compares, for example "Last 7 days · to Oct 11 (final data)". The presets end on the latest final data.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f322d5a0925e82c9701d856b014b21f5da788fe1%2Fgsc-rankings-movers-range.png?alt=media" alt="The Movers range picker with Last 7 days, Last 28 days, Last 3 months and Custom"><figcaption><p>Pick a preset or a custom pair of days</p></figcaption></figure>

* **Last 7 days** (the default), **Last 28 days** and **Last 3 months** end on the latest final date.
* **Custom** compares the positions on two days you pick in the calendar: a start day and an end day. The end day cannot be later than the latest final data.

The line above the lists spells out the comparison, for example "Positions on Oct 4 compared with Oct 11, 2026". The range is remembered for each tracker.

## Improved and Declined

Each list shows these columns:

| Column       | What it shows                                                                                                                    |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------- |
| **Keyword**  | The keyword or rule. Click it to open the [keyword details](/guide/google-search-console/gsc-rank-tracker/keyword-details).      |
| **Position** | The position at the start and at the end of the range, rounded. Hover for the exact values.                                      |
| **Change**   | How many positions it gained or lost. A positive number is an improvement.                                                       |
| **Clicks Δ** | Clicks in the range compared with the same number of days just before it. It reads "new" when there were no clicks before.       |
| **Page**     | The page path Google showed, or "/old → /new" when it switched pages between the two dates. A rule has no page and shows a dash. |

Under the lists, a note counts what was left out, for example "12 skipped for thin data · 3 still loading". Skipped items have too few days with enough impressions at the start or the end of the range. Items still loading are still downloading their history.

{% hint style="warning" %}
If the range overlaps the period when Google logged impressions wrongly in Search Console (May 13, 2025 to Apr 27, 2026), an amber note says so: "Part of this range falls inside a Google Search Console data error, not an SEO Utils problem: Google logged impressions wrongly from May 13, 2025 to Apr 27, 2026, which also affects CTR and average position. Compare with care." A **Read Google's notice** link follows it. The error is in Google's data, not in SEO Utils. See [Before / After](/guide/google-search-console/gsc-rank-tracker/before-after#googles-data-error).
{% endhint %}


# Alerts

Alerts tell you when something real happens to a keyword, so you do not have to watch the table. The tracker checks for alerts after each refresh, and you can read them in the **Alerts** tab, get a desktop notification, or send them by email or webhook with an [automation](/guide/automations).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fd7af442e2d99c587c15a2398b99b6cea72a8324%2Fgsc-rankings-alerts-tab.png?alt=media" alt="The Alerts tab listing recent alerts with their type, positions and page"><figcaption><p>The Alerts tab</p></figcaption></figure>

## When an alert fires

There are six types of alerts. They use final data only, and a position change must hold on two separate days, so a one-day spike never alerts.

| Type                         | Fires when                                                                                                                                         |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Top 3 / 10 / 20 crossing** | A keyword enters or leaves the top 3, top 10 or top 20, confirmed on two separate days.                                                            |
| **Moved**                    | A keyword moves at least the **move threshold** without crossing one of those edges, confirmed on two separate days.                               |
| **Wrong page**               | You set a target page, and Google showed another page on at least 2 days with enough impressions in the last 7 days.                               |
| **Split**                    | A second page of yours got a quarter or more of the impressions on at least 2 such days in the last 7 days.                                        |
| **Vanished**                 | A keyword that had impressions for a while gets none for 7 days. It may have dropped out of the top 100 or become anonymised.                      |
| **New in a rule**            | A new query joined one of your [rules](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#rules) and already sits inside the top 10. |

You get **one alert per real change**. A keyword that drops out of the top 10 alerts once, not at every refresh. If it recovers and later drops again, that is a new alert.

{% hint style="info" %}
A new keyword or tracker never alerts about its past. Alerts start after the 16 months of history are downloaded.
{% endhint %}

## Read and manage alerts

Open the **Alerts** tab. Each row shows:

| Column        | What it shows                                                                                                                                                                                                                                                            |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Day**       | The final-data day the alert was confirmed on (Pacific Time). An unread alert has a dot in front of it.                                                                                                                                                                  |
| **Keyword**   | The keyword or rule. Click it to open its [details](/guide/google-search-console/gsc-rank-tracker/keyword-details).                                                                                                                                                      |
| **Type**      | What happened, in words: "Dropped out of the top 10", "Improved 7 positions", "Google shows /page instead of your target".                                                                                                                                               |
| **From → To** | The position before and after, rounded; hover for the exact values. A vanished keyword reads "25 → not shown", a new rule member "new → 8", and a wrong page or split shows only the position now.                                                                       |
| **Page**      | The page path involved. A crossing or a move shows the page, or "/old → /new" when Google switched pages. A wrong page shows your target and the page Google shows instead, a split shows the main page and the second page, and a vanished keyword shows "last: /path". |

* Filter with **Type** and **Unread only**, or search by keyword.
* Click **Mark all read**, or tick rows and use **Mark read**. The row menu has **Open**, which shows the keyword around the day of the alert, and **Mark read**.
* Alerts are kept for 365 days.

Unread alerts show up in several places, so you notice them without opening the tab: the **Alerts (n)** tab label, the **Unread alerts** figure in the KPI strip, a dot or number in the tracker selector, and a badge on **Rankings** in the page menu of the top bar.

## Move threshold

The **move threshold** is how many positions a keyword must move to count as a move, for **Moved** alerts and for the [Movers](/guide/google-search-console/gsc-rank-tracker/movers) tab. The default is 5.

Set it in the wizard's last step, or later in the tracker's **Settings** (click the tracker's name at the top), under **Move threshold**. It must be a whole number from 1 to 100. When you save a new value, the open alerts are checked again against it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f99ec65a50f3310e2a76b33a6c5dff7add2cc0fa%2Fgsc-rankings-settings-sheet.png?alt=media" alt="The tracker settings with Thin threshold, Move threshold and Desktop notifications"><figcaption><p>Move threshold and Desktop notifications in the tracker settings</p></figcaption></figure>

## Desktop notifications

Turn on **Desktop notifications** in the wizard or in the tracker settings. When a refresh finds new alerts, SEO Utils shows one notification for that tracker, not one per alert. Click it to open the tracker's **Alerts** tab.

* The first time you turn it on, your computer may ask you to allow notifications from SEO Utils. If they are blocked, the setting shows an **Allow notifications** link or tells you where to switch them on in the system settings.
* Notifications appear in the SEO Utils desktop app. The Alerts tab lists every alert either way.

## Send alerts by email or webhook

Use the **GSC Rank Tracker Alerts** trigger in [Automations](/guide/automations) to send new alerts to your inbox or to another tool.

{% stepper %}
{% step %}

#### Create an automation

Go to **Automations** in the sidebar, click **Create Automation** and give it a name.
{% endstep %}

{% step %}

#### Choose the trigger

Open the trigger list and choose **GSC Rank Tracker Alerts**. Under **Apply to**, pick **All reports** or **Specific reports** to limit it to some trackers.

Then narrow down what you receive:

* **Alert types**: tick the types you want. Leave all unticked to receive every type.
* **Only keywords in**: **Any position**, **Top 3**, **Top 10** or **Top 20**. Only alerts of keywords that were or are in this range are sent.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-08f78e10a96d7a03a36f8bd263e229fce7ae3112%2Fgsc-rankings-automation-trigger.png?alt=media" alt="The automation trigger step for GSC Rank Tracker Alerts with alert types and a position filter"><figcaption><p>Choose which alerts the automation sends</p></figcaption></figure>
{% endstep %}

{% step %}

#### Add an action

This trigger supports **Export PDF**, **Send Email** and **Webhook**. **Export PDF** saves the tracker's [report](/guide/google-search-console/gsc-rank-tracker/print-and-pdf#send-it-with-an-automation). Send Email needs your [SMTP credentials](/guide/smtp-credentials); until they are set up it shows as unavailable.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-eb6ec316be235290aa6206e6870a03e2bda34c70%2Fgsc-rankings-automation-actions.png?alt=media" alt="The action type list with Export PDF, Send Email and Webhook"><figcaption><p>Export PDF, Send Email and Webhook are the actions for this trigger</p></figcaption></figure>
{% endstep %}
{% endstepper %}

The automation runs **once per refresh** with all the new alerts of that tracker, not once per alert. If its filters leave no alert, nothing is sent.

<details>

<summary>Variables and webhook payload</summary>

In an email subject or body, use these variables:

| Variable                                                                                               | Value                                                                                                                                                                                                                                                                                                                                                                                                 |
| ------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `{{trigger.trackerName}}`                                                                              | The tracker's name                                                                                                                                                                                                                                                                                                                                                                                    |
| `{{trigger.propertyDomain}}`                                                                           | The Search Console property                                                                                                                                                                                                                                                                                                                                                                           |
| `{{trigger.market}}`                                                                                   | Country and device                                                                                                                                                                                                                                                                                                                                                                                    |
| `{{trigger.alertsCount}}`                                                                              | Number of alerts sent                                                                                                                                                                                                                                                                                                                                                                                 |
| `{{trigger.alertsSummary}}`                                                                            | The alerts in a few words, for example "3 dropped, 1 wrong page"                                                                                                                                                                                                                                                                                                                                      |
| `{{trigger.alertsList}}`                                                                               | One line per alert, up to 20                                                                                                                                                                                                                                                                                                                                                                          |
| `{{trigger.fromDate}}` and `{{trigger.toDate}}`                                                        | The first and last day an alert was confirmed on                                                                                                                                                                                                                                                                                                                                                      |
| `{{trigger.reportFrom}}` and `{{trigger.reportTo}}`                                                    | The first and last day of the report period: the 30 days ending on the tracker's latest final day. The Export PDF action covers them                                                                                                                                                                                                                                                                  |
| `{{trigger.kpis.tracked}}`, `{{trigger.kpis.avgH}}`, `{{trigger.kpis.top3}}`, `{{trigger.kpis.top10}}` | The tracker's headline figures                                                                                                                                                                                                                                                                                                                                                                        |
| `{{trigger.aiSummaryText}}`                                                                            | This week's AI summary as one paragraph. Empty when the [weekly summary](/guide/google-search-console/gsc-rank-tracker/ai#weekly-summary) is off or not written yet. It starts "This week (Oct 1 – Oct 7), written by AI (provider and model):", or "This week (Oct 1 – Oct 7):" when the tracker's [AI label](/guide/google-search-console/gsc-rank-tracker/ai#hide-the-ai-label-for-clients) is off |

A webhook receives JSON with the tracker, the property, the filtered `alerts` and the headline `kpis`:

{% code title="Webhook payload (shortened)" %}

```json
{
  "event": "gsc_rank_alerts",
  "tracker": { "id": 7, "name": "US · All devices · Web" },
  "property": { "domain": "harborpine.example" },
  "alerts": [
    {
      "keyword": "best coffee grinder",
      "type": "band_cross",
      "direction": "down",
      "from": 4.1,
      "to": 14.3,
      "band": 10,
      "page": "https://harborpine.example/products/coffee-grinder",
      "confirmedDate": "2026-10-11"
    }
  ],
  "kpis": { "tracked": 102, "avgH": 8.1, "top3": 15, "top10": 51 }
}
```

{% endcode %}

With the weekly AI summary on and written, the payload also has an `aiSummary` object with the week, the text, its evidence, the provider and the model. It keeps the provider and model even when the tracker's AI label is off.

</details>


# Before / After

The **Before / after** tab answers "did my change work?". Pick a day, such as the day you rewrote a page or a Google update, and see how each keyword's position moved in the days before and after it.

## Compare around a date

Open the **Before / after** tab, next to Alerts.

{% stepper %}
{% step %}

#### Pick the date

Click the date button (1) and choose a day in the calendar. Until you pick, the tab uses the newest day whose days after it already have final data.
{% endstep %}

{% step %}

#### Choose the window

Choose **7 days**, **14 days** or **28 days** (2). It is how many days SEO Utils compares before and after the date. The date itself is skipped.
{% endstep %}
{% endstepper %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-18b805487e1ee5f5f5837d7f2e7576d12454781e%2Fgsc-rankings-before-after-tab.png?alt=media" alt="The Before / after tab with the date, the window, the Compare around chips and the summary strip"><figcaption><p>The date (1), the window (2), the chips (3) and the summary (4)</p></figcaption></figure>

Instead of the calendar, click a chip under **Compare around** (3). The chips list your [notes](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#position-bands-chart) and Google's updates, newest first, and **Show all** lists the rest. A line under the chips spells out the comparison, for example "Oct 1 – Oct 7 compared with Oct 9 – Oct 15, 2026 (Pacific). Oct 8 is skipped." The tab remembers your date and window for each tracker.

## Read the result

The strip (4) counts the keywords and rules by verdict, shows the **Median change** and the **Clicks** gained or lost in total. The table lists each one.

| Column                                            | What it shows                                                                                                                                    |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Before**, **After**                             | Google's average position over the days with enough data in each window, weighted by impressions. Hover for the decimals and the number of days. |
| **Δ**                                             | Before minus after, so a positive number is an improvement. Under half a position shows an arrow.                                                |
| **Clicks before**, **Clicks after**, **Clicks Δ** | The clicks on those days in each window, and the difference.                                                                                     |
| **Verdict**                                       | See the next table.                                                                                                                              |

| Verdict                    | Meaning                                                                          |
| -------------------------- | -------------------------------------------------------------------------------- |
| **Improved**, **Declined** | The position changed by at least 1, and both windows have enough days with data. |
| **No change**              | The position changed by less than 1.                                             |
| **Not enough data**        | One window has too few days with final data and enough impressions.              |
| **Too early**              | The days after the date are not final yet, so only the Before side is shown.     |

Use the **Verdict** and **Tags** filters to focus the table, for example the keywords of one AI [topic](/guide/google-search-console/gsc-rank-tracker/ai#group-with-ai). Click a keyword to open its [details](/guide/google-search-console/gsc-rank-tracker/keyword-details) on the day you compared.

{% hint style="info" %}
Google's data is final about 2–3 days late. A date too close to today shows **Too early** until the days after it are final. Pick an earlier date or a shorter window.
{% endhint %}

### Google's data error

Google logged impressions wrongly in Search Console from May 13, 2025 to Apr 27, 2026. When the days you compare overlap that period, an amber note appears above the summary strip:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f7493ba3254a5c3ff75e1b0ec1650587db18f48f%2Fgsc-rankings-before-after-anomaly.png?alt=media" alt="The Before / after tab for Nov 12, 2025 with the amber Google data error note above the summary strip"><figcaption><p>The note says the error is in Google's data, not in SEO Utils (1)</p></figcaption></figure>

{% hint style="warning" %}
"Part of this range falls inside a Google Search Console data error, not an SEO Utils problem: Google logged impressions wrongly from May 13, 2025 to Apr 27, 2026, which also affects CTR and average position. Compare with care." A **Read Google's notice** link follows it and opens Google's own page about the error.

The error also affects CTR and average position, so a change that falls in that period may come from Google's data and not from your change. Compare with care.
{% endhint %}


# AI: Explanations, Summary and Topics

Three optional AI helpers write about your tracker's own numbers. **Why did it move?** explains one keyword, the **weekly summary** writes up the week, and **Group with AI** sorts your keywords into topics. They use your own AI key or a local model, so the cost is whatever your AI provider charges, and nothing for a local model.

{% hint style="info" %}
The AI only gets facts the tracker already holds, such as positions, confirmed moves, page changes, Google updates, your notes and click-through rate. Every answer says it was written by AI, with the provider and model.
{% endhint %}

## Choose the AI model

All three helpers use one model. Open **Settings > Services**, go to **AI & NLP > Rank Tracker AI model** and pick a model in **GSC Rank Tracker AI**, then click **Save**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2e677e16b8571764a720222f8ac599014e770d73%2Fgsc-rankings-ai-settings-card.png?alt=media" alt="The GSC Rank Tracker AI card with the AI model field and the Save button"><figcaption><p>One model for Why did it move?, the weekly summary and Group with AI</p></figcaption></figure>

* The list shows the providers whose API key you added in **AI Settings**, plus the models of a local Ollama. See [Choose the AI model](/guide/bulk-seo-metadata-optimizer#choose-the-ai-model) to add a key or set up Ollama.
* Some models also offer a **reasoning effort**. A higher effort gives more careful answers and costs more output tokens.
* If the chosen provider has no API key, the helpers use the default AI model of **Settings > General**, and the note under each button says so. Until you save a choice, the card shows the default it would use.

The explanation panel, the grouping estimate and the weekly summary switch each show a line naming what will run, for example "Uses Ollama · llama3.1:8b, runs locally", or "billed to your API key" for a cloud provider.

## Why did it move?

Use it when a keyword's position changed and you want to know what the data says.

{% stepper %}
{% step %}

#### Open the explanation

Click a keyword to open its [details](/guide/google-search-console/gsc-rank-tracker/keyword-details), then click **Why did it move?** or **Explain** in the panel. You can also open the **⋯** menu of a row in the Keywords table and choose **Why did it move?**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-09026ee94e1f006cb6dfab6308b024b77dc02808%2Fgsc-rankings-ai-why-explain.png?alt=media" alt="The keyword details with the Why did it move? button and the Explain button"><figcaption><p>Two buttons start the same request</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c640b528e35eda06803919a25987a7b13147825b%2Fgsc-rankings-ai-why-row-menu.png?alt=media" alt="The row menu of a keyword with Why did it move? at the top"><figcaption><p>The row menu</p></figcaption></figure>
{% endstep %}

{% step %}

#### Read the answer

The answer is two or three sentences, with an evidence line for each fact it relies on. The panel names the day it explains, for example "Around Oct 22". That is the keyword's latest day with final data, or the day of the mover or alert you opened it from.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6537d7c891a6e175d6cabcdf4bf9bb06d5563bd7%2Fgsc-rankings-ai-why-answer.png?alt=media" alt="An answer with three evidence lines and the Written by AI footer"><figcaption><p>The answer (1), its evidence (2) and who wrote it (3)</p></figcaption></figure>

Click a date chip to jump to that day on the chart. The chart widens when it needs to, and Google updates and your notes appear when the chip is about one.
{% endstep %}
{% endstepper %}

The answer is saved. Click again with nothing changed and the panel says "Up to date: nothing has changed since this answer, so nothing was sent." Nothing is asked and nothing is billed. If new data arrives, the panel says "The data changed since this was written." and offers **Explain again**. Another model or reasoning effort asks again.

A rule can be explained too. An archived keyword cannot, until you restore it, and neither can a keyword with no final data yet.

## Weekly summary

A short write-up of the week, shown on the tracker page and available to your automations. It is off by default.

{% stepper %}
{% step %}

#### Turn it on

Switch on **Weekly AI summary** in the tracker's **Settings** (click the tracker's name at the top) and click **Save**, or on the **Review** step when you [create a tracker](/guide/google-search-console/gsc-rank-tracker/create-a-tracker#the-five-steps). The line under the switch names the model and says it runs once a week.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d10c9be7c8b6d42bf25ced453b08d4329f039219%2Fgsc-rankings-ai-weekly-setting.png?alt=media" alt="The tracker settings with the Weekly AI summary switch turned on"><figcaption><p>The switch in the tracker settings</p></figcaption></figure>
{% endstep %}

{% step %}

#### Read the This week card

Every Monday, after the first refresh of the week, SEO Utils writes the summary for the 7 days ending on the latest final date. It appears in a **This week** card above the KPI strip, built from the confirmed moves, the alerts and the position bands.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8750e12157c1488769ea971aec1024b6ff64ae0a%2Fgsc-rankings-ai-this-week.png?alt=media" alt="The This week card with a summary and three evidence lines"><figcaption><p>The title (1), the evidence (2) and the arrow that hides the card (3)</p></figcaption></figure>

A keyword or alert chip opens that keyword at that date. A position band or Google update chip focuses the chart, and the key figures chip scrolls to the KPI strip.
{% endstep %}
{% endstepper %}

* A week with no confirmed moves and no alerts reads "No confirmed moves or alerts this week." and sends nothing to the AI.
* If the request fails, the card shows the reason and **Try again**. SEO Utils also tries once more 30 minutes later.
* Until the first Monday after you turn it on, the card says when the first summary will be written. An older summary stays visible as **Last summary**.
* In [Automations](/guide/automations#gsc-rank-tracker-alerts-trigger), the summary is the `aiSummaryText` variable and the `aiSummary` part of a webhook. It is also the Weekly summary section of the [report](/guide/google-search-console/gsc-rank-tracker/print-and-pdf).

### Hide the AI label for clients

If the tracker's reports go to clients who do not need to know that an AI wrote the summary, turn off **Show the AI label in reports and emails**. It is in the tracker's **Settings** (click the tracker's name at the top), under **Weekly AI summary**. It is on by default, also for trackers you made before it existed, and a [duplicate](/guide/google-search-console/gsc-rank-tracker/manage-trackers#duplicate-a-tracker) keeps your choice.

With it off, the [report](/guide/google-search-console/gsc-rank-tracker/print-and-pdf), the PDF, the HTML page, the browser print and the PDF an automation creates still show the weekly summary with its title, dates, text and evidence chips, but:

* the "Written by AI (provider and model)" line is gone, and so is "No AI request was needed" in a quiet week;
* the "Written by AI from the data above" footer under the evidence is gone;
* the `aiSummaryText` variable of an [automation email](/guide/automations#gsc-rank-tracker-alerts-trigger) reads "This week (Oct 1 – Oct 7): …" instead of "This week (Oct 1 – Oct 7), written by AI (provider and model): …".

The switch changes only what a client reads. These always show the AI label, because you and your team need to know which text came from AI:

* the **This week** card, the **Why did it move?** panel and the **Group with AI** dialog in the app;
* the `aiSummary` part of a webhook, which keeps the provider and model, since the webhook is your own data feed;
* the answers of an AI assistant connected through [MCP](/guide/mcp-server).

The switch costs nothing and starts no AI request. A team member with the **Manager** role can change it in the browser.

## Group with AI

Group with AI sorts your keywords into topics, so you can filter the table by subject.

{% stepper %}
{% step %}

#### Start it

Click the arrow beside **Add keywords** and choose **Group with AI…**. It covers every active keyword. To group only some, tick rows and choose **Group with AI…** in the bulk actions. Rules and archived keywords are left out.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e0181f7a21f39ff4f85f8a563a57f795c4d8f664%2Fgsc-rankings-add-keywords-menu.png?alt=media" alt="The Add keywords menu with Group with AI and Check metrics for missing"><figcaption><p>The menu beside Add keywords</p></figcaption></figure>
{% endstep %}

{% step %}

#### Check the estimate

The dialog shows how many keywords and AI requests the run needs and the approximate tokens, and says whether your provider bills for them. Nothing is sent until you click **Group N keywords**. Switch on **Only keywords without a topic** to leave keywords that already have one.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7dcfc04c1b6da52656e62d3c7098e36308d8fd28%2Fgsc-rankings-ai-group-estimate.png?alt=media" alt="The Group with AI estimate with keywords, requests, tokens and the Group 87 keywords button"><figcaption><p>The estimate (1), the cost note (2) and the start button (3)</p></figcaption></figure>

If you use the [Embedding Database](/guide/embedding-database), SEO Utils groups similar keywords by their embeddings first and asks the AI only to name each group. Otherwise the AI reads the keywords in batches of 300.

You can close the window while it runs. When it is done, a message tells you to open **Group with AI** to review the topics.
{% endstep %}

{% step %}

#### Review and apply

Nothing is tagged until you apply. In the table:

* Edit a **Topic** name to rename it (1).
* Pick another topic in **Merge into** to join two topics (2).
* Untick a topic to leave its keywords alone (3).

Keywords the AI put in no topic are listed under **Unassigned** and keep their tags. Click **Apply topics** (4), or **Start over** to ask again.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-14824f583751e08065730642c4115c56b37d8eca%2Fgsc-rankings-ai-group-review.png?alt=media" alt="The topic review table with a renamed field, a merged topic, an unticked topic and the Apply topics button"><figcaption><p>Rename, merge or untick a topic, then apply</p></figcaption></figure>
{% endstep %}
{% endstepper %}

Each topic becomes a tag on its keywords. To see one topic's keywords, open the **Tags** filter and pick it from the **Topics** group, which sits above your own tags. The **Show in Tags filter** button in the message after Apply opens it for you.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-95c204b0986b644d56628bfd13916d61bd06b772%2Fgsc-rankings-ai-topics-filter.png?alt=media" alt="The Tags filter with a Topics group listing the topics"><figcaption><p>Topics have their own group in the Tags filter</p></figcaption></figure>

In the **Tag…** dialog, topics show apart from your own tags, and you can remove one from a keyword. Topics also appear in the CSV export's tags and are copied when you [duplicate a tracker](/guide/google-search-console/gsc-rank-tracker/manage-trackers#duplicate-a-tracker).

## Team members

Every role can read the saved answers, the This week card and the topics. Asking for a new answer, a new grouping or a retry needs **Run reports** and **Can use the owner's machine and accounts**, because they spend your AI provider. Applying topics needs the right to tag keywords. Turning on the weekly summary needs the owner's accounts too. See [Team](/guide/team).

## Best practices

* Treat the answer as a lead to check, not as proof. The evidence lines show what it rests on.
* Turn the weekly summary on for the trackers you report on, and leave it off for the rest.
* Run **Group with AI** after you add a batch of keywords, with **Only keywords without a topic** switched on.


# Report and PDF

The report turns one tracker into a printable page you can hand to a client or keep as a record: the key figures, the weekly summary, the position bands, the top 1, 3 and 10 counts, the biggest movers, the pages with the most to gain, the alerts and the top keywords. Open it from the tracker, save it as a PDF, or have an [automation](#send-it-with-an-automation) create it for you.

## Open the report

{% stepper %}
{% step %}

#### Pick the period

On the Rankings page, set the date range above the Keywords table. The report covers that range, **Last 30 days** by default.
{% endstep %}

{% step %}

#### Open the export

Click the tracker's name at the top of the page, then **Export PDF & HTML…**. In a browser through [Remote Access](/guide/remote-access) the item reads **Export PDF…**, because a browser has no HTML export. The report opens in its own page, with **Back to Rankings** at the top left.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-79c723a282cde5910b59cb27589cbe88fa7232cd%2Fgsc-rankings-report-menu.png?alt=media" alt="The menu under the tracker&#x27;s name with the Export PDF &#x26; HTML… item after Settings"><figcaption><p>Export PDF &#x26; HTML… (1) is in the tracker's menu</p></figcaption></figure>
{% endstep %}
{% endstepper %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fde460bce00f5ac0b711ff0a22cad9041ca7eff3%2Fgsc-rankings-report-preview.png?alt=media" alt="The top of the report with the header, key figures, weekly summary and position bands"><figcaption><p>The header (1), the weekly summary (2) and the position bands (3)</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-738c5138307f511a135425ae5d71ff930cb587bf%2Fgsc-rank-tracker-report-top-counts.png?alt=media" alt="The report section Keywords in the top 1, 3 and 10 with both sources, the gap tiles and the explanation"><figcaption><p>The top 1, 3 and 10 section of a linked tracker: the sources line (1), the gap tiles (2) and the explanation (3)</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-429a31b2767e6af5fdf9a2af9adf09c923f6bec9%2Fgsc-rankings-report-preview-lists.png?alt=media" alt="The report&#x27;s Top movers, Alerts in this period and Top keywords by impressions sections"><figcaption><p>Top movers (1), alerts (2) and the top keywords grid (3)</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2898f16b9c1c2814cfd3e9685d0905fcd4881690%2Fgsc-rank-tracker-report-top-pages.png?alt=media" alt="The report section Top pages by opportunity with its note, one row per page and the Top opportunity column"><figcaption><p>Top pages by opportunity: the note (1), an Opportunity with its second line (2) and the Top opportunity column (3)</p></figcaption></figure>

## What the report holds

| Section                             | What it shows                                                                                                                                                                                                                                                                                                                                                                      |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Header**                          | The tracker's name, site and market, the period, how current the data is and when the report was made.                                                                                                                                                                                                                                                                             |
| **Key figures**                     | The [KPI strip](/guide/google-search-console/gsc-rank-tracker/read-your-rankings#kpi-strip), **Top 1** included, without the unread alerts. The movers figure counts the 7 days to the latest final date.                                                                                                                                                                          |
| **Weekly summary**                  | The saved [weekly summary](/guide/google-search-console/gsc-rank-tracker/ai#weekly-summary). Left out when the summary is off or none was written yet.                                                                                                                                                                                                                             |
| **Position bands**                  | The band chart with its **#1** segment and average position line, and Google updates and your notes marked.                                                                                                                                                                                                                                                                        |
| **Keywords in the top 1, 3 and 10** | The [card](/guide/google-search-console/gsc-rank-tracker/top-1-3-10) for every keyword, with its Clicks and Impressions bars. With a linked report it shows both sources, the four gap tiles with their definitions and the first two sentences of **Why do the lines differ?**. Without a link it says "From your Search Console data." and shows the Search Console lines alone. |
| **Site traffic (GA4)**              | The site's GA4 traffic for the period, when a GA4 property is chosen in the tracker's settings. See [Show site traffic in the report](#show-site-traffic-in-the-report).                                                                                                                                                                                                           |
| **Top movers**                      | The 20 biggest confirmed moves each way in the period, from final data. A one-day period, or one that starts on or after the latest final date, has no list. When the period overlaps [Google's data error](/guide/google-search-console/gsc-rank-tracker/before-after#googles-data-error), the same amber note shows here, with Google's address written out in the PDF.          |
| **Top pages by opportunity**        | The 10 pages with the largest [Opportunity](/guide/google-search-console/gsc-rank-tracker/opportunities-per-page) at the end of the period, with **Keywords**, **Clicks (28d)**, **Opportunity** and **Top opportunity**, for all keywords. It is always included, and left out when no page has an Opportunity.                                                                   |
| **Alerts in this period**           | The alerts confirmed in the period, newest first. The report never marks them read.                                                                                                                                                                                                                                                                                                |
| **Top keywords by impressions**     | The 50 keywords and rules with the most impressions in the period, with their position over time.                                                                                                                                                                                                                                                                                  |

The saved PDF is always in light colours, even when SEO Utils is in dark mode.

The weekly summary says it was written by AI, with the provider and model, unless you switch that off for the tracker. See [Hide the AI label for clients](/guide/google-search-console/gsc-rank-tracker/ai#hide-the-ai-label-for-clients).

## Show site traffic in the report

A client report can show the site's traffic from [Google Analytics 4](/guide/google-analytics-4) next to its rankings. Choose the GA4 property in the tracker's settings.

{% stepper %}
{% step %}

#### Open the settings

Click the tracker's name at the top of the Rankings page, then **Settings**.
{% endstep %}

{% step %}

#### Choose the property

In **General**, pick the GA4 property in **Site traffic (GA4)**, then click **Save**. Choose **Off** to leave the section out.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c967ae95f6b8c1a10e0a81acbfbe2442aff7e9f0%2Fgsc-rankings-settings-site-traffic.png?alt=media" alt="The Site traffic (GA4) field in the tracker settings, filled in with a property, and the Save button"><figcaption><p>The Site traffic (GA4) field (1) and Save (2)</p></figcaption></figure>
{% endstep %}
{% endstepper %}

If exactly one GA4 property matches the tracker's site, SEO Utils shows it with a **Suggested** badge, and nothing is turned on until you click **Save**. Under the field it says **Not saved yet** after a change and **Saved. The report uses this property.** once stored. An **Off** you chose stays off.

The report then has a **Site traffic (GA4)** section for the report's period. See [the same section in an Organic Rank Tracker report](/guide/organic-rank-tracker#show-site-traffic-in-the-report) for what it holds. It is in the PDF you download and in the PDFs an [automation](#send-it-with-an-automation) creates, in the same language as the rest of the report. If the property is removed from SEO Utils, the section is left out and the report says so on screen.

## Save it as a PDF

Move over the round **+** button at the bottom right of the report. Wait until the report has finished loading, because the buttons stay greyed out until then.

* **On the desktop app**, click **Download PDF** to save a landscape A4 PDF, or **Download HTML** to save a web page. You choose where to save the file.
* **In a browser through** [**Remote Access**](/guide/remote-access), click **Print / Save as PDF** and choose **Save as PDF** in your browser's print window. HTML is not offered.

{% hint style="info" %}
**Export PDF & HTML…** (**Export PDF…** in a browser) and the PDF buttons need the **Export data** permission for a [team member](/guide/team). Without it they are greyed out with the reason.
{% endhint %}

## Send it with an automation

The **GSC Rank Tracker Alerts** trigger can create the report as a PDF, so it lands in a folder or in an email each time a refresh finds new alerts.

{% stepper %}
{% step %}

#### Choose the trigger

In [Automations](/guide/automations), create an automation and choose the **GSC Rank Tracker Alerts** trigger, as in [Alerts](/guide/google-search-console/gsc-rank-tracker/alerts#send-alerts-by-email-or-webhook).
{% endstep %}

{% step %}

#### Add Export PDF

Add an action and choose **Export PDF**. Pick the **Export Folder** and, if you like, a **Report language**. Add **Send Email** after it to attach the file, using the **Variables** button to insert the file path.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8595b65942b302daaaf1c73b9477b094f97d21cd%2Fgsc-rankings-automation-export-pdf.png?alt=media" alt="The action type list for the GSC Rank Tracker Alerts trigger with Export PDF, Send Email and Webhook"><figcaption><p>Export PDF is one of three actions for this trigger</p></figcaption></figure>
{% endstep %}
{% endstepper %}

The PDF covers the 30 days that end on the tracker's latest final date, lists the alerts of that period and holds the same sections as the report, including the top 1, 3 and 10 and top pages sections. The trigger's `reportFrom` and `reportTo` variables hold those two dates, while `fromDate` and `toDate` keep holding the span of the alerts that fired the automation. See [GSC Rank Tracker Alerts trigger](/guide/automations#gsc-rank-tracker-alerts-trigger).


# Manage Trackers

Everything about a tracker as a whole lives in the menu under the tracker's name, in the bar at the top of the Rankings page, plus a few shortcuts from other Search Console screens.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5cc06b8c532e7ea130295c4a6a5de51fe4380572%2Fgsc-rankings-actions-menu.png?alt=media" alt="The menu under the tracker&#x27;s name with Settings, Publish to client, Export PDF &#x26; HTML…, Export CSV…, View log and Duplicate tracker…"><figcaption><p>Click the tracker's name (1) to open its menu</p></figcaption></figure>

* **Refresh now**, at the right end of the same bar, downloads the newest data right away. Otherwise the tracker refreshes itself every 6 hours while the property's **Auto-sync Enabled** setting is on.
* **View log** in the menu shows what the latest refreshes did, in plain sentences.
* **Publish to client** in the menu shares a read-only copy of the tracker with your client at a private link. See [Share Reports with Clients](/guide/white-labeled-client-report).
* **Export PDF & HTML…** opens a printable report of the tracker, to save as a PDF or an HTML page. In a browser the item reads **Export PDF…**. See [Report and PDF](/guide/google-search-console/gsc-rank-tracker/print-and-pdf).

## Settings

Click the tracker's name at the top, then **Settings**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f99ec65a50f3310e2a76b33a6c5dff7add2cc0fa%2Fgsc-rankings-settings-sheet.png?alt=media" alt="The tracker settings sheet with thresholds, Desktop notifications, the Weekly AI summary switch and the Show the AI label in reports and emails switch"><figcaption><p>Tracker settings</p></figcaption></figure>

| Setting                                     | What it does                                                                                                                                                                                                                                                                                           |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Name**                                    | The name shown in the tracker selector.                                                                                                                                                                                                                                                                |
| **Thin threshold**                          | Days with fewer impressions are faded and left out of averages. Default 5.                                                                                                                                                                                                                             |
| **Move threshold**                          | How many positions a keyword must move to count as a move, confirmed on two days. Default 5. See [Alerts](/guide/google-search-console/gsc-rank-tracker/alerts#move-threshold).                                                                                                                        |
| **Rule member minimum**                     | A rule lists a query once it has this many impressions in 28 days.                                                                                                                                                                                                                                     |
| **Desktop notifications**                   | Show a notification when a refresh finds new alerts. See [Alerts](/guide/google-search-console/gsc-rank-tracker/alerts#desktop-notifications).                                                                                                                                                         |
| **Weekly AI summary**                       | An AI model writes a short summary of the tracker's moves and alerts every Monday. Off by default. See [AI](/guide/google-search-console/gsc-rank-tracker/ai#weekly-summary).                                                                                                                          |
| **Show the AI label in reports and emails** | On by default. Turn it off to hide "Written by AI" and the model name from the report, its PDF and HTML, and the automation email, for clients. The app itself always shows them. See [Hide the AI label for clients](/guide/google-search-console/gsc-rank-tracker/ai#hide-the-ai-label-for-clients). |

Click **Save** to apply. Below those fields, the sheet has the market, rank tracker link, duplicate and delete options.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1991d211db893a5d24c4df4207e7c5e7b009e05d%2Fgsc-rankings-settings-sheet-more.png?alt=media" alt="The bottom of the settings sheet with Change market, Duplicate tracker and Delete tracker"><figcaption><p>Change market, Duplicate and Delete</p></figcaption></figure>

## Change the market

Click **Change market…** to pick another country, device or search type for the same tracker.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-23a1b0ae63f59d4d8024f5fc3152828a18e8e3f3%2Fgsc-rankings-settings-change-market.png?alt=media" alt="The Change market dialog with a warning that history is replaced"><figcaption><p>Changing the market replaces the history</p></figcaption></figure>

{% hint style="warning" %}
**Change and re-pull** downloads all of the tracker's history again for the new market and replaces the old one. Rule members and alerts are cleared. History older than 16 months cannot be downloaded again.
{% endhint %}

To keep the current history, click **Duplicate to a new tracker** instead. It opens the [Duplicate dialog](#duplicate-a-tracker) with the market you chose.

## Link a rank tracker report

The **Rank tracker link** section of the settings sheet links an [Organic Rank Tracker](/guide/organic-rank-tracker) report to the tracker, so the Keywords table can compare its positions with Search Console. Use **Link a report…**, **Change…**, **Unlink** and **Pull new ORT keywords**. See [Compare with Organic Rank Tracker](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#link-a-report). A team member needs Manager access to change the link; see [Team members](/guide/google-search-console/gsc-rank-tracker/compare-with-organic-rank-tracker#team-members).

## Duplicate a tracker

**Duplicate tracker…** creates a new tracker on the same property, for example the same keywords for another country, device or search type. Click the tracker's name at the top, then **Duplicate tracker…**. You can also use the **Duplicate** section of the settings sheet, or the first step of the [New tracker wizard](/guide/google-search-console/gsc-rank-tracker/create-a-tracker#the-five-steps).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-651b004feb8c66ef4a3c484554008d6b8b83d444%2Fgsc-rankings-actions-menu-duplicate.png?alt=media" alt="The menu under the tracker&#x27;s name with Duplicate tracker… as its last item"><figcaption><p>Duplicate tracker… is the last item of the tracker's menu</p></figcaption></figure>

In the dialog, choose a name and a market. To copy a Web tracker as an Image tracker, set **Search type** to **Image**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1ba55c64da87166e79cdb0dfa8b839b62e35eac0%2Fgsc-rankings-settings-clone.png?alt=media" alt="The Duplicate tracker dialog with a name, a market and Search type set to Image"><figcaption><p>Duplicate a Web tracker as an Image tracker</p></figcaption></figure>

* The duplicate gets the active keywords and rules, their targets and tags (AI topics included), the thresholds and the weekly AI summary switch. Archived keywords are not copied.
* It downloads its own 16 months of history, and the page opens it as soon as it is created. Alerts do not carry over.
* The default name follows the market, for example "US · All devices · Image".

## Delete a tracker

**Delete tracker…** removes the tracker and all the history it downloaded, after you confirm. The dialog shows since when the history goes back. History older than 16 months cannot be downloaded again, so export first if you may need it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-aabf524d951e1bc29ff58e345f187beea77c1ec4%2Fgsc-rankings-settings-delete.png?alt=media" alt="The Delete tracker confirmation"><figcaption><p>Deleting asks for confirmation first</p></figcaption></figure>

To remove only some keywords, use **Archive** in the Keywords table instead. Archived keywords keep their history, and you can restore them from the **Archived** filter.

## Export to CSV

Click the tracker's name at the top, then **Export CSV…** to export what the Keywords table shows. The export follows the table's search, filters and sort, and the date range of the page. To export only some rows, tick them and use **Export selected…**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-822b98244ca1d1c615daecb3c2856a1e63b7f083%2Fgsc-rankings-export-dialog.png?alt=media" alt="The Export CSV dialog with the Table, Grid and Long layouts"><figcaption><p>Choose a layout</p></figcaption></figure>

| Layout    | What the file contains                                                         |
| --------- | ------------------------------------------------------------------------------ |
| **Table** | The columns you see, for the keywords that match your filters.                 |
| **Grid**  | One row per keyword and one column per day, week or month, like the Grid view. |
| **Long**  | One row per keyword per day, with page, impressions, clicks and data flags.    |

On the desktop app, you choose where to save the file. In a browser through [Remote Access](/guide/remote-access), the file downloads, and a download is limited to 64 MiB. For a bigger export, such as the **Long** layout of many keywords over 16 months, export a shorter range or use the desktop app.

## Track in Rankings from other screens

You can add keywords to a tracker straight from other Search Console screens. Tick rows, open **Bulk Actions** and click **Track in Rankings…**:

* **Performance > Queries** and **Keyword Metrics** add the selected queries as keywords.
* **Performance > Pages** adds each selected page as a page rule that matches that exact URL.
* **Cannibalization** adds each query with its top page as the target.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4f9821852a08600ad567fadd6e469af2700b9125%2Fgsc-rankings-track-in-menu.png?alt=media" alt="The Bulk Actions menu on Performance with Track in Rankings"><figcaption><p>Track in Rankings… in the Bulk Actions menu</p></figcaption></figure>

In the dialog, choose the tracker, or **New tracker…** to open the wizard with your selection. Optionally enter a target page for the keywords, then click **Add keywords**. Keywords already in the tracker are skipped, and an archived keyword comes back with its history.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-806fb6b221342ab4eab89967ef4a6fc311aba7e8%2Fgsc-rankings-track-in-dialog.png?alt=media" alt="The Track in Rankings dialog with a tracker, a target page and the selected keywords"><figcaption><p>Choose a tracker and an optional target page</p></figcaption></figure>


# My Go-To SEO Checklist with Google Search Console & GPTs

When I tackle SEO projects, I always start with these steps. They help me decide which keywords and pages need optimization, which ones should be removed, or where to add new content.

#### Step 1: Download all the query and page data from my Google Search Console account.

#### Step 2: Go over each prompt individually using my [Data Analyzer GPTs](https://chat.openai.com/g/g-3uK215Gt4-seo-utils-gsc-data-analyzer). Each prompt includes specific actions, so you'll know exactly what to do.

{% embed url="<https://drive.google.com/file/d/1YNadjXKZHTZNt1AyqtCGwBgRv7j8mZ_g/view?usp=sharing>" %}
Demo video on how to use Data Analyzer GPTs.
{% endembed %}

**#1. Prompt:** Find keywords that ranked on page 2 but are not mentioned in the title

**Action:** I add these keywords to the title. It's a simple tweak that can make a big difference.

***

**#2. Prompt:** Find keywords that ranked on page 2 but are not mentioned in the meta description **Action:** I make sure to include these keywords in the meta description for better relevance.

***

**#3. Prompt:** Find keywords that ranked on page 2 but are not mentioned in headings

**Action:** Adding these keywords to the headings helps in better structuring my content.

***

**#4. Prompt:** Find keywords that are not mentioned at all, but still ranking

**Action:** Sprinkle these keywords throughout my content to climb higher in search rankings.

***

**#5. Prompt:** Find keywords that have high impressions but are not mentioned.

**Action:** Ensure these keywords are mentioned in my content as Google already finds them relevant.

***

**#6. Prompt:** Find keywords that are getting a lot of impressions, but no or low clicks. These are potential opportunities. A high impression count means your site is showing up in search results, but a low click-through rate suggests that users are not finding your listing relevant or compelling enough to click.

**Action:** I focus on these keywords more, sometimes creating new content around them. It's all about converting views to clicks.

***

**#7. Prompt:** Find keywords that are ranking in position 3-11.

**Action:** Almost there, just put extra effort into these by optimizing my content and sometimes adding backlinks to boost them further.

***

**#8. Prompt:** Find keywords that have low average ranking positions but high CTR.

**Actions:** These keywords are already doing good in terms of CTR, just need to optimize content to get a higher rank.

***

**#9. Prompt:** Find keywords that have high average ranking positions but low CTR.

**Action:** Working on title or meta description to increase clicks on these well-positioned keywords.

***

**#10. Prompt:** Find question keywords that I can add to FAQ sections

**Action:** Add these to my FAQ section, answering popular queries directly.

***

**#11. Prompt:** Find keywords & pages that bring traffic to my site

**Actions:**

* You might find variations of your current keywords or entirely new phrases that you hadn’t considered before.
* Explore expanding this topic or using a similar approach (content or backlink strategy) for other topics.
* Consider creating more related content or enhancing existing content around these topics.

***

**#12. Prompt:** What are the topics that all keywords are covering? This will help you understand what topics are already covered on the website

**Action:** Find the topic gap by doing reverse-engineering on competitor's websites

***

**#13. Prompt:** Find keyword cannibalization

**Action:**

* First, I usually ignore the URLs that contain fragment symbols ("#"). GSC considers those URLs are pages, just make sure you have a correct canonical tag on your page.
* Then, I visit the pages that are ranking the same keywords as other pages and check if they haven't had any traffic in the last 3 months, I will delete them and do a 301 redirect. if you feel the content of the deleted page is good, consider merging its content with the content of the main page.

***

{% hint style="success" %}
**Output:** The GPTs will export the keyword list as a CSV file.
{% endhint %}

#### 🔑 If your keyword list is still large after using the prompts, here are some additional tips:

✅ Add the topic with the prompt. For example, "Find keywords that are not mentioned at all, but still ranking"

✅ Focus on long-tail keywords first. For example, "Find long-tail keywords that have high average ranking positions but low CTR"

✅ Focus on search intents. Are your users looking for information, trying to make a purchase, or seeking a specific website? Align your content with the user's intent for the keyword. "For example, Find informational keywords that are ranking in position 3-11"

{% hint style="info" %}
**Pro Tip:** With SEO Utils, use the Mentions filter to quickly see if your keyword is in the title, headings, or body of a page.

<img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d4dd34e9e170c466aed3b49b8f9f2f48a3238b93%2FXnapper-2024-01-24-22.16.08.png?alt=media" alt="" data-size="original">
{% endhint %}

I hope these tips are useful for you. Cheers! 🎉🔥


# Auto-Indexing Tool

With this Auto-indexing tool, you can connect your personal Google Service Account to automatically submit many URLs for indexing.

{% hint style="danger" %}
This tool has been **deprecated**. Please use the **new version** integrated into the [Indexing Dashboard (Google Search Console integration)](/guide/google-search-console/indexing-dashboard).
{% endhint %}

### Set up the Web Search Indexing API and Google Service Accounts.

#### Step 1: Enable the Web Search Indexing API

Visit the Google Cloud Console at <https://console.cloud.google.com/> and create a Project.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fed3ebd0e873d1eb361254ecf4c04de3847767f1%2FXnapper-2023-11-30-17.42.13.png?alt=media" alt=""><figcaption><p>Create a project on Google Cloud Console</p></figcaption></figure>

In the top search bar, type "API" and select "Enabled APIs & services".

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-526b594bd3e7325182497fcc4c3227b9423c9249%2FXnapper-2023-11-30-17.44.04.png?alt=media" alt=""><figcaption><p>Select "Enabled APIs &#x26; services"</p></figcaption></figure>

Click "Library" on the left sidebar.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1c7e1b829ebfef2ed383ab3d7a9ef8a0d0e01788%2FXnapper-2023-11-30-17.46.47.png?alt=media" alt="" width="346"><figcaption><p>Select "Library"</p></figcaption></figure>

Search for "**Web Search Indexing API**" in the top search bar and enable it, so you can access it with your Google Service Account

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ad2e23c8585e4b89cd26c33891e081142c3f68cb%2FXnapper-2024-02-21-14.34.18.png?alt=media" alt="" width="563"><figcaption><p>Enable the Web Search Indexing API</p></figcaption></figure>

#### Step 2: Create a Google Service Account

In your [Google Cloud Console](https://console.cloud.google.com/) dashboard, search for "**Service Accounts**" and click on it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a1cc74a736cda2c0440b1e8b9ab41c553e091718%2FXnapper-2023-11-30-17.51.43.png?alt=media" alt=""><figcaption><p>Click on "Service Accounts"</p></figcaption></figure>

Hit the "Create Service Account" button, and enter a service account name. Then, hit the "Done" button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-25f938df748c78cbfa2b6e28a69370b4d45db02f%2FXnapper-2023-11-30-17.56.52.png?alt=media" alt=""><figcaption><p>Enter service account name</p></figcaption></figure>

Copy the email of the service account.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9785e7daf49d21a78bdaf7b770179cbb9c158ef6%2FXnapper-2023-11-30-17.58.38.png?alt=media" alt=""><figcaption><p>Copy the email</p></figcaption></figure>

Click on the Service Account's email, select the "**KEYS**" tab, then click the "**Create new key**" button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4c8c4f49958bb72884c7a528d8baf1e336277a61%2FXnapper-2023-11-30-18.08.28.png?alt=media" alt=""><figcaption><p>Create a key for your service account</p></figcaption></figure>

A model will pop up. Select "JSON" and click the "Create" button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e7e6a767e843707a70f32c22e7d663f5ec465d19%2FXnapper-2023-11-30-18.10.57.png?alt=media" alt=""><figcaption><p>Select JSON in Key type field.</p></figcaption></figure>

After creating the key, Google will download it to your machine. Keep that file. We will need it in Step 3.

#### Step 3: Add the Google Search Console to SEO Utils

Access the **Google Service Accounts** menu from the App dropdown at the top-right corner.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f6a35c6a12dc9855db793fdaac0b45a9f5018d26%2FXnapper-2024-02-21-14.41.52.png?alt=media" alt="" width="563"><figcaption><p>Access the Google Service Accounts menu</p></figcaption></figure>

Then, click the **Add Account** button, and select the JSON file that you downloaded in Step 2 to add a new account.

{% hint style="warning" %}
**Google Indexing API Rate Limit**

Google only allows you to submit 200 URLs per day via the Indexing API. There are 2 ways to bypass this.

1. [Request more quota](https://developers.google.com/search/apis/indexing-api/v3/quota-pricing).
2. Create multiple projects and Google Service Accounts by repeating Step 1 to Step 3. Please note that you have to create a new project and then create a new Google Service Account in that new project because Google limits the API usage per project, not per Google Service Account.
   {% endhint %}

After creating an account, please copy the Google Service Account email address.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-48181b5e7984bac630b9fc89eac9fcfdff13c25a%2FXnapper-2024-02-21-14.57.37.png?alt=media" alt=""><figcaption><p>Copy the Google Service Account email address</p></figcaption></figure>

Visit your Google Search Console, select the site that you want to submit for indexing. Click on **Settings** > **Users and Permissions**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0efc0309590f187db218226bbe9116a3685bcbb8%2FXnapper-2024-02-21-15.02.18.png?alt=media" alt=""><figcaption></figcaption></figure>

Click the "**Add User**" button, then paste the Google Service Account that you copied previously. Select "Owner" permission for the new user.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7e60d9a24cf7a0df916ea852e1dbf5e33f215278%2FXnapper-2024-02-21-15.04.49.png?alt=media" alt=""><figcaption><p>Add a new user</p></figcaption></figure>

{% hint style="info" %}
If you have multiple Google Service Accounts, you will need to add multiple users.
{% endhint %}

### Connect your Google Search Console Sites & Sitemaps

If you haven't connected a site on your Google Search Console, please follow [this guide](/guide/google-search-console) to do that.

After connecting a site, SEO Utils will pull all the sitemaps that you entered on your Google Search Console.

If you haven't added a sitemap to your Google Search Console account, you can add sitemaps manually on SEO Utils

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e40a6b6a8f898d73fe89593d9c2185b2b58c7560%2FXnapper-2024-02-21-15.18.08.png?alt=media" alt=""><figcaption><p>Add a sitemap manually.</p></figcaption></figure>

{% hint style="info" %}
You can add as many sitemaps as you want.
{% endhint %}

After adding sitemaps, you can fetch all URLs from them by clicking the "**Fetch URLs From All Sitemaps**" action. SEO Utils will pull all URLs from all sitemaps and check the index of every single URL.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-81dc864511337c2a64af9c3c3db434d6aef20d54%2FXnapper-2024-02-23-18.23.42.png?alt=media" alt=""><figcaption><p>Fetch URLs From All Sitemaps</p></figcaption></figure>

### Checking Index

You can trigger a process to bulk-check the index for all URLs on your site by clicking the **Check Index** action.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-edc2692121b031d82bfda9473d6f62ea4b8132fe%2FXnapper-2024-02-23-18.28.56.png?alt=media" alt=""><figcaption><p>Bulk-check index</p></figcaption></figure>

You can also check index for a single URL by clicking the vertical dots icon.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8d92f478c7945abb760fa97ccb926fd739f16da6%2FXnapper-2024-02-23-18.31.16.png?alt=media" alt="" width="375"><figcaption><p>Check index for a URL</p></figcaption></figure>

#### Two Checking Index Methods

**#1. Using Google Search Console API (default)**

Since March 4, 2024, SEO Utils has supported checking index by using [Search Console URL Inspection API](https://developers.google.com/search/blog/2022/01/url-inspection-api). This method has some pros when compared to method #2 which uses the "site:url" operator.

* Do not require proxies, so no extra cost.
* Faster, can check 10 URLs per second.
* Easy to set up, just need to enable the Google Search Console API.

However, there are some [quota limits](https://developers.google.com/webmaster-tools/limits#url-inspection). The quota is enforced per Search Console [website property](https://support.google.com/webmasters/answer/34592) (calls querying the same site):

* 2,000 queries per day
* 600 queries per minute

So if you reach the limit, you might want to switch to the #2 method.

Moreover, the Google Search Console API method also gives you [some extra information](https://developers.google.com/webmaster-tools/v1/urlInspection.index/UrlInspectionResult) that the second method doesn't provide like

* Indexing State
* Coverage State
* Crawled Date

You can hover on the blue "info" icon to see that information.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6b5650e7ebf77f0bfe7f99e5b811821c49900f88%2FXnapper-2024-03-04-15.25.24.png?alt=media" alt="" width="563"><figcaption><p>Extra information that the first method gives you.</p></figcaption></figure>

{% hint style="info" %}
There is a filter for the Indexing State, so you can tell why the URL is not allowed to be indexed.

<img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-384d5c71fdc2c2b85977f82bbddf64c8d152502b%2FXnapper-2024-03-04-15.30.31.png?alt=media" alt="" data-size="original">
{% endhint %}

**#2. Using the "site:url" Operator**

When using this method, SEO Utils will search Google using the "site:url" operator to see if the URL is on the SERP.

This method doesn't have a quota limit but you want to consider [using Proxies](/guide/how-to-use-proxies) to prevent Google from blocking your IP when checking thousands of URLs.

#### Switching Method

You can click on the "cog icon" button to switch the method. The method is saved on the site scope, which means you can use method #1 for site A and method #2 for site B.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ace57840c9047efebaecf24f275b33b1f0dd0e8d%2FXnapper-2024-03-04-15.31.17.png?alt=media" alt=""><figcaption><p>Switching checking index method.</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3f26ebf72e433fc4afb87da47dbeeaff4a4ea697%2FXnapper-2024-03-04-15.33.56.png?alt=media" alt="" width="563"><figcaption><p>Click the "Update" button to save the settings.</p></figcaption></figure>

### Submitting Index

Just like the "Check Index" action, you can submit either multiple URLs or just one URL for indexing.

When you bulk-submit URLs, SEO Utils will submit all URLs regardless of their indexed or submitted status.

### Auto Index Feature

SEO Utils provides an auto-pilot mode so you don't need to pull URLs from sitemaps, check & submit index manually.

To enable the Auto Index feature of a site, please ensure that you toggle the **Auto Index** field on.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-06ce3423c202ce45f8a8bcac50b0df19807352ba%2FXnapper-2024-02-25-09.38.00.png?alt=media" alt=""><figcaption><p>Enable Auto Index for sites</p></figcaption></figure>

You can also enable the Auto Index feature for specific sitemaps by visiting the Sitemaps list page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-11d3ca8e86620a37f2eae8b7ef7693777f7bc894%2FXnapper-2024-02-25-09.40.00.png?alt=media" alt=""><figcaption><p>Enable Auto Index for all URLs of a specific sitemap</p></figcaption></figure>

You can tell if a URL is enabled for auto-indexing if the URL is yellow like this.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-18ec7d373fbecdbdc9c6fe0eb409f35d2230a5eb%2FXnapper-2024-02-25-09.50.57.png?alt=media" alt=""><figcaption><p>URLs are disabled for auto-indexing</p></figcaption></figure>

{% hint style="info" %}
When URLs are disabled for auto-indexing, SEO Utils won't automatically check and submit them for indexing. However, you still can manually do that by using "**Check Index**" & "**Submit Index**" actions.
{% endhint %}

{% hint style="info" %}
To use the Auto Index feature, you need to keep SEO Utils running on your machine or use a VPS, so you don't need to keep your computer on constantly.
{% endhint %}

#### Auto Pull URLs From Sitemaps

SEO Utils will pull URLs from all sitemaps daily at **5:00 AM (your local time)** to get new URLs and check if the existing URLs have content updated by using the Last Mod field.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a0625dd09e89f6edb367778bc35c440606b66913%2FXnapper-2024-02-25-10.00.18.png?alt=media" alt=""><figcaption><p>Using Last Mod field to detect if the content of a URL is updated.</p></figcaption></figure>

{% hint style="success" %}
If a URL has updated content, SEO Utils will resubmit it for indexing, regardless of the submission status.
{% endhint %}

#### Auto Check Index

SEO Utils will check index of all sites that enable the Auto Index feature at **6:00 AM (your local time).**

**Note:** It will skip the URLs that belong to a sitemap with the Auto-Index setting turned off.

{% hint style="info" %}
Please consider [using Proxies](/guide/how-to-use-proxies) if you have many URLs to check index.
{% endhint %}

#### Auto Submit Index

SEO Utils will submit for indexing all sites that enable the Auto Index feature **every 10 minutes**.

**Note:**

* It will skip the URLs that belong to a sitemap with the Auto-Index setting turned off.
* The auto-pilot mode only submits URLs that have already been checked for indexing. You don't have a setting to ignore this behavior like when running the "**Submit Index**" action manually.

### Override the Auto-Mode Behavior

This is the default behavior of the Auto-mode

* **Checking index**: If a URL is already **indexed**, it won't re-check index for that URL in the subsequent runs.
* **Submitting index**: If a URL is already **submitted** or **indexed**, it won't re-submit that URL in the subsequent runs.

If you would like to override those behaviors, please open the Site setting modal.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6abc5f722fd1ce0a011f6e5ac30c65d1810a6339%2FXnapper-2024-04-24-20.50.12.png?alt=media" alt=""><figcaption><p>Open the setting modal.</p></figcaption></figure>

You will see 2 fields:

* **Auto Recheck Index After** field: You can specify the number of days to recheck the index even if the URL is already indexed.
* **Auto Resubmit Index After** field: You can specify the number of days to resubmit URLs even if URLs are already submitted but not indexed.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3103503eff0a4fc12346d3e3442be88955c7ab4a%2FXnapper-2024-04-24-20.54.07.png?alt=media" alt=""><figcaption><p>Override the Auto-mode behavior</p></figcaption></figure>

{% hint style="info" %}
Those two fields will only be shown if you **turn on the Auto mode** for the site.
{% endhint %}

### Quick Tips

You can view all the logs of check and submit for indexing of each URL by clicking the log bar at the bottom.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-11b7c6387e4c37ce026b37df6753c54aacb07568%2FXnapper-2024-02-25-10.18.50.png?alt=media" alt=""><figcaption><p>View logs</p></figcaption></figure>

You can quickly switch between pages on a site by using the dropdown menu in the header section.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-154c1cbf009befaaa2a90b05be4bccda6167829e%2FXnapper-2024-02-25-10.43.03.png?alt=media" alt=""><figcaption><p>Quickly move to a page</p></figcaption></figure>

### Updates on March 22, 2024

You can now set which Google service accounts you want to use on specific sites.

For example, if you set up a Google Search Account can be used on site A. SEO Utils will only use that account to check & submit index for that site only.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c3d2553e0974f3ecaaac7e3c4c4d70f2f2754c09%2F431388398_7260302147372284_1054525268246411615_n.jpg?alt=media" alt=""><figcaption><p>Set site scopes for each Google Service Account</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2148d15b70a3b268de8e88a2f78c625b69581724%2F431629039_7260302684038897_1728235001124597070_n.jpg?alt=media" alt=""><figcaption><p>Select a site where you want to use the Google Service Account.</p></figcaption></figure>


# IndexNow

While the [Auto-Indexing tool](/guide/auto-indexing-tool) only submits your URLs to Google, the [IndexNow](https://www.indexnow.org/index) tool submits your URLs to many other search engines like Bing, Yandex, Naver, Seznam.cz, and Yep with just **one submission**.

### How to Integrate IndexNow to SEO Utils?

#### Step 1: Get an API Key

Visit <https://www.bing.com/indexnow/getstarted>, you will see a form like this to generate an API key.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-dbb8abe46a4964c6969160642d4697ce144916e9%2FCleanShot%202024-03-21%20at%2016.58.01%402x.png?alt=media" alt=""><figcaption><p>Generate a IndexNow API key</p></figcaption></figure>

Click the "**Generate**" button to get an API Key, then click the "**Download**" icon to download the API Key file.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0f63d29bdce5bf966034ff7c6d8b582931220caf%2FXnapper-2024-03-21-17.01.49.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Step 2: Upload the Key File to the Root of Your Website

You will need to host your downloaded key file (Step 1) at the root of your website.

If your website domain is **tuikhoeconban.com**, then the file should be located at <https://tuikhoeconban.com/c52ff0461aee4edf836b8ff0d24c5ff8.txt>

You can visit that URL to validate if the file is uploaded successfully.

#### Step 3: Add Sitemap URLs to SEO Utils

Open the SEO Utils app and click the IndexNow in the left sidebar to access the tool.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1ec044300daf40b0937c55c0a784e607aaaea804%2FCleanShot%202024-03-21%20at%2017.09.51%402x.png?alt=media" alt=""><figcaption><p>IndexNow tool in SEO Utils</p></figcaption></figure>

Click the "Import URLs" button or the "Plus" icon to add sitemap URLs.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-439ec4218588850d7caf2cc2cac04c37946900c4%2FXnapper-2024-03-21-19.43.56.png?alt=media" alt=""><figcaption><p>Add sitemap URLs</p></figcaption></figure>

After adding sitemap URLs, SEO Utils will import all the URLs. You can also switch the sites by using the Site dropdown.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1c670034e8ff92ff2460aa1cdbe957a20ffd3d66%2FXnapper-2024-03-21-19.45.11.png?alt=media" alt=""><figcaption><p>Switching to a site to view URLs</p></figcaption></figure>

#### Step 4: Add IndexNow API Key to Sites

While selecting a site, you will see the "Cog" icon. Click on it to open the settings modal.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e5121bc7f6b1fb4f4c8562d3f9fa5fcad6a69d19%2FXnapper-2024-03-21-19.48.02.png?alt=media" alt="" width="563"><figcaption><p>Open the Site Settings modal</p></figcaption></figure>

Enter the IndexNow API Key you got from **Step 1** and hit the "Save" button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-bb0f6f6ee0f54fc90eec3504f891994993ff57f6%2FXnapper-2024-03-21-19.50.10.png?alt=media" alt=""><figcaption><p>Enter the API Key</p></figcaption></figure>

Now, all the setup is done. You are ready for indexing submission!

### Checking Index <a href="#checking-index" id="checking-index"></a>

You can trigger a process to bulk-check the index for all URLs on your site by clicking the **Check Index** action.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1367e600c6736f8ff4673e46c16980a97c501d26%2FXnapper-2024-03-22-10.23.55.png?alt=media" alt=""><figcaption><p>Bulk check index action</p></figcaption></figure>

You can also check index for a single URL by clicking the vertical dots icon.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-97e88e9c9e56d9de5e1202e758e27aca6264eee8%2FXnapper-2024-03-22-10.26.34.png?alt=media" alt="" width="563"><figcaption><p>Check index for a URL</p></figcaption></figure>

{% hint style="info" %}
SEO Utils will search Bing and other search engines using the "site:url" operator to see if the URL is on the SERP.

You want to consider [using Proxies](https://help.seoutils.app/guide/how-to-use-proxies) to prevent the search engines from blocking your IP when checking thousands of URLs.
{% endhint %}

### Submitting Index <a href="#submitting-index" id="submitting-index"></a>

Just like the "Check Index" action, you can submit either multiple URLs or just one URL for indexing.

When you bulk-submit URLs, SEO Utils will submit all URLs, regardless of their indexed or submitted status.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e8c09fd67563509b6b47718552d8b420d9d6ceab%2FXnapper-2024-03-22-10.40.30.png?alt=media" alt=""><figcaption><p>Bulk submit index action</p></figcaption></figure>

### Scheduled Jobs (Auto-mode)

* SEO Utils will pull URLs from all sitemaps daily at **5:00 AM (your local time)** to get new URLs and check if the existing URLs have content updated by using the Last Mod field from your sitemaps.
* SEO Utils will auto-check index of all sites at **6:00 AM (your local time).**
* SEO Utils will auto-submit your sites for indexing **every 10 minutes**.

{% hint style="info" %}
SEO Utils also detects when your content has been added or updated; it will automatically resubmit the URL. Just make sure to keep the app open at all times.
{% endhint %}

### Override the Auto-Mode Behavior

This is the default behavior of the Auto-mode

* **Checking index**: If a URL is already **indexed**, it won't re-check index for that URL in the subsequent runs.
* **Submitting index**: If a URL is already **submitted** or **indexed**, it won't re-submit that URL in the subsequent runs.

If you would like to override those behaviors, please open the Site setting modal.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b02cef9810e18407b0a057ead1e9a1f0f7969549%2FXnapper-2024-04-24-21.05.33.png?alt=media" alt=""><figcaption><p>Open the setting modal.</p></figcaption></figure>

You will see 2 fields:

* **Auto Recheck Index After** field: You can specify the number of days to recheck the index even if the URL is already indexed.
* **Auto Resubmit Index After** field: You can specify the number of days to resubmit URLs even if URLs are already submitted but not indexed.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f041d3a46a596ced06bc3bf53e27b48e5574fef7%2FXnapper-2024-04-24-21.06.29.png?alt=media" alt=""><figcaption><p>Override the Auto-mode behavior</p></figcaption></figure>

### Troubleshooting

#### URL received. IndexNow key validation pending

When you have just added a new API key and try to submit the index, you will see a message: "URL received. IndexNow key validation pending." This is because IndexNow needs to validate the API key with the file you uploaded to your website.

This message will disappear after a couple of minutes.

#### How to Fix 403 Forbidden Error: User is unauthorized to access the site. Please verify the site using the key and try again

This error occurs when IndexNow is unable to verify your site because you entered the wrong API key or the uploaded file was not located at the root of your website.

If this error keeps happening, you will need to **regenerate an API key** and complete the setup process again.

{% hint style="info" %}
If you have any further questions, please visit the FAQs section on the IndexNow website at <https://www.indexnow.org/faq>
{% endhint %}

### Two Checking Index Methods

Since version 1.17.0, SEO Utils now supports using the **Bing Webmaster Tools API** to check if a URL is indexed on Bing.com, in addition to the traditional **"site:url"** operator method.

To switch the checking index method of a site, please open the site setting modal.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7adde49ed45140c23181b1158b460fc95d813d2e%2FXnapper-2024-06-25-13.55.01.png?alt=media" alt=""><figcaption><p>Open the site setting modal.</p></figcaption></figure>

You can select the Bing Webmaster Tools API option from the "**Checking Index Method**" field.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-38d34d32a5707a3fb74c0cace3aee1d6431de402%2FXnapper-2024-06-25-13.56.32.png?alt=media" alt=""><figcaption></figcaption></figure>

You are required to enter a Bing Webmaster Tools API key. To get one, please visit <https://www.bing.com/webmasters/tools>.

Then, open the Settings panel to access the **API access** menu.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2f62f5ca757912f1988bba9ae27ab998fd1413eb%2FCleanShot%202024-06-25%20at%2013.59.59%402x.png?alt=media" alt=""><figcaption><p>API access from Settings panel</p></figcaption></figure>

Select the **"API Key"** menu to continue.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5702e8e1a164ae5a38f1f8b6870767c617be20d6%2FXnapper-2024-06-25-14.02.57.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

After creating an API Key, please copy it and paste it into the **Bing Webmaster Tools API Key** field on SEO Utils.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c371ac81f49898c3a1155e2194c1e8098e3808f2%2FCleanShot%202024-06-25%20at%2014.04.05%402x.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

That's all! Now, you can check the index of URLs by using the Bing Webmaster Tools API.


# Google My Business Rank Tracker

The Google My Business (GMB) Rank Tracker shows where your Google Business Profile ranks around a place. SEO Utils searches your keywords from a grid of spots around the business and draws the result as a map: a green pin where you are in the top 3, orange for 4 to 10, red for 11 to 20.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-bf14cf98c2271ff5059976c43959bc20502497b2%2Fgmb-report-workspace.png?alt=media" alt="A report with the map in the middle, the keyword and run chips above it and the details drawer below"><figcaption><p>A report: the grid on the map, the keyword (1) and run (2) chips, the list switch (3), the map tools (4), the legend (5) and the drawer tabs (6)</p></figcaption></figure>

## What it tracks

Every report checks **Google Maps**. You can also turn on two more lists that Google Search shows for the same search. They are different lists, so the same business can rank differently in each. See [Local Pack and Local Finder](/guide/google-my-business-rank-tracker/local-pack-and-local-finder).

| List             | What it is                                                               | How a spot reads                                                                |
| ---------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
| **Google Maps**  | The list a searcher sees in the Google Maps app, top 20. Always tracked. | Your rank, or **21+** when you are not in the top 20                            |
| **Local Pack**   | The up to three businesses in the box on the Google Search results page. | In the pack or not, as a share of spots. Also shows where Google showed no pack |
| **Local Finder** | The longer "More places" list behind the pack, top 20.                   | Your rank, or **21+**                                                           |

## What you get

* A map for every keyword and every run, with your rank at each spot and the change since the run before.
* The businesses that rank around you, their ratings, categories and [opening hours](/guide/google-my-business-rank-tracker/read-a-report#opening-hours).
* [History](/guide/google-my-business-rank-tracker/history): every run as a small map, maps over date ranges and a trend chart.
* [Compare](/guide/google-my-business-rank-tracker/compare) two runs, two businesses or two lists on the same map.
* [Report groups](/guide/google-my-business-rank-tracker/report-groups) that combine the locations of one business into a single dashboard.
* [PDF and HTML reports](/guide/google-my-business-rank-tracker/exports-and-client-reports), your own branding and a link you can share with a client.
* [Your AI app](/guide/google-my-business-rank-tracker/ask-your-ai-app) can set up reports, group them and read the results for you.

## What you need

* A **Google Places API key**. It finds your business and draws the maps.
* Your own **DataForSEO account**. It checks the rankings and bills each check, so a run costs money. The form shows the price before you start. The tracker does not run while DataForSEO's **Sandbox Mode** is on.

[Set up](/guide/google-my-business-rank-tracker/set-up) walks through both. Until they are done, the tracker's page shows a setup panel with a card for each missing step, and you can still lay a report out in the form. Scheduled runs only start while SEO Utils is open.

### Setup the Google Places API

Create the key with **Connect Google**, with your AI app or by hand, then paste it in **Settings → Services → Google Business Rank Tracker**. The steps are in [Set Up](/guide/google-my-business-rank-tracker/set-up#google-places-api-key).

### Interactive maps in HTML exports

The **Interactive Maps API Key** setting is explained in [Exports and client reports](/guide/google-my-business-rank-tracker/exports-and-client-reports#interactive-maps-in-html-exports).

## Team members

[Team members](/guide/team) you invite can use the tracker in the browser, in the workspaces you gave them. Their [role](/guide/team/inviting-your-team#roles) decides what they can do: a Viewer reads reports, an Analyst also runs and exports them and adds tags and notes, and a Manager also creates, edits, imports, publishes and deletes. Runs spend your DataForSEO credit, so they need **Can use the owner's machine and accounts**. The RingTonic campaign of a report stays with you.

## Guides

{% content-ref url="/pages/eGbdP53tVwnXCQSkxSVN" %}
[Set Up](/guide/google-my-business-rank-tracker/set-up)
{% endcontent-ref %}

{% content-ref url="/pages/pe4cEY6xitA5dolfDiI9" %}
[Create a Report](/guide/google-my-business-rank-tracker/create-a-report)
{% endcontent-ref %}

{% content-ref url="/pages/LUh7WZcD1ezNir0wXrX5" %}
[Run and Schedule](/guide/google-my-business-rank-tracker/run-and-schedule)
{% endcontent-ref %}

{% content-ref url="/pages/mURj1KywOuh19SJyLD3W" %}
[Your Reports](/guide/google-my-business-rank-tracker/your-reports)
{% endcontent-ref %}

{% content-ref url="/pages/fUrE48XVfi6MMWrt7d9F" %}
[Read a Report](/guide/google-my-business-rank-tracker/read-a-report)
{% endcontent-ref %}

{% content-ref url="/pages/tLXD4VeGzDwBNgcg1z0Q" %}
[Spot](/guide/google-my-business-rank-tracker/spot)
{% endcontent-ref %}

{% content-ref url="/pages/ZTTbmDsJ4SW05bd8VFhn" %}
[Local Pack and Local Finder](/guide/google-my-business-rank-tracker/local-pack-and-local-finder)
{% endcontent-ref %}

{% content-ref url="/pages/2EhzNeNUn0rWw5Pe8mkb" %}
[History](/guide/google-my-business-rank-tracker/history)
{% endcontent-ref %}

{% content-ref url="/pages/tEayoEH6EuRL4ApcOIoa" %}
[Compare](/guide/google-my-business-rank-tracker/compare)
{% endcontent-ref %}

{% content-ref url="/pages/HYrVWLDrjgOO9PxarAzq" %}
[Map Tools and Styles](/guide/google-my-business-rank-tracker/map-tools)
{% endcontent-ref %}

{% content-ref url="/pages/3iiprpDq77W4A4b3OU1l" %}
[Report Groups](/guide/google-my-business-rank-tracker/report-groups)
{% endcontent-ref %}

{% content-ref url="/pages/eQgvJl2viaxCAgbzR3vk" %}
[Exports and Client Reports](/guide/google-my-business-rank-tracker/exports-and-client-reports)
{% endcontent-ref %}

{% content-ref url="/pages/5n0AWwV0JmckBucCZtML" %}
[Ask Your AI App](/guide/google-my-business-rank-tracker/ask-your-ai-app)
{% endcontent-ref %}

{% content-ref url="/pages/sOz17rigs64JUQSgdFI6" %}
[Manage Reports](/guide/google-my-business-rank-tracker/manage-reports)
{% endcontent-ref %}


# Set Up

The GMB Rank Tracker needs two things before its first run: a **Google Places API key** and your own **DataForSEO account**. A few optional keys add map layers and interactive exports.

## What you see until it is set up

Open **Local SEO → GMB Rank Tracker**. The page shows what is missing, so you do not have to look for it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7660defd421729e47fbd8abf1f6400d965b085db%2Fgmb-onboarding-setup-panel.png?alt=media" alt="The setup panel with a DataForSEO API card and a Google Places API key card, beside the What a report shows preview"><figcaption><p>Nothing set up and no report yet: the setup panel (1) has a card for each missing step, with <strong>What a report shows</strong> beside it (2). The Google Places API key card also offers <strong>Connect Google</strong> (3)</p></figcaption></figure>

* **Nothing set up and no reports:** **Set up GMB Rank Tracker to start** ("Do it yourself, or let your AI app guide you.") lists the steps that are missing, **DataForSEO API** and **Google Places API key**. Each card has **Open settings**, **Set up with your AI app** and **Read the guide**, and the Google Places API key card also has **Connect Google**. **What a report shows** is a sample grid with three lines on what a report tracks, so you see what the two steps are for. A card disappears when you finish its step, and the page updates when you come back
* **You have reports and a step is missing:** the panel shrinks to **New runs are paused: a setup step needs you** above your reports. The reports and their history stay readable
* **Everything is set up and you have no reports:** the page reads **Create your first report**. See [Your reports](/guide/google-my-business-rank-tracker/your-reports#create-your-first-report)

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ee555507305a4c21074dc01a40c7c68c78207c14%2Fgmb-onboarding-compact-panel.png?alt=media" alt="The compact panel above the reports with the two step cards"><figcaption><p>With reports, the panel sits above the list. <strong>Open settings</strong> on the DataForSEO API card (1) and <strong>Connect Google</strong> on the Google Places API key card (2) start the two steps</p></figcaption></figure>

**Open settings** opens the settings card for the step and highlights the field to fill. **Set up with your AI app** copies the prompt for that step, ready to paste in your AI app, or opens the page that connects one. **Connect Google** creates the Google key for you.

You can still click **New report** while a step is missing and lay the report out. Running it needs DataForSEO. See [If DataForSEO is not set up](/guide/google-my-business-rank-tracker/create-a-report#if-dataforseo-is-not-set-up).

The report page and the new report form need the Google key to show the map. Without it, the report page shows **Connect Google to see your grid on the map** in place of the map, and the rest of the page keeps working. The new report form shows the same card until the key is set.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-419d13fb2d6359fca18d788ad06a55085cddd97b%2Fgmb-map-no-key.png?alt=media" alt="The Connect Google to see your grid on the map card with its three buttons: Connect Google automatically, Paste a key and Set up with your AI app"><figcaption><p>The card that stands in for the map, with <strong>Connect Google automatically</strong>, <strong>Paste a key</strong> and <strong>Set up with your AI app</strong></p></figcaption></figure>

**Paste a key** opens the key field in the settings. **How it works** opens [Set Up SEO Utils](/guide/set-up-seo-utils#connect-google-automatically).

## Google Places API key

One key does three jobs: it finds your business, draws the maps and turns addresses into coordinates. Pick one way to create it.

{% tabs %}
{% tab title="With Your AI App" %}
When your AI app is connected to SEO Utils (see [Set Up with Your AI App](/guide/set-up-seo-utils#set-up-with-your-ai-app-recommended)), ask it:

> Set up the Google Places API key for the GMB Rank Tracker.

It checks what is missing, starts **Connect Google** with the Google Maps tools on and explains each step. You sign in to Google and answer its questions in SEO Utils: Google Cloud's terms and, if you want the map to work, a billing account. The key goes straight into SEO Utils, never through the chat.
{% endtab %}

{% tab title="Connect Google (Recommended)" %}
SEO Utils creates the key for you, with the three APIs it needs.

1. Click **Connect Google** on the setup panel, or open **Settings → Services → Google Business Rank Tracker** and click **Create a key automatically** under **Google Places API Key**. Both open **Connect Google** with the **Google Maps tools** switched on
2. Click **Connect Google**, sign in to Google and click **Allow**

It takes about 3 minutes. If SEO Utils asks a question on the way, see [Connect Google Automatically](/guide/set-up-seo-utils#connect-google-automatically).
{% endtab %}

{% tab title="By Hand" %}

1. Go to [console.cloud.google.com](https://console.cloud.google.com/) and choose an existing project or create one
2. Search for "**APIs & Services**" in the top search bar

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-87bc621c15416903c2a82885e722277511e8edc1%2FXnapper-2024-06-07-15.59.02.png?alt=media" alt=""><figcaption><p>Search for "APIs &#x26; Services"</p></figcaption></figure>

3. Click **Library** in the left sidebar

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0aa4d95c3a9bd9bb1d4c78366c8c5ab8180b413e%2FXnapper-2024-06-07-16.02.10.png?alt=media" alt="" width="563"><figcaption><p>Select "Library" from the left sidebar</p></figcaption></figure>

4. Search for "Places API", select **Places API (New)** and enable it

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-817c1bb40e2dfdb9ec11d379b9b1ebac97ae4d15%2FXnapper-2024-06-07-16.09.29.png?alt=media" alt="" width="563"><figcaption><p>Enable Places API (New)</p></figcaption></figure>

5. Search for "**Maps JavaScript API**" and enable it

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7b1db15882e576d12b2851fddf47a5b738679b4a%2FXnapper-2024-06-07-22.56.59.png?alt=media" alt="" width="563"><figcaption><p>Enable the Maps JavaScript API</p></figcaption></figure>

6. Search for "**Geocoding API**" and enable it

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ef6b32fde953f456f96ffd992970e0a3d50c80b6%2FCleanShot%202024-06-07%20at%2023.22.31%402x.png?alt=media" alt="" width="563"><figcaption><p>Enable the Geocoding API</p></figcaption></figure>

7. Open **Keys & Credentials** from the left sidebar, click **Create Credentials** and choose **API key**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b7aac10a096b7a036df741c4eaa17f97ce096678%2FXnapper-2024-06-07-16.08.57.png?alt=media" alt="" width="563"><figcaption><p>Create an API key</p></figcaption></figure>

8. Optional: click **Edit API key** to give it a name. You do not need to restrict it, because it stays on your computer. If you do restrict it, restrict it by API to the three above, never by website (HTTP referrer)

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-41c381ee92274f0d6117e52275a52d3ca1c85823%2FXnapper-2024-06-07-16.12.20.png?alt=media" alt="" width="563"><figcaption><p>Name your API key</p></figcaption></figure>

9. Copy the key. In SEO Utils, open **Settings → Services → Google Business Rank Tracker**, paste it in **Google Places API Key** on the **Google My Business Rank Tracker** card and click **Save**. **Paste a key** on the map card and **Open settings** on the setup panel open the same field

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7a30f54598beab8b30ff1afc5d397bed55f2114e%2Fgmb-settings-places-key.png?alt=media" alt="The Google Places API Key field with a placeholder key and the Create a key automatically button"><figcaption><p>The key goes in the Google Places API Key field (1). The button under it (2) creates a key for you</p></figcaption></figure>

{% hint style="warning" %}
Google may ask for billing details because the Places API is an enterprise API. It includes a free monthly allowance, and SEO Utils uses very little of it.
{% endhint %}
{% endtab %}
{% endtabs %}

## DataForSEO

DataForSEO runs the searches and bills each one, so you need your own account with credit on it. A [rented API key](/guide/rent-dataforseo-api-key) does not work for the GMB Rank Tracker. SERP API: DataForSEO is the only data source for now; your own IP and proxies are not available yet.

{% tabs %}
{% tab title="With Your AI App" %}
Ask your AI app to set up DataForSEO for the GMB Rank Tracker. It explains what a run costs, opens the DataForSEO settings for you and checks again after you save. You paste the API login and password in SEO Utils, never in the chat.
{% endtab %}

{% tab title="By Hand" %}

1. Create an account at DataForSEO and verify your email
2. Top up your credit
3. Copy the **API login** and **API password** from the API Access page of the DataForSEO dashboard. They differ from your dashboard login
4. In SEO Utils, click **Open settings** on the **DataForSEO API** card, or open **Settings → Services → DataForSEO API**. On the **DataForSEO Settings** card, paste the login in **Username** and the password in **Password**, then click **Save**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-51e1e740882593b6f8131ccfdc8ca8ada30951d7%2Fgmb-settings-dataforseo.png?alt=media" alt="The DataForSEO Settings card with the Username and Password fields and the Sandbox Mode switch"><figcaption><p>The DataForSEO Settings card: the <strong>Username</strong> and <strong>Password</strong> fields and the <strong>Sandbox Mode</strong> switch, which must stay off</p></figcaption></figure>

The full steps are in [SEO Data Source](/guide/seo-data-source#how-to-connect-your-dataforseo-account-to-seo-utils).
{% endtab %}
{% endtabs %}

### Sandbox Mode

The GMB Rank Tracker does not run while **Sandbox Mode** is on in the DataForSEO card. It does not fall back to dummy data: **Run now** is refused, scheduled runs are skipped and a new report cannot be saved and run. The page says so and links to the setting.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cdc0b063006a174569744377c40ec36143e2fd30%2Fgmb-onboarding-sandbox-alert.png?alt=media" alt="The alert DataForSEO Sandbox Mode is on, and GMB Rank Tracker cannot run in it, with the link Turn it off in DataForSEO settings"><figcaption><p>With Sandbox Mode on, the alert links to the setting: <strong>Turn it off in DataForSEO settings</strong></p></figcaption></figure>

Click **Turn it off in DataForSEO settings**, switch **Sandbox Mode** off and click **Save**. The new report form shows the same alert, and its **Save and run** button is off, with the tooltip **Turn off DataForSEO Sandbox Mode to run this report**.

## Optional keys

These live on the same settings card as the Google key, **Settings → Services → Google Business Rank Tracker**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0902766b907e46086c4a612a85770949f74c4f01%2Fgmb-settings-other-keys.png?alt=media" alt="The Geoapify, Census, RingTonic and Interactive Maps API key fields"><figcaption><p>The optional keys: Geoapify (1), RingTonic (2) and Interactive Maps (3)</p></figcaption></figure>

| Key                             | What it is for                                                                                                | Guide                                                                                                                            |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Geoapify API Key**            | The Demographics layer outside the US, Canada, the UK and Australia                                           | [Map tools](/guide/google-my-business-rank-tracker/map-tools#demographics-layer)                                                 |
| **Census API Key**              | Your own US Census key, instead of the built-in one                                                           | [Map tools](/guide/google-my-business-rank-tracker/map-tools#demographics-layer)                                                 |
| **RingTonic API Key**           | The Money Map layer                                                                                           | [Map tools](/guide/google-my-business-rank-tracker/map-tools#money-map)                                                          |
| **Interactive Maps API Key**    | A restricted key for HTML exports whose maps stay clickable                                                   | [Exports and client reports](/guide/google-my-business-rank-tracker/exports-and-client-reports#interactive-maps-in-html-exports) |
| **Browser Maps JavaScript Key** | The map in the remote browser and in published client reports. Anyone who opens a published report can see it | [Exports and client reports](/guide/google-my-business-rank-tracker/exports-and-client-reports#publish-to-a-client)              |

The same card holds the [marker colour, size and glow](/guide/google-my-business-rank-tracker/map-tools#marker-styles) settings.


# Create a Report

A report follows one business across a grid of spots, for a list of keywords, on a schedule. The form has four steps beside a live map, and the price of a run stays in view under the map.

{% hint style="info" %}
The form needs a [Google Places API key](/guide/google-my-business-rank-tracker/set-up#google-places-api-key) to show the map. Running the report needs a [DataForSEO account](/guide/google-my-business-rank-tracker/set-up#dataforseo), but you can lay the report out without one. See [If DataForSEO is not set up](#if-dataforseo-is-not-set-up).
{% endhint %}

## Open the form

In the sidebar, open **Local SEO → GMB Rank Tracker** and click **New report**. To start from a report you already have, see [Clone a report](/guide/google-my-business-rank-tracker/manage-reports#clone-a-report). To bring in a history from another tool, see [Import](/guide/google-my-business-rank-tracker/your-reports#import).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e67ecbf6caf4d44e3328ab0b5fe6dfb761de22f5%2Fgmb-form-new.png?alt=media" alt="The first step of the new report form with the business search and the grid settings"><figcaption><p>The first step of the form. The map is on the right and the price of a run under the map</p></figcaption></figure>

## The four steps

{% stepper %}
{% step %}

#### Business and area

**Find the business.** Under **Search With**, pick **Google Places API**, type the business name or address in **Address** and choose it from the list. For a Service Area Business without a street address, pick **Google Maps URL**, paste the business's Google Maps link and click **Fetch Address**.

**Shape the grid.** The grid is the set of spots SEO Utils searches from. Choose a **Grid Shape**: **Square**, **Circle** or **Draw an area**. For a Square or a Circle, also choose a **Size**.

| Setting                   | What it does                                                                                                                                                                                                                      |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Square** and **Circle** | A grid centred on the business. The **Size** list goes from 3x3 to 15x15. A Square 3x3 has 9 spots, a 5x5 has 25, a 15x15 has 225. A Circle has fewer spots for most sizes. The open **Size** list shows how many each size makes |
| **Draw an area**          | A boundary you draw on the map, filled with spots. See [Draw an area](#draw-an-area) below                                                                                                                                        |
| **Size → No preset**      | The first option of the **Size** list: a blank map where you add every spot yourself                                                                                                                                              |
| **Use Radius**            | On, the grid reaches out to the **Radius** you pick from the centre. Off, you set the **Spacing** between spots                                                                                                                   |
| **Units**                 | **mi** or **m**. SEO Utils starts with miles when your default location is the US, and meters otherwise                                                                                                                           |

{% hint style="info" %}
In a dense city, 1 to 1.5 miles of radius works well. In a rural area, go up to 10 miles.
{% endhint %}

**Edit the spots on the map.** The hint bar under the map lists the shortcuts:

* Click the map to **add a spot**. Click a spot to **turn it off**: SEO Utils does not search or charge a spot that is off
* Drag a spot to move it. When you create a report, drag the business pin to move the whole grid
* Hold **Shift** and drag to select several spots, then move them together or press **Delete** to remove them
* Press **Cmd/Ctrl + Z** to undo

**Turn off spots where no one lives.** Click **Turn off points where no one lives** and SEO Utils turns off every spot that falls on water, forest, scrub, wetland, sand, bare rock, glacier or military land, using public OpenStreetMap data. A message says how many it turned off, and you can turn any spot back on. The check sends your spot coordinates to OpenStreetMap, needs no key and takes a few seconds on a large grid.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a27349d280b836e14e0871dcb664535b626d93fd%2Fgmb-form-step1.png?alt=media" alt="Step 1 open with the grid shape and size, and the map with the grid on it"><figcaption><p>Step 1: the grid settings and the button that turns off spots where no one lives (1). The price of a run is under the map</p></figcaption></figure>
{% endstep %}

{% step %}

#### Keywords and result sets

* **Keywords:** one per line. On an existing report, the box adds new keywords. Manage the others, paused ones included, in the report's [Keywords tab](/guide/google-my-business-rank-tracker/manage-reports#manage-keywords)
* **Location** and **Language:** the language is sent with every search. The location is a country or territory, never a city, and does not move the searches: **the grid decides where they come from**. To search as if from another area, move the grid
* **Lists to track:** **Google Maps** is always on. Turn on **Local Pack** and **Local Finder** to track them too. Each list shows its price per check. See [Local Pack and Local Finder](/guide/google-my-business-rank-tracker/local-pack-and-local-finder)
* **Speed:** **Normal** returns results in up to 5 minutes. **High, 2× price** returns them in up to 1 minute and costs twice as much
* **Data source:** **SERP API: DataForSEO**. Own IP and proxies are marked as coming soon

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d47fda766cec11b36bdb1fcbc485386ca1b6cac2%2Fgmb-form-step2.png?alt=media" alt="Step 2 open with the keyword box, the three lists and their prices"><figcaption><p>Step 2: the lists to track (1) with their price per check</p></figcaption></figure>
{% endstep %}

{% step %}

#### Schedule

Choose how often the report runs.

| Schedule            | When it runs                                                                      |
| ------------------- | --------------------------------------------------------------------------------- |
| **One time**        | Once, when you save. Run it again by hand whenever you want                       |
| **Daily**           | Every day                                                                         |
| **Weekly**          | Once on each day you pick                                                         |
| **Twice per month** | Once between the 1st and 14th, and once between the 15th and the end of the month |
| **Monthly**         | Once a month                                                                      |

To run in business hours, set a time window and a **Timezone**. Turn off **Run on any days** to pick days:

* **Weekly:** tick as many days as you like. The report runs on each of them
* **Twice per month** and **Monthly:** pick one day. The report runs on the first such day of each period, so Monthly + Monday runs on the first Monday of the month

{% hint style="info" %}
A manual run counts for its period. If a weekly report is set for Sunday and you run it on Wednesday, Sunday's run is skipped because the week already has a run. SEO Utils must be open for scheduled runs to start.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f11f0f8fab647b0fc09ec86cbee5d587d4098dc1%2Fgmb-form-step3.png?alt=media" alt="Step 3 open with the frequency, the time window, the days and the timezone"><figcaption><p>Step 3: frequency, time window, days and timezone</p></figcaption></figure>
{% endstep %}

{% step %}

#### Report and integrations

* **Report Name:** how the report is called in the list and on exports
* **Show Changes:** show the change since the compared run on each pin
* **Comparison Days:** how many days back the report looks for the run to compare with
* **RingTonic Campaign UUIDs:** optional, for the [Money Map](/guide/google-my-business-rank-tracker/map-tools#money-map)

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5dc206c5fba770d0cbcced39bceac3aa12249b54%2Fgmb-form-step4.png?alt=media" alt="Step 4 open with the report name, show changes, comparison days and the RingTonic field"><figcaption><p>Step 4: name, change indicator, comparison days and RingTonic</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Draw an area

Choose **Draw an area** to cover a neighbourhood and skip water, forest or highways.

1. Click **Draw Polygon**, then click the map to place the corners of the area and click the first corner again to close it. Drag a corner to adjust the shape
2. Pick a **Pin Distribution**: **Grid-based** places spots in an even grid inside the area, at your **Grid Spacing**. **Random** places the **Number of Pins** you enter, up to 500
3. Click **Generate Pins**. **Clear Polygon** starts the area again

{% hint style="warning" %}
For a **Grid-based** area the spacing must be small compared with the area. A one-mile area needs about 0.1 miles of spacing: 0.5 miles gives only a few spots. A line under the buttons says how many pins the spacing makes and offers a spacing that fits.
{% endhint %}

Generated spots behave like any other: turn them off, move them or remove them.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-644f59f94f9fce22204e7dd2573c5485e6f762df%2Fgmb-form-polygon.png?alt=media" alt="A drawn area on the map filled with grid spots"><figcaption><p>A drawn area filled with spots</p></figcaption></figure>

## What a run costs

The bar under the map reads, for example, "25 points × 5 keywords = 125 checks per list", then the price of each list you track, the total **per run** and **about … a month** for the schedule. Spots that are off are left out. Local Pack and Local Finder add checks, and the price of each list shows next to its switch in step 2. Prices come from DataForSEO. See [Run and schedule](/guide/google-my-business-rank-tracker/run-and-schedule).

## Save

Click **Save and run** to create the report and start its first scan, which spends credit. In an existing report the button reads **Save**. **Cancel** goes back without saving.

## If DataForSEO is not set up

You can fill in the whole form before DataForSEO is set up. What changes:

* A notice at the top of the form reads **DataForSEO isn't set up**: "You can lay out the report now. Running it needs DataForSEO: each check is paid from your DataForSEO account." It has **Open settings**, **Set up with your AI app** and **Read the guide**
* **Save and run** is off. Hover it to read **Set up DataForSEO to run this report**
* **Data source** lists **SERP API: DataForSEO** with **Needs setup**
* The bar under the map reads **Price shows once DataForSEO is set up.** instead of the price

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-da80f272f966e27f6716b7b64ac58c56283aa783%2Fgmb-form-dataforseo-missing.png?alt=media" alt="The notice DataForSEO isn&#x27;t set up at the top of the form, with Open settings, Set up with your AI app and Read the guide"><figcaption><p>The notice (1) at the top of the form</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9719e08ef10a7a8f4dd6ab4244ced936bf34e1a4%2Fgmb-form-save-and-run-off.png?alt=media" alt="The top bar with Cancel and Save and run switched off, and the tooltip Set up DataForSEO to run this report"><figcaption><p><strong>Save and run</strong> is off until DataForSEO is set up</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-68bf6c31998ab7ba828a1d58694db1d9e39090d4%2Fgmb-form-price-needs-setup.png?alt=media" alt="The bar under the map reading Price shows once DataForSEO is set up."><figcaption><p>The bar under the map has no price yet</p></figcaption></figure>

What you typed and the grid you laid out are kept when you leave through **Open settings**, **Connect Google** or **Set up with your AI app** and come back, for up to 6 hours. Leaving the form any other way, including **Cancel**, forgets them. When DataForSEO is set up, the notice goes and **Save and run** turns on.

In Sandbox Mode the notice becomes the [Sandbox Mode alert](/guide/google-my-business-rank-tracker/set-up#sandbox-mode), and **Save and run** stays off until you turn it off.


# Run and Schedule

A run checks every enabled keyword from every spot that is on, on every list the report tracks, and saves the result as one **run** on the report's timeline. Each check is billed by DataForSEO, so a run costs money.

## Start a run

* **Run now** is the main button in the report's top bar. It asks "Are you sure you want to re-run this report?" and starts the run when you click **Re-run**
* **Run first scan** appears in the [reports list](/guide/google-my-business-rank-tracker/your-reports) on a report that has never run. It opens the report with the same question
* **Save and run** in the [new report form](/guide/google-my-business-rank-tracker/create-a-report#save) creates a report and starts its first scan
* On a schedule, SEO Utils starts the run itself while the app is open

{% hint style="danger" %}
Run now and the first scan spend DataForSEO credit. Read the price in the form's cost bar first.
{% endhint %}

## What a run costs

The cost bar under the map in the [report form](/guide/google-my-business-rank-tracker/create-a-report#what-a-run-costs) shows the checks and the price of each list, the total **per run** and **about … a month** for the schedule. Spots that are off and paused keywords are left out. Local Pack and Local Finder are extra checks, so they add to the price. The **High, 2× price** speed doubles it.

Prices come from DataForSEO and bill to your account. Until DataForSEO is set up, the bar reads **Price shows once DataForSEO is set up.** The **Retry failed checks** dialog shows its own estimated cost before you confirm it.

## Follow a run

The status button in the top bar names the run it covers, for example **Nov 9 · complete**. Click it for the run card:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1d6da94672fd0ea72c978a425faffbb46253fbc3%2Fgmb-report-run-status.png?alt=media" alt="The run card with Complete, the run date and the count of grid checks done"><figcaption><p>The run card: what happened, how many grid checks it had and how many are done</p></figcaption></figure>

While a run goes, the card shows its phase and the checks done so far. Results usually arrive within a few minutes: **Normal** speed returns in up to 5 minutes. The map fills in as they arrive.

| Control                 | When you see it                | What it does                                                                                                  |
| ----------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------- |
| **Cancel run**          | While the run is still sending | Stops sending checks. Checks already sent were paid for, and their results are still added when they arrive   |
| **Stop waiting**        | When every check is sent       | Stops waiting for the results that have not arrived. The run keeps what it has                                |
| **Retry failed checks** | After a run with failed checks | Sends the failed checks again, shows the estimated DataForSEO cost first and adds the results to the same run |

A run reads **Collecting** while results arrive, then **Complete** when every check returned, **Needs attention** when some did not, or **Cancelled** when you cancelled it. When some checks failed, the run chip says how many, for example **3 of 300 checks failed**. A run that did not finish cleanly keeps the results it collected.

{% hint style="info" %}
"Some results for this snapshot have not arrived from DataForSEO yet. They are added automatically when they arrive." means SEO Utils is still waiting for paid results. Nothing needs fixing. If you do not want to wait, use **Stop waiting**.
{% endhint %}

## Schedule

The schedule chip in the top bar, for example **Weekly · next Nov 16**, shows when the report runs next. Click it to **Pause schedule** or **Edit schedule**. A paused schedule reads **Paused** until you resume it. **Pause schedule** and **Resume schedule** are also in the title menu. The frequencies and the day rules are in [Create a report](/guide/google-my-business-rank-tracker/create-a-report#the-four-steps).

SEO Utils must be open for a scheduled run to start. A manual run counts for its period: a weekly report you ran by hand on Wednesday skips its Sunday run.

A report whose last run is 30 days old or more shows a **days ago** note in the [reports list](/guide/google-my-business-rank-tracker/your-reports) and in its [group](/guide/google-my-business-rank-tracker/report-groups), so you notice a schedule that stopped.

## When a run does not finish

1. Open the run card and read what it says about the checks that failed or are still waiting
2. Click **Retry failed checks** for the failed ones, or **Stop waiting** to close a run that is only waiting for results
3. Check your DataForSEO credit, and that **Sandbox Mode** is off on the **DataForSEO Settings** card (**Settings → Services → DataForSEO API**). The tracker does not run in Sandbox Mode: see [Sandbox Mode](/guide/google-my-business-rank-tracker/set-up#sandbox-mode)

{% hint style="info" %}
The old **Free Stuck GMB Rank Trackers** action is gone. Every run now keeps a record of each check, so **Stop waiting** and **Retry failed checks** work on the run itself.
{% endhint %}


# Your Reports

This page lists every report of the workspace with its latest figures, so you see which locations improved and which dropped before you open one. Open it from **Local SEO → GMB Rank Tracker**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b354521f9654c6d5ee3b3de348c5cc7ed1b016ac%2Fgmb-reports-table.png?alt=media" alt="The reports table with the list switch, the three figure columns and the Table and Cards switch"><figcaption><p>The list switch (1) picks the list for the pictures and sorts. Each report shows its figure on every list it tracks (2). Switch between Table and Cards (3), or create a report (4)</p></figcaption></figure>

## Create your first report

A workspace with no report has no table, filters or **Table | Cards** switch yet. What the page shows depends on the setup:

* **A step is missing:** the setup panel. See [Set up](/guide/google-my-business-rank-tracker/set-up#what-you-see-until-it-is-set-up)
* **Everything is set up:** **Create your first report**, with **New report** and **Import**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8c02394124a952308aa60427532261ec01273e22%2Fgmb-onboarding-first-report.png?alt=media" alt="The Create your first report screen with New report and Import beside a sample grid"><figcaption><p>No report yet: <strong>New report</strong> and <strong>Import</strong> (1) beside a sample grid</p></figcaption></figure>

**New report** opens the [report form](/guide/google-my-business-rank-tracker/create-a-report). **Import** brings in a report you already track elsewhere. See [Import](#import). Once the first report exists, the page shows the list below. A search or filter that matches nothing keeps the list and its **No reports.** row.

## Table and Cards

Use the **Table | Cards** switch at the right of the toolbar. SEO Utils remembers your choice, and both views share the same search, filters and list switch.

**Table.** One row per report, with these columns:

| Column                                        | What it shows                                                              |
| --------------------------------------------- | -------------------------------------------------------------------------- |
| **Report**                                    | Name, address, the grid and spacing and the tags                           |
| **Maps avg**, **In the pack**, **Finder avg** | The report's figure on each list, with its change since the run before     |
| **Last runs**                                 | A small chart of the last runs on the list you picked with the list switch |
| **Schedule**, **Last run**, **Next run**      | How often it runs, when it last ran and when it runs next                  |

The column picker, the icon at the right of the toolbar, shows or hides columns, including **Keywords**, **Snapshots**, **Enabled**, **Disabled** and **Created At**.

**Cards.** Each card shows the latest run as a strip of coloured dots on the list you picked, the name and address, the figures of every list the report tracks and one line with the grid, spacing, schedule and when it last ran. Click anywhere on a card to open the report. Hover a card for its checkbox and its **···** menu. **Sort** orders the cards, for example by **Last Run**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cf0834a46793ef6f18a3daa7d7db3a4aaa6a3c1c%2Fgmb-reports-cards.png?alt=media" alt="The reports as cards with a dot strip, the figures of each list and a facts line"><figcaption><p>Cards: the list switch (1), the Table and Cards switch (2) and the sort (3)</p></figcaption></figure>

## The figures of each list

The three figures come from each report's latest finished run, over all its keywords:

* **Maps avg** and **Finder avg** are average ranks. A spot where you are not in the top 20 counts as 21
* **In the pack** is the share of spots where you are in the Local Pack

Each figure has its change since the run before: green for better, red for worse, **same** for none. A dash means there is no figure for that list. Hover it to see why, for example **Not tracked** when the report does not track the list.

The **list switch** (**Google Maps | Local Pack | Local Finder**) picks the list for what only one list can show: the dots on the cards, the **Last runs** chart and the sorts and filters below. It does not hide the other figures. SEO Utils remembers the list you pick.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-27a069ab8e922eabef808bc954a9e9328677de89%2Fgmb-reports-local-pack.png?alt=media" alt="The table with the Local Pack picked, so the Last runs chart follows the Local Pack"><figcaption><p>With Local Pack picked (1), the <strong>Last runs</strong> column follows it (2)</p></figcaption></figure>

## Search and filter

Type in **Search name or address** to find a report. Then narrow the list with the filter chips:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b4382cb423106cc8392b4c9b647038868671b352%2Fgmb-reports-filters.png?alt=media" alt="The Result sets filter open with Google Maps only, Local Pack and Local Finder"><figcaption><p>The Result sets filter</p></figcaption></figure>

| Filter                     | What it keeps                                                                             |
| -------------------------- | ----------------------------------------------------------------------------------------- |
| **Schedule**               | Reports with the frequency you pick                                                       |
| **Tags**                   | Reports with the tags you pick                                                            |
| **Result sets**            | Reports by the lists they track: **Google Maps only**, **Local Pack** or **Local Finder** |
| **Dropped since last run** | Reports whose figure on the picked list got worse since the run before                    |
| **Last run**               | Reports by when they last ran                                                             |

Sorting by **Maps avg**, **In the pack** or **Finder avg** orders the whole list, not only the page you see. A report with no figure for the list goes last.

A report whose last run is 30 days old or more shows a note such as **Oct 2, 2026 · 39 days ago**. It marks a schedule that stopped. A report that never ran shows **Run first scan** instead.

## Row and bulk actions

Click **···** on a row for **Edit**, **Update Tags**, **Clone** and **Delete**. See [Manage reports](/guide/google-my-business-rank-tracker/manage-reports).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-dd10001f9b7236509614d6de11621df3305a9bd5%2Fgmb-reports-row-menu.png?alt=media" alt="The row menu with Edit, Update Tags, Clone and Delete"><figcaption><p>The row menu</p></figcaption></figure>

Tick the checkboxes, or the one in the header, and **Bulk Actions** acts on the selected reports:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cf0dbf355ceb0ebc8f44138d204e7e52e29037e0%2Fgmb-reports-bulk-actions.png?alt=media" alt="The bulk actions menu"><figcaption><p>Bulk actions</p></figcaption></figure>

| Action                  | What it does                                                                                           |
| ----------------------- | ------------------------------------------------------------------------------------------------------ |
| **Run Tracker**         | Runs every selected report. It spends credit for each one                                              |
| **Update Schedule**     | Updates the schedule of the selected reports                                                           |
| **Move to Workspace**   | Moves them to another workspace                                                                        |
| **Create Report Group** | Starts a [report group](/guide/google-my-business-rank-tracker/report-groups#create-a-group) with them |
| **Delete Reports**      | Deletes them with their history                                                                        |

## Import

**Import** next to **New report** turns an export from another tool into a report, with its history, ready for its first scan of your own.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-91d4927b990ac2bb15fac1580c58d5e492af808e%2Fgmb-reports-import-menu.png?alt=media" alt="The Import menu with Import from Local Brand Manager and Import from Search Atlas"><figcaption><p>The Import menu</p></figcaption></figure>

* **Import from Local Brand Manager:** choose one or more Local Brand Manager geogrid CSV exports of the same business. Each export is one keyword scanned once, so choose every export to bring in the whole history

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ea9957783236b8f7d7c2302f5e412b8506a6226c%2Fgmb-import-lbm-dialog.png?alt=media" alt="The Import from Local Brand Manager dialog with a Choose Files button"><figcaption><p>Import from Local Brand Manager</p></figcaption></figure>

* **Import from Search Atlas:** choose the CSV a Search Atlas Local Heatmaps list exports. SEO Utils creates the report with the same business, keywords and grid

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-748cec0814f0af494918f7d3763cedf8b1881e5c%2Fgmb-import-searchatlas-dialog.png?alt=media" alt="The Import from Search Atlas dialog with a Choose File button"><figcaption><p>Import from Search Atlas</p></figcaption></figure>

## Report groups

The **Groups** tab next to **Reports** lists your [report groups](/guide/google-my-business-rank-tracker/report-groups).


# Read a Report

A report opens as one workspace: the map shows where you rank for one keyword on one run, and a drawer under it holds the details. Everything on the page follows the same three choices, so you always know what you are looking at: the **keyword**, the **run** and the **list**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-bf14cf98c2271ff5059976c43959bc20502497b2%2Fgmb-report-workspace.png?alt=media" alt="A report with the map in the middle, the keyword and run chips above it and the details drawer below"><figcaption><p>The keyword (1), the run (2), the list (3), the map tools (4), the legend (5) and the drawer tabs (6)</p></figcaption></figure>

## The top bar

The report's name is the title. The arrow next to it opens the title menu with everything you can do to the report: **Edit**, **Pause schedule**, **Publish to client**, **Share and export…**, **Manage Keywords**, **Compare**, **Progress view** and **Delete Report**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8a48da874f040926144141272284c953d06fac91%2Fgmb-report-page-bar.png?alt=media" alt="The top bar with the title, the keywords chip, the schedule chip, More, the run status, Compare and Run now"><figcaption><p>The top bar: title menu (1), keywords (2), schedule (3), report details (4), run status (5), Compare (6) and Run now (7)</p></figcaption></figure>

| Item                     | What it does                                                                                                                              |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **6 keywords**           | Opens the [Keywords tab](/guide/google-my-business-rank-tracker/manage-reports#manage-keywords)                                           |
| **Weekly · next Nov 16** | The schedule and the next run. Click it to pause or [edit the schedule](/guide/google-my-business-rank-tracker/run-and-schedule#schedule) |
| **More**                 | **Report details**: the place, the grid, the keywords, the lists tracked, the schedule and the days it compares over                      |
| **Nov 9 · complete**     | The [run card](/guide/google-my-business-rank-tracker/run-and-schedule#follow-a-run)                                                      |
| **Compare**              | Turns on [Compare](/guide/google-my-business-rank-tracker/compare)                                                                        |
| **Run now**              | [Starts a run](/guide/google-my-business-rank-tracker/run-and-schedule#start-a-run)                                                       |

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ab859262d097d1fe9fcd8717e4534651ce2fe538%2Fgmb-report-title-menu.png?alt=media" alt="The title menu with Edit, Pause schedule, Publish to client, Share and export, Manage Keywords, Compare, Progress view and Delete Report"><figcaption><p>The title menu</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1cf5cdf4c35b7158a785af931cf3a4cfcc493418%2Fgmb-report-details.png?alt=media" alt="The Report details card with the place, grid, keywords, lists tracked, schedule and comparison days"><figcaption><p>More opens the report details</p></figcaption></figure>

On a narrow window the chips drop out of the bar one by one. **More** always stays.

## Pick the keyword, the run and the list

**Keyword chip.** It shows the keyword on screen, its value on the list on screen and its change. Click it to open the keyword list: search it, filter it by tag and sort it by **Worst first**, **A to Z** or **Biggest change**. Each row shows the keyword's value, its change, its tags and whether it is **New** or **Paused**. **Add** and **Manage** open the [Keywords tab](/guide/google-my-business-rank-tracker/manage-reports#manage-keywords). SEO Utils remembers the keyword per report.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b250ac2f34202ce38c65009ab64ca21f2a21d84b%2Fgmb-report-keyword-picker.png?alt=media" alt="The keyword list with values, changes, sparklines and tags"><figcaption><p>The keyword list, worst first</p></figcaption></figure>

**Run chip.** It shows the run on screen: a green dot for the latest run and an amber one for an older run, its date, **latest run** or how many runs ago it was, and the run it is compared with (**vs Nov 2**). Use **‹** and **›** to step through the runs, and **Latest** to come back. Click the chip for the list of runs, newest first, with the keyword's value on each, notes and the run it is compared with.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-69218bfec433d46b8c335bf32ba21b99cc8231e4%2Fgmb-report-run-menu.png?alt=media" alt="The run list with the keyword&#x27;s value on each run, a compared tag and Compared with"><figcaption><p>The run list. <strong>Compared with</strong> picks the run the changes are measured against</p></figcaption></figure>

**Compared with** is the run every change refers to. By default it is the run before the one on screen. If you set **Comparison Days** in the report's form, it is the run nearest to that many days before the one on screen. Pick another run here or on the [timeline](/guide/google-my-business-rank-tracker/history#the-runs-timeline) and every figure and badge follows.

**List switch.** At the top right of the map, **Google Maps | Local Pack | Local Finder** picks the list. It shows when the report tracks more than one list, and it drives the map, the drawer and the exports. See [Local Pack and Local Finder](/guide/google-my-business-rank-tracker/local-pack-and-local-finder).

## The map and its legend

Each pin is one spot. The number is your rank there, and the small badge above it is the change since the compared run: a green arrow for better, red for worse, **0** or **same** for none.

| Pin colour | Rank on Google Maps and the Local Finder |
| ---------- | ---------------------------------------- |
| Green      | 1 to 3                                   |
| Orange     | 4 to 10                                  |
| Red        | 11 to 20                                 |
| Grey       | 21+, not in the top 20                   |

The legend sits at the bottom left of the map. **Hide** shrinks it to a small **Legend** chip. The Local Pack has its own legend: see [Local Pack and Local Finder](/guide/google-my-business-rank-tracker/local-pack-and-local-finder#read-the-local-pack-map).

The tools at the right of the map, the colours and the size of the pins are in [Map tools and styles](/guide/google-my-business-rank-tracker/map-tools).

## The drawer

The drawer holds five tabs: **Overview**, **Competitors**, **Keywords**, [**Spot**](/guide/google-my-business-rank-tracker/spot) and [**History**](/guide/google-my-business-rank-tracker/history). It is as tall as its content. Drag the handle at its top to change how tall it can grow, and double-click the handle to collapse or expand it. A click on a tab while it is collapsed opens it. SEO Utils remembers the tab and the height for each report.

### Overview

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cb715e7a58c63b0437f2767b73f245d8834d2ae7%2Fgmb-overview-tab.png?alt=media" alt="The Overview tab with four figure cards, the spots by rank, who beats you here and the average rank over the last runs"><figcaption><p>Overview: the four figures (1), the spots by rank (2), who beats you here (3) and the average rank over the last runs (4)</p></figcaption></figure>

* **Avg rank:** your average rank over all spots. A spot where you are not in the top 20 counts as 21
* **In top 3:** how many spots you hold a top 3 rank in
* **Share of local voice:** the share of spots where you are in the top 3. This is the same as **SoLV** elsewhere
* **Not in top 20:** how many spots you are missing from

Each card shows its change and a small chart over the last runs. Under them, **spots by rank** counts the spots in each colour with the change since the compared run, **Who beats you here** lists the eight best businesses by average rank with your row pinned (**All competitors →** opens the full table) and a chart follows your average rank over the last runs.

**Showing** at the top right of the drawer is the business the grid is coloured for. Pick a competitor to see where they rank on the same map. **View on map** in the Competitors tab does the same.

### Competitors

The table lists every business that ranked for the keyword on this run, sorted by average rank.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9e8de5d20765707429fdce792197bae39f06a711%2Fgmb-competitors-tab.png?alt=media" alt="The Competitors table with rating, average rank, SoLV, distance, hours and categories"><figcaption><p>Competitors: opening hours (1), CSV export (2) and share of local voice (3)</p></figcaption></figure>

Its columns are the business with its website and address, **Rating**, **Avg Rank**, **SoLV**, **Distance** from you, **Hours**, the primary and search category, **Additional Categories**, **Photos**, price and whether the profile is claimed. Search the table, sort a column, and use **Export CSV** to download the list for this keyword.

#### Opening hours

The **Hours** column compares your opening hours with your competitors' so you can tell whether hours affect a ranking. Each row shows an **Open** or **Closed** badge with today's hours. Click the row's hours to see the whole week. A business open all day reads **Open 24 hours**, and a closing time at midnight reads **12:00 AM**.

{% hint style="info" %}
The badge needs the report's timezone, which you set with the schedule. Without a timezone SEO Utils cannot tell whether a business is open now, so it shows no badge.
{% endhint %}

### Keywords

The **Keywords** tab is one table for analysing and managing the keywords: each one's average rank, share in the pack and Finder average on the run on screen. See [Manage reports](/guide/google-my-business-rank-tracker/manage-reports#manage-keywords).

## When there is nothing to show

* **No ranking data for this keyword in this run:** the run did not check it, for example because you added it later or paused it
* **This run did not check the Local Pack** (or the Local Finder): see [Local Pack and Local Finder](/guide/google-my-business-rank-tracker/local-pack-and-local-finder#when-a-run-did-not-check-a-list)
* **Pick another run:** appears when the run on screen has no data and the report has other runs


# Spot

A spot is one pin of the grid: one place the search was made from. Click a pin and the **Spot** tab lists every business that ranked there, with its rank on each list side by side.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-08c82ead69974272c12a3dd6d718a3ab2d91b48d%2Fgmb-spot-map.png?alt=media" alt="A pin selected on the map and the Spot tab open under it"><figcaption><p>Click a pin (the map) and the Spot tab (1) opens</p></figcaption></figure>

## Open a spot

Click any pin on the map. The spot gets a thin dark ring, and the **Spot** tab opens with the businesses at that spot. **Clear spot** closes it.

The header says where the spot is: how far and in which direction from your business ("0.71 mi northeast of your business"), and its coordinates, which you can copy.

Spot reads the run you already have. It never starts a search, so it costs nothing.

## Read the table

There is one row for every business at the spot, whichever list it ranked in. Your own row is highlighted and marked **you**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9a76e68612197012b6ededafc900f04ff893e997%2Fgmb-spot-tab.png?alt=media" alt="The Spot table with the Maps, Pack and Finder ranks of every business at the spot"><figcaption><p>The Spot tab: the rank of each business on Google Maps, the Local Pack and the Local Finder</p></figcaption></figure>

* **Maps**, **Pack** and **Finder:** the business's rank on each list the report tracks, in the colour of the pin. A dash means it is not in that list at this spot
* **Rating**, **Distance** from the spot and **Distance from you**
* **SoLV**, the share of spots of the run where the business is in the top 3. With the Local Pack on screen the column reads **In the pack**
* **Hours:** an **Open** or **Closed** badge with today's hours. See [Opening hours](/guide/google-my-business-rank-tracker/read-a-report#opening-hours)
* The business's categories, photos, price and whether it is claimed sit further to the right. The column picker shows or hides columns

Click a column to sort it, and use **Search businesses** to find one by name or address. The business name and the ranks stay in place while you scroll sideways.

{% hint style="info" %}
Businesses are matched across the lists by the Google place they stand for, not by name. Three businesses with the same name at different addresses stay three rows.
{% endhint %}

## When you are not in a list

Under the spot's header, one line per list tells you what happened there. For example, **Google Maps: You're not in the top 20 at this spot**, or **Local Pack: You're not in the Local Pack at this spot**. When a run did not check a list, its line says so and offers the latest run that did.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5e04b649fde25b63108cfdf85ee1d033894c1b21%2Fgmb-spot-not-in-top-20.png?alt=media" alt="The Spot tab with a line saying you are not in the top 20 at this spot"><figcaption><p>A spot where the business is not in the top 20 on Google Maps, on a run that did not check the Local Pack</p></figcaption></figure>

On the Local Pack, a spot can also show that Google showed **no pack here**, which is different from a pack that showed without you. See [Local Pack and Local Finder](/guide/google-my-business-rank-tracker/local-pack-and-local-finder#read-the-local-pack-map).


# Local Pack and Local Finder

Google Maps is not the only place a local business shows up. When someone searches Google, a box of up to three businesses often appears on the results page, and a link under it opens a longer list. The GMB Rank Tracker can track both, next to Google Maps, from the same grid of spots.

| List             | What it is                                                   | What the tracker records                                                                |
| ---------------- | ------------------------------------------------------------ | --------------------------------------------------------------------------------------- |
| **Google Maps**  | The list in the Google Maps app, top 20                      | Your rank at each spot                                                                  |
| **Local Pack**   | The up to three businesses on the Google Search results page | Whether you are in the pack at each spot, and whether Google showed a pack there at all |
| **Local Finder** | The longer "More places" list behind the pack, top 20        | Your rank at each spot, which shows how far below the pack you are                      |

These are three different lists. A business can be first on Google Maps and missing from the pack at the same spot, so SEO Utils keeps each list separate and never mixes their numbers.

## Turn them on

1. Open the report's **Edit** form, or create a new report
2. In step **Keywords and result sets**, under **Lists to track**, turn on **Local Pack**, **Local Finder** or both. **Google Maps** is always on
3. Check the price: each list shows what it adds per check, and the cost bar under the map shows the total for a run
4. Click **Save**

Each list adds checks to every run, so it adds to what a run costs. The change applies to the next run. Runs you already have stay as they were, and they show **This run did not check the Local Pack** for the list they never checked.

## Switch the list

At the top right of the map, **Google Maps | Local Pack | Local Finder** picks the list. SEO Utils remembers your choice for each report. The choice drives the whole workspace: the map, the Overview, Competitors, Keywords and Spot tabs, [History](/guide/google-my-business-rank-tracker/history), [Compare](/guide/google-my-business-rank-tracker/compare) and the exports.

On the [reports list](/guide/google-my-business-rank-tracker/your-reports) and on [group](/guide/google-my-business-rank-tracker/report-groups) pages the same switch picks the list for the pictures.

## How the lists read

The Local Pack and the other two lists read differently:

| List                              | Headline figure                                               | A spot where you are missing                 |
| --------------------------------- | ------------------------------------------------------------- | -------------------------------------------- |
| **Google Maps**, **Local Finder** | **Avg rank**: your average rank over all spots                | Counts as 21 and shows as **21+**            |
| **Local Pack**                    | **In the pack**: the share of spots where you are in the pack | Shows as **not in the pack**, or **no pack** |

For example, the Local Pack figure on a card reads **In the pack 41%**: you are in the pack at 41% of the spots. Its change is in points, for example **↓4 pts**.

## Read the Local Pack map

On the Local Pack, each pin shows your place in the pack, 1 to 3. The legend explains the rest:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1d848f94f0470339c607895b3864c6a2512595e7%2Fgmb-local-pack-map.png?alt=media" alt="The Local Pack on the map with its figures and legend"><figcaption><p>The Local Pack: the list switch (1), the four figures (2) and the legend (3)</p></figcaption></figure>

| Mark                                              | What it means                                                     |
| ------------------------------------------------- | ----------------------------------------------------------------- |
| **Your place in the pack (1 to 3)**               | You are in the pack, at that position                             |
| **Last place in the pack (Google showed 2 or 3)** | You are in the pack, in its last place. A pack holds two or three |
| **A pack showed without you**                     | Google showed a pack at that spot, and you are not in it          |
| **Google showed no pack here**                    | There was no pack at that spot. This is not a miss on your side   |
| **No answer from Google for this spot**           | The check did not return an answer                                |

Ads in the pack are not counted.

The four figures under the list switch sum it up:

* **In 3-Pack:** the spots where you are in the pack, out of the spots checked, for example **5/25**
* **Pack shown:** the spots where Google showed a pack at all, for example **17/25**
* **Avg pack position:** your average position in the pack, where you are in it
* **Maps top 3, not in pack:** the spots where you are in the top 3 on Google Maps but not in the pack

The **Overview** tab repeats them as cards, splits the spots into **In the pack**, **Pack without you**, **No pack** and **No answer**, and charts **Pack coverage** over the last runs.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3f419288f3ee5f27be404bd717a3835b450688fb%2Fgmb-local-pack-overview.png?alt=media" alt="The Overview tab on the Local Pack with In 3-Pack, Pack shown, spots in the pack and pack coverage"><figcaption><p>Overview on the Local Pack: In 3-Pack (1), Pack shown (2) and the spots in the pack (3)</p></figcaption></figure>

## Read the Local Finder map

The Local Finder reads like Google Maps: a number is your rank and **21+** means you are not in the top 20. Its legend adds **Local Finder listed no businesses here** for a spot with no list. Everything else, including the Overview and Competitors tabs, works as it does for Google Maps.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-72f3743b0c6b2157bef672bbe576dba5fbc7bdc5%2Fgmb-local-finder-map.png?alt=media" alt="The Local Finder on the map with its legend"><figcaption><p>The Local Finder: your rank at each spot, and its legend</p></figcaption></figure>

## When a run did not check a list

If you pick a list on a run that did not check it, for example a run from before you turned the list on, every tab says so in the same words:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-44ea3c4edf1491b6ab9f755033fd841527e3ab1d%2Fgmb-list-not-checked.png?alt=media" alt="The message This run did not check the Local Finder with a button to show the latest run that checked it"><figcaption><p><strong>This run did not check the Local Finder.</strong> The button jumps to the latest run that did</p></figcaption></figure>

Click **Show Nov 9, the latest run that checked the Local Finder** to go straight to that run. If no run has checked the list yet, the message says so, and you can switch back to Google Maps.


# History

The **History** tab shows how a keyword's ranking moved over time. It starts with the runs timeline, and three views sit under it: **Every run**, **Date ranges** and **Trend**. All of them follow the keyword and the list on screen.

## The runs timeline

The timeline is on top of the History tab. Each circle is a run, and the number in it is the average rank of the keyword on that run. The border follows the colour of the pins.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6a35b9cca6656374d0a92863bce38c258ca9462f%2Fgmb-history-every-run.png?alt=media" alt="The runs timeline with the timeframe, the compared run, the Notes menu and the Every run maps under it"><figcaption><p>The timeline: the timeframe (1), the compared run (2) and the notes (3), then one small map for every run</p></figcaption></figure>

* **Runs** and the timeframe next to it: **Last 3 months**, **Last 6 months**, **Last 12 months** or **All time**. Change it to look further back
* **Compared with:** the run the changes are measured against. The dashed ring marks it on the strip. Pick another run here and every figure on the page follows
* **Notes:** your [notes](/guide/google-my-business-rank-tracker/manage-reports#notes) and the Google updates, shown as flags on the strip
* **N earlier** and **N later**, at the ends of the strip (for example **6 earlier**): page through the runs
* **The selected run** shows its date as a menu: **Export this run**, **Export Grid Points**, **Export Grid Points with Businesses**, **Export Grid Points with Demographics** and **Delete this run**. A right-click on any run opens the same menu for it

## Every run

One small map for every run, newest first. Click a map to show that run on the big map. **Showing** at the top picks whose ranks the small maps draw: yours or a competitor's.

## Date ranges

**Date ranges** shows the same keyword over several periods, side by side. Each map covers a period, such as one month, and shows the latest scan in it. It is the view to show a client how a ranking moved over a quarter.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d41307db1a9df260728d2299b50e92c6fd944c78%2Fgmb-date-ranges.png?alt=media" alt="Three grid maps for three months with the summary figures above them"><figcaption><p>Date ranges: three maps, one for each month. <strong>Configure</strong> (1) sets the periods and <strong>Export progress report</strong> (2) exports them</p></figcaption></figure>

The summary above the maps compares the newest map with the oldest. The **Columns** buttons lay the maps out in two, three or four columns, and the keyword title is a picker: choose another keyword without leaving the view.

### Configure the ranges

Click **Configure** to choose what the maps cover. A generator builds the ranges, and you can then adjust each one.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-977c3aeb6f7c8ec06e74f1921f2452108dbd0da6%2Fgmb-date-ranges-configure.png?alt=media" alt="The Configure progress view panel with the time span, the number of maps, the switches and the ranges"><figcaption><p>Configure: the time span (1), rolling or fixed (2), the ranges and pinned scans (3) and Preview (4)</p></figcaption></figure>

| Setting                                          | What it does                                                                                                                               |
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Time span** and **Grid maps**                  | How many months the view looks back, and how many maps it divides them into. **Generate ranges** splits the span evenly                    |
| **Rolling · always ends with the current month** | On, the view moves forward with time and stays current. Off, an **End date** fixes the period, so a report shows the same dates every time |
| Each range                                       | Choose **Custom…** to set that map's own dates, or **Back to auto** to go back to the generated ones                                       |
| **Auto — latest scan in the range**              | Takes the newest scan of the period. Pick a scan from the list instead to **pin** it: that map always shows that scan                      |
| **Show scan dates under each map**               | On by default. Off hides each scan date and the pinned-scan labels, for a client report where the exact days do not matter                 |
| **Show summary numbers above the maps**          | Off hides the figures above the maps, so a client reads the maps alone                                                                     |

**Preview** applies the settings without saving them, and the view says **Previewing · not saved**. **Save** stores them on the report, so the view opens this way next time and the export matches. **Reset** goes back to the saved settings.

### How each map picks its scan

| Situation                               | What the map shows                                           |
| --------------------------------------- | ------------------------------------------------------------ |
| Several scans in the period             | The most recent finished scan that has data for this keyword |
| A scan is pinned to the range           | That scan, whatever else the period holds                    |
| No scan in the period                   | An empty map with **No scan** and the period                 |
| A scan ran before you added the keyword | A note that the scan has no data for this keyword            |

Each map's caption gives its period, its scan date and the grid it used.

{% hint style="warning" %}
Change arrows appear only when two maps cover the **same grid points**. If you changed the size, shape or spacing of the grid between two scans, the maps are no longer comparable and the arrows are hidden. The caption says so.
{% endhint %}

A scan you pinned can fall outside its range, because the ranges move with the date and a pin stays on its scan. The map keeps it and tells you the pinned run is outside the range, with a way to pick another one.

**Export progress report** (also **Progress report** in [Share and export](/guide/google-my-business-rank-tracker/exports-and-client-reports)) exports the maps for up to 100 keywords in one document.

## Trend

**Trend** charts the keyword over the runs, for you and for the businesses you add.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6b8d3707bc561529e09f68a18bd97d222edac83a%2Fgmb-history-trend.png?alt=media" alt="The Trend chart with the average rank over the runs and Google update markers"><figcaption><p>Trend: your average rank over the runs, with a marker for each Google update</p></figcaption></figure>

The metric switch above the chart depends on the list on screen:

| List                              | Metrics                                                                                                                                                  |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Google Maps**, **Local Finder** | **Avg rank**, **Share of voice (top 3)** and **Reviews**                                                                                                 |
| **Local Pack**                    | **Avg pack position** (your average place in the pack, 1 to 3), **Pack coverage** (the share of checked spots where you are in the pack) and **Reviews** |

* The date range and **Business** (with a plus sign) choose the period and the businesses. Each one adds a line, and SEO Utils remembers your choice per report
* Markers above the chart show events. A grey **G** is a Google update, a violet flag is a note, and a pill with a number groups several that fall close together. Hover or click a marker to list them


# Compare

Compare puts two maps side by side, or one map with a before and after slider, so you can see what changed. Compare two runs of the same business, two businesses on the same run, or two lists on the same run.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-bf835b9478ecd052041a0eb5b770a442a56d20c9%2Fgmb-compare-side-by-side.png?alt=media" alt="Two maps side by side, Nov 2 and Nov 9, with the comparison summary under them"><figcaption><p>Compare: what to compare (1), the layout (2), hiding business names (3) and exporting a PDF (4)</p></figcaption></figure>

## Open Compare

Click **Compare** in the report's top bar, or choose **Compare** in the title menu or **Compare side by side** in the run list. **Close compare**, or the **Esc** key, returns to the single map. Compare never changes the keyword, run or list you had selected.

## What to compare

The first row of the toolbar picks the kind of comparison. Each map has its own **Run**, **List** and **Business** pickers, labelled **A** and **B**, and a card with the business's name, address and rating.

| Mode           | Map A starts as          | Map B starts as                       | Use it to see                             |
| -------------- | ------------------------ | ------------------------------------- | ----------------------------------------- |
| **Past run**   | The run you compare with | The run on screen                     | How your ranking changed between two runs |
| **Competitor** | You                      | The top competitor                    | Where a competitor beats you              |
| **Other list** | Google Maps              | The Local Pack, else the Local Finder | How the same business ranks on two lists  |

Change any picker to compare something else, for example two runs of a competitor. The keyword picker in the toolbar changes the keyword for Compare only.

## Side by side or slider

* **Side by side:** two equal maps. Hover a spot to ring it on both maps and see both values in the pin's tooltip
* **Slider:** one map. Pins left of the divider show A and pins right of it show B. Drag the divider, or use the arrow keys

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-77e2a38dcdc552bc6d648dc3b59a9e1d5a84f25c%2Fgmb-compare-slider.png?alt=media" alt="One map with a divider showing run A on the left and run B on the right"><figcaption><p>The slider: Nov 2 on the left of the divider and Nov 9 on the right</p></figcaption></figure>

Turn on **Hide business details** to blur the business names and cards, for a screenshot you want to share. **Export PDF** (desktop app) saves both maps side by side with the summary, from either layout.

## Read the summary

The drawer under the maps adds up the difference. The cards show each side's figure and who leads:

* **Avg rank**, for example **4.0 → 2.6** with **better** or **worse**. On the Local Pack the card reads **Avg pack position**, with how many spots you are in the pack at
* **Spots in the top 10** and **Not in the top 20**, with the same counts on both sides
* **Spots that changed** (a past run): how many spots got better and how many got worse. In the other modes, **Spot by spot** counts the spots where A is ahead and where B is ahead

Two bars, **A** and **B**, split the spots by colour.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5d8aa72ba5cd67e1a04a88d6067ce078eca523f6%2Fgmb-compare-other-list.png?alt=media" alt="Google Maps on the left and the Local Pack on the right, with the summary"><figcaption><p>Comparing two lists: Google Maps against the Local Pack</p></figcaption></figure>

The cards and bars count only the spots both sides answered. A spot with no answer on either side is left out, and on the Local Pack so is a spot with no pack. The summary says how many spots it counted.


# Map Tools and Styles

The four tools at the top right of the map help you measure, add layers, find your way back and work on a bigger map. Style settings change how the pins look.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ecc052449bbff04462bec48f24b3f43f999dc8d3%2Fgmb-map-tools.png?alt=media" alt="The map tools: measure, layers, center and full screen"><figcaption><p>The map tools: Measure distance (1), Layers (2), Center the map (3) and Full screen (4)</p></figcaption></figure>

## Measure a distance

Click the **Measure distance** tool, then click points on the map. Each segment shows its length, so you can measure the distance between two spots or along a route of several. A hint on the map says **Continue clicking to add more points**. Press **Esc** to remove the last line or to leave measuring mode. **Clear measurements** removes the lines you drew.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-964d7a3b58aa57ba06ef63c8458f99c12d7e28aa%2Fgmb-map-measure.png?alt=media" alt="A measuring line across the grid with its distance"><figcaption><p>Measuring across the grid</p></figcaption></figure>

## Center and full screen

**Center the map** brings the grid back into view after you pan or zoom. **Full screen** gives the map the whole window when you need more room to work on it, and reads **Exit full screen** while it does.

The grid is also editable in the report's form: move or remove spots, and turn off the ones where no one lives. See [Create a report](/guide/google-my-business-rank-tracker/create-a-report#the-four-steps).

## Layers

**Layers** adds data on top of the map. Each layer has a switch, its name, one line saying how it is set up and a **gear** for its settings.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3eeb0e568ac9a016a2770163e7192849916a7836%2Fgmb-map-layers.png?alt=media" alt="The Layers menu with the Demographics and Money Map switches"><figcaption><p>The Layers menu: Demographics and Money Map</p></figcaption></figure>

### Demographics layer

The Demographics layer colours the map by who lives where, so you see which areas hold the most potential customers. Open the **gear** to pick what it colours by:

| Colour by         | What it shows                 | Good for                                       |
| ----------------- | ----------------------------- | ---------------------------------------------- |
| **Density**       | People per square mile        | Finding busy areas                             |
| **Median Income** | Household income              | Areas with more buying power                   |
| **Homeowners**    | Share of owner-occupied homes | Home services such as HVAC, roofing or solar   |
| **Median Age**    | The median age of residents   | Reaching an age group, for example 55 and over |

The colours run from yellow (low) through orange to red (high). Click a coloured area for its figures, and read the scale in the legend, which shows in the corner of the map while the layer is on.

Where the data comes from depends on the country. It needs no setup in the US, Canada, the UK and Australia, and uses a key you add elsewhere:

| Location                                                | Source                                          | Detail                                                                     |
| ------------------------------------------------------- | ----------------------------------------------- | -------------------------------------------------------------------------- |
| **US**                                                  | US Census Bureau                                | Tracts: density, income, homeowners and age. A built-in key is included    |
| **UK** (England and Wales)                              | ONS Census 2021 and small area income estimates | The same four measures, with income in £                                   |
| **Australia**                                           | ABS Census 2021                                 | The same four measures, with income in A$                                  |
| **Canada**                                              | Statistics Canada Census 2021                   | The same four measures, with income in C$                                  |
| **Everywhere else** (and Scotland and Northern Ireland) | Geoapify                                        | Population and density at city level only. It needs a **Geoapify API Key** |

For Geoapify, create a free account at [geoapify.com](https://www.geoapify.com/), create an API key and paste it in **Settings → Services → Google Business Rank Tracker → Geoapify API Key**.

<details>

<summary>Use your own US Census key</summary>

The built-in key works for everyone. Use your own only to avoid sharing its rate limits during very heavy use.

1. Request a free key at [api.census.gov/data/key\_signup.html](https://api.census.gov/data/key_signup.html)
2. Click the activation link in the confirmation email. The key does not work until you do
3. Paste it in **Settings → Services → Google Business Rank Tracker → Census API Key**. Leave the field empty to keep the built-in key

</details>

### Money Map

The Money Map shows where your website visitors and phone calls come from, on the ranking grid, so you see which areas bring engagement. It needs a [RingTonic](https://ringtonic.app) account, a call tracking and visitor analytics platform that provides the locations.

1. Create an API key in RingTonic. See the [RingTonic API guide](https://help.ringtonic.app/guides/api)
2. Paste it in **Settings → Services → Google Business Rank Tracker → RingTonic API Key**
3. Edit the report and, in step **Report and integrations**, enter its **RingTonic Campaign UUIDs**, one per line, up to 10. Add every campaign that brings leads for this business, such as your Website Tracker campaign and the campaign of the number on your Google Business Profile
4. Open **Layers** and switch **Money Map** on

The map shows blue heatmaps and markers for visitors with a known location, and orange ones for phone calls. The legend gives the counts and the period, which is the 30 days ending on the run on screen, so it updates when you pick another run. Zoom in to see individual markers with their counts.

When a report has more than one campaign, the legend lists each one with its counts. Untick a campaign to hide its visitors and calls, and tick it again to bring them back. Click a marker to see which campaigns its calls and visitors came from.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d84e0135c3b62541c42e7028ba81c0f35f50ed5d%2Fgmb-rank-tracker-money-map-campaigns.png?alt=media" alt="The Money Map legend listing three RingTonic campaigns with tick boxes" width="375"><figcaption><p>The Money Map legend with a tick box for each campaign</p></figcaption></figure>

{% hint style="success" %}
To see only the calls from your Google Business Profile number against the grid, untick every campaign except that number's campaign.
{% endhint %}

If RingTonic cannot load a campaign, for example because of a mistyped UUID, the other campaigns still show and the legend marks that one with a warning icon. Hover it to see why. The Money Map turns off when the map shows another business.

## Marker styles

Three settings in **Settings → Services → Google Business Rank Tracker** change how the pins look.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a330843773ef94fba3ae05abc534068953b439da%2Fgmb-settings-marker-styles.png?alt=media" alt="The Show More Color Variants and Enable Glow Effect switches and the Marker Size menu"><figcaption><p>Marker styles: more colours (1), glow (2) and size (3)</p></figcaption></figure>

| Setting                      | What it does                                                                                  |
| ---------------------------- | --------------------------------------------------------------------------------------------- |
| **Show More Color Variants** | Shows more colour shades than the three main colours                                          |
| **Enable Glow Effect**       | Adds a soft glowing border around pins so they stand out. It applies to every grid right away |
| **Marker Size**              | **Default** or **Small**. Use **Small** on a small screen                                     |

The glow is removed from PDF exports so documents stay clean. HTML exports keep it.


# Report Groups

A report group combines the reports of one business's locations into a single dashboard. Use it for a multi-location business: one view for the visibility, the rankings and the trends of every location, and one export for the whole business.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-11166e3f702fceb0ad485bcc29a5a4196104f760%2Fgmb-group-card.png?alt=media" alt="A report group card with three headline figures, a health bar and a stale warning"><figcaption><p>A group card: the headline of each list (1), the health bar of the picked list (2) and locations that have not run in 30 days (3)</p></figcaption></figure>

## Create a group

1. Open **Local SEO → GMB Report Groups**, or the **Groups** tab of the [reports list](/guide/google-my-business-rank-tracker/your-reports), and click **New group**
2. Enter a **Name** under **Group Details**, then tick the reports to include under **Select Reports**. Use the search box to find them by name or address
3. Optional: fill in the **Branding** of the group's exports: logo, heading, subheading, description and page colour. See [Exports and client reports](/guide/google-my-business-rank-tracker/exports-and-client-reports#branding)
4. Click **Create Group**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fd1008b335b23af6862c9c2c5d49c264392acc32%2Fgmb-group-form.png?alt=media" alt="The group form with the name, the report picker and the branding"><figcaption><p>The group form: the name (1), the reports (2) and the branding (3)</p></figcaption></figure>

### Before you have a group

The **Groups** tab says what is missing:

* **Groups need reports:** the workspace has no report yet. A group is made of reports, so **New group** is off, with the tooltip "Create a report first: a group is made of reports." Click **New report** in the message and create a report for each location first
* **No groups yet:** you have reports but no group. The message says what a group gives you, one dashboard with the headline figures per list, the biggest drops and gains and a keyword × location table, and has a **New group** button

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0522b1cfc03e45d20e7854834da721ac85e01a0a%2Fgmb-groups-need-reports.png?alt=media" alt="The Groups tab reading Groups need reports, with a New report button and New group switched off"><figcaption><p>Groups need reports (1). <strong>New report</strong> (2) starts the first one. <strong>New group</strong> at the top right stays off until the workspace has a report</p></figcaption></figure>

{% hint style="info" %}
You can also tick several reports in the [reports list](/guide/google-my-business-rank-tracker/your-reports#row-and-bulk-actions) and use **Bulk Actions → Create Report Group**.
{% endhint %}

## The groups list

The **Groups** tab lists your groups as a table or as cards, with a search, a **Tags** filter and the same list switch as the reports list. Each card shows:

* **Three headline figures**, one per list: **Top 3 on Maps**, **In the pack** and **Finder top 3**. Each is the share of the group's spots in the top 3 (in the pack for the Local Pack), with its change and **3 of 4 track it**: how many of the group's reports track that list
* **A health bar** of the list you picked with the switch. It colours every spot of every location's latest run by your best rank there: green for 1 to 3, yellow for 4 to 10, red for 11 to 20 and grey for not in the list
* **N not run in 30+ days**, when a recurring report in the group has stopped running
* A dot for each location and when the group last ran. **Open** opens the dashboard

## The dashboard

Open a group to see all its locations. The line at the top reads, for example, "4 locations · latest runs Nov 10, 2026". The dropdown at the top right sets what the changes compare against: **vs 7 days ago**, or 14, 30, 60 or 90 days ago.

### Headlines and warnings

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-83ef7af5bfe34fcc733758a81873013b2da5ed47%2Fgmb-group-tiles.png?alt=media" alt="The three headline tiles, a warning about a location that has not run and the Needs attention list"><figcaption><p>The tile that picks the list (1), the warning for a location that has not run (2) and the run each location is compared with (3)</p></figcaption></figure>

* **The three tiles**, one per list, are also the control: click one to pick the list for the rest of the page. The picked tile says **Showing below**. Under each figure, a bar splits the spots the figure counts by rank, with a legend. **N of M locations** tells how many locations track the list
* **The warning** appears for a location with no run for 30 days: "Harbor & Pine Coffee Capitol Hill hasn't run in 39 days, so its figures are from Oct 2, 2026." Click **Run now** (**Run all 2 now** when several locations are stale) to run them. It spends DataForSEO credit, and the dashboard updates when they have a run
* **Needs attention** lists up to three biggest drops and three biggest gains, per location and list, with the change from one figure to the other. Click a row to open that report on that list. **Compared with** names, for each location, the run the changes are measured against. Each location is compared with its newest run that is at least as old as the dropdown says, so two locations can be compared with two different days

### The locations map

The map shows a pin for each location, coloured and labelled by its figure on the list you picked. Click a pin to open that report. It uses the same Google Maps key as the report page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a1c9a7a9fd3b311bab2ff02b762fc04569f7592b%2Fgmb-group-dashboard-1.png?alt=media" alt="The locations map with the four locations, the metric cards, the ranking distribution and the start of the rankings chart"><figcaption><p>The locations map, the metric cards and the ranking distribution</p></figcaption></figure>

### Visibility and rankings

The cards read for the list you picked:

| Card                       | What it shows                                                                                                        |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Visibility Score**       | The share of the group's spots where you are in the top 3 (in the pack on the Local Pack), with its change in points |
| **Keywords Ranking**       | How many keyword and location combinations are ranking, out of all the group tracks                                  |
| **Improved**, **Declined** | How many keywords gained or lost position since the compared run                                                     |
| **Ranking distribution**   | How many keywords fall in each band: 1 to 3, 4 to 6, 7 to 10, 11 to 15 and 16 to 20                                  |

The **Summary** repeats them in words, for example "Your visibility score was 37% (+11 pt)".

## Rankings over the period

Two charts show the same period, from three months back to today, on the same date axis, so a date sits at the same place on both. A location keeps the same colour on both charts.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-86d919434468d9206326e95f03837c3f0911f59c%2Fgmb-group-rankings-chart.png?alt=media" alt="The rankings over the period chart with a line for each location and a 21+ lane"><figcaption><p>Rankings over the period: a line for each location, the compared run ringed (1) and the 21+ lane at the bottom</p></figcaption></figure>

**Rankings over the period** has one line per location through its runs. Dots are real runs, and the line between two runs is straight. Lower is better on a rank list, and a ring marks each location's **Compared run**. A location out of the top 20 runs along the **21+** lane under rank 20. On the Local Pack the axis is the share of spots, higher is better, and there is no lane. A location with no run in the period is dimmed in the legend as **(no run in this period)**, or **(no run yet)**. Hover a date for each location's figure.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0fd25ed83a7bcaf7deb2ee792a271eba9510e9bb%2Fgmb-group-keywords-chart.png?alt=media" alt="The keywords by rank over the period chart with coloured bands and run days under it"><figcaption><p>Keywords by rank over the period: the hatched <strong>No run yet</strong> band (1) and the <strong>Run days</strong> dots (2)</p></figcaption></figure>

**Keywords by rank over the period** counts every keyword at every location that tracks the list, as of each day. Each location stands at its latest run on or before that day, so a location that did not run that day still counts. The bands are the ranks 1 to 3, 4 to 6, 7 to 10, 11 to 15 and 16 to 20, then **Not in top 20** and the hatched **No run yet**: the location had no run on the list yet, or the keyword was added after its last run. Every day adds up to the same total, and the dots under the chart are each location's **Run days**. Hover a day for the count in each band, the first keywords of each and the date of the run a figure comes from. The Local Pack keeps five share bands and has no **Not in top 20**.

## Keyword × location

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-46267bc416f69a29a858f780fc918b054b2cb9cb%2Fgmb-group-matrix.png?alt=media" alt="The keyword by location table with a rank cell and its change for each location"><figcaption><p>Keyword × location: one row per keyword and one cell per location</p></figcaption></figure>

One row per keyword and one cell per location, with that location's rank for the list you picked in its colour and its change since the compared run. A dash with **Not tracked** means the location does not track the list. When a cell has no change, its tooltip says why: the compared run did not check the list, or no run is old enough. Click a cell to open that report on that keyword and list.

## Export

Open the title menu next to the group's name and choose **Export PDF** to open the preview, where you can download a PDF or HTML file. The export follows the list you picked: the cover names it, each location's summary shows its figure on it and the keyword table is the list's. On the Local Pack, the table shows the pack as a share and no SoLV. Set the logo, heading and colours in the group's [Branding](/guide/google-my-business-rank-tracker/exports-and-client-reports#branding).

A group is not published to a client. Publish the reports of each location instead. See [Exports and client reports](/guide/google-my-business-rank-tracker/exports-and-client-reports#publish-to-a-client).

## Manage groups

| Action     | How                                                                                        |
| ---------- | ------------------------------------------------------------------------------------------ |
| **Edit**   | **Edit report group** in the title menu, or the row menu on the Groups tab                 |
| **Delete** | **Delete** in the title menu or the row menu. It does not delete the reports or their data |

## Ask your AI app

With your AI app connected, ask for the dashboard in words: "Show me the visibility score for Harbor & Pine Coffee across all locations" or "Which location ranks best for 'espresso bar'?". See [Ask your AI app](/guide/google-my-business-rank-tracker/ask-your-ai-app).


# Exports and Client Reports

Everything you take out of a report starts in one panel. Choose **Share and export…** in the report's title menu.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-85ec92b79c25b0788785fecc324d4e8239f1951a%2Fgmb-share-export-panel.png?alt=media" alt="The Share and export panel with Client link, Reports, Data and Branding"><figcaption><p>Share and export: the client link, the reports, the data files and the branding</p></figcaption></figure>

The exports follow the run and the list on screen. The panel names them, for example **Nov 9, Google Maps**. Pick the Local Pack or the Local Finder first, and the PDF and the files describe that list.

## PDF and HTML reports

**Preview**, next to **This run as a PDF**, opens a preview of the report for the run on screen: a cover, a keyword table and, for each keyword, its figures, a map and the top businesses. In the preview, **Download PDF** saves it and **Download HTML** saves a web page. **Branding** opens the cover settings.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1d0f231646109e66b2b19f24d936331df1d6b068%2Fgmb-export-p0.png?alt=media" alt="The cover of the report preview with a heading, a subheading and a description"><figcaption><p>The cover of the report preview</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a221bf4493b08ba0d78b85286103e4a0c0bb96e3%2Fgmb-export-p2.png?alt=media" alt="A keyword page of the report preview with its figures and the grid map"><figcaption><p>A keyword page: the figures, the grid map and the top businesses</p></figcaption></figure>

In the browser, the PDF is the browser's print. HTML export is a desktop feature. The glow around pins is removed from PDFs and kept in HTML.

**Progress report** exports the [Date ranges](/guide/google-my-business-rank-tracker/history#date-ranges) maps for up to 100 keywords: click **Choose keywords** and pick them.

### Interactive maps in HTML exports

An exported HTML file can keep its maps clickable, so whoever opens it can pan and zoom. The file contains the key, and you will share the file, so it needs a **separate, restricted** key. Never put your main Google Places API key in it.

{% stepper %}
{% step %}

#### Create a restricted key

In the [Google Cloud Console](https://console.cloud.google.com/), make sure the **Maps JavaScript API** is enabled for your project. Then open **APIs & Services → Credentials**, click **Create Credentials → API Key** and set it up on the creation screen:

* Give it a name, such as "Interactive Maps in HTML Exports"
* Under **Application restrictions**, choose **Websites**. Under **Website restrictions**, add the addresses where the file will be hosted, for example `https://yourdomain.com/*` and `https://clientdomain.com/*`
* Under **API restrictions**, choose **Restrict key** and select **Maps JavaScript API**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FqF1AwgjwIn0C7LHvJbeg%2FXnapper-2026-02-13-11.46.41.png?alt=media&amp;token=3ae507e7-ae09-4311-9107-f5a10706ae9f" alt=""><figcaption><p>Create and restrict an API key in one step</p></figcaption></figure>
{% endstep %}

{% step %}

#### Save it in SEO Utils

Open **Settings → Services → Google Business Rank Tracker**, paste the key in **Interactive Maps API Key** and save. SEO Utils then fills it in whenever you export. You can also paste it in the export dialog each time.
{% endstep %}

{% step %}

#### Export

In the Share and export panel, click **Export** next to **Interactive HTML**, or click **Download HTML** in the preview. In the **Export HTML Report** dialog, turn on **Enable Interactive Maps**, check the **Restricted Google Maps API Key** and click **Export HTML**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FCoxvTwppEmcpUCfQxq7V%2FXnapper-2026-02-13-11.49.59.png?alt=media&amp;token=3d50fcb9-ac10-4305-99ec-dc38af6899f7" alt="" width="563"><figcaption><p>Turn on <strong>Enable Interactive Maps</strong> in the export dialog</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The restriction by website does not apply when you open the file from your computer, so the maps do not load. Host the file on a website that matches the addresses you allowed.
{% endhint %}

{% hint style="danger" %}
An unrestricted key in a public file can be copied and used to run up charges on your Google Cloud account. Always restrict it by website and by API.
{% endhint %}

## Data files

| File                              | What it holds                                                                        |
| --------------------------------- | ------------------------------------------------------------------------------------ |
| **Grid points**                   | A CSV with the latitude and longitude of every spot                                  |
| **Grid points with businesses**   | An Excel file with every business at every spot, for the keyword on screen           |
| **Grid points with demographics** | A CSV with census data for each spot. It uses paid census data                       |
| **Competitors**                   | A CSV of the businesses for the keyword on screen. It is also in the Competitors tab |

The run's menu on the [timeline](/guide/google-my-business-rank-tracker/history#the-runs-timeline) offers the same exports for any run.

## Branding

**Branding** sets how your exports look: the PDF, the HTML, the progress report and automated exports. Click **Edit** in the panel, or **Branding** in the preview.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-de9323f12dcad7795876bf71feae2dd4bb1467c4%2Fgmb-branding-editor.png?alt=media" alt="The Branding editor with the logo URL, heading, subheading, description, background colour and placeholders"><figcaption><p>The Branding editor</p></figcaption></figure>

| Field                                        | What it sets                                                                                        |
| -------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Logo URL**                                 | The logo at the top of the cover                                                                    |
| **Heading**, **Subheading**, **Description** | The text of the cover                                                                               |
| **Background color**                         | The page colour of the exports. On a dark colour the text turns white. **Reset to white** goes back |

Use these placeholders in the text: **\[reportName]**, **\[snapshotDate]**, **\[snapshotDateTime]** and **\[previousSnapshotDate]** (the date of the run it compares with). A [report group](/guide/google-my-business-rank-tracker/report-groups) has its own branding, set in the same editor.

## Publish to a client

**Publish to client** in the title menu, or **Manage** under **Client link** in the panel, turns the report into a link your client opens in any browser, with an optional password. The client sees a read-only copy of the same layout, with Google Maps only: the Local Pack and the Local Finder are not published, and neither are notes or editing. You can also use your own domain.

A published map uses your **Browser Maps JavaScript Key**, a separate key that anyone who opens the report can see. Restrict it by website. The setup, the domain and the password are in [Share Reports with Clients](/guide/white-labeled-client-report), and the key in [Google Maps in Published GMB Reports](/guide/white-labeled-client-report#google-maps-in-published-gmb-reports).

## Automated exports

An [automation](/guide/automations) can email, export a PDF or call a webhook when a report's run finishes, so the report goes out without you opening it.


# Ask Your AI App

When your AI app is connected to SEO Utils, it can set up the GMB Rank Tracker, create and run reports, group locations and read the results for you, in plain language.

{% hint style="info" %}
For setup, connect your app as described in [Set Up SEO Utils](/guide/set-up-seo-utils#set-up-with-your-ai-app-recommended). To use the tracker itself from your AI app you also need the [MCP add-on](/guide/mcp-server#setting-up-the-mcp-server). Without it, your AI app can set up SEO Utils but not run its tools.
{% endhint %}

## Set up with your AI app

Ask it to set up the GMB Rank Tracker. It checks what is missing, starts [Connect Google](/guide/google-my-business-rank-tracker/set-up#google-places-api-key) for the Google Places API key, opens the DataForSEO card and explains what a run costs. You sign in to Google and paste the DataForSEO login in SEO Utils: your AI app never asks for a key in the chat.

> Set up the GMB Rank Tracker for me. What is missing?

On a GMB page that still misses a step, **Set up with your AI app** copies the prompt for that step.

## What to ask

| You want to                  | Ask, for example                                                                                                                                                                                    |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Find a business**          | "Find Harbor & Pine Coffee on 1420 4th Ave, Seattle." You can also paste its Google Maps link                                                                                                       |
| **Create a report**          | "Create a GMB rank tracker for Harbor & Pine Coffee Downtown: 5x5 grid, 0.5 miles, keywords 'coffee shop' and 'espresso bar', weekly on Mondays, and track the Local Pack and the Local Finder too" |
| **Search from another area** | "Track Harbor & Pine Coffee but search as if from Ballard." The grid moves, and the business stays                                                                                                  |
| **Change a report**          | "Switch my Downtown report to a 7x7 grid and run it twice a month." "Turn on the Local Finder for report 1"                                                                                         |
| **Run a report**             | "Run my Downtown GMB report now." This spends DataForSEO credit                                                                                                                                     |
| **Delete reports**           | "Delete the test reports." Your AI app lists them first, and you confirm                                                                                                                            |
| **Group locations**          | "Create a report group with all my Harbor & Pine Coffee reports"                                                                                                                                    |
| **Read a group**             | "Show me the visibility score for Harbor & Pine Coffee across all locations, compared with 30 days ago." "Which location ranks best for 'espresso bar'?"                                            |
| **Read a report**            | "How many spots do I rank top 3, top 10 and not at all for 'coffee shop'?" "Show me the trend for 'coffee shop' in report 1"                                                                        |
| **Look at the area**         | "What is the population density and median income around my Downtown business?"                                                                                                                     |

The more specific you are about the grid, the schedule and the lists, the less it has to ask you back.

## What it cannot do for you

* **Sign in to Google, accept its terms or choose a billing account.** You do these in SEO Utils when it asks
* **Enter your keys.** You paste them in SEO Utils, never in the chat
* **Change the keywords of an existing report.** Add, pause or delete them in the report's [Keywords tab](/guide/google-my-business-rank-tracker/manage-reports#manage-keywords)
* **Look at the map.** It reads your data. Click a pin yourself to see a [spot](/guide/google-my-business-rank-tracker/spot)
* **Run for free.** A run or a group's **Run now** spends DataForSEO credit, so check the price before you say yes

{% hint style="warning" %}
A group dashboard that your AI app reads covers Google Maps. For the Local Pack and the Local Finder, use the dashboard in SEO Utils.
{% endhint %}

More example prompts are in [MCP Server](/guide/mcp-server#example-prompts).


# Manage Reports

Change a report, its keywords and its tags, add notes to its timeline, copy it for another location or delete it.

## Edit a report

Open the title menu and choose **Edit**, or choose **Edit** in the row menu of the [reports list](/guide/google-my-business-rank-tracker/your-reports). The form is the same four steps as when you [created it](/guide/google-my-business-rank-tracker/create-a-report), with the settings the report has now. The buttons at the top are **Cancel** and **Save**.

* **Business and area:** the business's address and coordinates are shown. **Update** next to them offers **Refresh from Google**, for a business that has moved, or **Set Manually on Map**, which lets you drag the pin and click **Save Position**. You can change the shape, size, radius and spacing, and turn spots on or off
* **Keywords and result sets:** the box adds new keywords. Turn the Local Pack and the Local Finder on or off here
* **Schedule** and **Report and integrations:** the frequency, the days, the name, the comparison days and the RingTonic campaigns

A change applies to the next run. Runs you already have keep the grid they used. If you change the grid between two runs, SEO Utils cannot compare spot by spot, so the change arrows between those runs are hidden.

## Manage keywords

The **Keywords** tab is one table that analyses and manages the keywords. Open it from the title menu (**Manage Keywords**), the **keywords** chip in the top bar or **Manage** in the keyword list.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-35dad08d90de04822e456f413cc737d7c9f72a83%2Fgmb-keywords-tab.png?alt=media" alt="The Keywords tab with the maps average, share in the pack, finder average, SoLV, tracking switch and Add keywords"><figcaption><p>The Keywords tab: add keywords (1), the tracking switch (2) and the figure for each list (3)</p></figcaption></figure>

A line above the table says which run the figures come from, for example "Figures from the Nov 9 run, compared with Nov 2". Each row shows the keyword, its tags, **Maps avg** with its change, **In the pack**, **Finder avg**, **SoLV**, a small chart of the last runs and the **Tracking** switch. A keyword the run did not check shows a dash, with the reason: it is paused, or it was added after that run.

Click a keyword to show it on the map.

| To                               | Do this                                                                                                   |
| -------------------------------- | --------------------------------------------------------------------------------------------------------- |
| **Add keywords**                 | Click **Add keywords**, enter one keyword per line and click **Save Changes**                             |
| **Pause or resume**              | Use the **Tracking** switch. A paused keyword is left out of every scheduled and manual run               |
| **Tag, pause or delete several** | Tick their checkboxes, or the one in the header to select across pages, and use the bulk actions          |
| **Update tags or delete one**    | Use the **···** menu of its row. Deleting asks in the row first, and removes the keyword with its history |
| **Filter**                       | Search by keyword, or filter by **Status** and **Tags**                                                   |

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-51fe9825b98cff06d0028ee07117f47d21aab09d%2Fgmb-keywords-add.png?alt=media" alt="The Add Keywords dialog with one keyword per line"><figcaption><p>Add keywords, one per line</p></figcaption></figure>

{% hint style="info" %}
To run one keyword on its own, pause all the others and run the report. Resume them afterwards.
{% endhint %}

## Tags

Tags group reports and keywords. Choose **Update Tags** in a report's row menu to tag the report, and filter the [reports list](/guide/google-my-business-rank-tracker/your-reports#search-and-filter) by **Tags**. Tag a keyword from its row in the Keywords tab. Tags show next to the keyword in the keyword list.

## Notes

Notes mark what you changed, such as new photos on your Google Business Profile, a new opening hour or a burst of review replies, so you can see what may have moved your ranking. They appear as flags on the [runs timeline](/guide/google-my-business-rank-tracker/history#the-runs-timeline) and as markers on the [Trend](/guide/google-my-business-rank-tracker/history#trend) chart. SEO Utils also adds the dates of Google updates for you.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5eae0f8c7414ba357155d903cee2be06d4e533bf%2Fgmb-notes-menu.png?alt=media" alt="The Notes menu with Show on the timeline, Note types, View all notes and Add note"><figcaption><p>The Notes menu on the timeline</p></figcaption></figure>

The **Notes** menu on the timeline has:

* **Show on the timeline:** switch notes on or off on the strip
* **Note types:** show all types, or only some
* **View all notes:** the list of every note
* **Add note:** a title, a date and some content, then **Save changes**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d32d47840308e17b536a859a666fe7fee33573ca%2Fgmb-notes-add.png?alt=media" alt="The Add Annotation dialog with a title, a date and some content"><figcaption><p>Add a note</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-913c9a5a91e19975593520cf24fb7cbd8a0153aa%2Fgmb-notes-timeline.png?alt=media" alt="The runs timeline with a note flag after the latest run"><figcaption><p>A note shows as a flag on the timeline</p></figcaption></figure>

## Clone a report

Clone a report to track a second location with the same setup. Choose **Clone** in the row menu, name the new report and search for the new business.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f775762e3ed9474cd00a37da6881bb630484871c%2Fgmb-clone-dialog.png?alt=media" alt="The Clone Report dialog with the report name, Search With and Address"><figcaption><p>The Clone Report dialog</p></figcaption></figure>

The clone keeps the original's keywords, lists, schedule and settings, and moves the grid, with its turned-off spots, to the new business. It does not start a run.

## Delete

Choose **Delete Report** in the title menu or **Delete** in the row menu, and confirm. SEO Utils deletes the report with its keywords, grid and every run. This cannot be undone. A [report group](/guide/google-my-business-rank-tracker/report-groups) that contained it keeps its other reports.

To remove a single run, use **Delete this run** in its menu on the [timeline](/guide/google-my-business-rank-tracker/history#the-runs-timeline). To move reports to another workspace, use **Bulk Actions → Move to Workspace** in the reports list.


# N.A.P Finder

The N.A.P Finder tool in SEO Utils streamlines local citation tracking for businesses. It automatically searches for variations of a business’s name, address, and phone number (N.A.P.) across the web, helping you find inconsistent or rogue citations indexed in search engines.

**What N.A.P Finder does for you:**

* Discovers all your business citations with a single click
* Identifies inconsistent N.A.P. information that could hurt your local rankings
* Exports comprehensive citation data into easy-to-use reports
* Saves hours of manual search work

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6a14b4e0ad3ab3783ed5b66f9f20fcbc9b3383f8%2FXnapper-2024-10-21-17.31.17.png?alt=media" alt=""><figcaption><p>N.A.P Finder report</p></figcaption></figure>

You can access the tool in the left sidebar under the Local SEO menu.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f20654e9e4a3d34a32b2cd81b1e568d6b86279e8%2FXnapper-2024-10-21-20.34.29.png?alt=media" alt="" width="375"><figcaption><p>Access N.A.P Finder tool</p></figcaption></figure>

### Manage Search Term Lists

You can click the "Manage Search Term Lists" button to see all the search term Lists.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6db5546b16dffe3bf156d3ccd6106a1df6aeb26a%2FCleanShot%202024-10-22%20at%2011.50.19%402x.png?alt=media" alt=""><figcaption><p>Manage Search Term Lists button</p></figcaption></figure>

SEO Utils allows you to create a Search Term List to automatically search for N.A.P. information on Google. You can structure search terms using placeholders, which are then replaced with your actual business details like name, address, and phone number. For instance, a placeholder search term like:

```
"[business]" "[address_line_1]" - "[phone]"
```

is transformed by SEO Utils into:

```
"Monsoon Seattle" "615 19th Ave E" - "(206) 325-2111"
```

This makes it easy to generate precise search queries for accurate N.A.P. tracking.

By default, SEO Utils will create a **Default** list with these placeholders:

```
"[business]" "[address_line_1]" - "[phone]"
"[business]" "[phone]"
"[business]" - "[phone]"
"[address_line_1]" "[phone]"
"[address_line_1]" - "[phone]"
"[business]" "[address_line_1]"
"[business]" - "[address_line_1]"
"[business]" "[phone]" - "[address_line_1]"
"[business]" "[address_line_1]" - "[phone]"
"[address_line_1]" - "[business]"
"[phone]" - "[business]"
"[phone]" - "[address_line_1]"
"[phone]" - "[address_line_1]" - "[business]"
"[address_line_1]" - "[business]" - "[phone]"
```

You can create a new search term list with your custom placeholders by clicking the "Add List" button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f2d62b0e546f58826174cab523a2735fc1a459a7%2FXnapper-2024-10-24-22.21.19.png?alt=media" alt=""><figcaption><p>Add a new search term list modal</p></figcaption></figure>

{% hint style="info" %}
Note: To search for exact data on Google, be sure to enclose your placeholders in double-quotes. For example: **"\[business]"**. This ensures that Google retrieves precise matches for your business name.
{% endhint %}

### How to Start an N.A.P Finder Report?

After clicking the "**Run N.A.P Finder**" button, you will see a form like this:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2da6e7dc3d324b32f53610d5bad9c55d70e0590c%2Fnap-finder-run-form.png?alt=media" alt=""><figcaption><p>Run N.A.P Finder form. (1) Location. (2) Language</p></figcaption></figure>

Let’s walk through all the fields.

**Business fields**

SEO Utils replaces placeholders in your [search term list](#manage-search-term-lists) with the following business details:

* Business Name
* Address Line 1
* Address Line 2 (Optional)
* City
* State
* Postal Code
* Phone Number

**SERP Scraping fields**

**Location:** Type a country, region, city or postal code and pick it from the list. For a local business, pick its city. A country searches the whole country. See [Organic Rank Tracker](/guide/organic-rank-tracker#report-tab) for more on locations.

**Language:** Select the language you are targeting.

**Desktop Devices:** Enabling this field simulates desktop devices when scraping SERP data. If disabled, SEO Utils will simulate mobile devices.

**Search Term List:** Choose a search term list for your N.A.P. search. You can either use the default list provided by SEO Utils or create a custom list tailored to your specific needs.

**Scrape SERP With:** This field functions just like the Organic Rank Tracker tool. For detailed information on how it works, please refer to the “Scraping SERP Methods” section in the [Organic Rank Tracker guide](https://help.seoutils.app/guide/organic-rank-tracker#scraping-serp-methods).

{% hint style="warning" %}
**Important:** To use the SERP API, you must have your own DataForSEO account. [Renting API key services](https://help.seoutils.app/guide/rent-dataforseo-api-key) isn't viable because DataForSEO restricts certain endpoints that I utilized to implement the Queue mode. If multiple users rely on a rented API key from my account, it will slow down the process for everyone. For the quickest results, using your own DataForSEO account is the best approach.
{% endhint %}

#### Updates on v1.21.0

**Excluded Domains field**

Since v121.0, SEO Utils allows you to exclude specific domains from search results by using the `-site:domain.com` operator. This feature makes it easier to filter out unwanted sites and focus on relevant citations.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-63453ad773a9b3083b33dc0d808142fb4a35bb77%2FXnapper-2024-10-31-12.56.26.png?alt=media" alt=""><figcaption><p>Add domains to exclude</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-23706452980da93a610748dc3288e115c241b73c%2Fplaceholder.png?alt=media" alt=""><figcaption><p>Exclude domain using "-site:domain.com" operator</p></figcaption></figure>

**Multiple Phone Number Formats**

You now can enter various phone number formats in the N.A.P Finder tool. SEO Utils will use each format for more thorough search results.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f370264fd4694eb4e6d9b33ded8433bc96c725f4%2FXnapper-2024-10-31-12.58.37.png?alt=media" alt=""><figcaption><p>Enter different phone number formats.</p></figcaption></figure>

### Mange Your N.A.P Finder Reports

After successfully running a report, you’ll see a table like the one shown.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d3cd8a42a9aa8679d66355bbb66baa152f9e9822%2FXnapper-2024-10-22-12.06.33.png?alt=media" alt=""><figcaption><p>N.A.P Finder report</p></figcaption></figure>

Here’s a breakdown of each column:

**Title**: Displays the title of the webpage where your N.A.P. information appears. It also includes the URL of the page, allowing you to easily access the site where the citation is found.

**Search Term**: Shows the exact search term used, with your business details (like name, address, and phone number) replacing the placeholders.

**Position**: Indicates the ranking position of the result on the search engine results pages (SERP).

{% hint style="info" %}
You can click on the SERP button to view detailed SERP data for each result.
{% endhint %}

#### Available Filters

**Search Term Filter:** Allows you to filter results based on specific search terms from your list, making it easy to target certain N.A.P. variations.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-56ad443437a47ef5b914e16cc67cc5c2410f4d22%2FXnapper-2024-10-22-12.12.55.png?alt=media" alt=""><figcaption><p>Search term filter</p></figcaption></figure>

**Position Filter:** This lets you narrow the results to show only those that rank within the top 10, top 30, or any position range you specify.

**Domain Filter:** Helps you filter by domain to view where your business is cited across specific websites.

Once you’re satisfied with the results, you can export the data as a CSV file for further analysis by clicking the **Export** button.


# Google Business Reviews Fetcher

<div data-full-width="false"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d8b0b939359374461cdc360a355e1950c50ce27c%2FXnapper-2025-11-25-12.39.47.png?alt=media" alt=""><figcaption></figcaption></figure></div>

The Google Business Reviews Fetcher automatically collects and tracks Google reviews for a single business location. Instead of manually checking Google Maps for new reviews, this tool fetches review data on a schedule and tracks changes over time through snapshots.

### Why Use This Tool

**Perfect for:**

* Businesses monitoring their Google reviews over time
* Tracking new reviews as they come in
* Building a historical record of all reviews
* Exporting review data for reporting or analysis
* Monitoring owner response rates

**Key Benefits:**

* 📸 Snapshot-based tracking - See exactly what changed each time
* 🔄 Smart depth calculation - Automatically optimizes API costs
* 📊 Deduplication - Only tracks new reviews, skips duplicates
* 👁️ Visibility tracking - Optionally detect when reviews disappear or reappear on Google
* 🔔 Email alerts for low-rating reviews via Automations
* 💾 Export reviews to CSV for analysis
* ⏰ Scheduled or manual fetching

### Quick Start Guide

{% hint style="warning" %}
This tool requires you to set up a Google Places API key to search for Google businesses. Please read the guide at: [Setup Google Places API key](/guide/google-my-business-rank-tracker/set-up#google-places-api-key)
{% endhint %}

#### Step 1: Add a Business

1. Navigate to **Google Business Reviews Fetcher** in the sidebar
2. Click **"Create New Fetcher"**
3. Search for your business using the business search field
4. Enter a friendly name (e.g., "Downtown Seattle Location")

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9155f0d224151e48e6a1ecc7311ec355d8e9de33%2FXnapper-2025-11-25-12.41.08.png?alt=media" alt="" width="375"><figcaption><p>Access Google Business Reviews Fetcher tool</p></figcaption></figure>

#### Step 2: Configure Fetch Settings

**Initial Depth** (First run only)

* How many historical reviews to fetch on first run
* Range: 10 - 4,490 reviews (in multiples of 10)
* Example: Set to 1,000 to fetch complete review history
* **This only runs once** - pulls all historical reviews

**Subsequent Depth** (Optional)

* How many reviews to fetch on future runs
* Leave at **0 for automatic** (recommended)
* Or set a custom value if you know your review volume

**How Automatic Depth Works:**

```
First Run: Fetches 1,000 reviews (your historical data)
Second Run: Automatically calculates based on schedule
  - Example: 7-day schedule = ~21 reviews (3/day × 7 days)
Third+ Runs: Analyzes previous snapshot
  - If last run found 15 new reviews
  - Next run fetches ~30 reviews (15 × 2 buffer)
```

**Track Disappearing Reviews** (Optional)

* Off by default
* Turn on to detect reviews that Google removes or that reviewers delete
* Every run after the first fetches your **complete** review list, overriding Subsequent Depth
* Uses more DataForSEO credits per run, since each run pulls every review instead of just the newest ones

{% hint style="warning" %}
Confirming that a review was removed requires seeing every review the business has. A shorter fetch cannot tell a deleted review apart from one that simply sits below the depth limit.

Leave this off to keep runs cheap — snapshots will then state that missing reviews were not checked, rather than reporting numbers that cannot be trusted.
{% endhint %}

**Schedule Interval**

* 0 = Manual only (you click "Fetch Data" when needed)
* 7 = Weekly (runs every 7 days)
* 30 = Monthly (runs every 30 days)
* Custom = Any number of days

**Location & Language**

* Select the geographic location and language for review fetching
* Example: United States - English

**Queue Priority**

* **Standard Queue**: Up to 45min processing, $0.00075 per 10 reviews
* **Priority Queue**: Up to 1min processing, $0.0015 per 10 reviews

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-12e2f10d02765b008847e7137ba764f858ca46d5%2FXnapper-2025-11-25-12.43.06.png?alt=media" alt=""><figcaption><p>Create a Google Business Reviews Fetcher</p></figcaption></figure>

#### Step 3: Save and Run

1. Click **"Add Business"**
2. Initial fetch starts automatically
3. You'll be redirected to the snapshot page showing progress

### Understanding the Business Detail Page

After creating a business, you'll see the detail page with:

#### Business Information Card

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f9edc66915a14d706e458ba40dde0b868073aa7e%2FXnapper-2025-11-25-12.51.59.png?alt=media" alt=""><figcaption><p>Business Information Card</p></figcaption></figure>

Shows configuration and tracking details:

* **Address**: Business name and location
* **Place ID**: Google's unique identifier for this business
* **Schedule**: How often reviews are fetched (Manual, Weekly, etc.)
* **Queue Priority**: Standard or Priority processing
* **Initial Depth**: Number of reviews fetched on first run
* **Last Run**: When reviews were last fetched
* **Total Snapshots**: How many times reviews have been fetched
* **Location & Language**: Geographic and language settings

#### Snapshots History Table

Every time you fetch reviews, a new snapshot is created. The table shows:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4644aa3e11c6f8e3f0c37f7d04e60a24a4fe4137%2FXnapper-2025-11-25-12.52.34.png?alt=media" alt=""><figcaption><p>Snapshots History Table</p></figcaption></figure>

**Columns:**

* **Date**: When the snapshot was created
* **Depth**: How many reviews were requested from the API
* **Found**: Total reviews returned by Google
* **New**: Reviews that didn't exist in previous snapshots
* **Duplicates**: Reviews already captured in previous snapshots
* **Status**: Pending → Processing → Completed (or Failed)
* **Type**: Scheduled (automatic) or Manual (you clicked "Fetch Data")

**Example Snapshot Flow:**

```
Snapshot #1 (Initial):
  Depth: 1,000
  Found: 847 reviews
  New: 847 (all are new on first run)
  Duplicates: 0

Snapshot #2 (7 days later):
  Depth: 30 (auto-calculated)
  Found: 18 reviews
  New: 3 (3 new reviews since last week)
  Duplicates: 15 (already had these)

Snapshot #3 (7 days later):
  Depth: 30 (auto-calculated)
  Found: 25 reviews
  New: 5 (5 new reviews this week)
  Duplicates: 20 (already had these)
```

#### Actions

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-62dcc0b8fbc1478008417ced25c156747b4afb9c%2FXnapper-2025-11-25-12.54.21.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

* **Fetch Data**: Manually trigger a new snapshot
* **Edit**: Change business settings (except business selection)
* **Delete**: Remove business and all snapshots

#### Bulk Actions

From the main business list, you can select multiple businesses using the checkboxes and perform bulk actions:

* **Fetch Reviews**: Trigger a review fetch for all selected businesses at once. The fetches run sequentially to avoid API overload.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FFSllctd7jzXkWS2YjaHY%2FXnapper-2026-01-10-14.58.14.png?alt=media&amp;token=3f24f2df-6dd8-4f07-ada7-6cf1376c8fa4" alt=""><figcaption><p>Fetch reviews for multiple businesses</p></figcaption></figure>

This is useful when you want to manually refresh reviews for multiple businesses before generating reports.

### Viewing Review Data (Snapshot Page)

Click on any snapshot date to view the reviews captured in that snapshot.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f6508a90806cd0afa3d18f10086bb3e17897bc2c%2FXnapper-2025-11-25-12.55.05.png?alt=media" alt=""><figcaption><p>View detail a snapshot</p></figcaption></figure>

#### Snapshot Information

Shows details about this specific fetch:

* **Date**: When this snapshot was created
* **Depth**: How many reviews were requested
* **Reviews Found**: Total reviews returned by Google
* **New Reviews**: Reviews discovered for the first time
* **Duplicates Skipped**: Reviews already in previous snapshots
* **Status**: Completion status
* **Type**: Manual or Scheduled run
* **Business Rating**: Overall star rating and total review count
* **Missing Reviews**: Every review known to this business that is no longer on Google, with the number that disappeared in this particular run shown next to it (appears only when the run checked for missing reviews)
* **Reinstated Reviews**: Reviews that reappeared after being missing (shown only if > 0)

If a run could not check for missing reviews, a notice appears here explaining why. See [Review Visibility Tracking](#review-visibility-tracking) below.

#### Reviews Table

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9566765b712c154ed6a5254aceb0b85189e0125c%2FXnapper-2025-11-25-12.55.50.png?alt=media" alt=""><figcaption><p>Reviews table</p></figcaption></figure>

**Cumulative View (Default)**

By default, the snapshot page shows **all reviews ever collected** for this business with their current visibility status. This gives you a complete picture of all reviews regardless of which snapshot first captured them.

To see only reviews from this specific snapshot, enable the **"Only show reviews in this snapshot"** toggle above the table.

**Review Columns:**

* **Reviewer**: Name, photo, profile (if available)
  * Shows review count and photo count
  * "Local Guide" badge if applicable
* **Rating**: Star rating (1-5)
  * Number of "helpful" votes
  * "View on Google" link to see review on Google Maps
* **Review Date**: When the review was posted
* **Review Text**: Full review content
  * Expandable for long reviews
  * Shows review images if attached
* **Owner Response**: Business reply to the review
  * Shows if owner has responded
  * Full response text
* **Status**: Review visibility status (see below)

#### Review Visibility Tracking

The tool can detect when reviews disappear from Google and when they come back. Every review carries a visibility status:

| Status         | Description                                                                           |
| -------------- | ------------------------------------------------------------------------------------- |
| **New**        | First time discovered for this business                                               |
| **Visible**    | Currently visible on Google                                                           |
| **Missing**    | Was visible before but no longer on Google (deleted by reviewer or removed by Google) |
| **Reinstated** | Was missing but has reappeared on Google                                              |

**When missing reviews are checked**

To keep costs down, a regular fetch pulls only your most recent reviews. That means it cannot tell a removed review apart from one that simply sits below the depth limit — so missing reviews are reported only when a run has seen **every** review the business has.

Turn on **Track disappearing reviews** in the business settings to make each run fetch the complete list and compare it against everything collected previously.

When a run could not check, the snapshot says so instead of reporting numbers that cannot be trusted:

| Why the check was skipped                                    | What to do                                                             |
| ------------------------------------------------------------ | ---------------------------------------------------------------------- |
| The run covered only part of the review list                 | Turn on **Track disappearing reviews** so future runs fetch everything |
| There is nothing collected yet to compare against            | Run another fetch — the next one can report changes                    |
| The business has more reviews than a single run can retrieve | Removals cannot be detected for this business                          |
| Google returned incomplete data for the run                  | Run the fetch again                                                    |

{% hint style="info" %}
**Why do reviews go missing?** Reviews can disappear from Google for several reasons:

* Reviewer deleted their review
* Google removed it for policy violations
* Google's spam filter flagged it (may be reinstated later)
* Temporary Google Maps data issues
  {% endhint %}

{% hint style="warning" %}
**Snapshots created before version 1.48.1** show a notice that their missing-review counts are unverified.

Earlier versions counted every review a run had not looked at as missing, so those counts can include reviews that are still live on Google. The data is left in place, but confirm it with a new fetch before acting on it — particularly before raising a case with Google.
{% endhint %}

#### Filters

* **Rating**: Filter by star rating (e.g., show only 1-2 star reviews)
* **Owner Response**: Filter by "With Response" or "No Response"
* **Visibility**: Filter by status (New, Visible, Missing, Reinstated)
* **Search**: Search reviewer names or review text

#### Export

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-46be2088ca55292175c6cdb2dd3c66c043bfeb83%2FXnapper-2025-11-25-12.57.38.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

Click **Export** to download reviews as a CSV file.

The export matches what is on screen. It respects the current filters, the search box, and the **"Only show reviews in this snapshot"** toggle — so filtering the table to **Missing** and clicking Export gives you a file containing only the disappeared reviews.

Each row includes a **Visibility Status** column (New, Visible, Missing or Reinstated), along with the reviewer name, rating, date, review text, any owner response, and a direct link to the review on Google.

Use exports for:

* Client reporting
* Analysis in Excel/Google Sheets
* Documenting disappeared reviews when raising a case with Google
* Integration with other tools
* Long-term archiving

### Example Workflows

<details>

<summary>Workflow 1: New Business Setup</summary>

**Goal**: Track reviews for a coffee shop with \~200 total reviews

**Setup:**

```
Business: Blue Bottle Coffee - Ferry Building
Initial Depth: 500 reviews
Subsequent Depth: 0 (automatic)
Schedule: 7 days (weekly)
Priority: Standard Queue
```

**What Happens:**

1. First run: Fetches 500 reviews, finds 187 total
2. Week 1: Auto-fetches \~21 reviews, finds 2 new reviews
3. Week 2: Auto-fetches \~30 reviews (2×2 buffer), finds 3 new
4. Week 3: Auto-fetches \~30 reviews, finds 1 new
5. Ongoing: Adapts based on review frequency

</details>

<details>

<summary>Workflow 2: High-Volume Business</summary>

**Goal**: Track reviews for busy restaurant getting 5-10 reviews/day

**Setup:**

```
Business: Popular Restaurant Downtown
Initial Depth: 4,490 reviews (max)
Subsequent Depth: 0 (automatic)
Schedule: 3 days
Priority: Priority Queue (faster processing)
```

**What Happens:**

1. First run: Fetches 4,490 reviews (complete history)
2. Day 3: Auto-fetches \~27 reviews, finds 18 new
3. Day 6: Auto-fetches \~36 reviews (18×2), finds 22 new
4. Day 9: Auto-fetches \~44 reviews (22×2), finds 15 new
5. Ongoing: Automatically adjusts to review volume

</details>

<details>

<summary>Workflow 3: Manual Monitoring</summary>

**Goal**: Fetch reviews only when needed (e.g., before monthly reports)

**Setup:**

```
Business: Consulting Firm
Initial Depth: 100 reviews
Subsequent Depth: 50
Schedule: 0 (manual only)
Priority: Standard Queue
```

**What Happens:**

1. First run: Manual click, fetches 100 reviews
2. Month 1: Manual click, fetches 50 reviews
3. Month 2: Manual click, fetches 50 reviews
4. Ongoing: You control when to fetch

</details>

<details>

<summary>Workflow 4: Monitoring Disappearing Reviews</summary>

**Goal**: Build evidence that reviews are being removed from a business with \~90 reviews

**Setup:**

```
Business: Local Dental Practice
Initial Depth: 100 reviews
Track Disappearing Reviews: On
Schedule: 7 days (weekly)
Priority: Standard Queue
```

**What Happens:**

1. Each run fetches the complete review list rather than just the newest reviews
2. Any review that was present before and is now gone is marked **Missing**
3. The snapshot shows the running total of missing reviews, plus how many disappeared in that run
4. If a review returns later, it is marked **Reinstated**

**To pull the evidence:**

1. Open the snapshot and set the **Visibility** filter to **Missing**
2. Click **Export**
3. The file lists each disappeared review with its reviewer, rating, date, text and Google link

</details>

### Setting Up Low-Rating Alerts (Automation)

Get notified by email when new reviews below your rating threshold are detected using the [Automations](/guide/automations) tool.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ab94fb841fa481771d77cc42635cba2d2c142887%2FXnapper-2025-11-25-13.03.53.png?alt=media" alt=""><figcaption></figcaption></figure>

#### How It Works

After each fetch completes, the automation system:

1. Checks for NEW reviews in the snapshot
2. Filters reviews by your rating threshold (e.g., 3 stars or lower)
3. Sends email only if matching reviews are found
4. Skips notification if no reviews match criteria

#### Step-by-Step Setup

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-95e707107ea91a5ceed608015959b04efe1f7460%2FXnapper-2025-11-25-13.05.35.png?alt=media" alt=""><figcaption></figcaption></figure>

1. Go to **Automations** in the sidebar
2. Click **"Create Automation"**
3. Configure the automation:

**Basic Settings:**

```
Name: Low Rating Alert - [Your Business Name]
Trigger: Google Business Reviews Snapshot
Report: Select your business (or "All Reports" for all businesses)
```

**Trigger Configuration:**

```
Include All Reviews: No (unchecked) - Only sends alerts for reviews at or below threshold
                     Yes (checked)  - Sends alerts for ALL new reviews regardless of rating
Rating Threshold: 3 (triggers for 1, 2, or 3 star reviews) - Only visible when "Include All Reviews" is unchecked
```

**Add Action → Send Email:**

```
To: your-email@company.com
Subject: ⚠️ {{trigger.newReviewsMatchingCount}} New Low-Rating Review(s) - {{trigger.businessName}}
```

**Email Body:**

```
{{trigger.newReviewsMatchingCount}} new review(s) with ratings at or below {{trigger.ratingThreshold}} stars have been detected for {{trigger.businessName}}.

{{trigger.reviewsList}}

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Business Information:
Name: {{trigger.businessName}}
Address: {{trigger.address}}
Place ID: {{trigger.placeID}}

Summary:
• Total new reviews: {{trigger.newReviewsCount}}
• Matching criteria: {{trigger.newReviewsMatchingCount}}
• Average rating: {{trigger.averageRating}}/5
• Total reviews: {{trigger.totalReviews}}

Action Required:
Please review this feedback and respond promptly to address customer concerns.

---

This is an automated notification from SEO Utils.
Snapshot Date: {{trigger.createdAt}}
```

4. Click **"Save Automation"**

#### Available Template Variables

| Variable                              | Description                        | Example                    |
| ------------------------------------- | ---------------------------------- | -------------------------- |
| `{{trigger.businessName}}`            | Business name                      | "Blue Bottle Coffee"       |
| `{{trigger.address}}`                 | Business address                   | "123 Main St, Seattle, WA" |
| `{{trigger.placeID}}`                 | Google Place ID                    | "ChIJ..."                  |
| `{{trigger.newReviewsCount}}`         | Total new reviews found            | 5                          |
| `{{trigger.newReviewsMatchingCount}}` | Reviews matching threshold         | 2                          |
| `{{trigger.ratingThreshold}}`         | Configured threshold               | 3                          |
| `{{trigger.averageRating}}`           | Business average rating            | 4.2                        |
| `{{trigger.totalReviews}}`            | Total review count                 | 847                        |
| `{{trigger.reviewsList}}`             | Formatted list of matching reviews | (see below)                |
| `{{trigger.createdAt}}`               | Snapshot date                      | "2024-01-15"               |

#### Example Email Output

```
2 new review(s) with ratings at or below 3 stars have been detected for Blue Bottle Coffee.

Review 1:
Rating: 2/5 ⭐⭐
Reviewer: John D.
Date: 2024-01-15
Review: "Coffee was cold and service was slow. Very disappointed."
View Review: https://maps.google.com/...

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Review 2:
Rating: 1/5 ⭐
Reviewer: Sarah M.
Date: 2024-01-14
Review: "Worst experience ever. Will not return."
View Review: https://maps.google.com/...

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Business Information:
Name: Blue Bottle Coffee
Address: 1 Ferry Building, San Francisco, CA
Place ID: ChIJAQDl8...

Summary:
• Total new reviews: 5
• Matching criteria: 2
• Average rating: 4.2/5
• Total reviews: 847

Action Required:
Please review this feedback and respond promptly to address customer concerns.

---

This is an automated notification from SEO Utils.
Snapshot Date: 2024-01-15
```

{% hint style="success" %}
Besides sending emails, you can set up the [Automations tool](/guide/automations) to send data view webhooks, so you can perform other analyses or automations.
{% endhint %}


# Local SERP Checker

The SERP UULE tool leverages the UULE (Unicode URL-Encoded) parameter, a method Google uses to understand and simulate search results as if they were being conducted from various geographic locations. This capability is significant because Google's search results can vary greatly depending on the searcher's location, due to localization and personalization factors.

By manipulating the UULE parameter, this tool can simulate searches from different locations, providing insights into how search results appear to users in those areas.

### Benefits of Using the SERP UULE Tool

1. **SEO Strategy Optimization:** By understanding how websites rank in different regions, SEO professionals can tailor their strategies to target specific geographic markets more effectively.
2. **Competitive Analysis:** It enables businesses to see how their competitors perform in different locales, providing insights into local market competition and identifying potential areas for expansion.
3. **Content Localization:** Helps in identifying what localized content performs well in certain regions, guiding content creation and marketing strategies to cater to local tastes and preferences.
4. **Ad Campaigns Refinement:** By analyzing search results in different locations, marketers can refine their ad campaigns to be more relevant to local audiences, potentially increasing engagement and conversion rates.

### **How To Check Google Search Results for Different Locations**

1. Click the "SERP UULE" tool in the left sidebar.
2. Enter a search query.
3. Pick the **Location** that you want to view the search results for: a country, region, city or postal code. Then pick the **Language**.
4. Hit the "Search" button. SEO Utils will open a new tab with the SERP based on the location you selected.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-686faac3eb3a55115e11cb78bfb17fe79bbe137a%2Flocal-serp-checker-uule-search.png?alt=media" alt=""><figcaption><p>SERP UULE</p></figcaption></figure>

### How to Change the Default Location

You can change the default location by visiting **Settings > General**. Choose the **Default Location** and the **Default Language**, then click **Save**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cf6cac5a46e88b3d33d2a34bb69031e23d661089%2Flocal-serp-checker-default-location.png?alt=media" alt=""><figcaption><p>Set the default location. (1) Default Location. (2) Default Language</p></figcaption></figure>

By setting the default location, new forms start with it, so you won't have to pick it in every search.


# Organic Rank Tracker

This tool enables you to track keywords ranking in organic search results on Google or Bing. You can customize tracking for desktop or mobile searches, as well as target specific locations. It also generates insightful reports, helping you compare your website’s performance against competitors.

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-51b3b0a425fe0d71b343bef458fa916a97f6b81a%2FXnapper-2024-09-30-10.24.02.png?alt=media" alt=""><figcaption><p>Organic Rank Tracker tool</p></figcaption></figure></div>

{% hint style="info" %}
**New in** [**v1.30.0**](https://help.seoutils.app/changelog#v1.30.0): You can now access the [Organic Rank Tracker Dashboard](https://help.seoutils.app/guide/dashboard/organic-rank-tracker) to view an overview of all your rank tracking reports in one place. This dashboard helps you quickly monitor performance across multiple domains, devices, and locations.
{% endhint %}

### How to Add a Tracker

You can access the tool from the Organic SERP menu, where you’ll find an “Add Rank Tracker” button in the top-right corner.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6fb43c5a15fbfd19cd38a461753e145b70564a26%2FXnapper-2024-09-30-09.20.40.png?alt=media" alt="" width="375"><figcaption><p>Access Organic Rank Tracker tool</p></figcaption></figure>

After clicking the button, the tracker form opens. Its fields are grouped into four tabs: **Report**, **SERP Collection**, **Page HTML**, and **Schedule**. If validation finds an error, SEO Utils automatically opens the tab that contains the field so you can correct it.

#### Report tab

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ad3a6bd387b97933ffc6da1d2d037f67ba63726a%2Forganic-rank-tracker-report-tab.png?alt=media" alt=""><figcaption><p>Organic Rank Tracker setup form - Report tab. (1) Location. (2) Language</p></figcaption></figure>

**Name:** Enter an optional custom name for the tracker. If you leave it empty, SEO Utils uses the domain.

**Domain:** Enter the target domain here, typically your website’s domain.

**Keywords:** Add a list of keywords you want to track, placing each keyword on a new line. There’s no limit to the number of keywords you can enter. You can add more keywords later.

**Search Engine:** Select Google. Bing support is listed as coming soon.

**Location:** Type a country, region, city or postal code and pick it from the list. A country tracks the whole country; any other place is tracked inside its country. To go back to the whole country, pick the country row again.

**Language:** Select the language you are targeting. SEO Utils uses the Location and Language to gather keyword metrics like CPC and search volume.

{% hint style="info" %}
Hover the (?) next to **Location** to see what you can pick. Each tool lists the locations DataForSEO supports for it, so the list can differ from tool to tool (the Google Business tools, for example, offer countries only). A saved report keeps the location it was created with. If a place is missing, [refresh the location lists](/guide/seo-data-source#refresh-the-location-lists).
{% endhint %}

**Desktop Devices:** Enabling this field simulates desktop devices when scraping SERP data. If disabled, SEO Utils will simulate mobile devices.

**Include Subdomains:** Enable this to count rankings from subdomains of the target domain.

#### SERP Collection tab

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F2ECWPSsrzeBQsrz5iuFP%2FXnapper-2026-08-15-08.51.20.png?alt=media&amp;token=5be12b79-4e8f-4cad-8643-1e89a3cdaeb5" alt=""><figcaption><p>Organic Rank Tracker setup form - SERP Collection tab</p></figcaption></figure>

**Depth:** Choose how many search results SEO Utils should collect for each keyword. This setting cannot be changed after it is set.

**Scrape SERP With:** Choose **My Own IP**, **Proxies**, or **SERP API: DataForSEO**. Method-specific settings appear only when they apply.

**Business Name (DataForSEO only):** Enter your business name to track its position in Google's Local Pack. This is especially valuable for local businesses, as Local Pack positions (1-3) appear prominently at the top of search results. The business name must match exactly as it appears in Google (case doesn't matter).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fn2i62Zdc6nQov0tFI0El%2FXnapper-2026-08-15-08.52.26.png?alt=media&amp;token=4fef67d7-3f8f-4180-bfe9-23ec897a0eb3" alt=""><figcaption><p>You can optionally add the business name to track the local pack</p></figcaption></figure>

**PAA Click Depth (DataForSEO only):** Detect when your domain (or a competitor's) is featured as a source inside Google's People Also Ask box — not just whether the box appears. This is a separate visibility signal from organic ranking, and one that Semrush, Ahrefs, and SE Ranking all expose in their position trackers.

Choose how many PAA questions DataForSEO should expand to reveal source URLs:

* **Off (default)** — PAA box presence is still detected (as a SERP feature), but no source attribution.
* **1–4** — DataForSEO clicks into that many PAA questions and returns each source's URL, title, and domain.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fsm0pfVXZdQjDJeeZTigb%2FXnapper-2026-05-03-15.01.29.png?alt=media&amp;token=5c6c077c-df91-45f4-bb21-5d78491cceed" alt=""><figcaption><p>PAA Click Depth setting in the rank tracker configuration modal</p></figcaption></figure>

{% hint style="warning" %}
**Extra DataForSEO cost:** $0.00015 per click, regardless of priority. Unused clicks (PAA box absent or fewer questions than depth) are automatically refunded by DataForSEO. The cost estimate in the modal updates to reflect the new total when you change this setting.
{% endhint %}

{% hint style="info" %}
**When is this worth enabling?** PAA presence is becoming an important visibility metric as Google leans more on PAA boxes for informational queries. If your content strategy includes answering specific questions, this signal tells you whether Google is citing you as a source. If you only care about the classic blue links, you can leave this off.
{% endhint %}

**Track Pixels From Top (DataForSEO only):** Measure the actual vertical distance — in pixels — between the top of the SERP and each result's snippet. Pure rank position is increasingly misleading because ads, AI Overviews, knowledge panels, PAA boxes, image packs, and other features push organic results down by varying amounts. Pixels From Top reflects the real on-screen visibility a result gets.

Toggle **Track Pixels From Top** on to enable. You can optionally override the browser dimensions DataForSEO uses to render the SERP:

* **Browser Width / Browser Height** — viewport size in pixels. Defaults to **1920 × 1080** on desktop reports and **360 × 640** on mobile reports.
* **Resolution Ratio** — device pixel ratio. Defaults to **1** on desktop, **3** on mobile. Range 0.5–3.

Leave any field empty to use the default — the actual numbers used are shown under each input.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FeUgHvBvKvUfN3fQZpBTv%2FXnapper-2026-05-12-14.39.17.png?alt=media&amp;token=14791fc3-ea08-4a46-8c38-e9b6b9a57a06" alt=""><figcaption><p>Track Pixels From Top toggle and viewport inputs in the rank tracker configuration modal</p></figcaption></figure>

{% hint style="warning" %}
**Extra DataForSEO cost:** $0.0006 per keyword per scrape. The cost estimate in the modal updates to reflect the new total when you toggle this on. For a 1,000-keyword tracker, that's an extra $0.60 per run.
{% endhint %}

{% hint style="danger" %}
**These settings are locked once data is collected.** After your first scrape with Track Pixels From Top enabled, you can no longer change the toggle, browser dimensions, or even switch the scrape method away from DataForSEO. Changing viewport mid-history would invalidate the pixel deltas across snapshots — a measurement taken at 1920×1080 is not comparable to one taken at 1280×800. If you need different settings, create a new tracker. Pick the viewport you want before you start.
{% endhint %}

{% hint style="info" %}
**When is this worth enabling?** SERP layouts have changed dramatically. A result at rank #1 below a fold-filling AI Overview is far less visible than a result at rank #1 with no SERP features. Pixels From Top captures this in a single number that's directly comparable across keywords. Particularly valuable for tracking the impact of ranking improvements when SERP features are added or removed by Google.
{% endhint %}

**Re-check Results That Look Poisoned:** Since mid-September 2026, Google sometimes serves rank trackers a manipulated results page. The page looks normal, but the usual sites are swapped for Facebook, Yelp, directories and forums, and your site disappears, so a keyword shows a sudden drop that is not real. Turn this on to have SEO Utils fetch such a result once more and label it if it still looks wrong. It works with every scrape method and is **off by default**; when it is off, nothing changes. See [Possibly Poisoned Results](#possibly-poisoned-results) for how it works.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f56af4b2a43be85d970fe5aceb30d15ad68a4f38%2Forganic-rank-tracker-recheck-poisoned-toggle.png?alt=media" alt="The Re-check results that look poisoned switch on the SERP Collection tab, with its help text open"><figcaption><p>Hover the (?) to read what the setting does and what a re-check costs</p></figcaption></figure>

{% hint style="warning" %}
**Extra cost:** each re-check is one more request, and only keywords whose result looks suspicious are re-checked. The (?) quotes about $0.0006 per keyword for DataForSEO's standard queue at depth 10. A re-check uses your report's own depth, so a deeper report costs more. With My Own IP or Proxies there is no DataForSEO charge, only the extra request.
{% endhint %}

**SERP collection method details**

Just like the [SERP Clustering tool,](/guide/serp-clustering) you can also select the method to scrape the SERP data. There are 3 options:

* **My Own IP:** Uses your machine’s IP to scrape SERP data. This is suitable if you’re tracking only a few keywords. For larger keyword sets, consider using the Proxies or SERP API method.
* **Proxies:** The best choice when tracking millions of keywords per month. [Click here to learn how to set up a proxy](/guide/how-to-use-proxies).
* **SERP API:** [**DataForSEO**](/guide/seo-data-source#what-is-dataforseo)**:** Ideal for tracking hundreds to thousands of keywords per month. You’ll be charged an additional $0.60 per 1,000 keywords via the SERP API, with a pay-as-you-go model. It’s affordable and easy to get started.

{% hint style="warning" %}
**Important:** To use the SERP API, you must have your own DataForSEO account. [Renting API key services](https://help.seoutils.app/guide/rent-dataforseo-api-key) isn't viable because DataForSEO restricts certain endpoints that I utilized to implement the Queue mode. If multiple users rely on a rented API key from my account, it will slow down the process for everyone. For the quickest results, using your own DataForSEO account is the best approach.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3dbcce8d73fced7c3de8f30f3e46fcfdc2152bf4%2FXnapper-2024-09-30-09.48.41.png?alt=media" alt="" width="563"><figcaption><p>Select a suitable Scrape SERP method.</p></figcaption></figure>

**My Own IP and Proxies include additional controls for collection speed and retries.**

**Workers (Proxies):** Select the total number of workers to scrape SERP data. The more workers you choose, the faster the process will be, but it will also require more CPU power and proxy quality. You can enter 1-50 workers.

**Request delay:** Enter the number of seconds you wish to have between each request to scrape SERP data for keywords. The more delay time you set, the slower the process will be, but it will help you avoid being blocked by Google. Set '0' to scrape SERP data without any delay.

**Back-off Time (Proxies):** Enter the number of seconds you wish to wait before retrying the failed scraping request. SEO Utils retries the request up to 3 times before skipping a keyword. The more back-off time you set, the slower the process will be, but it will help you avoid being blocked by Google. Set '0' to use the default back-off time.

{% hint style="info" %}
My favorite setting when using rotating residential proxies is:

* Workers: 10.
* Request delay: 1.
* Back-off time: 1 (sometimes 2 if I notice many failed requests).
  {% endhint %}

#### Page HTML tab

SEO Utils can store the rendered HTML of the actual pages found in the ranking results. This is different from saving Google's search results page: the capture contains the content and markup of your page, or a tracked competitor's page, so you can investigate what changed around a ranking gain or loss.

This feature is off by default and works with every **SERP Collection** method.

{% stepper %}
{% step %}
**Open the Page HTML tab**

In the add or edit tracker form, select **Page HTML**, then turn on **Capture Ranked Page HTML**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FqiVU8ORBWn1A2Liee04O%2FXnapper-2026-08-15-08.53.35.png?alt=media&amp;token=5f874f1c-b50f-48a4-9f81-09f073bd38db" alt=""><figcaption><p>Capture Ranked Page HTML settings in the Page HTML tab</p></figcaption></figure>
{% endstep %}

{% step %}
**Choose which pages to capture**

Set **Pages to Capture** to one of these options:

| Option                                    | What SEO Utils captures                                                   |
| ----------------------------------------- | ------------------------------------------------------------------------- |
| **Target domain only** (default)          | Ranked pages from the report's target domain                              |
| **Target domain and tracked competitors** | Ranked pages from the target domain and competitors added to this tracker |

Competitor capture applies only to domains that are already listed as tracked competitors.
{% endstep %}

{% step %}
**Set the retention period**

Use **Keep Captured HTML** to control local storage:

* Enter **0** (default) to keep captured HTML forever.
* Enter a positive number of days to remove older captures automatically in the background.
  {% endstep %}
  {% endstepper %}

{% hint style="info" %}
Page HTML is collected in a separate background queue after the rank results are saved. A page that disappears from the results is captured once more when the loss is observed. When an earlier capture exists, this lets you compare its last ranked version with the version collected when it became lost.
{% endhint %}

{% hint style="warning" %}
Rendered HTML can use significant disk space when you track many pages or competitors. Set a retention period if you do not need to keep the complete history forever.
{% endhint %}

#### Schedule tab

**Rerun Every:** Specify how often you want the tracker to run, in days. For example, set it to 1 for daily runs, 7 for weekly runs, or 0 for on-demand runs. The value can range from 0 to 30. Choose the frequency that fits your project budget and requirements.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-174a83549ee8525860675855f0254efb141ff800%2FXnapper-2024-09-30-09.38.42.png?alt=media" alt="" width="563"><figcaption><p>"Rerun Every" field.</p></figcaption></figure>

{% hint style="info" %}
You will need to **leave the SEO Utils app open** for scheduled runs to occur.
{% endhint %}

{% hint style="info" %}
**New in** [**v2.0.0**](https://help.seoutils.app/changelog#v2.0.0): You can now control **when** scheduled runs happen — set a time window, days of the week, and a timezone. This is especially useful for local businesses, where SERP results during open hours are the most representative.
{% endhint %}

**Schedule to run from / to:** Set a daily time window for scheduled runs. When a run is due, the tracker waits and starts inside this window. Pick the tracked business's open hours for the most representative results, or leave both fields empty to run at any time. The window must be at least 30 minutes wide.

**Run on any days:** Keep this on to run on whichever day the tracker is due. Toggle it off to select specific days of the week — when a run is due on another day, it waits for the next selected day.

**Timezone:** The timezone used to evaluate the time window and the selected days. Type to search for any timezone (for example, the business's own timezone). Leave it empty to use your computer's timezone.

**How scheduling works:** a scheduled run starts when all three conditions are true:

* The "Rerun Every" interval has passed since the last run.
* The current time — in the selected timezone — is inside the time window.
* Today is one of the selected days (when "Run on any days" is off).

The next run then counts from the day the tracker actually ran. For example, a weekly tracker with only Monday–Friday selected that becomes due on a Sunday waits until Monday — and from then on, it keeps running on Mondays.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FUwtB7dP2tYK37SYrw89T%2FXnapper-2026-08-04-14.33.43.png?alt=media&amp;token=2a9105df-138c-47ed-8ebf-790d2b3a918b" alt=""><figcaption><p>Schedule section with the time window, "Run on any days" toggle, weekday selection, and timezone picker</p></figcaption></figure>

{% hint style="success" %}
The report page shows exactly when the next run will start — for example, *"Next run: Aug 12 between 09:00–17:00 (America/Chicago)"*. If you create a tracker outside its window, the first scan also waits for the window instead of starting right away.
{% endhint %}

{% hint style="info" %}
**Good to know:** the window controls when a **new** run starts. If a run cannot finish all keywords (for example, a request failed midway), the tracker completes the unfinished keywords shortly after, even outside the window. Switching a tracker to on-demand (Rerun Every = 0) clears its window, days, and timezone settings.
{% endhint %}

Once all the fields are set up, please click the Add Tracker button.

### Manage Tracker: Keywords, Competitors, Annotations, Snapshots

At the top of the page, you will find all the essential information about the report, including the location, language, search engine, total keywords, and competitors. You can also hover over the updated date to see when the next run is scheduled.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a5c4e49579a272c93e1e813ed141933dbd0c6942%2FXnapper-2024-09-30-10.01.26.png?alt=media" alt=""><figcaption><p>Basic information of the report.</p></figcaption></figure>

{% hint style="info" %}
You can always edit the report by clicking the pencil icon button.
{% endhint %}

#### Manage keywords & tags

To manage your keywords, simply click on the keyword count. This will redirect you to a page where you can add or remove keywords as needed.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4d7369cfa197f5c727b638b674f51860bf1304f2%2FXnapper-2024-09-30-10.16.30.png?alt=media" alt=""><figcaption><p>Manage keywords.</p></figcaption></figure>

You can update tags for several keywords at once by selecting them and using the "Update Tags" bulk action.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a15a98d1f0b6fb513efa485d70be4038b4bcf833%2FXnapper-2024-09-30-10.18.34.png?alt=media" alt="" width="563"><figcaption><p>Update tags for multiple keywords.</p></figcaption></figure>

You can instruct SEO Utils to check rankings immediately after adding keywords by toggling the “**Rerun Tracker After Adding Keywords**” option. If left off, the tool will check the rankings of new keywords during the next scheduled run.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-784c25b866525332d28c18baa1675a98ce778153%2FXnapper-2024-09-30-10.51.09.png?alt=media" alt=""><figcaption><p>Adding new keywords modal.</p></figcaption></figure>

By adding tags for keywords, you’ll be able to tag and filter keywords for more efficient tracking and organization.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e7783ca168dadd36b5e0940dd6725e1639eed427%2FXnapper-2024-09-30-10.24.49.png?alt=media" alt=""><figcaption><p>Filter keywords by tags</p></figcaption></figure>

#### Check Keyword Metrics & Analyze SERP Data

To check keyword metrics *(Search Volume, CPC, KD, etc)*, you can simply select the keywords you want to check and run the bulk action: Check Keyword Metrics.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0eec417ded1b0ca2dd78e4a32e9dedd46d49fc4c%2FXnapper-2024-11-13-20.31.46.png?alt=media" alt=""><figcaption><p>Check keyword metrics for multiple keywords</p></figcaption></figure>

You can also click Analyze SERP bulk action, to pull valuable insights on the top 10-100 URLs, including:

* Backlink count for each URL.
* Total keywords each URL ranks for.
* Estimated traffic each URL receives.
* Domain rating (DR) and URL rating (UR) of each URL.

These insights empower you to assess competitor strengths and uncover opportunities to boost your own rankings.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a7ebbafeb5f6e66ced0764e9dab329cd355d3040%2FCleanShot%202024-11-13%20at%2020.35.50%402x.png?alt=media" alt=""><figcaption><p>SERP analysis</p></figcaption></figure>

{% hint style="info" %}
You can also **export SERP data** of all keywords to view more metrics: Referring IPs, Referring Pages, Referring Main Domains, Broken Backlinks, etc
{% endhint %}

#### Map External Keyword Data

{% hint style="info" %}
**New in** [**v1.33.4**](https://help.seoutils.app/guide/pages/FYHJNu9cAi74Qc90ALo7#v1.33.4): You can now import external keyword metrics and tags from Excel or CSV files to enrich your keyword data.
{% endhint %}

The Map Keyword Data feature allows you to import external data sources to enhance your keyword tracking with:

* **Search Volume**: Monthly search volume for keywords
* **CPC (Cost Per Click)**: Average cost per click data
* **KD (Keyword Difficulty)**: Competitive difficulty scores
* **Search Intents**: User intent classification (informational, navigational, transactional, commercial)
* **Tags**: Custom labels for organizing keywords
* **Weight**: How much each keyword counts in the report's averages (see [Keyword weights](#keyword-weights))

To use this feature:

1. Click on the keyword count to go to the keywords management page
2. Click on "**Map Keyword Data**" from the "3 dots" action dropdown menu

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3143924b0ef79bb6fe472f7741a59c5318469972%2FXnapper-2025-07-30-16.51.45.png?alt=media" alt=""><figcaption><p>Map Keyword Data bulk action</p></figcaption></figure>

4. In the modal, select your Excel or CSV files containing the keyword data
5. Map the columns from your file to the appropriate data types (Keyword, Volume, CPC, Intent, Tags, Weight)
6. Click "Import Data" to sync the external metrics with your keywords

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c609315637f6eb1e7f46780cab7d18cc4d766147%2FXnapper-2025-07-30-16.52.45.png?alt=media" alt=""><figcaption><p>Map Keyword Data modal interface</p></figcaption></figure>

{% hint style="success" %}
**Important notes:**

* Keywords are matched case-insensitively by default (you can preserve case if needed)
* External metrics will override any existing internal data
* Tags should be comma-separated in your file (e.g., "seo, analytics, tools")
* Weights must be whole numbers from 0 to 1000 ("50%" reads as 50); an empty, fractional or invalid weight keeps the keyword's current weight
* Multiple files can be imported at once if your data is spread across different sources
  {% endhint %}

**Example Template**: Download this [sample Google Sheets template](https://docs.google.com/spreadsheets/d/13kxL8YpwUwifNlWm6ULETl1D7_cU4SUT/edit?usp=sharing\&ouid=113491029958464815726\&rtpof=true\&sd=true) to see the recommended format for importing keyword data.

#### Delete Keywords by Text

To delete specific keywords without searching through the table:

1. Click on the keyword count to go to the keywords management page
2. Click on the dropdown menu (three dots) in the page header
3. Select "**Delete Keywords**"
4. Enter or paste keywords to delete (one per line or comma-separated)
5. Click "Delete" to remove matching keywords

Only exact matches will be deleted. After deletion, you'll see a summary of how many keywords were deleted and how many were not found.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FrLB3AY6rds8RLe87cF4B%2FXnapper-2026-01-08-18.33.06.png?alt=media&amp;token=d34c7a55-f5d1-472b-a954-05b55747de1c" alt=""><figcaption><p>Bulk delete keywords by simply pasting a list of keyword names.</p></figcaption></figure>

{% hint style="warning" %}
Deleting keywords will permanently remove all historical ranking data for those keywords. This action cannot be undone.
{% endhint %}

#### Keyword weights

Give the keywords that matter most to a client more say in the report. Each keyword has a weight from 0 to 1000 (default 100). Average position, ranking coverage and visibility count every keyword by its weight: a keyword at 300 counts three times as much as one at 100, and a keyword at 0 (**Track only**) is still tracked but no longer counts.

For example, three keywords rank #1, #1 and #3:

| Keyword                | Position | Weight         |
| ---------------------- | -------- | -------------- |
| harbor and pine coffee | 1        | 100            |
| french press ratio     | 1        | 0 (Track only) |
| coffee subscription    | 3        | 300            |

Counted equally, the average position is 1.67. With these weights it is (1 × 1 + 3 × 3) ÷ (1 + 3) = **2.50**, because the keyword the client cares about most is the one ranking lower.

**Set the weight of one keyword**

{% stepper %}
{% step %}

#### Open the weight picker

Click the keyword count to open the keywords management page, then click the number in the **Weight** column.
{% endstep %}

{% step %}

#### Pick a weight

Choose a level, or type any whole number from 0 to 1000 and click **Set**.

| Level          | Weight |
| -------------- | ------ |
| Full (default) | 100    |
| High           | 75     |
| Medium         | 50     |
| Low            | 25     |
| Minimal        | 10     |
| Track only     | 0      |

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ac4de19d15a43b48d5345798bebfc4a0953f6f61%2Forganic-rank-tracker-keyword-weight-picker.png?alt=media" alt="The Keywords page with the weight picker open on a keyword"><figcaption><p>Click a keyword's weight (1), pick a level (2), or type a custom weight (3).</p></figcaption></figure>
{% endstep %}
{% endstepper %}

**Set the weight of several keywords**

Select the keywords, then choose **Bulk Actions > Set Weight**. Pick a level or type a number, and click **Set Weight**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-58f596057adb6b8e5d1b7ae37f5a9297614ad782%2Forganic-rank-tracker-keyword-weight-bulk.png?alt=media" alt="The Bulk Set Weight dialog with the Low level selected"><figcaption><p>Pick one weight for every selected keyword (1) and click Set Weight (2).</p></figcaption></figure>

You can also import weights from a file with [Map Keyword Data](#map-external-keyword-data), and cloning a tracker copies every keyword's weight.

**Where weights show**

The Overview chart, the [Competition Map](#competitors-discovery-tab), PDF/HTML exports, client reports and the Organic Rank Tracker dashboard all use the weights. When their keywords do not all share one weight, they show a **Weighted** badge. The Top 3/10/20/100 counts in the Rankings Distribution tab stay plain keyword counts.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7c4fd535fa2f08b8f0bcb66598fd96bf7453d80b%2Forganic-rank-tracker-keyword-weight-chart.png?alt=media" alt="The Overview chart with the Weighted badge"><figcaption><p>The Weighted badge (1) tells readers the averages count keywords by their weights.</p></figcaption></figure>

{% hint style="success" %}
Filter the Overview by a tag to see the weighted average of one group, such as your money keywords.
{% endhint %}

{% hint style="info" %}
On a date when every ranked keyword is Track only, the chart shows "No weighted keywords" for that date instead of a value. If every keyword in the view is Track only, the chart has nothing to show.
{% endhint %}

When a report's weights differ, the keyword table on the Overview tab also shows a **Weight** column. Sort by it to see the keywords that count most first.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b718471e2d7c2354ebd3d1acfa73f31b145f4824%2Forganic-rank-tracker-keyword-weight-column.png?alt=media" alt="The Overview keyword table with the Weight column"><figcaption><p>The Weight column (1). A Track only keyword shows empty bars and 0 (2).</p></figcaption></figure>

{% hint style="warning" %}
A client report shows the weights as they were when you published it. After you change weights, publish the report again so your client sees the new numbers.
{% endhint %}

#### Manage competitors

To manage your competitors, click on the competitors count. This will redirect you to a page where you can add or remove competitors as needed.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b8c99907fe8e3ba51104b922f2cb55570ff4cf68%2FXnapper-2024-09-30-10.32.00.png?alt=media" alt=""><figcaption><p>You can add multiple competitors at once.</p></figcaption></figure>

{% hint style="info" %}
**Tracking Competitor Business Names in Local Pack**

You can also track competitor business names in Google's Local Pack by entering them in this format:`domain.com|Business Name`

For example: `happylambhotpot.com|Happy Lamb Hot Pot`

This allows you to monitor both organic rankings and Local Pack positions for your competitors, giving you a complete view of the competitive landscape.
{% endhint %}

Once you’ve added competitors, you’ll be able to filter them using the Competitors Filter for more focused analysis.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4409d2e8c5f620f286d1aa637c0959426186a407%2FXnapper-2024-09-30-10.33.14.png?alt=media" alt=""><figcaption><p>The table and chart will show the data for the selected competitors.</p></figcaption></figure>

{% hint style="success" %}
SEO Utils automatically populates keyword ranking data for newly added competitors starting from **the date you originally created the tracker**, not just from the date you add competitors. This ensures you don't lose any historical data.
{% endhint %}

#### Manage snapshots

Each time the rank tracker runs, SEO Utils creates a snapshot containing all ranking data for that date. You can manage these snapshots to clean up old data or remove unwanted entries.

To access the snapshots management page, click on the "Snapshots" link in the report header, or navigate to **Rank Trackers > \[Your Report] > Snapshots**.

From this page, you can:

* **View all snapshots** with their date and ID
* **Delete snapshots** you no longer need

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FlWHbp2whhM9lNkfvuXiH%2FXnapper-2025-12-03-10.24.25.png?alt=media&amp;token=719d6b53-ffd7-450c-9f72-d774367088cd" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="warning" %}
**Important:** Deleting a snapshot will permanently remove all associated position data for that date. This action cannot be undone.
{% endhint %}

### View Rank Tracker Report in Each Tab

#### Overview Tab

In this tab, you’ll be able to view the average ranking. The line chart displays how your keywords and competitors perform over time within a specified date range.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7dd64f8cb585f6859c1fa0dd4ba8a8a66758c234%2FXnapper-2024-09-30-10.39.25.png?alt=media" alt=""><figcaption><p>Use the Date filter to see the average ranking of all keywords overtime.</p></figcaption></figure>

The below table also reflects the changes when you update the filters.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-50abba783011cc24634db0267eb13e595385ae36%2FXnapper-2024-09-30-10.41.42.png?alt=media" alt=""><figcaption><p>This table shows all keywords that you added to the report.</p></figcaption></figure>

In the screenshot above, you’ll see that the keyword *“hạt điều”* ranked at position **90** on Sep **24 (From Date)** and improved to position **84** on **Sep 30 (End Date)**, showing a gain of 6 positions. The green badge highlights this positive change in the keyword’s ranking. Conversely, if a keyword declines in ranking, the badge will appear red.

{% hint style="success" %}
**Important to know**

* If a keyword ranks outside the top 100, SEO Utils will display its position as “100+” in the position column.
* If a keyword wasn’t added by a selected date, SEO Utils will display “**—**”, indicating no position data is available for that date.
* If a keyword is outside the top 100 on the start date and then ranks within the top 100 by the end date, SEO Utils will display a green “<mark style="color:green;">**New**</mark>” badge. Conversely, if a keyword drops out of the top 100 by the end date, it will show a red “<mark style="color:red;">**Lost**</mark>” badge.
* A keyword can rank for multiple pages within the same domain. SEO Utils only displays the best position. To view other positions, please switch to the [Pages tab](#pages-tab).
* When your business appears in **Google's Local Pack (top 3 local results)**, the position shows your organic rank first, with a green 📍 badge for your Local Pack position beside it (for example **9 📍1**). See [Local Pack Tracking](#local-pack-tracking).
  {% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-349c8bb889f64414be1bf4ee1d7bb017877e3595%2FXnapper-2025-06-19-12.12.38.png?alt=media" alt="" width="375"><figcaption><p>Google's Local Pack indicator</p></figcaption></figure>

{% hint style="success" %}
**Pro Tips**

To see your keyword ranking performance over the **last 7 days**, set the End Date to the current date and the From Date to 7 days ago. You can then observe keyword performance by examining the **Diff column**.
{% endhint %}

You can also click on a specific keyword to view its ranking performance over time.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-65bd277d6e2d7df850a1e2a4c2f33de9f04e97ff%2FXnapper-2024-09-30-11.11.53.png?alt=media" alt=""><figcaption><p>View data for a keyword.</p></figcaption></figure>

If you'd like to view the SERP data for a keyword, simply click on the SERP button next to it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-775c87e271bc3057f79dba5bd751e21c167e1357%2FXnapper-2024-09-30-11.20.21.png?alt=media" alt="" width="563"><figcaption><p>View SERP data of a keyword.</p></figcaption></figure>

You can view the historical SERP data by using the Date filter.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4a468d2f79958077fa9c3b2288a643023bb18640%2FXnapper-2024-11-13-20.18.38.png?alt=media" alt=""><figcaption><p>View historical SERP data</p></figcaption></figure>

#### SERP Features Tracking

SEO Utils now tracks various SERP features that appear alongside organic results. The **SF** (SERP Features) column shows how many special features appear for each keyword.

**Tracked SERP Features Include:**

* **Local Pack** - Top 3 local business results with map
* **Featured Snippet** - Answer box at the top of results
* **Knowledge Panel** - Information box about entities
* **AI Overview** - AI-generated summaries
* **People Also Ask** - Related questions section
* **Shopping** - Product listings
* **Video** - Video carousel
* **News** - News articles
* **Images** - Image pack
* And more...

Click on the number in the SF column to see which specific features appear for that keyword.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-71c6a186bf0dfdd8d3082e84f25fce44e4facfea%2FXnapper-2025-06-19-12.19.53.png?alt=media" alt="" width="375"><figcaption><p>SERP features for keyword.</p></figcaption></figure>

You can also use the SERP Features filter to find keywords that trigger specific features, helping you optimize for these valuable SERP positions.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c484779a0551492b5195208fb3893240d45b6bfa%2FXnapper-2025-06-19-12.21.03.png?alt=media" alt=""><figcaption><p>Filter by SERP Features.</p></figcaption></figure>

{% hint style="success" %}
**Local Pack Advantage**

When your business appears in the Local Pack, it shows as a green 📍 badge beside your organic rank. These positions are extremely valuable as they:

* Appear at the very top of search results
* Include rich information (reviews, address, hours)
* Link directly to your Google Maps listing
* Drive both online visibility and foot traffic
  {% endhint %}

#### Local Pack Tracking

When a report or a competitor has a **Business Name**, SEO Utils tracks its Local Pack position separately from its organic rank. They come from two different lists on the results page, so a Local Pack position never replaces the organic rank.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-83c791fac8c2e617c52c65e460c5f0c953cd88f7%2Forganic-rank-tracker-local-pack-table.png?alt=media" alt="Keyword table with organic ranks, green Local Pack badges and the Local pack column"><figcaption><p>The organic rank with the Local Pack position beside it (1), and the Local pack column (2)</p></figcaption></figure>

1. **Position cells** show the organic rank (a number, or NR when the site does not rank organically), with a green 📍 badge for the Local Pack position on days the business was in the map results.
2. The **Local pack** column shows the Local Pack position on the last day of the selected range, and its change since the first day. Click the header to sort by it. Without a position, it reads:
   * **Not in pack**: Google showed a Local Pack, but your business was not in it.
   * **No pack**: Google showed no Local Pack for the keyword that day.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-90b868c4b0e2ca2ded5df4ad3246d82944871e95%2Forganic-rank-tracker-local-pack-summary.png?alt=media" alt="Local pack filter in the toolbar and the Local pack summary above the chart"><figcaption><p>The Local pack filter (1) and the Local pack summary (2)</p></figcaption></figure>

1. Use the **Local pack** filter to list only the keywords that are **In pack**, **Not in pack** or have **No pack** on the last day of the range.
2. The **Local pack** summary shows how many keywords put your business in the map results, and their average Local Pack position, with the change since the first day.

{% hint style="info" %}
Average Position, Ranking Coverage, Visibility Score, Rankings Distribution, Keyword Fluctuation and Insights count **organic results only**. A Local Pack position appears in the Local pack column and summary instead, so it does not lift your averages.
{% endhint %}

Click a keyword to open its chart. The **Pack** row under the chart shows the Local Pack position on each date; an empty date means the business was not in the pack.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6cc9a68f95b0aa696f9d087b053148215159c5f0%2Forganic-rank-tracker-local-pack-chart.png?alt=media" alt="Keyword chart with a legend above it and a Pack row of Local Pack positions under it"><figcaption><p>The legend (1) explains each mark; the Pack row (2) shows the Local Pack position on each date</p></figcaption></figure>

#### PAA Source Tracking

When **PAA Click Depth** is enabled on the report (see the configuration section above), SEO Utils detects whether your target domain — or any of your competitors — is featured as a source inside Google's People Also Ask box. This is a separate signal from organic ranking and from the "PAA box appeared on the SERP" SF flag.

**The purple PAA badge**

In the Overview tab, a small purple PAA badge appears next to the diff cell whenever the corresponding domain has at least one PAA source appearance for that keyword. The number on the badge is the appearance count.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FdMbnAm8LHlzV8rO1Fb2M%2FXnapper-2026-05-03-15.02.50.png?alt=media&amp;token=04d70b2e-8bd5-4792-95a9-9be42e01cf69" alt=""><figcaption><p>Purple PAA badge in the Overview tab indicating the domain is featured as a source inside the People Also Ask box</p></figcaption></figure>

Hover the badge for a tooltip showing the count, or click it to open the SERP slideover with the full list of PAA questions and source URLs grouped by domain.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fe7h1L7HYZmjrTV4if3i8%2FXnapper-2026-05-03-16.28.06.png?alt=media&amp;token=72fa9870-4d19-4c9e-a71d-1cd84bc21c26" alt=""><figcaption><p>SERP slideover panel listing every PAA appearance — questions, source URLs, and the matched domain</p></figcaption></figure>

**Filtering by PAA presence**

A new **"\[Your Domain] in PAA"** filter sits next to the SERP Features filter. Two values:

* **Featured in PAA** — keywords where your target domain has at least one PAA source appearance in the selected date range.
* **Not featured in PAA** — keywords where your target domain has zero PAA source appearances. Useful for finding **PAA opportunities**: the box exists for the keyword, but you're not the source — so you can write content targeting those questions.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FtXYjZjJoa59MMx0OELN8%2FXnapper-2026-05-03-16.29.01.png?alt=media&amp;token=528a49e1-0cb1-4659-89af-57823f254cfe" alt=""><figcaption><p>"Featured in PAA" / "Not featured in PAA" filter alongside the existing SERP Features filter</p></figcaption></figure>

{% hint style="info" %}
**How matching works:** SEO Utils normalizes the source domain returned by DataForSEO (stripping the `www.` prefix) before matching against your tracked domains. So adding `kentucky.com` as a competitor will match PAA sources Google attributes to `www.kentucky.com`. Real subdomains like `blog.example.com` still require **Include Subdomains** to be enabled on the report.
{% endhint %}

{% hint style="warning" %}
**Reality check on PAA sources:** Google increasingly answers PAA questions with AI Overview content instead of citing a single source URL. When this happens, DataForSEO returns the question but no source domain — so no badges fire even though the PAA box appeared. This is a Google trend, not a tracking gap on our side. Coverage varies by query.
{% endhint %}

#### Pixels From Top Display

When **Track Pixels From Top** is enabled on the report, every rank cell in the Overview tab shows a small **px** value next to the position number. This is the vertical pixel offset of the snippet from the top of the SERP — lower numbers mean better real-world visibility.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FYsiOHJE3T3h1BT545kfp%2FXnapper-2026-05-12-14.41.41.png?alt=media&amp;token=dd3bb76f-e8e6-4689-851a-1372e85aa1f7" alt=""><figcaption><p>Position cells showing the px value next to the rank number — e.g. "1 / 182px" or "2 / 750px"</p></figcaption></figure>

A dedicated **Pixels Diff** column also appears alongside the existing **Diff** column, showing how the pixel offset changed between the From and End dates. Color coding follows the same convention as rank diff:

* **Green** — the snippet moved up the page (fewer pixels from top) → improved visibility.
* **Red** — the snippet moved down the page → worse visibility, even if organic rank stayed the same. This is what usually happens when Google adds new SERP features above your result.
* **New** / **Lost** — the snippet appeared for the first time or disappeared between the two dates.

Hover the px value to see the exact pixel offset in a tooltip.

{% hint style="info" %}
**Pixel data for competitors works automatically.** When you add a competitor to a tracker with Track Pixels From Top enabled, SEO Utils backfills pixel offsets for that competitor across every existing snapshot — no re-scrape needed, no extra cost. The pixel data was already captured in the SERP cache during the original scrapes; adding a competitor just reads it back out for that domain. Each competitor row in the Overview grid gets its own Pixels Diff column.
{% endhint %}

{% hint style="warning" %}
**Not every position gets a pixel value.** DataForSEO only emits rectangle coordinates for snippets that were laid out within the rendered viewport. Results deeper on the page (typically beyond position \~10–15) and certain SERP item types may have no pixel measurement attached — the column simply shows the rank without a px value. This isn't a bug; the data just isn't part of DataForSEO's response.
{% endhint %}

You can also switch to the **SERP Comparison** tab. That tool allows you to instantly view side-by-side SERP results for any keywords to easily spot trends and competitors.

{% embed url="<https://drive.google.com/file/d/1yshf84UURl5w_nQiVRWRLP3Y70IWqLEu/view?usp=sharing>" fullWidth="false" %}
SERP Comparison tool in action
{% endembed %}

#### Possibly Poisoned Results

With [Re-check Results That Look Poisoned](#serp-collection-tab) on, every keyword's result is judged against its **usual sites**: the domains in its top 10 on at least 2 of its last 3 runs. A keyword with fewer than 2 earlier runs is not judged.

If fewer than half of the usual sites are left, SEO Utils fetches the keyword once more through the same route (My Own IP, Proxies or DataForSEO), for the same market and your report's depth. Then:

| The re-check shows                                           | What is stored                                     | Label                 |
| ------------------------------------------------------------ | -------------------------------------------------- | --------------------- |
| The usual sites again                                        | The re-check's result: the first page was poisoned | None                  |
| The same new sites as the first fetch                        | The result: it is a real change                    | None                  |
| Still wrong and different from the first fetch, or no answer | The keyword's **previous position**                | **Possibly poisoned** |

**Where you see the label**

* **Tables.** In the Overview and Insights tabs, the kept position is grey with an amber **Possibly poisoned** chip. Hover it to see what the page showed, for example "Only 1 of 8 usual sites in the top 10", "Your site was missing from the top 10" and "3 facebook.com results", and that the previous position is kept.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e6b19e6716b1e6efb0faf0f01dda50e25ec7dfd7%2Forganic-rank-tracker-possibly-poisoned-chip.png?alt=media" alt="A keyword with the Possibly poisoned chip and its tooltip listing what the results page showed"><figcaption><p>The chip and its tooltip</p></figcaption></figure>

* **Chart.** Expand a keyword to see its Positions chart. The labelled day is a grey point, and the legend explains it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-474642c049e0767c1751a30458ed9c7b21991a55%2Forganic-rank-tracker-possibly-poisoned-chart.png?alt=media" alt="The keyword chart with a grey point on the last day, the chip above it and the legend"><figcaption><p>The grey point on the chart</p></figcaption></figure>

* **Run status.** After a run, the summary says how many keywords looked poisoned and how each ended: recovered by a re-check, confirmed as a real change, or kept at its previous position.
* **Run log.** **View log** in the report's **⋯** menu has one plain line per re-checked keyword, such as:

```
'cold brew coffee beans' looked poisoned (only 1 of 8 usual sites; the tracked site was missing; 3 facebook.com results; 1 yelp.com result): the re-check also looked wrong — the previous position was kept and labelled Possibly poisoned.
```

A labelled day counts as no drop: it shows the kept position, so it does not appear as a fall in the **Diff** column, and [Trending Down](#insights-tab), Pogo Sticking and Flickering skip that day.

{% hint style="info" %}
**Good to know:** client portal reports and exports show the kept position without the **Possibly poisoned** label.
{% endhint %}

#### Rerun the Tracker

You can rerun the tracker at any time. This is particularly useful when you need to check the keyword ranking on-demand, without relying on a scheduled run.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2df20f3319e12a251535b85b58c57267a39ddb31%2FXnapper-2024-09-30-11.24.42.png?alt=media" alt="" width="373"><figcaption><p>Click the button to rerun the tracker.</p></figcaption></figure>

{% hint style="success" %}
When you re-run the tracker, SEO Utils only scrapes SERP data for keywords missing current date information. This helps save time and costs.
{% endhint %}

#### Run Partial Scan

For advanced users who need more control over which keywords to scan, SEO Utils offers a **Partial Scan** feature. This allows you to select specific keywords and update only their rankings, while preserving the existing ranking data for other keywords.

**How to run a partial scan:**

1. Navigate to the [Keywords management page](#manage-keywords-and-tags) by clicking on the keyword count
2. Select the specific keywords you want to scan
3. Click the "Run Partial Scan" bulk action

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5562398d0fe5c1ddb1757c4d7e85fd40a4c8b33c%2FXnapper-2025-11-10-22.09.47.png?alt=media" alt=""><figcaption><p>Select keywords and run partial scan</p></figcaption></figure>

**Understanding Stale Data:**

When you run a partial scan, only the selected keywords get fresh SERP data. Keywords that weren't included in the scan will show their last known positions with a **stale data indicator** (⚠️ icon).

Hovering over the stale indicator shows when that keyword was last scanned. This helps you identify which keywords have current data versus which ones are showing historical positions.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a97c7589cd98cc22646a83581c63805dd696bed3%2FXnapper-2025-11-10-22.12.13.png?alt=media" alt=""><figcaption><p>Stale data indicator showing when keyword was last scanned</p></figcaption></figure>

{% hint style="warning" %}
**Important: Partial Scan Best Practices**

We recommend only using partial scans when you have **disabled the schedule** (set "Rerun Every" to 0 days).

Here's why: If you have scheduled auto-runs enabled and you run a partial scan on only some keywords, the next scheduled run will automatically scan all keywords—including the ones you didn't include in your partial scan. This could lead to unexpected SERP API costs or proxy usage.
{% endhint %}

#### Annotations

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-551bc906c8e5261b6ecf4bf635449a73b0d16069%2FXnapper-2024-09-30-11.27.39.png?alt=media" alt=""><figcaption><p>Annotations</p></figcaption></figure>

This feature let you highlight key events or changes in your data. For instance, if you’ve just wrapped up a major content audit, you can mark that event on the chart to track its impact on your rankings.

{% hint style="info" %}
When adding new keywords, SEO Utils creates a **System** annotation to indicate the date you added those keywords.
{% endhint %}

You can watch this video to see how to manage annotations.

{% embed url="<https://drive.google.com/file/d/1Mmk8nCnp6t4J0mYdYMg4yIPmnRYQDKlS/view?usp=sharing>" %}
How to manage annotations.
{% endembed %}

#### Pages Tab

You can see all the ranked pages in this tab. Like the Overview tab, you can filter by **Dates** or **Competitors**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f8585e4f315c2c53984b82790dd4192e1259caa0%2FXnapper-2024-09-30-13.30.49.png?alt=media" alt=""><figcaption><p>View all ranked pages with filters</p></figcaption></figure>

The **Status** column displays the ranking status of each page. You can filter based on this column. This is particularly useful for identifying good or bad performing pages within a specific date range.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fb7ea6cbcbe0e06882edb7a0daa5b6d332eb09ad%2FXnapper-2024-09-30-13.40.20.png?alt=media" alt="" width="375"><figcaption><p>Extract new ranking pages or pages with improved average positions.</p></figcaption></figure>

You can also filter the pages with the status "Unchanged" to improve their ranking.

{% hint style="info" %}
**Important to know**

* <mark style="color:green;">**New**</mark>: Keywords that have no ranking on the From date but have a ranking on the End date
* <mark style="color:red;">**Lost**</mark>: Keywords that have a ranking on the From date but no ranking on the End date
* <mark style="color:green;">**Improved**</mark>: Keywords that have moved up in ranking position between the From date and End date
* <mark style="color:red;">**Declined**</mark>: Keywords that have moved down in ranking position between the From date and End date
* **Unchanged**: Keywords that have maintained the same ranking position on both the From date and End date
  {% endhint %}

The **Keyword Count** column indicates how many keywords the page is ranking for. You can also click on the down arrow icon button next to the page URL to view all ranking keywords of that page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7a8945bb3897ab5c209ffd8c4c5523d8f7d75fbe%2FXnapper-2024-09-30-13.51.44.png?alt=media" alt=""><figcaption><p>This page has improved by 26 from September 23 to September 30.</p></figcaption></figure>

**View Ranked Page HTML Changes**

When **Capture Ranked Page HTML** is enabled, the Pages tab shows an HTML action below each page URL. The label reflects the available history:

| Action                   | Meaning                                                           |
| ------------------------ | ----------------------------------------------------------------- |
| **View HTML changes**    | Two or more completed captures are available                      |
| **View captured HTML**   | One completed capture is available                                |
| **HTML capture pending** | The first capture is still running                                |
| **View capture error**   | The latest capture failed; open it to see the failure information |

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-23706452980da93a610748dc3288e115c241b73c%2Fplaceholder.png?alt=media" alt=""><figcaption><p>Ranked-page HTML actions below page URLs in the Pages tab</p></figcaption></figure>

{% stepper %}
{% step %}
**Open a page's HTML history**

Click **View HTML changes** or **View captured HTML** below the page URL. SEO Utils opens **Ranked Page HTML Changes** in a dedicated window. In the browser or through Remote Access, it opens in a new browser tab.
{% endstep %}

{% step %}
**Choose the captures**

Use **Base capture** and **Compare capture** to select two completed versions. SEO Utils initially selects the latest capture and the one immediately before it. Each option includes the capture time and its **Ranked**, **New**, or **Lost** state.

If only one completed version exists, SEO Utils displays that stored source until another capture becomes available.
{% endstep %}

{% step %}
**Choose what to compare**

* **Full HTML** (default) compares the complete rendered document, including metadata and template markup.
* **Main content** extracts the primary page content to reduce navigation, footer, and template noise.
  {% endstep %}

{% step %}
**Review the differences**

Removed lines appear in red on the Base side, and added lines appear in green on the Compare side. The source panes include line numbers, wrapped text, sticky capture headings, and synchronized scrolling.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-23706452980da93a610748dc3288e115c241b73c%2Fplaceholder.png?alt=media" alt=""><figcaption><p>Ranked Page HTML Changes comparing two captured versions</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Investigating new and lost pages:** The Pages tab keeps separate capture histories for each URL. Open the lost page to compare its earlier and loss-time captures when both are available. Open a new page to inspect its first capture; its before-and-after comparison becomes available after a later run captures the same URL again.
{% endhint %}

{% hint style="info" %}
If the selected captures used different device, language, or viewport settings, SEO Utils warns that some differences may come from the capture profile. For a very large comparison that does not finish within five seconds, switch to **Main content** mode.
{% endhint %}

{% hint style="success" %}
To have an AI summarize the changes and relate them to affected keywords, connect the [MCP Server](/guide/mcp-server) and use the **Ranked Page HTML Changes** prompt. MCP can also compare the last capture of an old URL with the first capture of a replacement URL, clearly labeled as a cross-page comparison.
{% endhint %}

#### Rankings Distribution Tab

In [v1.25.0](https://help.seoutils.app/guide/pages/FYHJNu9cAi74Qc90ALo7#v1.25.0), SEO Utils introduced a new report for the Organic Rank Tracker that provides a detailed ranking distribution analysis. This feature lets you see how many keywords your website or competitors rank in the **top 3, top 10, top 20, and top 100**.

For each ranking range, you can also track the number of keywords that are new, lost, improved, or declined—giving you valuable insights into performance trends.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e9f5e8f8d2f072edee131cf105a8eddaa948d886%2FXnapper-2025-01-05-17.53.14.png?alt=media" alt=""><figcaption><p>Rankings Distribution report view</p></figcaption></figure>

You can click on the total number of keywords to see which keywords are ranking.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-58916e0b9bdbc289970df210ad161c4af35d5c86%2FXnapper-2025-01-05-18.22.53.png?alt=media" alt=""><figcaption><p>Keywords in the top 100 of vinmec.com on Jan 5, 2025.</p></figcaption></figure>

#### Competitors Discovery Tab

[In v1.26.3](https://help.seoutils.app/guide/pages/FYHJNu9cAi74Qc90ALo7#v1.26.3), SEO Utils introduces a new report: Competitors Discovery. It helps you analyze and compare your competitors’ search engine rankings.

This guide will walk you through how to read and benefit from the Competition Map (scatter plot), the timeline scrubber, and the detailed table, along with how to use the available filters.

**Understanding the Competition Map (Scatter Plot)**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9520ead22b289f979991a730b10341397085f6de%2FXnapper-2025-02-26-15.14.14.png?alt=media" alt=""><figcaption><p>Competition Map</p></figcaption></figure>

**What does it show?**

* The **x-axis** represents the **number of keywords** a domain ranks for in Google’s top 100 search results.
* The **y-axis** represents the **average position** of a domain across all its ranked keywords.
* The **size of each bubble** represents the **visibility** of the domain. A larger bubble indicates higher visibility.
* The **color** represents different competitor domains for easy differentiation.

**With keyword weights**

When the report's keywords have different [weights](#keyword-weights), the map counts each keyword by its weight:

* **Average position**, **standard deviation** and **visibility** count each keyword by its weight.
* **Track only** keywords are left out. A domain that ranks only for Track only keywords does not appear.
* The **keyword count** is the number of counted keywords the domain ranks for.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-eeabd17f1fa5108a6b1ebe226883b27a982f6d22%2Forganic-rank-tracker-keyword-weight-competition-map.png?alt=media" alt="The Competition Map with the Weighted badge"><figcaption><p>The Weighted badge (1) tells you the map counts keywords by their weights.</p></figcaption></figure>

**How to read it?**

* **Bottom-right corner (low average position & high keyword count)** → This means a domain ranks for many keywords and is performing well (closer to position #1).
* **Top-left corner (high average position & low keyword count)** → This means a domain ranks for fewer keywords and is performing poorly.
* **Large bubbles** → These indicate competitors with strong visibility across many keywords.
* **Small bubbles** → These competitors have a lower presence in SERPs.
* **Overlapping bubbles** → Multiple domains competing for similar keywords.

{% hint style="success" %}
**Key benefits of the scatter plot**

* **Identify strong competitors** → Look for large bubbles with low average positions.
* **Spot market gaps** → Find competitors ranking for fewer keywords but with high visibility.
* **Assess keyword competition** → See who dominates a niche by ranking for many keywords.
  {% endhint %}

{% hint style="info" %}
**Tips:**

* **Minimap Toggle**: Enables zooming for a closer view.
* **Hovering Over a Bubble**: Displays a tooltip with details about that domain, including: Number of keywords, Average ranking position, Standard deviation, Visibility percentage & change over time.
  {% endhint %}

**Scrubbing Through Time with the Timeline**

Below the Competition Map sits a timeline that lets you scrub through every snapshot the report has — drag the playhead, click anywhere on the track to jump, or press **Play** to auto-advance (\~750ms per snapshot, loops back to the From anchor at the end) and watch bubbles smoothly reposition and resize as competitors gain or lose visibility over time.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FF4KwP49eqAlnxuF7ngG0%2FXnapper-2026-05-23-12.23.32.png?alt=media&amp;token=a5549d11-2efd-478b-b874-543afcfe9520" alt=""><figcaption><p>Timeline scrubber below the Competition Map</p></figcaption></figure>

Click the track once to focus it, then use the keyboard:

| Shortcut   | Action                                 |
| ---------- | -------------------------------------- |
| ← / →      | Step to the previous / next snapshot   |
| Home / End | Jump to the earliest / latest snapshot |
| Space      | Toggle play / pause                    |

{% hint style="info" %}
Snapshots are spaced evenly along the track (not by calendar gap), so days where the tracker didn't run don't waste width and the playhead always snaps to a real data point. The timeline hides itself for reports with fewer than two snapshots.
{% endhint %}

{% hint style="success" %}
**Scrub anywhere — including dates before your From anchor.** Bubble positions always reflect the playhead's date. Diff numbers stay mathematically consistent in both directions: positive means the competitor was bigger on the playhead date than on the anchor date.
{% endhint %}

**Understanding the Detailed Competitor Table**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3ccff6b8fb5f677c715ecb70bae6b5084c5dc56b%2FXnapper-2025-02-26-15.23.08.png?alt=media" alt=""><figcaption><p>Competitor table</p></figcaption></figure>

The table provides more specific metrics for each domain, helping you analyze competitor trends in depth.

<table><thead><tr><th>Column</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>Domain</td><td>The competitor’s website</td><td></td></tr><tr><td>Visibility</td><td>A percentage representing how visible the domain is in search results. Higher visibility means better rankings across keywords.</td><td></td></tr><tr><td>Keywords</td><td>The number of keywords the domain ranks for in the <strong>top 100</strong>.</td><td></td></tr><tr><td>Avg. Position</td><td>The <strong>average ranking position</strong> of all ranked keywords for the domain. A lower number means better rankings.</td><td></td></tr><tr><td>Std. Deviation</td><td>Measures the variation of ranking positions. A <strong>low value</strong> indicates stable rankings, while a <strong>high value</strong> suggests fluctuations.</td><td></td></tr></tbody></table>

{% hint style="success" %}
Tips:

* Sort the columns by clicking on the headers to rank competitors by Visibility, Keywords, or Average Position.
* Compare visibility changes to see which domains are gaining or losing ranking positions over time.
* Check standard deviation to determine ranking stability—domains with a low Std. Deviation have consistent rankings.
  {% endhint %}

**Using Filters for a More Targeted Analysis**

1. Date Filter

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-99e89f93892fc49f0c9cd0a04c6625662425baf3%2FCleanShot%202025-02-26%20at%2015.28.26%402x.png?alt=media" alt="" width="375"><figcaption><p>Date filter</p></figcaption></figure>

* Compare ranking changes over two specific dates.
* Useful for tracking ranking trends over time.

2. Depth Filter

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6ed906a51c90e522dafa86849857fe497b56e33e%2FCleanShot%202025-02-26%20at%2015.29.24%402x.png?alt=media" alt="" width="218"><figcaption><p>Depth filter</p></figcaption></figure>

* Select Top 100, Top 50, Top 20, Top 10, Top 5, or Top 3 domains.
* Helps you analyze only the most relevant competitors in SERPs.
* Use Case: If you want to focus on high-ranking competitors, select Top 10 or Top 5.

3. Ignored Domains Filter

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-84f29dd35052dc10cb507a70520ce743160d56ee%2FCleanShot%202025-02-26%20at%2015.30.50%402x.png?alt=media" alt="" width="350"><figcaption><p>Ignored domain filter</p></figcaption></figure>

* Exclude specific competitors that may not be relevant (e.g., social media sites like Facebook or large aggregators).
* Use Case: If a competitor dominates rankings but isn’t a direct competitor, excluding them gives clearer insights into your true competitors.

{% hint style="success" %}
You can also filter the data by searching for a specific keyword, allowing you to analyze rankings and competition for that keyword alone.
{% endhint %}

#### Keyword Fluctuation Tab

The Keyword Fluctuation tab helps you track how your keyword rankings have changed over time. Unlike the Overview tab which compares two specific dates, this tab shows ranking changes across multiple time periods at a glance.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FMRHEQQWbpISpof9IaaEa%2FXnapper-2026-01-31-23.13.43.png?alt=media&amp;token=f4c68610-dfe6-4491-8204-f3c98e6af266" alt=""><figcaption><p>Keyword Fluctuation tab showing ranking changes over time</p></figcaption></figure>

**Understanding the Columns**

| Column  | Description                                                                                   |
| ------- | --------------------------------------------------------------------------------------------- |
| Keyword | The tracked keyword with tags                                                                 |
| Intent  | Search intent classification (I=Informational, N=Navigational, C=Commercial, T=Transactional) |
| Start   | The earliest ranking position within the selected date range                                  |
| Rank    | Current ranking position at the end of the date range                                         |
| SF      | Number of SERP features appearing for this keyword                                            |
| 1d      | Ranking change compared to 1 day ago                                                          |
| 7d      | Ranking change compared to 7 days ago                                                         |
| 30d     | Ranking change compared to 30 days ago                                                        |
| Life    | Lifetime change (difference between Start and current Rank)                                   |
| URL     | The ranking page URL                                                                          |

{% hint style="info" %}
**Reading the change columns:**

* **Green numbers** indicate ranking improvements (moved up in search results)
* **Red numbers** indicate ranking declines (moved down)
* **0** means no change in position
* **—** means data is not available (keyword wasn't ranked on that date)
  {% endhint %}

{% hint style="success" %}
**Use Cases for Keyword Fluctuation**

* **Monitor stability**: Keywords showing 0 across all time periods have stable rankings
* **Identify quick wins**: Look for keywords with positive 7d/30d changes to understand what's working
* **Spot problems early**: Negative changes in recent periods (1d, 7d) may indicate issues to address
  {% endhint %}

#### Insights Tab

The Insights tab automatically analyzes your keyword ranking data and classifies keywords into actionable categories. It helps you identify which keywords need attention and why — without manually scanning through hundreds of rows.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FS6HPoSqgYytnxSsrCkhr%2FXnapper-2026-03-30-21.45.57.png?alt=media&amp;token=f6b1da7e-be0b-40bb-b14d-527a8c3d35b4" alt=""><figcaption><p>Insights tab showing summary cards for each insight type</p></figcaption></figure>

Insights are computed automatically after each snapshot completes. You don't need to trigger them manually.

**Summary Cards**

The tab displays summary cards, each representing a different insight type:

| Card          | Color  | Description                                                                                                                                           |
| ------------- | ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| Trending Up   | Green  | Keywords with a statistically significant upward ranking trend over the configured window                                                             |
| Trending Down | Red    | Keywords with a statistically significant downward ranking trend                                                                                      |
| Pogo Sticking | Orange | Keywords with unstable rankings that oscillate back and forth significantly                                                                           |
| Flickering    | Purple | Keywords that repeatedly appear and disappear from search results                                                                                     |
| Key Events    | Blue   | Keywords associated with pages that generated conversions in Google Analytics 4                                                                       |
| PAA Source    | Purple | Keywords where your target domain currently appears as a source inside the People Also Ask box. Requires PAA Click Depth to be enabled on the report. |

Click any card to see the matching keywords in a table directly below the cards. The selected card is highlighted, and you can switch between insight types by clicking different cards. Your selection is remembered across sessions.

A subtitle above the cards shows the date range used for calculations: *"Insights calculated from your last 14 snapshots (Mar 13 – Mar 26)"*. You can adjust the number of snapshots using the dropdown — options range from 7 to 90 days.

{% hint style="success" %}
**Enabling Key Events:** Connect your [Google Analytics 4](/guide/google-analytics-4) property to see which keywords drive conversions. SEO Utils matches keywords to landing pages using your rank tracker's position data. If you also have [Google Search Console](/guide/google-search-console) connected, attribution accuracy improves — GSC provides Google's actual click data showing which keyword led to which page.
{% endhint %}

**Keyword Table**

When you click a summary card, a keyword table appears showing:

* **Keyword** — with insight badges displayed inline
* **Start Position** — position at the beginning of the rolling window
* **Current Position** — position at the end of the rolling window
* **Diff** — position change over the window
* **Page** — the ranking URL

You can expand any keyword row to view its position history chart with trend lines and conversion bars.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FVeKY10nCf8K3JAJZFjuN%2FXnapper-2026-03-30-21.46.56.png?alt=media&amp;token=30c54d37-eb58-4b73-8e22-ca64bb79ea45" alt=""><figcaption><p>Insights tab with keyword table showing filtered results for a selected insight type</p></figcaption></figure>

**Inline Badges in Overview**

Keywords with active insights also display colored badges in the Overview tab — next to existing tags. These badges are read-only indicators that help you spot insights while browsing the full keyword table.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F8AzJffSIIWMWChwXuwm2%2FXnapper-2026-03-30-21.47.46.png?alt=media&amp;token=6389bfb8-30ab-4f05-b5fb-16d14c9a9170" alt=""><figcaption><p>Keyword rows showing inline insight badges alongside tags in the Overview tab</p></figcaption></figure>

**Chart Overlays**

When you expand a keyword row to view its position history chart, additional overlay controls appear if that keyword has insights:

* **Show Trend Line** — Toggle a dashed regression line across the chart. Green for trending up, red for trending down.
* **Highlight Swings** — Toggle orange markers on the specific data points that triggered pogo sticking detection.
* **Key Events Bars** — When GA4 conversion data exists, subtle blue bars appear at the bottom of the chart on days that had conversions. These are always visible (no toggle needed) and show the event count in the tooltip.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FKTVu85gQ58ecLBtALFEP%2FXnapper-2026-03-30-21.48.40.png?alt=media&amp;token=aa80478f-999c-45d6-9bf1-7e2b9d29b93a" alt=""><figcaption><p>Position history chart with trend line overlay and GA4 conversion bars</p></figcaption></figure>

{% hint style="info" %}
**How Insight Detection Works**

* **Trend Detection** uses linear regression with an R² safety net to distinguish real trends from noise. It applies tiered thresholds — small ranking changes on page 1 are significant, while the same change on page 5 is noise.
* **Pogo Sticking** detects keywords with 2 or more significant opposing position swings within a 14-day window. The swing threshold scales by position tier (3+ positions for top 10, 5+ for positions 11-30, 10+ for positions 31-100).
* **Flickering** counts state transitions between ranked and not-ranked. Keywords with 3 or more transitions in 14 days are flagged — this indicates indexation instability, not ranking competition. For reports with a shallow tracking depth (under 50), SEO Utils automatically excludes transitions where the keyword was near the depth boundary — preventing false positives from keywords that simply bounce in and out of your configured tracking range.
* **PAA Source** is a binary current-state signal — only the most recent snapshot matters. The card count reflects "your target domain is in PAA right now" rather than "was in PAA at some point recently". Activation and resolution events fire the day you appear in or disappear from a PAA box, giving precise gained/lost alerts via [Automations](/guide/automations).
  {% endhint %}

{% hint style="warning" %}
**Requirements for Each Insight Type**

* **Trending Up/Down** — Requires a minimum number of snapshots (at least 50% of the configured trend window, minimum 7). Available for all report frequencies.
* **Pogo Sticking & Flickering** — Require **daily tracking**. These insights are locked for weekly or monthly reports because the data between snapshots is invisible. A notice appears on locked cards. For the most accurate flickering detection, use a tracking depth of 100. Shallow depths (10-30) may miss some genuine flickering because keywords near the depth boundary are automatically excluded to prevent false positives.
* **Key Events** — Requires [Google Analytics 4](/guide/google-analytics-4). Connect a GA4 property and map it to the same domain as your rank tracker report. Optionally connect [Google Search Console](/guide/google-search-console) for more accurate keyword-to-page attribution. Available for all report frequencies.
* **PAA Source** — Requires **PAA Click Depth ≥ 1** on the report (DataForSEO only). The card is locked otherwise, with a hint to enable the setting. Available for all report frequencies.
  {% endhint %}

**Insights Readiness Checklist**

Use this table to check which insights are available for your report:

| Insight          | Schedule      | Min Snapshots               | Tracking Depth                          | GA4 Connected | GSC Connected                | Other Requirement                         |
| ---------------- | ------------- | --------------------------- | --------------------------------------- | ------------- | ---------------------------- | ----------------------------------------- |
| Trending Up/Down | Any           | 7+ (or 50% of trend window) | Any                                     | Not needed    | Not needed                   | —                                         |
| Pogo Sticking    | Daily (1 day) | 7+                          | Any (100 recommended)                   | Not needed    | Not needed                   | —                                         |
| Flickering       | Daily (1 day) | 2+                          | Any (100 recommended for best accuracy) | Not needed    | Not needed                   | —                                         |
| Key Events       | Any           | Any                         | Any                                     | **Required**  | Optional (improves accuracy) | —                                         |
| PAA Source       | Any           | 1+                          | Any                                     | Not needed    | Not needed                   | **PAA Click Depth ≥ 1** (DataForSEO only) |

{% hint style="info" %}
To check your report's settings, open the report and look at the schedule frequency (daily/weekly/on-demand), tracking depth, and snapshot count. If Pogo Sticking or Flickering cards show as locked, switch your report schedule to **daily**.
{% endhint %}

**Configuring the Trend Window**

The trend detection window defaults to 14 days. You can adjust it directly on the Insights tab using the dropdown in the subtitle area (e.g., "Insights calculated from your last **\[14 ▾]** snapshots"). When you change the value, insights are automatically recomputed in the background. A longer window (e.g., 30 days) catches slower trends but requires more snapshots before badges appear.

**Insights in Exported Reports**

When you export a rank tracker report as PDF or HTML, insight badges are included in the keyword table. Each badge uses inline styling, so they render correctly in emails, PDFs, and shared links without requiring JavaScript.

### Manage Organic Rank Tracker Reports

You can add tags to your Organic Rank Tracker reports and filter by those tags.

This will be especially useful if you manage dozens of locations for a single client. You can add the client's name as a tag, and whenever you want to view all reports for that client, you can simply filter by the tag name.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8d02d5088b862e0e9ff9709d1a832a2d4c6c7ed8%2FXnapper-2024-10-31-12.49.57.png?alt=media" alt=""><figcaption></figcaption></figure>

### Export Reports

You can export the organic rank tracker report as **CSV**, **PDF**, or **HTML** by clicking the Actions dropdown.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3b1c8de4b5b1546daaacb6b029f3074b7a9cc1ac%2FXnapper-2025-01-05-18.26.52.png?alt=media" alt=""><figcaption><p>Export an organic rank tracker report</p></figcaption></figure>

{% hint style="info" %}
**PAA Appearances column** — When PAA Click Depth is enabled on the report, the CSV export includes a `PAA Appearances` column showing how many times each domain appeared as a PAA source within the selected date range. This lets you pivot or filter PAA visibility data externally in Excel, Sheets, or any analytics tool.
{% endhint %}

{% hint style="info" %}
**Pixels From Top columns** — When Track Pixels From Top is enabled on the report, the CSV export includes three additional columns: `Pixels From Top [from-date]`, `Pixels From Top [to-date]`, and `Pixels Diff`. Use these to analyze on-screen visibility trends outside the app or build custom reports that combine rank and pixel signals.
{% endhint %}

{% hint style="info" %}
**Local Pack columns** — When the report tracks a Business Name, the CSV export adds the Local Pack position for both dates and its change. The Position, Page and Diff columns are always the organic rank. PDF and HTML exports, and client reports, show the same green 📍 badge as the app.
{% endhint %}

When exporting a report as PDF or HTML, you can personalize the report cover with your own branding by clicking the Settings icon.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-11f34e6b03dcffc30568f3fcc8bb482d81fc8989%2FCleanShot%202025-01-05%20at%2021.52.54%402x.png?alt=media" alt="" width="229"><figcaption><p>Custom your own branding</p></figcaption></figure>

You can use placeholders to dynamically replace content in headings, subheadings, or descriptions. For example, if you include the placeholder `[domain]`in a sub-heading, it will automatically replace it with the target domain of your report.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9fae2f0faf134862e13c46c34cb384aadb172825%2FCleanShot%202025-01-05%20at%2021.53.57%402x.png?alt=media" alt=""><figcaption></figcaption></figure>

### Show Site Traffic in the Report

A PDF report can show the site's traffic from [Google Analytics 4](/guide/google-analytics-4) next to its rankings. Choose the GA4 property when you edit the report.

{% stepper %}
{% step %}

#### Open Edit Tracker

Open the report, click its name at the top, then **Edit Tracker**.
{% endstep %}

{% step %}

#### Choose the property

On the **Report** tab, pick the GA4 property in **Site traffic (GA4)**, below **Name**, then click **Update Tracker**. Choose **Off** to leave the section out.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a6677692123002c4636b98f29899046c14209e95%2Fort-edit-site-traffic.png?alt=media" alt="The Report tab of Edit Organic Rank Tracker with the Site traffic (GA4) field showing a Suggested property and the Update Tracker button"><figcaption><p>The Site traffic (GA4) field (1) and Update Tracker (2)</p></figcaption></figure>
{% endstep %}
{% endstepper %}

The field is only in **Edit Tracker**, not in the form that adds a report. Under it, SEO Utils says where the choice stands:

* **Suggested** (badge). Exactly one GA4 property matches the report's domain, so SEO Utils suggests it. Nothing is turned on until you click **Update Tracker**.
* **Not saved yet.** You changed the choice and have not clicked **Update Tracker**.
* **Saved. The report uses this property.** The choice is stored.

An **Off** you chose stays off.

The report then gets a **Site traffic (GA4)** section for the report's period:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1dc285ca953db7f9740c4f1b4219644667cb4c9a%2Freport-site-traffic-section.png?alt=media" alt="The Site traffic section of a report with KPI tiles, the organic search split and the Channels table"><figcaption><p>The KPI tiles (1), organic search against all other channels (2) and the Channels table (3)</p></figcaption></figure>

* **KPI tiles** for sessions, engaged sessions, engagement rate, key events, session key event rate and revenue, each compared with the previous period and the same period last year.
* **Organic search and all other channels**, then the **Channels** table.
* A **Last 13 months** chart of sessions by channel, and **Key events by channel**.
* Short definitions of the terms, because paper has no tooltips.

GA4 can still change its last three days, so the report marks them and leaves them out of the comparisons. The section is in the PDF you export and in the PDFs an [automation](/guide/automations) creates, in the same language as the rest of the report. If the property is removed from SEO Utils, the section is left out and the report says so on screen.

#### The Traffic tab

The same setting adds a **Traffic** tab to the report's own page, and to the [published client report](/guide/white-labeled-client-report#the-traffic-tab). It is there for the owner and for team members who can view reports, so you can see what your client will see.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c08091e904822b4bd2eafd81f9db798a87722ab2%2Fort-traffic-tab.png?alt=media" alt="The Traffic tab of an Organic Rank Tracker report with the date range, the comparison, View GA4 traffic and the KPI cards"><figcaption><p>The Traffic tab (1), the date range (2), the comparison (3) and View GA4 traffic (4)</p></figcaption></figure>

* **Same figures as the client report.** The tab has the same presets and comparisons, counted back from the report's newest snapshot day, so it shows what a report published now would show. Unlike the client report, it also lets you pick a custom date range.
* **Live reads.** The tab reads the GA4 data SEO Utils has synced, so it needs no publishing.
* **View GA4 traffic (4)** opens the full [GA4 Traffic](/guide/google-analytics-4/ga4-traffic) page, for people who can open it. The tab itself has no **Sync now**, export or property switcher.
* **No tab when Site traffic is Off.** If the property was removed from SEO Utils, the tab says **GA4 property no longer connected** and shows no figures.
* **Export as CSV** is not offered in the report's menu while the Traffic tab is open, because the tab has no keyword table to export. **Export as PDF** stays.


# Saved Keywords

Saved Keywords lets you collect and organize keywords from various tools into named lists. You can save keywords from Keyword Explorer, Google PAA, Autocomplete, Organic Keywords, and Ads Vision—all in one place.

Each list is organized by location and language, making it easy to manage keywords for different markets or projects.

## Creating a Saved Keywords List

{% stepper %}
{% step %}
**Navigate to Saved Keywords**

Go to **Keyword Research > Saved Keywords** in the sidebar.
{% endstep %}

{% step %}
**Create a New List**

* Click the **"Create List"** button in the top-right corner
* Enter a **name** for your list
* Pick the **Location / Language** you're targeting, for example United States / English. It is used for checking keyword metrics, so the list offers the pairs your [default keyword metrics source](/guide/keyword-metrics-data-source) supports
* Click **"Create List"**

The lists table then shows each list's location (with its flag) and language.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FSLaS5r2uQikWLKpcQIxK%2FXnapper-2026-01-31-11.08.01.png?alt=media&amp;token=0aa6c386-34ac-40af-873c-dc25f00c5725" alt=""><figcaption><p>Create a new saved keywords list</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b054dfa70331e8efec5fafb962beb49477380d54%2Fsaved-keywords-create-list-dialog.png?alt=media" alt=""><figcaption><p>(1) Name the list. (2) Pick the Location / Language. (3) Create it</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Saving Keywords from Other Tools

You can save keywords directly from any keyword tool using bulk actions.

{% stepper %}
{% step %}
**Select Keywords**

* Go to any keyword tool (Keyword Explorer, Organic Keywords, Google PAA, Autocomplete, or Ads Vision)
* Select the keywords you want to save using the checkboxes
  {% endstep %}

{% step %}
**Use the Save to List Action**

* Click **"Bulk Actions"**
* Select **"Save to List"**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FmY8JxJorgIM8vyZm7drq%2FXnapper-2026-01-31-11.26.42.png?alt=media&amp;token=fe355789-3aac-4311-b801-032df070046b" alt=""><figcaption><p>Save keywords using bulk action</p></figcaption></figure>
{% endstep %}

{% step %}
**Choose a List**

* Select an existing list from the dropdown, or
* Click **"New List"** to create one directly from the modal
* Click **"Add Keywords"**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fjz0V4UfdTCnOWqCcH32d%2FXnapper-2026-01-31-11.27.25.png?alt=media&amp;token=bea6b88a-6c20-4c7b-a62d-023590b20269" alt=""><figcaption><p>Select a list or create a new one</p></figcaption></figure>

{% hint style="info" %}
SEO Utils automatically skips duplicate keywords. You'll see a message showing how many were added and how many were skipped.
{% endhint %}
{% endstep %}
{% endstepper %}

## Managing Keywords in a List

Click on any list to open the detail view where you can manage your keywords.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FuLRoEfIpuTSgmKlPWWA1%2FXnapper-2026-01-31-11.28.34.png?alt=media&amp;token=51342061-9302-4e32-ad83-1ada8ac282ae" alt=""><figcaption><p>Saved keywords list detail view</p></figcaption></figure>

### Available Actions

| Action                | Description                                              |
| --------------------- | -------------------------------------------------------- |
| Add Keywords          | Manually add keywords to the list                        |
| Check Keyword Metrics | Fetch search volume, CPC, and difficulty from DataForSEO |
| Update Tags           | Add or remove tags for selected keywords                 |
| Remove Keywords       | Delete keywords from the list                            |
| Export CSV            | Download all keywords with their metrics                 |
| Map Keyword Data      | Import external metrics from CSV/Excel files             |

### Filtering Keywords

Use filters to narrow down your list:

* **Search**: Find keywords by name
* **Volume Range**: Filter by search volume
* **CPC Range**: Filter by cost per click
* **Difficulty Range**: Filter by keyword difficulty
* **Search Intents**: Filter by user intent
* **Tags**: Filter by custom tags

## Adding Tags to Keywords

Tags help you organize keywords within a list.

### Update Tags for Multiple Keywords

{% stepper %}
{% step %}
**Select Keywords**

Select keywords using the checkboxes in the table.
{% endstep %}

{% step %}
**Apply Tags**

* Click **"Bulk Actions"** > **"Update Tags"**
* Choose tags to **add** or **remove**
* Click **"Execute"**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FL8a1MOtq4XGWUctsmXlj%2FXnapper-2026-01-31-11.29.14.png?alt=media&amp;token=55825289-c455-4d5e-ad16-9d80165907a4" alt=""><figcaption><p>Bulk update tags for keywords</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="success" %}
You can also update tags for a single keyword by clicking the three-dot menu on any row and selecting **"Update Tags"**.
{% endhint %}

## Importing External Data

Use **Map Keyword Data** to import metrics and tags from CSV or Excel files.

{% stepper %}
{% step %}
**Open Map Keyword Data**

Click the three-dot menu in the page header and select **"Map Keyword Data"**.
{% endstep %}

{% step %}
**Upload Files**

Upload your CSV or Excel file(s) containing keyword data.
{% endstep %}

{% step %}
**Map Columns**

Map each column to the appropriate data type:

* **Keyword**: Required - matches keywords in your list
* **Volume**: Search volume data
* **CPC**: Cost per click data
* **Intent**: Search intent classification
* **Tags**: Custom tags (comma-separated)

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FQOxJzWyWMxABNun5uTCq%2FXnapper-2026-01-31-11.30.11.png?alt=media&amp;token=e5d0e27d-9b88-4140-8776-890dd1f51e57" alt=""><figcaption><p>Map external keyword data</p></figcaption></figure>
{% endstep %}

{% step %}
**Import Data**

Click **"Import Data"** to apply the external data to matching keywords.

{% hint style="info" %}

* Keywords are matched case-insensitively by default
* External metrics override existing data
* Tags should be comma-separated (e.g., "seo, tools, analytics")
  {% endhint %}
  {% endstep %}
  {% endstepper %}

## Exporting Keywords

{% stepper %}
{% step %}
**Export to CSV**

* Open a saved keywords list
* Click the three-dot menu in the page header
* Select **"Export CSV"**
* Choose where to save the file
  {% endstep %}
  {% endstepper %}

The exported CSV includes: Keyword, Search Volume, CPC, Keyword Difficulty, Search Intents, and Tags.

## Checking Keyword Metrics

Fetch keyword metrics from DataForSEO for selected keywords.

{% stepper %}
{% step %}
**Select Keywords**

Select the keywords you want to check using the checkboxes. Select all if you want to check the entire list.
{% endstep %}

{% step %}
**Run the Action**

* Click **"Bulk Actions"** > **"Check Keyword Metrics"**
* Review the cost estimation
* Click **"Execute"**

{% hint style="info" %}
DataForSEO only charges for keywords that return data. Keywords without search volume won't incur costs.
{% endhint %}
{% endstep %}
{% endstepper %}

## Best Practices

* **Use descriptive list names**: Include the project or client name for easy identification
* **Organize by locale**: Create separate lists for different location/language combinations
* **Tag consistently**: Use the same tag names across lists for better organization
* **Import your data**: Use Map Keyword Data to enrich lists with external metrics
* **Export regularly**: Keep backups of your keyword lists


# Bulk Autocomplete

Bulk Autocomplete collects the search suggestions Google, Bing, YouTube or Amazon shows while people type. Give it a list of seed keywords, choose how each seed is expanded, and SEO Utils looks up every variation and saves the suggestions in one report.

You can also let AI suggest more seeds for you, or fill a template with a list of things — for example, every coffee brewing method in `{brew method} coffee ratio`.

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F0MSaISsqxm8Xl0XVcTrP%2FXnapper-2026-09-27-14.41.08.png?alt=media&amp;token=adca1f37-e180-47d3-8b71-14af7e603acd" alt=""><figcaption><p>A Bulk Autocomplete report with its suggestions and the seed each one came from</p></figcaption></figure></div>

## How It Works

1. **Seeds** — You type seed keywords, generate them with AI, or fill a template.
2. **Lookups** — Each seed is expanded into variations (for example `cold brew a`, `cold brew b`, `how to cold brew`), and each variation is looked up in the search engine's autocomplete. One variation is one lookup.
3. **Suggestions** — Every suggestion is saved with the seed it came from, after your filters (excluded words and the `*` pattern) have removed the ones you don't want.

## Running Bulk Autocomplete

{% stepper %}
{% step %}
**Open the Run Dialog**

Go to **Keyword Research > Bulk Autocomplete** in the sidebar and click **"Run Bulk Autocomplete"**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-aa47916e940f1fc14bcf8e82b45b4b3a8905100f%2Fbulk-autocomplete-run-dialog.png?alt=media" alt=""><figcaption><p>The Run Bulk Autocomplete dialog. (1) Location. (2) Language. (3) Search engine</p></figcaption></figure>
{% endstep %}

{% step %}
**Enter Seed Keywords**

Type or paste your seed keywords, one per line.

Use `*` as a wildcard to ask for words in a specific position. For example, `how to clean * machine` looks up `how to clean a machine`, `how to clean b machine`, and so on.

{% hint style="info" %}
Don't have many seeds yet? Click **"Generate seeds with AI"** under the box. See [Generating Seeds with AI](#generating-seeds-with-ai).
{% endhint %}
{% endstep %}

{% step %}
**Choose the Location, Language and Search Engine**

* **Location** and **Language** — The market you want suggestions for. Type a country or territory and pick it from the list, then pick the language. Cities and regions are not offered here.
* **Search engine** — **Google**, **Bing**, **YouTube** or **Amazon**. SEO Utils remembers your choice for the next run.

{% hint style="info" %}
**YouTube** returns what people type in YouTube's search box, which is often different from Google: more "how to", tutorials, reviews and music. Use it to plan videos, or to find topics people prefer to watch rather than read.
{% endhint %}

{% hint style="info" %}
**Amazon** returns what shoppers type in an Amazon store's search box: product names, brands, sizes and features. Use it for product pages, listings and shopping content.

* Choosing Amazon replaces the Location and Language fields with one **Location / Language** field, for example United States / English. If the location you picked for another engine has no Amazon store, the form asks you to choose one that does.
* Only locations with an Amazon store are offered, for example the United States (amazon.com), the United Kingdom (amazon.co.uk), Germany (amazon.de) and Japan (amazon.co.jp). Austria uses amazon.de.
* Amazon blocks heavy use sooner than Google. Use [proxies](/guide/how-to-use-proxies) and a few workers.
  {% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e66abd9f2e163f725741d6c210817bb661ea38ec%2Fbulk-autocomplete-amazon-location.png?alt=media" alt=""><figcaption><p>With Amazon selected: (1) one Location / Language field. (2) The engine and its note</p></figcaption></figure>
{% endstep %}

{% step %}
**Choose How Each Seed Is Expanded**

Under **Expand each seed with**, pick one or both:

| Option                        | What it looks up                                                                                                       | Lookups per seed |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ---------------- |
| **Letters a–z**               | A letter after and before the seed (`cold brew a`, `a cold brew`). For a seed with `*`, a letter or digit at each `*`. | About 52         |
| **Questions and comparisons** | Question and comparison words (`how to cold brew`, `cold brew vs …`). English only.                                    | About 180        |

If you turn both off, each seed is looked up exactly as you typed it.
{% endstep %}

{% step %}
**Filter the Suggestions (Optional)**

* **Exclude words** — Type a word and press Enter. Any suggestion that contains one of these words is not saved. Whole words only: excluding `tea` drops "iced tea recipe" but keeps "teapot". Phrases such as `near me` work too.
* **Keep only suggestions that match the \* pattern** — For seeds with a wildcard, keep only suggestions that follow the same pattern. With `how to clean * machine`, "how to clean espresso machine" is kept and "how to clean a mirror" is dropped.
  {% endstep %}

{% step %}
**Adjust Advanced Settings (Optional)**

Open **Advanced** to change:

* **Workers** — How many lookups run at the same time (1 to 50). More workers finish sooner but use more CPU.
* **Use proxies** — Recommended for large runs so the search engine doesn't block you. See [How to Use Proxies](/guide/how-to-use-proxies).
  {% endstep %}

{% step %}
**Check the Estimate and Run**

The bottom of the dialog shows how many lookups the run will make (for example **≈ 234 lookups**). The number updates as you change seeds and options, and it is exactly what the run will do.

Click **"Run"**. You go to the report page, where you can follow the progress. You can close the page or keep working — the run continues in the background.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
SEO Utils remembers your expansion choices, the `*` pattern switch, workers, and proxies for the next run. Excluded words belong to one run and are not remembered.
{% endhint %}

## Generating Seeds with AI

Click **"Generate seeds with AI"** under the seed keywords box to open the AI helper. It has two tabs: **Related keywords** and **Fill a template**.

Nothing is looked up in the helper. The seeds you add join your run, and you review them before you click **"Run"**.

{% hint style="warning" %}
The AI helper uses your own AI provider account. Before you start:

* Add your API key in **Settings > Services > AI Settings**.
* Choose the model in **Settings > General > Default AI Model**.

Each click on **Generate** is one request to your provider. **"My own list"** in the **Fill a template** tab needs no AI.
{% endhint %}

### Related Keywords

Use this tab to get seed ideas that contain a keyword, optionally kept inside a topic.

{% stepper %}
{% step %}
**Describe the Ideas You Want**

* **Keyword** — Every idea will contain it (for example `cold brew`). SEO Utils fills this with your first seed.
* **Stay within a topic** (optional) — Keep ideas on one subject, such as `home brewing`. Leave it empty for broad ideas.
* **How many** — 10, 20, 30, or 50 ideas.

Click **"Generate"**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fi6ucwtjn8ADcqoRDH9Yk%2FXnapper-2026-09-27-15.47.48.png?alt=media&amp;token=973cd431-fe99-498b-aa9d-24b49dc0f3a0" alt=""><figcaption><p>Related keyword ideas for "cold brew" in the AI helper</p></figcaption></figure>
{% endstep %}

{% step %}
**Pick the Ideas to Keep**

All ideas are selected, except the ones marked on the right:

| Mark                      | Meaning                                                                                |
| ------------------------- | -------------------------------------------------------------------------------------- |
| **excluded word**         | The idea contains one of your excluded words, so all its suggestions would be dropped. |
| **already in your seeds** | It looks like a seed you typed. You can still select it.                               |
| **already added**         | It is already in your AI seeds.                                                        |

Use **Select all** and **Clear** to change the selection quickly, or click **"Regenerate"** for a new list.
{% endstep %}

{% step %}
**Add the Seeds**

Click **"Add N seeds"**. The ideas appear under **Generated seeds** in the run dialog, marked as **AI related**.
{% endstep %}
{% endstepper %}

### Fill a Template

Use this tab when you have one pattern and many things to put in it. Each value fills the slot and becomes a seed.

{% stepper %}
{% step %}
**Write the Template**

Put one `{slot}` where the list goes, for example `{brew method} coffee ratio` or `best {dog breed} food`.

You can add `*` too, like `best {brew method} for *`. The wildcard expansion and the `*` pattern filter then apply to each filled seed.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F4hIATk34Uaeh9HsmrgP3%2FXnapper-2026-09-27-14.43.49.png?alt=media&amp;token=a4ddd2c7-05cb-465d-98e8-8090ea3dbabb" alt=""><figcaption><p>A template with its slot, the list of values, and the preview of filled seeds</p></figcaption></figure>
{% endstep %}

{% step %}
**Choose Where the List Comes From**

* **A list from AI** — Describe the list in **List all** (for example `coffee brewing methods`), choose **Up to** 10, 20 or 30 values, and click **"Generate"**.
* **My own list** — Type the values yourself. Press Enter or type a comma after each one.
  {% endstep %}

{% step %}
**Edit the Values**

The values appear as chips. Remove the ones you don't want and add your own — an AI list can be edited just like your own list.

The **Preview** shows the seeds that will be added. Values that are empty after cleanup, or that make a seed longer than 200 characters, are listed as dropped.
{% endstep %}

{% step %}
**Add the Seeds**

Click **"Add N seeds"**. The seeds appear under **Generated seeds**, marked **From templates**.
{% endstep %}
{% endstepper %}

<details>

<summary>Template rules and error messages</summary>

* A template needs exactly one `{slot}`:
  * No slot shows **"Add one {slot} where the list goes"**.
  * Two or more show **"Use only one {slot}"**.
* The slot needs a name, like `{brew method}`.
* A template can't contain a comma, because commas separate seeds.
* Values are used as plain text: `*`, `{`, `}` and commas inside a value are removed.

</details>

{% hint style="info" %}
**Fewer wasted lookups for templates.** When a template doesn't start with its slot, such as `best {dog breed} food`, SEO Utils adds letters only **after** each filled seed. A query like "a best labrador food" is never useful, so those lookups are skipped. When the template starts with its slot, such as `{brew method} coffee ratio`, letters go before and after as usual. The estimate already reflects this.
{% endhint %}

### Reviewing Generated Seeds

Back in the run dialog, **Generated seeds** lists the seeds from the helper in groups (**AI related** and **From templates**).

* Click the **×** on a seed to remove it.
* Click **"Remove"** next to a group, or **"Remove all"**, to clear seeds in bulk.
* Click **"Generate more with AI"** to add more.

When generated seeds are present, **Expand each seed with** shows one row for **Seeds you typed** and one for **Generated seeds**, so each group can be expanded differently. By default, generated seeds get letters only; turn on questions for them if you need more.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fa4rQXxJx0XUn1YxBdUIL%2FXnapper-2026-09-27-15.50.41.png?alt=media&amp;token=597738c0-ea86-48ae-aaaf-7729229df6bc" alt=""><figcaption><p>Generated seeds in the run dialog with a separate expansion row</p></figcaption></figure>

{% hint style="info" %}
A run can use generated seeds only — you don't need to type any seed yourself. If the same keyword is both typed and generated, it is looked up once, as a typed seed.
{% endhint %}

## Report Detail Page

Click a report to open it. The header shows how many seeds of each type the run used (**typed**, **AI related**, **from a template**) and a summary of the run's settings: expansion, excluded words, the `*` pattern filter, and any templates.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FwpyYdowh1KlbVl99PHPQ%2FXnapper-2026-09-27-15.56.53.png?alt=media&amp;token=b980af43-48f5-40cf-bd4e-6a2341c9c4e9" alt=""><figcaption><p>Report header with the seed types and the run settings</p></figcaption></figure>

While a run is in progress, the report shows how many lookups are done. Click **"Cancel run"** to stop it; suggestions saved so far are kept.

### Columns

| Column        | Description                                                                      |
| ------------- | -------------------------------------------------------------------------------- |
| Keyword       | The suggestion                                                                   |
| Volume        | Monthly search volume (after Check Metrics)                                      |
| Amazon Volume | Monthly Amazon search volume (Amazon reports only, after Check Amazon Volume)    |
| CPC           | Cost per click (after Check Metrics)                                             |
| KD            | Keyword difficulty (after Check Metrics)                                         |
| Intent        | Search intent (after Check Metrics)                                              |
| Word Count    | Number of words in the suggestion                                                |
| Found from    | The seed the suggestion came from, with its type (typed, AI · related, template) |

{% hint style="warning" %}
On a YouTube or Amazon report, **Check Metrics** fills in **Google** search volume, CPC and difficulty for the suggestions, and the column is named **Google Volume** to make that clear. YouTube does not publish search volume; for Amazon, use [Check Amazon Volume](#checking-amazon-volume).
{% endhint %}

### Filtering Suggestions

Use **Filters** to narrow the list:

* **Search** — Find suggestions by text.
* **Volume**, **CPC**, **Difficulty**, **Word Count** — Filter by range.
* **Amazon Volume** — Filter by range (Amazon reports only).
* **Seed type** — Show only suggestions from typed, AI related, or template seeds.
* **Seed Keyword** — Show only suggestions from one seed.

### Available Actions

| Action              | Description                                                                                                                    |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Check Metrics       | Fetch search volume, CPC, difficulty, and intent for the suggestions                                                           |
| Check Amazon Volume | Fetch Amazon search volume for the suggestions (Amazon reports only, **Actions > Check Amazon Volume**)                        |
| Export              | Download the suggestions as CSV, including the seed and its type, and Amazon Volume on an Amazon report (**Actions > Export**) |
| View log            | See what the run did: lookups, failures, and how many suggestions each filter dropped (**Actions > View log**)                 |
| Save to List        | Select suggestions, then **Bulk Actions > Save to List** to add them to [Saved Keywords](/guide/saved-keywords)                |

### Checking Amazon Volume

On an Amazon report, **Check Amazon Volume** gets each suggestion's monthly search volume on Amazon from DataForSEO. It is a separate figure from Google search volume, and checking it does not change the **Google Volume** column.

{% stepper %}
{% step %}
**Open the Dialog**

Filter the table to the suggestions you want (or keep all of them), then click **Actions > Check Amazon Volume**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-dec8fff95761d8af7dd2c6c8e1fad4a6a2a8aa92%2Fbulk-autocomplete-check-amazon-volume.png?alt=media" alt="The Check Amazon Volume dialog"><figcaption><p>The Check Amazon Volume dialog: the switch for keywords not checked this month (1), the keyword count, cost and who pays (2), and the button that runs the check (3)</p></figcaption></figure>
{% endstep %}

{% step %}
**Review the Count and the Cost**

* **Only keywords not checked this month** — On by default, so a second check this month costs nothing for keywords already checked.
* The dialog shows how many keywords will be checked and about how much it costs, for example **About $0.13 for 1,000 keywords**.
  {% endstep %}

{% step %}
**Run the Check**

Click **"Check Amazon Volume"**. The **Amazon Volume** column fills in when the check is done. A dash means Amazon had no figure for that keyword; hover over it to see when it was checked.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Check Amazon Volume works with your own DataForSEO credentials or with the rented SEO Utils key, like Check Metrics. The dialog shows who pays: **Billed to your DataForSEO account** or **Billed to your SEO Utils credits**.
{% endhint %}

DataForSEO has Amazon search volume for these locations: Australia, Austria, Canada, Egypt, France, Germany, India, Italy, Mexico, the Netherlands, Saudi Arabia, Singapore, Spain, the United Arab Emirates, the United Kingdom and the United States. Reports for other Amazon locations get suggestions but no Amazon volume, and the dialog says so.

## Managing Reports

The **Autocomplete Reports** page lists every run with its search engine, seed counts by type, number of keywords, and date.

Use the three-dot menu on a row to **View** or **Delete** a report. Select several reports and use **Bulk Actions > Move to Workspace** to move them to another [workspace](/guide/workspace).

{% hint style="info" %}
With [Remote Access](/guide/remote-access), the workspace owner can run Bulk Autocomplete, use the AI helper, and open reports from any browser.
{% endhint %}

## Best Practices

* **Start small.** Check the estimate before running thousands of seeds, and use [proxies](/guide/how-to-use-proxies) for large runs.
* **Exclude competitors and off-topic words** (brand names, "free", "near me") to keep the report focused.
* **Use `*` for positions you care about**, and keep the pattern filter on to stay on topic.
* **Keep AI seeds lean.** Pick only the ideas you would target; letters alone usually give enough suggestions for generated seeds.
* **Use templates for lists of things** — products, locations, breeds, methods — instead of typing every combination.


# LLM Rank Tracker

This tool enables you to monitor your brand's visibility and sentiment across AI-powered answers: Google AI Overview, Google AI Mode, ChatGPT and Gemini. Track how often your brand appears in AI-generated responses, analyze competitor mentions, monitor citations, and measure sentiment over time to understand your brand's presence in the AI search landscape.

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5c35bd2bc039ffdfb68f746f647135bf68ebb007%2FCleanShot%202025-07-21%20at%2015.59.36%402x.png?alt=media" alt=""><figcaption><p>LLM Rank Tracker tool showing brand visibility across AI engines</p></figcaption></figure></div>

{% hint style="info" %}
**Supported AI Engines**: Google AI Overview, Google AI Mode, ChatGPT, ChatGPT – Web Search and Gemini. We're working on adding Perplexity and other AI platforms.
{% endhint %}

## Initial Setup: Configuring Required API Credentials

Before you can start tracking your brand in AI responses, you need to configure the required API credentials. The LLM Rank Tracker requires two different API services to function properly.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-10b63522f6d4f5ee4fd01a86c91591a1c82fadc5%2FXnapper-2025-07-24-08.46.01.png?alt=media" alt="" width="563"><figcaption><p>LLM Rank Tracker onboarding screen showing credential requirements</p></figcaption></figure>

### Required API Credentials

#### 1. DataForSEO Credentials

DataForSEO provides access to the AI engines:

* **Purpose**: Required for every engine: Google AI Mode, Google AI Overview, ChatGPT and Gemini
* **Cost**: Pay-as-you-go pricing, approximately $1.2 per 1,000 queries
* **Account Type**: You must have your own DataForSEO account

{% hint style="warning" %}
**Important**: You cannot use [rented API key services](/guide/rent-dataforseo-api-key) for LLM Rank Tracker. DataForSEO restricts certain endpoints that are essential for the queue mode functionality. Multiple users sharing a rented API key would slow down processing for everyone. For optimal performance, use your own DataForSEO account.
{% endhint %}

#### 2. LLM Provider API Key (OpenAI or OpenRouter)

An LLM provider is used for intelligent data extraction:

* **Purpose**: Required for extracting structured brand mentions from AI responses
* **Supported Providers**: OpenAI or OpenRouter - you only need one
* **Model Used**: GPT-6 Luna for cost-efficient extraction
* **Cost**: Minimal due to efficient prompt design and caching

{% hint style="info" %}
**Provider Selection**: The onboarding screen includes a dropdown to select your preferred provider and a "Test Provider" button to verify your API key is working correctly.
{% endhint %}

### Optional API Credentials

#### 3. Google NLP API Key (Optional)

Google's Natural Language API provides advanced sentiment analysis:

* **Purpose**: Enables sentiment analysis of brand mentions in AI responses
* **When to use**: If you want to track how positively or negatively your brand is mentioned
* **Note**: Without this API key, sentiment analysis will be skipped and sentiment scores will not be available

**Pricing Structure**:

* **Free Tier**: First 5,000 units per month are free (1 unit = 1,000 characters)
* **Paid Tiers**:
  * 5,001 to 1,000,000 units: $0.0010 per unit
  * 1,000,001 to 5,000,000 units: $0.0005 per unit
  * Over 5,000,000 units: $0.00025 per unit
* **Example**: Analyzing 2,500 characters = 3 units

{% hint style="info" %}
**Cost Estimation**: Most brand mentions are 100-500 characters, so you can analyze approximately 10,000-50,000 brand mentions within the free tier each month.
{% endhint %}

{% hint style="success" %}
If you don't have a DataForSEO account yet, visit [this guide](https://help.seoutils.app/guide/seo-data-source#how-to-connect-your-dataforseo-account-to-seo-utils) for step-by-step instructions on creating one.
{% endhint %}

## How to Create Your First LLM Rank Tracker

Creating an LLM Rank Tracker involves configuring what to track (your brand variants), where to track (AI engines), and how to track (search terms and schedule).

### Step 1: Access the LLM Rank Tracker Tool

Navigate to the LLM Rank Tracker section from the main menu. You'll see a list of existing trackers (if any) and an "Add LLM Rank Tracker" button in the top-right corner.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a06dd6cca31931b8f4e7c1be5a410ce7da7b187b%2FXnapper-2025-07-21-16.07.19.png?alt=media" alt=""><figcaption><p>LLM Rank Tracker list page with Add button</p></figcaption></figure>

### Step 2: Configure Basic Tracker Settings

Clicking "Add LLM Rank Tracker" opens a configuration page. Let's go through each field in detail:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-31e4399365144cd74add639791d6b8030b3a4f30%2Fllm-rank-tracker-create-form.png?alt=media" alt=""><figcaption><p>Complete Add LLM Rank Tracker configuration page. (1) Location. (2) Language</p></figcaption></figure>

#### Brand Variants

**Purpose**: All variations of your brand name that should be tracked in AI responses.

**How to Add**: Type a brand variant in the input field and hit the enter or comma key (",") to apply.

**What to Include**:

* Official brand name: "SEO Utils"
* Common variations: "SEOUtils", "SEO Utils App"
* Abbreviations: "SU" (if commonly used)
* Misspellings: "SEO Util", "SEOUtils"
* Previous names: If recently rebranded
* Domain variations: "seoutils.app"

**Main Name**: The first brand variant is your **Main** name and shows a **Main** badge. Every other variant shows a star (☆). Click a star to make that variant the Main name.

The Main name is used for:

* The report title
* Your single **(You)** row in the Competitors, Sentiment and Citations tabs
* New AI answers: the extraction step is asked to record your brand under this name

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FyCpsQeyUrQ8HF6bYC57k%2FXnapper-2026-09-24-16.52.59.png?alt=media&amp;token=0773c67e-7d04-4440-a1bc-03c087a350af" alt="" width="563"><figcaption><p>Brand Variants field with the Main badge on the first variant and a star on the others</p></figcaption></figure>

{% hint style="info" %}
**Pro Tip**: Make your current official brand name the Main name. After a rebrand, add the new name, click its star to make it Main, and keep the old name as a variant so past mentions still count as your brand.
{% endhint %}

**How Brand Matching Works**: A brand name found in an AI response counts as your brand when one of your variants appears in it as whole words. Matching ignores letter case.

* ✅ Variant "Acme" matches "Acme Corp", "ACME" and "acme.com"
* ❌ Variant "Acme" does not match "Kacme" (the letters sit inside another word)
* ❌ Variant "Acme Australia" does not match a plain "Australia" or "Acme"
* ❌ Variant "C++" does not match "C#" (symbols are part of the variant)

{% hint style="warning" %}
**Add each short form you want counted**: A shorter name is not matched by a longer variant. If AI tools often call you "Acme" while your variant is "Acme Corp", add "Acme" as its own variant.
{% endhint %}

{% hint style="info" %}
**Existing trackers**: After you update SEO Utils, your existing reports are re-checked once with these matching rules. Names that only matched part of a word stop counting as your brand, so a few numbers may change slightly.
{% endhint %}

#### Location and Language

Pick the **Location** and the **Language** of the AI answers. Each AI engine works in its own set of markets and languages, so both fields list every option that at least one engine supports.

**Location** lists countries and territories, such as Hong Kong, Taiwan and Puerto Rico. Type to search.

* Each option shows one icon per checked engine. A struck-through icon means that engine does not offer this location. For example, ChatGPT answers for Taiwan but not for Hong Kong or Puerto Rico
* Only Google AI Mode uses a region, city or postal code: check it to see them in the list, and Google answers for that place instead of the whole country. The other engines use the country of the place you pick

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f906b5647f4dcd6b9682b5ae642ebca1f0c62853%2Fllm-rank-tracker-location-hong-kong.png?alt=media" alt="Location field open on Hong Kong, with one icon per checked engine"><figcaption><p>(1) A territory such as Hong Kong is offered like a country. (2) ChatGPT does not offer it. (3) The hint under the field</p></figcaption></figure>

**Language** lists every language an engine supports. Options are grouped by the engines you checked: **All checked engines answer**, **Some checked engines answer** and **No checked engine answers**. The same icons show which engine offers each language.

#### AI Engines Selection

Check the engines that should answer each search term. Each engine has its own icon: Google AI Mode has a small sparkle and ChatGPT – Web Search a small magnifier, so you can tell them apart from Google AI Overview and ChatGPT.

| Engine               | What it asks                                          |
| -------------------- | ----------------------------------------------------- |
| Google AI Overview   | The AI summary on Google's search results (desktop)   |
| Google AI Mode       | Google's conversational AI Mode (English only)        |
| Gemini               | The Gemini app (gemini.google.com)                    |
| ChatGPT              | ChatGPT's answer                                      |
| ChatGPT – Web Search | ChatGPT that always searches the web before answering |

Each engine row shows whether that engine answers for the location and language you picked:

| Label                                               | What it means                                                                                                                                           |
| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Answers here**                                    | The engine answers for this location and language                                                                                                       |
| **Google decides**                                  | DataForSEO accepts this location and language, but Google shows AI answers only in some markets. A check without an AI answer can still cost the search |
| **Location not offered** / **Language not offered** | The engine does not answer here. You cannot check it                                                                                                    |
| **English only**                                    | Google AI Mode answers in English only                                                                                                                  |
| **Support not checked**                             | SEO Utils could not read the engine's list, for example without DataForSEO credentials. You can still check the engine                                  |

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d83ec219df88cced099633146c0a88854339dfc3%2Fllm-rank-tracker-ai-engines.png?alt=media" alt="AI engines list with China selected"><figcaption><p>(1) Gemini answers in China. (2) ChatGPT does not, so it is disabled. (3) The note under the list</p></figcaption></figure>

When you change the location or language, a checked engine that does not answer there is unchecked, and a note under the list names it. It is checked again when you pick a location and language it answers for, unless you changed it yourself in the meantime.

{% hint style="info" %}
**Editing a tracker**: The location and language of a tracker cannot change. An engine the tracker already runs stays checked even when it is not offered there, so you can clear it.
{% endhint %}

#### Schedule Configuration

**Schedule Frequency**: Determines how often the tracker runs automatically.

**How Scheduling Works**:

* First run happens immediately when you create the tracker
* Subsequent runs occur at the scheduled interval
* SEO Utils must be open for scheduled runs

{% hint style="success" %}
**Recommended Schedules**:

* **On-demand (0)**: Manual runs only
* **Daily (1)**: For competitive industries or active campaigns
* **Weekly (7)**: For stable markets with regular monitoring needs
* **Monthly (30)**: For long-term trend analysis or low-competition niches
  {% endhint %}

After filling all fields, click "Create Tracker". The system will redirect you to the tracker detail page

## Managing Your LLM Rank Tracker

Once your tracker is created and running, you'll need to manage various aspects to maintain effective tracking.

### Understanding the Report Header

The report header provides essential information at a glance:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-249738c42f020f514f08f47a821a25fa72883abb%2FCleanShot%202025-07-21%20at%2016.14.19%402x.png?alt=media" alt=""><figcaption><p>LLM Rank Tracker report header with key metrics</p></figcaption></figure>

1. **Report Title**: Shows your Main brand name (the first brand variant)
2. **Edit Button**: Quick access to modify tracker settings
3. **Key Metrics Bar**:

* Brand variants count with list on hover
* AI engines count with details on hover
* Search terms count (clickable)
* Snapshots count (clickable)
* Last updated timestamp with next run on hover

### Running the Tracker Manually

To run the tracker outside of its schedule:

1. **Click "Run Tracker"** button in the top-right
2. **Confirm in the modal** showing:

* Number of brand variants
* Total search terms
* AI engines to query

3. **Monitor progress** in the Log Panel
4. **Wait for completion** notification

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c4ba937c16bf7ed3e242e441159db4d72bb878de%2FXnapper-2025-07-21-16.14.52.png?alt=media" alt=""><figcaption><p>Run tracker confirmation modal</p></figcaption></figure>

{% hint style="success" %}
**Important:** SEO Utils caches DataForSEO results and OpenAI extraction data, so you won't be charged twice for re-running the same queries.
{% endhint %}

### Updating Brand Variants (for Example After a Rebrand)

You can change your brand variants at any time. SEO Utils then re-checks all previously collected data against the new list, without asking the AI engines again.

{% stepper %}
{% step %}

#### Open the Tracker Settings

Click the **Edit** button (pencil icon) next to the report title.
{% endstep %}

{% step %}

#### Update Your Brand Variants

* Type the new name in **Brand Variants** and press Enter
* Click the star (☆) on the name you want as your **Main** name
* Keep older names in the list so past mentions still count as your brand

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F7swza9yuTyyuWwsEm8Ce%2FXnapper-2026-09-24-16.53.29.png?alt=media&amp;token=3eb9cb44-d34a-48a8-99fe-56ebaa936cf7" alt="" width="563"><figcaption><p>Edit LLM Rank Tracker page with a new brand name set as Main and the previous name kept as a variant</p></figcaption></figure>
{% endstep %}

{% step %}

#### Save the Changes

Click **Update Tracker**. Your brand's metrics in every tab now include all of its names.
{% endstep %}
{% endstepper %}

**What changes and what does not**:

* ✅ All past answers are re-checked, so every name in your list counts as your brand
* ✅ New AI answers are recorded under your Main name
* ❌ Past answers keep the name they were recorded under. In the Responses view and the extracted mentions you may still see an older name, but it is counted as your brand
* ❌ No AI engine is queried again, so an edit costs nothing

{% hint style="info" %}
**Editing while the tracker runs**: If you change brand variants while a run is in progress, the run re-checks your brand at the end, so answers collected after your edit are counted correctly too.
{% endhint %}

### Managing Search Terms

Access search term management by clicking the **search terms count** in the header.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4ba8e5031e03052e8cbe41d15570da67351b7efa%2FCleanShot%202025-07-21%20at%2016.17.43%402x.png?alt=media" alt=""><figcaption><p>Search terms management page</p></figcaption></figure>

#### Adding Prompts from AI Visibility

You can also add prompts you find in [AI Visibility](/guide/ai-visibility). On its **Prompts** tab, select the prompts, click **Track in LLM Rank Tracker** and choose **Add to an existing report**. Prompts the report already tracks are skipped, and the new ones are tracked from its next run. See [Track Prompts in LLM Rank Tracker](/guide/ai-visibility#track-prompts-in-llm-rank-tracker).

#### Organizing with Tags

Tags help categorize search terms for better analysis:

**Creating Tags**:

1. Select search terms using checkboxes
2. Click "Update Tags" from bulk actions
3. Add relevant tags:

* By intent: "informational", "commercial", "comparison"
* By product: "rank-tracker", "serp-clustering"
* By competition: "vs-competitor", "alternative-searches"
* By priority: "high-priority", "monitoring"

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5b2dfc2daecd5958a8d293c87d4fcb6e57286a21%2FXnapper-2025-07-21-16.19.07.png?alt=media" alt=""><figcaption><p>Search terms organized with multiple tags</p></figcaption></figure>

### Managing Snapshots

Snapshots represent daily tracking data points. Access via the snapshots count in the header.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-38992850556ddb8d807f2cd8e56b73010f55857b%2FXnapper-2025-07-21-16.19.46.png?alt=media" alt=""><figcaption><p>Visit the snapshots management</p></figcaption></figure>

#### Understanding Snapshots

**Key Concepts**:

* One snapshot per day maximum
* Re-running on the same day updates existing snapshot
* Each snapshot contains all search term results
* Deleting a snapshot removes all associated data

#### Managing Snapshot Data

**Viewing Details**:

* Snapshots are listed newest first
* Use date sorting to find specific periods
* Search by date using the search box

**Deleting Snapshots**:

1. Click the three-dot menu on a snapshot
2. Select "Delete"
3. Confirm deletion (irreversible)

{% hint style="danger" %}
**Warning**: Deleting a snapshot permanently removes:

* All position data for that date
* Associated citations and sources
* Sentiment analysis results
* Competitor data for that date
  {% endhint %}

### Manage Responses

View the exact AI responses captured for each search term. To access the list of responses, click the "Response" menu item from the "3 dots" dropdown.

You can click on the search term to see:

* Full AI response content with formatting
* Referenced URLs and sources
* Extracted brand mentions with positions
* Copy buttons for easy export

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0fc5e7886997feb8f1a883684667bb747a8a9cfc%2FXnapper-2025-07-21-16.23.54.png?alt=media" alt=""><figcaption></figcaption></figure>

**Use Cases**:

* Verify how AI describes your brand
* Analyze competitor positioning
* Check citation sources
* Understand sentiment context

{% hint style="info" %}
**Tip**: Red search terms indicate no AI content was found for that query.
{% endhint %}

**Gemini Model**: A Gemini answer shows the model the Gemini app used, for example "3.5 Flash-Lite". When the model differs from the previous check of the same search term, the answer is marked **Model changed**: a ranking change there may come from the new model, not from your content.

## Understanding the Report Tabs

The LLM Rank Tracker provides four comprehensive analysis tabs, each offering unique insights into your brand's AI visibility.

### Date Range Filter & Comparison Data

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6cb4b7ed1c90b45e9a00e464fd263b174f8da839%2FXnapper-2025-07-21-16.54.26.png?alt=media" alt="Date range filter" width="563"><figcaption><p>The global date range filter</p></figcaption></figure>

You can choose from preset date ranges like *Last 7 Days, Last 30 Days*, or set a *custom range*.

To enable comparison, switch to the **Compare** tab. There, you can select options like *Previous Period, Year Over Year, or set a Custom Comparison Range.*

The date range filter will apply to all the following tabs below:

### Overview Tab: Brand Performance Metrics

The Overview tab provides a high-level view of your brand's performance across AI platforms.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0773b183cde7b67ad76daac0299a6efa0029d52f%2FCleanShot%202025-07-21%20at%2016.25.16%402x.png?alt=media" alt=""><figcaption><p>Overview tab showing key performance metrics</p></figcaption></figure>

#### Key Performance Indicators (KPIs)

**1. Visibility**

* **Definition**: How often your brand appears in AI responses
* **Calculation**: (Queries with brand mention / Total queries) × 100
* **Good benchmark**: 20-30% for branded searches, 5-10% for non-branded

**2. Top 3 Visibility**

* **Definition**: Percentage of queries where your brand ranks in the top 3 positions
* **Calculation**: (Queries where brand ranks 1-3 / Total queries) × 100
* **Indicates**: How prominently your brand appears when mentioned

**3. Average Position**

* **Definition**: The average position across all queries in the selected date range where your brand was mentioned
* **Range**: 1-10+ (lower numbers indicate better visibility)
* **Position 0**: Not mentioned in the response
* **Several brand names in one answer**: If one AI answer mentions your brand under two of its names, only the better position counts

**4. Latest Position**

* **Definition**: The average position from the snapshot closest to your selected end date
* **Purpose**: Shows your most recent performance within the date range
* **Use case**: Quickly assess current standing without changing date ranges

#### Secondary Metrics

Below the primary KPIs, you'll find three additional metrics that provide deeper insights:

**1. Sentiment Score**

* **Definition**: Average sentiment of your brand mentions (0-100 scale)
* **Calculation**: Converts sentiment from -1 to +1 range to 0-100 scale
* **Range**: 0 (very negative) to 100 (very positive)
* **Good benchmark**: 70+ indicates positive brand perception

**2. Total Citations**

* **Definition**: Number of cited sources that mention your brand
* **What it measures**: How many URLs/sources referenced by AI contain mentions of your brand
* **Calculation**: Count of citations where your brand appears in the cited content
* **Importance**: More citations = stronger brand presence in AI's source material

**3. Detection Rate**

* **Definition**: Percentage of search terms where your brand appears
* **Calculation**: (Search terms with brand mentions / Total search terms) × 100
* **What it shows**: How many of your tracked queries mention your brand
* **Good benchmark**: Higher percentage = better brand coverage

#### Performance Chart

The line chart visualizes your selected metrics over time, comparing your brand against top competitors.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d3352acd9227d6c850e098374bbf8c68b6ea5af9%2FCleanShot%202025-07-21%20at%2016.27.13%402x.png?alt=media" alt=""><figcaption><p>Performance chart with metric selector</p></figcaption></figure>

**Metric Selection**: Use the dropdown to switch between different KPIs and metrics:

* Visibility Score (default)
* Average Position
* Top 3 Visibility
* Sentiment Score
* Citations Count
* Detection Rate

**Chart Features**:

* **Blue line**: Your brand's performance
* **Colored lines**: Top 10 competitors. The chart automatically selects the top 10 competitors based on your chosen metric. This means you're always comparing against the most relevant competition for each specific measurement.

{% hint style="info" %}
**Note**: For Average Position, trends are inverted—a downward movement is positive since lower positions are better.
{% endhint %}

#### Search Terms Performance Table

The table shows how your brand performs for each tracked search term:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e9cf9ac658f3c208c07ce9ffe3f102e49ab8f31b%2FXnapper-2025-07-21-16.28.17.png?alt=media" alt=""><figcaption><p>Search terms table with performance metrics</p></figcaption></figure>

**Key Metrics**:

* **Avg. Position**: Average ranking across all AI engines (lower is better)
* **Visibility**: Percentage of AI engines mentioning your brand
* **Sentiment**: Tone of mentions (0-100 scale)
* **Citations**: Number of sources referencing your brand
* **Individual AI Engines**: Position in each platform

**Using the Table**:

* Sort by any column to find opportunities
* Filter by position range to focus on specific rankings
* Search for specific terms or groups
* Compare periods to track progress

**Competitor Filter**: The table includes a Competitor filter that allows you to view performance data for specific competitors instead of just your brand:

* By default, the table shows data for your brand
* Select any competitor from the dropdown to see their performance metrics
* This helps you benchmark competitor visibility and identify gaps in their coverage

{% hint style="info" %}
**Competitor Analysis**: Use the competitor filter to analyze which search terms your competitors rank well for, their average positions, and sentiment scores. This intelligence helps you identify opportunities where competitors are weak or absent.
{% endhint %}

{% hint style="success" %}
**Quick Tip**: Focus on terms with positions 4-6—these are easiest to improve to top 3.
{% endhint %}

### Competitors Tab: Competitive Intelligence

The Competitors tab reveals who else appears in AI responses for your tracked queries.

#### Competition Map (Scatter Plot)

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-50f2b971510a5b394d2e8075492484c81b7bd49b%2FCleanShot%202025-07-21%20at%2016.32.40%402x.png?alt=media" alt=""><figcaption><p>Competition Map showing brand and competitor positioning</p></figcaption></figure>

**What does it show?**

* The **x-axis** represents the **Detection Rate (%)** - how consistently a brand appears across all tracked search terms.
* The **y-axis** represents the **Average Position** of a brand across all its mentions.
* The **size of each bubble** represents the overall **visibility** of the brand. A larger bubble indicates higher visibility.
* The **color** represents different brands for easy differentiation.
* **Your brand** is one blue bubble, marked **(You)** in the list next to the map. It combines every name your brand was recorded under and is labelled with your Main name.

**How to read it?**

* **Bottom-right corner (low average position & high detection rate)** → This means a brand appears consistently and ranks well (closer to position #1).
* **Top-left corner (high average position & low detection rate)** → This means a brand appears sporadically and ranks poorly.
* **Large bubbles** → These indicate brands with strong visibility across many queries.
* **Small bubbles** → These brands have lower presence in AI responses.

{% hint style="success" %}
**Key benefits of the scatter plot**

* **Identify market leaders** → Look for large bubbles in the bottom-right corner.
* **Spot opportunities** → Find areas with few competitors or weak positioning.
* **Track competitive movement** → Monitor how positions shift over time.
  {% endhint %}

{% hint style="info" %}
**Tips:**

* **Minimap Toggle**: Enables zooming and panning for detailed analysis.
* **Hovering Over a Bubble**: Displays detailed metrics including visibility score, total mentions, and trends.
  {% endhint %}

#### Competitors Performance Table

Detailed metrics for each competitor:

**Key Metrics Explained**:

1. **Visibility %**:

* How often they appear vs. total queries
* Higher percentage = stronger AI presence
* Compare to your own visibility

2. **Total Mentions**:

* Raw count of appearances
* Indicates content volume recognized by AI

3. **Average Position**:

* Their typical ranking when mentioned
* Lower numbers = more prominent placement

4. **Detection Rate**:

* Consistency of appearances over time
* 100% = mentioned every day tracked
* Lower % = sporadic mentions

5. **Top 3 Rate**:

* Percentage of mentions in positions 1-3
* Indicates prominence in AI responses

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-28b6a501c4b21fc72b1a71670caf5b5d1c004c77%2FXnapper-2025-07-21-16.33.38.png?alt=media" alt=""><figcaption><p>Competitors table with sortable columns</p></figcaption></figure>

**Competitive Analysis Strategies**:

1. **Identify Direct Threats**:

* High visibility + good positions
* Consistent detection rates
* Growing trend lines

2. **Find Opportunities**:

* Competitors with declining metrics
* Gaps where no one dominates
* Queries with weak competition

3. **Learn from Leaders**:

* Study their content strategy
* Analyze their cited sources
* Understand their positioning

{% hint style="info" %}
**Competitor Discovery**: The system automatically identifies competitors from AI responses. You don't need to manually add them—anyone mentioned alongside your search terms appears here.
{% endhint %}

{% hint style="info" %}
**Your Brand Is One Row**: Your brand appears once in this table, even when AI answers used several of its names (for example an old and a new name after a rebrand). Its metrics count every one of those names. If a name of your brand still shows up as a competitor, add it to your [brand variants](#updating-brand-variants-for-example-after-a-rebrand).
{% endhint %}

{% hint style="warning" %}
**Merging Competitors**: When you merge competitors, the new name cannot be one of your brand names. To count a name as your brand, add it as a brand variant instead.
{% endhint %}

### Citations Tab: Source Authority Analysis

The Citations tab reveals which sources AI engines reference when responding to your tracked queries, helping you understand the authority landscape in your industry.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-724fa3201f16325cdb9d79f612488b3ac7e6ba75%2FXnapper-2025-07-21-16.34.43.png?alt=media" alt=""><figcaption><p>Citations tab showing comprehensive source analysis</p></figcaption></figure>

#### Citation Metrics Overview

At the top of the tab, five key metrics provide a snapshot of citation patterns:

**Key Metrics**:

1. **Total Citations**: Total number of links found across all AI responses for your tracked search terms
2. **Unique URLs**: Number of distinct URLs cited across all domains (not limited to your website)
3. **Unique Domains**: Number of distinct domains that received citations in AI responses
4. **Brands Found**: Number of distinct brands detected in the citations, including yours and competitors. Your brand counts once, whatever names it appears under
5. **Most Appearances**: The highest number of times any single URL was cited

{% hint style="info" %}
**Understanding Citation Metrics**: These metrics help you gauge the diversity and concentration of sources AI engines trust. A high "Most Appearances" number indicates certain pages are heavily favored by AI.
{% endhint %}

#### Citation Analysis Charts

Two visualization charts help you understand citation patterns:

1. **Top 20 Citations by Domain**: Bar chart showing which domains are cited most frequently
2. **Daily Mentions by Top Domains**: Line chart tracking citation trends over time for the most cited domains

#### URL Overview Tab

The URL Overview provides a detailed list of all cited URLs with rich context:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7d0dd1af6f6f80ba773b3baa4052b18376941582%2FXnapper-2025-07-21-16.36.01.png?alt=media" alt=""><figcaption><p>URL Overview showing individual citations</p></figcaption></figure>

**Table Information**:

* **Citation URL**: The specific page cited (with title when available)
* **Search Term**: Which query triggered this citation
* **Mentioned Brands**: Brands associated with this citation. Your brand is highlighted and listed once, under your Main name
* **AI Engine**: Which AI platform cited this URL
* **Found On**: When the citation was first discovered

**Filtering Options**:

* Filter by AI Engine
* Filter by Mentioned Brands. Selecting your Main name shows every citation of your brand, under any of its names
* Search across URLs and search terms

#### Domain Overview Tab

The Domain Overview aggregates citations by domain, showing the bigger picture:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e62882c57486cb083845703a9a648af7c1104cfe%2FXnapper-2025-07-21-16.36.49.png?alt=media" alt=""><figcaption><p>Domain Overview with expandable details</p></figcaption></figure>

**Table Information**:

* **Domain**: Website domain with citation bar visualization
* **URLs**: Number of unique pages cited from this domain (click to expand)
* **Citations**: Total citation count with percentage share

**Expandable Details**: Click the URL count to see:

* All specific pages cited from that domain
* Citation count per page
* AI engines that cited each page
* Associated brands per citation

#### Strategic Insights from Citations

**Why Citations Matter**:

1. **Authority Signals**: Frequently cited sources are considered authoritative by AI
2. **Content Opportunities**: Identify which types of content get cited
3. **Partnership Targets**: Find websites for potential collaborations
4. **Competitive Intelligence**: See where competitors get their authority

**Action Items Based on Citation Data**:

1. **Create Content on Cited Domains**: If certain domains dominate citations, consider guest posting or partnerships
2. **Analyze Cited Content**: Study what makes content "citation-worthy"
3. **Build Relationships**: Connect with editors and authors of frequently cited sources
4. **Fill Citation Gaps**: Create authoritative content where citations are lacking

{% hint style="success" %}
**Citation Strategy**: Focus on domains that appear in both the "Top Citations" chart and have high brand association. These represent the most valuable opportunities for building your AI visibility through strategic content placement.
{% endhint %}

### Sentiment Tab: Brand Perception Analysis

The Sentiment tab analyzes how AI platforms perceive and present brands in their responses, tracking sentiment scores over time and across different queries.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a9e67d68669e1acd9e21d998d228978cf4d9a9cd%2FCleanShot%202025-07-21%20at%2016.38.35%402x.png?alt=media" alt=""><figcaption><p>Sentiment analysis tab</p></figcaption></figure>

#### Sentiment Over Time by Brand

The line chart visualizes sentiment trends for each brand across the selected date range:

**Chart Features**:

* **Multiple brand lines**: Each brand gets its own colored line. Your brand is a single line labelled with your Main name and **(You)**
* **Sentiment scale**: 0-100 (normalized from -1 to +1 scale)
* **Interactive tooltips**: Hover to see exact sentiment scores

**Understanding Sentiment Scores**:

* **80-100**: Very positive sentiment
* **60-80**: Positive sentiment
* **40-60**: Neutral sentiment
* **20-40**: Negative sentiment
* **0-20**: Very negative sentiment

#### Sentiment Analysis by Brand Table

Below the chart, a comprehensive table breaks down sentiment metrics for each brand:

**Table Columns**:

1. **Brand**: Brand name with building icon for your brand
2. **Source**: AI engine that provided the sentiment data
3. **Sentiment**: Overall sentiment score with emoji indicator

* 😊 Positive (60%+)
* 😐 Neutral (40-60%)
* 😟 Negative (<40%)

4. **Positive/Neutral/Negative**: Count of mentions by sentiment type
5. **Mentions**: Total number of brand mentions

Your brand is one row that combines all of its names. The table shows 50 brands per page; use the page controls below it to see the rest.

**Expandable Keyword Analysis**: Click the brand to reveal detailed keyword-level sentiment. For your brand, this includes mentions under all of its names:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4da810d0d616927d69aa5a5a3a94762d46f126c0%2FXnapper-2025-07-21-16.39.29.png?alt=media" alt=""><figcaption><p>Expanded view showing sentiment by individual keywords</p></figcaption></figure>

The expanded view shows:

* **Search Term**: The specific query
* **Sentiment Score**: Score for that keyword-brand combination
* **Response Context**: Actual text where the brand was mentioned
* **AI Engine**: Which platform generated this response

This granular view helps you:

* Identify which queries generate positive/negative sentiment
* Read exact AI responses about your brand
* Spot opportunities to improve brand perception
* Compare sentiment across different AI engines

#### How Sentiment Analysis Works

**Text Analysis Process**:

1. **Text Extraction**: When a brand is mentioned in an AI response, the system extracts the specific text segment containing the brand mention
2. **Google NLP Processing**: The extracted text is sent to Google's Natural Language API for sentiment analysis
3. **Sentiment Scoring**: Google NLP returns a sentiment score ranging from -1 (very negative) to +1 (very positive)
4. **Score Normalization**: The system converts this to a 0-100 scale for easier interpretation

**What Text is Analyzed**:

* The actual text snippet where your brand is mentioned in the AI response
* Context around the brand mention is included for accurate sentiment detection
* Each brand mention is analyzed separately if multiple mentions exist

**Supported Languages for Sentiment**: Sentiment analysis is currently available for:

* English (en)
* Spanish (es)
* French (fr)
* German (de)
* Italian (it)
* Portuguese (pt)
* Japanese (ja)
* Korean (ko)
* Chinese (zh, zh-CN, zh-TW)
* Russian (ru)

{% hint style="info" %}
**Note**: If Google NLP API Key is not configured or if the content is in an unsupported language, sentiment scores will show as N/A and sentiment analysis will be skipped.
{% endhint %}

#### Strategic Insights from Sentiment Analysis

**Sentiment Monitoring Benefits**:

1. **Brand Health Tracking**: Monitor overall brand perception in AI responses
2. **Competitive Benchmarking**: Compare your sentiment against competitors
3. **Issue Detection**: Quickly spot queries generating negative sentiment
4. **Content Strategy**: Focus on improving content for problematic queries

**Action Items Based on Sentiment**:

1. **For Negative Sentiment**:

* Review the specific queries and responses
* Update content to address concerns
* Create positive content around those topics
* Monitor improvements over time

2. **For Neutral Sentiment**:

* Add more compelling value propositions
* Include customer success stories
* Highlight unique benefits

3. **For Positive Sentiment**:

* Amplify successful messaging
* Use similar tone in other content
* Leverage positive AI responses in marketing

{% hint style="warning" %}
**Sentiment Alert**: Pay special attention to queries where your brand has significantly lower sentiment than competitors. These represent immediate opportunities for improvement through better content and messaging.
{% endhint %}

{% hint style="info" %}
**Note**: Sentiment analysis is currently available for AI engines that provide detailed responses. As we add more AI platforms, sentiment tracking will expand accordingly.
{% endhint %}

## Practical Use Cases and Strategies

### Use Case 1: Brand Launch and Awareness Tracking

**Scenario**: You're launching a new brand or product and need to establish AI visibility from zero.

**Strategy**:

1. **Baseline Setup**: Initial search terms:

* What is \[brand name]
* \[Brand] reviews
* \[Brand] vs alternatives
* \[Product category] solutions
* Best \[product type] for \[use case]

2. **Track with these metrics**:

* **Detection Rate**: Start at 0%, aim for 20%+ in 3 months
* **Visibility Score**: Monitor weekly growth
* **Sentiment**: Ensure positive from the start

3. **Optimization Actions**:

* Create comprehensive "About" content
* Publish on domains with high citation rates
* Build comparison pages vs. established brands
* Monitor which content gets cited first

**Success Metrics**:

* Week 1-4: First mentions appear
* Month 2: 10%+ detection rate
* Month 3: Consistent citations from authority domains

### Use Case 2: Competitive Displacement Strategy

**Scenario**: A competitor dominates AI responses in your category.

**Strategy**:

1. **Analysis Phase** (Use Competition Map):

* Identify their detection rate and average position
* Export their top-cited URLs from Citations tab
* Study their sentiment scores by keyword

2. **Target Their Weaknesses**:

* Find keywords where they have low/negative sentiment
* Identify gaps in their citation coverage
* Look for outdated information in their cited content

3. **Content Creation Plan**:

* Create superior content on their top-cited domains
* Target keywords where they rank 4-6 (easier to displace)
* Build relationships with sites that cite them

4. **Track Progress**:

* Monitor position changes in head-to-head queries
* Track citation share shifts
* Compare sentiment scores weekly

### Use Case 3: Reputation Crisis Management

**Scenario**: Negative sentiment appears in AI responses about your brand.

**Immediate Response**:

1. **Identify Scope** (Sentiment Tab):

* Filter by negative sentiment (<40%)
* Expand keywords to see exact responses
* Check which AI engines show negative content

2. **Source Analysis** (Citations Tab):

* Find which URLs drive negative mentions
* Identify if it's from news, reviews, or forums
* Check citation frequency of negative sources

3. **Response Strategy**:

* Create authoritative response content
* Update cited pages if you control them
* Publish on high-authority domains
* Monitor daily until sentiment improves

**Tracking Recovery**:

* Daily sentiment monitoring
* Citation source changes
* Position improvements for affected queries

### Use Case 4: Product Feature Optimization

**Scenario**: Determine which features to highlight based on AI visibility.

**Strategy**:

1. **Feature-Specific Tracking**: Search terms by feature:

* \[Brand] \[feature] review
* How does \[brand] \[feature] work
* \[Brand] \[feature] vs \[competitor]
* Best \[product] with \[feature]

2. **Analyze Performance** (Overview Tab):

* Which features get mentioned most?
* Which have highest positions?
* Which generate positive sentiment?

3. **Citation Analysis**:

* Which features get cited from authority sites?
* Are technical specs or benefits cited more?

4. **Optimization**:

* Double down on well-performing features
* Improve content for underperforming features
* Create comparison content for strong features

### Use Case 5: Multi-Location Brand Management

**Scenario**: Managing brand visibility across different geographic markets.

**Setup**:

1. **Create Location-Specific Trackers**:

* One tracker per major market
* Pick the right Location for each market
* Include localized search terms

2. **Location-Specific Queries**:

* Best \[product] in \[city]
* \[Brand] \[location] reviews
* \[Service] near me (with a city as the Location, Google AI Mode only)
* \[Brand] vs local competitors

3. **Comparative Analysis**:

* Compare visibility scores across locations
* Identify market-specific competitors
* Track sentiment variations by region

4. **Localization Strategy**:

* Create location-specific content
* Build local citations
* Address regional concerns

## Best Practices and Optimization Tips

### Setting Up Effective Tracking

#### 1. Search Term Strategy

**The 70-20-10 Rule**:

* **70% Core Terms**: Direct brand and product searches
* **20% Competitive**: Comparison and alternative queries
* **10% Exploratory**: Broad industry and problem-solving queries

**Search Term Templates**: Brand Searches:

* \[brand] review
* is \[brand] worth it
* \[brand] pricing
* \[brand] customer service

Comparison Searches:

* \[brand] vs \[competitor]
* \[brand] alternatives
* better than \[brand]
* \[brand] or \[competitor]

Problem Searches:

* how to \[solve problem]
* best way to \[achieve goal]
* \[industry] tools for \[use case]
* \[problem] solution

#### 2. Metric-Driven Optimization

**Weekly Review Checklist**:

* [ ] Check Performance Chart for all key metrics
* [ ] Review new competitors in Competition Map
* [ ] Analyze new citations in Citations Tab
* [ ] Monitor sentiment changes
* [ ] Export data for team reports

**Monthly Analysis**:

1. **Visibility Trends**:

* Compare month-over-month visibility scores
* Identify fastest-growing competitors
* Track market share changes

2. **Citation Patterns**:

* New domains citing content
* Changes in citation concentration
* Opportunities for guest content

3. **Sentiment Shifts**:

* Overall brand perception trends
* Keyword-specific sentiment changes
* Competitive sentiment comparison

### Advanced Optimization Techniques

#### 1. Citation Optimization Strategy

**Build Citation Authority**:

1. **Analyze Top Cited Domains** (Citations Tab):

* Sort by citation count
* Identify accessible platforms
* Study cited content types

2. **Content Placement Priority**:

* **Tier 1**: Domains with 50+ citations
* **Tier 2**: Domains with 20-49 citations
* **Tier 3**: Emerging domains with growth

3. **Citation-Worthy Content**:

* Comprehensive guides with clear sections
* Data-driven research and statistics
* Comparison tables and matrices
* Step-by-step tutorials
* Expert quotes and insights

#### 2. Position Improvement Tactics

**For Positions 4-6** (Quick Wins):

1. Identify these positions in Overview Tab
2. Check current citations for these queries
3. Create content on higher-authority domains
4. Add structured data markup
5. Update existing content with fresh data

**For No Visibility** (Position 0):

1. Analyze competitors who rank
2. Check their citation sources
3. Create foundational content
4. Build topic authority gradually
5. Target long-tail variations first

#### 3. Sentiment Optimization

**Improving Negative Sentiment**:

1. **Identify Root Causes**:

* Expand keywords in Sentiment Tab
* Read actual AI responses
* Find common negative themes

2. **Content Response Strategy**:

* Address concerns directly
* Provide updated information
* Share positive customer stories
* Create FAQ content

3. **Monitor Progress**:

* Daily sentiment tracking
* A/B test messaging approaches
* Track which content improves sentiment

#### 4. Competitive Intelligence Framework

**Weekly Competitive Analysis**:

1. **Competition Map Review**:

* Screenshot weekly positions
* Track movement patterns
* Identify rising competitors

2. **Citation Competitive Analysis**:

* Compare domain overlap
* Find exclusive citation sources
* Track citation velocity

3. **Sentiment Benchmarking**:

* Compare sentiment by keyword
* Identify perception gaps
* Find differentiation opportunities

### ROI Measurement and Reporting

#### Executive Dashboard Metrics

**Primary KPIs**:

1. **Visibility Score**: Overall brand presence
2. **Share of Voice**: Your visibility vs. total market
3. **Sentiment Index**: Average sentiment across queries
4. **Citation Authority**: Unique domains citing you

**Calculated Metrics**: Share of Voice = (Your Mentions / Total Market Mentions) × 100 Citation Quality Score = (Citations from Top 20 Domains / Total Citations) × 100 Sentiment Advantage = Your Avg Sentiment - Competitor Avg Sentiment

#### Reporting Best Practices

**Weekly Reports Should Include**:

* Visibility score with week-over-week change
* Top 5 position improvements
* New citations acquired
* Sentiment alerts (if <40%)

**Monthly Reports Should Include**:

* Comprehensive competitor analysis
* Citation growth trends
* Sentiment analysis by category
* Strategic recommendations

{% hint style="success" %}
**Pro Tip**: Create automated alerts for:

* Visibility drops >10%
* New competitors with >20% detection rate
* Sentiment scores below 40%
* Loss of citations from top domains
  {% endhint %}

### Common Pitfalls to Avoid

1. **Over-Optimizing for Current AI Behavior**:

* AI algorithms evolve rapidly
* Focus on quality content, not tricks
* Build genuine authority

2. **Ignoring Competitor Innovations**:

* Weekly Competition Map reviews are essential
* New entrants can disrupt quickly
* Learn from competitor successes

3. **Neglecting Citation Diversity**:

* Don't rely on single domains
* Build broad citation portfolio
* Maintain content freshness

4. **Reactive vs. Proactive Approach**:

* Don't wait for problems
* Anticipate market changes
* Test new content formats

{% hint style="info" %}
**Remember**: AI visibility is dynamic. What works today may change tomorrow. Focus on building genuine authority, creating helpful content, and maintaining strong sentiment across all touchpoints.
{% endhint %}


# AI Visibility

AI Visibility shows how often AI answers (Google AI Overviews and ChatGPT) name your brand compared with your competitors, and where they win instead of you. Every number leads to the real prompts and answers behind it, and to the sites AI cites.

It reads DataForSEO's database of real AI answers, so you don't write a prompt list first. Type a website or brand name and the results arrive in seconds. When you have your findings, [export them as CSV files](#exporting-to-csv) or hand a client a [ready-made report](#client-report).

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-19a62685b5b8059e122dc1e40bf573b9fb31e9aa%2Fai-visibility-overview.png?alt=media" alt=""><figcaption><p>The Overview of an exploration: the four key numbers, share of voice, where rivals win and the share over time</p></figcaption></figure></div>

{% hint style="info" %}
**AI Visibility or** [**LLM Rank Tracker**](/guide/llm-rank-tracker)**?** AI Visibility reads answers DataForSEO has already collected. It doesn't run your prompts. The LLM Rank Tracker runs your own prompts on a schedule. Use AI Visibility to find the prompts worth tracking, then [send them across](#track-prompts-in-llm-rank-tracker).
{% endhint %}

## What You Need

* **A DataForSEO login or an SEO Utils rental key.** Add your own API credentials in **Settings > Services > DataForSEO Settings**. See [SEO Data Source](/guide/seo-data-source#how-to-connect-your-dataforseo-account-to-seo-utils). AI Visibility can also run on your SEO Utils rental credits instead of your own login: see [Rent DataForSEO API Key](/guide/rent-dataforseo-api-key#use-your-credits-for-ai-visibility). Without either, the AI Visibility page shows the setup steps instead of the form.
* **Sandbox Mode turned off** when you use your own login. Sandbox Mode returns dummy data, so AI Visibility refuses to run while it is on. Turn it off in the same settings.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-73ed6e20b6e493817d5ecf5bd7b57621fe59c3ad%2Fai-visibility-credentials.png?alt=media" alt=""><figcaption><p>Open <strong>AI Era > AI Visibility</strong> (1). Without credentials, the page lists the setup steps, and the last one (2) opens the settings</p></figcaption></figure>

AI Visibility is available in the desktop app. With [Remote Access](/guide/remote-access), you and the [team members](/guide/team) you invite can also [use it in the browser](#using-ai-visibility-in-the-browser). Your DataForSEO login or rental key stays on your computer, so you add or change it in the desktop app.

## What It Costs

DataForSEO bills your account about $0.10 per request. On a rental key, the same prices are taken from your rental credits instead. Every price SEO Utils shows is an upper bound: you pay only for the requests that are actually sent.

| What you do                                                                                       | Cost                                                                                                                                                                                           |
| ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Reopen an exploration, switch platform on the Overview, open an answer, open **Sources by brand** | Free                                                                                                                                                                                           |
| Load anything already fetched this week                                                           | Free                                                                                                                                                                                           |
| **Explore** (the first load) or **Refresh**                                                       | Up to the price on the button. For example, six brands in the United States show up to about $1.65, or about $0.43 for a Refresh in the second week ([why](#how-long-share-over-time-is-kept)) |
| Find competitor suggestions                                                                       | About $0.10, not counted in **Spent**                                                                                                                                                          |
| Open **Prompts** or a page list on **Citations**                                                  | The price shows in the toolbar while it loads. Above 10 requests or $1.00 it asks first                                                                                                        |
| **Save changes** in **Edit brands**                                                               | Free. The next load pays only for what is new                                                                                                                                                  |
| **Export shares & gaps CSV**, **Export as HTML**, **Download PDF**, **Print or save as PDF**      | Free                                                                                                                                                                                           |
| **Export citations CSV**, **Export prompts as CSV**                                               | Free for what is already loaded this week. Otherwise the dialog shows the price first                                                                                                          |
| Open the **Client report**                                                                        | Free when its top prompts are already loaded. Otherwise up to the price shown ([details](#client-report))                                                                                      |

**Results are cached per data week.** A data week runs from Monday to Sunday (UTC). Every number you fetch is reused for free by any exploration with the same brands, market and scope, until the next Monday. The first load of a new week pays again.

### How Long Share Over Time Is Kept

**Share over time** is the biggest part of the price, so SEO Utils keeps it in the cache for up to 2 weeks. Numbers fetched in one data week are reused for free through the next one. Everything else still refreshes weekly.

* It is never reused once a new calendar month (UTC) starts, because the new month would have no bar yet.
* A **Refresh** in the second week therefore costs about $0.43 instead of about $1.65 (six brands, United States).
* The note under the chart gives the date of its numbers, for example "Share over time from 9 Oct 2026 · kept up to 2 weeks to save cost". The [client report](#client-report) shows the same note.

To fetch fresh history, go to **Settings > Services > DataForSEO Local Cache**, click **"Clear Cache & History"**, then **Refresh**. This clears the cached answers of every DataForSEO tool, so the next loads in other tools pay again too.

## Starting an Exploration

{% stepper %}
{% step %}

#### Enter a Website or Brand Name

Go to **AI Era > AI Visibility**, type a **website or brand name** (1, for example `nike.com` or `Nike`), choose the **Market** (2), and click **"Continue"** (3).

* The market is one country and language, or **Worldwide**. It starts on your app's default location, else United States.
* Google AI Overviews covers every market in the list. ChatGPT covers the United States (English) only. On Worldwide it is labelled **ChatGPT · US only**. **How the data works** under the form explains the coverage.
* For a website, SEO Utils reads its home page to find the brand's name. You can edit the name on the next screen.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d473f98f2c1206ea362eed3af75a16656135edb9%2Fai-visibility-start.png?alt=media" alt=""><figcaption><p>The start page: the website or brand name (1), the market (2) and <strong>Continue</strong> (3). Your latest explorations are listed under <strong>Recent explorations</strong></p></figcaption></figure>
{% endstep %}

{% step %}

#### Review the Brands and Competitors

* **Your brand** (1): the **Brand name**, an optional **Website**, up to two **Other spellings** and an optional **Context term**. A brand without a website works, but its citations show "—".
* **Competitors** (2): SEO Utils suggests competitors found in AI answers, each with a badge (**Cited in your answers** or **Named with you on ChatGPT**) and an answer count. Tick up to five. The counter reads **2 of 5 selected**. Or click **"Add competitor"**. This lookup runs on **Continue** and costs about $0.10 the first time (**Finding competitors · \~$0.10**). It doesn't repeat by itself when you change the brand name or the scope. Click **"Suggest again"** to refresh the suggestions.
* **Market & scope** (3): the **Market**, **Answers collected in the last** 30, 90 (default), 180 days or **All time**, an optional **Topic** (only prompts whose question contains it count), and **Exclude branded prompts** (on by default). With it on, a prompt that already contains a brand's own name doesn't count for that brand.

{% hint style="info" %}
If a name is also a common word (for example "Target") or a phrase of two or three everyday English words ("New Balance", "Best Buy", "Whole Foods"), the review card and the Overview suggest a **Context term**, such as what the brand makes or does. Only answers that also contain the term are counted.

The hint reads, for example, "'New Balance' is also a common phrase. Add a context term, such as what the brand makes or does, to count only answers about the brand." It disappears once the brand has a context term. It checks English names only for now.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-dfd82eaabe32f1601b9e568ccf9fd2b453071fa7%2Fai-visibility-review.png?alt=media" alt=""><figcaption><p>The review card: your brand (1), the suggested competitors (2), the market and scope (3) and <strong>What this costs</strong> (4)</p></figcaption></figure>
{% endstep %}

{% step %}

#### Check the Price and Explore

**What this costs** (4) lists the requests per part (**Share of voice & citations**, **Where rivals win**, **Monthly history**, **AI search demand**) and a total. The button shows the same upper bound, for example **Explore · up to \~$0.11** when most numbers are already cached, or **Explore · free** when all of them are.

Click **"Explore"**. The Overview opens and fills in part by part.
{% endstep %}
{% endstepper %}

<details>

<summary>How names are matched</summary>

* A **mention** is one answer that names the brand, however many times it does.
* Upper and lower case don't matter, but accents do: "Müller" doesn't count "Muller". Add the other spelling under **Other spellings** to count both.
* A name of several words is matched as a phrase, in that order.

</details>

## The Exploration Header

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-83c80303b131c43977414d95a890ae1ca72ffefa%2Fai-visibility-header.png?alt=media" alt=""><figcaption><p>The exploration header: <strong>Edit brands</strong> (1), <strong>Actions</strong> (2), the scope settings (3), the data status and load button (4) and the tabs (5)</p></figcaption></figure>

* **Edit brands** reopens the review card with everything filled in, and the market can change here. **Save changes** spends nothing: the Overview shows **Needs refresh** until you load it, and the card shows what that costs.
* **Actions** has **Export shares & gaps CSV**, **Export citations CSV**, **Client report**, **Rename**, **Duplicate** (same brands, market and report settings, no saved results) and **Delete**. The first three are described under [Exporting to CSV](#exporting-to-csv) and [Client Report](#client-report).
* **The line under the name** holds the scope. The market is read-only. The window menu (**Last 90 days · since 7 Jul**), **Unbranded prompts** / **All prompts** and **Topic** each change the exploration, and each asks you to confirm the price first (**Apply and load**).
* **Data from** is when the saved results were fetched. It dates the parts a Refresh renews and leaves out the reused [Share over time](#how-long-share-over-time-is-kept), which has its own date on the chart. **Needs refresh** means the brands or scope changed since. **Spent** is what this exploration has cost, without competitor suggestions.
* The load button reads **Refresh · up to \~$X** when everything is current, and fetches every number again, cached ones included, except the Share over time that is still kept. When a part is missing or out of date it reads **Load · up to \~$X** and fetches only those parts.

While a load runs, the Overview shows its progress and a **Stop** button. Requests already sent still finish, and **Edit brands** and the scope settings wait.

## Overview

The platform control at the top is **All platforms**, **Google AI Overviews** or **ChatGPT**. ChatGPT only appears for the United States and Worldwide. Under **All platforms**, share of voice is the average of the platforms, and **Mentions** and **Citations** show each platform's count.

* **AI share of voice**: your share of the brand mentions among the brands in the exploration, with your rank (**#1 of 4**) and the change against three months earlier when there is enough data. An answer that names two brands counts for both, so it is a share of mentions, not of answers. **Low data** appears below 30 brand mentions.
* **Mentions**: answers that name you. **Citations**: answers that cite your website as a source ("—" without a website). **AI search demand**: monthly AI searches for your brand name (hidden on Worldwide).
* **Share of voice**: one bar per brand.
* **Where rivals win**: how many prompts name a rival and not you, then one strip per competitor with **They win**, **Both** and **You win**.
* **Share over time**: each brand's share per month. **Raw counts** shows mentions instead. Monthly counts follow how many answers DataForSEO collected that month, so the shares are the reliable trend. A note under the chart dates its numbers, because they are [kept for up to 2 weeks](#how-long-share-over-time-is-kept).
* **Countries** (Worldwide only): your top 10 countries. **Explore this market** asks for the price first.

With few mentions, **Try 180 days**, **Try all time** or **Try Worldwide** offers a wider scope with its price. With none, **Not in AI answers yet** shows the top prompts where the leading competitor appears and you don't (a small extra load of about $0.11, with its price shown) and the domains AI cites for your competitors.

Every number is a link. It opens the prompts or sources behind it.

## Prompts

The **Prompts** tab lists the real prompts behind a number, with the answer AI gave.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9484d2b48954a0e5b84b914c0eea2c512fb76703%2Fai-visibility-prompts.png?alt=media" alt=""><figcaption><p>The Prompts tab with the list picker open: <strong>Rivals win</strong>, <strong>You're mentioned</strong> and the <strong>They win / Both / You win</strong> counts of each competitor, for the platform shown</p></figcaption></figure>

* **List picker** (the first control): **Rivals win** (the default) is prompts that name a competitor and not you. **You're mentioned** is prompts that name you. For each competitor, **They win**, **Both** and **You win** open that group.
* **Platform**: **Google AI Overviews** or **ChatGPT**. A list shows one platform at a time, so under **All platforms** it shows Google.
* **Filters**: **Prompt** (contains or doesn't contain a word or phrase) and **AI volume** (minimum and maximum). Click **"Apply"** to load the filtered list.
* **Columns**: **Prompt**, **AI volume**, **Brands named**, **Your site cited**, **Sources**, **Last collected** and **First collected**. Sort by **AI volume** (default, highest first) or either date. AI volume estimates how often people ask a prompt. The platforms measure it differently, so compare it within one platform only.
* The count on the right (for example **124,051 prompts**) is exact. Pages go up to row 5,000, so refine the filters for longer lists. The download icon next to it [exports the list as CSV](#exporting-prompts).

**Cost.** Opening a list or a new page of it costs money unless it is cached, with the [limits above](#what-it-costs). The toolbar shows **Loading this list costs up to \~$0.20** while it loads. A bigger load asks first (**Load page** or **Cancel**). A list that reloads without a click, for example after **Edit brands**, never pays by itself. It shows **Not loaded** and a **Load list** button.

### The Answer Drawer

Click a prompt to open its answer. Opening it is free.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f9520653930e6a7a5d20e502d540f203e4223c6b%2Fai-visibility-answer-drawer.png?alt=media" alt=""><figcaption><p>The answer drawer: the prompt, its volume and dates, whether you are named and cited, the answer with brand highlights, and its sources</p></figcaption></figure>

* **The header** shows the platform and market, the AI volume with a 12-month trend, the first and last collection dates, whether you are named and cited, and the brands named.
* **The answer** has every brand's name highlighted in its colour. Images load only after you click **Show**.
* **Sources** lists the pages the answer cites, with a **Your site** or **Rival's site** badge. A source marked **This page** is the page you came from in Citations.
* On ChatGPT you also see **Retrieved, not cited**, **Fan-out queries** and **Brand entities**.
* The icons copy the prompt, open it in Google or ChatGPT, or track it.

### Track Prompts in LLM Rank Tracker

Select prompts with the checkboxes and click **Track in** [**LLM Rank Tracker**](/guide/llm-rank-tracker), or click the track icon in the drawer for one prompt.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7b87dc39cc7e7abc465921835380c7a6a15f0f9e%2Fai-visibility-track-dialog.png?alt=media" alt=""><figcaption><p>The <strong>Track in LLM Rank Tracker</strong> dialog: <strong>New report</strong> (1) or <strong>Add to an existing report</strong> (2)</p></figcaption></figure>

| Option                            | What happens                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **New report** (1)                | Creates an LLM Rank Tracker report and runs it now. Check the **Brand variants**, **Location** and **Language**, **AI engines**, **Rerun every** and **Cost estimate**, then click **"Create report and run"**. Each engine row says whether it answers for the location and language you picked, and an engine that does not is switched off. The first run is paid. It needs your DataForSEO credentials and an AI provider key, as in the [LLM Rank Tracker setup](/guide/llm-rank-tracker#initial-setup-configuring-required-api-credentials). |
| **Add to an existing report** (2) | Adds the prompts to a report in this workspace. Free. Prompts it already tracks are skipped, and the new ones are tracked from its next run.                                                                                                                                                                                                                                                                                                                                                                                                       |

Each prompt is added exactly as written. Prompts over 700 characters are skipped because Google AI Mode can't take them.

## Citations

The **Citations** tab shows which sites AI cites. Choose a list with the picker at the top left.

### Sources by Brand

Free. Each row is a domain and each column a brand: the number of answers naming that brand that cite the domain, both platforms together. A **Your site** or **Rival's site** badge marks the tracked brands' own sites. "—" means the domain isn't among that brand's top 10. Click a count to open the matching prompts.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-befda1a71ef59aea9140da02a2cc00f97b4969a0%2Fai-visibility-citations-sources.png?alt=media" alt=""><figcaption><p><strong>Sources by brand</strong>: the domains AI cites in answers naming each brand, with a badge on the tracked brands' own sites</p></figcaption></figure>

### Your Cited Pages

The pages that AI cites on your website, labelled **Pages on** *your domain* **and its subdomains**, with **Mentions** (answers citing the page) and **AI volume**. Choose the platform above the list. It needs a website on your brand.

### Cited for a Competitor, Not You

Pick **Cited for** *a competitor***, not you** (1) for the pages cited in answers that name that competitor and not you. It works as an outreach list. **Open answers** (2) opens the matching prompts, filtered to that domain, with the page marked **This page** in each answer's sources.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c4d806bc480586d18b1956ee1aa8f47b45eaac6a%2Fai-visibility-citations-gap.png?alt=media" alt=""><figcaption><p>Pages cited for Adidas and not for Nike: the list picker (1) and <strong>Open answers</strong> (2) on each row</p></figcaption></figure>

A page list loads when you open it and follows the same price rules as Prompts. A list you return to loads for free if it is cached. Otherwise it waits for **Load list**.

{% hint style="warning" %}
**Why a count can differ from Prompts.** **Sources by brand** counts one exact website host on both platforms together. When you click a count, Prompts counts the domain and its subdomains on one platform. Either number can be the higher one.
{% endhint %}

## Exporting to CSV

Three exports save a CSV file that opens in Excel and Google Sheets. In the desktop app, each one opens your computer's save dialog, so you choose the file name and the folder. In the browser, the browser downloads the file.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0b21139b04762ff22c9eafc3710b64afde49bde9%2Fai-visibility-actions-menu.png?alt=media" alt=""><figcaption><p>The <strong>Actions</strong> menu: <strong>Export shares &#x26; gaps CSV</strong> (1), <strong>Export citations CSV</strong> (2) and <strong>Client report</strong> (3)</p></figcaption></figure>

| Export                           | Where                                              | What the file holds                                                                                                                    |
| -------------------------------- | -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Export shares & gaps CSV** (1) | **Actions**                                        | The Overview's numbers: share of voice per brand and platform, the gaps against each competitor, **Rivals win** and the monthly shares |
| **Export citations CSV** (2)     | **Actions**, or the download icon on **Citations** | The cited domains of **Sources by brand**, then every page list already loaded                                                         |
| **Export prompts as CSV**        | The download icon on **Prompts**                   | The list on screen, with its sort and filters                                                                                          |

**Export shares & gaps CSV** is free. It reads the loaded Overview, so it shows **Load the Overview first** until there is one.

### Exporting Prompts

Click the download icon (1) on the **Prompts** toolbar. Opening the dialog is free and sends nothing.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4b372567ba00af8d6c56997d88b8b371c9e08fed%2Fai-visibility-export-prompts.png?alt=media" alt=""><figcaption><p>The <strong>Export prompts as CSV</strong> dialog: the download icon (1), <strong>Include full answers</strong> (2) and the <strong>Cost</strong> (3)</p></figcaption></figure>

* **List** and **Rows** say what the file will hold: the list on screen, in its order and with its filters. A file stops at 20,000 rows, so filter a long list first.
* **Include full answers** (2) is on by default. It adds the full AI answer to each row, which makes the file bigger. It costs nothing extra.
* **Cost** (3) is the price of the rows the export still has to fetch. Rows already loaded this week are free (**Free: every row is already cached this week**). The figure is an upper bound: you pay only for the requests that are sent. The example is high because it covers 20,000 rows. A shorter list costs less.

Click **"Export"** and choose where to save the file. Each row has the **Prompt**, **Platform**, **Location**, **Language**, **AI search volume**, **Brands named**, **Your site cited**, **Cited domains**, **First collected** and **Last collected**, plus the **Answer** when you included it.

### Exporting Citations

The download icon (1) on **Citations** does the same as **Export citations CSV** in **Actions**. When every page list is loaded, the export is free and goes straight to the save dialog.

Otherwise a dialog opens first. It says how many page lists are missing (**5 page lists are not loaded yet**), and the **Cost** (2) is the price of loading the top 100 cited pages of each. Click **"Export"** to accept it, or **"Cancel"** to send nothing.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-bee6b4e2a00219141aa182769fc8399aa826a786%2Fai-visibility-export-citations.png?alt=media" alt=""><figcaption><p>The price dialog of <strong>Export citations as CSV</strong>: the download icon (1) and the <strong>Cost</strong> (2) of loading the missing page lists</p></figcaption></figure>

## Client Report

The client report turns the loaded Overview into a document of A4 pages that you can send to a client as a PDF or an HTML file. In the browser, you print the report instead. It shows the Overview as it was last loaded, so load or refresh the Overview first. Otherwise the report asks you to (**Open the Overview**).

{% stepper %}
{% step %}

#### Open the Report

Choose **Actions > Client report**. The report opens on its own page, and its settings and save buttons float at the bottom right: **Report settings** (1), **Export as HTML** (2) and **Download PDF** (3). In the browser, the last two are replaced by one **Print or save as PDF** button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a56ce734c706fb428d8ea426446febbfdfc7f191%2Fai-visibility-report-preview.png?alt=media" alt=""><figcaption><p>The report preview: <strong>Report settings</strong> (1), <strong>Export as HTML</strong> (2) and <strong>Download PDF</strong> (3)</p></figcaption></figure>

The pages follow this order:

| Section                          | What it shows                                                                                                |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Cover**                        | The logo, heading, subheading and description, on a page of its own                                          |
| **Summary**                      | A few plain sentences: your share and rank, the trend, the rival gaps and your citations                     |
| **Key figures**                  | The key numbers at the top of the Overview                                                                   |
| **Share of voice**               | One bar per brand                                                                                            |
| **Share over time**              | Each brand's share per month, with the same date note as the Overview. A faded month is still running        |
| **Where rivals win**             | **They win**, **Both** and **You win** for each competitor                                                   |
| **Top prompts where rivals win** | The top 10 prompts by AI volume, each platform on its own page                                               |
| **Top cited domains**            | The 10 domains AI cites most, with a count for each brand                                                    |
| **Your cited pages**             | The pages AI cites on your website, from the lists you loaded on **Citations**. Left out when none is loaded |
| **Methodology**                  | How the numbers are counted                                                                                  |

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fbd6e16ab060987d3e20d71b8d2b6f3fa4c6be1a%2Fai-visibility-report-pages.png?alt=media" alt=""><figcaption><p>Two pages of the report: the summary, key figures, share of voice and share over time, then where rivals win and the top prompts</p></figcaption></figure></div>

**The top prompts are the only part that can cost money.** When they are not loaded yet this week, the report prepares them as it opens: a line shows the price (for example **Preparing the report costs up to \~$0.33**). Above 10 requests or $1.00 it asks first (**Prepare** or **Cancel**). A report you reopen with a reload or Back never pays by itself. It shows **Not prepared** and a **Prepare** button instead.
{% endstep %}

{% step %}

#### Adjust the Settings

Click **Report settings**. Changes show in the preview as soon as you click **"Save"**, and each exploration keeps its own settings.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-77e86259342c77f1a9eb101f9be45d52b18cb892%2Fai-visibility-report-settings.png?alt=media" alt=""><figcaption><p>The report settings: the heading (1), the placeholders (2), the sections (3) and <strong>Reset to defaults</strong> (4)</p></figcaption></figure>

* **Logo URL**: a full web address of an image, starting with `http://` or `https://`. Leave it empty for no logo.
* **Heading**, **Subheading** and **Description** (1): the texts of the cover. An empty field uses the default shown in it.
* **Placeholders** (2) work in all three texts and are filled in when the report is built. Click the copy icon next to one to copy it. For example, `[brand] — AI Visibility Report` becomes "Nike — AI Visibility Report".
* **Sections** (3): switch off what you don't want in the report.
* **Reset to defaults** (4) clears your changes at once: the logo, the texts and the sections.

| Placeholder     | Becomes                                |
| --------------- | -------------------------------------- |
| `[brand]`       | Your brand's name                      |
| `[competitors]` | The competitors' names                 |
| `[market]`      | The country and language, or Worldwide |
| `[window]`      | The window, such as "the last 90 days" |
| `[cutoff]`      | The first day of the window            |
| `[date]`        | The date the report is generated       |
| {% endstep %}   |                                        |

{% step %}

#### Save the Report

Click **Download PDF** for an A4 PDF, or **Export as HTML** for a file with the same pages. Both open the save dialog and are free, because they use the data the preview has already prepared. They stay disabled until the report is ready.

In the browser, click **Print or save as PDF** instead. It opens the browser's own print dialog, where you choose a printer or save the report as a PDF. It is free too, and stays disabled until the report is ready. **Download PDF** and **Export as HTML** are available in the desktop app only.
{% endstep %}
{% endstepper %}

## Finding an Exploration Again

Press **⌘K** (**Ctrl+K** on Windows and Linux) to open the command palette. **Recent** lists each exploration once, as its name and market, and opens its Overview whichever tab or filter you used last. Type "ai visibility" and choose **New AI Visibility exploration** to start another. **View all explorations** on the AI Visibility page lists every exploration with its share of voice, data date and spend.

## Using AI Visibility in the Browser

With [Remote Access](/guide/remote-access), you can use AI Visibility from any web browser. Your computer still does the work and sends the DataForSEO requests, and the results stay on it.

In the browser you can:

* Open the start page and the list of explorations, review the brands and competitors, and click **"Explore"**.
* Watch the Overview load part by part, with **Stop** available while it loads.
* Work in **Prompts** (with the answer drawer) and **Citations**, including the page lists.
* Export the [three CSV files](#exporting-to-csv). The browser downloads each file.
* Open the [client report](#client-report). It has **Print or save as PDF** in place of **Download PDF** and **Export as HTML**.

Spending works as on the desktop. Every paid action shows its price first, and a page you reload never pays by itself. See [What It Costs](#what-it-costs).

### Team Members

[Team members](/guide/team) you invite can use AI Visibility in the browser too. **AI Visibility** is in their **AI Era** menu, and they see the explorations of the workspaces you gave them. Their [role](/guide/team/inviting-your-team#roles) decides what they can do:

| Role        | In AI Visibility                                                                                                                                                                    |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Viewer**  | Open the explorations, the Overview, **Prompts**, **Citations** and the answer drawer. What is already loaded costs nothing.                                                        |
| **Analyst** | Everything a Viewer does, plus **Load** or **Refresh** an exploration, stop a load they started, export the three CSV files and print the client report.                            |
| **Manager** | Everything an Analyst does, plus start, edit, rename, duplicate and delete explorations, change the report settings, track prompts in the LLM Rank Tracker, and stop anyone's load. |

Anything that sends DataForSEO requests, such as a first load, a refresh or a page list that is not loaded yet, also needs **Can use the owner's machine and accounts**. Without it, the button is greyed out with **Ask {your name} for run access**, and a team member can still load what is already saved on your computer, for free. Their spend appears in the [Spend tab](/guide/team/activity-and-spend#spend), and the price of every action is shown first, as it is for you.


# How to Use Proxies

While proxies aren't necessary for SEO Utils, using them is recommended if you want to speed up scraping for "People Also Ask" (PAA), check if URLs are indexed, or avoid having your IP blocked by Google.

### Recommended Proxy Providers

#### Proxy Rack

* Website: <https://www.proxyrack.com/>
* Proxy plans that work for Google scraping tasks:
  * Premium Residential Proxies
  * Private Unmetered Residential Proxies

(More coming soon...)

### Renting Proxies

Residential proxies can be expensive, typically costing between $60 to $150 per month. To offer a more affordable solution, I've decided to launch a proxy rental service. Details will be released next month.

### How to Connect Proxies in SEO Utils

To use proxies in SEO Utils for tasks like scraping Google's "People Also Ask" or checking if URLs are indexed, go to the App dropdown in the top right corner of the app and select the "Proxies" menu item.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-57f50c3cbaa3da1da11cb15e8f3fcb0b24a43450%2FXnapper-2024-02-25-16.57.33.png?alt=media" alt="" width="375"><figcaption><p>Proxies menu</p></figcaption></figure>

Then, click the "**Add Proxy**" button and fill all the required fields.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1ca1e403fce19380f3041f00f1842ef1e2c8f357%2FXnapper-2024-02-25-16.58.34.png?alt=media" alt="" width="375"><figcaption><p>Fill all the fields to add a proxy</p></figcaption></figure>

After you add a proxy, SEO Utils will automatically use it for tasks that require proxies.


# Bulk Check Mentions

Updating...


# Bulk SEO Metadata Optimizer

The **Bulk SEO Metadata Optimizer** in SEO Utils allows you to optimize **titles, meta descriptions, and H1 headings** across multiple pages using AI. This tool is perfect for SEOs looking to save time while enhancing metadata for better search engine visibility and click-through rates.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-48d423e0ebd44f628d30907a090001ec956c8164%2FXnapper-2024-12-15-22.25.10.png?alt=media" alt=""><figcaption><p>Bulk SEO Metadata Optimizer tool</p></figcaption></figure>

### Start Your First Run with the Bulk SEO Metadata Optimizer

To get started, open SEO Utils. On the left-hand sidebar, navigate to the **Utilities** section and click on **Bulk Metadata Optimizer**. This will open the dashboard where you can manage your previous reports or create a new one.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1986b05c3acf86a4362fef34c8e2b7e8d63c5d64%2FXnapper-2024-12-15-22.26.00.png?alt=media" alt="" width="375"><figcaption><p>The tool is under Ultiltes menu</p></figcaption></figure>

To create a new optimization report, click the **Run** button located at the top-right corner of the screen. This will open the **Run Form**, where you can configure your optimization settings.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9ee43a83fea24e99ce77118acc10669456c7fa06%2FXnapper-2024-12-15-22.28.06.png?alt=media" alt=""><figcaption><p>Click the "Run" button to start a new run.</p></figcaption></figure>

#### **Add URLs for Optimization**

In the **Run Form**, you’ll see a text box labeled **Enter URLs (one per line)**. Here, you can paste the list of pages you want to optimize. Each URL must be on a separate line.

If you want to optimize all pages under a specific path, you can use the **wildcard (\*)** character. For example:

* Entering `https://example.com/blog/*` will scrape and optimize all pages under the `/blog/` path.
* Entering `https://example.com/category/content/*` will target every page under `/category/content/`.
* If you enter a specific page like `https://example.com/page-1`, only that exact page will be optimized.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4213d9d82731e288dd158af641fe563b716af7d2%2F470205909_8818212598247890_4358969561379193977_n.jpg?alt=media" alt=""><figcaption><p>Use wilcard (*) to quickly import URLs</p></figcaption></figure>

{% hint style="info" %}
The wildcard feature is extremely useful for bulk optimization, saving you the hassle of manually adding every single URL.
{% endhint %}

{% hint style="warning" %}
You must **install Google Chrome** on your computer to use the wildcard feature.
{% endhint %}

#### **Choose the AI Model**

The next step is to select the AI model that will generate the optimized metadata. SEO Utils supports multiple AI providers, so you can choose the one that best suits your needs.

* **OpenAI:** You can choose models like GPT-4o, GPT-4o Mini, and more. Get an API key at <https://platform.openai.com/settings/organization/api-keys>
* **Anthropic**: You can use Claude models like Claude 3.5 Sonnet or Claude 3 Ocpus by getting your API key at <https://console.anthropic.com/dashboard>
* **OpenRouter**: This platform gives you access to around 281 different AI models, providing plenty of options. Register an account at <https://openrouter.ai/>

{% hint style="info" %}
You can access the list of models from OpenRouter at <https://openrouter.ai/models>
{% endhint %}

Once you have the API keys, go to the Services settings to enter them. You don’t need to enter all the keys—just input the one for the provider you want to use.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b8eb7944d4e169b8828da8c5fca3613076a03e30%2FXnapper-2024-12-15-22.42.24.png?alt=media" alt=""><figcaption><p>Enter LLM Provider API keys</p></figcaption></figure>

* **Local Models via Ollama**: If you prefer not to rely on **cloud APIs**, you can use local models like *Mistral* for **FREE**. To set up Ollama:
  1. Download and install Ollama from <https://ollama.com>.
  2. Open the **Terminal** app on your computer and run the command `ollama pull mistral` to download the model. Ensure your PC meets the requirements specified for the model. For example, Mistral requires at least 16GB of RAM.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-72189f6a620f6a9290454cf3777cc5d4ca4cf02e%2FCleanShot%202024-12-15%20at%2022.36.09%402x.png?alt=media" alt=""><figcaption><p>Run the command from your Terminal app to download Ollama models.</p></figcaption></figure>

{% hint style="info" %}
You don’t need an API key to use local models from Ollma. Just keep the Ollama app open, and SEO Utils will find and display all the downloaded models in the dropdown.
{% endhint %}

{% hint style="success" %}
Using local models is cost-effective, but keep in mind they require strong hardware to run efficiently. You can access the list of models at <https://ollama.com/search>
{% endhint %}

#### **Customize Advanced Settings**

Below the AI model selection, there is an option to **Toggle Advanced Settings**. Clicking this will reveal additional customization options to fine-tune the optimization process.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-714c3c911f8a8347e041d3eb8e8b706460015c3a%2FXnapper-2024-12-15-22.58.52.png?alt=media" alt=""><figcaption><p>Advance settings</p></figcaption></figure>

In the **Instruction** field, you can provide a clear instruction for the AI to follow. For example, you might write:

> "You are an SEO expert tasked with improving metadata. Write engaging meta titles, descriptions, and headings that include target keywords and improve click-through rates."

The **Prompt** field is where you can provide SEO metadata that you want to improve using placeholders.

Placeholders are special tags that SEO Utils will automatically replace with the actual content when scraping data from each URL. Here is a breakdown of available placeholders:

* `[title]`: This will be replaced with the page title scraped from the URL.
* `[meta_description]`: This will be replaced with the meta description found on the page.
* `[heading_1]`: This will be replaced with the main H1 heading of the page.
* `[content:50]`: This will include the first 50 words of the page content, and you can edit the number to include any amount of words you prefer, such as 100 or 200 words.

For example, you can define the prompt as follows:

```
Title: [title]
Meta Description: [meta_description]
Heading 1: [heading_1]
Content Preview: [content:50]
```

With this setup, SEO Utils will scrape the page content for each URL, replace the placeholders with the corresponding values, and send them to the AI for optimization.

{% hint style="success" %}
Keep the **Instruction** and **Prompt** fields empty if you want to use the default value that SEO Utils provides.
{% endhint %}

#### **Start the Optimization**

Once you’ve entered your URLs, selected the AI model, and customized the advanced settings, you’re ready to start the optimization process. Click the **Optimize SEO Metadata** button at the bottom of the form.

SEO Utils will process all the URLs and send the scraped data to the selected AI model. Depending on the number of URLs and the model chosen, the optimization may take a few moments to complete.

After the optimization is complete, you will be redirected to the **Report Detail Page** where you can review the results.

### Review the Results

The Report Detail Page provides a clear view of the optimized metadata generated for each URL. For every URL, you can see the **original version** alongside the **improved version** generated by the AI.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cde841eba260d9fdd1711c91c971e63434115275%2FCleanShot%202024-12-15%20at%2023.01.11%402x.png?alt=media" alt=""><figcaption><p>Preview changes of each URL</p></figcaption></figure>

Changes are highlighted for easy comparison:

* **Green**: New content that has been added.
* **Red**: Content that has been removed.

If you want to make manual adjustments to any metadata, simply click the **pencil icon** beside the corresponding field. This will allow you to edit the title, meta description, or H1 heading directly.

To modify additional aspects of the optimization, switch to the **Main Content** tab. Here, you can edit the extracted content from the page. If you need to adjust the AI instructions or prompt message for a specific URL, switch to the **Messages** tab. This lets you refine the instructions or prompt to better suit your needs, and placeholders can still be used here for consistency.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1c482d1e7578c46ea174f84139061d685385f075%2FXnapper-2024-12-15-23.02.59.png?alt=media" alt=""><figcaption><p>Edit data if needed</p></figcaption></figure>

After making changes, you can re-optimize the URL by selecting it and clicking the **Re-optimize** button.

{% hint style="info" %}
**Tip:** You can make small edits to the **Improved version** before [publishing changes](#publish-changes-to-your-website) by clicking the pencil icon next to it.
{% endhint %}

### Publish Changes to Your Website

SEO Utils makes it easy to publish the optimized metadata directly to your website through **Site Integrations**.

{% hint style="info" %}
SEO Utils currently support integration with WordPress. More integrations, such as Shopify, Webflow, and custom platforms, will be added gradually soon.
{% endhint %}

To connect your website:

1. Go to the **Settings** section in the sidebar and select **Site Integrations**.
2. Click **Add Integration** and enter the following details:
   * **Site URL**: The URL of your WordPress site.
   * **Platform**: Select WordPress.
   * **Username** and **App Password**: These can be generated in WordPress.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4085c747c43902d3b2e31d8a152d9bd3148c4707%2FXnapper-2024-12-15-23.13.54.png?alt=media" alt="" width="563"><figcaption><p>Access Site Integrations</p></figcaption></figure>

To generate an App Password in WordPress:

1. Go to your WordPress dashboard.
2. Navigate to **Users > Profile**.
3. Edit a user who has permission to edit posts or pages. If you're unsure, just choose the admin user.
4. Scroll down to the **Application Passwords** section.
5. Generate a new password and copy it.
6. Paste the application password & username into the SEO Utils integration form.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-30e34a5b8aa1c2a2f3fbc2e95b69a5f933a67656%2FCleanShot%202024-12-17%20at%2013.04.22%402x.png?alt=media" alt=""><figcaption><p>Make sure you copy the correct username.</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-dc2dd3debae3b878d2cfba081d38179fe140c004%2FXnapper-2024-12-15-23.19.22.png?alt=media" alt=""><figcaption><p>Create an app password</p></figcaption></figure>

{% hint style="info" %}
SEO Utils will use this application password to change metadata on your website using the SEO Utils WordPress plugin (please install it below).

This application password is **NOT the same as the password** you use to log into your WordPress dashboard, and you can revoke it anytime you need.
{% endhint %}

**Install SEO Utils WordPress plugin**

This plugin will provide a REST API endpoint that lets the SEO Utils app send a request to your website to update metadata.

Please [download it](https://larseov2.s3.us-east-1.amazonaws.com/seo-utils/site-integrations/seo-utils.zip) and install it as a normal WordPress plugin.

**Note**: To update metadata, ensure you have one of the following SEO plugins installed on your WordPress site:

* Yoast SEO
* Rank Math
* All-in-One SEO Pack
* SEOPress
* Slim SEO
* Squirrly SEO

If these plugins are not installed, only the H1 heading can be updated, as it is part of the WordPress core content.

After connecting your site, return to the [**Report Detail Page**](#review-the-results). Click the pencil icon, and you will see a dropdown to select your connected site.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b292c563e951f5130ff9bbd35197d8772b2268fb%2FCleanShot%202024-12-15%20at%2023.27.23%402x.png?alt=media" alt=""><figcaption><p>Edit the report to select the added site integration from the previous step.</p></figcaption></figure>

Once the site is selected, a **Publish** button will appear.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-48ea31a3dfd9950047f802011190f99270e7a920%2FXnapper-2024-12-15-23.28.35.png?alt=media" alt=""><figcaption><p>The "Publish" button appears after connecting to your site.</p></figcaption></figure>

You can publish the following fields:

* Meta Title
* Meta Description
* H1 Heading

{% hint style="danger" %}
Before publishing, always back up your data to avoid any unintended changes.
{% endhint %}

### Bulk Actions

You can select multiple URLs and bulk publish or re-optimize them at once.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-092daa94a14bd48409a4cc1adff9df4a2835ac7c%2FXnapper-2024-12-15-23.35.03.png?alt=media" alt=""><figcaption><p>Bulk Publish URLs</p></figcaption></figure>

{% hint style="info" %}
While the bulk action is running, you can view the log in the Log Panel at the bottom of the page.
{% endhint %}

### Export the Report

If you need to save the results for further analysis or reporting, SEO Utils allows you to export the optimized metadata. On the [Report Detail Page](#review-the-results), click the **Export** button at the top-right corner.


# How to Save Costs when Using DataForSEO

To save costs while using DataForSEO data on SEO Utils, consider implementing the following strategies:

### 1. Reusing Past Searches with Recent Searches & Local Cache

Every DataForSEO search you run is stored locally in your SQLite database. Under each tool's search bar, a **Recent searches** list lets you re-open past searches in one click — no API credits spent if the data is still cached. A small freshness widget in the bottom-right corner shows how old the data is and has a Refresh button for when you need the latest.

<mark style="color:green;">Read the instructions at:</mark> [Recent Searches & Cache](/guide/recent-searches-and-cache)

### 2. Using S3 Cache to Share Data

SEO Utils can cache DataForSEO API responses using S3-compatible storage (AWS S3, Cloudflare R2, DigitalOcean Spaces, MinIO), and the data is cached for up to 7 days. Your teammates can access the same data without paying any extra fees.

<mark style="color:green;">Read the instructions at:</mark> [S3 Cache for DataForSEO Data](/guide/data-sharing-with-s3)

### 3. Using Default Filters

Since [v1.13.0](https://help.seoutils.app/guide/pages/FYHJNu9cAi74Qc90ALo7#v1.13.0), you will be able to set default filters for each request to DataForSEO. SEO Utils will apply those filters on the initial load, helping you save costs by avoiding pulling unneeded data.

For example, I often look for keywords that get searched at least **800 times per month**, have a **Keyword Difficulty of no more than 25**, and are used for **informational purposes**. I can set the default filters as shown in the following image.

Every time I visit the **Organic Keywords** page, the same filters will be applied during the initial loading.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-464d7079ef7d64cac80b430ef8039a7010238ba4%2F436261487_7529981993737630_4040108221033116791_n.jpg?alt=media" alt=""><figcaption><p>Set default filters for the tool that pulls DataForSEO data to save costs.</p></figcaption></figure>


# Manage SERP Data

This tool allows you to seamlessly transfer SERP data from one device to another

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f0e50599bce60dd24c77c4506c67150b81863529%2FCleanShot%202024-10-31%20at%2014.09.42%402x.png?alt=media" alt=""><figcaption><p>SERP Data</p></figcaption></figure>

### SERP Data Exporter / Importer

You can export your SERP data from one computer and easily import it onto another, making it convenient to work across multiple devices. This helps reduce costs for [SERP Clustering](/guide/serp-clustering), [N.A.P Finder](/guide/n.a.p-finder), and [Organic Rank Tracker](/guide/organic-rank-tracker).

Additionally, SEO Utils supports importing external SERP data, making it an ideal solution when migrating your SERP data from other tools.

In the screenshot below, I uploaded over **18,000 keywords** to the SERP Clustering tool and used SERP data from the past 7 days. The cost came to just **$0.0390**, saving me **$11.2470**! SEO Utils only sent **65 keywords** to the SERP API for new data, as most of the keywords already had recent SERP data within 7 days.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fc3800a5525db616bd73013b49b0287268edced0%2F464919090_8563919223677230_7461303937806986891_n.jpg?alt=media" alt=""><figcaption><p>Save money when using old SERP data.</p></figcaption></figure>

### Delete Old SERP Data

By default, SEO Utils stores all your SERP data in a database indefinitely. However, as your database grows over years of running SERP Clustering, you may notice slower performance.

To address this, you can view your SERP database size and set a data retention period. Any SERP data older than this period will be automatically deleted at startup, helping the app run reports—like SERP Clustering and Organic Rank Tracker—more efficiently.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-81af268cbfbd0032a014ef9c55a90a270841d0ea%2FXnapper-2024-10-31-14.19.59.png?alt=media" alt=""><figcaption><p>SERP Database Manager</p></figcaption></figure>

In the example above, I've set the retention period to **90 days (3 months)**, so SEO Utils will only keep SERP data from the past 90 days on my computer. You can adjust this to any timeframe you like, such as 365 days for one year, or set it to 0 to store data indefinitely.

### DataForSEO SERP Data Getter

{% hint style="info" %}
Available since v1.38.3
{% endhint %}

This feature allows you to directly import SERP data from DataForSEO by entering task IDs. This is useful when you have existing DataForSEO tasks and want to save their SERP data to your local database for use in [SERP Clustering](/guide/serp-clustering), [Organic Rank Tracker](/guide/organic-rank-tracker), and other tools.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d6f23a852838d2c77bab9d87f0c889212b001a24%2FXnapper-2025-10-05-13.07.36.png?alt=media" alt="DataForSEO SERP Data Getter"><figcaption><p>DataForSEO SERP Data Getter</p></figcaption></figure>

**Where to find your task IDs**

Your task IDs are listed in your DataForSEO account under [**API Dashboard → SERP**](https://app.dataforseo.com/api-detail/serp). Each row is a task you have already paid for, with its ID, keyword and creation date. Copy the IDs you want and paste them into SEO Utils, one per line.

{% hint style="warning" %}
DataForSEO keeps completed results for roughly **30 days**. After that the ID can no longer be fetched, so import anything you still need before the window closes.
{% endhint %}

**How to use:**

1. Enter your DataForSEO task IDs (one per line) in the text area
2. Select the search engine type (Organic, or AI Mode)
3. Click "Fetch SERP Data"

The tool will automatically:

* Fetch the SERP data from DataForSEO using the task IDs
* Extract all necessary metadata (keyword, location, language, device type, etc)
* Save the data to your local database

This is particularly helpful when:

* You've run SERP tasks through DataForSEO's API directly
* You want to import historical SERP data from DataForSEO
* You're migrating data from another system that uses DataForSEO

#### Restoring missing days in an Organic Rank Tracker report

By default, this tool saves results into the shared SERP cache only. Turn on **"Also backfill Organic Rank Tracker reports"** and it can also put those results back into the report **and the day** they belong to.

This is for the situation where a tracker run was interrupted — the app closed mid-run, the computer restarted, a run failed part-way — and a day is missing from your report even though you already paid DataForSEO for those results. Instead of re-running the keywords and paying a second time, you paste the task IDs and put the results you already own back where they belong.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FNkRUHNUFaNgJc1yZqIgS%2FXnapper-2026-08-10-15.42.44.png?alt=media&amp;token=1ddf3776-16c1-4500-a906-84f256757798" alt=""><figcaption><p>The "Also backfill Organic Rank Tracker reports" switch on the DataForSEO SERP Data Getter</p></figcaption></figure>

{% hint style="info" %}
Tracker backfill works with **Organic** results only. AI Mode results are still saved to the shared cache as before.
{% endhint %}

**How it works**

{% stepper %}
{% step %}

#### Paste your task IDs and turn the switch on

* Enter your task IDs, one per line
* Leave **Search Engine Type** on **Organic**
* Turn on **"Also backfill Organic Rank Tracker reports"**
* Click **"Fetch SERP Data"**

There is no task limit in this mode. Long lists are processed in batches of up to 1,000.
{% endstep %}

{% step %}

#### Wait while the tool checks each task

Results are fetched one at a time, so a long list takes a while. The screen shows how many tasks are done and an estimated time remaining, calculated from how fast your own tasks are actually coming back.

You can leave this page, or close the app entirely. The job continues where it stopped when you come back.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FEOzZ9Ex4Ey3Uq4ZwbaTf%2FCleanShot%202026-08-10%20at%2015.43.58%402x.png?alt=media&amp;token=9ef93b1c-519c-4a4b-ae7b-a0427bc6c2a9" alt=""><figcaption><p>Analysis progress showing processed tasks and estimated time remaining</p></figcaption></figure>
{% endstep %}

{% step %}

#### Review the plan before anything is saved

Nothing is written until you confirm. You'll see your results grouped by report and date, marked either **Exact** or **Suggested**, with a preview of what each result contains.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FnzPKZV02z4rpLQn2Jmc6%2FXnapper-2026-08-10-15.45.34.png?alt=media&amp;token=9c959545-43e0-47e2-97f0-d19c1395162f" alt=""><figcaption><p>Confirmation screen showing report groups, match confidence and import previews</p></figcaption></figure>
{% endstep %}

{% step %}

#### Choose the groups and confirm

* Tick the groups you want, or click **"Select all exact"**
* Set a destination date for any suggested group
* Tick any confirmation the screen asks for
* Click **"Confirm backfill"**

The import then runs in the background, and you can leave the page.
{% endstep %}
{% endstepper %}

**Exact and suggested matches**

The tool separates what it can prove from what it can only guess, and never applies a guess on its own.

| Match type    | What it means                                                                                                                                           | What you need to do                                                          |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| **Exact**     | The task ID matches a task this app created, so the report and the original day are both known.                                                         | Nothing. These are safe to select and are the ones "Select all exact" picks. |
| **Suggested** | The keyword, location, language, device and other search settings fit a report, but nothing proves the result came from it or which day it belonged to. | Check the destination date, then confirm you understand it is an estimate.   |

{% hint style="warning" %}
A suggested match uses DataForSEO's fetch time as the destination date. That is when the result was **collected**, which is not always the day your tracker was scheduled to run. Set the date yourself if you know better.
{% endhint %}

**The import preview**

Each keyword shows a small card so you can judge a match before importing it, rather than importing first and checking afterwards.

| On the card                        | What it tells you                                  |
| ---------------------------------- | -------------------------------------------------- |
| **#3** (or similar)                | Your tracked domain's best position in this result |
| **Not ranked**                     | The result is valid, but your domain isn't in it   |
| Page title and link                | The exact page that ranked                         |
| Organic results / Other SERP items | How much the fetched result contains               |

The card shows your domain's best organic position. The full result is imported, including other rankings and supported SERP features.

{% hint style="danger" %}
If you change a report's **target domain** or its **Include subdomains** setting after the analysis, the import stops and asks you to analyze the task IDs again. The preview you approved was read under the old settings, so it no longer describes what would be saved.
{% endhint %}

**Tasks with no matching report**

Task IDs that don't fit any tracker keyword can still be imported as ordinary SERP data, using DataForSEO's proven fetch date. This is on by default and changes no tracker positions. A task is only skipped entirely when DataForSEO returns no fetch date and no original task can be found, in which case there is no date that can be trusted.

**Confirmations you may be asked for**

Each checkbox covers a different decision, so you're only asked for the ones that apply.

| Confirmation                  | When it appears                                                                          |
| ----------------------------- | ---------------------------------------------------------------------------------------- |
| Suggested dates are estimates | You selected at least one suggested group                                                |
| Replacing tracker data        | A selected destination already holds data for that date, or you changed a suggested date |
| Replacing shared cache data   | An unmatched task already has data for its fetch date                                    |

<details>

<summary>If the analysis or import reports errors</summary>

The screen lists up to 100 details under **"Review details"**. Common causes:

1. **A task ID DataForSEO no longer has.** Results are kept for roughly 30 days, after which the ID can't be fetched.
2. **A task ID that isn't ready yet.** The result hasn't finished on DataForSEO's side; try it again later.
3. **A report changed after the analysis.** If the keyword, target domain or search settings changed, run the analysis again so the plan matches the report as it is now.
4. **A report is currently running.** A backfill won't compete with a live run for the same report and day. Wait for the run to finish, then analyze the task IDs again.

Results that imported successfully are always kept. Re-running the same task IDs never imports the same result twice — anything already imported is reported as "already imported" and skipped.

</details>

{% hint style="success" %}
Interrupted work is picked up automatically. If the app closes during an analysis or an import, it resumes at the point it reached the next time you open SEO Utils.
{% endhint %}


# DataForSEO Task Monitor

See what your paid DataForSEO tasks are doing, and whether anything actually needs your attention

Every SERP report you run creates paid tasks at DataForSEO. Most of the time they complete quietly in the background. The DataForSEO Task Monitor is where you look when you want to check on them — whether they're still with DataForSEO, already collected and waiting to be saved, recovering on their own, or genuinely stuck.

This is a monitoring page. You read it to understand what's happening; the app handles the fixing.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FebAbFG9XxQOTTo38ccYS%2FXnapper-2026-08-10-15.58.31.png?alt=media&amp;token=4fe74812-a877-4079-98eb-594fa863aaa1" alt=""><figcaption><p>The DataForSEO Task Monitor showing summary counters, collector health and the active tasks table</p></figcaption></figure>

## Opening the monitor

Go to **Settings → DataForSEO Monitor**.

You can also reach it from the Dashboard. When something needs looking at, a **DataForSEO Needs Attention** card appears there with a link to this page. When everything is healthy, that card stays hidden — so if you don't see it, there's nothing to check.

## The four counters

| Counter                   | What it counts                                                                                                                                                                                                   |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Waiting on DataForSEO** | Tasks being prepared, submitted, or still with DataForSEO — their result has not reached your computer yet. Also shows the age of the oldest one.                                                                |
| **Ready to import**       | Results already downloaded to your computer, waiting to be saved into the report that asked for them. A result counts here as soon as it arrives.                                                                |
| **Automatic recovery**    | Organic SERP, Google Maps, ChatGPT and Google AI Mode tasks older than 24 hours whose result has not arrived yet. The app has their DataForSEO task ID and keeps fetching them on its own.                       |
| **Needs attention**       | Tasks that failed, were rejected or expired; submissions DataForSEO never confirmed that have no result yet; results not saved into their report within 15 minutes; and submissions or imports stuck for longer. |

{% hint style="info" %}
A task is either **Waiting on DataForSEO** or **Ready to import**, never both. A task under **Automatic recovery** is also still **Waiting on DataForSEO**.
{% endhint %}

{% hint style="warning" %}
**A high "Waiting on DataForSEO" number is usually normal.** Standard-queue tasks can legitimately take hours. Look at **Needs attention** to decide whether anything is actually wrong.
{% endhint %}

## Late results are imported automatically

DataForSEO results can arrive after a report stopped waiting for them — for example when you closed the app during a run, or when a large run took longer than expected. The app saves these results into their report on its own. You don't need to run the report again.

{% stepper %}
{% step %}

#### The result is downloaded

A collector downloads the result to your computer. The task moves to **Ready to import**.
{% endstep %}

{% step %}

#### The result is saved into its report

Within a minute or two, the app saves the result into the report that asked for it. Closing the app pauses this; it continues the next time you open SEO Utils.
{% endstep %}

{% step %}

#### The report finishes

When all its results are in, the report finishes on its own — a SERP Clustering report, for example, is clustered at this point — and its page updates.
{% endstep %}
{% endstepper %}

This covers the Organic Rank Tracker, GMB Rank Tracker, Business Reviews, LLM Rank Tracker, SERP Clustering, SERP Extractor, Bulk Google PAA and N.A.P Finder. **Content Struct** is the exception: run a Content Struct report again if its run stopped before it finished.

* While results are still arriving, the report shows as running.
* A **SERP Clustering** or **LLM Rank Tracker** report can't be run again until its results are in.
* If a result never arrives, the app stops waiting once DataForSEO can no longer deliver it, and the report finishes with the results that did arrive.
* SERP Clustering and LLM Rank Tracker stop waiting after about 3 days of SEO Utils running.
* If SEO Utils was closed for longer, it first asks DataForSEO again for every missing result. DataForSEO keeps results for 30 days, so results you paid for are still imported.

## Collector Health

A collector is the background worker that asks DataForSEO whether results are ready. The monitor tracks five of them:

* Organic SERP
* Google Maps
* Google AI Mode
* ChatGPT
* Business Reviews

Each one shows whether it's running, when it last checked in, and how many results DataForSEO had waiting during that check. There's also a button to open that collector's log.

A collector counts as running if it checked in within the last three minutes. A collector working through a large batch of results keeps checking in every minute, so a busy collector is never shown as stopped. Collectors download several results at a time, so a large backlog clears much faster than before.

{% hint style="info" %}
**"Ready on last check" is not your backlog.** It's the number of results DataForSEO showed on the last page it looked at. A low number doesn't mean few tasks are outstanding.
{% endhint %}

A stopped collector only raises a warning at the top of the page when it currently owns active tasks. A collector for a tool you don't use sits idle without raising a false alarm.

## Active Tasks table

The table opens in **Needs attention** mode, so you see the problems first. Switch to **All active** to see every task currently in flight.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fp8FD4eXqeQwlPj4f3et7%2FXnapper-2026-08-10-16.06.54.png?alt=media&amp;token=775fb001-06fc-42bb-80a8-fb677a8fd51f" alt=""><figcaption><p>Active tasks table filtered to tasks that need attention</p></figcaption></figure>

Each row shows the task's current state, its collector, the keyword, its DataForSEO task ID, whether it belongs to a durable run or is a legacy task, the date the data is for, and how old it is. Two more columns — the last provider check, and which report owns the task — can be switched on when you need them.

You can search by keyword, task ID, provider status, endpoint or owner, and filter by state, collector, owner type and age.

### Task states

| State                     | What it means                                                                                                                                      |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Preparing**             | The task is being created and has not been sent yet.                                                                                               |
| **Submitting**            | The task is being sent to DataForSEO.                                                                                                              |
| **Waiting on DataForSEO** | DataForSEO accepted the task and is still working on it, or its result has not been downloaded yet.                                                |
| **Needs confirmation**    | The task was sent, but DataForSEO's reply didn't confirm it. It is matched automatically if DataForSEO lists it as ready.                          |
| **Ready to import**       | The result is on your computer, waiting to be saved into its report. A waiting or unconfirmed task shows this state as soon as its result arrives. |
| **Importing**             | The result is being saved into its report.                                                                                                         |
| **Rejected**              | DataForSEO refused the task.                                                                                                                       |
| **Failed**                | The task could not be completed.                                                                                                                   |
| **Expired**               | DataForSEO can no longer return the result.                                                                                                        |
| **Pending (legacy)**      | A task created without run tracking (by Content Struct, or by an older version of the app) that has not received its result.                       |

## Alerts

| Alert                                   | What it means                                                                                                                                       |
| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Disk is full**                        | Collection is paused until you free up space. Results stay at DataForSEO in the meantime.                                                           |
| **A collector has stopped checking in** | A collector that currently owns tasks is no longer running, which may be holding up paid results. Restarting SEO Utils starts the collectors again. |

Task problems don't get their own banner — that's what the **Needs attention** counter and the filtered table are for.

## Staying up to date

The page refreshes itself every 15 seconds. The **Refresh** button reloads the counters, collector health and the task table immediately, and confirms when it's done.

## Logs and diagnostics

* Open any collector's log from the **Collector Health** section. Logs can be refreshed, copied, or opened in your default editor.
* **Export retired tasks** saves a file of tasks the app has finished with. This is for sending to support when you're investigating something.

## Automatic cleanup

The app removes tasks that nothing can use any more, together with their downloaded result files:

* Tasks of reports you deleted.
* Tasks no report can import any more — for example tasks left by an older version of the app — once they are 7 days old.

Recently removed tasks appear in **Export retired tasks**, with the reason they were removed.

## Why you can't delete tasks here

Earlier versions let you delete task records by hand. That option has been removed, and the app now refuses those requests even if an older screen still offers the button.

The reason is that deleting a task row throws away the DataForSEO task ID and the downloaded result file. Those are exactly what the app needs to recover a result **you have already paid for**. Deleting the row doesn't cancel anything at DataForSEO — it only destroys your own copy of how to fetch it.

{% hint style="danger" %}
**Don't re-run a report just because a task looks slow.** The app still has the task and saves its result into the report as soon as it arrives. Running the report again pays for the same keywords a second time.
{% endhint %}

<details>

<summary>What to do when tasks need attention</summary>

1. **Check Collector Health first.** If a collector has stopped checking in, results can't be collected no matter what the tasks say. Restarting SEO Utils starts the collectors again.
2. **Check for the disk-full alert.** Collection pauses when there's no room to save results safely.
3. **Look at the age column.** A task a few minutes past the 15-minute mark is often just slow, not broken.
4. **Look at Ready to import tasks.** They are saved into their report within a minute or two while SEO Utils is open. If they stay, open the collector's log for details.
5. **Open the collector's log** for the tasks in question. The log shows what the collector saw on its most recent checks.
6. **Export retired tasks** if you need to send the history to support.

Wait before re-running a report. A paid result that is still recoverable is worth more than a fast retry.

</details>

<details>

<summary>Re-running a SERP Clustering report from an older version</summary>

Older versions could leave a SERP Clustering run's results downloaded but not saved into the report, for example when the app closed during the run. To use those results without paying for them again:

1. Open the **same** report — not a new one with the same keywords.
2. Click **Re-cluster**.
3. Set **Use Saved SERP Data For X Days** above 0, for example 7.
4. Run it.

The report saves the results that were already downloaded first, then only fetches the keywords that are still missing.

</details>

{% content-ref url="/pages/D1TDLflLs8kfQXbkpdvI" %}
[Manage SERP Data](/guide/manage-serp-data)
{% endcontent-ref %}


# Backups & Restore

Back up SEO Utils to a file, an S3 / R2 bucket or a folder, by hand or on a schedule, and restore it on this computer or another one.

SEO Utils backs up everything you work with to a file, to a cloud bucket, or to a folder such as an external drive. You can back up by hand or on a schedule, and restore on this computer or on a new one. It works in the desktop app, not in a browser over [Remote Access](/guide/remote-access).

To open it, go to the user dropdown and select **Backup Tools > Database**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8875d9e589d227c7373eb8e9910df518948eb322%2FXnapper-2024-11-13-20.47.25.png?alt=media" alt=""><figcaption><p>Access Database backup tool</p></figcaption></figure>

## What a Backup Contains

A backup is one file that ends in `.seobackup`.

| Part                | What it holds                                                                      |
| ------------------- | ---------------------------------------------------------------------------------- |
| **Database**        | Your workspaces, reports, keyword lists and everything else you work with          |
| **Vector database** | The embeddings SEO Utils keeps for semantic search and clustering, if you have any |
| **Settings**        | Your app settings, including saved API keys and Google sign-ins                    |
| **Saved pages**     | Only in a backup to a file, and optional: the saved SERP pages on this computer    |

{% hint style="warning" %}
A backup contains your saved API keys and Google sign-ins. Keep it private, or [encrypt your backups](#encrypt-your-backups).
{% endhint %}

A backup never holds what belongs to the computer: your licence key, the Remote Access pairing, where your saved pages are stored, and secret keys kept in the keychain, such as S3 / R2 secret keys. A restore never changes them either.

## Where Backups Can Go

| Destination | Good for                                             | Needs                                             |
| ----------- | ---------------------------------------------------- | ------------------------------------------------- |
| **File**    | A one-off copy you keep or move yourself             | Nothing. By hand only.                            |
| **Bucket**  | Automatic backups, and restoring on another computer | An [S3 / R2 connection](/guide/s3-r2-connections) |
| **Folder**  | An external drive, or a Dropbox or iCloud folder     | A folder on this computer                         |

To use a bucket or a folder, choose it once:

{% stepper %}
{% step %}

#### Open the destination

On the Database page, find the **Destination** row in the **Automatic backups** card and click **Set up**.
{% endstep %}

{% step %}

#### Pick the bucket or the folder

{% tabs %}
{% tab title="Bucket" %}
Choose a **Storage connection** (1), or click **New connection** to add one. Its key needs to read, write and delete, and its endpoint must be `https://`. Then enter the **Bucket** (2) and, if you like, a **Prefix**: a folder in the bucket for the backups.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-94ec28d1a790a36c7f586fedcf3bd0744af9a935%2Fbackups-destination-bucket.png?alt=media" alt=""><figcaption><p>A bucket destination: (1) connection, (2) bucket, (3) test, (4) save</p></figcaption></figure>
{% endtab %}

{% tab title="Folder" %}
Select **Folder or external drive**, click **Choose folder…** (1) and pick a folder. It cannot be inside the SEO Utils data folder. The folder belongs to this computer: on another computer, choose the folder there.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-52713f55f9d2ef1cc4fa7e1a3ea735913cac51a3%2Fbackups-destination-folder.png?alt=media" alt=""><figcaption><p>A folder destination: (1) choose, (2) test, (3) save</p></figcaption></figure>
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

#### Test and save

Click **Test**. SEO Utils writes, lists, reads and deletes a small file there to prove it can use the place. When the test passes, click **Save**.
{% endstep %}
{% endstepper %}

Backups go in a `seo-utils-backups` folder with one subfolder for each computer, so computers that share a destination never delete each other's backups.

## Back Up Now

{% stepper %}
{% step %}

#### Open the Database page

The **Back up now** card has **To a file…** (2) and, after your first backup, the **Last backup** line with **View log** (3). The switch **Include saved pages on this computer** (1) applies to files only.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-48360ae72597d91919b748211c13534afab0658f%2Fdatabase-backup-back-up-now.png?alt=media" alt=""><figcaption><p>The Back up now card: (1) include saved pages, (2) start the backup, (3) read the log of the last backup</p></figcaption></figure>
{% endstep %}

{% step %}

#### Choose where to back up

{% tabs %}
{% tab title="File" %}
Click **To a file…**, then choose a folder and a file name. Keep **Include saved pages on this computer** on to put the saved SERP pages in the file; without them, SERP snapshots and page-change histories are unavailable after a restore.
{% endtab %}

{% tab title="Bucket" %}
Click **To the bucket** (2). It uses the destination you saved.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e2d8ce66791f57700a27b134d5b6759b81b4f9c1%2Fbackups-back-up-now.png?alt=media" alt=""><figcaption><p>With a destination saved, <strong>To the bucket</strong> (2) sits beside <strong>To a file…</strong> (1)</p></figcaption></figure>
{% endtab %}

{% tab title="Folder" %}
Click **To the folder**. It replaces **To the bucket** when your destination is a folder.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

#### Keep working and check the result

SEO Utils keeps working while it backs up, and the card shows the progress. When it finishes, **Last backup** shows when it ran and how big it is. Click **View log** to read what it did.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9733d555cf2c60b73a8a14b7445349fd22016f78%2Fdatabase-backup-progress.png?alt=media" alt=""><figcaption><p>A backup in progress</p></figcaption></figure>
{% endstep %}
{% endstepper %}

**Backup history** lists every backup this computer has started, with how it started, where it went and its status. A backup cut short by closing SEO Utils shows **Interrupted**: start it again.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c2ccc6723777e58521d093c6a0c083d55d4a3916%2Fdatabase-backup-history.png?alt=media" alt=""><figcaption><p>Backup history</p></figcaption></figure>

## Automatic Backups

Automatic backups send a backup to your bucket or folder on a schedule and delete the oldest ones after each new one.

{% stepper %}
{% step %}

#### Choose the schedule

In the **Automatic backups** card, click **Set up**. The dialog repeats your destination and adds:

* **How often** (1): every hour, every 2, 3, 6 or 12 hours, every day or every week. A daily or weekly schedule also asks for a **Start time**, and a weekly one for a **Day of the week**.
* **Keep** (2): how many backups this computer keeps in the destination, from 1 to 365 (14 by default). After each successful backup, older ones are deleted.
  {% endstep %}

{% step %}

#### Set the encryption

**Encrypt backups** (3) is on. Type a passphrase twice and tick **I understand that SEO Utils cannot recover a forgotten passphrase.** See [Encrypt Your Backups](#encrypt-your-backups).
{% endstep %}

{% step %}

#### Turn it on

Click **Save and turn on** (4). The first backup starts about 5 minutes later, then follows the schedule.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-76bae991473910bf26591a3c9aa8f7009ff96312%2Fbackups-automatic-setup.png?alt=media" alt=""><figcaption><p>The setup dialog: (1) how often, (2) keep, (3) encryption, (4) save and turn on</p></figcaption></figure>
{% endstep %}
{% endstepper %}

The card then shows **On**, the schedule, the size of the last backup and when the next one starts. **Edit** changes the schedule, **Turn off** pauses it and **Turn on** resumes it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6d2dd8a24e9d6da74424e25d2a333b42140a9fb8%2Fbackups-automatic-card.png?alt=media" alt=""><figcaption><p>The Automatic backups card: (1) on, (2) edit, (3) turn off, (4) destination</p></figcaption></figure>

* **Backups run while SEO Utils is open.** One missed while it was closed starts 5 minutes after SEO Utils opens again.
* **Keep counts only this computer's backups**, and only while automatic backups are on.
* **After two failed scheduled backups in a row**, the card shows the reason and the date of the last good backup, and **View log** opens the details. The notice goes away after the next backup to the destination succeeds.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0049dfad39012ac4da94f8678c9fd90b0aec55fe%2Fbackups-failing-notice.png?alt=media" alt=""><figcaption><p>The notice after two failed backups: (1) the reason, (2) the log</p></figcaption></figure>

## Encrypt Your Backups

Encryption keeps a backup unreadable to anyone without your passphrase. Turn it on in the automatic backups dialog, or in the **Encryption** card: click **Encrypt backups**, enter a passphrase of at least 12 characters twice, tick the box and click **Save**. It applies to later backups.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d62235b067a9095b690d1a036f69857bd8f95451%2Fdatabase-backup-encrypt.png?alt=media" alt=""><figcaption><p>Set a backup passphrase</p></figcaption></figure>

{% hint style="danger" %}
**An encrypted backup cannot be restored without its passphrase.** If you forget it, your backups can never be restored, and SEO Utils cannot recover the passphrase or open the backups for you. Store it somewhere safe.
{% endhint %}

| Action                  | What it does                                                                                  |
| ----------------------- | --------------------------------------------------------------------------------------------- |
| **Check my passphrase** | Confirms that you still remember it. Do this after you set it.                                |
| **Change passphrase**   | Sets a new passphrase for future backups. A backup file made earlier still needs the old one. |
| **Turn off**            | Stops encrypting future backups, after you confirm in place.                                  |

## Restore a Backup

{% hint style="danger" %}
Restoring replaces everything in SEO Utils with the backup. Your current data is kept only until the restored data has started once, so make a new backup first if you might need it.
{% endhint %}

{% stepper %}
{% step %}

#### Choose the backup

In the **Restore** card, choose where the backup is:

{% tabs %}
{% tab title="From a file" %}
Click **From a file…** and choose the backup. Besides `.seobackup` files, SEO Utils restores the `.tar.gz` and `.db.gz` files made by earlier versions (see below).
{% endtab %}

{% tab title="From the bucket or folder" %}
Click **From the bucket** (or **From the folder**). The list shows the backups of **This computer**; use **Device** (1) to see another computer's. Open the row's menu (2) and choose **Restore**. The same menu has **Delete**, which asks **Remove?** in place and deletes the backup for good.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1307d59b80993b3f1dce2d27e3c2311c0cce6609%2Fbackups-restore-bucket-list.png?alt=media" alt=""><figcaption><p>Backups in the bucket: (1) choose the computer, (2) open the row's menu</p></figcaption></figure>
{% endtab %}

{% tab title="From another bucket" %}
For a computer that has no destination yet: see [Restore on Another Computer](#restore-on-another-computer).
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

#### Check the summary

The dialog shows who made the backup (**Made by**, **Date**, **Computer**), what it **Contains** and whether it is **Encrypted** (1). For an encrypted backup, type the passphrase it was made with (2). Then click **Restore** (3).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ebfcbf622061a0ec5340690c60740d2aeddeafd5%2Fdatabase-backup-restore-summary.png?alt=media" alt=""><figcaption><p>What the backup holds, the passphrase and Restore</p></figcaption></figure>

A backup in a bucket or folder may also show **Saved SERP pages of reports deleted after this backup was made may be missing.** It means the saved pages of a report you deleted after that backup may be gone. See [Saved Pages and Backups](#saved-pages-and-backups).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cb4f195882a9afff22e179abca8bd31f1f735bb3%2Fbackups-restore-bucket-summary.png?alt=media" alt=""><figcaption><p>A restore from the bucket: (1) summary, (2) warning, (3) passphrase, (4) restore</p></figcaption></figure>
{% endstep %}

{% step %}

#### Confirm

SEO Utils asks once more, in place: read the message (1) and click **Restore** (2).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-72ba9a0ff5dae9a526559a8184ad00544f59374f%2Fdatabase-backup-restore-confirm.png?alt=media" alt=""><figcaption><p>Confirm the restore</p></figcaption></figure>
{% endstep %}

{% step %}

#### Wait for the restore

SEO Utils reads the backup and prepares the restored data. Your current data is not touched yet, so you can click **Cancel restore** (1) and nothing changes, until **Replacing your data** begins. Then the window shows **Restoring the backup**: do not close the app.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8458a34520a4ce9b866aafe9d4edaa6a6f1653bc%2Fdatabase-backup-restore-progress.png?alt=media" alt=""><figcaption><p>A restore in progress, with Cancel restore</p></figcaption></figure>
{% endstep %}

{% step %}

#### Restart SEO Utils

When you see **Restore completed. Restart SEO Utils to finish.**, click **Restart SEO Utils** (1). It opens again with the data from the backup.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-90b358e0b15104ab3be112465bf1c73d613c2c24%2Fdatabase-backup-restore-restart.png?alt=media" alt=""><figcaption><p>The restore is complete</p></figcaption></figure>
{% endstep %}
{% endstepper %}

* A backup made by the same or an older version restores. One from a **newer** version is refused, and the dialog names the version to update to.
* A wrong passphrase changes nothing. A backup in a bucket or folder also opens with your latest passphrase.
* If SEO Utils closes while it replaces your data, the next start puts your data back and shows **Restore interrupted** once.

<details>

<summary>Restoring files from earlier versions</summary>

* The dialog marks them **Older backup format**. They hold the database, plus saved pages in a `.tar.gz`, but not your settings. Use [Back Up Only Your Settings](#back-up-only-your-settings) for those.
* A file from a different version shows a warning about issues or data corruption. Tick the acknowledgement to enable **Restore**. After you confirm, a progress page ends with **Restore completed successfully! Please restart the application.** Click **Restart App**.

</details>

## Restore on Another Computer

Use this to move to a new computer or to open a copy on a second one.

{% stepper %}
{% step %}

#### Install and activate

Install SEO Utils in the same version as the backup or a newer one, and [activate your licence](/guide/manage-license-key).
{% endstep %}

{% step %}

#### Reach the backups

{% tabs %}
{% tab title="From a bucket" %}
In the **Restore** card, click **From another bucket…** and enter the bucket's keys: the same fields as an [S3 / R2 connection](/guide/s3-r2-connections), plus the **Prefix** you set on the first computer. No connection is needed here. Leave **Save these keys on this computer** (3) on, and SEO Utils saves the secret key in your keychain for the restored connection. Click **List backups** (4).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d3514e13e4f207e742a789afc480a9dcaa219570%2Fbackups-restore-another-bucket.png?alt=media" alt=""><figcaption><p>Restore from another bucket: (1) account, (2) bucket, (3) keep the keys, (4) list the backups. Example values.</p></figcaption></figure>

Choose the computer in **Device** (1), then open the menu of its newest backup (2) and choose **Restore**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-aaaaab0f89e5dddbae62ce24ab697f419567f04f%2Fbackups-restore-another-pick.png?alt=media" alt=""><figcaption><p>The backups of another computer: (1) choose it, (2) restore</p></figcaption></figure>
{% endtab %}

{% tab title="From a file" %}
Copy the `.seobackup` file to the new computer and use **From a file…**. Before you make the file, bring any saved pages that you moved to a drive or bucket [back to this computer](/guide/saved-serp-pages-storage#bringing-pages-back), and keep **Include saved pages on this computer** on.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

#### Restore and restart

Type the passphrase if the backup is encrypted, restore as above, and restart SEO Utils. Then:

* **Secret keys needed** lists the connections whose secret keys are not on this computer, because the keychain is never in a backup. Open **Settings > Services > Storage > S3 / R2 Connections**, edit each one and enter its secret key. The notice shows once.
* **Automatic backups come back set up but turned off.** Click **Turn on** when you want them. With a folder destination, choose the folder on this computer first.
* Pair [Remote Access](/guide/remote-access) again if you use it. Your licence stays as you activated it.
  {% endstep %}
  {% endstepper %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0348170c67c152e32f5848de917a2bfafd08e751%2Fbackups-secret-keys-needed.png?alt=media" alt=""><figcaption><p>The notice after a restore: (1) open the connections</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-117a2c987cdc84b2b50ce39eb9385a8221c1f9a4%2Fbackups-set-up-but-off.png?alt=media" alt=""><figcaption><p>Automatic backups wait for you: (1) the notice, (2) turn on</p></figcaption></figure>

## Saved Pages and Backups

[Saved SERP pages](/guide/saved-serp-pages-storage) can take many gigabytes, so backups to a bucket or a folder, scheduled or not, never contain them. Only a backup to a file can, with the switch on.

To keep them safe anyway, store them in the bucket next to your backups:

1. In the **Automatic backups** card, find the **Saved pages** row: **Saved SERP pages on this computer are not in automatic backups.**
2. Click **Keep them in this bucket too** (1). SEO Utils moves the pages into a `saved-pages` folder inside your backup prefix, in the background.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-44907588df8ea83b0debd1d1b9b8279f899a307e%2Fbackups-saved-pages-row.png?alt=media" alt=""><figcaption><p>The Saved pages row</p></figcaption></figure>

The row then says where the pages are, and a restore finds them again. The button shows only for a bucket destination, while the pages are still on this computer.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d58c1a2241341da850dfef9e8dd7187138c34b74%2Fbackups-saved-pages-kept.png?alt=media" alt=""><figcaption><p>The Saved pages row after the move</p></figcaption></figure>

* **Restoring on the same computer** needs nothing more.
* **Restoring on another computer** asks whether to copy the backup's saved pages into this computer's own storage. **Copy them** copies inside the bucket and downloads nothing; **Restore without them** skips them.
* **The daily cleanup** keeps every saved page that a backup you still keep needs.
* **Bringing the pages back** to this computer warns you, while automatic backups are on, that a backup restored elsewhere will not have them.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6dd102ae21e9604031c20d7dc457f37c3561b7a4%2Fbackups-restore-pages-question.png?alt=media" alt=""><figcaption><p>A restore on another computer: (1) copy the pages, (2) restore without them</p></figcaption></figure>

## Back Up Only Your Settings

A database backup already includes your settings, so use the **App Configurations** tool only when you want the settings alone, to save time re-entering important ones such as the [DataForSEO API](/guide/seo-data-source#how-to-connect-your-dataforseo-account-to-seo-utils), a [rented API key](/guide/rent-dataforseo-api-key), the [Google Maps API](/guide/google-my-business-rank-tracker#setup-the-google-places-api) and [IndexNow](/guide/indexnow).

To open it, go to the user dropdown and select **Backup Tools > App Configurations**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ef99527a2823ab8c91662ac70bcbc06e117e44f4%2FXnapper-2024-11-13-21.07.01.png?alt=media" alt=""><figcaption><p>Access the app configurations backup tool</p></figcaption></figure>

Create and restore a backup file of your settings the same way as in the database tool.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-140764d912c293482756fc3ae9f14139d2c8c2b1%2FXnapper-2024-11-13-21.08.09.png?alt=media" alt=""><figcaption><p>Create &#x26; restore app configurations</p></figcaption></figure>


# Remote Access

Open your own SEO Utils from any web browser — phone, tablet or another laptop — through a private address, while your data stays on your computer.

Remote Access lets you open the SEO Utils that runs on your computer from any web browser — your phone, a tablet, or another laptop — through a private address that belongs to you. Your computer keeps doing the work and keeps your data; the browser is just a window onto it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0ed35e906510161f232629292ef9c17ec2a63ae9%2FXnapper-2026-09-06-19.01.23.png?alt=media" alt=""><figcaption><p>The Remote Access card in Settings, online, showing the private browser address, the status badge and the list of signed-in browsers</p></figcaption></figure>

## How It Works

* **Your computer does the work.** SEO Utils has to be running on your computer, and the computer has to be switched on and online. Nothing moves to the cloud — your reports, keywords and settings stay where they are. The one exception is a report you choose to publish to a client (see [Share Reports with Clients](/guide/white-labeled-client-report)).
* **You get a private address.** After a one-time pairing, your computer gets its own address of the form `https://inst-….seoutils.app`. Open it in any browser to use SEO Utils.
* **Your SEO Utils cloud account keeps it safe.** Sign-in for the browser, approving a new computer, your Remote Access plan and the list of your paired computers all live in your cloud account at [app.seoutils.app](https://app.seoutils.app). Only people signed in to your cloud account can open your address.
* **Each signed-in browser uses a seat.** Your plan includes a number of seats — the browsers that can be signed in at once.

{% hint style="info" %}
Remote Access is managed from the desktop app. If you open the same settings card from a browser, it only tells you to make changes from SEO Utils on your computer.
{% endhint %}

## Before You Start

You'll need:

* **SEO Utils installed and activated** with your license key on the computer you want to reach (see [Manage License Key](/guide/manage-license-key)).
* **A cloud account** at [app.seoutils.app](https://app.seoutils.app). You'll create one in Step 1 if you don't have it yet, and your email address must be verified.
* **An internet connection** on that computer. It has to stay on, with SEO Utils open, whenever you want to use Remote Access.
* **A Remote Access plan** for that computer. You choose it during setup (Step 5) — see [Plans and Pricing](#plans-and-pricing).

## Setting Up Remote Access

Pairing connects your computer to your cloud account. You do it once per computer.

{% stepper %}
{% step %}

#### Create Your Cloud Account (Skip if you already had one)

Go to [app.seoutils.app](https://app.seoutils.app) and click **"Register"**. Enter your name, email address and a password, then click **"Create account"**.

Check your inbox for the verification email and follow its link. The Remote Access pages stay locked until your email address is verified. If you already have a cloud account, just **"Log in"**.

{% hint style="info" %}
Use the same cloud account for all your computers. A Remote Access plan stays with the account that bought it.
{% endhint %}
{% endstep %}

{% step %}

#### Open Remote Access in SEO Utils

In SEO Utils, go to **Settings → Services** and select **Remote Access** in the settings sidebar.

The card says **Not paired yet** and lists the three steps ahead of you.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FkA9o9a4XFXmGRD6cvrQI%2FXnapper-2026-09-06-19.49.30.png?alt=media&amp;token=79906500-634a-45d5-8bb5-935006c4d56b" alt=""><figcaption><p>The Remote Access card before pairing, with the three pairing steps and the Enable Remote Access button</p></figcaption></figure>
{% endstep %}

{% step %}

#### Click "Enable Remote Access"

SEO Utils shows **Your pairing code** — two groups of four characters, such as `7GKP-XT29` — and starts **Waiting for approval…**.

Click **"Open approval page"**. Your browser opens the approval page on app.seoutils.app with your code already filled in. Sign in to your cloud account if asked.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FOOLe0W7vB5mv1wlzQh4f%2FXnapper-2026-09-06-19.50.25.png?alt=media&amp;token=f496eed6-c36d-4786-9dd8-520d1e731705" alt=""><figcaption><p>The pairing code shown in SEO Utils, with the Open approval page and Cancel buttons</p></figcaption></figure>

{% hint style="warning" %}
The code is only valid for a short time — the approval page shows exactly when it expires. If it runs out, click **"Try again"** in SEO Utils to get a new one. You can also click **"Cancel"** to stop pairing.
{% endhint %}
{% endstep %}

{% step %}

#### Approve the Computer

The page **Pair this computer to your account** shows the code and the account you're signed in as. Check two things:

* The code matches the one on your computer's screen.
* **Signed in as** shows the right account. If not, click **"Not you? Switch account"**.

Then click **"Approve pairing"**. Only approve a request you started yourself — click **"Deny"** if you didn't.

The page shows **Approved — setting up your computer…**. Keep it open. Back in SEO Utils, the card changes to **Approved — setting up your address…** and then **Paired. Checking your plan…**. This takes a few seconds.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F0JCPFghGYP9aT334hcGU%2FXnapper-2026-09-06-19.57.15.png?alt=media&amp;token=9909c304-000a-4ff3-bfde-e07e75620b81" alt="" width="563"><figcaption><p>The approval page at app.seoutils.app showing the pairing code, the signed-in account and the Approve pairing button</p></figcaption></figure>
{% endstep %}

{% step %}

#### Choose a Plan

As soon as the pairing completes, the browser takes you to the **Remote Access** page of your cloud account, with your new computer selected and the notice **Your computer is paired but not online yet.**

* Under **Plan**, pick **Remote Access**.
* Under **Extra seats**, add seats if more than one browser will be signed in at once.
* Check **Your order** and click **"Continue to checkout"**. The next screen only collects your card, and billing starts when you finish.

When you come back, the page confirms **Remote Access is now active for this installation.** In SEO Utils, the card fills in with your address by itself — no restart needed.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8d65b3b79556d0ad78081772221214ffc1dfdfae%2FXnapper-2026-09-06-20.07.38.png?alt=media" alt=""><figcaption><p>The Remote Access page at app.seoutils.app with the newly paired computer selected and the plan picker</p></figcaption></figure>

{% hint style="info" %}
Already paying for a Remote Access plan that isn't attached to a paired computer? The new computer picks it up automatically, and the page says **Your existing Remote Access plan moved to this computer.** There is no second checkout.
{% endhint %}
{% endstep %}

{% step %}

#### Your Computer Is Online

The Remote Access card now shows your **Browser address** with a status badge. **Connector running** with a green dot means your computer is reachable.

* Click **"Open in browser"** to try it right away.
* Click **"Copy link"** to send the address to your phone or another computer.

The switch at the top of the card shows **On**, and the card shows when your computer last checked in with your cloud account (**Last hub heartbeat**).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d9256c8865af1477faae97b78a3e2ee3be7d1dba%2FXnapper-2026-09-06-21.28.41.png?alt=media" alt=""><figcaption><p>The Remote Access card online, showing the private address, the Connector running badge and the Open in browser and Copy link buttons</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Opening SEO Utils From a Browser

{% stepper %}
{% step %}

#### Open Your Private Address

Type or paste the address from the Remote Access card into any browser — on your phone, a tablet or another computer.
{% endstep %}

{% step %}

#### Sign In With Your Cloud Account

You're sent to app.seoutils.app to log in. If you're already signed in to your cloud account in that browser, you go straight through.
{% endstep %}

{% step %}

#### Use SEO Utils

SEO Utils opens in the browser with the same workspaces and reports as on your computer. The user menu at the bottom of the sidebar shows the computer's name and **Owner · Remote Access**, so you always know which computer you're working on.
{% endstep %}
{% endstepper %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4bb495bdae3b27ae1d0e21970f208726b2f55726%2FXnapper-2026-09-06-21.30.14.png?alt=media" alt=""><figcaption><p>SEO Utils open in a browser through the private address, with the computer's name and your role in the user menu</p></figcaption></figure>

### Using Your Own Domain

On the **Agency** plan you can reach your computer at your own address — `app.youragency.com` — instead of the address we generate. Your clients see your brand, and your original address keeps working alongside it.

{% stepper %}
{% step %}

#### Add the Domain

In your cloud account, open **Remote Access** and enter the address you want under **Your own domain**. In SEO Utils, **Use your own domain instead of this address** on the Remote Access card opens that page.
{% endstep %}

{% step %}

#### Create Two DNS Records

Both records are shown straight away, with a **Copy** button on each. Add them at whoever manages your domain, then click **"Check now"**.
{% endstep %}

{% step %}

#### Wait for It to Go Live

Your domain is checked and a certificate is issued automatically. This usually takes a few minutes.
{% endstep %}
{% endstepper %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FwosmiJX3ZkIb3wneFKy8%2FXnapper-2026-09-11-10.32.28.png?alt=media&amp;token=f5bf5aaa-0bb5-48de-b31c-ab85f6558fb4" alt="custom domain"><figcaption><p>The custom domain card showing both DNS records and the progress of each step</p></figcaption></figure>

{% hint style="info" %}
Signing in on your own address uses its own seat, so the same browser reaching one computer on both addresses uses two.
{% endhint %}

### What Works in the Browser

Most tools and reports work in the browser exactly as they do on the desktop, and anything you start keeps running on your computer even after you close the browser. A few things stay on the desktop — mainly screens that store credentials or work with files on the computer:

| In the browser                                           | Desktop only                                                                                                                                       |
| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Your workspaces, reports and rank tracking               | **Settings → Services** and every credential screen: Google Service Accounts, Google OAuth tokens, SMTP credentials, proxies and site integrations |
| Running reports and checks, and watching them progress   | **License Manager** and license key entry                                                                                                          |
| Most tools, with the same results as on the desktop      | **Backup Tools** (database and app configuration backups)                                                                                          |
| Copying results and exports the browser can build itself | Onboarding, Manage SERP Data, and a few export and preview buttons                                                                                 |

{% hint style="info" %}
If a button you use on the desktop is missing in the browser, that action is desktop-only for now. Everything else about the tool works the same way.
{% endhint %}

### Seats: Who Can Be Signed In

* A **seat** is one signed-in browser. All tabs in the same browser share one seat; your laptop and your phone use two.
* Every plan includes **1 seat**, and you can add more at any time (see [Adding or Removing Seats](#adding-or-removing-seats)).
* The desktop app on your computer never uses a seat.
* With [Team](/guide/team), each team member and each pending invitation also uses a seat. See [Seats](/guide/team/inviting-your-team#seats).
* Closing the tab does not free the seat — a browser stays signed in for up to 30 days. Sign out to free it, or it is freed automatically after 30 days without activity.

If every seat is taken when you sign in from a new browser, app.seoutils.app shows **Every seat is in use** with the list of signed-in browsers. Click **"Sign out that browser"** next to one of them and your sign-in continues.

### Signing Out of a Browser

Open the user menu in the sidebar and choose **"Sign out this browser"**. You'll see **Signed out of this browser** — its seat is free again — with a **"Sign in again"** link for whenever you want to come back.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f2ebd94ee423af2b7a10daa45f8143e679be91fd%2FXnapper-2026-09-06-21.32.59.png?alt=media" alt="" width="280"><figcaption></figcaption></figure>

### When Your Computer Is Offline

If SEO Utils isn't running, the computer is asleep or shut down, or it has no internet, your address shows a page saying **\[your computer's name] is offline**. It reconnects automatically as soon as the computer running SEO Utils is back online, and the page refreshes itself every minute — there is nothing to do on the browser side.

{% hint style="warning" %}
Remote Access needs SEO Utils **open** on the computer — not just installed. Keep the app running and the computer awake if you plan to work from elsewhere.
{% endhint %}

## AI Apps

Remote Access also lets AI apps such as Claude, ChatGPT, Codex and Cursor use SEO Utils on this computer from anywhere. It needs MCP Access (the MCP add-on) on your license. Turn on **Allow AI apps over Remote Access** in the **AI apps** section of the Remote Access card, then connect each app and manage it from your cloud account. An AI app does not use a browser seat. See [Connect AI Apps From Anywhere](/guide/mcp-server/connect-ai-apps-from-anywhere).

## Turning Remote Access Off and On

Once paired, the switch at the top of the Remote Access card turns browser access **Off** and **On** without unpairing.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-aeee7efc8a8db1dae86d27ef5f297176766bea66%2FXnapper-2026-09-06-21.34.22.png?alt=media" alt=""><figcaption></figcaption></figure>

| Switch  | What happens                                                                                                                                  |
| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Off** | Browser access stops now. Your address shows the offline page, and the card says **Browser access is off. Turn it on to reach this address.** |
| **On**  | Browser access starts the next time the app opens — restart SEO Utils to bring the address back online.                                       |

The switch does not change your plan or your list of signed-in browsers.

## Managing Signed-in Browsers

The **Signed-in browsers** list on the Remote Access card shows every browser that can open your address, with a counter such as **1 of 1** for your seats.

| Column          | What it shows                                                 |
| --------------- | ------------------------------------------------------------- |
| **Browser**     | The account name and a description of the browser             |
| **Status**      | **Active**, or **Pending** while a sign-in is still finishing |
| **Address**     | The address the browser signed in through                     |
| **Last active** | The last time that browser was used                           |

* To free a seat, click **"Sign out"** on its row and confirm in the **Sign this browser out?** dialog. That browser loses access at its next check-in, usually within a minute. Any job it started keeps running on your computer.
* When every seat is taken, the card shows **You've reached 1 of 1 signed-in browsers**. Sign a browser out, or click **"Buy more seats"** to add seats on your cloud account.
* Click the refresh icon to reload the list.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-584caec055d82e229c4cee9bb3d5d37de584d772%2FXnapper-2026-09-06-21.36.04.png?alt=media" alt=""><figcaption><p>The Signed-in browsers list on the Remote Access card, with the seat counter, the Buy more seats button and a Sign out button on each row</p></figcaption></figure>

## Plans and Pricing

Remote Access is an add-on to your SEO Utils license, billed monthly per computer. You choose it on the **Remote Access** page of your cloud account; the same prices are shown publicly at [app.seoutils.app/pricing](https://app.seoutils.app/pricing).

| Plan                       | Price          | What you get                                                                        |
| -------------------------- | -------------- | ----------------------------------------------------------------------------------- |
| **Remote Access**          | $5.99 / month  | Open SEO Utils on this computer from any browser, with **1 browser seat included**  |
| **Remote Access + Agency** | $19.99 / month | Everything in Remote Access, plus employee logins for your team and your own domain |

**Extra seats** cost $1.99 per seat per month on either plan, and you can cancel at any time.

{% hint style="info" %}
Employee logins are part of the Agency plan. See [Team](/guide/team) to invite and manage your team.
{% endhint %}

## Managing Computers and Your Plan

Everything about billing and your paired computers lives on the **Remote Access** page of your cloud account. Open it from the sidebar at [app.seoutils.app](https://app.seoutils.app), or click **"Choose a plan"** or **"Buy more seats"** on the Remote Access card in SEO Utils.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3bcee3c16fff32deeb30df594218e2d8ba2325a1%2FXnapper-2026-09-06-21.37.05.png?alt=media" alt=""><figcaption><p>The Remote Access page at app.seoutils.app listing paired computers with their status and plan badges</p></figcaption></figure>

### Your Computers

Each paired computer has a tile showing its name and status:

| Badge                                                   | Meaning                                                                                                                 |
| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Paired** / **Not paired**                             | Whether the computer is currently connected to your account                                                             |
| **On Remote Access** (plus any extra seats)             | The plan this computer is on                                                                                            |
| **Remote Access active**                                | Paid for and online                                                                                                     |
| **Remote Access not subscribed**                        | Paired, but no plan yet — its address stays offline                                                                     |
| **Payment needs attention**                             | The last payment failed. Remote Access keeps working for up to 7 days while the payment is retried                      |
| **Subscribed — pairing needed**                         | The plan is running, but the computer is no longer paired. Pair it again from SEO Utils                                 |
| **Subscribed — licence problem** / **Licence disabled** | The license on that computer is no longer valid (see [Remote Access and Your License](#remote-access-and-your-license)) |

### Changing Your Plan

{% stepper %}
{% step %}

#### Select the Computer

Click the computer's tile. Its **Current plan** card shows the plan, the monthly price and the seats included.
{% endstep %}

{% step %}

#### Switch and Confirm

Click **"Switch plan"**, choose the other plan, and click **"Update plan"**. The change takes effect now, and the difference is prorated onto your next monthly invoice.
{% endstep %}
{% endstepper %}

### Adding or Removing Seats

In the **Extra seats** section, use **Add a seat** or **Remove a seat**, then click **"Update plan"**. Each extra seat is $1.99 per month.

{% hint style="info" %}
If you remove seats below the number of browsers currently signed in, those browsers stay signed in — but no new browser can sign in until you are under the limit again.
{% endhint %}

### Cancelling or Resuming

* Click **"Cancel at period end"** and confirm with **"Schedule cancellation"**. Remote Access, extra seats and Agency all stop on the date shown, and everything keeps working until then. The computer's tile shows **Ends** with that date.
* Changed your mind? Click **"Resume this plan"** before that date.

{% hint style="warning" %}
Turning Remote Access off, forgetting the pairing, unpairing a computer or deactivating your license does **not** cancel the plan. Billing continues until you cancel it here.
{% endhint %}

### Unpairing a Computer

Unpairing disconnects a computer from your cloud account. Do it when you sell or retire the computer, or want to pair it with a different cloud account. You can do it from either side:

{% tabs %}
{% tab title="From your hub account" %}
On the **Remote Access** page, click **"Unpair…"** on the computer's tile. The **Unpair this computer?** dialog explains what happens:

* The computer is disconnected from your account. Anyone with the desktop app on it can pair it again, with this account or another.
* Your Remote Access plan for this computer is **not** cancelled and keeps billing. To stop paying, cancel it with **"Cancel at period end"**.
* Published reports from this computer stay available.

Click **"Unpair this computer"** to confirm.
{% endtab %}

{% tab title="From SEO Utils app" %}
At the bottom of the Remote Access card, click **"Forget this pairing"** and confirm in the dialog.

Every signed-in browser loses access and your address stops working. Your desktop app and its license are unaffected, and billing for the Remote Access add-on continues until you cancel it separately. You can pair again later.
{% endtab %}
{% endtabs %}

Unpaired computers move to the **Previously paired** list on the Remote Access page. A plan left without a computer keeps billing until you cancel it — or until you pair another computer with the same account, which picks the plan up automatically.

{% hint style="info" %}
To move a computer to a different cloud account, unpair it from the account that has it, then pair it again while signed in to the other account. The plan stays with the original account.
{% endhint %}

## Remote Access and Your License

| License state                                           | Effect on Remote Access                                                                                                                                                                                                                                                                      |
| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active**                                              | Works normally.                                                                                                                                                                                                                                                                              |
| **Expired** (your updates window is over)               | Nothing changes. Remote Access keeps working, billing continues, and an expired key can still pair a computer.                                                                                                                                                                               |
| **Disabled, refunded, or deactivated on this computer** | Remote Access on that computer is paused: the computer is unpaired and signed-in browsers lose access. Your cloud account shows a **Licence disabled** badge and the notice **Your Remote Access plan for … is on a licence key that is no longer valid, so Remote Access on it is paused.** |

A license problem never cancels your plan by itself. Either cancel the plan on the Remote Access page, or activate a valid license on the computer and pair it again — the plan moves to whichever computer you pair next.

### Deactivating Your License on This Computer

If you deactivate your license on a paired computer (user menu → **License Manager** → **Deactivate license on this computer**), two things matter for Remote Access:

* Remote Access on that computer ends immediately. Every signed-in browser loses access and its address stops working.
* Your Remote Access plan is **not** cancelled. It stays on your account, and the next computer you pair with this account picks it up with no new checkout.

The deactivation steps and the expired-key warning are in the [Manage License Key](/guide/manage-license-key#option-3-from-the-app-on-this-computer) guide.

## Troubleshooting

| What you see                                                                                                                             | What it means                                                                                                                                                             | What to do                                                                                                                                                                                                                                           |
| ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Pairing didn't complete**                                                                                                              | The code expired, the request was denied on the approval page, or the pairing was interrupted. The card shows the reason.                                                 | Click **"Try again"** for a fresh code and approve it on app.seoutils.app.                                                                                                                                                                           |
| **Remote Access can't go through a proxy** (older versions: **could not reach the hub**) right after clicking **"Enable Remote Access"** | The computer reaches the internet only through a proxy. Remote Access needs a direct connection.                                                                          | Open the direct connections listed in [Computers Behind a Proxy or Firewall](#computers-behind-a-proxy-or-firewall).                                                                                                                                 |
| **This installation is paired to another hub account**                                                                                   | This computer is currently paired with a different cloud account. The message names that account (with the email partly hidden).                                          | Sign in to that account on app.seoutils.app, open **Remote Access** and click **"Unpair…"** on the computer — or, if you simply approved from the wrong account, use **"Not you? Switch account"** on the approval page. Then click **"Try again"**. |
| **Paired. Choose a plan to bring your address online.**                                                                                  | The computer is paired but has no Remote Access plan yet.                                                                                                                 | Click **"Choose a plan"** and complete checkout. The card recovers on its own.                                                                                                                                                                       |
| **The hub is refusing Remote Access for this installation**                                                                              | The plan for this computer lapsed, so the computer was unpaired.                                                                                                          | Click **"Open the hub"**, choose a plan for the computer again, then click **"Enable Remote Access"** to pair it again.                                                                                                                              |
| **This pairing belongs to a different license**                                                                                          | The license key activated on this computer changed after it was paired.                                                                                                   | Click **"Forget this pairing"**, then **"Enable Remote Access"** to pair again with the current license.                                                                                                                                             |
| **The hub is refusing this installation**                                                                                                | Browser access is paused.                                                                                                                                                 | Wait — this clears on its own if the cause was temporary. If it doesn't, forget the pairing and pair again.                                                                                                                                          |
| Status badge shows **Stopped** or **Retrying…**                                                                                          | Your computer can't reach the cloud right now, or browser access is switched off.                                                                                         | Check the computer's internet connection and the **On** / **Off** switch. If you just switched it on, restart SEO Utils.                                                                                                                             |
| The browser shows **… is offline**                                                                                                       | SEO Utils isn't running, the computer is asleep or off, or it has no internet.                                                                                            | Start SEO Utils on the computer. The page refreshes itself.                                                                                                                                                                                          |
| **Every seat is in use** when signing in                                                                                                 | Every seat is taken by another signed-in browser.                                                                                                                         | Click **"Sign out that browser"** on one of them, or add extra seats.                                                                                                                                                                                |
| You're asked to sign in again                                                                                                            | You signed out, the owner signed that browser out, the browser wasn't used for 30 days, the pairing was changed or forgotten, or the connection was down for a long time. | Log in again at app.seoutils.app.                                                                                                                                                                                                                    |
| **Payment needs attention** on your cloud account                                                                                        | The last payment failed.                                                                                                                                                  | Remote Access keeps working for up to 7 days while the payment is retried. If it isn't completed, the plan ends and the computer is unpaired — subscribe again before pairing.                                                                       |

### Computers Behind a Proxy or Firewall

Remote Access connects straight from your computer to the internet. It does not use a proxy set on the computer (`HTTP_PROXY` / `HTTPS_PROXY`), so on a network where all traffic must go through a proxy, pairing fails. License activation does go through the proxy, which is why it can work on the same computer.

Ask whoever manages the network or server to:

1. Allow outbound connections to `app.seoutils.app` on port **443** (TCP). This is pairing and sign-in.
2. Allow outbound connections to `region1.v2.argotunnel.com` and `region2.v2.argotunnel.com` on port **7844**, over **TCP and UDP**. These relay servers carry your private address.
3. Add `app.seoutils.app` to `NO_PROXY` in the environment SEO Utils starts with, then restart SEO Utils.

{% hint style="warning" %}
If the network allows no direct outbound connection at all, Remote Access can't work on that computer.
{% endhint %}

<details>

<summary>Checking the connections from the computer</summary>

Run these on the computer that runs SEO Utils (Linux or macOS terminal):

1. Check the connection to the cloud account. It should print `200`:

   ```bash
   curl -sS --noproxy '*' -o /dev/null -w "%{http_code}\n" https://app.seoutils.app
   ```
2. Check the connection to the relay. It should report that the connection succeeded:

   ```bash
   nc -vz region1.v2.argotunnel.com 7844
   ```

When both pass, click **"Enable Remote Access"** again.

</details>

{% hint style="info" %}
Still stuck? Post in the [SEO Utils Facebook group](https://www.facebook.com/groups/seoutils).
{% endhint %}

## Frequently Asked Questions

<details>

<summary>Is my data uploaded to the cloud?</summary>

No, with one exception that you choose. Your reports, keywords and settings stay on your computer:

1. The browser talks to your computer through the private address.
2. Your cloud account only handles sign-in, approving computers, seats and billing.
3. When the computer is off, the address shows an offline page — nothing is served from the cloud.

The exception is a report you publish to a client with **Publish to client**. SEO Utils uploads a read-only copy of that report, so your client can open it while your computer is off. Reports you don't publish are never uploaded. See [Share Reports with Clients](/guide/white-labeled-client-report).

</details>

<details>

<summary>Can I use it on my phone?</summary>

Yes. Open your private address in the phone's browser and log in with your cloud account. The phone counts as one signed-in browser, so it uses one seat.

</details>

<details>

<summary>What happens when I close SEO Utils or shut down my computer?</summary>

* Your address shows the **… is offline** page until SEO Utils is running again.
* Anyone using the browser at that moment loses the connection. Once the computer is back, they can carry on — after a long outage they may be asked to log in again.
* Your plan, your pairing and your signed-in browsers are unchanged.

</details>

<details>

<summary>Can I pair two computers?</summary>

Yes. Pair each computer from its own copy of SEO Utils. Every paired computer gets its own address and needs its own plan — Remote Access is billed per computer.

</details>

<details>

<summary>Does closing the browser tab free the seat?</summary>

No. A seat is freed when you choose **"Sign out this browser"**, when the owner signs that browser out from the Remote Access card, or after 30 days without activity.

</details>

<details>

<summary>Does turning Remote Access off cancel my plan?</summary>

No. The switch, **"Forget this pairing"**, **"Unpair…"** and deactivating your license all leave the plan in place. Cancel it with **"Cancel at period end"** on the Remote Access page of your cloud account.

</details>

## Related Guides

{% content-ref url="/pages/XSCk1mZIdhq2Ewkaex7a" %}
[Manage License Key](/guide/manage-license-key)
{% endcontent-ref %}

{% content-ref url="/pages/9qIhGQj6hMFevY4S9lLU" %}
[Share Reports with Clients](/guide/white-labeled-client-report)
{% endcontent-ref %}

{% content-ref url="/pages/rvkHkv2lFV0hYLzWHS1w" %}
[Connect AI Apps From Anywhere](/guide/mcp-server/connect-ai-apps-from-anywhere)
{% endcontent-ref %}


# Team

Give the people you work with their own login to your SEO Utils, choose what each person can do, and see who did what.

Team gives the people you work with their own login to your SEO Utils. They open it in a web browser through your private [Remote Access](/guide/remote-access) address and see only the workspaces you give them, with only the permissions you choose. Your computer still does the work and keeps your data.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-12f35eaf3c89cb723d8872f8b4403aa37aff7f7c%2Fteam-people.png?alt=media" alt="The Team page with the People tab, the seat summary and the Online now badge"><figcaption><p>Settings → Team: your people, their roles and workspaces, and who is online</p></figcaption></figure>

## How It Works

* **Everyone gets a role.** Viewer, Analyst, Manager or Custom decides what a person can do inside a workspace. See [Roles](/guide/team/inviting-your-team#roles).
* **Workspaces are the walls.** Inside a workspace, a team member sees what you see. They never see your other workspaces.
* **Your machine and paid accounts are behind one switch.** Runs that fetch data use your computer, your proxies and your paid accounts (DataForSEO, AI providers). Only people you give **Can use the owner's machine and accounts** can start them.
* **Every action is recorded.** [Team Activity and Spend](/guide/team/activity-and-spend) shows who did what, and what each person's paid calls cost.
* **You stay in control.** Change access, pause or remove a person at any time. The change reaches their browser within about a minute.

## What Team Members Never Get

Some areas are yours alone and are hidden from every team member, whatever their role:

* **Most of Settings**, including API keys, Google accounts and integrations, proxies, SMTP and Remote Access.
* **Creating, renaming or deleting workspaces**, and this Team page.
* **Automations.**
* **Your account balances.** They see the estimated cost of a run, never what is left on your accounts.
* **Renaming or deleting tags.**

## Before You Start

* **Remote Access is set up** and your computer is paired. See [Remote Access](/guide/remote-access).
* **Your plan includes team logins.** They are part of the **Remote Access + Agency** plan. See [Plans and Pricing](/guide/remote-access#plans-and-pricing).
* **Each person has a cloud account** at [app.seoutils.app](https://app.seoutils.app) with the email address you invite. They can create one when they accept.
* **SEO Utils is open on your computer.** Team members can only work while it is, just like you in a browser.

## Where to Find It

Open **Settings → Team** in the sidebar. It is in the desktop app and in your own browser over Remote Access. Team members never see it.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-07710d011a48b299ecf0cb90cc03cc76e37cf17c%2Fteam-settings-nav.png?alt=media" alt="The Settings menu with Team highlighted" width="280"><figcaption><p>Settings → Team in the sidebar</p></figcaption></figure>

## Guides

{% content-ref url="/pages/zWM2z6aKfFcLUvaQUcgF" %}
[Inviting Your Team](/guide/team/inviting-your-team)
{% endcontent-ref %}

{% content-ref url="/pages/ogPs6K1UtwwkyigUxwJF" %}
[Managing People](/guide/team/managing-people)
{% endcontent-ref %}

{% content-ref url="/pages/koJiG7rKf97eL7cd1TNQ" %}
[Team Activity and Spend](/guide/team/activity-and-spend)
{% endcontent-ref %}

{% content-ref url="/pages/kwtq8jrH792LHSVn7gdG" %}
[Who's Online](/guide/team/whos-online)
{% endcontent-ref %}

{% content-ref url="/pages/Vwz0lvqt4nPZQpeEZJCP" %}
[For Employees](/guide/team/for-employees)
{% endcontent-ref %}


# Inviting Your Team

Invite a person, choose their role and workspaces, decide whether they can use your machine and paid accounts, and keep track of seats.

You invite each person by email from **Settings → Team**. The invitation carries the role, the workspaces and the machine access you choose, so the person has everything the moment they accept. Make sure your plan includes team logins first; see [Before You Start](/guide/team#before-you-start).

## Roles

A role is a set of permissions. Inside the workspaces they can open, a team member sees what you see; the role decides what they can change.

| Role        | What the person can do                                                                                                                                                                                   |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Viewer**  | View reports in their workspaces. A Viewer never uses your machine or accounts.                                                                                                                          |
| **Analyst** | Everything a Viewer does, plus run and re-run reports, export data, cancel their own runs, and add tags and annotations.                                                                                 |
| **Manager** | Everything an Analyst does, plus create and edit reports, import files, move reports between their workspaces, publish reports to clients, delete reports, and cancel anyone's runs in their workspaces. |
| **Custom**  | You pick each permission yourself.                                                                                                                                                                       |

<details>

<summary>Custom permissions</summary>

Choose **Custom** to tick exactly the permissions you want.

| Permission                  | What it allows                                            |
| --------------------------- | --------------------------------------------------------- |
| **Run reports**             | Run and re-run existing reports with their saved settings |
| **Create and edit reports** | Create reports, change their settings and keyword lists   |
| **Delete reports**          | Delete reports and their data                             |
| **Import files**            | Upload keyword files and import data into a workspace     |
| **Move reports**            | Move reports between the workspaces they can open         |
| **Publish to clients**      | Share reports in the client portal                        |
| **Export data**             | Download CSV and PDF exports                              |
| **Cancel their own runs**   | Stop runs they started                                    |
| **Cancel any run**          | Stop runs anyone started in their workspaces              |
| **Add tags**                | Create tags and attach them to rows                       |
| **Add annotations**         | Write annotations and edit their own                      |

Machine access is a separate box; see the next section.

</details>

## Machine and Accounts Access

**Can use the owner's machine and accounts** is the one switch for everything that spends your resources: runs that fetch data or spend credits use this computer, its proxies and your paid accounts (DataForSEO, AI providers). You see each person's spend in the [Spend tab](/guide/team/activity-and-spend#spend).

* It is **ticked by default for Analyst and Manager**, and you can untick it.
* A **Viewer never has it**. The box is greyed out for a Viewer.
* Without it, an Analyst or Manager shows a **No machine access** badge in People. Their run buttons and lookups are greyed out with **Ask {your name} for run access**.

{% hint style="info" %}
Lookup tools such as Keyword Explorer are visible to every team member, but using them, and reading their saved results, needs machine access.
{% endhint %}

## Workspace Access

Choose which workspaces the person can open:

* **All workspaces, including future ones.** A workspace you create later is open to them too.
* **A list of workspaces.** Tick the ones they need. **Select all** and **Clear all** help with long lists.

If you pick none, the person can sign in but sees nothing until you add a workspace. They get a waiting page that opens by itself as soon as you do.

## Invite Someone

Open **Settings → Team** and go to the **Invite** tab.

{% stepper %}
{% step %}

#### Enter the email address

Type the address the invitation goes to. The person must use a cloud account with this address to accept.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-737e33b6040fc4e24ba4a14d2a84a885cd15dafd%2Fteam-invite-form.png?alt=media" alt="The Invite tab with an email address, the four roles, the machine access box and the workspace picker"><figcaption><p>The Invite tab: 1 email, 2 role, 3 machine access, 4 workspaces</p></figcaption></figure>
{% endstep %}

{% step %}

#### Choose a role

Pick **Viewer**, **Analyst**, **Manager** or **Custom**. The line under the roles lists what the chosen role can do.
{% endstep %}

{% step %}

#### Set machine access

Leave **Can use the owner's machine and accounts** ticked, or untick it. See [Machine and Accounts Access](#machine-and-accounts-access).
{% endstep %}

{% step %}

#### Choose workspaces

Switch on **All workspaces, including future ones**, or tick the workspaces they can open.
{% endstep %}

{% step %}

#### Send the invitation

Click **"Send invite"**. SEO Utils emails the person a link and shows the invitation in **People** with the status **Invited**.
{% endstep %}
{% endstepper %}

The invitation is valid for **7 days** and holds a seat until it is accepted, revoked or expired. To cancel it, open the row's **...** menu, choose **Revoke invitation** and confirm with **Yes**. The person can then no longer use the link.

What happens next is described in [For Employees](/guide/team/for-employees).

## Seats

The top right of the Team page shows two lines:

* **{n} of {total} seats.** Each team member and each pending invitation uses one seat. A suspended or removed person does not.
* **{n} of {total} browsers signed in, {n} of them yours.** The same total also limits how many browsers can be signed in at the same time, your own included.

Both lines use the same total. Every plan includes 1 seat, so buy extra seats for your team on the **Remote Access** page of your cloud account; see [Adding or Removing Seats](/guide/remote-access#adding-or-removing-seats).

When every seat is in use, the Invite tab says **All seats are in use** and the form is switched off. Buy more seats, revoke an invitation or remove someone to invite another person.

{% hint style="warning" %}
If every browser seat is taken when a team member signs in, they see a page asking them to ask you to free one, and you get an email naming them. Sign out a browser on the Remote Access card to free a seat.
{% endhint %}

## Best Practices

* Start people as **Viewer** or **Analyst**, and move them to **Manager** when they need to create or publish reports.
* Untick machine access for an Analyst or Manager who should not spend your credits. Their runs that fetch data then stay switched off.
* Give each client-facing person only the workspaces they work on.


# Managing People

Change a person's access, pause or remove them, see what they experience afterwards, and require two-factor sign-in for the team.

The **People** tab of **Settings → Team** lists everyone who has, or is about to get, access. Pending invitations come first, then team members.

| Column          | What it shows                                                                                                         |
| --------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Person**      | Name and email. A green dot means the person is [online now](/guide/team/whos-online).                                |
| **Role**        | Viewer, Analyst, Manager or Custom (hover Custom to see its permissions), plus **No machine access** when it applies. |
| **Workspaces**  | **All workspaces**, or the names of the workspaces they can open.                                                     |
| **Status**      | **Invited** (with the date the invitation expires), **Active** or **Suspended**.                                      |
| **Last active** | **Online now**, or how long ago they were last active.                                                                |

Open the **...** menu at the end of a row to act on it.

| Action                | For                 | What it does                                                                     |
| --------------------- | ------------------- | -------------------------------------------------------------------------------- |
| **Edit access**       | Team members        | Change role, machine access and workspaces.                                      |
| **Suspend**           | Active members      | Pause the person. They are signed out and cannot sign in until you restore them. |
| **Restore**           | Suspended members   | Give access back. It needs a free seat.                                          |
| **Remove**            | Team members        | Take the person off the team.                                                    |
| **Revoke invitation** | Pending invitations | Cancel the invitation and free its seat.                                         |

Suspend, Remove and Revoke ask first, in the row: the menu turns into **Remove? Yes · Cancel**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3fc150e3a8aadfc342decca5bf0df9148eb4b2fd%2Fteam-remove-confirm.png?alt=media" alt="A row of the People table asking Remove? with Yes and Cancel buttons"><figcaption><p>Removing someone asks for confirmation in the row itself</p></figcaption></figure>

## Edit Access

Choose **Edit access** to open the person's current access. Change what you need and click **"Save changes"**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f176606e15e17cc7e06acd8fbb8a299fd9943aac%2Fteam-edit-access.png?alt=media" alt="The Edit access dialog with the role, the machine access box and the workspace picker"><figcaption><p>Edit access: 1 role, 2 machine access, 3 workspaces</p></figcaption></figure>

The options are the same as when you [invite someone](/guide/team/inviting-your-team): role, **Can use the owner's machine and accounts**, and workspaces, including **All workspaces, including future ones**. The change reaches the person's browser within a minute, even while they are signed in. If you remove a workspace they are working in, SEO Utils moves them to another one and tells them their access changed.

## Suspend or Remove

|                         | Suspend                          | Remove                                                                   |
| ----------------------- | -------------------------------- | ------------------------------------------------------------------------ |
| **Use it to**           | Pause someone for a while        | End someone's access for good                                            |
| **Their browsers**      | Signed out within about a minute | Signed out within about a minute                                         |
| **Their seat**          | Freed                            | Freed                                                                    |
| **In the People table** | Stays, marked **Suspended**      | The row disappears                                                       |
| **Coming back**         | You click **Restore**            | You send a new invitation; they start with exactly the access it carries |
| **Their past activity** | Kept                             | Kept, under their name                                                   |

Both actions email the person. Neither deletes their cloud account.

### What Happens to Their Work

* **Runs that have not been sent yet** are cancelled with the reason that the person who started them no longer has access.
* **Work already sent to a provider** keeps collecting its results, so you do not lose what you paid for.
* **Schedules** keep running and are shown as **Scheduled** in Activity.
* **Reports they published to clients** stay online at the same link and move to you.

### What They See

The next time they open SEO Utils, or sign in, they land on a page that names your computer and you, and says what to do.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c3f65795d6b5724f4d573a6c46f172bd213a05b0%2Fteam-hub-access-paused.png?alt=media" alt="The Access paused page: Your access is paused, with the owner&#x27;s name and a Go to your dashboard button"><figcaption><p>A suspended team member's sign-in page</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7e79884b38b18ca565294c0f6150078cae7437e3%2Fteam-hub-access-removed.png?alt=media" alt="The page You&#x27;re no longer on this team, with the owner&#x27;s name and a Go to your dashboard button"><figcaption><p>A removed team member's sign-in page</p></figcaption></figure>

| When                    | They read                                                                                                                 |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| You suspended them      | **Your access is paused.** Ask you to restore it. They are still on the team.                                             |
| You removed them        | **You're no longer on this team.** You have to send a new invitation to bring them back.                                  |
| Your seats were reduced | **Your access is paused** because the team's seats were reduced.                                                          |
| Your Agency plan lapsed | **Your team's access is paused.** Ask you to renew. Nothing is deleted, and access returns when the plan is active again. |

{% hint style="info" %}
When you reduce your seats below the size of your team, SEO Utils cancels pending invitations first, then pauses the people who were active least recently. Restore them once a seat is free.
{% endhint %}

## Two-Factor Sign-In for the Team

Below the People table, the **Two-factor sign-in** card has one switch: **Require two-factor for my team**. It is on by default.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-99daf5866fc8c633b7162b454a82c4821d5b54e6%2Fteam-two-factor.png?alt=media" alt="The Two-factor sign-in card with the Require two-factor for my team switch turned on"><figcaption><p>The team two-factor switch</p></figcaption></figure>

* **On:** a team member without two-factor sets it up at their next sign-in, before they continue. They can use an authenticator app or a passkey.
* **Off:** team members can sign in with only their password.

Your own account always needs two-factor, whatever this switch says.


# Team Activity and Spend

See who signed in and who did what, filter the feed, and check what each person's paid calls cost each month.

Two tabs of **Settings → Team** answer "who did that?" and "what did it cost?". Both are for you only; team members never see them.

## Activity

The **Activity** tab lists what happened, newest first. It merges two sources:

* **Your cloud account:** sign-ins and sign-outs, invitations, access changes, suspensions, removals and changes to the team settings.
* **This computer:** what people did in SEO Utils, such as running, exporting and publishing reports.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b09d61de5f343ab8d5513825404b0a2f14402269%2Fteam-activity.png?alt=media" alt="The Activity tab with filters for Date, Person, Action and Workspace above a list of sign-ins, runs and exports"><figcaption><p>The Activity tab: 1 filters</p></figcaption></figure>

Each row shows **When**, **Person**, **Action**, what it was **About**, the **Workspace** and some **Details**. Hover a time to see the exact date.

### What Is Recorded

| Area               | Examples                                                                                                                          |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| **Reports**        | Created, edited, deleted, run, imported, exported, moved, published, unpublished a report                                         |
| **Runs**           | Cancelled a run                                                                                                                   |
| **Tags and notes** | Created, added or removed a tag; added, edited or deleted an annotation                                                           |
| **Sign-ins**       | Signed in, signed out, and a sign-in blocked because every seat was in use                                                        |
| **Team**           | Invited, accepted, revoked, suspended, restored or removed someone; changed a role or workspace access; changed the team settings |

The **Person** is whoever did it. Your own actions are listed too. Runs that start on a schedule show **Scheduled**, and runs started from the MCP server show **MCP**. A name is saved when the action happens, so a person you removed keeps their name on what they did.

### Filter the Feed

Use the filters above the table:

* **Date:** a range of days.
* **Person:** you or one team member.
* **Action:** one or several actions.
* **Workspace:** one workspace. Sign-ins and team changes belong to no workspace, so they are hidden while one is chosen.

{% hint style="info" %}
If your cloud account cannot be reached, the tab says **Showing this computer's activity only** and lists the rest again once the connection is back. Activity from this computer is kept for 400 days.
{% endhint %}

### Who Did What Elsewhere

You also see the person where the work lives:

* **Report header.** A report shows **Created by Priya Shah · Last run by Marcus Lee, 2 hours ago**. Team members see the same line. Reports that existed before this was recorded show it only after their next run, and without the creator.
* **Run log.** The first line of a run's log says **Run started by** the person's name, or **Scheduled run started**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-171947097fe254186030def8f5cf9e447069c19d%2Fteam-report-attribution.png?alt=media" alt="A report header showing Created by Priya Shah and Last run by Marcus Lee, 2 hours ago"><figcaption><p>The report header names who created the report and who ran it last</p></figcaption></figure>

## Spend

The **Spend** tab shows what each person's paid calls cost in one month, including yours.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c00589390e5fe9827328495d5e579de432671aed%2Fteam-spend.png?alt=media" alt="The Spend tab with a month picker, a total, and a table with cost, paid calls, cost unknown and cached lookups for each person"><figcaption><p>The Spend tab: 1 month, 2 calls with an unknown cost, 3 cached lookups</p></figcaption></figure>

1. Pick a **month**. The list goes back about 13 months (400 days).
2. Read the total above the table: the cost, the number of paid calls, and any calls with an unknown cost.
3. Read the row of each person. Your own row is marked **You**, and runs on a schedule are grouped as **Scheduled**.

| Column             | Meaning                                                                                                                |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------- |
| **Cost**           | What the calls cost, in US dollars, for the calls whose cost is known.                                                 |
| **Paid calls**     | Calls to DataForSEO, AI providers and the renting service that were charged.                                           |
| **Cost unknown**   | Paid calls whose provider did not report a cost, shown as **N calls (cost unknown)**. They are not in the Cost column. |
| **Cached lookups** | Lookups answered from the cache. They are free and are not counted as paid calls.                                      |

Click a column heading to sort.

{% hint style="info" %}
Cost is the figure each provider reports for each call, so use your provider's invoice for billing. People with machine access see the estimated cost of a run before they start it, as you do, but never the balance of your accounts.
{% endhint %}


# Who's Online

See which team members are using SEO Utils right now, and which workspace they are in.

The **Online now** badge shows which team members are using your SEO Utils at this moment, and which workspace each of them is in. Only you can see it.

## What Counts as Online

A team member is **online** when they used SEO Utils in the last **10 minutes**. A tab left open in the background does not count, because its automatic refreshes are not use. The list is read every 30 seconds while the page or menu showing it is open.

## Where You See It

### On the Team Page

At the top right of the **People** tab, the **Online now** badge shows one avatar per person. Hover an avatar to see the person's name, their role, the workspace they are in and when they were last active, for example **Manager · In Harbor & Pine Coffee**. The role is the one in the **Role** column of the table: **Viewer**, **Analyst**, **Manager** or **Custom**, and **Owner** for you when you are signed in from a browser. If more than five people are online, a **+N** avatar lists the rest.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8802513cf4233db3971fdd4839480bf49cd60501%2Fteam-online-toolbar.png?alt=media" alt="The Online now badge above the People table with a tooltip showing Priya Shah, her role Manager, her workspace and when she was last active"><figcaption><p>Hover an avatar to see who it is, their role and where they are</p></figcaption></figure>

In the table, people who are online also have a green dot next to their name and **Online now** in the **Last active** column. Everyone else shows how long ago they were last active.

### In Your Browser's User Menu

When you use SEO Utils in your own browser through Remote Access, the same badge sits in the user menu at the bottom of the sidebar, below the line **Signed in as** with your name and email. Open the menu to see up to three avatars. Hover an avatar to see the same details as on the Team page, including the person's role. The desktop app shows it on the Team page only.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f2a23aa3caef0822cc11e96cde80156310199b2d%2Fteam-online-user-menu.png?alt=media" alt="The user menu in the owner&#x27;s browser with a Signed in as line and the Online now badge with two avatars"><figcaption><p>The Online now badge in the user menu of your own browser</p></figcaption></figure>

{% hint style="info" %}
SEO Utils does not store who was online. For history, use [Activity](/guide/team/activity-and-spend#activity).
{% endhint %}


# For Employees

Accept an invitation to a team's SEO Utils, set up two-factor sign-in, and understand what you can and cannot do.

If the owner of an SEO Utils invited you to their team, this page walks you through joining and shows what to expect once you are in. You work in your web browser. The owner's computer does the work and keeps the data.

## What You Need

* **The invitation email** with the subject **You have been invited to SEO Utils**.
* **A cloud account** at [app.seoutils.app](https://app.seoutils.app) with the email address the invitation was sent to. You can create one when you open the invitation, and you have to verify the address.
* **An authenticator app or a passkey**, if the team requires two-factor sign-in. It does by default.

## Join the Team

{% stepper %}
{% step %}

#### Open the invitation

Click the link in the email and sign in, or create an account, with the address the invitation was sent to. The page shows the team, who invited you, your role and your workspaces.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-505492b2e531d78e02279a453a56a74f5e957a54%2Fteam-hub-accept-invitation.png?alt=media" alt="The Team invitation page showing the role Analyst, All workspaces and the Accept invitation button" width="640"><figcaption><p>The invitation: 1 your role, 2 your workspaces, 3 accept</p></figcaption></figure>

{% hint style="info" %}
If the page says **Sign in with the invited address**, you are probably signed in with another account. Choose **Switch account**, then sign in with the address from the email. If you are already using that address, the invitation has expired or the owner withdrew it; ask the owner to send a new one.
{% endhint %}
{% endstep %}

{% step %}

#### Accept it

Click **"Accept invitation"**. You continue straight to the team's sign-in. The invitation link works for 7 days.
{% endstep %}

{% step %}

#### Set up two-factor sign-in

If the team requires it and you have not set it up yet, you land on **Set up two-factor authentication** before you continue. Click **"Enable 2FA"**, scan the QR code (or enter the setup key) in an authenticator app, and enter the code it shows. Save your recovery codes, then click the **Continue to** button that names the team. You can use a passkey instead of an authenticator app.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2d7fc635c7a323e3d875ea2192456e4dace443e3%2Fteam-hub-two-factor-setup.png?alt=media" alt="The Set up two-factor authentication page with the Enable 2FA button" width="600"><figcaption><p>Two-factor setup, once, before your first sign-in</p></figcaption></figure>
{% endstep %}

{% step %}

#### Start working

SEO Utils opens in your browser with the workspaces the owner gave you. When you sign in again, you enter your two-factor code.
{% endstep %}
{% endstepper %}

## Come Back Later

* **Use the same address.** Bookmark the address SEO Utils opened at.
* **Or start from your cloud account.** Sign in at [app.seoutils.app](https://app.seoutils.app). The dashboard lists every team you belong to under **Teams you belong to**; click **Open**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-dad378bba377af6a8873a4cc72bf2e1755d9c553%2Fteam-hub-teams-you-belong-to.png?alt=media" alt="The Teams you belong to card on the dashboard with the team name, the owner, the role and an Open button"><figcaption><p>Teams you belong to, on your cloud account dashboard</p></figcaption></figure>

Open the user menu at the bottom of the sidebar to see which account you are signed in as. **Sign out this browser** signs you out and frees the seat your browser uses.

{% hint style="info" %}
SEO Utils only works while the owner's computer is on and SEO Utils is open there. Otherwise the address shows a page saying the computer is offline, and it reconnects by itself; see [When Your Computer Is Offline](/guide/remote-access#when-your-computer-is-offline).
{% endhint %}

## What You Can Do

* **Your role decides what you can change.** See [Roles](/guide/team/inviting-your-team#roles). If the owner changes your role or workspaces, it reaches your browser within a minute, without signing in again.
* **You only see your workspaces.** The workspace menu at the top of the sidebar lists the ones you were given, and the dashboard and search show the selected one.
* **Some areas are the owner's alone,** such as most of Settings and Automations. They are hidden from you. See [What Team Members Never Get](/guide/team#what-team-members-never-get).
* **Runs use the owner's computer and accounts,** and only with **Can use the owner's machine and accounts**. A run can wait in line behind other runs on the same computer, shown as **Queued — N runs ahead**, without saying whose they are.
* **Your name is on your work.** Reports show **Created by** and **Last run by**, and the owner sees what you do in Activity and what your paid calls cost in Spend.

### Controls You Cannot Use

A control your role does not allow is greyed out. Hover it to see why, for example **Ask Elena Marsh for run access** or **Needs Manager access**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-80dcc1c1ed3a797cfa7654b976b4f0364c9be0ee%2Fteam-employee-run-locked.png?alt=media" alt="A greyed-out Run Tracker button with the explanation Ask Elena Marsh for run access"><figcaption><p>Run Tracker is greyed out: this person has no run access</p></figcaption></figure>

Lookup tools such as Keyword Explorer are visible to everyone, but using them, and reading their saved results, needs machine access. Ask the owner if you need it.

## When Something Looks Different

| What you see                                    | What it means                                           | What to do                                                                                        |
| ----------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| **You don't have access to any workspace yet**  | The owner has not given you a workspace.                | Ask the owner. The page checks regularly and opens a workspace by itself as soon as you have one. |
| A notice **Your access to {workspace} changed** | The owner took a workspace away while you were working. | SEO Utils switched you to another one. Nothing to do.                                             |
| **Your access is paused**                       | The owner paused you, or the team's seats were reduced. | Ask the owner to restore it. You are still on the team.                                           |
| **You're no longer on this team**               | The owner removed you.                                  | The owner has to send you a new invitation.                                                       |
| **Your team's access is paused**                | The owner's team plan has lapsed.                       | Ask the owner to renew. You are still on the team, and you can sign in again after renewal.       |
| **Every seat is in use**                        | All the browsers the team allows are signed in.         | Sign out one of your own other browsers from the list, or ask the owner to free one.              |

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e3d0f7f39c0839b9d647c87c8e0d1fe5212e7bbe%2Fteam-employee-no-workspace.png?alt=media" alt="The home page for a team member with no workspace yet, asking them to ask the owner to add them to a workspace"><figcaption><p>No workspace yet: the page opens one by itself when the owner adds you</p></figcaption></figure>

After the owner pauses or removes you, your browser is signed out within about a minute, and signing in shows the matching page above.


# Dashboard

The health check you see when you open SEO Utils

The Dashboard is the first screen you see when you open SEO Utils. It answers four questions at a glance: which version you're running, how much API credit you have left, whether your local database needs maintenance, and whether any of your paid DataForSEO tasks need attention.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FXUBoYH3cPG0VQ9ucvjy7%2FXnapper-2026-08-10-16.16.33.png?alt=media&amp;token=ca21a99c-0edf-428c-aba6-55bbe74c628c" alt="The SEO Utils Dashboard"><figcaption><p>The Dashboard, with the DataForSEO Needs Attention card showing 66 tasks to review</p></figcaption></figure>

The **Onboarding** button in the top-right corner reopens the setup walkthrough at any time, which is useful when you're connecting a new service.

## Version

Shows the version you're running and its release date.

Click **What's new** to read what changed in this version without leaving the app.

## DataForSEO Balance

Your remaining credit on your own DataForSEO account. This card appears once you've connected your DataForSEO credentials.

**Top Up Balance** opens your DataForSEO account page in your browser so you can add credit.

{% hint style="warning" %}
Reports stop when your balance runs out. If you schedule daily rank tracking, check this card regularly — an empty balance means tasks are never created, and a missed day cannot be recovered later.
{% endhint %}

## Renting API Balance

Your remaining credit if you use a [rented API key](/guide/rent-dataforseo-api-key) instead of your own DataForSEO account. **Top Up Balance** opens the purchase page.

{% content-ref url="/pages/gwYT1OgDY4moZ5jr2WTJ" %}
[Rent DataForSEO API Key](/guide/rent-dataforseo-api-key)
{% endcontent-ref %}

## Database Fragmentation

As you add and delete data over months of reports, your local database accumulates unused space. This card shows how much.

| Badge      | What it means                                                                                   |
| ---------- | ----------------------------------------------------------------------------------------------- |
| **Normal** | Under 20% — nothing to do.                                                                      |
| **High**   | Over 20% — a **Maintain** button appears so you can compact the database and reclaim the space. |

Compacting is optional housekeeping. A fragmented database makes reports slower but doesn't put your data at risk.

## DataForSEO Needs Attention

This card appears **only when something needs looking at**. A Dashboard without it means your paid tasks are healthy.

It shows two badges when they apply:

* **N tasks** — tasks that failed, were rejected, or have not moved for more than 15 minutes
* **N collectors offline** — background workers that have stopped checking DataForSEO for results

Click the card to open the DataForSEO Task Monitor, where you can see collector health and which tasks are recovering on their own.

{% content-ref url="/pages/o4Z0dWCJONqiSdJfaDrV" %}
[DataForSEO Task Monitor](/guide/dataforseo-task-monitor)
{% endcontent-ref %}

{% hint style="danger" %}
**Don't re-run a report to force a slow task.** You pay for the same keywords twice, and the original task is usually still recoverable. Open the Task Monitor first — if the task appears under **Automatic recovery**, the app still has its DataForSEO task ID and is still collecting the result you already paid for.
{% endhint %}

## Disk Full alert

If your disk runs out of space, a **Disk Full** alert appears above the cards and task collection pauses until you free some up.

Nothing is lost while collection is paused. Your results stay at DataForSEO and are collected once there is room to save them safely.

<details>

<summary>Repair actions removed from earlier versions</summary>

Older versions showed Organic SERP and Google Maps queue cards on the Dashboard, along with manual repair actions under **Settings → Services**:

* **Free Organic SERP Tasks**
* **Free Stuck GMB Rank Trackers**
* **Delete DataForSEO Post Tasks**

All of these have been removed. Stuck queues now clear on their own through automatic recovery, and the DataForSEO Task Monitor shows you whether that is happening.

The last action was also unsafe: deleting a task record threw away the DataForSEO task ID and the downloaded result file, which are exactly what the app needs to recover a paid result. Deleting the record never cancelled anything at DataForSEO — it only destroyed your own copy of how to collect it.

If you're following older instructions that mention any of these actions, use the Task Monitor instead.

</details>


# Organic Rank Tracker

The Organic Rank Tracker Dashboard provides a centralized view of all your rank tracking reports, allowing you to monitor performance across multiple domains, devices, and locations from a single screen.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-bfa490126ce47ca252d78b2bf445290349da5526%2F502698006_9868867933182346_6566893985095021518_n.jpg?alt=media" alt=""><figcaption><p>Organic Rank Tracker Dashboard</p></figcaption></figure>

## Accessing the Dashboard

### Via the Left Sidebar Menu

1. Look for the **Dashboard** section in the left sidebar
2. Click on **Organic Rank Tracker** under the Dashboard menu
3. The dashboard will load showing all your rank tracking reports

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f7af973a99ca9a433da5f8bf8b37d05fe071f439%2FXnapper-2025-05-30-10.27.25.png?alt=media" alt="" width="375"><figcaption><p>Access the Organic Rank Tracker Dashboard from the left sidebar</p></figcaption></figure>

### Via the Reports Page

You can also access the dashboard from the [Organic Rank Tracker Reports](/guide/organic-rank-tracker) page by clicking the **Dashboard** button in the top right corner.

## Understanding the Dashboard Layout

### Date Range Filter

At the top of the dashboard, you'll find the date range filter. This filter controls the time period for all data displayed on the page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-af69921e478fd60967c75c049d8d8e83130ebfe5%2FXnapper-2025-05-30-10.29.15.png?alt=media" alt="" width="375"><figcaption><p>Date range filter with preset options</p></figcaption></figure>

{% hint style="info" %}
**Preset Options Available:**

* Past 2 days
* Past 7 days
* Past 30 days
* Past 60 days
* Past 90 days
* Previous Month
* All Time
  {% endhint %}

### Average Position Chart

The chart displays average position trends for all your tracked domains. This powerful visualization helps you spot trends across your entire portfolio at a glance.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ce7592a2890336ce60a1bf5ca9affc03e064e9db%2FCleanShot%202025-05-30%20at%2010.29.56%402x.png?alt=media" alt=""><figcaption><p>Average position trends consolidated by domain</p></figcaption></figure>

**How the Chart Works:**

* **Each line represents one domain** - If you track the same domain across multiple locations or devices, they're combined into a single line
* **Automatic averaging** - When you have multiple reports for one domain (e.g., tracking in US, UK, and Canada), the chart shows the average position across all locations
* **Lower is better** - The Y-axis shows positions, where position 1 is the best
* **Interactive tooltips** - Hover over any point to see exact positions and dates

{% hint style="success" %}
**Example**: If you track "example.com" in 3 different cities, the chart shows one line representing the average performance across all 3 locations, giving you a unified view of your domain's performance.
{% endhint %}

### Reports by Domain

The dashboard intelligently groups your reports by domain, making it easy to monitor performance across different configurations.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-880719276bde5a83222cf412c81e2d20ac9cc3d1%2FXnapper-2025-05-30-10.31.20.png?alt=media" alt=""><figcaption><p>Reports grouped by domain for easy comparison</p></figcaption></figure>

**Benefits of Domain Grouping:**

* **Compare device performance** - See how your mobile vs desktop rankings differ
* **Monitor multiple locations** - Track performance across different countries or cities
* **Unified domain view** - All reports for a domain are visually grouped together

### Domain Search

Quickly find specific domains using the search bar. This is especially helpful when managing many domains.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5cf9f9ac9a71c3bbe809ecc321e4a213c43d2591%2FXnapper-2025-05-30-10.33.33.png?alt=media" alt=""><figcaption><p>Filter reports by domain name</p></figcaption></figure>

## Understanding Report Cards

Each report is displayed as a card containing comprehensive ranking data and metrics.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-8c928a9d6a3200fce24177c82acb1cc55f16625d%2FXnapper-2025-05-30-10.35.00.png?alt=media" alt=""><figcaption><p>Report card</p></figcaption></figure>

### Card Header

The card header displays:

* **Domain name** (e.g., laravel.com)
* **Actual comparison dates** (e.g., Feb 20, 2025 → May 29, 2025)
* **Report configuration**: Device type, search engine, location, and language
* **View Report button** to access the full report details

{% hint style="warning" %}
**Important: Closest Available Dates**

The dates shown in the card header (next to the View Report button) are the actual dates being compared, which may differ from your selected date range. The system automatically finds the closest available snapshot dates for each report.

For example:

* You select: May 25-29, 2025
* Report only has data for: Feb 20 and May 29, 2025
* Dashboard shows: Feb 20 → May 29 comparison
  {% endhint %}

### Metrics Section (Left Side)

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-203763dde79f528f62a18b60f309b164588708a8%2FXnapper-2025-05-30-10.35.48.png?alt=media" alt=""><figcaption><p>Metric section</p></figcaption></figure>

The left side of each card displays position distribution metrics:

#### Position Rankings

* **Top 3**: Keywords ranking in positions 1-3
* **Top 10**: Keywords ranking in positions 1-10
* **Top 20**: Keywords ranking in positions 1-20
* **Top 100**: Keywords ranking in positions 1-100

Each metric shows:

* Previous count → Current count
* Change indicator (↑ increase, ↓ decrease)
* Net change value in parentheses

#### Overall Changes

Below the position rankings, you'll find the overall change summary:

* 🟢 **New**: Keywords that started ranking (weren't ranking before)
* 🔵 **Improved**: Keywords that improved their positions
* 🔴 **Lost**: Keywords that stopped ranking (were ranking before)
* 🟠 **Declined**: Keywords that dropped in positions
* ⚪ **Unchanged**: Keywords that maintained their positions

### Keywords Table (Right Side)

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-75fd0b4908e6f9cc1e11be378fea8a2f110e7fd5%2FXnapper-2025-05-30-10.35.58.png?alt=media" alt=""><figcaption><p>Top 10 performing keywords</p></figcaption></figure>

The right side displays the top 10 performing keywords with:

* **Keyword**: The tracked keyword
* **Position columns**: Shows positions for both comparison dates
* **Diff**: Position change (positive = improvement, negative = decline)
* **Volume**: Monthly search volume
* **KD**: Keyword difficulty score
* **CPC**: Cost per click value

{% hint style="info" %}
**Keyword Sorting**

Keywords are sorted by best current position, with search volume as a secondary sort to ensure consistent ordering when multiple keywords have the same position.
{% endhint %}

## Important Notes

### Understanding Domain Grouping

The dashboard makes it easy to manage multiple reports for the same domain:

* **Visual grouping** - All reports for a domain appear together under a domain header
* **Separate cards** - Each configuration (device/location) gets its own card for detailed analysis
* **Combined chart data** - The average position chart intelligently combines all reports for a domain into one line

{% hint style="success" %}
**Perfect for Multi-Location Tracking**: If you track "mysite.com" for New York, Los Angeles, and Chicago, you'll see:

* 3 separate cards showing detailed metrics for each city
* 1 line in the chart showing the overall average performance
* All 3 cards grouped together under "mysite.com" for easy comparison
  {% endhint %}

## Common Use Cases

**1. Quick Performance Overview**\
Use the dashboard to get a bird's-eye view of how all your tracked domains are performing without opening individual reports.

**2. Identify Trends**\
The average position chart helps you spot overall trends across your portfolio of tracked domains.

**3. Spot Issues Quickly**\
The change metrics (New, Improved, Lost, Declined) help you quickly identify domains that need attention.

**4. Compare Time Periods**\
Use the date filter to compare different time periods and understand how your rankings have evolved.

## Tips for Best Results

### Monitoring Multiple Locations

When tracking the same domain across different locations:

* Each location gets its own detailed card
* The chart combines all locations to show overall trend
* Use this to identify which locations perform best

### Device Comparison

Track both mobile and desktop for comprehensive insights:

* Quickly spot mobile vs desktop ranking differences
* Identify device-specific SEO opportunities
* All device data for a domain stays grouped together

### Using Date Comparisons

The dates shown next to "View Report" button are the actual dates being compared:

* These may differ from your selected range if exact dates aren't available
* The system automatically finds the closest available data
* All metrics in the card use these same dates for accuracy

{% hint style="info" %}
**No data showing?** Check if the report has tracking data within your selected date range. The system needs at least two different dates with data to show comparisons.
{% endhint %}


# NLP Text Analysis

Easily extract important topics and entities from any text or webpage with our NLP Text Analysis tool. Using popular APIs like Google NLP, TextRazor, and Dandelion, it supports around 20 languages.

Whether optimizing content for SEO, performing competitive research, uncovering hidden trends, or finding gaps in topics and entities, NLP Text Analysis provides the clarity and precision your workflow demands. Boost your efficiency and elevate your strategy with deep semantic insights at your fingertips.

### Supported API Drivers

#### 1. Text Razor

Register for an account at [TextRazor](https://www.textrazor.com/signup).

TextRazor offers a free plan with up to 500 requests per day. The free tier includes full access to all features, allowing you to extract entities and topics effectively.

If you need more than 500 requests per day, please consider a paid plan at [TextRazor Plans](https://www.textrazor.com/plans).

After registering an account, you can obtain your API key at your [TextRazor Console](https://www.textrazor.com/console).

To enter the API key to SEO Utils, please visit the **Services** > **Natural Language Processing** page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-3511f184fe693688ff755392ded2b8f1b3a40c3f%2FXnapper-2025-03-12-09.49.14.png?alt=media" alt=""><figcaption><p>Add TextRazor API Key to SEO Utils</p></figcaption></figure>

#### 2. Google NLP

To use Google NLP, you must first enable the "**Cloud Natural Language API**" in your project.

Google NLP offers a free tier providing **5,000 units per month**, where each unit represents 1,000 characters processed. Additional usage beyond the free tier incurs minimal charges based on character count. For complete pricing details and calculations, visit [Google NLP Pricing](https://cloud.google.com/natural-language/pricing).

Visit [Google Cloud Console](https://console.cloud.google.com/) and search for "Cloud Natural Language API" in the top search bar.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-afb9d858a42ed36c17d1a87e3702ba695636bdf0%2FXnapper-2025-03-12-10.06.21.png?alt=media" alt=""><figcaption><p>Find the Cloud Natural Language API.</p></figcaption></figure>

After enabling the API, go to the Credentials tab from the left sidebar. Click on the "Create Credentials" button and select "API Key."

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-29dc308682b85def917929208ca12197871840f3%2FXnapper-2025-03-12-09.58.42.png?alt=media" alt=""><figcaption><p>Create an API key.</p></figcaption></figure>

{% hint style="info" %}
If you already have an existing API key, you can use that instead.
{% endhint %}

Copy the API key from the pop-up window.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6a8bb8bdbe0e7be2ceaa3465be68c6c62a581f2a%2FXnapper-2025-03-12-09.59.50.png?alt=media" alt=""><figcaption><p>Copy the API key.</p></figcaption></figure>

You can edit the API key to add a name and restrict access. It is recommended to restrict the key to only allow access to the Cloud Natural Language API.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e18477c1b321a633e244c58a31c13f1290a517ac%2FXnapper-2025-03-12-10.00.55.png?alt=media" alt=""><figcaption><p>Restrict API key.</p></figcaption></figure>

To enter the API key to SEO Utils, please visit the **Services** > **Natural Language Processing** page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f7fc973316a8d7a78181e2008f8a8913d7ff776e%2FXnapper-2025-03-12-09.50.31.png?alt=media" alt=""><figcaption><p>Enter the Google NLP API Key.</p></figcaption></figure>

#### 3. Dandelion

Register for an account at [Dandelion](https://dandelion.eu/accounts/register/).

Dandelion offers a free tier allowing up to 1,000 requests per day, approximately 30,000 requests per month.

Obtain your API key by visiting your [Dandelion Dashboard](https://dandelion.eu/profile/dashboard/).

For additional requests beyond the free tier, consider upgrading to a paid plan at [Dandelion Pricing](https://dandelion.eu/profile/plans-and-pricing/).

To enter the API key to SEO Utils, please visit the **Services** > **Natural Language Processing** page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-61bda5bef04fb42d720a73d94451b2b994c32584%2FXnapper-2025-03-12-09.49.57.png?alt=media" alt=""><figcaption><p>Enter Dandelion API Key to SEO Utils.</p></figcaption></figure>

### How to Use the NLP Text Analysis Tool

To access the NLP Text Analysis tool, navigate to **NLP > Text Analysis** in the left sidebar. Hit the "Run" button to perform a new analysis.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7e3a273f738034c3e95283edfd29837c088c2883%2FXnapper-2025-03-12-10.26.06.png?alt=media" alt=""><figcaption><p>Text Analysis tool</p></figcaption></figure>

You can enter raw text, HTML, or multiple URLs into the provided input area.

Next, select your preferred API Driver and the language for analysis from the dropdown menus.

After the analysis process is finished, SEO Utils will provide three report pages: **Text Analysis**, **Entities**, **Topics**.

#### 1. Text Analysis Tab

The **Text Analysis** tab breaks your content down sentence by sentence and highlights all detected entities. Simply hover over an entity to view its details!

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-764afb56f14eb10affc7a233069abd4a9e8c3592%2F482116189_9295668087169003_4889640696323789957_n.jpg?alt=media" alt=""><figcaption><p>Text Analysis tab</p></figcaption></figure>

Instead of scanning through large blocks of text, you get a clear, digestible view of the key topics, terms, and important concepts in every sentence. This makes it incredibly easy to refine your content, optimize for SEO, and ensure that your messaging is precise and impactful.

#### 2. Entities Tab

An **entity** is a meaningful word or phrase that represents a real-world concept, such as a person, place, object, event, or idea. Unlike simple keywords, entities have deeper meanings and are linked to other related concepts. This helps you understand not just what words appear in your content, but what they actually represent.

For example, if your text mentions “**New York**”, SEO Utils doesn’t just recognize it as a word but understands it as a city, which belongs to a larger category of locations. This deeper understanding helps you structure content better, and ensure search engines correctly interpret your topics. By detecting and categorizing entities, you can fine-tune your content, focus on the most important subjects, and make it more relevant to your audience.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6a5898e94136e85b3cb20280a6e1547cfbd526d6%2FXnapper-2025-03-12-11.19.04.png?alt=media" alt=""><figcaption><p>Entities Tab</p></figcaption></figure>

* **Relevance Score:** Measures how strongly an entity relates to your content. A high score means the entity is central to the text.
* **Confidence Score:** Measures how confident the API Driver is that the detected entity is correct. A higher score means the detection is more reliable.
* **Mention Count:** Tracks how many times an entity appears in your content. A high count means the entity is frequently referenced.
* **Types**: Categorizes entities based on their meaning, such as **Software**, **Person**, or **Location**. This helps you quickly understand what kind of concepts appear in your content.

Key difference between Relevance Score and Confidence Score:

| Feature              | Relevance Score                                               | Confidence Score                                                              |
| -------------------- | ------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Definition           | Measures how relevant an entity is to the input text.         | Measures how confident the API Driver is that the detected entity is correct. |
| What it Evaluates    | Contextual similarity between the entity and the source text. | Probability that the detected entity is correct, based on multiple signals.   |
| Use Case             | Helps rank entities by importance in the text.                | Helps filter out incorrect or uncertain entity detections.                    |
| Supported API Driver | [TextRazor](#id-1.-text-razor) only.                          | All API Drivers.                                                              |

**Using Mention Count Toggle Button**

You can see how many times each entity appears in your content by clicking the toggle button on each entity row in the table.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5329c0af892414fc3ab1f95188fed2c7bdac2b54%2F482348105_9301755739893571_7965608977519722321_n.jpg?alt=media" alt=""><figcaption><p>Mention Count Toggle Button</p></figcaption></figure>

**Using Filters for Entity List**

1. **Filter by Relevance Score** – Focus on the most important topics in your content.

* **Use Case:** If you want to analyze core topics for SEO or research, filtering by high Relevance Score ensures you see only the most relevant entities. For example, if your article is about “*coffee brewing*”, terms like “*espresso*” and “*French press*” will have high relevance, while broader terms like “*beverages*” might be excluded.

2. **Filter by Confidence Score** – Remove incorrect or uncertain entity detections.

* **Use Case:** If you are analyzing a large text and need high-accuracy results, filtering by high Confidence Score ensures that only correctly detected entities are included. For example, if “*Apple*” appears in a tech article, a high confidence score ensures it refers to the company rather than the fruit.

3. **Filter by Mention Count** – Identify the most frequently used entities.

* **Use Case:** If you want to track dominant topics in your content, filtering by mentionCount helps you find terms that appear most often. This is useful for content structuring and topic clustering. For example, if “*climate change*” is mentioned 20 times in an article, but “*global warming*” only appears twice, you might focus on emphasizing “climate change” in your SEO strategy.

By adjusting these filters, you can fine-tune your entity analysis, whether you need **precise topic identification** (high relevance), **accurate entity detection** (high confidence), or **frequently mentioned topics** (high mention count). 🚀

#### 3. Topics Tab

{% hint style="warning" %}
Only [TextRazor](#id-1.-text-razor) supports topic extraction, so you can only see the Topics tab when using that API driver.
{% endhint %}

A **topic** is a broad subject or theme that your content discusses. Topics provide a high-level understanding of what your text is about, grouping related concepts under general categories like Business, Science, or Technology. Unlike entities, which represent specific names or objects, topics capture the overall theme of your content, helping you see its main focus at a glance.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-01cfa02b926bfbe4958cc9995fb41729fae13cd3%2FXnapper-2025-03-12-11.52.37.png?alt=media" alt=""><figcaption><p>Topics Tab</p></figcaption></figure>

* **Score:** Measures how relevant a topic is to the input text. The higher the score, the more relevant the topic is. Score ranges from 0 to 1.
* **Coarse Topics:** General categories.

**Key Differences Between Topics and Entities**

| Feature     | Topics                                                  | Entities                                         |
| ----------- | ------------------------------------------------------- | ------------------------------------------------ |
| Definition  | General themes or subject categories                    | Specific real-world objects, names, or concepts  |
| Purpose     | Helps categorize content and understand its broad focus | Identifies key terms and their semantic meaning  |
| Examples    | *Business, Science, Mathematics*                        | *New York, Tesla, Python (programming language)* |
| Granularity | High-level classification                               | Detailed and specific references                 |

While **entities tell you exactly what appears in the text, topics help you see the bigger picture**, making it easier to categorize, summarize, and optimize your content for relevance and clarity.

**Key Differences Between Topics and Coarse Topics**

| Feature     | Topics (Fine-grained)     | Coarse Topics (Broad)     |
| ----------- | ------------------------- | ------------------------- |
| Granularity | More specific topics      | General categories        |
| Example     | Google Search             | Technology                |
| Use Case    | Detailed topic extraction | Broad text classification |

**Use Cases for the Topics Tab**

1. **Content Categorization & Relevance**

* Use Case: Ensure your content aligns with your target niche.
* Example: If you’re writing about “*eCommerce trends*,” but the detected topics are **Business** and **Marketing**, it confirms your content is on track. However, if unrelated topics like **Mathematics** or **Arts** appear, you might need to adjust your content focus.

2. **Topic Gap Analysis**

* Use Case: Compare your content topics against competitor content to find missing areas.
* Example: If competitors covering “*email marketing*” are categorized under **Digital Marketing**, but your article only shows **Business**, you may need to add more relevant details to strengthen topic alignment.

3. **Improving Search Intent Matching**

* Use Case: Make sure your content aligns with what search engines expect for a given keyword.
* Example: If you’re targeting “*AI in healthcare*,” but your topics only show **Technology**, adding more medical references can help trigger **Health & Medicine** topics for better search relevance.

4. **Optimizing Internal Linking & Topic Clusters**

* Use Case: Identify content clusters for better internal linking.
* Example: If multiple articles on your site are categorized under **Web Development**, you can interlink them to create a **stronger topical authority** on that subject.

5. **Structuring Content for Featured Snippets**

* Use Case: Improve content structure by ensuring clear topic coverage.
* Example: If your article about “*Best SEO Practices*” is categorized under **Business** but lacks SEO or **Digital Marketing**, adding a structured section with on-page, off-page, and technical SEO could improve your chances of ranking in Google’s featured snippets.

By leveraging topic detection, you can ensure **better content alignment, improve topical authority, and optimize your content for higher rankings in search results**. 🚀


# Content Struct

The **Content Struct** tool lets you input one or multiple seed keywords. SEO Utils will then scrape the top 20 Google SERP results for those keywords, collecting all headings, main content, and SEO metadata—including meta titles and descriptions.

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-bbf66f5a8b235e32a1dcc3244fd2bca69212827f%2FXnapper-2025-03-26-10.51.11.png?alt=media" alt=""><figcaption><p>Content Struc tool</p></figcaption></figure></div>

You can export the scraped data to other tools within SEO Utils, such as [NLP Text Analysis](/guide/nlp-text-analysis), to extract entities and topics from the content. Alternatively, you can use the data to manually build a comprehensive content outline—or generate one instantly with AI, all in a single click.

### Create a Content Struct

To create a new Content Struct, head to the left sidebar and click on “Content Struct.” Then, simply click the “**Create Content Struct**” button to get started.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c074c9c22650973f48fa6ab2636fe062ff0ba0e2%2FXnapper-2025-03-26-10.53.06.png?alt=media" alt=""><figcaption><p>Access the Content Struct tool.</p></figcaption></figure>

Next, enter your main keyword and choose the target locale you’d like to focus on.

**Excluded Domains:** If you want to skip scraping headings and metadata from certain domains (e.g., youtube.com, reddit.com), simply add them to this field.

**Scrape SERP With:** This field functions just like the Organic Rank Tracker tool. For detailed information on how it works, please refer to the “Scraping SERP Methods” section in the [Organic Rank Tracker guide](https://help.seoutils.app/guide/organic-rank-tracker#scraping-serp-methods).

{% hint style="warning" %}
**Important:** To use the SERP API, you must have your own DataForSEO account. [Renting API key services](https://help.seoutils.app/guide/rent-dataforseo-api-key) isn't viable because DataForSEO restricts certain endpoints that I utilized to implement the Queue mode. If multiple users rely on a rented API key from my account, it will slow down the process for everyone. For the quickest results, using your own DataForSEO account is the best approach.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ccc06801b8ccb9c8dad97266c7d9d110e20d9725%2FXnapper-2025-03-26-10.56.12.png?alt=media" alt=""><figcaption><p>New Conent Struct Form</p></figcaption></figure>

#### Bulk Mode

You can enable Bulk Mode by toggling the switch on, allowing you to enter multiple keywords at once. When Bulk Mode is active, you can also assign a Group Name to organize your keywords. This makes it easy to identify which keywords belong to the same group, filter them accordingly, and quickly switch between them.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-eb3dd190bc0ae6cb6d3f1668770b8505fcc90b16%2FXnapper-2025-03-27-08.28.10.png?alt=media" alt=""><figcaption><p>Filter content structs by group</p></figcaption></figure>

### Content Struct Detail

After creating a new Content Struct, you’ll be redirected to the Content Struct detail page, which is divided into two main sections.

On the **left side**, you’ll find all the scraped data from the top 20 Google SERP results—this includes headings, metadata, and main content.

On the **right side**, you’ll see your Content Outline. You can use the “**Show/Hide My Content Outline**” button to toggle the visibility of your outline as needed.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a45a7cf90cde729a873bf55d672ff47baf5bcbd9%2FXnapper-2025-03-27-08.41.20.png?alt=media" alt=""><figcaption><p>Content Struct Detail</p></figcaption></figure>

You can copy all headings, metadata, and main content—or add specific headings from a competitor’s URL directly to your content outline.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-c701461308a59984fce48ef768255ab0466dcb1b%2FXnapper-2025-03-27-08.49.09.png?alt=media" alt="" width="375"><figcaption><p>Copy or add headings to your content outline</p></figcaption></figure>

#### Manage Your Content Outline

Use the checkboxes to select headings in your content outline. You can then delete them, promote a heading (using the left arrow icon), or demote a heading (using the right arrow icon) to adjust its level.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f20d1623a2a0c01cd0def65f38d27125c39e995e%2FXnapper-2025-03-27-08.52.00.png?alt=media" alt="" width="375"><figcaption><p>Manage your content outline</p></figcaption></figure>

You can also rearrange headings by simply dragging and dropping them into your preferred order.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-2f01ba61604e70d49b1579d2598828d1f953bc18%2FCleanShot%202025-03-27%20at%2008.55.22%402x.png?alt=media" alt="" width="375"><figcaption><p>Move headings</p></figcaption></figure>

### Auto-generate Content Outline using AI

In addition to adding headings manually, you can use AI to generate a content outline automatically. The AI-generated outline includes hierarchical headings, a meta title, and a meta description to help you get started quickly.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-1e82709716f0b03ef09a4e40da1ff75166a47063%2FXnapper-2025-03-27-09.00.34.png?alt=media" alt="" width="563"><figcaption><p>Auto Generate Outline</p></figcaption></figure>

Please [follow this guide](/guide/bulk-seo-metadata-optimizer#choose-the-ai-model) to set up your LLM provider API keys or connect a local LLM using Ollama.

Once your API keys are configured, click the “**Auto Generate Outline**” button. You can choose your preferred AI model and customize both the **instruction** and **prompt** sent to the LLM.

{% hint style="info" %}
SEO Utils also provides a default setup, so you can start generating content outlines right away.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-0a76363cd49731c0c041b648d912848b1d74f3f9%2F486055323_9380230298712781_7484248210886069612_n.jpg?alt=media" alt=""><figcaption><p>Customize prompt and instruction</p></figcaption></figure>

{% hint style="success" %}
**Tips**

* Please select an AI model with a **large context window**, as SEO Utils sends detailed competitor data—including metadata and headings—to the model.
* Local models with smaller parameters (*e.g., llama3.2:latest (3.2B), mistral:latest (7.2B), llama2:latest (7B)*) typically do not generate high-quality content outlines. For better results, use a larger model (e.g., **32B, 70B**) or a **cloud-based model** from providers like **OpenAI** or **Anthropic**.
  {% endhint %}

### Export a Content Struct

ou can export your Content Struct as a **DOCX** file directly to **Google Drive** by clicking the **download icon** button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ae9f65afa1fc8634476472a384c0d4c77d378e05%2FXnapper-2025-03-27-09.16.50.png?alt=media" alt=""><figcaption><p>Export your content sturct</p></figcaption></figure>

### Setup Google Drive API Integration

To export to Google Drive, you'll need to take one extra step: enable the Google Drive API. Please [follow this guide](/guide/google-service-accounts) to create a Google Service Account and obtain your **JSON key file**—it's completely free. Make sure to also enable the **Google Drive API** in your Google Cloud project.

After obtaining your API key and copying the service account email, go to [Google Drive](https://drive.google.com/drive/u/0/) and create a new folder. Then, share the folder with the service account email.

Next, copy the Folder ID from the URL of your Google Drive folder. For example, if the URL is:

`https://drive.google.com/drive/u/0/folders/1GvqiPSvGEDgq2yKOC52VGtS433iZXMIv`

then the **Folder ID** is: `1GvqiPSvGEDgq2yKOC52VGtS433iZXMIv` .

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-25f8ffe446c64f07fa8d45fdbf01a01cce9eef97%2FXnapper-2025-03-27-09.23.22.png?alt=media" alt=""><figcaption><p>Create a folder on Drive and share the permission to the Google Service Account email.</p></figcaption></figure></div>

Lastly, In the SEO Utils app, go to the Services page from the left sidebar.

Upload the **Google Service Account JSON Key file** you downloaded earlier, and paste the **Google Drive Folder ID** into the corresponding input field—just like shown in the screenshot below.

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-18522c5144ceaee33077a8551d5437c28991d8c9%2FXnapper-2025-03-27-09.33.09.png?alt=media" alt=""><figcaption><p>Etner all information</p></figcaption></figure></div>

That’s it! You can now export your Content Struct to Google Drive. All exported files will be saved directly to the folder you created.

### Troubleshooting

#### Unable to retrieve headings due to error.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-bc99e75fbd072dbd31a2785fc8d872f960a174e0%2FCleanShot%202025-03-27%20at%2009.53.57%402x.png?alt=media" alt="" width="563"><figcaption><p>Error when scraping data</p></figcaption></figure>

Sometimes, you may see an error like the one shown in the screenshot above. This usually happens when the website blocks SEO Utils’ scraper, preventing it from retrieving the data.

To fix this, click the “**Enter HTML manually instead**” button. A modal will open, where you can click the provided link to open the URL in your browser.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b6b91427115b255bcde4780020246e98662755f2%2FXnapper-2025-03-27-09.57.30.png?alt=media" alt="" width="563"><figcaption><p>Add HTML content modal</p></figcaption></figure>

After that, right-click anywhere on the page and select “**View Page Source**” from the context menu.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6caeb4c28c1e920db867adbe1c78ba2fb39904f6%2FXnapper-2025-03-27-09.58.29.png?alt=media" alt="" width="563"><figcaption><p>View page source to grab HTML</p></figcaption></figure>

Then, copy the entire HTML content and paste it into the “**HTML Content**” field in the SEO Utils app. Click the “**Extract Data**” button, and you’ll see the headings, metadata, and main content extracted from that URL.


# Log File Analysis

Track which bots — Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot, ChatGPT-User and more — are crawling your site, what they're fetching, and whether they respect your robots.txt. The tool reads raw server access logs and turns them into an AEO/GEO-focused dashboard.

## Creating a report

Open **Log File Analysis** in the sidebar and click **New Analysis**. Enter a report name and domain, then pick how SEO Utils should get your logs:

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-094bff80ba792c265eabebb2f9db1a17b7c944df%2FXnapper-2025-06-08-15.05.42.png?alt=media" alt=""><figcaption><p>Log File Analysis in the sidebar</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FwAnyxNUus52YuLOE132R%2FXnapper-2026-05-01-10.44.02.png?alt=media&amp;token=976f1ae3-e219-40e0-83c5-dfe82fae3984" alt=""><figcaption><p>Create form</p></figcaption></figure>

{% tabs %}
{% tab title="Upload files" %}
Best for one-off analyses, historical archives, or servers without SSH/FTP access.

Drag `access.log` / `.gz` archives into the create form and submit. Apache Combined, Nginx Combined, and Cloudflare Logpush files are auto-detected; compressed `.gz` archives work without unzipping.

**Where to find logs:**

| Server                      | Path                                                                               |
| --------------------------- | ---------------------------------------------------------------------------------- |
| Apache (Ubuntu/Debian)      | `/var/log/apache2/access.log`                                                      |
| Apache (CentOS/RHEL)        | `/var/log/httpd/access_log`                                                        |
| Nginx                       | `/var/log/nginx/access.log`                                                        |
| cPanel                      | Metrics → Raw Access                                                               |
| Plesk                       | Websites & Domains → Logs                                                          |
| Cloudflare (Workers, Pages) | Logpush export — see [Getting logs from Cloudflare](#getting-logs-from-cloudflare) |

Re-uploading is safe. SEO Utils fingerprints the first 20 lines of each file, so the same file twice is a no-op, and an extended file imports only the new entries.

To add more files later, open the report and click **Add Log Files** — same dedup rules apply.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F9btXSjfJ6YsHa85a21QI%2FXnapper-2026-05-01-10.56.18.png?alt=media&amp;token=762e35ad-a381-44db-83fa-831d6570cc4d" alt=""><figcaption><p>Add Log Files dialog on an existing report</p></figcaption></figure>
{% endtab %}

{% tab title="Connect a source" %}
Best for continuous monitoring. Give SEO Utils SFTP, FTP, or FTPS access once and it pulls new logs on a schedule. After submitting the create form, the Add Source dialog opens automatically. For sites on Cloudflare, the source reads a storage bucket instead — see [Getting logs from Cloudflare](#getting-logs-from-cloudflare).

{% hint style="info" %}
**Is this for me?** If your site runs on **cPanel, shared hosting, Wix, Squarespace, or Webflow**, automated log access is usually disabled — use **Upload files** instead. SFTP/FTP is common on VPS providers (Laravel Forge, Hetzner, DigitalOcean, AWS Lightsail) and managed-WordPress hosts that advertise SFTP support (Kinsta, WP Engine, Pressable).
{% endhint %}

**What you'll need before you start:**

* The server's **hostname or IP** (e.g. `45.63.38.207` or `logs.example.com`)
* A **username** with read access to the log directory
* Either a **password** or a **private key file** — your host or developer gave you one of these when they set up the server
* The **folder path** where access logs live on that server (we'll list the common ones below)

If any of those are unfamiliar, ask your developer or host for "SFTP credentials and the path to the access log directory" — that one sentence covers it.

{% hint style="info" %}
The scheduler runs in-process — sources fetch only while SEO Utils is open, with a catch-up pass on every launch.
{% endhint %}

{% stepper %}
{% step %}
**Connection details**

* **Source name** — any label, e.g. "production web1".
* **Protocol** — leave as **SFTP** unless your host specifically told you otherwise. SFTP is the same secure protocol as the `ssh` command and is what nearly every modern VPS uses. Pick FTP or FTPS only if your host instructed you to.
* **Host / Port / Username** — the port auto-fills to the standard for each protocol (22 for SFTP, 21 for FTP, 990 for FTPS implicit). Only change it if your host uses a non-standard port.

{% hint style="warning" %}
If Test connection later returns `lookup HOST: no such host` for an IP address you typed, the Host field has trailing whitespace from copy-paste. Re-type it.
{% endhint %}
{% endstep %}

{% step %}
**Authentication**

Pick whichever your host gave you:

* **Password** — type the SFTP/FTP password they supplied. Simplest if you have it.
* **Private key** *(SFTP only)* — paste the entire contents of your private key file, including the `-----BEGIN…-----` and `-----END…-----` header/footer lines. On macOS/Linux the file is typically `~/.ssh/id_rsa` or `~/.ssh/id_ed25519`; on Windows look in `C:\Users\<you>\.ssh\`. If the key is protected with a passphrase, a passphrase field appears — fill it in.

For **FTPS** specifically, your host will tell you Explicit mode (port 21, the common case) or Implicit (port 990, rare).

{% hint style="info" %}
Credentials never touch the SEO Utils database. They live in your OS keychain (macOS Keychain, Windows Credential Manager, Linux Secret Service); the report row only stores an opaque pointer.
{% endhint %}
{% endstep %}

{% step %}
**File selection**

**Remote directory** — the folder on the server that contains your access logs.

| Server / Host            | Common path                                       |
| ------------------------ | ------------------------------------------------- |
| Nginx (default)          | `/var/log/nginx/`                                 |
| Apache (Ubuntu/Debian)   | `/var/log/apache2/`                               |
| Apache (CentOS/RHEL)     | `/var/log/httpd/`                                 |
| Laravel Forge (per-site) | `/home/forge/<your-site>/` *or* `/var/log/nginx/` |
| Plesk (per-site)         | `/var/www/vhosts/system/<your-site>/logs/`        |

Not sure? Ask your host or developer "where do my access logs live?" and paste their answer here.

**File glob** — a simple wildcard pattern that picks which files to fetch.

| If you want…                                         | Pattern                   |
| ---------------------------------------------------- | ------------------------- |
| The active log plus rotated archives *(recommended)* | `access.log*`             |
| Just one site on a multi-site server                 | `example.com-access.log*` |
| Anything Nginx writes that mentions access           | `*access*`                |

The trailing `*` is what catches the rotated archives (`access.log.1`, `access.log.2.gz`, …).
{% endstep %}

{% step %}
**Schedule and backfill**

* **Interval** — Hourly / Every 6 hours / Daily *(default Daily)*. Daily is enough for most sites; pick Hourly if you need near-realtime AEO monitoring.
* **Initial backfill** — Last 7 days, **Last 30 days** *(recommended)*, Last 90 days, or Everything available. This decides how far back the first run looks; later runs only pick up new entries.

{% hint style="warning" %}
The backfill cutoff is **permanent for this source**. Files older than the cutoff are never fetched, even on a future "Run now". If you need older history later, upload those archives manually instead.
{% endhint %}
{% endstep %}

{% step %}
**Test connection and save**

Click **Test connection**. SEO Utils opens the connection, lists matching files, and samples the newest one to confirm the format is supported.

A green "Found N files… Detected format: nginx\_combined" panel means you're good to **Save**. The source then appears in the report's **Sources** tab and the scheduler picks it up within a minute.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FpfYsJalpGlvfLAhsIUUB%2FXnapper-2026-05-01-11.27.14.png?alt=media&amp;token=5d176302-50bf-4f72-82db-2a5833d02d62" alt=""><figcaption><p>Successful Test connection result with file count and detected format</p></figcaption></figure>

**If Test connection fails, the error usually maps to one of these:**

| Error                    | What it usually means                                            |
| ------------------------ | ---------------------------------------------------------------- |
| `lookup …: no such host` | Trailing whitespace in Host (re-type), or DNS can't resolve it   |
| `i/o timeout`            | Wrong port, or the server's firewall is blocking your IP         |
| `permission denied`      | Wrong password/key, or the username doesn't match the credential |
| `no files matched`       | Remote directory is wrong, or the glob pattern doesn't match     |

{% hint style="info" %}
**About the host-key check (SFTP only):** on first connect SEO Utils records the server's SSH fingerprint. If that fingerprint changes on a future run (unusual), SEO Utils blocks the run as a safety measure — that pattern can indicate someone intercepting your connection. If you legitimately rebuilt the server, delete and re-add the source.
{% endhint %}
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}

## Getting logs from Cloudflare

Sites served by Cloudflare Workers or Pages have no server access log. Cloudflare **Logpush** exports the same request data as files into a storage bucket, and SEO Utils reads them from there on a schedule. Logpush is available on every Cloudflare plan: the first 25 GB per month are free, then Cloudflare bills by usage.

{% stepper %}
{% step %}

#### Create a Logpush job in Cloudflare

In the Cloudflare dashboard, open your domain, go to **Logpush**, and click **Create a Logpush job**.

* **Destination** — **R2 Object Storage** (cheapest) or Amazon S3. Turn on **Organize logs into daily subfolders**.
* **Dataset** — **HTTP requests**.
* **Send the following fields** — tick the fields in the table below.
* **Timestamp format** *(Advanced Options)* — any option works.

Create one job per domain. For full details, see Cloudflare's guides for [R2](https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/r2/) and [Amazon S3](https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/aws-s3/).
{% endstep %}

{% step %}

#### Create a read-only key for the bucket

{% tabs %}
{% tab title="Cloudflare R2" %}
In Cloudflare, go to **R2 Object Storage → Manage API Tokens → Create Account API token**.

* **Permissions** — **Object Read only**.
* **Specify bucket(s)** — **Apply to specific buckets only**, then pick the Logpush bucket.

Click **Create Account API Token** and copy the **Access Key ID** and the **Secret Access Key**. Cloudflare shows the secret only once.
{% endtab %}

{% tab title="Amazon S3" %}
In the AWS console, go to **IAM → Users → Create user**.

1. Attach a policy that lets the user list the Logpush bucket and read its files, and nothing else (see below).
2. Open the user, go to **Security credentials → Create access key**, and choose **Application running outside AWS**.
3. Copy the **Access key** and the **Secret access key**. AWS shows the secret only once.

<details>

<summary>Read-only policy for the Logpush bucket</summary>

Replace `your-logpush-bucket` with the bucket name in both places.

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "s3:ListBucket",
      "Resource": "arn:aws:s3:::your-logpush-bucket"
    },
    {
      "Effect": "Allow",
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::your-logpush-bucket/*"
    }
  ]
}
```

</details>
{% endtab %}

{% tab title="Other S3-compatible storage" %}
Create an access key that can list the bucket and read its files. Most providers call this a read-only key.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

#### Add a source to the report

Open the site's report, go to **Sources**, click **Add source**, choose **S3 / R2 bucket**, and click **Next**.

Choose the **S3 / R2 connection** that holds the read-only key. To add it, click **New connection**, enter a **Name** and the fields below, then click **Add connection**. See [S3 / R2 Connections](/guide/s3-r2-connections) for details.

{% tabs %}
{% tab title="Cloudflare R2" %}

1. **Storage** — **Cloudflare R2**.
2. **Cloudflare account ID** — paste the account ID, or the bucket's **S3 API** URL from its settings page.
3. **Access key ID** — from the token.
4. **Secret access key** — from the token.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-55f418124fb31f1aef3b5d63b65005423a380459%2Flog-file-analysis-add-r2-source.png?alt=media" alt="Add log source dialog with a Cloudflare R2 connection chosen in the S3 / R2 connection picker"><figcaption><p>Choosing the Cloudflare R2 connection for the source</p></figcaption></figure>
{% endtab %}

{% tab title="Amazon S3" %}

1. **Storage** — **Amazon S3**.
2. **Region** — the bucket's AWS Region, for example `us-east-1`.
3. **Access key ID** — from the IAM user.
4. **Secret access key** — from the IAM user.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-098501ba9dba97e19cacd6c43c29d833a057f78a%2Flog-file-analysis-add-s3-source.png?alt=media" alt="Add log source dialog with an Amazon S3 connection chosen in the S3 / R2 connection picker"><figcaption><p>Choosing the Amazon S3 connection for the source</p></figcaption></figure>
{% endtab %}

{% tab title="Other S3-compatible storage" %}

1. **Storage** — **Other S3-compatible storage**.
2. **Endpoint** — the provider's S3 endpoint, for example `https://s3.example.com`.
3. **Region** — the bucket's region. Leave it empty if the provider has none.
4. **Access key ID** and **Secret access key** — from the provider.
   {% endtab %}
   {% endtabs %}

On the next step, enter the **Bucket** and the **Folder** the Logpush job writes to. Leave the folder empty if the job writes to the top of the bucket.

Click **Test connection**. SEO Utils lists the newest day folder and shows the detected format, **cloudflare\_logpush**. Then choose how far back to import and how often to fetch.
{% endstep %}
{% endstepper %}

Each file is imported once. If a download breaks, the next fetch continues where it stopped. A file that cannot be read (empty, damaged, or missing the required fields) is skipped and named on the source card.

To import files by hand instead, download the `.log.gz` files from the R2 or S3 console and upload them with **Add Log Files**. There is no need to unzip them.

**Fields to send.** If a required field is missing, the import stops and names the fields to add to the job.

| Field                                                                | Why SEO Utils needs it                              |
| -------------------------------------------------------------------- | --------------------------------------------------- |
| `ClientIP`                                                           | Required — verifies that a bot is genuine           |
| `ClientRequestUserAgent`                                             | Required — identifies the bot                       |
| `ClientRequestMethod`, `ClientRequestURI`                            | Required — the page that was requested              |
| `EdgeResponseStatus`                                                 | Required — status codes and error rates             |
| `EdgeStartTimestamp`                                                 | Required — when the request happened                |
| `ClientRequestHost`                                                  | Recommended — keeps each site in its own report     |
| `ClientRequestReferer`, `ClientRequestProtocol`, `EdgeResponseBytes` | Optional — referrers and AI queries, response sizes |

{% hint style="info" %}
**One file covers every subdomain.** A Logpush job exports all hosts of a domain, such as `example.com`, `blog.example.com`, and `shop.example.com`. Each report keeps only the requests for its own domain (`www.` counts as the same site), so give each subdomain's report its own source with the same bucket and folder. This needs the `ClientRequestHost` field.
{% endhint %}

{% hint style="warning" %}

* Logging starts when you create the job. Cloudflare cannot export traffic from before that.
* Logpush covers your own domains, not `*.workers.dev` or `*.pages.dev` addresses.
* Files you already uploaded by hand are imported again by a source. Choose a backfill range that starts after them, or **From now on**.
* SEO Utils only reads the bucket. To keep storage costs down, add a lifecycle rule in R2 or S3 that deletes old files, for example after 30 days.
  {% endhint %}

## Managing sources

Each source row has a status badge and three actions.

| Badge                 | Meaning                                  |
| --------------------- | ---------------------------------------- |
| **Pending first run** | Saved but never run yet                  |
| **Running**           | Actively fetching (with a spinner)       |
| **OK**                | Last run succeeded                       |
| **Failing (N)**       | N consecutive failures. Auto-pauses at 5 |
| **Paused**            | Disabled                                 |

* **Run now** — fire immediately, ignoring the schedule.
* **Pause / Resume** — toggle on/off. Resuming clears the failure counter.
* **Delete** — removes the config and its keychain credentials. Historical imports stay; aggregates aren't touched.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FCVtAxLur423te3eaLf9I%2FXnapper-2026-05-01-11.30.24.png?alt=media&amp;token=267ca161-c2a3-4886-86a0-0224597555b5" alt=""><figcaption><p>Sources tab with status badges and per-source actions</p></figcaption></figure>

## Switching between upload and source modes

You can mix both modes on the same report. One thing to know:

* **Rotated archives are safe.** Both paths key dedup on `(report_id, SHA256 of first 20 lines)`. A manual upload of `access.log.5.gz` plus the source scanning the same file → second one is skipped.
* **The growing `access.log` is the trap.** It uses byte-offset watermarking with a synthetic per-run identifier, so it can't dedup against a manual snapshot of the same content. Uploading a tail of the live file AND connecting a source to the same path will double-count the overlap.

Practical rule: **let the source own the live file.** Use manual uploads for one-off historical archives.

## Classifying newly detected bots

SEO Utils ships with a built-in list of known bots. When your logs contain a bot that isn't on it, the bot is added automatically with a best-guess category and flagged for review. A banner appears at the top of the report asking you to confirm.

Getting these right matters: the category decides which AI View bucket the bot's traffic lands in (AI Answer, AI Assistant, AI Training, Search…), so your AEO charts are only as accurate as these classifications.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Frdz2dwO5trB0JnQKINWe%2FXnapper-2026-08-04-10.11.56.png?alt=media&amp;token=3a060280-6a4b-449a-9548-c387765aec67" alt=""><figcaption><p>New bots banner with Review all and Copy bot names buttons</p></figcaption></figure>

Each bot gets one of these categories:

| Category          | Examples                           |
| ----------------- | ---------------------------------- |
| AI Answer engines | PerplexityBot, OAI-SearchBot       |
| AI Assistants     | ChatGPT-User, Claude-User          |
| AI Training       | GPTBot, CCBot, Bytespider          |
| Search engines    | Googlebot, Bingbot                 |
| Social            | Facebook, Twitter/X link previews  |
| SEO tool          | AhrefsBot, SemrushBot              |
| Monitoring        | Uptime checkers, security scanners |
| Other             | Everything else                    |

For a handful of bots, pick a category per row in the banner and click **Confirm**. For a large batch, click **Review all** to open a dialog that lists every pending bot at once.

### Reviewing in bulk with AI help

The fastest way to classify dozens of bots is to let an AI assistant do the first pass:

{% stepper %}
{% step %}

#### Open the review dialog

Click **Review all** on the banner. The dialog lists every pending bot with its current best-guess category.
{% endstep %}

{% step %}

#### Copy the AI prompt

Click **Copy AI prompt**. This copies a ready-made prompt containing the category list and all bot names in the expected answer format.

Paste it into ChatGPT, Claude, or any AI assistant.
{% endstep %}

{% step %}

#### Paste the answer back

Copy the AI's reply, paste it into the **Paste AI answer** box, and click **Apply to list**.

SEO Utils matches each line to a bot and pre-selects its category. A summary shows how many lines were applied; lines that couldn't be matched are listed so you can handle those bots manually.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FaMg9RcgQamRdfl0mNHPd%2FXnapper-2026-08-04-10.18.26.png?alt=media&amp;token=0383cfb7-5035-45c7-ae16-3d2234f196ae" alt=""><figcaption><p>Review dialog after applying a pasted AI answer</p></figcaption></figure>
{% endstep %}

{% step %}

#### Adjust and confirm

Scroll the list, correct anything the AI got wrong, then click **Confirm all**. The whole batch is saved and the banner clears.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Prefer to work in your own spreadsheet or chat? **Copy bot names** (on the banner and in the dialog) copies all pending bot names, one per line, without the prompt wrapper.
{% endhint %}

Clicking **Dismiss** hides the banner for now; unreviewed bots reappear the next time you open the report.

## The report dashboard

Each report has six tabs.

| Tab                     | What it shows                                                            |
| ----------------------- | ------------------------------------------------------------------------ |
| **AI View** *(default)* | AEO/GEO panels — see below                                               |
| **Overview**            | Summary metrics, daily activity timeline, status/file-type/device donuts |
| **Bot Details**         | Per-bot activity, error rates, device breakdown                          |
| **Pages**               | Most-crawled pages with per-bot hit counts                               |
| **Sources**             | Connected SFTP/FTP sources (see above)                                   |
| **Advanced**            | Maintenance — see below                                                  |

### AI View

The default tab. A range picker in the report header (default: Last 30 days) drives the windowed panels; two are all-time by design.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FtbZqb5kvIO76GAnLqVUC%2FXnapper-2026-05-01-11.31.12.png?alt=media&amp;token=14abf341-3ba6-4670-ad00-f86790021bec" alt=""><figcaption><p>AI View tab with the six AEO/GEO panels</p></figcaption></figure>

#### AI vs Search traffic

Stacked area chart of daily hits by bucket — AI Answer (PerplexityBot, ClaudeBot, OAI-SearchBot…), AI Assistant (ChatGPT-User, Claude-User, Gemini-User), AI Training (GPTBot, CCBot, Google-Extended, Bytespider…), Search (Googlebot, Bingbot…). Watch the AI Answer line growing relative to Search — that's the AEO story.

#### Pages fetched by AI answer engines

URLs hit by `ai_answer` bots, with per-bot breakdown, last AI visit, and an expandable "top queries" cell. Sortable by total hits, last hit, or error rate.

#### Top queries routing AI to your site

Grouped by extracted query string, with the dominant bot and top landing pages per query.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F0NTgIDyfAQrR79V0z9TH%2FXnapper-2026-05-01-11.32.21.png?alt=media&amp;token=224fa7b5-1bfd-4a4a-b145-34380385b902" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Why this list might look short:** SEO Utils can only extract queries from bots that share them in the `Referer` header — Perplexity, You.com (YouBot), Phind. ChatGPT-User, Claude-User, and Gemini-User intentionally strip prompt data, so their hits never produce a query row. A low total is normal if your AI traffic is mostly OpenAI/Anthropic assistants.
{% endhint %}

#### Stale for AI / AI-only interest *(all-time)*

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FWjBphe0WQP4kqLxy0TCx%2FXnapper-2026-05-01-11.35.12.png?alt=media&amp;token=13e46fd4-53dc-48c6-a2f0-2c097a24da48" alt=""><figcaption></figcaption></figure>

* **Stale for AI** — pages Googlebot has crawled recently where AI bots are 7+ days behind or have never visited. Content AI engines may be missing.
* **AI-only interest** — pages AI bots crawl that Googlebot rarely touches. Long-tail content AI is finding that traditional search is deprioritising.

#### Per-bot error rates

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FVmgAmGivSN9JniZXUFoU%2FXnapper-2026-05-01-11.35.47.png?alt=media&amp;token=ea7b3ffc-7129-401c-adbf-fca7dd04053d" alt=""><figcaption></figcaption></figure>

Status-class matrix per AI bot: 2xx / 3xx / 4xx / 5xx + computed error rate. A 4xx/5xx spike means AI engines are seeing broken pages — those errors poison their answers about your site.

#### Robots.txt compliance

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F2fUgGgbd08XB9R7kEPSh%2FXnapper-2026-05-01-11.36.22.png?alt=media&amp;token=350e1cd1-1302-4de4-a750-5fbd9d80409d" alt=""><figcaption></figcaption></figure>

Per-AI-bot table showing whether each bot is allowed at `/`, total hits in the window, and how many of those hits violated a `Disallow` rule.

| `allowed` | `violations` | Meaning                                    |
| --------- | ------------ | ------------------------------------------ |
| true      | 0            | Welcome and behaving                       |
| false     | 0            | Opted out and respecting it ✓              |
| false     | > 0          | **Ignoring your `Disallow`** — investigate |

Your `robots.txt` is fetched from `https://{your-domain}/robots.txt` once per 24h and cached on the report.

### Overview, Pages, Bot Details

The classic dashboard, broken across three tabs.

#### Summary cards

Total requests, unique bots, error rate, and average response time. Response time is "N/A" if your server isn't logging it — add `%D` to Apache `LogFormat` or `$request_time` to Nginx `log_format`.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-de72de5401dcee49a37a5078a838d6bf8fdb90eb%2FXnapper-2025-06-08-15.10.07.png?alt=media" alt=""><figcaption><p>Summary cards</p></figcaption></figure>

#### Bot activity timeline

Daily volume per bot — useful for spotting crawl-rate changes after a content update or robots.txt change.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f5cbcf2b9066b3c2f5e6d83f6bd96749193d256f%2FCleanShot%202025-06-08%20at%2015.11.33%402x.png?alt=media" alt=""><figcaption><p>Bot activity timeline</p></figcaption></figure>

#### Distribution donuts

Status codes, file types, and devices at a glance. If images / CSS / JS dominate file types, your crawl budget is being burned on assets — block them in `robots.txt` for AI bots.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-90cf85ee666ee8f2f7af88745dcc3bf8247fa3c4%2FXnapper-2025-06-08-15.12.35.png?alt=media" alt=""><figcaption><p>Status / file type / device donuts</p></figcaption></figure>

#### Most crawled pages *(Pages tab)*

Sorted by crawl frequency, with per-bot hit columns and "Every N minutes" cadence labels. High-frequency pages are your most valuable surface — make sure AI bots are in the per-bot mix.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-d318dafc2d9cf434f6e730c0bcca4442ede5bc24%2FCleanShot%202025-06-07%20at%2022.18.08%402x.png?alt=media" alt=""><figcaption><p>Most crawled pages</p></figcaption></figure>

#### Per-bot detail *(Bot Details tab)*

Pick any bot to see its requests, status-class breakdown, devices, and a per-day trend.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-f299dc02e85c8cbc97b2ef20647cbdab3bc16ec2%2FCleanShot%202025-06-08%20at%2015.15.35%402x.png?alt=media" alt=""><figcaption><p>Per-bot detail</p></figcaption></figure>

#### Inconsistent status alerts

If a page returns different status codes across requests, an alert appears with a "View Details" link. Common causes: load-balancer or CDN misconfiguration, intermittent 503s under load, dynamic 404/200 conflicts. Fix the root cause, then re-import to confirm.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-08791f22e952aae9e3c893694c7352e458197385%2FXnapper-2025-06-08-15.17.24.png?alt=media" alt=""><figcaption><p>Inconsistent status code alert</p></figcaption></figure>

### Advanced

Two cards.

* **Optimize historical data** — visible only on reports created before the AI/LLM upgrade (`bucket_schema_version = 0`). Click **Rebuild bucket columns** to backfill the denormalised AI Answer / Assistant / Training / Search hit columns. The AI View works without this — it falls back to a live join — but rebuilding is faster on long date ranges. Idempotent; the button disappears once complete.
* **Danger zone — Delete report** — removes the report and everything attached: aggregates, log import history, sources, AI-request rows, and the keychain credentials those sources used. Cannot be undone.

## Exporting tables to CSV

Most analytical tables have an **Export CSV** button in their header. Exports honour the active date range and the table's current sort. Paginated tables export every row, not just the visible page. Filenames default to `{domain}-{table}-{YYYY-MM-DD}.csv`.

| Tab     | Tables with Export CSV                                                                                                      |
| ------- | --------------------------------------------------------------------------------------------------------------------------- |
| AI View | Pages fetched by AI answer engines, Top queries, Per-bot error rates, Robots.txt compliance, Stale for AI, AI-only interest |
| Pages   | Most Crawled Pages                                                                                                          |

## Tips for LLM SEO

* Aim for an overall error rate under 5%. AI bots don't retry as aggressively as search engines.
* Keep response times under 500ms — slow servers shrink crawl budget.
* Don't block AI bots in `robots.txt` unless you mean to. Once blocked, your content can't influence their answers.
* If AI Answer traffic is flat while Search keeps growing, something on your site is blocking AI specifically — check `robots.txt`, firewall rules, and bot user-agent allowlists.
* Re-import logs weekly so trends and freshness signals stay fresh. Or connect a source and forget about it.


# Share Reports with Clients

Publish a read-only copy of a GMB, Organic, LLM or GSC Rank Tracker report to a link your client opens in any browser, with no sign-in and nothing to install, even while your computer is off.

**Publish to client** puts a read-only copy of a report online at a private link. Your client opens the link in any web browser, with no sign-in and nothing to install, and the report stays available while your computer is switched off.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F2R2tSD85RXjDSQKDJymE%2FXnapper-2026-09-27-15.25.24.png?alt=media&amp;token=99433194-085d-4332-b4f6-4d0f1306c324" alt=""><figcaption><p>The Publish to a client dialog for a published GMB Rank Tracker report, showing the Published badge, the Publish automatically switch, the client link and the password field</p></figcaption></figure>

## How It Works

* **A read-only copy, stored in the cloud.** When you publish a report, SEO Utils uploads a copy of it. Your client opens that copy, not your computer, so your computer can be off.
* **Nothing for your client to set up.** The link opens the report straight away. You can add a password if you want one.
* **It stays up to date.** With **Publish automatically** on, the report publishes a new version after its runs finish. Updates normally upload only the parts that changed, so they are quicker than the first publish.
* **Your report stays yours.** Your client can look at the report but cannot change it. Nothing you do to the published copy changes the report or its data in SEO Utils.

{% hint style="info" %}
You can publish reports from four tools: [GMB Rank Tracker](/guide/google-my-business-rank-tracker), [Organic Rank Tracker](/guide/organic-rank-tracker), [LLM Rank Tracker](/guide/llm-rank-tracker) and [GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker).
{% endhint %}

## Before You Start

You'll need:

* **The SEO Utils desktop app** on the computer that has the report. You publish from the desktop app. The option is not available when you use SEO Utils in a browser through Remote Access.
* **Remote Access set up on that computer**: paired with your cloud account and switched **On** (see [Remote Access](/guide/remote-access)).
* **The Remote Access + Agency plan** for that computer (see [Plans and Storage](#plans-and-storage)).
* **A report that has finished at least one run.** For a GSC Rank Tracker, at least one refresh that downloaded data.
* **SEO Utils open and online while it publishes.** When the upload is done, your computer can be off. Your client still sees the report.

### When Something Is Missing

If this computer cannot publish yet, the dialog shows a setup panel in place of **"Publish now"**, with the one button that fixes it: for example **"Set up Remote Access"** when the computer is not paired, or **"Upgrade to Agency"** when its plan has no Agency. Until then, a waiting report shows **Setup needed**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Ft8EknH8T7cvHZ9qMVPhe%2FXnapper-2026-09-27-20.29.34.png?alt=media&amp;token=9ad01794-a6e5-4263-a645-5eee60790431" alt="" width="563"><figcaption><p>The setup panel in the Publish to a client dialog, with the button that fixes what is missing</p></figcaption></figure>

## Publishing a Report

{% stepper %}
{% step %}

#### Open the Report

Open the GMB, Organic, LLM or GSC Rank Tracker report you want to share. A GSC Rank Tracker is on the **Rankings** page of its Search Console property.
{% endstep %}

{% step %}

#### Open "Publish to client"

Click the report's name in the bar at the top of the page, then **Publish to client**. The **Publish to a client** dialog opens.

{% hint style="info" %}
After the first publish, the **Publish to client** menu item shows the report's status at a glance: a small dot and one word, such as **Published** or **Publishing**.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a3f48ec43b06c9daf2df96a1ccf0de030248c728%2Fclient-report-publish-menu.png?alt=media" alt="The menu under an Organic Rank Tracker report&#x27;s name with Publish to client as its first item" width="563"><figcaption><p>Click the report's name (1), then Publish to client (2)</p></figcaption></figure>
{% endstep %}

{% step %}

#### Turn On "Publish Automatically"

Turn on the **Publish automatically** switch: *"Publish a new version each time this report finishes running."*

The badge changes to **Shared**. The report publishes after its next run, and the **"Publish now"** button appears.
{% endstep %}

{% step %}

#### Click "Publish Now"

Click **"Publish now"** to publish the latest run straight away. A progress card shows how far it is:

* **Publishing… preparing the report.**
* **Publishing… 1,250 of 3,064 cards**, with a progress bar. The report is uploaded in small pieces called cards, and the count shows how many are sent.
* **Publishing… making the new version visible.**

You don't have to wait: *"You can close this window. Publishing continues in the background, and reopening it shows where it is."*

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FoSayku9VfFuenxpeY93h%2FXnapper-2026-09-27-15.28.33.png?alt=media&amp;token=03f0eebb-7d2f-4598-8f56-d093e0632e5c" alt=""><figcaption><p>The progress card in the Publish to a client dialog while a report uploads, with the count of cards sent and the progress bar</p></figcaption></figure>

{% hint style="info" %}
The first publish of a large report can take several minutes. Later versions normally upload only what changed, so they are faster. SEO Utils publishes one report at a time, and the next one starts by itself.
{% endhint %}
{% endstep %}

{% step %}

#### Your Report Is Published

The badge shows **Published**, with the **Version** number. **Data as of** is the date of the newest finished run of the report, which is the data **"Publish now"** publishes. For a GSC Rank Tracker, it is the newest day with Search Console data (Pacific time). Your client's page shows its own **Data as of** date at the bottom.

The **Client link** appears below the switch. Next, [share the link](#sharing-the-link).
{% endstep %}
{% endstepper %}

## Sharing the Link

The **Client link** field shows the address of the published report, on app.seoutils.app. Click the copy button beside it to copy the link, then send it to your client.

Below the link, SEO Utils reminds you: *"Anyone with this link can view it unless you add a password."*

{% hint style="warning" %}
Without a password, anyone who gets the link can open the report, for example if your client forwards the email. Add a password before you send the link if the report must stay private.
{% endhint %}

### Adding a Password

{% stepper %}
{% step %}

#### Enter a Password

In **Add a password (optional)**, type the password. The field appears after the report is published.
{% endstep %}

{% step %}

#### Click "Set"

SEO Utils confirms: *"The password is set. Clients will be asked for it."* The status line changes to *"Clients with the link and the password can view this report."*
{% endstep %}

{% step %}

#### Send the Password to Your Client

SEO Utils does not show the password again after you set it, so keep a note of it. Send it to your client separately from the link.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Your computer must be online to set a password, because the password is stored with the published report and never on your computer. During an upload, the password can be changed once the current publishing step finishes.
{% endhint %}

### What Your Client Sees With a Password

When your client opens the link, a page titled **This report is protected** asks them to *"Enter the password the report owner shared with you."* They type it and click **"View report"**. A wrong password shows *"That password is not correct."*

The browser remembers the password for **30 days**, so your client doesn't have to type it on every visit.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FuHyyY0Cc84AmJW9dIbHx%2FXnapper-2026-09-27-15.29.29.png?alt=media&amp;token=bb366561-ba4e-4f1d-887b-54c09b3677df" alt="" width="563"><figcaption><p>The This report is protected page a client sees before entering the password</p></figcaption></figure>

### Changing or Removing the Password

* **Change it:** Type the new password in **Change the password** and click **"Set"**. Every browser that used the old password is asked for the new one.
* **Remove it:** Click **"Remove"**. SEO Utils confirms: *"The password is removed. Anyone with the link can now view this report."*

{% hint style="success" %}
Sent the link to the wrong person? Change the password. The old password stops working at once for everyone.
{% endhint %}

## Google Maps in Published GMB Reports

A published GMB Rank Tracker report draws its map with your **Browser Maps key**, the separate Google Maps key you also use for the map in Remote Access. For a GMB report, the dialog has a **Google Maps key for published reports** section with a **Set** or **Not set** badge.

{% hint style="warning" %}
*"Published reports use your Browser Maps key, and anyone who opens a published report can see it."* Always restrict this key to the websites it is used on, and never use your **Google Places API Key** for it.
{% endhint %}

{% stepper %}
{% step %}

#### Add the Key if It Is Not Set

If the badge shows **Not set**, the map of the published report shows **Map unavailable**.

Click **"Open the Browser Maps key setting"**. SEO Utils opens **Settings → Services** at the Google My Business Rank Tracker section. Enter the key in **Browser Maps JavaScript Key** and save. To create a key, follow [Setup the Google Places API](/guide/google-my-business-rank-tracker/set-up#google-places-api-key).

Saving the setting does not change reports that are already published. After you add or change the key, click **"Publish now"** on the report, so the published map uses the new key.
{% endstep %}

{% step %}

#### Allow the Published Reports Website

In the [Google Cloud Console](https://console.cloud.google.com/apis/credentials), edit the Browser Maps key:

1. Under **Application restrictions**, select **Websites**.
2. Add `https://app.seoutils.app/*`. The dialog shows the exact address to add.
3. Keep your Remote Access address in the list if you use the map in the browser too.
4. Under **API restrictions**, allow the **Maps JavaScript API** and the **Geocoding API**.
5. Click **Save**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FpwKkv3NZ31NpPHy65am7%2FXnapper-2026-09-27-15.30.45.png?alt=media&amp;token=ef3d3881-0425-4cbc-aa30-d37b16a01d74" alt=""><figcaption><p>The Google Maps key for published reports section of the dialog, with the Set badge, the website restriction to add and the Open the Browser Maps key setting button</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Use Your Own Domain for Client Reports

On the Agency plan, your clients can open published reports on your own address, such as `reports.your-agency.com`, instead of app.seoutils.app. One domain covers the published reports of every computer on your account, and each report's app.seoutils.app link keeps working.

{% stepper %}
{% step %}

#### Add the Domain

Sign in at [app.seoutils.app](https://app.seoutils.app), open **Remote Access** and find **Client report domain**. Enter a subdomain, for example `reports.your-agency.com`, and click **"Add domain"**. Use a subdomain, not your bare domain.
{% endstep %}

{% step %}

#### Add the Two DNS Records

The card shows two records to add where your domain's DNS is managed:

1. A **TXT** record that proves you control the domain.
2. A **CNAME** record that points your subdomain to `customers.seo-utils.com`.

Under **Show names as**, choose **Host** for providers such as Namecheap or GoDaddy, or **Full name** for Cloudflare or Route 53, and copy each value with its **Copy** button.

{% hint style="warning" %}
If your DNS is on Cloudflare, set the CNAME record to **DNS only** (grey cloud). A proxied (orange cloud) record does not work.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-26fcbfba98e52a41e72dc32e81402f382c06f686%2Fclient-report-domain-records.png?alt=media" alt=""><figcaption><p>The Client report domain card while the domain is set up: (1) the TXT record, (2) the CNAME target and (3) the DNS only note for Cloudflare</p></figcaption></figure>
{% endstep %}

{% step %}

#### Wait Until It Is Live

The card checks your records every 20 seconds. After your DNS provider publishes them, SEO Utils confirms the domain and issues its certificate, which usually takes a few minutes. The card then shows **Live since** and the address your reports open at.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-96eb49d040adceab63fe2787165003d6198a001a%2Fclient-report-domain-live.png?alt=media" alt=""><figcaption><p>The Client report domain card once the domain is live: (1) the Live badge and (2) the reminder to allow the domain on the Browser Maps key</p></figcaption></figure>
{% endstep %}

{% step %}

#### Allow the Domain on Your Google Maps Key

Published GMB maps load your Browser Maps key from your domain too. In the [Google Cloud Console](https://console.cloud.google.com/apis/credentials), edit the key and add `https://reports.your-agency.com/*` under **Websites**, next to `https://app.seoutils.app/*`. Without it, maps on your domain show **Map unavailable**.
{% endstep %}
{% endstepper %}

Once the domain is live, the Publish dialog shows the link on your domain as the **Client link**, with the app.seoutils.app address below it. Both open the same report.

{% hint style="info" %}
To stop using the domain, click **"Remove domain"** on the card. Links on your domain stop working at once; the app.seoutils.app links keep working. Removing the CNAME record at your DNS provider also takes your domain offline.
{% endhint %}

## What Your Client Sees

Your client sees the report page as it looks in SEO Utils, but read-only:

* **One report only.** There is no sidebar, no list of your other reports and no settings. The page shows no account name, computer name or logo.
* **The same views and tabs.** For example, the timeline, Bird's Eye and trend views of a GMB report, the Overview, Pages, Rankings Distribution, Competitors Discovery, Keyword Fluctuation and Insights tabs of an Organic report, and its [Traffic tab](#the-traffic-tab), or the charts and the Keywords, Pages and Movers tabs of a GSC Rank Tracker.
* **Date presets that start from the newest data.** A preset such as the past 7 days counts back from the newest data in the published version, not from today.
* **A "Data as of" date** at the bottom of the page, so your client knows how fresh the data is.
* **Always the latest version.** If your client has the page open when a new version is published, the page reloads by itself, within a few minutes or when they come back to the tab.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FlG57UkgraLxDw0IR473g%2FXnapper-2026-09-27-15.34.05.png?alt=media&amp;token=107c698d-d130-4b9e-a9f1-11c6641928ee" alt=""><figcaption><p>A published Organic Rank Tracker report open in a browser, with the report tabs and the Data as of date at the bottom of the page</p></figcaption></figure>

### The Traffic Tab

When an Organic Rank Tracker report has a GA4 property chosen in its **Site traffic (GA4)** field in **Edit Tracker** (see [Show Site Traffic in the Report](/guide/organic-rank-tracker#show-site-traffic-in-the-report)), the published report gets a **Traffic** tab. It shows your client where the site's visitors came from: the KPI cards, the sessions by channel chart, the Channels table, key events by channel, top sources and the last 13 months, as on the [GA4 Traffic](/guide/google-analytics-4/ga4-traffic) page.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-19d813e712c81eb6dc17b2f851a7d3f8ac76200f%2Fportal-traffic-tab.png?alt=media" alt="The Traffic tab of a published Organic report with the date presets, the comparison and the KPI cards"><figcaption><p>The Traffic tab (1), the date presets (2) and the comparison (3)</p></figcaption></figure>

* **Date presets only.** Your client picks a preset such as **Past 7 days** or **Previous Month**, and a comparison. There is no custom date range.
* **See it before you publish.** The report in SEO Utils has the same [Traffic tab](/guide/organic-rank-tracker#the-traffic-tab), anchored on its newest snapshot, so it shows what a version published now would show. There you can also pick a custom date range.
* **Nothing after "Data as of".** The tab shows the GA4 data SEO Utils had when the version was published, and no day after that date.
* **Not live.** The tab is rebuilt with each published version, so with **Publish automatically** on it updates with each tracker run.
* **Owner controls stay hidden.** There is no property switcher, **Sync now** or **Export CSV**.

The tab is left out when **Site traffic (GA4)** is **Off** or the property was removed from SEO Utils.

<details>

<summary>What is not included in a published report</summary>

Some controls need data that is only on your computer. They are hidden in the published copy instead of showing an empty result:

* **All reports:** buttons that run, edit or export the report.
* **GMB Rank Tracker:** the Money Map and demographics layers, annotations on the timeline, and the search box and "view on map" in the Competitors tab. Clicking a grid marker still lists the competitors at that point.
* **Organic Rank Tracker:** the custom date range (the date presets stay), the SERP view of a keyword, the per-keyword insight chart, the SERP features filter of Keyword Fluctuation, key events from Google Analytics, the keyword lists behind the Rankings Distribution counts and the Pages rows, and the search, depth, ignored domains and timeline controls of Competitors Discovery.
* **LLM Rank Tracker:** the custom date range (the date presets stay), the button that shows more keyword mentions, the citation domain search and the competitor filter of the search terms table. The citation URL table shows its first page only.
* **GSC Rank Tracker:** the custom date range (the date presets stay), the Alerts and Before / after tabs, the **This week** card, the Keyword Details panel (keywords show as plain text), the row menu, the Grid view, the member queries of a rule, chart notes, the Google Analytics columns, the page filter on the charts and the Tags filter of the Pages tab.

</details>

## Keeping the Report Up to Date

* **Automatically:** With **Publish automatically** on, each run that finishes, scheduled or started by you, queues a new version. For a GSC Rank Tracker, each refresh that downloads new data does. If a newer run finishes before an older version starts to upload, SEO Utils publishes the newer one, so your client may skip a version.
* **Right now:** Click **"Publish now"** to publish the latest run without waiting for the next one.
* **Usually only changes are uploaded.** Parts of the report that did not change since the last version are normally not uploaded again. A very large report can upload in full.
* **If SEO Utils is closed or offline**, publishing waits and continues the next time SEO Utils runs and is online.

To stop publishing new versions, turn **Publish automatically** off: *"This report will no longer publish automatically."* The version your client has stays online. To publish again, turn the switch back on.

## Unpublishing or Deleting the Published Copy

The buttons at the bottom of the dialog take the report offline:

|                              | **Unpublish**                                                               | **Delete published copy**                                                                                       |
| ---------------------------- | --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| **What your client sees**    | A page saying **This report is not available**\*                            | A page saying **This link is no longer available**                                                              |
| **The published copy**       | Kept, but hidden                                                            | Removed from the cloud                                                                                          |
| **The link**                 | Kept. It works again when you bring the report back.                        | Stops working for good                                                                                          |
| **Publish automatically**    | Turned off                                                                  | Turned off                                                                                                      |
| **To bring it back**         | Click **"Publish now"**. The report is shown again and publishing turns on. | Click **"Publish now"**. The report is published again from the start, at a **new link**. The password is kept. |
| **Your report in SEO Utils** | Not affected                                                                | Not affected                                                                                                    |

\* If the report has a password, a client whose browser has not entered it yet sees **This report is protected** first.

**Delete published copy** asks you to confirm first. If you only want to take the report out of view for now, use **Unpublish**, which keeps the published copy and the link.

After a delete, the old link never works again. When you publish the report again, the **Client link** field shows the new link: send it to your client. If the report had a password, the new link has the same password.

* **It takes effect once confirmed:** SEO Utils sends the request in the background, and your client loses access once the publishing service confirms it. The badge then shows **Hidden** or **Removed**. Keep SEO Utils open and online until then.
* **During an upload:** An Unpublish or Delete stops the upload first, unless the new version is already being made visible. Then it runs right after.
* **While the report is hidden or removed**, the **Publish automatically** switch is off and greyed out. **"Publish now"** is the one way back, and it turns automatic publishing on again.

{% hint style="warning" %}
Deleting a report in SEO Utils also deletes its published copy, in the same way as **Delete published copy**. Your client's link then stops working for good and shows **This link is no longer available**.
{% endhint %}

## See All Your Client Reports

The **Client reports** page lists every link you have shared with clients from the computers on your account, newest first. Sign in at [app.seoutils.app](https://app.seoutils.app) and click **Client reports** under **Remote Access** in the sidebar.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-26ec1eb97be2ddb7b37d58e765f4230dedf48260%2Fclient-reports-page.png?alt=media" alt=""><figcaption><p>The Client reports page: (1) the page in the sidebar, (2) the status filter, (3) the Copy button and (4) Rotate</p></figcaption></figure>

* **Find a report:** Search by report name or paste a link, or filter by computer, status and access. Revoked links stay hidden until you choose **Revoked** or **Live and revoked** in the status filter.
* **Copy:** Copies the client link. If you use [your own domain](#use-your-own-domain-for-client-reports), the link on your domain comes first, with the app.seoutils.app link below it.
* **Rotate:** Gives the same report a new link and stops the old one at once. A password stays on the new link. Send the new link to your client.
* **Revoke:** Stops the link at once for everyone you shared it with. This cannot be undone; to keep sharing the report, rotate the link instead.

## Publishing Status

The badge in the dialog tells you where the report stands:

| Badge                           | What it means                                                                                                             |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Not shared**                  | The report has never been published.                                                                                      |
| **Shared**                      | **Publish automatically** is on, but no version is published yet. It publishes after the next run, or on **Publish now**. |
| **Queued**                      | The publish is waiting to start. The line below the badge says why.                                                       |
| **Publishing**                  | The report is being uploaded. The progress card shows how far it is.                                                      |
| **Published**                   | Clients can open the link.                                                                                                |
| **Unpublishing** / **Removing** | An Unpublish or a Delete is being sent.                                                                                   |
| **Hidden**                      | Unpublished. The link is kept, but clients see a not-available page.                                                      |
| **Removed**                     | The published copy and its link were deleted. **"Publish now"** publishes the report again at a new link.                 |
| **Not published**               | The latest version was stopped or failed. A red message says why and what to do (see below).                              |
| **Setup needed**                | Publishing cannot start on this computer yet. The setup panel says what to do.                                            |
| **Paused**                      | The computer's Agency plan has ended (see [If Your Agency Plan Ends](#if-your-agency-plan-ends)).                         |

In the **Publish to client** menu item, a stopped version shows as **Held** and a failed one as **Failed**.

## Troubleshooting

### In the Publish Dialog

| What you see                                                                                                  | What to do                                                                                                                                                                   |
| ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Setup needed**                                                                                              | Click the button on the setup panel. Publishing continues once the setup is done.                                                                                            |
| **Paused**                                                                                                    | The computer's Agency plan has ended. Click **"Upgrade to Agency"** before the date shown.                                                                                   |
| **Queued** with *"Publishing will start shortly. Reports are published one at a time."* for a long time       | Check that SEO Utils is online. If the report stays queued, contact support with the name of the report.                                                                     |
| *"Waiting for another report to finish publishing."*                                                          | Nothing. Another report is uploading, and this one starts by itself after it. **Publish now** is greyed out until then.                                                      |
| *"Paused briefly — the publishing service asked us to slow down."*                                            | Nothing. The upload continues by itself at the time shown.                                                                                                                   |
| *"Paused — couldn't reach the publishing service."*                                                           | Check the internet connection. The upload retries at the time shown, or click **"Retry now"**.                                                                               |
| *"Publishing could not reach the publishing service."*                                                        | Check the internet connection. SEO Utils tries again by itself, or click **"Publish now"**.                                                                                  |
| *"The latest run of this report could not be published."*                                                     | Click **"Publish now"** to try again. If it keeps failing, contact support.                                                                                                  |
| *"…the person who shared it no longer has permission to publish."*                                            | An owner shares the report again with the **Publish automatically** switch. If you are the owner, first check that the computer is still on the Remote Access + Agency plan. |
| *"…client publishing was not active on this installation's plan at the time."*                                | Once the plan has Agency again, click **"Publish now"**.                                                                                                                     |
| *"…the person who shared it was removed from its workspace."*                                                 | Someone with access to that workspace shares the report again with the **Publish automatically** switch.                                                                     |
| *"This report is no longer shared, so the latest run was not published."*                                     | Click **"Publish now"**.                                                                                                                                                     |
| *"This report was deleted from the shared portal."*                                                           | Make sure the deletion was expected, then click **"Publish now"**.                                                                                                           |
| *"A newer version of this report is already published."* or *"…data no longer matches the published report…"* | Contact support with the name of the report. Re-running the report alone does not publish it again.                                                                          |
| A message ending in *"no action is needed from you."*                                                         | Wait a while. If the message stays, contact support with the name of the report.                                                                                             |
| A message asking you to contact support                                                                       | Contact support with the name of the report.                                                                                                                                 |
| **Status unavailable**                                                                                        | SEO Utils could not read the status. It does not mean the report is unpublished. Click **"Try again"**.                                                                      |
| **The password could not be set**                                                                             | Read the message under it. If it says the publishing service cannot be reached, check the internet connection and try again.                                                 |

### What Your Client Reports

| Your client sees                     | What to do                                                                                                                                                                    |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Map unavailable** in a GMB report  | Add a Browser Maps key and allow the published reports website (see [Google Maps in Published GMB Reports](#google-maps-in-published-gmb-reports)).                           |
| **This report is not available**     | The report is unpublished, or the computer's Agency plan has ended. Click **"Publish now"**, or add Agency back. If every link on your account shows it, check your payments. |
| **This link is no longer available** | The published copy was deleted, and the link stopped working for good. Click **"Publish now"** to publish the report again, then send your client the new link.               |
| **This report is protected**         | The report has a password. Send your client the password.                                                                                                                     |
| **That password is not correct.**    | Check the password with your client, or set a new one.                                                                                                                        |
| **This report could not be opened**  | Ask your client to try again in a moment.                                                                                                                                     |

{% hint style="info" %}
Still stuck? Post in the [SEO Utils Facebook group](https://www.facebook.com/groups/seoutils).
{% endhint %}

## Plans and Storage

Publishing reports to clients is part of the **Remote Access + Agency** plan (see [Plans and Pricing](/guide/remote-access#plans-and-pricing)).

* The plan includes **1 GB** of storage for published reports on that computer.
* Storage above that is billed at **$0.50 per GB per month**, separately from the plan.
* A part of a report that does not change between versions is stored once, so unchanged parts do not use storage twice.
* When a newer version replaces an older one, the older version is cleared automatically about a day later.
* **Delete published copy** frees the storage of that report. **Unpublish** keeps it, so you can show the report again.
* If a storage payment stays unpaid, every published report on your cloud account shows the not-available page until the payment is made.

{% hint style="info" %}
Looking for share.seoutils.app or the **Share (Legacy)** action? That older sharing system is retired, and **Publish to client** replaces it.
{% endhint %}

## If Your Agency Plan Ends

When a computer's plan no longer has Agency (you switch plans, cancel, or a payment stays unpaid after the grace period):

* Its client links show **This report is not available**, and the dialog in SEO Utils shows **Paused** with a deadline.
* The published copies are kept for **30 days**. Add Agency back in that time and the reports come back at the same links.
* After 30 days they are deleted. Publishing again gives the report a new link.

The **Remote Access** page warns you how many client reports are affected before you downgrade or cancel. Unpairing the computer or turning Remote Access off does not end Agency.

## Frequently Asked Questions

<details>

<summary>Does my computer need to be on for my client to view the report?</summary>

No. Your client opens the published copy, which is stored in the cloud.

Your computer only needs to be on, with SEO Utils open and online, to publish a new version.

</details>

<details>

<summary>Can my client change the report?</summary>

No. The published report is read-only. Your client can switch tabs, date presets and filters, but cannot run, edit or export it, and cannot see your other reports.

</details>

<details>

<summary>How often does the published report update?</summary>

* With **Publish automatically** on, after the report's runs finish, on its schedule or when you start them.
* Any time you click **"Publish now"**.

</details>

<details>

<summary>Does publishing cost extra?</summary>

Publishing is included in the **Remote Access + Agency** plan, with 1 GB of storage for published reports. Storage above 1 GB is billed at $0.50 per GB per month. See [Plans and Storage](#plans-and-storage).

</details>

<details>

<summary>Does the published report show my brand?</summary>

No. The published report shows the report only. It shows no logo, no SEO Utils account name and no computer name. To show it on your own address, see [Use Your Own Domain for Client Reports](#use-your-own-domain-for-client-reports).

</details>

<details>

<summary>What happens to published reports if I unpair my computer?</summary>

They stay available at their links, and their storage keeps counting toward your plan. To publish new versions, pair the computer again (see [Remote Access](/guide/remote-access)).

</details>

## Related Guides

{% content-ref url="/pages/5g6NABzsFmX50yVSKbWU" %}
[Remote Access](/guide/remote-access)
{% endcontent-ref %}

{% content-ref url="/pages/SFqUeDLssiMWvquyuPek" %}
[Google My Business Rank Tracker](/guide/google-my-business-rank-tracker)
{% endcontent-ref %}

{% content-ref url="/pages/VyqVBrCDPTnO3JOSPtfo" %}
[Organic Rank Tracker](/guide/organic-rank-tracker)
{% endcontent-ref %}

{% content-ref url="/pages/pu5oCuuOTZif3zBLaN45" %}
[LLM Rank Tracker](/guide/llm-rank-tracker)
{% endcontent-ref %}

{% content-ref url="/pages/Vp6S5COczg6spqmdaBNZ" %}
[GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker)
{% endcontent-ref %}


# Embedding Database

The **Embedding Database** feature lets you convert text into mathematical representations (embeddings) that capture semantic meaning. SEO Utils uses these embeddings to find similar content, group related topics, and perform intelligent analysis—even when the exact words don't match.

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ce5e8f5e9fd77a7243798acf3c6b20766f9d3c88%2FXnapper-2025-08-27-21.47.02.png?alt=media" alt=""><figcaption><p>Embedding Settings</p></figcaption></figure></div>

With embeddings, you can discover that "best coffee shops NYC" and "top cafes in New York" are semantically similar, enabling smarter content grouping and analysis.

### Why Use Embeddings?

Traditional keyword matching only finds exact or partial text matches. Embeddings understand **meaning**, allowing SEO Utils to:

* Group semantically related search queries
* Find content gaps and opportunities
* Build topical clusters based on actual intent
* Analyze content relationships beyond keywords

### Supported Providers & Models

SEO Utils supports both **paid cloud models** and **free local models**, giving you flexibility based on your needs and budget.

**Cloud Models (OpenAI)**

* [**Text Embedding 3 Small**](https://platform.openai.com/docs/models/text-embedding-3-small)**:** Multilingual, highly efficient, 5x cheaper than ada-002. 1536 dimensions, 8191 max tokens ($0.02 per 1M tokens)
* [**Text Embedding 3 Large**](https://platform.openai.com/docs/models/text-embedding-3-large)**:** Multilingual, best accuracy, 54.9% MIRACL score. 3072 dimensions, 8191 max tokens ($0.13 per 1M tokens)

**Local Models (Ollama - Free)**

* [**Nomic Embed Text v1.5**](https://ollama.com/library/nomic-embed-text)**:** English-focused, surpasses OpenAI ada-002 & text-embedding-3-small, local & free. 768 dimensions, 8192 max tokens
* [**Nomic Embed Text v2 MoE (Q6\_K)**](https://ollama.com/toshk0/nomic-embed-text-v2-moe)**:** Multilingual (\~100 languages), MoE architecture, 65.8 MIRACL score, local & free. 768 dimensions, 512 max tokens
* [**Snowflake Arctic Embed v1**](https://ollama.com/library/snowflake-arctic-embed)**:** English-only, 334M BERT, optimized for retrieval, local & free. 1024 dimensions, 512 max tokens
* [**Snowflake Arctic Embed v2**](https://ollama.com/library/snowflake-arctic-embed2)**:** Multilingual, 567M BERT, beats text-embedding-3-large on MTEB, MRL compression, local & free. 1024 dimensions, 8192 max tokens
* [**mxbai-embed-large**](https://ollama.com/library/mxbai-embed-large)**:** English-only, 334M BERT, SOTA for its size, beats text-embedding-3-large, local & free. 1024 dimensions, 512 max tokens
* [**BGE-M3 (BAAI)**](https://ollama.com/library/bge-m3)**:** Multilingual (100+ languages), 567M XLM-RoBERTa, dense+sparse+colbert retrieval, local & free. 1024 dimensions, 8192 max tokens

{% hint style="success" %}
**Understanding Dimensions**

Embedding dimensions represent the size of the vector that stores semantic information. Think of it like image resolution—higher dimensions can capture more detail, but with tradeoffs:

* **768 dimensions**: Fast and efficient, perfect for most keyword clustering and query grouping
* **1024 dimensions**: Balanced performance, better for multilingual content and complex queries
* **1536-3072 dimensions**: Maximum semantic detail, but requires more storage and slower searches

For most SEO tasks, 768-1024 dimensions provide excellent results. Higher dimensions are only needed for highly nuanced semantic analysis or when working with very similar content that requires fine-grained distinctions.
{% endhint %}

{% hint style="info" %}
Local models run entirely on your computer—no API costs, no data sent to external servers. Perfect for privacy-conscious users or those processing large volumes of data.
{% endhint %}

### Enable Embedding Database

To start using embeddings, head to the left sidebar and click on "**Settings**," then navigate to "**Embedding**".

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fdd302369aab73f9d6721f5dab277667244be581%2FXnapper-2025-08-27-21.48.31.png?alt=media" alt=""><figcaption><p>Access Embedding Settings</p></figcaption></figure>

Next, toggle the "**Enable Embeddings**" master switch to activate the embedding system.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-377f78a2675d15b886abdfacb08885de75f43c5b%2FXnapper-2025-08-27-21.47.02.png?alt=media" alt=""><figcaption><p>Enable the embedding database</p></figcaption></figure>

Once enabled, you'll see available features that can use embeddings. Each feature can use a different model based on your requirements.

#### For Cloud Models (OpenAI)

1. Ensure you have your OpenAI API key configured in the Services page

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-848fa9f53428a0dd176b97f7bcbbe34dd7e873c7%2FXnapper-2025-08-27-22.00.12.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

2. Select "OpenAI" as the provider
3. Choose your preferred model (Text Embedding 3 Small recommended for most use cases)

#### For Local Models (Ollama)

1. Install Ollama on your computer from [ollama.com](https://ollama.com)
2. Open Terminal and pull the model you want to use:

   ```bash
   ollama pull nomic-embed-text
   ```

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-83ee9738e51df5ada41a1f232886b6319fb7fb85%2FXnapper-2025-08-27-22.02.23.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

3. Ensure Ollama is running (it runs in the background by default)
4. Select "Ollama" as the provider
5. Choose from installed models (unavailable models will be disabled)

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fd79feebf715d6e7fff505a702cc0fc36070ab6d%2FXnapper-2025-08-27-21.50.12.png?alt=media" alt=""><figcaption><p>Choose embedding model for each feature</p></figcaption></figure>

### How Embeddings Are Stored

SEO Utils stores all generated embeddings in your local database. Once content is embedded, it won't be re-embedded again—saving API costs, processing time, and computational resources. This means you can experiment with different similarity thresholds and search queries without regenerating embeddings each time.

### Understanding Similarity Scores

When using semantic search in most of the semantic tools, you'll work with **similarity score thresholds** that control how closely items must match:

* **Score range**: -1 to 1 (where 1 = identical meaning, 0 = unrelated, -1 = opposite meaning)
* **Finding the right threshold**: Each model and dataset combination requires different thresholds
* **Ollama models**: Typically need 0.8–0.9 for good matches with SEO data
* **OpenAI models**: Often work well with 0.7–0.9 (higher dimensions allow slightly lower thresholds)
* **Fine-tuning tip**: Use precise decimals (0.810, 0.825, 0.835) to find the sweet spot for your specific data

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-902f695373e2e1a63a2992822dd6cc0f965bb6af%2FXnapper-2025-08-27-22.04.18.png?alt=media" alt=""><figcaption><p>Similarity threshold is used in the Topic Cluster tool of the Google Search Console Queries.</p></figcaption></figure>

### Available Features

Currently, SEO Utils uses embeddings for:

#### **1. Google Search Console Queries -** [**Topic Clusters**](/guide/google-search-console/topic-clusters)**:**

Generate embeddings for your search queries to enable semantic clustering. Group related queries by topic to analyze their collective performance.

#### **2. Internal Links Pages -** [**Internal Links**](/guide/google-search-console/internal-links)**:**

Generate embeddings for your crawled pages so the tool can tell which pages cover the same topic, then propose a sentence on each related page to add a link from.

{% hint style="info" %}
The two features are **independent**. Each picks its own model, and they never share vectors — so changing the model for one leaves the other's embeddings untouched.
{% endhint %}

{% hint style="success" %}
**Coming Soon**

* Topical Map Builder
* Semantic Clustering v3
  {% endhint %}

### How to Choose the Right Model

#### **By Budget & Privacy:**

* **Zero cost + Maximum privacy:** Use Ollama models (all processing stays on your computer)
* **Pay-as-you-go + Fast processing**: Use OpenAI models (data sent to OpenAI servers)
* **Large volume processing**: Local models save money long-term despite slower speed

#### **By Language Requirements:**

* **English-only content**: Nomic Embed Text v1.5 (768D) or mxbai-embed-large (1024D)
* **Multilingual content**: BGE-M3 or Snowflake Arctic Embed v2 (both support 100+ languages)
* **Mixed content**: Text Embedding 3 Small offers good multilingual support with cloud speed

#### **By Computer Specs:**

* **Limited RAM (8GB)**: Use cloud models or stick to smaller embedding models (768D requires \~150MB per model)
* **Standard specs (16GB RAM)**: Can run all embedding models comfortably (1024D models need \~400MB)
* **Power users (32GB+ RAM)**: Run multiple models simultaneously or process large batches locally
* **Apple Silicon (M1/M2/M3/M4)**: 3-5x faster than CPU-only, with M3/M4 delivering best performance for local models

#### **By Use Case Complexity:**

* **Basic keyword clustering**: 768D models (Nomic Embed Text) are sufficient
* **Topic clustering & semantic search**: 1024D models provide better accuracy
* **Fine-grained content analysis**: Consider 1536D+ models for nuanced distinctions
* **Large query volumes (10,000+)**: Prioritize speed—use cloud models or accept longer processing

#### **Quick Recommendations:**

* **Most users**: Start with Nomic Embed Text (free, fast, good quality)
* **Agencies with client data**: Use local models for privacy compliance
* **High-volume operations**: OpenAI Text Embedding 3 Small balances cost and speed
* **Maximum accuracy needed**: Text Embedding 3 Large or BGE-M3


# Automations

### How Does the Automations Tool Work?

SEO Utils allows you to automate actions when rank tracking completes. When an Organic Rank Tracker or Google Business Rank Tracker snapshot finishes, you can automatically export PDFs, send emails to clients, or trigger webhook URLs.

A PDF created by an automation holds the same sections as one you export yourself, including [Site traffic (GA4)](/guide/organic-rank-tracker#show-site-traffic-in-the-report) when the report has a GA4 property chosen.

The automation system processes actions sequentially. If one action fails, subsequent actions that don't depend on its output will still run. Only actions requiring output from failed actions will be skipped.

### How to Create an Automation

To get started, head to Automations in the left sidebar. Then, click the Create Automation button.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-e4a6382c006c3d4cc1ab0e664862ce22499ca4f8%2FXnapper-2025-09-18-10.53.03.png?alt=media" alt=""><figcaption><p>Access the Automations tool in the left sidebar</p></figcaption></figure>

The automation form has three steps:

#### Step 1: Basic Information

* **Name**: Give your automation a descriptive name like "Send GMB Report to Client"
* **Description**: Optional notes about what this automation does
* **Active Status**: Toggle whether the automation should run

#### Step 2: Configure Trigger

Select when the automation should run:

* **Trigger Type**: Choose between Organic Rank Tracker or GMB Rank Tracker completion, or GSC Rank Tracker Alerts (see [GSC Rank Tracker alerts](/guide/google-search-console/gsc-rank-tracker/alerts#send-alerts-by-email-or-webhook))
* **Run On**: Select "All Reports" or choose specific reports
* **Run Once**: Enable this to run the automation only once per report, preventing duplicate actions like sending multiple emails when re-running the tracker

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-80da7af0eb1056d5b88da96b47555af3a47da32d%2FXnapper-2025-09-18-10.53.52.png?alt=media" alt=""><figcaption><p>Configure the trigger</p></figcaption></figure>

#### Step 3: Define Actions

Add one or more actions that execute in sequence. Each action type has specific configuration options.

### Using Variables in Actions

Variables allow you to use dynamic data from your rank tracking reports. Variables are wrapped in double curly braces `{{variable_name}}`.

Click the **Variables** button in any text field to search and insert variables quickly. You can search by typing keywords like "action 1" or "email" to find relevant variables.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-af20336ebf5f4dc588810c72a7dd6006261277b7%2FXnapper-2025-09-18-10.54.50.png?alt=media" alt=""><figcaption><p>Use Varaibles Selector button to quickly find and insert variables</p></figcaption></figure>

**GMB Rank Tracker Trigger Variables:**

* `{{trigger.reportID}}` - ID of the GMB rank tracker report
* `{{trigger.reportType}}` - Type of report (google-business-rank-tracker)
* `{{trigger.fromDate}}` - Date of the comparison snapshot (based on automation's comparison days setting)
* `{{trigger.toDate}}` - Date of the current snapshot that triggered this automation
* `{{trigger.ranOn}}` - Date when the snapshot was created
* `{{trigger.snapshotID}}` - ID of the current snapshot
* `{{trigger.businessName}}` - Business name being tracked
* `{{trigger.address}}` - Business address
* `{{trigger.comparisonDays}}` - Number of days between snapshots

### GSC Rank Tracker Alerts Trigger

This trigger runs once each time a refresh of a [GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker) finds new alerts. Its actions are **Export PDF**, **Send Email** and **Webhook**. The setup is in [Alerts](/guide/google-search-console/gsc-rank-tracker/alerts#send-alerts-by-email-or-webhook), and **Export PDF** creates the tracker's [report](/guide/google-search-console/gsc-rank-tracker/print-and-pdf).

**Main trigger variables:**

* `{{trigger.trackerName}}` - Name of the tracker
* `{{trigger.alertsCount}}`, `{{trigger.alertsSummary}}`, `{{trigger.alertsList}}` - How many alerts, in a few words, and one line each
* `{{trigger.fromDate}}` and `{{trigger.toDate}}` - The first and last day an alert was confirmed on
* `{{trigger.reportFrom}}` and `{{trigger.reportTo}}` - The report period: the 30 days ending on the tracker's latest final day. The Export PDF action covers it
* `{{trigger.aiSummaryText}}` - This week's AI summary as one paragraph, empty when the weekly summary is off or not written yet. It says "written by AI" and names the model, unless the tracker's [AI label](/guide/google-search-console/gsc-rank-tracker/ai#hide-the-ai-label-for-clients) is switched off

The full list is in [Alerts](/guide/google-search-console/gsc-rank-tracker/alerts#send-alerts-by-email-or-webhook). To email the PDF with the summary, add **Export PDF**, then **Send Email** with the file attached and a body such as:

```
Hi,

Here is the rank report for {{trigger.trackerName}}, from {{trigger.reportFrom}} to {{trigger.reportTo}}.

{{trigger.aiSummaryText}}
```

### Example: GMB Report Email Automation

Here's a practical template for automatically sending GMB ranking reports to clients:

#### Action 1: Export PDF

* **Action Type**: Export PDF
* **Export Folder**: `/Users/yourname/Downloads` (or your preferred folder)

**Output Variables** (automatically available for next actions):

* `exportDate` - Date when the file was exported
* `exportTime` - Full timestamp of export
* `fileName` - Name of the PDF file
* `filePath` - Full path to the exported PDF file
* `fileSize` - Size of the file in bytes

#### Action 2: Send Email

* **Action Type**: Send Email
* **SMTP Credential**: Select your configured credential or leave empty for default
* **Recipients**: `client@example.com`
* **CC Recipients**: *(optional)*
* **Email Subject**: `GMB Rankings Report - {{trigger.businessName}} - {{trigger.ranOn}}`
* **Email Body**:

```
Hi,

Your Google Business ranking report for {{trigger.businessName}} is ready.

Comparison Period: {{trigger.fromDate}} to {{trigger.toDate}}
Location: {{trigger.address}}

The detailed report is attached to this email.

Best regards,
Your SEO Team
```

* **Attachments**: Use the Variables button to insert the file path from Action 1. It will look like: `{{action.act_[actionId].filePath}}`

{% hint style="info" %}
**Tip**: The action ID (like `act_1757983518769_inus10vs5`) is automatically generated when you create the action. Use the Variables button to easily insert the correct reference without typing it manually.
{% endhint %}

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6dbc4b023cf70a55268541480a4deabd71293598%2FXnapper-2025-09-18-21.55.43.png?alt=media" alt=""><figcaption><p>Configure multiple actions to run in sequence</p></figcaption></figure>

{% hint style="info" %}
**Important**: To send emails, you must first configure SMTP credentials. See [SMTP Credentials](/guide/smtp-credentials) Setup for instructions.
{% endhint %}

### Monitoring Automation History

The Automation detail page shows comprehensive execution history:

#### Execution Statistics

* **Total Runs**: How many times the automation has triggered
* **Successful/Failed/Partial**: Breakdown of execution results

#### Execution History Tab

View each automation run with:

* **Status**: Completed, Failed, or Partial (some actions failed)
* **Duration**: How long the automation took
* **Actions**: Number of actions executed
* **Trigger Data**: The snapshot or report that triggered it

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-b767e7a53a862646c1d0fdd81836070818772369%2FXnapper-2025-09-18-21.56.23.png?alt=media" alt=""><figcaption><p>Monitor automation execution history and retry failed actions</p></figcaption></figure>

### Retrying Failed Automations

When an automation fails or partially completes, you have two retry options:

1. Click the **vertical three dots** next to the execution
2. Choose your retry method:
   * **Retry All Actions**: Runs the entire automation from the beginning
   * **Retry Failed & Cancelled Actions**: Only retries actions that failed or were cancelled
3. The system will:
   * For "Retry All": Execute all actions from the start
   * For "Retry Failed & Cancelled": Skip completed actions and only retry failed/cancelled ones
   * Use the **original trigger data** (not current automation settings)

### Execution & Action Status Types

#### Automation Execution Status

* **Running**: Automation is currently executing
* **Success**: All actions completed successfully
* **Failed**: All actions failed
* **Partial**: Some actions succeeded, others failed or cancelled

#### Individual Action Status

* **Running**: Action is currently executing
* **Completed**: Action executed successfully
* **Failed**: Action encountered an error
* **Cancelled**: Action was stopped before completion


# MCP Server (AI Integration)

The MCP Server lets you connect AI assistants like Claude, ChatGPT, Codex, Cursor, or any MCP-compatible client to your SEO data. Ask questions in plain English and get instant answers — no need to navigate dashboards or export reports manually.

<div data-full-width="true"><figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FRf4Cj5GRET4ouj1V5xDv%2FXnapper-2026-03-19-21.42.45.png?alt=media&amp;token=f20fe4f9-cffd-40f5-bf56-dd8ef24b189a" alt=""><figcaption><p>Claude using SEO Utils to build an area demographics dashboard</p></figcaption></figure></div>

{% hint style="info" %}
MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external data sources. SEO Utils runs an MCP server locally on your machine — your data never leaves your computer.
{% endhint %}

### Example Reports Generated by MCP

These reports were generated entirely by the MCP Server — one prompt, zero manual work:

* [**Laravel.com Complete SEO & Backlink Report**](https://app.seoutils.app/laravel-complete-seo-report) — Traffic analytics, keyword rankings, backlink profile, competitor analysis, and trend charts in one interactive dashboard.
* [**SEO Health Report for tuikhoeconban.com**](https://app.seoutils.app/seo-health-report-tuikhoeconban) — Google Search Console audit with CTR opportunities, keyword cannibalization, zero-click queries, and prioritized recommendations.

## What Can You Do With It?

| Use Case                         | Example Prompt                                                                                                                                                                     |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Generate reports**             | "Generate a weekly SEO report for example.com"                                                                                                                                     |
| **Find weak pages**              | "Find pages with high impressions but low CTR"                                                                                                                                     |
| **Keyword cannibalization**      | "Which keywords have multiple pages competing?"                                                                                                                                    |
| **Ranking trends**               | "Show me my biggest ranking winners and losers this month"                                                                                                                         |
| **Rank tracker questions**       | "Which keywords moved the most in my GSC rank tracker this week, and why?" ([more prompts](#try-these-prompts-with-the-gsc-rank-tracker))                                          |
| **Ranked-page changes**          | "Compare the captured HTML before and after this page was lost, and tell me which changes may have contributed"                                                                    |
| **Content gaps**                 | "Find queries I'm ranking for but don't have dedicated pages"                                                                                                                      |
| **Local SEO**                    | "Generate a local SEO report for my business"                                                                                                                                      |
| **Multi-location analytics**     | "Compare my Haidilao hot pot rankings across all locations"                                                                                                                        |
| **Client reports**               | "Create a professional client-ready report for example.com"                                                                                                                        |
| **Keyword research**             | "Check keyword metrics for: seo tools, rank tracker"                                                                                                                               |
| **SERP analysis**                | "What's ranking for 'seo tools' in Google?"                                                                                                                                        |
| **Backlink analysis**            | "Show me the backlinks for example.com"                                                                                                                                            |
| **Content gap**                  | "Find keywords competitors rank for but I don't"                                                                                                                                   |
| **Backlink gap**                 | "Find sites linking to competitors but not me"                                                                                                                                     |
| **Traffic analytics**            | "Show me the traffic overview for laravel.com"                                                                                                                                     |
| **Organic keywords**             | "What keywords does laravel.com rank for?"                                                                                                                                         |
| **Demographics**                 | "Show me population and income data around my business"                                                                                                                            |
| **Bulk analysis**                | "Compare organic traffic for laravel.com, symfony.com, and codeigniter.com"                                                                                                        |
| **NAP Finder**                   | "Which domains have the most NAP citations for my business?"                                                                                                                       |
| **Keyword explorer**             | "What are the keyword suggestions for 'keto diet' in the US?"                                                                                                                      |
| **Saved keywords**               | "Create a keyword list called 'Competitors' and add: seo tools, rank tracker"                                                                                                      |
| **Grow rank tracker**            | "Add the top 20 content-gap keywords from my competitor into my example.com rank tracker"                                                                                          |
| **Clean up rank tracker**        | "Remove these irrelevant keywords from my example.com rank tracker: foo, bar, baz"                                                                                                 |
| **Weight rank tracker keywords** | "In my example.com rank tracker, make 'buy seo tools' count three times and set 'seo tools login' to Track only"                                                                   |
| **Automations**                  | "Create an automation that exports PDF when my rank tracker finishes"                                                                                                              |
| **Indexing health**              | "How many of my pages are indexed? Which directories have the worst indexing rate?"                                                                                                |
| **Indexing diagnostics**         | "Find pages with zero internal links that aren't indexed — orphan pages"                                                                                                           |
| **Internal link analysis**       | "Which pages have the most internal links pointing to them?"                                                                                                                       |
| **Find internal links**          | "Find internal links for my five best priority pages on example.com — quote the cost first"                                                                                        |
| **AI log analysis**              | "Which AI bots are violating my robots.txt? What questions is Perplexity asking about my site?"                                                                                    |
| **Keyword insights**             | "Which keywords are trending up in my rank tracker?"                                                                                                                               |
| **GA4 conversions**              | "Which pages generate the most conversions from organic search?"                                                                                                                   |
| **GA4 traffic**                  | "How did organic search compare with paid and direct traffic last month?"                                                                                                          |
| **Custom queries**               | "How many keywords am I tracking across all reports?"                                                                                                                              |
| **Manage workspaces**            | "Create a new workspace called Client A" or "In the Client A workspace, create a rank tracker for clienta.com"                                                                     |
| **SEO Tests**                    | "Create a split test on example.com comparing /pricing vs /pricing-v2 — 50/50 traffic, hypothesis is the new layout will lift CTR"                                                 |
| **Local rank tracking**          | "Create a GMB rank tracker for Haidilao Hot Pot in Bellevue, WA — 5x5 grid at 500m radius, tracking 'hot pot bellevue' and 'best chinese bellevue', weekly on Mondays 9am Pacific" |
| **LLM rank tracking**            | "Create an LLM rank tracker for my brand Acme (variants: Acme, Acme Inc) tracking 'best crm software' and 'top crm tools' in ChatGPT and Google AI Overview, weekly"               |
| **AI Visibility**                | "In my Ahrefs exploration, what is my share of voice in AI answers, and in which prompts do Semrush and Moz win instead of me?"                                                    |
| **Review monitoring**            | "Start tracking the Google reviews for Haidilao Hot Pot Bellevue — pull the 200 most recent reviews and tell me which ones have no owner response"                                 |
| **Citation discovery**           | "Run a NAP Finder for Monsoon Seattle at 615 19th Avenue East, phone (206) 325-2111, then show me which directories cite the business"                                             |
| **Content briefs**               | "Create a content struct for 'keto meal plan', wait for the analysis, then generate an AI outline with GPT and write an article draft from it"                                     |
| **Keyword clustering**           | "Cluster these 50 keto keywords by SERP similarity and tell me how many pages I need to cover them — use the DataForSEO SERP API"                                                  |
| **Entity analysis**              | "Run an NLP analysis on my keto guide and my competitor's page with TextRazor — which entities do they cover that I don't?"                                                        |

The MCP server gives the AI read-only access to your database, can fetch live data from external APIs (keyword metrics, SERP results, backlinks), and can manage your saved keyword lists.

## Requirements

* A valid SEO Utils license key
* MCP Access (one-time purchase) to let AI apps run every tool

{% hint style="info" %}
**No MCP Access yet?** With an active license, an AI app can still connect and [set up SEO Utils for you](/guide/set-up-seo-utils): connecting and the setup actions work without the add-on. Every other action answers that it needs MCP Access. The Dashboard's **AI assistant** card shows which level you have: **Setup only** or **Full access**.
{% endhint %}

## Setting Up the MCP Server

{% stepper %}
{% step %}
**Purchase MCP Access**

Go to **Settings → Services** and scroll down to the **MCP Server (AI Integration)** section. Click **"Purchase MCP Access"** to complete the one-time purchase via Stripe. You can connect an app before you buy: without MCP Access it can only help you set up SEO Utils.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F56vFkvWBODYSBbc6P9Dh%2FXnapper-2026-03-21-15.13.49.png?alt=media&amp;token=4faf10c9-ba94-4b75-bbbc-7dcb850bcc1a" alt=""><figcaption><p>Purchase MCP Access button in Settings</p></figcaption></figure>

Alternatively, you can purchase MCP access directly from your browser at [app.seoutils.app/mcp/purchase](https://app.seoutils.app/mcp/purchase) — enter your license key and complete the checkout.

{% hint style="info" %}
MCP access is a one-time purchase with unlimited updates — no subscription. It's tied to your license key, works on all devices associated with your license, and cannot be transferred. An active (non-expired) SEO Utils license is required.
{% endhint %}
{% endstep %}

{% step %}
**Refresh Purchase Status**

After completing your purchase, go back to **Settings → MCP Server** and click the **"Refresh"** button to verify your purchase. This confirms your MCP access is active.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FO8DgaJGyC2rh4jgDor7u%2FXnapper-2026-03-21-15.15.35.png?alt=media&amp;token=43b5d43f-5efd-4698-b690-f9cec4c6c9b6" alt=""><figcaption><p>Click Refresh to verify your purchase</p></figcaption></figure>
{% endstep %}

{% step %}
**Check the MCP Server**

Connecting an app (next step) turns the server on for you. You can also toggle **"Enable MCP Server"** yourself. The status shows **Running (port 19515)** while it runs.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FIKIQ715z5A66FAXlLmy4%2FXnapper-2026-09-28-18.16.04.png?alt=media&amp;token=ead4bb9c-32a6-475b-ae06-edc32ff256b6" alt=""><figcaption><p>MCP Server running, with the Connect an AI app picker below</p></figcaption></figure>
{% endstep %}

{% step %}
**Connect your AI app**

Under **Connect an AI app**, pick your app and click its **Connect** button, described below.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-80ef6e2dd02f6b38bdd49edae72c722b846f426c%2Fmcp-connect-claude-code.png?alt=media" alt=""><figcaption><p>Connect an AI app: the app picker (1) and the Connect button (2)</p></figcaption></figure>

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FZupRvmROMYFOUrOl89WP%2FXnapper-2026-09-28-18.13.49.png?alt=media&amp;token=cf35fe36-d108-49df-a636-ed9d452588be" alt=""><figcaption><p>Connect an AI app with Claude Desktop &#x26; Cowork selected</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Connecting to AI Assistants

In SEO Utils, go to **Settings → Services → MCP Server (AI Integration)** and use **Connect an AI app**: pick your app. For Claude Desktop, Claude Code, Codex, Cursor, VS Code and OpenCode, one **Connect** button does it all:

1. Turns on the MCP server
2. Adds SEO Utils to the app
3. Installs the [SEO Utils skill](#install-the-seo-utils-skill-recommended) where the app reads one

Then restart the app the way the page says. The other apps keep their copyable commands and configs; every command has its own **Copy** button, already filled in with the location of SEO Utils on your computer.

You can also let your AI app do the rest: [Set Up SEO Utils](/guide/set-up-seo-utils) connects it and walks you through every tool's setup.

{% hint style="success" %}
**Using Claude on the web, ChatGPT, Perplexity, Grok or the Gemini app, or an app on another computer?** Connect it from anywhere through Remote Access, with no public address or token to set up: see [Connect AI Apps From Anywhere](/guide/mcp-server/connect-ai-apps-from-anywhere).
{% endhint %}

| App                                              | How it connects                                                                  | Requires Node.js? | Requires public URL?                              |
| ------------------------------------------------ | -------------------------------------------------------------------------------- | ----------------- | ------------------------------------------------- |
| **Claude Desktop & Cowork**                      | One click: **Connect Claude Desktop**                                            | No                | No                                                |
| **Claude Code**                                  | One click: **Connect Claude Code**                                               | No                | No                                                |
| **OpenAI Codex** (ChatGPT desktop app, CLI, IDE) | One click: **Connect Codex**                                                     | No                | No                                                |
| **OpenCode** (CLI, desktop app, IDE)             | One click: **Connect OpenCode**                                                  | No                | No                                                |
| **Cursor**                                       | One click: **Connect Cursor**                                                    | No                | No                                                |
| **VS Code** (GitHub Copilot)                     | One click: **Connect VS Code**                                                   | No                | No                                                |
| **OpenClaw**                                     | One command                                                                      | No                | No                                                |
| **Grok Build** (CLI coding agent)                | One command                                                                      | No                | No                                                |
| **Google Antigravity**                           | Paste a config                                                                   | No                | No                                                |
| **Perplexity (Mac)**                             | Paste a command                                                                  | No                | No                                                |
| **ChatGPT desktop app**                          | One click: **Connect Codex** (shared MCP servers)                                | No                | No                                                |
| **n8n / Make**                                   | HTTP with the auth token                                                         | No                | Yes (HTTPS), unless n8n runs on the same computer |
| **Claude Web (claude.ai)**                       | [From anywhere (Remote Access)](/guide/mcp-server/connect-ai-apps-from-anywhere) | No                | No (your Remote Access address)                   |
| **ChatGPT (web), Grok (grok.com)**               | [From anywhere (Remote Access)](/guide/mcp-server/connect-ai-apps-from-anywhere) | No                | No (your Remote Access address)                   |

{% hint style="info" %}
**How the local apps connect.** Every app down to Perplexity starts SEO Utils itself as its MCP server (the SEO Utils program with `mcp-stdio`). That needs no Node.js and puts no auth token in the app's config, so [rotating the token](#rotating-the-auth-token) doesn't break it. The app can also start before SEO Utils: if SEO Utils isn't open, the AI is told to open it, and it works as soon as SEO Utils is running.
{% endhint %}

{% hint style="warning" %}
**Connected with SEO Utils 2.5.0 or earlier?** Those connections use `mcp-remote` (Node.js) or a URL with your token. They keep working, but pick your app in **Connect an AI app** and click **Connect** again to switch to the new connection.
{% endhint %}

<details>

<summary>Claude Desktop &#x26; Cowork</summary>

1. In **Connect an AI app**, choose **Claude Desktop & Cowork**
2. Click **"Connect Claude Desktop"**
3. **Restart Claude Desktop** to apply changes: quit it from the menu bar (closing its window is not enough), then open it again. On Windows, fully quit it first (tray icon or Task Manager)

You'll see SEO Utils under **Settings → Developer** in Claude Desktop, with whether it is running. It works in Cowork on this computer too. Connect doesn't add the skill for Claude Desktop's chat: add it as a plugin (see [Install the SEO Utils Skill](#install-the-seo-utils-skill-recommended)).

{% hint style="info" %}
Claude Desktop can start before SEO Utils. Open SEO Utils whenever you want to use it; there's no need to restart Claude Desktop.
{% endhint %}

</details>

<details>

<summary>Claude Code</summary>

1. In **Connect an AI app**, choose **Claude Code**
2. Click **"Connect Claude Code"**. SEO Utils is added for all your projects, and the skill is saved in Claude Code's skills folder
3. Start a new Claude Code session: run `claude` in any folder

**Prefer the terminal?** Copy the command shown under the button and run it. On a Mac it looks like this:

```bash
claude mcp add --scope user seo-utils -- '/Applications/SEO Utils.app/Contents/MacOS/SEO Utils' mcp-stdio
```

{% hint style="warning" %}
**Added the SEO Utils plugin to Claude Code before?** Claude Code no longer uses the plugin marketplace: Connect saves the skill in Claude Code's skills folder instead. If the old plugin is still installed, Connect shows a command to remove it. Run it in Claude Code so it doesn't load two copies: `/plugin uninstall seo-utils@seo-utils`

Claude Code also loads the plugins turned on in your claude.ai account when you sign in with it. If you added the SEO Utils plugin on claude.ai for Claude Desktop or Cowork, Claude Code gets that copy too, beside the one Connect saves. To keep one copy, turn the plugin off for Claude Code only (Claude keeps it) by running this in a terminal: `claude plugin disable seo-utils@synced`
{% endhint %}

{% hint style="warning" %}
**Added SEO Utils by URL before** (`claude mcp add --transport http seo-utils …`)? That entry belongs to the project folder you ran it in and takes priority there. Remove it in that folder with `claude mcp remove seo-utils --scope local`, so the tools don't show up twice.
{% endhint %}

</details>

<details>

<summary>OpenAI Codex (ChatGPT Desktop App, CLI &#x26; IDE Extension)</summary>

The ChatGPT desktop app (Codex), the Codex CLI and the IDE extension share one config file: `~/.codex/config.toml` (Windows: `%USERPROFILE%\.codex\config.toml`).

1. In **Connect an AI app**, choose **OpenAI Codex**
2. Click **"Connect Codex"**. Only the SEO Utils entry in `config.toml` changes; your other settings and comments are kept. The entry lets SEO Utils tools run for up to 15 minutes. Without it, Codex stops any tool after 60 seconds
3. In the app, open the MCP settings and select **Restart**. In the CLI, start a new session; in the IDE extension, restart the extension

**Added SEO Utils to Codex with an earlier version?** Click **"Connect Codex"** again to get the 15-minute timeout.

**Prefer the terminal?** Copy the `codex mcp add seo-utils -- … mcp-stdio` command shown under the button and run it. The command can't set the timeout, so then open `config.toml` and add this line under `[mcp_servers.seo-utils]`:

```toml
tool_timeout_sec = 900
```

{% hint style="info" %}
If **Connect Codex** fails because `config.toml` couldn't be read, the file has an error, and SEO Utils leaves it unchanged. Fix the file, or run the command instead.
{% endhint %}

{% hint style="warning" %}
In the ChatGPT app, use **Work** or **Codex** mode: **Chat** mode can't use tools on this computer.
{% endhint %}

</details>

<details>

<summary>OpenCode (CLI, Desktop App &#x26; IDE Extension)</summary>

The OpenCode CLI, desktop app and IDE extension share one config folder: `~/.config/opencode` (Windows: `%USERPROFILE%\.config\opencode`).

1. In **Connect an AI app**, choose **OpenCode**
2. Click **"Connect OpenCode"**. SEO Utils adds itself to `opencode.json` in that folder, or to `opencode.jsonc` if that's the file you use. Your other settings and comments are kept
3. Restart OpenCode. To check, run `opencode mcp list`: **seo-utils** shows as connected

**Prefer to edit the file yourself?** Copy the config shown under the button and add its `seo-utils` entry to the `mcp` section of your config. On a Mac it looks like this:

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "seo-utils": {
      "type": "local",
      "command": ["/Applications/SEO Utils.app/Contents/MacOS/SEO Utils", "mcp-stdio"],
      "enabled": true,
      "timeout": 900000
    }
  }
}
```

{% hint style="warning" %}
Keep the `timeout` line. Without it, OpenCode stops every tool after 60 seconds, and some SEO Utils tools take several minutes.
{% endhint %}

</details>

<details>

<summary>Cursor</summary>

1. In **Connect an AI app**, choose **Cursor**
2. Click **"Connect Cursor"**. Cursor opens and asks you to confirm
3. Confirm the install in Cursor

</details>

<details>

<summary>VS Code (GitHub Copilot)</summary>

1. In **Connect an AI app**, choose **VS Code**
2. Click **"Connect VS Code"**. VS Code opens and asks you to confirm
3. Confirm the install and, when prompted, that you trust the server. Then use SEO Utils from Copilot Chat in agent mode

</details>

<details>

<summary>OpenClaw</summary>

1. In **Connect an AI app**, choose **OpenClaw** and copy the command. On a Mac it looks like this:

```bash
openclaw mcp add seo-utils --command '/Applications/SEO Utils.app/Contents/MacOS/SEO Utils' --arg mcp-stdio
```

2. Run it in a terminal. OpenClaw applies the change without a restart; the next turn uses SEO Utils
3. Check the connection with `openclaw mcp doctor seo-utils --probe`

</details>

<details>

<summary>Grok Build (xAI coding agent)</summary>

1. In **Connect an AI app**, choose **Grok Build** and copy the command. On a Mac it looks like this:

```bash
grok mcp add seo-utils -- '/Applications/SEO Utils.app/Contents/MacOS/SEO Utils' mcp-stdio
```

2. Run it in a terminal, then press `r` in `/mcps`

{% hint style="info" %}
Grok Build also reads Claude Code's MCP servers. If you already added SEO Utils to Claude Code, it's there already.
{% endhint %}

</details>

<details>

<summary>Google Antigravity</summary>

1. In **Connect an AI app**, choose **Google Antigravity** and copy the config. On a Mac it looks like this:

```json
{
  "mcpServers": {
    "seo-utils": {
      "args": ["mcp-stdio"],
      "command": "/Applications/SEO Utils.app/Contents/MacOS/SEO Utils"
    }
  }
}
```

2. Add it to `~/.gemini/config/mcp_config.json`, which Antigravity 2.0, the Antigravity IDE and the CLI share. In the IDE, open **… → MCP Servers → Manage MCP Servers → View raw config**. (In Antigravity 2.0, **Add MCP** opens the MCP Store, so edit the file for a custom server.) If the file already lists servers, add the `seo-utils` entry inside its `mcpServers`
3. Ask the agent "What tools do you have access to?" to confirm the connection

</details>

<details>

<summary>Perplexity (Mac — Local)</summary>

Perplexity's Mac app supports local MCP servers through a helper app.

1. Open Perplexity → **Settings** → **Connectors**
2. Install the **PerplexityXPC** helper when prompted
3. Click **Add Connector** → **Simple** tab
4. Set **Server Name** to `SEO Utils`
5. In SEO Utils, choose **Perplexity** in **Connect an AI app**, copy the command and paste it as the **Command**
6. Click **Save** and wait for status to show **Running**
7. Go to Perplexity homepage and toggle your MCP on under **Sources**

{% hint style="warning" %}
**macOS only.** Perplexity local MCP is only available in the Mac App Store version. Windows and Linux users can use Perplexity through Remote Access: see [Connect AI Apps From Anywhere](/guide/mcp-server/connect-ai-apps-from-anywhere).
{% endhint %}

{% hint style="info" %}
Requires a **Perplexity paid plan**.
{% endhint %}

</details>

<details>

<summary>ChatGPT</summary>

**ChatGPT desktop app:** it runs local MCP servers from the same list as Codex (**Settings → MCP servers**, stored in `~/.codex/config.toml`). In SEO Utils, choose **OpenAI Codex** in **Connect an AI app** and click **"Connect Codex"**, then select **Restart** in the ChatGPT app's MCP servers settings. In the ChatGPT app, use **Work** or **Codex** mode: **Chat** mode can't use tools on this computer. See **OpenAI Codex** above.

**ChatGPT on the web:** connect it through Remote Access, with Developer mode and a custom app. See [Connect AI Apps From Anywhere](/guide/mcp-server/connect-ai-apps-from-anywhere).

</details>

<details>

<summary>n8n / Make / Claude Web (claude.ai)</summary>

**Requires a publicly accessible HTTPS URL and the auth token**

Cloud apps cannot connect to `localhost`, so SEO Utils needs a public HTTPS address, and the app must send SEO Utils' auth token (`Authorization: Bearer …`) with every request.

* **n8n** — its MCP nodes support a Bearer header. If n8n runs on the same computer as SEO Utils, use `http://localhost:19515/mcp` directly, no public URL needed: in **Connect an AI app**, choose **Claude web, Grok, n8n, Make** and copy the config with the URL and header
* **Make** — its **MCP Client** app connects to a server URL with an access token
* **Claude Web (claude.ai)** — connect it through Remote Access instead: it needs no public address or token. See [Connect AI Apps From Anywhere](/guide/mcp-server/connect-ai-apps-from-anywhere)

**Getting a public HTTPS address**

* **VPS with a reverse proxy** — if SEO Utils runs on a VPS, set up a reverse proxy (Nginx on Linux, [Caddy](https://caddyserver.com) on any OS) with HTTPS pointing to `127.0.0.1:19515`, and use your public URL (e.g., `https://mcp.yourdomain.com/mcp`)
* **Cloudflare Tunnel** — use a named tunnel on your Cloudflare account ([Cloudflare's guide](https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/)) pointing to `http://localhost:19515`

{% hint style="warning" %}
**Don't use a quick tunnel** (`cloudflared tunnel --url …`, a `trycloudflare.com` address). Quick tunnels don't support Server-Sent Events, which MCP uses to stream responses.
{% endhint %}

The token is in SEO Utils **Settings → MCP Server → Connect an AI app → Other MCP apps**. A connection set up with the token stops working when you rotate it; update it with the new one.

</details>

<details>

<summary>Grok (grok.com)</summary>

Connect it through Remote Access with **grok.com/connectors → New Connector → Custom**. See [Connect AI Apps From Anywhere](/guide/mcp-server/connect-ai-apps-from-anywhere). Grok Build, xAI's coding agent, connects locally: see **Grok Build** above.

</details>

<details>

<summary>Other MCP apps</summary>

In **Connect an AI app**, choose **Other MCP apps**. It shows two configs to copy:

* **For apps that start a local server (stdio)**: runs SEO Utils with `mcp-stdio`. No token, and it keeps working after a token rotation
* **For apps that connect by URL (HTTP)**: `http://localhost:19515/mcp` with the `Authorization: Bearer …` header. Update it after you rotate the token. To keep the connection in one workspace, add an `X-SEO-Utils-Workspace` header (see [Working Across Client Workspaces](#working-across-client-workspaces))

</details>

## Install the SEO Utils Skill (Recommended)

The SEO Utils skill helps your AI assistant choose the right MCP tool automatically. Without it, the AI sometimes calls the wrong tool — for example, fetching third-party API data when you ask about your own rank tracker reports.

The skill is built into SEO Utils, so nothing is downloaded and it works offline. It uses the open [Agent Skills](https://agentskills.io) format (SKILL.md) and works across all major AI assistants. For most apps, **Connect** installs it for you:

| App                                          | How the skill gets there                                                       |
| -------------------------------------------- | ------------------------------------------------------------------------------ |
| **Claude Code**                              | **Connect Claude Code** saves it in Claude Code's skills folder                |
| **Codex, Cursor, VS Code, OpenCode**         | The **Connect** button saves it in the shared skills folder `~/.agents/skills` |
| **OpenClaw, Google Antigravity, Grok Build** | **Install skill** button under the picker, after you add the connection        |
| **Claude Desktop chat, Cowork, claude.ai**   | Plugin from the marketplace `seoutilsapp/seo-utils-skills`, or an uploaded ZIP |
| **ChatGPT**                                  | **Save skill ZIP**, then upload                                                |
| **Perplexity**                               | **Save SKILL.md**, then upload                                                 |

Prefer to place the file yourself? Under **Or set it up yourself**, **Save SKILL.md** saves it and the text beside it names the folder to put it in.

<details>

<summary>Claude Desktop / Cowork / claude.ai</summary>

The skill comes as a Claude plugin, so it updates from its source and reaches claude.ai, the desktop app and Cowork at once.

1. In Claude, go to **Customize → Plugins**
2. Click **Add → Add marketplace** and enter `seoutilsapp/seo-utils-skills`
3. Install **SEO Utils** from that marketplace

**Prefer to upload the skill?** In SEO Utils, choose **Claude Desktop & Cowork** in **Connect an AI app** and click **"Save skill ZIP"**. Then in Claude go to **Customize → Skills → + → Create skill → Upload a skill**. An uploaded skill doesn't update itself; don't install both.

</details>

<details>

<summary>OpenAI Codex, Cursor, VS Code &#x26; OpenCode</summary>

These apps all read the shared skills folder `~/.agents/skills`. **Connect** saves the skill to `~/.agents/skills/seo-utils-mcp-guide/SKILL.md`. Restart the app if it's open.

</details>

<details>

<summary>OpenClaw</summary>

In **Connect an AI app**, choose **OpenClaw** and click **"Install skill"**. The skill is saved to `~/.agents/skills/seo-utils-mcp-guide/SKILL.md`, the shared skills folder. Restart the app if it's open.

</details>

<details>

<summary>Google Antigravity</summary>

In **Connect an AI app**, choose **Google Antigravity** and click **"Install skill"**. The skill is saved to `~/.gemini/config/skills/seo-utils-mcp-guide/SKILL.md`, and new conversations pick it up.

</details>

<details>

<summary>Grok Build</summary>

In **Connect an AI app**, choose **Grok Build** and click **"Install skill"**. The skill is saved to `~/.grok/skills/seo-utils-mcp-guide/SKILL.md`, and Grok Build loads it right away.

</details>

<details>

<summary>ChatGPT</summary>

1. In **Connect an AI app**, choose **ChatGPT** and click **"Save skill ZIP"**
2. In ChatGPT, go to **Plugins → Skills → Create → Upload from your computer**
3. Upload the ZIP file

{% hint style="info" %}
Uploading skills needs a ChatGPT **Business, Enterprise or Edu** plan.
{% endhint %}

</details>

<details>

<summary>Perplexity</summary>

1. In **Connect an AI app**, choose **Perplexity** and click **"Save SKILL.md"**
2. In Perplexity, go to **Skills → Create skill → Upload a skill**
3. Upload the `SKILL.md` file

</details>

### Updating the Skill

SEO Utils updates the skill for you. Each time it starts, it rewrites every installed copy whose version differs from the one built into the app. It only updates copies that already exist: it never adds one where you didn't install it.

The Dashboard's **AI assistant** card shows the state of the copies on your computer: **Skill up to date**, **Skill just updated**, **Skill out of date** or **Skill update failed** (hover the status to see the apps and folders). When a copy is out of date or its update failed, click **Update skill** to write the new version into every copy, then restart those apps if they're open. The card also shows the AI app that used SEO Utils last, the **Access** level (**Full access**, **Setup only** or **Off**) and a link to connect another app.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-29fb27ddc2481d6678f88cdd493273d3d8af5c56%2Fmcp-ai-assistant-card.png?alt=media" alt=""><figcaption><p>The Dashboard's AI assistant card: Access (1), the skill status (2) and the link to connect an app (3)</p></figcaption></figure>

Copies SEO Utils doesn't write itself update the way you added them:

* **Claude plugin (Claude Desktop, Cowork, claude.ai)** — in **Customize → Plugins**, open the `seo-utils` marketplace and select **Check for updates**, or turn on **Sync automatically** once

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FaEarVSoVDEdbMe3FIuLl%2FXnapper-2026-10-15-12.13.27.png?alt=media&amp;token=c731d26e-71fe-45c1-a2de-f83d7c5dda52" alt=""><figcaption><p>Update SEO Utils skill in the Claude Desktop app.</p></figcaption></figure>

* **Uploaded file** (ChatGPT, Perplexity, or a ZIP uploaded to Claude) — save the file again, delete the old skill in the app, and upload the new one

Source: [github.com/seoutilsapp/seo-utils-skills](https://github.com/seoutilsapp/seo-utils-skills)

## Run SEO Tasks from Your Phone

You can run SEO tasks from your phone using either Cowork (Dispatch) or Telegram/Discord channels. Both methods process tasks on your desktop using the MCP server.

{% hint style="info" %}
With Remote Access, the Claude mobile app can also use SEO Utils directly through a connector. See [Connect AI Apps From Anywhere](/guide/mcp-server/connect-ai-apps-from-anywhere).
{% endhint %}

{% tabs %}
{% tab title="Using Cowork" %}
With [**Dispatch**](https://support.claude.com/en/articles/13947068-assign-tasks-to-claude-from-anywhere-in-cowork) in Cowork, you can assign SEO tasks from your phone and Claude will execute them on your desktop.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FTTteCJHeqpizMioftLWu%2F651722891_26122169734092241_7220925609115220025_n-1.jpg?alt=media&amp;token=ae30c609-a03b-4223-a002-ccd26816813e" alt="" width="188"><figcaption><p>Assign SEO tasks from your phone using Dispatch in Cowork</p></figcaption></figure>

For example, you can message Claude from your phone:

* "Generate a weekly SEO report for example.com and save it as HTML"
* "Check the backlink profile for competitor.com"
* "Find keyword cannibalization issues for my site in GSC"

Claude processes the task on your desktop using your local SEO data and MCP tools, then returns the results to your phone.

{% hint style="warning" %}
**Requirements:** Your computer must be awake and Claude Desktop must be open. You need a Claude **Pro or Max plan** and the latest Claude mobile + desktop apps installed.
{% endhint %}
{% endtab %}

{% tab title="Using Telegram or Discord" %}
With [**Channels**](https://code.claude.com/docs/en/channels) in Claude Code, you can send SEO prompts from Telegram or Discord — Claude processes them on your computer and replies right back in the chat.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2F9j11YZD2mDJPG9dZ8f9D%2F656274220_26154072467568634_4527803090415720073_n.jpg?alt=media&amp;token=abfcedd2-66e0-499f-81d7-b5ee9c08915a" alt="" width="188"><figcaption><p>Send SEO prompts from Telegram to Claude Code with MCP access</p></figcaption></figure>

{% stepper %}
{% step %}
**Create a project folder and set up MCP**

Create a folder for your SEO workspace:

```bash
mkdir ~/seo-workspace && cd ~/seo-workspace
```

Then add SEO Utils to Claude Code: in SEO Utils, choose **Claude Code** in **Connect an AI app** and click **"Connect Claude Code"** (see [Connecting to AI Assistants](#connecting-to-ai-assistants)). It's added for all your projects, this folder included.
{% endstep %}

{% step %}
**Install** [**Bun**](https://bun.sh) (required for channel plugins)

```bash
curl -fsSL https://bun.sh/install | bash
```

{% endstep %}

{% step %}
**Set up Telegram or Discord channel**

Follow the official guide for your platform:

* [**Telegram setup**](https://code.claude.com/docs/en/channels) — Create a bot via BotFather, install the plugin, configure, and pair
* [**Discord setup**](https://code.claude.com/docs/en/channels) — Create a bot in Discord Developer Portal, install the plugin, configure, and pair
  {% endstep %}

{% step %}
**Start Claude Code with channels enabled**

```bash
cd ~/seo-workspace
claude --channels plugin:telegram@claude-plugins-official
```

Or for Discord:

```bash
claude --channels plugin:discord@claude-plugins-official
```

{% endstep %}

{% step %}
**Send SEO prompts from your phone**

Open Telegram or Discord on your phone and message your bot:

* "Show me the top trending queries in GSC for my site"
* "Generate a backlink report for competitor.com"
* "Create an automation that emails me when rank tracking completes"

Claude processes the request on your computer and replies in the chat.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Requirements:** Your computer must be running with Claude Code open. Channels require Claude Code v2.1.80+, a Claude **Pro or Max plan**, and [Bun](https://bun.sh) installed.
{% endhint %}

**Multiple channels for different clients**

Run separate Claude Code sessions with different bot tokens — one per client or project. Each session has its own MCP connection, workspace, and chat bot.

```bash
# Client A
cd ~/seo-workspace-client-a
TELEGRAM_BOT_TOKEN=<token_A> claude --channels plugin:telegram@claude-plugins-official

# Client B
cd ~/seo-workspace-client-b
TELEGRAM_BOT_TOKEN=<token_B> claude --channels plugin:telegram@claude-plugins-official
```

The environment variable overrides the saved config, so each session uses a different bot. Works the same way for Discord with `DISCORD_BOT_TOKEN`.
{% endtab %}
{% endtabs %}

## Available Tools

The MCP server exposes the following tools that the AI uses automatically:

{% hint style="info" %}
The AI reaches most of these through a few catalog tools, so it doesn't load dozens of tool definitions up front: it finds an action with `search_actions`, reads its parameters with `describe_action`, and runs it with `read_action` (your local data, free), `lookup_action` (external data, may spend your API credits) or `write_action` (creates, changes, deletes or sends something). The names below are the action names it uses.
{% endhint %}

**Data Tools** (read your existing SEO data):

| Tool              | Description                                                                                      |
| ----------------- | ------------------------------------------------------------------------------------------------ |
| `list_tables`     | Lists all database tables with descriptions                                                      |
| `describe_table`  | Shows columns, types, and relationships for a specific table                                     |
| `query_database`  | Executes read-only SQL queries against your SEO data                                             |
| `query_gsc`       | Specialized SQL tool for Google Search Console data with built-in timezone and filter guidance   |
| `list_workspaces` | Lists all workspaces and shows the active one and how it was chosen                              |
| `set_workspace`   | Switches the AI to a different workspace until the AI app reconnects ([Workspaces](#workspaces)) |

**Action Tools** (fetch live data from APIs):

| Tool                                 | Description                                                                                                                                                                                                                       |
| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `check_keyword_metrics`              | Check search volume, difficulty, CPC, and search intents for keywords via DataForSEO                                                                                                                                              |
| `fetch_serp_data`                    | Fetch live Google SERP results for keywords. Caches results to avoid duplicate API calls                                                                                                                                          |
| `get_backlink_summary`               | Get backlink overview: total backlinks, referring domains, domain rank, spam score, distributions                                                                                                                                 |
| `get_backlink_history`               | Get historical backlink trends: new/lost backlinks and referring domains over time                                                                                                                                                |
| `fetch_backlinks`                    | Fetch individual backlink records with filters (dofollow, platform type, etc.)                                                                                                                                                    |
| `get_referring_domains`              | Get list of domains linking to a target with rank, spam score, and backlink count                                                                                                                                                 |
| `get_anchor_texts`                   | Get anchor text distribution — which texts are used most in backlinks                                                                                                                                                             |
| `get_backlink_competitors`           | Find domains competing for the same backlink sources                                                                                                                                                                              |
| `get_content_gap`                    | Find keywords competitors rank for but you don't                                                                                                                                                                                  |
| `get_backlink_gap`                   | Find domains linking to competitors but not you                                                                                                                                                                                   |
| `get_demographics`                   | Fetch demographic data (population, income, age, homeownership) around a location — supports US, UK, Australia, and Canada                                                                                                        |
| `get_gmb_report_group_dashboard`     | Get aggregated multi-location dashboard — visibility score, rankings, trends across all locations in a report group                                                                                                               |
| `create_gmb_report_group`            | Create a report group from existing individual GMB rank tracker reports for multi-location analytics                                                                                                                              |
| `delete_gmb_report_group`            | Delete a report group (individual reports are not affected)                                                                                                                                                                       |
| `find_google_business`               | Resolve a business name/address to a Google Place ID via Google Places autocomplete (used before create\_gmb\_rank\_tracker\_report or create\_google\_business\_review\_fetch)                                                   |
| `find_google_business_from_maps_url` | Resolve a Google Maps link (full URL, maps.app.goo.gl share link, or ?cid= link) to the business's Place ID, name, and address — no Google Places API key needed; goes through DataForSEO                                         |
| `create_gmb_rank_tracker_report`     | Create a new GMB rank tracker report with full grid, schedule, and keyword setup. Auto-geocodes place\_id → center coords; auto-generates the measurement grid (square/circle/polygon) or accepts an explicit list of coordinates |
| `update_gmb_rank_tracker_report`     | Partially update an existing GMB rank tracker report — change schedule, grid, locale, branding, or measurement points. Markers regenerate automatically when grid inputs change                                                   |
| `run_gmb_rank_tracker`               | Trigger a fresh snapshot run for an existing GMB rank tracker report. Asynchronous; consumes DataForSEO credits (one task per keyword × grid point)                                                                               |
| `delete_gmb_rank_tracker_reports`    | Permanently delete one or more GMB rank tracker reports (up to 100 per call) with their keywords, grid, snapshots and ranking history. Each report is deleted on its own; the result lists what was deleted and why any was not   |
| `get_traffic_summary`                | Get organic traffic overview (ETV, keyword counts, paid traffic) for a domain                                                                                                                                                     |
| `get_organic_keywords`               | Get keywords a domain ranks for with position, volume, traffic, difficulty                                                                                                                                                        |
| `get_traffic_competitors`            | Find organic search competitors with shared keyword overlap                                                                                                                                                                       |
| `get_top_pages`                      | Get top pages by organic traffic for a domain                                                                                                                                                                                     |
| `get_historical_rank`                | Get historical organic traffic and ranking trends over time (monthly)                                                                                                                                                             |
| `get_keyword_suggestions`            | Get Google keyword suggestions with full metrics (volume, KD, CPC, backlinks, SERP info)                                                                                                                                          |
| `get_bing_related_keywords`          | Get Bing related keywords with metrics                                                                                                                                                                                            |
| `fetch_autocomplete_keywords`        | Trigger autocomplete keyword generation from Google or Bing (background)                                                                                                                                                          |
| `get_autocomplete_keywords`          | Get autocomplete keywords with metrics from the database                                                                                                                                                                          |
| `bulk_traffic_analysis`              | Analyze organic traffic for multiple domains at once                                                                                                                                                                              |
| `bulk_backlink_analysis`             | Analyze backlink profiles for multiple URLs/domains at once                                                                                                                                                                       |
| `submit_url_for_google_indexing`     | Submit a URL for Google indexing via the Indexing API                                                                                                                                                                             |
| `check_google_indexing_status`       | Check a URL's indexing status via the URL Inspection API (returns coverage state, verdict, etc.)                                                                                                                                  |
| `trigger_indexing_action`            | Run batch inspection scan, trigger internal link crawl, check crawl status, recalculate paths                                                                                                                                     |
| `submit_url_to_index_now`            | Submit a URL to IndexNow for Bing indexing                                                                                                                                                                                        |
| `check_index_now_status`             | Check if a URL is indexed by Bing                                                                                                                                                                                                 |
| `send_email`                         | Send an email with optional attachments using your configured SMTP credentials                                                                                                                                                    |
| `get_robots_compliance`              | Per-bot robots.txt compliance for a log analysis report — which bots are allowed, how many requests violated a Disallow rule. Uses the Go-side robots.txt matcher (SQL can't evaluate robots.txt rules)                           |

**Saved Keywords Tools** (manage your keyword lists):

| Tool                         | Description                                      |
| ---------------------------- | ------------------------------------------------ |
| `list_saved_keywords_lists`  | List all keyword lists with keyword counts       |
| `create_saved_keywords_list` | Create a new keyword list with a name and locale |
| `update_saved_keywords_list` | Rename a keyword list                            |
| `delete_saved_keywords_list` | Delete a keyword list and all its keywords       |
| `add_keywords_to_list`       | Add keywords to a list (duplicates are skipped)  |
| `remove_keywords_from_list`  | Remove keywords from a list by their IDs         |

**Organic Rank Tracker Tools** (set up trackers, grow tracked keyword sets, and queue runs):

| Tool                                   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `create_organic_rank_tracker_report`   | Create a rank tracker with keywords, locale, schedule, collection method, device type, optional DataForSEO settings, and optional ranked-page HTML capture. HTML capture is off by default; its scope can include only the target domain or the target and tracked competitors, with a configurable retention period. The first scan runs automatically unless you say otherwise or its schedule window delays it.                          |
| `update_organic_rank_tracker_report`   | Update an existing tracker's name, schedule, collection method, business name, include-subdomains setting, DataForSEO settings, or ranked-page HTML capture, scope, and retention. Domain, keywords, locale, and device type cannot be changed. Disabling capture keeps existing HTML history. Some pixel-tracking settings lock after data is collected.                                                                                   |
| `add_organic_rank_tracker_keywords`    | Add keywords to an existing rank tracker report. A keyword the report already has is not added twice. With a weight, every listed keyword — new or existing — gets that weight. Does NOT rerun the tracker — the AI asks you separately.                                                                                                                                                                                                    |
| `update_organic_rank_tracker_keywords` | Set the weight of existing keywords in a rank tracker report: a whole number from 0 to 1000, where 100 counts once and 0 (Track only) tracks a keyword without counting it. Keywords are matched by their exact text; any not found are listed back.                                                                                                                                                                                        |
| `remove_organic_rank_tracker_keywords` | Remove keywords from a rank tracker report by their text. Destructive — also deletes those keywords' historical positions, PAA appearances, and insights. Keywords not found in the report are reported back but don't cause an error.                                                                                                                                                                                                      |
| `run_rank_tracker`                     | Queue a rank tracker run for a report. Background job; consumes DataForSEO credits. Optional `force_refresh` to rescrape everything.                                                                                                                                                                                                                                                                                                        |
| `compare_ranked_page_html`             | Compare two completed ranked-page HTML captures from the same URL, or explicitly compare an old and replacement URL. Returns paginated line differences, capture metadata, ranked/new/lost states, and affected keywords. It defaults to main content; full HTML is available for metadata and template analysis. It reads existing local captures, does not rescrape, and treats changes as evidence rather than proof of a ranking cause. |

{% hint style="info" %}
`compare_ranked_page_html` analyzes the rendered HTML of pages that ranked, not Google's SERP source. Enable [**Capture Ranked Page HTML**](/guide/organic-rank-tracker#page-html-tab) on the tracker first. The AI finds two completed captures in your local history, then uses the comparison tool; no DataForSEO credits are consumed by the comparison.
{% endhint %}

**GSC Rank Tracker Tools** (ten actions: read your free Search Console rankings, read or ask for an explanation of a move, and set up trackers; see [GSC Rank Tracker](/guide/google-search-console/gsc-rank-tracker)):

| Tool                               | Runs with       | Description                                                                                                                                                                                          |
| ---------------------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `list_gsc_rank_trackers`           | `read_action`   | Your trackers with their market, how many keywords and rules they hold, how current they are, unread alerts and the headline figures (average position, top 3, top 10, movers). Free                 |
| `get_gsc_rank_positions`           | `read_action`   | Daily, weekly or monthly positions of a tracker's keywords with impressions, clicks and each day's data state. These are the Grid's own numbers, 20 keywords a page, with a cursor to continue. Free |
| `get_gsc_rank_movers`              | `read_action`   | The confirmed movers of a date range: position, click and page change. Free                                                                                                                          |
| `list_gsc_rank_alerts`             | `read_action`   | Rank alerts, newest first, for one tracker or all of them. Reading never marks an alert read. Free                                                                                                   |
| `get_gsc_keyword_move_explanation` | `read_action`   | The saved "Why did it move?" answer for a keyword, or `cached: false` when there is none. Never sends anything. Free                                                                                 |
| `explain_gsc_keyword_move`         | `lookup_action` | Asks for a new "Why did it move?" answer, written by the AI model of **Settings > Services > GSC Rank Tracker AI**. Spends your AI provider's credit unless a saved answer exists                    |
| `create_gsc_rank_tracker`          | `write_action`  | Creates a tracker for a Search Console property in one market. Free, it only reads Search Console                                                                                                    |
| `add_gsc_rank_items`               | `write_action`  | Adds keywords and rules, up to 1,000 per call, and starts downloading their 16-month history                                                                                                         |
| `set_gsc_rank_target`              | `write_action`  | Sets or clears the target page of one keyword                                                                                                                                                        |
| `archive_gsc_rank_items`           | `write_action`  | Archives keywords or rules. Their history is kept, and nothing is deleted                                                                                                                            |

{% hint style="info" %}
The AI reads `get_gsc_keyword_move_explanation` first, which is free, and should ask you before `explain_gsc_keyword_move`, since that can spend credit. Restoring or deleting items, changing tracker settings and marking alerts read are not available over MCP: do them in the app.
{% endhint %}

#### Try these prompts with the GSC Rank Tracker

Replace the text in `<angle brackets>` with your own. Each of these was tried against the GSC rank tracker actions.

* "What GSC rank trackers do I have, and how are they doing?"
* "Show me daily positions for my `<tracker>` tracker over the last 2 weeks." Then "Show me the next page." The AI shows 20 keywords a page by default.
* "Which keywords moved the most this week in `<tracker>`?"
* "Any ranking alerts I should look at?" Reading alerts never marks them read.
* "Why did '`<keyword>`' drop?" The AI first reads the saved answer, which is free, and asks before it spends AI credit on a new one. Asking again later, even in a new chat, reuses the saved answer.
* "Create a GSC rank tracker for example.com in the United Kingdom and track: moka pot, french press, aeropress."
* "Set the target page for 'moka pot' to <https://example.com/moka-pot>", then "Archive 'aeropress' in that tracker."
* "Add these 1,200 keywords …" The AI adds them in batches of up to 1,000.

The GSC Rank Tracker does not check live Google results over MCP. If you ask for that, the AI may offer the general SERP lookup (`fetch_serp_data`), which costs DataForSEO credit.

**LLM Rank Tracker Tools** (track brand visibility in AI answers):

| Tool                             | Description                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `create_llm_rank_tracker_report` | Create a new LLM rank tracker — brand variants, search terms, AI engines (ChatGPT, ChatGPT Web Search, Google AI Overview, Google AI Mode), locale, and schedule. Auto-runs the first snapshot unless you say otherwise (scheduled reports still auto-start within \~15 minutes; use an on-demand schedule to fully defer). Requires DataForSEO credentials and a configured LLM extraction provider. The first brand variant becomes the report's title |
| `run_llm_rank_tracker`           | Queue a snapshot run for an existing LLM rank tracker report. Background job; sends every search term to every configured AI engine and consumes DataForSEO credits. One snapshot per day — re-running the same day updates today's snapshot                                                                                                                                                                                                             |

**AI Visibility Tools** (how often AI answers name your brand against competitors — see [AI Visibility](/guide/ai-visibility)):

{% hint style="info" %}
The read tools are free: they answer from what SEO Utils already loaded and never send a request to DataForSEO. When a list or the Overview is not loaded yet, the AI gets its price instead, and asks you before it runs the paid tool. A paid tool never spends more than the price you agreed to, and sends nothing when the price went up since the quote. Exports and the client report are not available over MCP; ask the AI to write its own report from the read tools instead.
{% endhint %}

| Tool                                | Runs with       | Description                                                                                                                           |
| ----------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| `list_ai_visibility_explorations`   | `read_action`   | Your explorations, most recently opened first, with your share of voice and the spend so far. Free                                    |
| `get_ai_visibility_exploration`     | `read_action`   | One exploration: its brands, market, window and topic, its spend so far, and the status of its latest load. Free                      |
| `get_ai_visibility_overview`        | `read_action`   | The Overview numbers: share of voice, mentions, citations, gaps, share over time, countries, cited domains and AI search demand. Free |
| `get_ai_visibility_gaps`            | `read_action`   | Where each competitor wins and you don't, plus the pages cited for a competitor and not for you. Free                                 |
| `search_ai_mentions`                | `read_action`   | The real prompts and answers behind a number (you mentioned, rivals win, one competitor wins, both…), filtered and sorted. Free       |
| `get_ai_visibility_prompt`          | `read_action`   | One prompt's full AI answer with its sources. Free                                                                                    |
| `get_ai_visibility_citations`       | `read_action`   | The domains cited for each brand, and your own cited pages. Free                                                                      |
| `estimate_ai_visibility_load`       | `read_action`   | Quote an Overview load or Refresh before it starts. Free                                                                              |
| `get_ai_visibility_load_status`     | `read_action`   | Progress of the latest load. Free                                                                                                     |
| `get_ai_visibility_markets`         | `read_action`   | The countries and languages you can explore, and where ChatGPT data exists. Free                                                      |
| `get_ai_visibility_ambiguity_hints` | `read_action`   | Warns about brand names that are common words, before you create an exploration. Free                                                 |
| `resolve_ai_visibility_brand`       | `lookup_action` | Turns a website or a name into a brand (it reads the site's home page once for its name). Free                                        |
| `suggest_ai_visibility_competitors` | `lookup_action` | Suggests up to 8 competitors from AI answers. About $0.10 when not cached, only after you agree                                       |
| `load_ai_visibility_list`           | `lookup_action` | Loads a page of prompts or cited pages that is not loaded yet. About $0.10–$0.20 a request, only after you agree                      |
| `run_ai_visibility_load`            | `write_action`  | Starts the Overview load or Refresh at the quoted price, only after you agree. Runs in the background                                 |
| `stop_ai_visibility_load`           | `write_action`  | Stops the running load. Requests already sent are still charged                                                                       |
| `create_ai_visibility_exploration`  | `write_action`  | Creates an exploration: your brand and up to 5 competitors in one market. Free; it loads nothing until you start a load               |
| `update_ai_visibility_exploration`  | `write_action`  | Renames an exploration or changes its brands, market, window or topic. A changed setup needs a new (paid) load                        |
| `delete_ai_visibility_exploration`  | `write_action`  | Deletes an exploration. The AI asks you first                                                                                         |

**Review Fetcher Tools** (track Google Business Profile reviews):

| Tool                                  | Description                                                                                                                                                                                                                                                                                                                                                                                                             |
| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `create_google_business_review_fetch` | Start tracking a business's Google reviews — resolves the business via `find_google_business` (name) or `find_google_business_from_maps_url` (Google Maps link), sets the initial pull depth, locale, and DataForSEO queue priority, and runs the first fetch unless you say otherwise. Requires DataForSEO credentials. Note: there is no automatic schedule for review fetches — each snapshot is triggered on demand |
| `run_google_business_review_fetch`    | Trigger a review fetch for a tracked business. Background job; pulls the latest reviews via DataForSEO, deduplicates them, and flags new, missing (removed/filtered by Google), and reinstated reviews. Returns the snapshot ID so progress can be checked                                                                                                                                                              |

**N.A.P Finder Tools** (find local citation pages):

| Tool             | Description                                                                                                                                                                                                                                                                                                                                                                                                                         |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `run_nap_finder` | Create and run a N.A.P Finder report in one step — searches Google for exact-match combinations of your business name, address, and phone number to find the pages that cite them. Each call is a fresh report (reports are one-shot and can't be re-run). Scrapes via DataForSEO, your own IP, or proxies; supports custom search-term template lists, excluded domains, and per-country locales. Results arrive in the background |

The AI resolves the business address and phone automatically via `find_google_business` when you only give a name, and analyzes finished reports through `query_database` on the `nap_finder_items` table (e.g. citations per domain, missing listings).

**Content Struct Tools** (competitor content analysis and AI outlines):

| Tool                       | Description                                                                                                                                                                                                                                                                                                                                                                                               |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `create_content_struct`    | Create a content analysis report for one or more keywords — scrapes the top Google results and extracts meta titles, descriptions, and heading structures (H1–H4) from up to 20 top-ranking competitor pages per keyword. Multiple keywords are grouped. Scrapes via your own IP (default), proxies, or the DataForSEO SERP API (consumes credits). The analysis runs in the background                   |
| `generate_content_outline` | Generate an AI content outline from a finished content struct report — sends the competitor headings to your chosen AI model (OpenAI, Anthropic, Gemini, OpenRouter, or Ollama) and produces a suggested meta title, meta description, and a full H1–H4 outline. Replaces any existing outline once the new one is ready (a failed generation keeps the old outline); uses your AI provider's API credits |

**SERP Clustering Tools** (group keywords into topic clusters):

| Tool                            | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `create_serp_clustering_report` | Create a SERP clustering report and run it — scrapes the Google results for every keyword and groups keywords into clusters when their SERPs share enough URLs (keywords whose results overlap can be targeted by one page). Supports a similarity threshold (3–7 shared results), three clustering algorithms (default / strict / balanced strict), per-country locales, device choice, and an optional target domain for per-cluster rank analysis. Scrapes via your own IP (default), proxies, or the DataForSEO SERP API (consumes credits); with DataForSEO connected it also fetches search volume / CPC / difficulty for the keywords. Runs in the background |
| `run_serp_clustering`           | Re-run clustering for an existing report — optionally adding new keywords first. Reuses SERP data newer than `saved_serp_days` instead of re-scraping, and can either re-cluster everything from scratch or keep existing clusters and only distribute new keywords into them. The similarity threshold can change per run; locale, device, and SERP depth stay fixed                                                                                                                                                                                                                                                                                                |

**Text Analysis Tools** (extract entities and topics with NLP):

| Tool               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `run_nlp_analysis` | Run an NLP entity analysis on pasted text/HTML or on live URLs (scraped first) — extracts the named entities (people, organizations, places, products, concepts) the content is about, with confidence scores, Wikipedia links, and mention counts; TextRazor also extracts topics. Uses whichever NLP provider you configured (TextRazor, Dandelion, or Google NLP — API key required in Settings, uses that provider's quota). Each call creates a new Text Analysis report and runs in the background |

**Internal Links Tools** (find, review and apply internal links — see [Internal Links](/guide/google-search-console/internal-links#use-it-from-an-ai-assistant)):

| Tool                                  | Description                                                                                                                             |
| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| `get_internal_links_overview`         | The Internal Links numbers for a property: pages crawled, orphans, priority targets, link text and link cap problems                    |
| `list_internal_link_opportunities`    | One Opportunities list (priority targets, orphans, anchors, too many links, duplicate links, or every page), searched, sorted and paged |
| `get_internal_link_source_candidates` | The pages that could link to one target page, closest first                                                                             |
| `estimate_internal_link_run`          | Quote a Find links run before it starts. Free                                                                                           |
| `run_internal_links`                  | Start Find links for up to 50 target pages. Spends TypeSafe and embedding credit                                                        |
| `get_internal_links_run_status`       | Progress of the latest Find links run                                                                                                   |
| `cancel_internal_links_run`           | Stop the running Find links run. Finished pages keep their suggestions                                                                  |
| `list_internal_link_suggestions`      | Suggestions by status and target page, with the sentence, the link text and the reason                                                  |
| `review_internal_link_suggestions`    | Accept, reject or move suggestions back to review, up to 200 at a time                                                                  |
| `edit_internal_link_anchor`           | Change a suggestion's link text to other words of the same sentence                                                                     |
| `apply_internal_links`                | Write accepted links into your live WordPress site, up to 50 at a time                                                                  |
| `revert_internal_links`               | Remove applied links from your live WordPress site                                                                                      |
| `reconcile_internal_links`            | Settle unconfirmed applies and reverts by reading the pages (**Check N unconfirmed**)                                                   |
| `get_internal_link_rules`             | The link rules, Advanced settings and your own rules for the AI                                                                         |
| `save_internal_link_rules`            | Change some of those rules. The others keep their values                                                                                |
| `get_internal_link_crawl_status`      | Progress of the latest link crawl                                                                                                       |

**Automation Tools** (manage your workflows):

| Tool                              | Description                                            |
| --------------------------------- | ------------------------------------------------------ |
| `get_automation_schemas`          | Get available trigger types, action types, and configs |
| `create_automation`               | Create a new automation workflow                       |
| `update_automation`               | Update or pause/resume an automation                   |
| `delete_automation`               | Delete an automation and its history                   |
| `save_automation_report_mappings` | Set which reports trigger an automation                |

**Workspace Tools** (manage your workspaces):

| Tool               | Description                                                                                                        |
| ------------------ | ------------------------------------------------------------------------------------------------------------------ |
| `create_workspace` | Create a new workspace for organizing projects. Name must be unique; new workspaces are not made active by default |
| `update_workspace` | Rename a workspace or update its logo URL. Default workspace can be renamed                                        |

To list, query, or switch workspaces, the AI uses the existing `list_workspaces` / `set_workspace` data tools. Deleting a workspace is done in the desktop app (and is blocked if the workspace still contains data).

**SEO Test Tools** (manage your SEO experiments):

| Tool              | Description                                                                                                                      |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `create_seo_test` | Create a new SEO test (split / time\_based / url\_switch). Validates type-specific fields and fetches baseline metrics from GSC  |
| `update_seo_test` | Update an existing SEO test's name, description, hypothesis, end\_date, or type-specific timing fields (test\_type is immutable) |

To list, view metrics, or delete tests, the AI uses `query_database` on the `tests`, `test_pages`, and `test_metrics` tables. Deleting a test is done in the desktop app.

**Keyword Insights Tools** (analyze ranking behavior):

| Tool                          | Description                                                                               |
| ----------------------------- | ----------------------------------------------------------------------------------------- |
| `get_keyword_insight_summary` | Get insight counts (trending up/down, pogo sticking, flickering, key events) for a report |

The AI can also query the `keyword_insights`, `keyword_insight_histories`, `ga4_landing_page_metrics`, and `ga4_property_mappings` tables directly via `query_database` for deeper analysis.

### Google Analytics tools

The read tools use the GA4 data SEO Utils has already synced (see [GA4 Traffic](/guide/google-analytics-4/ga4-traffic)), so they answer at once and cost nothing. Name a property with its `mapping_id` from `list_ga4_properties`, or with the site's domain.

| Tool                                | Description                                                                                                            |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| `list_ga4_properties`               | Lists the connected GA4 properties with their sync state and the days that are synced                                  |
| `get_ga4_traffic_by_channel`        | Sessions, key events and revenue for every channel and the organic split by search engine, with an optional comparison |
| `get_ga4_key_events`                | Key events per event and channel                                                                                       |
| `get_ga4_top_sources`               | The busiest source / medium rows, such as `google / organic`                                                           |
| `get_ga4_monthly_traffic`           | Traffic per month, with GA4's monthly users                                                                            |
| `get_ga4_organic_vs_search_console` | GA4 organic sessions next to Search Console clicks, per day, week or month                                             |
| `get_ga4_page_traffic`              | Organic sessions, key events and revenue for up to 100 pages                                                           |
| `sync_ga4_property`                 | Starts a sync of one property now. It calls Google Analytics, so it uses a little of the property's API quota          |

{% hint style="info" %}
SQL queries are **read-only** — the AI cannot modify your data via SQL. Action tools fetch data from external APIs (DataForSEO) and may incur API costs. Saved Keywords, Organic Rank Tracker, LLM Rank Tracker, Review Fetcher, and N.A.P Finder tools can create, update, and delete keyword lists, add, weight or remove keywords in rank tracker reports, create LLM rank tracker reports and review fetches, and queue tracker/fetch/citation-search runs on your behalf. Removing rank tracker keywords also deletes their historical positions and insights — there is no undo. Running a tracker, review fetch, or N.A.P Finder search via DataForSEO consumes DataForSEO credits. GSC Rank Tracker tools create trackers, add keywords and rules, set target pages and archive items, which is free because they read Search Console, and asking why a keyword moved spends your AI provider's credit. AI Visibility tools create, edit and delete explorations, and their paid tools (an Overview load, a list page, competitor suggestions) spend DataForSEO credits only after you agree to the quoted price.
{% endhint %}

## Built-in Prompts

Claude Desktop shows these in the prompt picker — click the slash icon to find them:

| Prompt                       | What It Does                                                                         |
| ---------------------------- | ------------------------------------------------------------------------------------ |
| **Weekly SEO Report**        | Comprehensive weekly performance report with rankings, GSC data, and recommendations |
| **Keyword Cannibalization**  | Finds keywords where multiple pages compete for the same query                       |
| **Weak Pages Analysis**      | Identifies underperforming pages that need optimization                              |
| **Ranking Trends**           | Analyzes ranking changes over time with winners and losers                           |
| **Content Gap Analysis**     | Finds content opportunities from Search Console data                                 |
| **Local SEO Report**         | Google Business rank tracking performance report                                     |
| **SERP Landscape**           | Competitive analysis of SERP features and competitors                                |
| **Ranked Page HTML Changes** | Compares stored page captures and evaluates changes around new, lost, or moved pages |
| **Client Report**            | Professional, client-ready report in non-technical language                          |

## Example Prompts

Here are some prompts you can try right away. Click each category to expand.

{% hint style="info" %}
**Tip for GSC queries:** When asking about your own site's search performance, include **"in GSC"** or **"from my Search Console data"** in your prompt. This tells the AI to query your local Google Search Console data instead of fetching third-party estimates.
{% endhint %}

<details>

<summary>📊 Reporting &#x26; Charts</summary>

* "Create a dashboard to report all SEO metrics of tuikhoeconban.com" (Work with [Claude Cowork Live Artifact to create live SEO dashboard](https://www.facebook.com/groups/seoutils/posts/1360693665894236/).)
* "Pull my Google Search Console data for the last 30 days. Show me a line chart of daily clicks and impressions over time. Also show a table of the top 10 queries by clicks."
* "Get my organic rank tracker data for example.com. Create a pie chart showing the ranking distribution: how many keywords are on page 1 (positions 1-10), page 2 (11-20), page 3 (21-30), and beyond."
* "Pull my Google Business rank tracker data for My Business Name. Create a heatmap or grid visualization showing my ranking positions across different geographic points."
* "Compare my Google Search Console query performance between the last 7 days and the previous 7 days. Find the top 10 queries that gained the most clicks and the top 10 that lost the most."
* "Create a comprehensive SEO dashboard for example.com with: 1) A line chart of GSC clicks over the last 30 days, 2) Current organic rank distribution as a donut chart, 3) A table of top 10 pages by impressions."

</details>

<details>

<summary>🔍 SEO Analysis</summary>

* "Find pages on my site that rank on positions 11-20 (page 2) with more than 100 impressions. These are quick-win opportunities to push to page 1."
* "Find pages with high impressions but low CTR — the title or description probably needs work."
* "Which keywords have multiple pages competing for the same position? Show me the cannibalization issues."
* "Find queries I'm appearing for in Google but don't have a dedicated page targeting them."

</details>

<details>

<summary>📈 Tracking &#x26; Trends</summary>

* "Compare my organic ranking distribution today vs 30 days ago. How many keywords moved to page 1? How many dropped off?"
* "Show me my biggest ranking winners and losers this month."
* "List all my organic rank tracker reports and how many keywords each one tracks."

</details>

<details>

<summary>🗺️ Local SEO</summary>

* "Show me my Google Business rank tracking data. Create a summary of how many grid points I rank in top 3, top 10, and not ranking."
* "Show me the ranking trend for 'hot pot' in my GMB report #7"
* "Compare my local rankings between this week and last week. Which keywords improved?"
* "List all my GMB rank tracker reports with their keywords and latest snapshot dates"
* "Show me the demographics around my business and correlate with my local rankings — do I rank better in high-income or high-density areas?"
* "Show me the multi-location dashboard for Haidilao Hot Pot across all locations"
* "Create a report group for all my Haidilao reports so I can see combined rankings"
* "What's my visibility score for Haidilao across Bellevue and Seattle? Compare vs 30 days ago"
* "Which location has the best local rankings for 'hot pot'?"

</details>

<details>

<summary>📍 Create, Update &#x26; Delete GMB Rank Trackers</summary>

* "Create a GMB rank tracker for Haidilao Hot Pot in Bellevue, WA tracking 'hot pot bellevue', 'best chinese bellevue', and 'haidilao'. Use a 5x5 square grid with 500m radius, run weekly on Mondays 9-11am Pacific."
* "Set up a circle 7x7 GMB tracker for my dental clinic at 100 Park Ave, New York with 1 mile radius, tracking 'dentist near me', 'emergency dentist nyc', and 'tooth cleaning manhattan'. Run once now so I can see the baseline."
* "Track Pho Bac Sup Shop in Seattle for 'pho near me' and 'best pho seattle' — square 7x7, 800m radius, weekly Mondays at 8am Pacific."
* "Create a GMB tracker for Joe's Pizza in NYC simulating searches from Brooklyn instead of Manhattan, tracking 'pizza near me' and 'best slice brooklyn'."
* "I have 9 specific tracking points for my market research project — coordinates: \[{lat: 47.61, lng: -122.20}, {lat: 47.62, lng: -122.20}, ...]. Create a GMB report for Haidilao Hot Pot Bellevue using those exact points and track 'coffee shop'."
* "Update my Haidilao GMB report — bump it from 5x5 to 7x7 grid and change the schedule to twice-per-month on the 1st at 8am Pacific."
* "Disable the daily run schedule on GMB report #7 and switch it to a one-time manual tracker."
* "Rebrand the export header on GMB report #12 to 'Q1 Local SEO — Acme Dental' and set the comparison period to 30 days."
* "Run a fresh snapshot for GMB report #7 right now — I want to see today's rankings without waiting for the schedule."
* "Delete GMB report #12 — it was only a test."
* "I have a few 'Joe's Pizza' GMB test reports. List them for me, then delete all of them once I confirm."

</details>

<details>

<summary>🌐 Create &#x26; Update Organic Rank Trackers</summary>

* "Set up an organic rank tracker for example.com in the US English, tracking 'best seo tool', 'seo software', and 'free seo audit'. Use DataForSEO, desktop, weekly schedule."
* "Track moz.com on mobile in the UK for 'keyword research', 'local seo', and 'backlink checker' — DataForSEO, weekly, start scanning right away."
* "Create a rank tracker for mycompany.io scraping from my own IP with 5-second delays. Daily schedule. Keywords: 'widget pricing', 'widget reviews', 'best widgets 2026'. Don't start scanning yet — I want to review settings first."
* "Set up tracking for a French SaaS — saas-fr.com in France French, tracking 'logiciel de gestion', 'outil de productivité', 'crm français'. DataForSEO, weekly."
* "Make a rank tracker for laravel.com in the US that includes subdomains (so docs.laravel.com counts as laravel.com). DataForSEO, desktop, weekly. Keywords: 'php framework', 'laravel tutorial', 'best php frameworks'."
* "Set up a rank tracker for a Chicago dental clinic — chicagosmiles.com, US English, DataForSEO, daily — but only run it between 9am and 5pm Chicago time."
* "Change the schedule on rank tracker #19 from weekly to daily."
* "Make rank tracker #19 run only on Mondays and Thursdays, between 08:00 and 12:00 in America/New\_York."
* "Remove the time window and day restrictions from rank tracker #22 so it can run at any time."
* "Rename rank tracker #22 to 'Moz.com — Q1 Tracking' and turn on include subdomains."
* "Switch rank tracker #23 from own-IP scraping to DataForSEO and bump priority to 2 for faster turnaround."
* "Disable pixel tracking on report #20." *(Will error if a snapshot has already captured pixel data — pixel settings are immutable after data is collected, by design.)*
* "Add 'cold brew beans' and 'nitro cold brew' to rank tracker #19 with a weight of 50."
* "In rank tracker #19, set 'buy seo tools' to a weight of 300 and make 'seo tools login' Track only."

</details>

<details>

<summary>🔑 Keyword Research</summary>

* "Check keyword metrics for: seo tools, rank tracker, keyword research, backlink checker"
* "Check keyword metrics for these keywords in Vietnam: công cụ seo, phân tích backlink"
* "What's the search volume and difficulty for 'best seo tools 2026'?"

</details>

<details>

<summary>🔗 Backlink Analysis</summary>

* "Show me the backlink profile for seoutils.app"
* "How have the backlinks for example.com changed over the past year? Show me a chart."
* "Which domains link to seoutils.app? Show the top 20 by authority rank."
* "Show me only dofollow backlinks for example.com"
* "Find backlinks from blog platforms pointing to example.com"
* "What's the spam score and domain rank for example.com's backlink profile?"
* "How many referring domains does example.com have? Break it down by dofollow vs nofollow."
* "What anchor texts are used most in backlinks to seoutils.app? Is there over-optimization?"
* "Who are the backlink competitors for seoutils.app? Which sites compete for the same link sources?"

</details>

<details>

<summary>🎯 Gap Analysis</summary>

* "Find keywords that ahrefs.com and semrush.com rank for but seoutils.app doesn't"
* "What content opportunities am I missing compared to my top 3 competitors?"
* "Find domains that link to ahrefs.com but not seoutils.app"
* "Show me the backlink gap between seoutils.app and its top competitors: semrush.com, moz.com"
* "Find high-volume keywords (1000+ searches) that competitors rank for in the US but I don't"

</details>

<details>

<summary>📊 Traffic Analytics</summary>

* "Show me the traffic overview for laravel.com"
* "What are the top organic keywords for laravel.com in the US?"
* "Who are the traffic competitors for seoutils.app?"
* "What are the top pages by traffic for laravel.com?"
* "Show me only informational keywords that laravel.com ranks for"
* "What keywords does laravel.com rank for in positions 1-3 with more than 1000 monthly searches?"
* "Show me the organic traffic trend for laravel.com over the past 5 years. Draw a chart."

</details>

<details>

<summary>🏘️ Demographics (US, UK, Australia &#x26; Canada)</summary>

* "Show me the demographics around my GMB report #7 business"
* "What's the population density and median income near Haidilao Hot Pot Bellevue?"
* "Compare the demographics data with my local rankings — do I rank better in high-income or low-income areas?"
* "Show me census data within 3 miles of coordinates 47.61, -122.20"
* "Show me demographics around my business in London / Sydney / Toronto"

</details>

<details>

<summary>🔎 GSC Insights &#x26; Mentions</summary>

* "Find keyword cannibalization issues for example.com in GSC"
* "Using my GSC data, what percentage of queries are branded vs non-branded for example.com?"
* "Show me my top trending queries in GSC this month vs last month"
* "What are my optimization opportunities in GSC — queries I rank for but don't mention in page titles?"
* "Show me GSC traffic by country for my site — which countries send the most clicks?"
* "Break down my GSC queries by position range: how many rank 1-3, 4-10, 11-20, and 21+?"
* "Which queries in GSC have zero mentions in page titles but high impressions?"
* "Show me additional traffic sources beyond web search in my Search Console data"

</details>

<details>

<summary>🔗 URL Indexing</summary>

* "How many of my URLs are indexed vs not indexed? Show the breakdown by coverage state."
* "Submit this URL for Google indexing: <https://example.com/new-page>"
* "Check the indexing status of <https://example.com/page> using the URL Inspection API"
* "Show me all URLs that have been crawled but not indexed — what's causing them to be rejected?"
* "Which directories on my site have the worst indexing rate?"
* "Find orphan pages — URLs with zero internal links that aren't indexed"
* "Show me the top 10 pages by internal inlink count and their indexing status"
* "Run an inspection scan for my site to update all URL statuses"
* "Start an internal link crawl for my site"
* "Which URLs have had their coverage state change in the last 7 days?"
* "Show me pages that went from 'Submitted and indexed' to something else recently"
* "Submit <https://example.com/updated-page> to IndexNow for Bing"

</details>

<details>

<summary>🪢 Internal Links</summary>

* "Show me the orphan pages on example.com and which pages could link to each one"
* "What would it cost to find links for my ten best priority targets?"
* "Find links for /coffee-grinders and /espresso-machines, and tell me when the run is done"
* "Show me the suggestions for /coffee-grinders — accept the ones with a confidence over 80% and reject the rest"
* "Change the link text of the second suggestion to 'burr grinder'"
* "Apply every accepted link to WordPress"
* "Set the maximum body links per page to 8 for example.com"

</details>

<details>

<summary>📐 Content Struct (Content Brief)</summary>

* "Create a content struct for 'keto meal plan' and tell me when the analysis is done"
* "Analyze the top Google results for 'best running shoes', 'trail running shoes', and 'running shoes for flat feet' — group them as 'Running Shoes Cluster'"
* "Create a content struct for 'best pho hanoi' targeting Vietnam, using the DataForSEO SERP API"
* "Create a content struct for 'coffee grinder' but exclude amazon.com and reddit.com from the competitor pages"
* "Generate an AI content outline for my 'keto meal plan' content struct using Claude"
* "Regenerate the outline for report #191 with GPT — focus the prompt on beginner-friendly content"
* "Show me the content brief for 'keto' — report #189"
* "Write a 2000-word article using the content outline from content struct report #191"
* "Show me the AI-generated outline and suggested meta title/description for report #193"
* "Which H2 headings appear most frequently across competitor pages for 'hot pot' in report #191?"
* "Write an SEO-optimized blog post following the content brief in report #189."
* "Compare the heading structure of the top 5 competitor pages for 'keto' in report #189"

</details>

<details>

<summary>🧩 SERP Clustering</summary>

* "Cluster these keywords by SERP similarity: keto diet, keto meal plan, keto recipes, low carb diet, keto for beginners — call the report 'Keto Cluster'"
* "Create a SERP clustering report for my keyword list using the DataForSEO SERP API with a similarity of 5 and the strict algorithm"
* "Cluster these German keywords for germany: hochzeit checkliste, hochzeitsplanung, hochzeit budget — and set target domain example.de so I can see where I rank per cluster"
* "Is my 'Keto Cluster' report done yet? If it failed, tell me why"
* "Add these new keywords to SERP clustering report #22 and distribute them into the existing clusters — reuse SERP data from the last 30 days"
* "Re-run report #22 from scratch with a stricter similarity of 6"
* "Show me the clusters in report #22 — cluster name, keyword count, and total search volume, biggest first"
* "Which keywords in report #22 ended up unclustered, and which clusters does my domain not rank in at all?"

</details>

<details>

<summary>📝 Text Analysis (NLP)</summary>

* "Run an NLP analysis on <https://example.com/blog/keto-guide> with TextRazor and show me the entities it covers"
* "Analyze these three competitor pages with Google NLP and tell me which entities all of them mention: \[urls]"
* "Here's my article draft — analyze it with Dandelion and list the entities with their Wikipedia links: \[pasted text]"
* "Analyze my German landing page example.de/preise with TextRazor in German — call the report 'Preise Entities'"
* "Is my 'Preise Entities' analysis finished? If it failed, tell me why"
* "Show me all my NLP analysis reports"
* "What are the top entities found in my TextRazor analysis report #19?"
* "Which entities appear most frequently across all items in report #21?"
* "Compare the entities found by GoogleNLP vs TextRazor for the same URLs"
* "Show me all entities with confidence score above 0.8 in report #20"
* "What topics were identified in my TextRazor report? Show them sorted by score"

</details>

<details>

<summary>📊 Bulk Analysis</summary>

* "Compare organic traffic for laravel.com, symfony.com, and codeigniter.com"
* "Show me the backlink profiles for seoutils.app, ahrefs.com, and semrush.com"
* "Which of these domains has the highest domain rank: moz.com, majestic.com, semrush.com?"
* "Analyze traffic and backlinks for my top 5 competitors"
* "Compare referring domains count for example.com vs example.org"

</details>

<details>

<summary>📍 NAP Finder</summary>

* "List all my NAP Finder reports"
* "Which domains have the most NAP citations for Monsoon Seattle?"
* "Show me all NAP citations found on yelp.com for my business"
* "What search terms found the most results in NAP Finder report #5?"
* "Find all NAP citations ranking in position 1-3 for monsoon seattle"
* "Compare NAP citations between report #5 and report #6 — which domains appear in both?"
* "Run a NAP Finder for Monsoon Seattle at 615 19th Avenue East, phone (206) 325-2111, using DataForSEO"
* "Find citation pages for Joe's Pizza — look up the address and phone from Google first, exclude joespizza.com"
* "Run a NAP citation check for my business with both phone formats: (222) 333-4444 and 222-333-4444"
* "Run a NAP Finder for my Toronto business in the Canadian locale, scanning the top 50 results per query"
* "Run a NAP Finder for Monsoon using my custom search term list, then tell me when it's done and which new domains it found compared to report #7"

</details>

<details>

<summary>🔬 Keyword Explorer</summary>

* "What are the keyword suggestions for 'keto diet' in the US?"
* "Show me Bing related keywords for 'coffee shops' sorted by search volume"
* "Find keyword suggestions for 'seo tools' with search volume over 1000 and keyword difficulty under 40"
* "Get keyword suggestions for 'best laptops' — only show commercial and transactional intent keywords"
* "Fetch autocomplete keywords for 'seo tools' from Google"
* "Show me the autocomplete keywords for 'keto' from both Google and Bing"
* "What's the search volume, keyword difficulty, and CPC for 'keto diet'?"

</details>

<details>

<summary>📋 Saved Keywords</summary>

* "Show me all my saved keyword lists"
* "Create a new keyword list called 'Competitor Keywords' for the US market"
* "Add these keywords to my 'Competitor Keywords' list: seo tools, keyword research, backlink checker"
* "Create a keyword list called 'Vietnam SEO' for Vietnam in Vietnamese"
* "Rename my 'Old Keywords' list to 'Archive - Q1 2026'"
* "Delete the 'Test Keywords' list"
* "How many keywords are in each of my saved keyword lists?"

</details>

<details>

<summary>📈 Organic Rank Tracker</summary>

* "Add these keywords to my rank tracker for example.com: seo audit, technical seo, on-page seo"
* "Take the top 20 keywords from the content gap report between example.com and competitor.com and add them to my rank tracker for example.com"
* "Pull the highest-converting GSC queries from the last 90 days that I'm not yet tracking, and add them to my example.com rank tracker"
* "Add 'black friday deals, cyber monday sale' to my shop.com tracker and rerun it right now"
* "Remove these keywords from my example.com rank tracker: outdated keyword, irrelevant term, typo'd kw"
* "Find every keyword in my shop.com tracker that hasn't ranked in the last 60 days and remove them"
* "Clean up my rank tracker — remove all keywords containing the word 'test'"
* "Force-refresh my rank tracker for example.com — I want fresh SERPs for every keyword"
* "Rerun the rank tracker for laravel.com"
* "Enable ranked-page HTML capture for my example.com tracker. Capture only my target domain and keep the files forever."
* "Enable ranked-page HTML capture for my shop.com tracker, include my tracked competitors, and keep captures for 90 days."
* "For my example.com rank tracker, compare the two captures around when <https://example.com/old-page> became lost. Summarize the main-content changes and tell me which are plausible contributors, without treating correlation as proof."
* "A new URL replaced my old ranking page. Compare the last capture of <https://example.com/old-page> with the first capture of <https://example.com/new-page>, show which tracked keywords moved, and clearly label it as a cross-page comparison."
* "Compare the full captured HTML before and after my page declined. Check title, canonical, robots directives, structured data, redirects, and template changes."

</details>

<details>

<summary>📉 GSC Rank Tracker</summary>

See [Try these prompts with the GSC Rank Tracker](#try-these-prompts-with-the-gsc-rank-tracker).

</details>

<details>

<summary>🌐 SERP Analysis</summary>

* "What's ranking for 'seo tools' in Google?"
* "Fetch SERP data for: rank tracker, keyword research tool, seo software"
* "Show me the top 10 Google results for 'best seo tools' in the US"
* "What pages are ranking for 'local seo' in the UK?"

</details>

<details>

<summary>🤖 LLM Rank Tracker</summary>

* "Show me all my LLM rank tracker reports"
* "Create an LLM rank tracker for my brand Ahrefs (variants: Ahrefs, ahrefs.com) tracking 'best seo tools' and 'best backlink checker' in ChatGPT and Google AI Overview, weekly"
* "Set up an LLM rank tracker for Hasiru Farms in India tracking 'organic vegetables bangalore' on Google AI Overview"
* "Create an LLM rank tracker for my brand across all four AI engines, on-demand only — don't run it yet, I want to review it first"
* "Run my Ahrefs LLM rank tracker now"
* "How is my brand mentioned across AI engines like ChatGPT and Google AI Overview?"
* "Which search terms trigger the most AI citations for my brand?"
* "Compare my LLM visibility across engines — ChatGPT vs ChatGPT Web Search vs Google AI Overview vs Google AI Mode"
* "Show me the trend of my brand mentions in AI responses over the last month"

</details>

<details>

<summary>🔭 AI Visibility</summary>

* "List my AI Visibility explorations and their share of voice"
* "In my Ahrefs exploration, what is my share of voice on ChatGPT compared with Google AI Overviews?"
* "Where do my competitors win in AI answers and I don't? Show me the top prompts where Semrush is named and Ahrefs isn't"
* "Which pages get cited in AI answers for Semrush but not for us?"
* "Create an AI Visibility exploration for ahrefs.com against semrush.com and moz.com in the United States, then tell me what the first load costs"
* "Refresh my Ahrefs exploration — quote the price first and wait for my OK"
* "Suggest competitors for notion.so in AI answers, and tell me the price before you look"
* "Write me a one-page client summary of my Ahrefs exploration: share of voice, the biggest gaps and the top cited domains"
* "Build a one-page visual dashboard of my Ahrefs AI Visibility exploration as an artifact: share of voice on Google AI Overviews vs ChatGPT, the head-to-head against each competitor (they win / both / you win) as a chart, the trend since the first month, and three key takeaways at the bottom. Use only cached data, don't spend anything"
* "Make a sleek battle card artifact for Ahrefs vs Semrush in AI answers from my AI Visibility data: who wins on each AI platform, by how much, and one line on why it matters. Big numbers, minimal text, cached data only"

</details>

<details>

<summary>⭐ Review Fetcher</summary>

* "Start tracking the Google reviews for Haidilao Hot Pot in Bellevue, WA — pull the 300 most recent reviews"
* "Track the reviews of this business: <https://maps.app.goo.gl/AbC123> — start with the 100 latest"
* "Add my dental clinic to the Review Fetcher but don't fetch anything yet — I'll run it manually later"
* "Set up review tracking for my restaurant in Germany with reviews translated to German"
* "Fetch the latest reviews for my Haidilao review tracker and tell me how many new ones came in"
* "Which of my reviews have no owner response yet? List the worst-rated ones first"
* "Did any of my Google reviews go missing since the last check? Show me the removed ones"
* "Summarize the themes in my 1-star and 2-star reviews from the latest snapshot"
* "Compare my star-rating breakdown between the latest snapshot and the previous one"

</details>

<details>

<summary>📄 Log Analysis</summary>

* "Show me all my log analysis reports"
* "Which pages get the most Googlebot crawls in my latest log analysis?"
* "Show me pages with 404 errors that Googlebot is trying to crawl"
* "What's the crawl frequency breakdown by HTTP status code?"

</details>

<details>

<summary>🤖 AI Log Analysis (AEO / GEO)</summary>

* "Is GPTBot violating my robots.txt in my latest log analysis report?"
* "Which AI bots are ignoring my Disallow rules — filter to violations > 0"
* "Which pages are Perplexity and ChatGPT-User fetching most this month?"
* "What questions are AI engines asking about my site? Group by extracted\_query"
* "How is AI traffic trending vs search traffic over the last 30 days?"
* "Which pages has Googlebot crawled recently but AI bots haven't visited in over a week?"
* "What's the error rate per AI bot — which bots are getting 4xx/5xx responses most?"

</details>

<details>

<summary>🧪 SEO Tests</summary>

* "Show me all my SEO tests and their current status"
* "How is my SEO test #5 performing — are clicks and impressions improving?"
* "Compare the before and after metrics for my latest completed SEO test"
* "Create a time-based SEO test on example.com starting today: hypothesis is rewriting the H1 on /blog/seo-guide will improve CTR. Change implemented date is today."
* "Create a 50/50 split test on shop.example.com comparing /products/a, /products/b (control) vs /products/c, /products/d (variant), starting next Monday"
* "Create a URL switch test on example.com alternating /pricing with /pricing-v2 every 7 days, starting today, ending in 60 days"
* "Update SEO test #7 — extend the end date to 2026-08-01 and update the hypothesis to mention the new schema markup"
* "Update test #3 to clear the end date so it runs indefinitely"

</details>

<details>

<summary>📧 Send Email</summary>

* "Send an email to <client@example.com> with subject 'Weekly SEO Report' and a summary of this week's ranking changes"
* "Email me the keyword cannibalization analysis for my site"
* "Send the content brief for 'keto diet' to my team at <team@example.com>"
* "Compose and send an email to <client@example.com> with the top 10 ranking improvements this month"

</details>

<details>

<summary>⚡ Automations</summary>

* "Show me all my automations"
* "What trigger types and action types are available for automations?"
* "Create an automation that exports a PDF report when my organic rank tracker snapshot completes"
* "Create an automation that runs when a content struct outline is generated. It should: 1) Export the outline as markdown to my Downloads folder, 2) Send an email to <client@example.com> with subject 'New Content Brief: \[keyword name]' and body showing the meta title, meta description, and number of headings, with the markdown file attached, 3) Send a GET webhook to <https://n8n.example.com/webhook/content-brief>"
* "Set up an automation to send an email with the rank tracker PDF attached when a snapshot finishes"
* "Create a webhook automation that posts rank tracker data to my n8n workflow when a snapshot completes"
* "Pause automation #1"
* "Delete the 'Test' automation"

</details>

<details>

<summary>🔬 Keyword Insights</summary>

* "Show me the keyword insight summary for my example.com rank tracker report"
* "Which keywords are trending up in my rank tracker report #20?"
* "Are any of my keywords pogo sticking or flickering? Explain what that means."
* "Show me the insight history — which keywords recently became unstable?"
* "How many of my keywords have enough data for trend analysis?"

</details>

<details>

<summary>📈 Rankings + GA4 Conversions (SEO Utils exclusive)</summary>

These prompts combine ranking data with Google Analytics 4 conversion metrics — something no standalone GA4 or rank tracker tool can do on its own. Note: this shows **correlation** (keyword ranking changes on pages that also saw conversion changes), not direct causation.

* "Show me keywords that improved in ranking on pages that also saw increased conversions. I want to see the position change alongside the page's conversion count."
* "Show me pages that generated conversions from organic search, and for each page, show me which keywords rank on that page and their current position."
* "Which pages generate the most organic revenue in GA4, and what keywords am I tracking on those pages?"
* "Are any of my pogo-sticking or flickering keywords on pages that generate conversions? These pages need stabilization first."
* "Give me a complete SEO health report for example.com: how many keywords are trending up vs down, which have unstable rankings, which pages have the most conversions, and what's my total organic revenue from GA4."

</details>

<details>

<summary>🗂️ Workspaces</summary>

* "List my workspaces"
* "Create a new workspace called Client A"
* "Create a workspace named E-commerce Projects with logo <https://example.com/logo.png>"
* "Rename workspace 3 to Personal Sites"
* "Update the Side Projects workspace — clear the logo"
* "Which workspace am I in right now? Switch me to Client A and show all the rank tracker reports in that workspace."
* "In the Client B workspace, create an organic rank tracker for clientb.com with the keywords from my 'Client B' saved list."
* "List the saved keyword lists in the Client A workspace without switching my workspace."

</details>

<details>

<summary>📝 Client &#x26; Comprehensive Reports</summary>

* "Generate a professional, client-ready SEO report for example.com for the last 30 days. Use clear, non-technical language suitable for stakeholders."
* "Create a comprehensive SEO health report for example.com. Include: GSC performance summary, top queries, optimization opportunities, cannibalization issues, and a weekly clicks trend chart."
* "Give me a complete SEO & backlink report for example.com — include traffic overview, top keywords, top pages, top competitors, backlink profile, and combined trends. Save it as an interactive HTML dashboard."

</details>

## Workspaces

If you use multiple workspaces in SEO Utils, the MCP server defaults to your currently active workspace. You can ask the AI to list, switch, create, or rename workspaces:

> "List my workspaces"

> "Switch to the Client Projects workspace"

> "Create a new workspace called Client A"

> "Rename workspace 3 to E-commerce Projects"

> "Update my Personal workspace — change the logo to <https://example.com/logo.png>"

After switching, all subsequent queries will be scoped to that workspace. New workspaces are **not** made active automatically — switch to them with `set_workspace` (or in the workspace switcher in the app). Workspace deletion is only available in the desktop app and is blocked if the workspace still contains any data.

### Working Across Client Workspaces

A switch lasts only until your AI app reconnects to SEO Utils. Apps reconnect when they restart, and remote connections can reconnect on their own. After a reconnect, the AI is back in the workspace that is active in the desktop app.

If you work across several client workspaces, choose the workspace in a way that survives reconnects:

| Way to choose                     | Example                                                           | How long it lasts                                       |
| --------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------- |
| Name the workspace in the request | "Create a rank tracker for example.com in the Client A workspace" | That request only                                       |
| Switch the workspace              | "Switch to the Client A workspace"                                | Until the AI app reconnects                             |
| Set a workspace on the connection | The `X-SEO-Utils-Workspace` header (see below)                    | Every request on that connection, also after reconnects |

When more than one applies, the first row in the table wins. When none applies, the AI uses the workspace that is active in the desktop app.

{% hint style="warning" %}
If the chosen workspace does not exist (for example, it was deleted), SEO Utils refuses the request and runs nothing. It never falls back to another workspace. Choose an existing workspace and ask again.
{% endhint %}

{% hint style="info" %}
Naming a workspace in a request and the connection header need SEO Utils versions after 2.7.0.
{% endhint %}

<details>

<summary>Set a workspace on the connection</summary>

Use this when one AI connection always works for one client, for example an agent per client on a server.

1. Find the workspace ID: ask the AI "List my workspaces".
2. Add the header `X-SEO-Utils-Workspace: <workspace ID>` to the connection, next to the `Authorization` header. For example, in Claude Code:

```bash
claude mcp add --transport http seo-utils-client-a http://localhost:19515/mcp \
  --header "Authorization: Bearer YOUR_TOKEN_HERE" \
  --header "X-SEO-Utils-Workspace: 12"
```

3. Add one connection per client, each with its own workspace ID.

Only apps that connect by URL (HTTP) can send a header. The **Connect Claude Desktop** connection and other local (stdio) connections cannot: with those, name the workspace in each request.

</details>

## Data Accuracy

The MCP server is designed to return the same numbers you see in the app. Behind the scenes, it automatically handles:

* **Timezone conversion** — Google Search Console uses Pacific Time, while other tools use your server's timezone. The MCP applies the correct offsets automatically.
* **Default filters** — Filters like `search_type = 'web'` for GSC data are applied automatically. You don't need to specify them.
* **Smart table selection** — When you ask about total clicks over time, the MCP uses the aggregate table (accurate totals). When you ask about specific queries, it uses the query-level table. Same logic as the app.
* **Rank tracker specifics** — NULL positions correctly handled as "not ranking," local pack results prioritized over organic, and average rank calculations match the app exactly.

You just ask your question in plain English — the MCP handles all the complexity.

## Security

| Aspect             | Detail                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Network**        | Server binds to `127.0.0.1` only — not accessible from the internet                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| **Authentication** | Bearer token required for all connections                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| **Data access**    | SQL queries are read-only. A small set of write tools can: create/update/delete saved keyword lists, add keywords to rank tracker reports, create LLM rank tracker reports and review fetches, queue tracker and review-fetch runs, run N.A.P Finder citation searches, create content structs and generate AI content outlines, create and run SERP clustering reports, run NLP text analyses, create/update workspaces, delete GMB rank tracker reports, manage automations and GMB report groups, and review, apply and revert internal links on your WordPress site |
| **Query safety**   | Only SELECT statements allowed, auto-limited to 1,000 rows                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| **Token storage**  | Auth token file has `0600` permissions (owner-read only)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| **Token rotation** | Rotate the auth token anytime from Settings — the old token stops working immediately, no restart needed                                                                                                                                                                                                                                                                                                                                                                                                                                                                |

{% hint style="success" %}
Your SEO data stays on your machine. The MCP server runs locally and the AI connects to it directly — no data is sent to any third-party server.
{% endhint %}

### Rotating the Auth Token

If your token was exposed — shared in a screenshot, a screen recording, or a config file — rotate it to generate a new one and lock out anyone still holding the old token.

{% stepper %}
{% step %}

#### Open the MCP Server Settings

Go to **Settings → Services** and scroll to the **MCP Server (AI Integration)** section. The **Rotate auth token** option appears while the server is running.
{% endstep %}

{% step %}

#### Click "Rotate token"

A confirmation dialog explains the impact: the current token is invalidated immediately, and apps connected by URL with the token, and Claude Desktop set up by an earlier SEO Utils version, lose access until you update them. Click **"Rotate"** to confirm.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fuf2k3NpdiKtUBlBYPNMI%2FXnapper-2026-09-28-18.17.32.png?alt=media&amp;token=34cd468d-56d8-41a1-82ee-68a3c691e70b" alt=""><figcaption><p>Rotate token in the MCP Server settings</p></figcaption></figure>
{% endstep %}

{% step %}

#### Reconnect Your AI Clients

The new token takes effect instantly — no restart of SEO Utils needed.

* **Apps added with a button or command in Connect an AI app** (Claude Desktop, Claude Code, Codex, Cursor, VS Code, OpenClaw, Grok Build, Antigravity, Perplexity) — nothing to do: they read the current token from SEO Utils
* **Apps connected by URL with the token** (n8n, Make, claude.ai, other HTTP clients) — copy the new token from **Connect an AI app → Other MCP apps** and replace the old one
* **Connections made with SEO Utils 2.5.0 or earlier** — click **Connect** again in **Connect an AI app**
  {% endstep %}
  {% endstepper %}

{% hint style="warning" %}
Rotation cannot be undone. Any client still configured with the old token — including automations on n8n, Make.com, or a VPS — will get authentication errors until you update it with the new token.
{% endhint %}

## Frequently Asked Questions

<details>

<summary>Is this self-hosted?</summary>

Yes! The MCP server runs entirely inside the SEO Utils app on your own machine. Your data stays local — nothing is sent to any third-party server. It works on macOS, Windows, and Linux (including VPS).

</details>

<details>

<summary>What about security? Is my desktop accessible from the internet?</summary>

No. The MCP server binds to `127.0.0.1` (localhost) only — it is **not** accessible from the internet. Only applications running on your own machine can connect to it, and they need a valid Bearer token to authenticate. Your data never leaves your computer.

</details>

<details>

<summary>Can I run this on a VPS for 24/7 automations?</summary>

Yes! You can install SEO Utils on a VPS (Linux is supported) and keep it running 24/7. This is great for automations with n8n, Make, etc. — they won't fail when your local machine is turned off. If you need external access from the internet, put SEO Utils behind a reverse proxy (like Nginx) with HTTPS. The built-in Bearer token auth ensures only authorized clients can connect.

</details>

<details>

<summary>Which AI clients are supported?</summary>

Any MCP-compatible client works, including:

* **Claude Desktop / Cowork (desktop)** — one click (local connection)
* **Claude Code** — one click or one command (local connection)
* **OpenAI Codex (ChatGPT desktop app, CLI, IDE extension)** — one click or one command (local connection, shared `config.toml`)
* **Cursor** and **VS Code (GitHub Copilot)** — one click (local connection)
* **OpenClaw**, **Grok Build** — one command (local connection)
* **Google Antigravity** — paste a config (local connection)
* **Perplexity (Mac)** — paste a command (macOS only, paid plan)
* **ChatGPT desktop app** — one click, through **Connect Codex** (local connection)
* **n8n, Make** — via HTTP with the auth token (requires a public HTTPS URL, or n8n on the same machine)
* **Claude Web (claude.ai), ChatGPT on the web, Grok (grok.com), Gemini app** — from anywhere, through Remote Access ([Connect AI Apps From Anywhere](/guide/mcp-server/connect-ai-apps-from-anywhere))
* **Any MCP client** — the standard MCP protocol, as a local command (stdio) or over HTTP

None of the local connections need Node.js. See [Connecting to AI Assistants](#connecting-to-ai-assistants).

</details>

<details>

<summary>Can the AI modify or delete my data?</summary>

SQL queries are strictly **read-only** — only `SELECT` statements are allowed. However, a small set of action tools can write on your behalf: Saved Keywords tools (create/rename/delete lists, add/remove keywords), Organic Rank Tracker tools (create/update reports, add or remove keywords, queue a tracker run — which consumes DataForSEO credits; removing a keyword also deletes its historical positions and insights), LLM Rank Tracker tools (create reports, queue a snapshot run — also consumes DataForSEO credits), Review Fetcher tools (create a review fetch, queue a fetch run — also consumes DataForSEO credits), Content Struct tools (create reports — consumes DataForSEO credits when scraping via the SERP API — and generate AI outlines, which spend your configured AI provider's credits), SERP Clustering tools (create reports and queue clustering runs — scraping and keyword metrics consume DataForSEO credits when it is the chosen method; adding keywords to an existing report is part of a run), GSC Rank Tracker tools (create trackers, add keywords and rules, set target pages, archive items — free, as they read Search Console; asking why a keyword moved spends your AI provider's credit), Workspace tools (create or rename workspaces), GMB report groups (create/delete), GMB rank tracker reports (delete one or many — permanent: it also removes their keywords, grid, snapshots and ranking history), Automations (create/update/delete), Internal Links (run Find links, which spends TypeSafe and embedding credit; review suggestions; change the rules; apply or revert links on your live WordPress site), and AI Visibility (create, edit and delete explorations; start or stop an Overview load and load lists that are not loaded yet, which consume DataForSEO credits, or your rental credits, only at the price you agreed to). Workspace deletion is intentionally *not* exposed over MCP — that operation lives in the desktop app. Everything else (GSC, backlinks, snapshots, settings) cannot be modified by the AI.

</details>

<details>

<summary>The AI uses the wrong tool for GSC queries</summary>

When asking about your own site's search performance (cannibalization, trending queries, weak pages, etc.), include **"in GSC"** or **"from my Search Console data"** in your prompt. Without this hint, the AI may fetch third-party estimated data from DataForSEO instead of querying your actual Google Search Console data stored locally.

**Example:** Instead of "Find cannibalization issues for example.com", say "Find cannibalization issues for example.com **in GSC**".

</details>

## Troubleshooting

{% hint style="info" %}
Problems with setting up SEO Utils with your AI app, the Google Cloud setup, or an AI app that can't see SEO Utils are in [Set Up SEO Utils → Troubleshooting](/guide/set-up-seo-utils#troubleshooting).
{% endhint %}

<details>

<summary>MCP server won't start or moved to another port</summary>

Make sure you have a valid license key. **Settings → Services → MCP Server** shows the state in its badge (**Running (port …)**, **Stopped** or **Not started**) and, when something is wrong, an alert:

* **The MCP server did not start**: the alert says why, for example that the port is taken by another program or kept for Remote Access. Pick another number in **Port**, click **Save port**, and switch **Enable MCP Server** on again
* **The MCP server moved to port …**: the saved port was taken, so SEO Utils picked a free one and saved it. Apps you added with a **Connect** button follow automatically. Only an app you connected by URL needs the new address

**Test connection** on the same card checks that the server answers.

</details>

<details>

<summary>Claude Desktop shows "Server disconnected" or "failed"</summary>

This usually means one of these:

1. **Installed with SEO Utils 2.5.0 or earlier** — that connection runs `mcp-remote` on Node.js, and it stops for good if Claude Desktop starts before SEO Utils. Click **"Connect Claude Desktop"** again with the current SEO Utils: the new connection needs no Node.js and survives either app starting first
2. **SEO Utils is not running** — Open the app and make sure the MCP server is enabled (status shows "Running")
3. **Didn't restart Claude Desktop** — After installing, you must fully quit and reopen Claude Desktop

</details>

<details>

<summary>Claude's custom connector can't use http://localhost</summary>

Claude's custom connectors (**Customize → Connectors**) run on Anthropic's servers, not on your computer, so they can't reach `localhost` at all, whatever the URL scheme.

**Use "Connect Claude Desktop" instead** — it connects locally, with no URL.

</details>

<details>

<summary>"Connect Claude Desktop" says success but nothing shows</summary>

Try these fixes in order:

**1. Fully kill Claude Desktop (most common fix on Windows)**

On Windows, closing the window doesn't quit Claude Desktop — it stays running in the background. Open **Task Manager** (Ctrl+Shift+Esc), find **Claude** in the process list, click **End Task**, then reopen Claude Desktop.

**2. Installed with SEO Utils 2.5.0 or earlier?**

That setup needs Node.js. Click **"Connect Claude Desktop"** again with the current SEO Utils, whose connection doesn't.

**3. Windows: config file in wrong location**

On Windows, Claude Desktop installs as an MSIX package and reads config from a different location than expected. Update to the latest SEO Utils version (v1.45+) which automatically detects the correct path.

If you're on an older version, manually create `claude_desktop_config.json` at:

```
C:\Users\<YourUsername>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\
```

instead of `%APPDATA%\Claude\`. Copy the local (stdio) config from SEO Utils **Settings → MCP Server → Connect an AI app → Other MCP apps**.

</details>

<details>

<summary>SyntaxError: Unexpected token { / Cannot find module 'node:path'</summary>

This comes from the `mcp-remote` connection that SEO Utils 2.5.0 and earlier installed: Claude Desktop ran it with an old Node.js, which is common with **nvm**.

**Fix:** click **"Connect Claude Desktop"** again with the current SEO Utils, then restart Claude Desktop. The new connection doesn't use Node.js.

</details>

<details>

<summary>The AI says "SEO Utils isn't running"</summary>

The AI app is connected, but SEO Utils is closed or its MCP server is off. Open SEO Utils and make sure **Settings → MCP Server** shows **Running**, then ask again. There's no need to restart the AI app.

If the AI says the connection dropped during a call and it "may or may not have completed", check the result in SEO Utils before asking it to run the same action again.

</details>

<details>

<summary>"Connect Claude Code" says the claude command wasn't found</summary>

SEO Utils looks for Claude Code's `claude` command in the usual install locations. If it's somewhere else, copy the command shown under the button and run it in a terminal.

</details>

<details>

<summary>"Connect Cursor" or "Connect VS Code" says it couldn't open the app</summary>

The app isn't installed, or your system doesn't know it can open its install links. Install or update Cursor or VS Code, open it once, then click the button again.

</details>

<details>

<summary>Get help from the AI with "Copy error"</summary>

When SEO Utils shows a red error, click **Copy error** on it before it disappears (it stays 10 seconds, and longer while your pointer is on it). It copies the error with the page you were on, the app version and the time, plus a request for help, ready to paste into your AI app.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7e4488d29bf6632caa803f87f857a280d9c418ab%2Fmcp-copy-error-toast.png?alt=media" alt=""><figcaption><p>An error toast with the Copy error button</p></figcaption></figure>

If that AI app is connected to SEO Utils with MCP Access, the copied text also tells it to read the failed run's log and the list of recent failures in SEO Utils, so it sees what failed and why instead of guessing. You can also open a tool's own log with its **View log** button and paste it.

</details>

<details>

<summary>Queries return no data</summary>

Make sure you're in the correct workspace. Use the prompt "List my workspaces" to check which one is active, then switch if needed. A switch ends when your AI app reconnects; to stay in one workspace, see [Working Across Client Workspaces](#working-across-client-workspaces).

</details>

<details>

<summary>Does the auth token change when I restart SEO Utils?</summary>

No. The auth token is generated once and persists across restarts. You only need to set up the connection once — it will keep working after restarting SEO Utils or your computer.

The token only changes when you rotate it yourself via **Settings → MCP Server → Rotate token** (see [Rotating the Auth Token](#rotating-the-auth-token)). After a rotation, only apps connected by URL with the token need the new one.

</details>


# Connect AI Apps From Anywhere

Use Claude, ChatGPT, Claude Code, Codex, Cursor and other AI apps with your SEO Utils from anywhere, without being at your computer.

AI apps such as Claude, ChatGPT, Claude Code, Codex, Cursor, Perplexity, Grok and the Gemini app can use the SEO Utils on your computer from anywhere: your phone, a laptop on the road, or an app that runs in the cloud. The app reaches your computer through your [Remote Access](/guide/remote-access) address and signs in with your cloud account, so you decide what it may do.

{% hint style="info" %}
Your reports and keywords stay on your computer. The app asks your computer for what a question needs, through your Remote Access address. An AI app does not use a browser seat.
{% endhint %}

An app on the same computer as SEO Utils, such as Claude Code, Codex or Cursor, connects without Remote Access: see [MCP Server](/guide/mcp-server#connecting-to-ai-assistants). This guide is for apps that run in the cloud or on another computer.

## Before You Start

* **Remote Access is on** for the computer, with its plan active. See [Remote Access](/guide/remote-access).
* **MCP Access** (the MCP add-on) is active on your license. See [Setting Up the MCP Server](/guide/mcp-server#setting-up-the-mcp-server).
* **SEO Utils is open** and the computer is awake and online whenever the app uses it.
* **You are the owner of the computer.** Team members cannot connect AI apps yet.

## Connect an AI App

{% stepper %}
{% step %}

#### Allow AI apps

In SEO Utils, go to **Settings → Services → Remote Access** and find the **AI apps** section. Turn on **Allow AI apps over Remote Access**.

The switch is off by default. While it is off, every AI app is refused.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a52979e8a87c8673fa2f1dc39bef4a80f7fd269e%2Fremote-mcp-switch.png?alt=media" alt="The AI apps section of the Remote Access card"><figcaption><p>The Allow AI apps over Remote Access switch (1) and the Connected AI apps list (2), empty until you connect an app</p></figcaption></figure>
{% endstep %}

{% step %}

#### Copy your address

Go to **Settings → Services → MCP Server**. Under **Connect an AI app**, choose your app (1), select **From anywhere (Remote Access)** (2) and copy the **Address** (3).

The address looks like `https://inst-….seoutils.app/mcp`. If you use your own domain, a menu lets you pick that address instead.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-6014ceed0ab4307ac824e56bf98a63d78a39f44c%2Fremote-mcp-claude-steps.png?alt=media" alt="Connect an AI app with the From anywhere tab selected and the address shown"><figcaption><p>The app picker (1), the From anywhere tab (2) and the address to copy (3), with the app's own steps below</p></figcaption></figure>

If the tab shows **To connect from anywhere, SEO Utils needs:** instead of the address, each missing item has a cross, the reason and a button that fixes it. Fix the crosses, then click **"Check again"**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-34ffbcc580f50f610891325d67b78f0acb828148%2Fremote-mcp-requirements.png?alt=media" alt="The list of what SEO Utils needs before an AI app can connect from anywhere"><figcaption><p>The From anywhere tab (1) when AI apps are not allowed yet: the cross (2) says what to turn on</p></figcaption></figure>
{% endstep %}

{% step %}

#### Add the address to your AI app

Add the address as a remote MCP server (some apps call it a connector). The steps for each app are [below](#add-seo-utils-to-your-ai-app).
{% endstep %}

{% step %}

#### Sign in and approve

The app opens a sign-in page on your cloud account. Sign in, choose what the app may do and in which workspaces, then click **"Allow"**. See [What You Approve](#what-you-approve).
{% endstep %}
{% endstepper %}

## Add SEO Utils to Your AI App

SEO Utils shows these same steps under the address, already filled in with yours.

{% tabs %}
{% tab title="Claude" %}
Works in Claude on the web, Claude Desktop, Cowork and the Claude mobile apps.

1. Open **Settings → Connectors → Add custom connector**.
2. Name it `SEO Utils`, paste the address as the remote MCP server URL, and click **"Add"**.
3. Click **"Connect"** and sign in on the page that opens.

On a Team or Enterprise plan, an owner of the Claude organization adds the connector first.
{% endtab %}

{% tab title="ChatGPT" %}

1. In ChatGPT on the web, open **Settings → Apps → Advanced settings** and turn on **Developer mode**.
2. In **Settings → Apps**, click **"Create"**. Name it `SEO Utils`, paste the address as the MCP server URL, choose **OAuth** for authentication, and create it.
3. Sign in on the page ChatGPT opens.

Developer mode needs a Plus, Pro, Business, Enterprise or Edu plan, and in a workspace an admin may have to turn it on. Some versions of ChatGPT call the menu **Apps & Connectors**.
{% endtab %}

{% tab title="Claude Code" %}
Run this in a terminal, with your address:

```bash
claude mcp add --transport http seo-utils https://inst-….seoutils.app/mcp
```

Then run `/mcp` in Claude Code, choose `seo-utils` and **Authenticate**. The sign-in page opens in your browser.
{% endtab %}

{% tab title="Codex" %}
Run this in a terminal, with your address. It adds SEO Utils and opens the sign-in page:

```bash
codex mcp add seo-utils --url https://inst-….seoutils.app/mcp
```

Run this one only if the sign-in page did not open or you did not finish signing in:

```bash
codex mcp login seo-utils
```

Codex stops any tool after 60 seconds. To allow longer, add `tool_timeout_sec = 900` under `[mcp_servers.seo-utils]` in `~/.codex/config.toml`.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-435eefb79a1407d2797990700c93f2286f9aa181%2Fremote-mcp-codex-steps.png?alt=media" alt="The Codex steps in Connect an AI app"><figcaption><p>The Codex steps: the command that adds SEO Utils (1) and the sign-in command to use only if needed (2)</p></figcaption></figure>
{% endtab %}

{% tab title="Cursor" %}
Add this to `~/.cursor/mcp.json`. If the file already lists servers, add the `seo-utils` entry inside `mcpServers`:

```json
{
  "mcpServers": {
    "seo-utils": {
      "url": "https://inst-….seoutils.app/mcp"
    }
  }
}
```

Then open **Cursor Settings → MCP**. Cursor asks you to sign in to `seo-utils`.
{% endtab %}

{% tab title="Perplexity" %}

1. Open **Settings → Connectors → Custom connector** and choose **Remote**.
2. Name it `SEO Utils`, paste the address as the MCP server URL, choose **OAuth**, and add it.
3. Sign in on the page Perplexity opens.

Custom connectors need a Pro, Max or Enterprise plan. On an organization plan, an admin turns them on first.
{% endtab %}

{% tab title="Grok" %}

1. In Grok on the web, open `grok.com/connectors`, click **New Connector** and choose **Custom**.
2. Paste the address as the MCP server URL, then sign in on the page Grok opens.

Custom connectors need a paid Grok plan. On Grok Business or Enterprise, an admin adds the connector first.
{% endtab %}

{% tab title="Gemini app" %}

1. In Gemini on the web, open **Settings & help → Connected apps** and add a custom app.
2. Paste the address as its server URL, then sign in on the page Gemini opens.

Only some Gemini plans offer custom apps, and only with a personal Google account.
{% endtab %}

{% tab title="Other apps" %}
In the app, add a remote MCP server (some apps call it a connector) with your address. When the app asks you to sign in, your cloud account opens its sign-in page.
{% endtab %}
{% endtabs %}

## What You Approve

The sign-in page names the app, the computer and the address, then asks two questions.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-9016b4f4514149b218d8db92d1c29f2dd341338f%2Fremote-mcp-consent.png?alt=media" alt="The consent page on the cloud account" width="520"><figcaption><p>The consent page: workspaces (1), access level (2) and Allow (3)</p></figcaption></figure>

**Workspaces.** Choose **All workspaces, including ones you create later**, or **Only the workspaces I choose**. An app never sees a workspace outside its choice.

**Access level.** The page opens on the level the app asked for, never on Full.

| Level                | What the app can do                                                                                     |
| -------------------- | ------------------------------------------------------------------------------------------------------- |
| **Read only**        | Read your data in SEO Utils. It changes nothing and spends nothing.                                     |
| **Read and look up** | Also look things up: it can spend your DataForSEO credits and call Google with your keys.               |
| **Full**             | Also create, change, delete and run your reports, submit URLs for indexing, and spend credits doing so. |

{% hint style="info" %}
**Verified app** marks the apps SEO Utils recognises, such as Claude, ChatGPT and Cursor. For any other app, check the **Sign-in goes to** line. An unrecognised app that finishes the sign-in on your own computer shows a warning: continue only if you started it yourself.
{% endhint %}

To change an app's level or workspaces later, disconnect it and connect it again.

## What the AI App Can Do

* **Read your results.** Reports from the rank trackers, Google Business, LLM and AI Visibility, N.A.P Finder, SERP Clustering, Search Console and more, as on their pages in SEO Utils.
* **Look things up** (Read and look up and Full). Backlinks, traffic, SERP data and similar live lookups, with your DataForSEO credits and Google keys.
* **Change things** (Full). Create, update, delete and run reports, manage saved keyword lists, and submit URLs for indexing.
* **Work in the workspaces you chose.** When it has more than one, name the workspace in your prompt, such as "in Harbor & Pine Coffee".
* **Start runs and follow them.** A run the app starts answers with a job number, which the app uses to check progress. In the run log it reads "Run started from *app name* via AI-app access".

The app sees a short list of tools (search, describe, read, look up and write) and finds the exact action it needs through search.

Some things stay on the desktop:

* Sending email
* Automations
* Setup steps that open SEO Utils windows, and the Google Cloud setup
* Creating or renaming workspaces
* The paid check of keyword metrics for a list of keywords (reading metrics already stored works)
* The database (SQL) tools of the local MCP server

## Seeing and Disconnecting Apps

In SEO Utils, **Settings → Services → Remote Access → AI apps → Connected AI apps** lists each app with its access level and workspaces.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-a9c25f064ba2110b68ffb887c9f798e5b0b61cc3%2Fremote-mcp-connected-apps.png?alt=media" alt="The Connected AI apps list on the Remote Access card"><figcaption><p>The connected apps (1) and Manage on the hub (2)</p></figcaption></figure>

To disconnect an app, click **"Manage on the hub"**. The **AI apps** page of your cloud account at [app.seoutils.app](https://app.seoutils.app), under **Remote Access**, also shows the computer and when each app was last used. Click **"Disconnect"** on the app's row and confirm with **"Yes"**. The computer refuses the app within a minute, usually within seconds.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-57b0c6ac5d657263a22dbf40cd87010598a1d473%2Fremote-mcp-hub-ai-apps.png?alt=media" alt="The AI apps page on the cloud account"><figcaption><p>The AI apps page: the connected apps (1) and Disconnect (2)</p></figcaption></figure>

To stop every app at once, turn off **Allow AI apps over Remote Access**. Each app is refused from its next request. The connections stay, so turning the switch on again needs no new sign-in.

## When the Computer or the Switch Is Off

* **The computer is off, asleep or SEO Utils is closed.** The app gets the answer "SEO Utils on *your address* is offline: the computer running it is asleep, closed or disconnected. Start SEO Utils and try again." Signing in still works, so you can connect an app while the computer is off.
* **The switch is off.** The app shows "AI apps are turned off in SEO Utils → Remote Access." Turn the switch on and the app works again.

{% hint style="info" %}
With your own domain, an app can sign in only while SEO Utils is open on the computer. On your `inst-….seoutils.app` address it can sign in at any time.
{% endhint %}

## Known Limits

* **A run that has started keeps going.** A job an AI app started that is already running when you disconnect the app, or turn AI apps off, keeps going until it ends, and what it paid for is kept in the report. A job that has not started yet does not start: it stops with "stopped: the AI app's access was revoked". Runs started by team members behave the same way when their access ends.
* **Very long calls.** Some apps stop waiting for a tool after about a minute (see the Codex setting above). Runs that go to the background answer at once, so they are not affected.

## Related Guides

{% content-ref url="/pages/eWCdj5l65f7zEfzXnaBt" %}
[MCP Server (AI Integration)](/guide/mcp-server)
{% endcontent-ref %}

{% content-ref url="/pages/5g6NABzsFmX50yVSKbWU" %}
[Remote Access](/guide/remote-access)
{% endcontent-ref %}


# SMTP Credentials

### What Are SMTP Credentials?

SMTP credentials allow SEO Utils to send automated emails through your email server. This is essential for automating report delivery to clients and team members.

### Setting Up SMTP Credentials

To configure email sending capabilities, navigate to **SMTP** in the left sidebar and click **Add Credential**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ea019aa98663c32743be9766002f1a7d88a323c1%2FXnapper-2025-09-17-22.44.40.png?alt=media" alt=""><figcaption><p>SMTP Credentials management interface</p></figcaption></figure>

#### Configuration Fields

Fill in the following settings based on your email provider:

**Basic Settings:**

* **Credential Name**: A friendly name to identify this configuration (e.g., "Main Gmail Account")
* **Default Credential**: Toggle on to use this as the default for all email automations

**Server Settings:**

* **SMTP Host**: Your email server address (see provider settings below)
* **Port**: Usually `587` for TLS or `465` for SSL
* **Encryption**: Select TLS/STARTTLS (recommended) or SSL

**Authentication:**

* **Username**: Your email address or username
* **Password**: Your email password or app-specific password

{% hint style="warning" %}
**Gmail Users**: You must use an [App Password](https://support.google.com/accounts/answer/185833) instead of your regular password. Enable 2-factor authentication first, then generate an app password.
{% endhint %}

**Sender Information:**

* **From Email**: The email address that appears as sender
* **From Name**: Optional display name (e.g., "SEO Reports")

#### Testing Your Configuration

Before saving, always test your SMTP settings:

1. Enter a **Test Email Address** where you can receive mail
2. Click **Send Test Email**
3. Check your inbox for the test message
4. If successful, click **Create Credential**

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-4c0af70fb0825567f7ccacd4f8ec2fa1955e77c5%2FXnapper-2025-09-17-22.51.23.png?alt=media" alt=""><figcaption><p>Test your SMTP configuration before saving</p></figcaption></figure>

### Common Email Provider Settings

#### Gmail

* Host: `smtp.gmail.com`
* Port: `587`
* Encryption: `TLS`
* Username: Your Gmail address
* Password: [App Password](https://myaccount.google.com/apppasswords) (not regular password)

#### Microsoft 365/Outlook

* Host: `smtp.office365.com`
* Port: `587`
* Encryption: `TLS`
* Username: Your email address
* Password: Your password

#### SendGrid

* Host: `smtp.sendgrid.net`
* Port: `587` (or `465` for SSL, `2525` as alternative)
* Encryption: `TLS`
* Username: `apikey` (literal string, not your username)
* Password: Your SendGrid API key

#### Mailgun

* Host: `smtp.mailgun.org`
* Port: `587` (or `2525` as alternative)
* Encryption: `TLS`
* Username: Your Mailgun email address
* Password: Your Mailgun API key

{% hint style="info" %}
**Tip**: Port `2525` is an alternative port offered by SendGrid and Mailgun if your ISP blocks standard ports. It works identically to port 587 with TLS encryption.
{% endhint %}

#### Custom/Business Email

Contact your IT administrator or hosting provider for:

* SMTP server address
* Port number
* Authentication requirements
* Encryption method

### Using SMTP in Automations

Once configured, your SMTP credentials are automatically available in the Automations tool. When creating an email action, simply:

1. Select **Send Email** as the action type
2. The system will use your default SMTP credential
3. Configure recipient, subject, and message content
4. Add attachments using variables like `{{pdf_export_path}}`

See the [Automations guide](/guide/automations) for detailed examples of email automation workflows.

### Troubleshooting

**Test email fails:**

* Verify your username and password are correct
* For Gmail, ensure you're using an App Password
* For SendGrid, use `apikey` as username (not your email)
* Check if your email provider requires specific security settings
* Try alternative ports (2525 for Mailgun/SendGrid if 587 is blocked)

**Emails not sending in automations:**

* Confirm the SMTP credential is marked as default
* Check automation execution logs for specific error messages
* Verify recipient email addresses are valid

**Connection timeout:**

* Your firewall or ISP may be blocking the SMTP port
* Try port 2525 as an alternative for SendGrid/Mailgun
* Try using port 465 with SSL encryption instead of 587/TLS


# Privacy Policy

Last Updated: November, 20th 2023

**1. Introduction**

* This Privacy Policy applies to all information collected through our desktop application, SEO Utils ("Service"), and any related services, sales, marketing, or events.

**2. Information We Collect**

* We may collect personal information that you voluntarily provide to us when registering to use our Service, expressing an interest in obtaining information about us or our products and services, or otherwise contacting us.
* The personal information we collect depends on the context of your interactions with us and the Service, the choices you make, and the features you use.

**3. How We Use Your Information**

* We use personal information collected via our Service for a variety of business purposes, such as:
  * To facilitate the creation and securing of your account on our Service.
  * To post testimonials with your consent.
  * To enforce our terms, conditions, and policies.
  * For other business purposes, such as data analysis, identifying usage trends, determining the effectiveness of our promotional campaigns, and to evaluate and improve our Service, products, marketing, and your experience.

**4. Sharing Your Information**

* We may share your information with our service providers, in connection with any business transfers, to comply with laws, to protect your rights, or with your consent.

**5. Cookies and Similar Technologies**

* We may use cookies and similar tracking technologies to access or store information.

**6. Data Security**

* We have implemented appropriate technical and organizational security measures designed to protect the security of any personal information we process.

**7. Data Retention**

* We will only retain your personal information for as long as necessary for the purposes set out in this Privacy Policy.

**8. Privacy Rights**

* Depending on your location, you may have rights under applicable data protection laws in relation to your personal data, such as the right to request access, correction, or deletion of your personal data.

**9. Policy Updates**

* We may update this Privacy Policy from time to time. The updated version will be indicated by an updated "Revised" date and the updated version will be effective as soon as it is accessible.

**10. Contact Us**

* If you have questions or comments about this policy, you may [email us](mailto:me@phuclh.com).


# Terms of Service

Last Updated: November, 9th 2026

**1. Acceptance of Terms**

* By downloading, accessing, or using SEO Utils, you agree to be bound by these Terms and Conditions ("Terms"). If you do not agree with these Terms, you must not use this application.

**2. Use of the Application**

* This application is intended for use in managing and improving the SEO of websites.
* Users must ensure that their use of the application complies with all applicable laws and regulations.
* The application should not be used for any unlawful purposes or in a way that violates the rights of others.

**3. Intellectual Property**

* All content, features, and functionality (including but not limited to all information, software, text, displays, images, and the design) are owned by SEO Utils or its licensors.

**4. User Obligations**

* Users must provide accurate and complete registration information and keep this information up to date.
* Users are responsible for maintaining the confidentiality of their license keys.
* Any unauthorized use of the application or breach of these Terms must be immediately reported to SEO Utils.

**5. Third-Party Services and API Keys**

* Many features of SEO Utils connect to third-party services that you choose, such as DataForSEO, Google Cloud (for example, the Natural Language API), OpenAI and other AI providers. You connect these services with your own accounts and your own API keys.
* Each third-party service is provided by its own company, under its own terms and prices. That company bills your account directly. SEO Utils does not receive these payments and cannot refund them.
* You are responsible for your API keys and for all usage and charges on your third-party accounts, including usage the application makes on your behalf, such as scheduled reports, automations and other automatic tasks. This includes keeping your keys secure, checking your usage, and setting budgets, quotas, spending limits and billing alerts with each provider.
* Any cost estimates the application shows are estimates only. The provider's own billing is the final record of what you are charged.
* SEO Utils is not liable for any charges, fees or other costs from third-party services, including charges caused by errors or defects in the application.
* This section does not cover credits you buy from SEO Utils, such as credits for a rented DataForSEO API key.

**6. Prohibited Activities**

* Users may not engage in activities that harm, disrupt, or otherwise negatively affect the operation of the application or the enjoyment of other users.
* Reverse engineering, decompiling, or disassembling the application is prohibited.
* Distributing, selling, or otherwise transferring your rights under these Terms to third parties is not allowed.

**7. Disclaimer of Warranties**

* SEO Utils is provided "as is" without any warranties, express or implied, including but not limited to implied warranties of merchantability or fitness for a particular purpose.

**8. Limitation of Liability**

* SEO Utils will not be liable for any indirect, incidental, special, consequential, or punitive damages arising out of or in connection with your access to or use of the application.

**9. Modifications to the Terms**

* SEO Utils reserves the right, at its sole discretion, to modify or replace these Terms at any time. If a revision is material, we will provide at least 30 days' notice prior to any new terms taking effect.

**10. Governing Law**

* These Terms shall be governed and construed in accordance with the laws of Washington, without regard to its conflict of law provisions.

**11. Contact Information**

* If you have any questions about these Terms, please contact us at [me@phuclh.com](/legal/terms-of-service).

***


