See where you rank on Google, and whether the AI Overview above you cites you

A rank tracker checks where your pages rank on Google for the keywords you choose and records how that moves over time. Linkeddit's also records, on every check, whether Google showed an AI Overview for the keyword and whether that Overview cited your domain as a source. Ranking fourth under an AI Overview that cites a competitor is a different situation from ranking fourth on a plain results page, and a rank number alone hides it.

Weekly, on Google in the United States, read from the first ten results. A site is due when its newest check is seven or more days old, and each keyword is checked at most once a day. A failed check writes nothing, so a timeout never shows up as not in the top 10. If the newest check is more than 14 days old, the page says the ranks are out of date.

Google does not show the same AI Overview every time, and may show none on a repeat of the same search, so read the AI Overview columns across several weeks rather than one row. Search Console's generative AI report counts your AI Overview impressions by page but has no query dimension and cannot see an Overview that skipped you, so the check records both per keyword.

With Search Console connected, the AI Overview impact card compares your queries that had an AI Overview with those that did not, using your own clicks before and after. It gives one of four plain verdicts, such as AI Overviews are taking clicks or Not enough data for a verdict yet, with the numbers and caveats beneath. It does not guess when the data is thin.

By shared results, not by similar wording. Each checked keyword has its top ten Google results stored, and keywords that share at least three of those results are grouped into one topic, named by a head keyword. Two phrasings Google answers with the same pages belong on one page of yours; two that Google answers differently usually need separate pages.

Striking distance means your best page ranks 11 to 20 for a topic, close enough that improving the page can reach page one. The catch: each check reads only the first ten results, so a page sitting at 11 to 20 is not visible to a top ten check and that topic reads Gap. Your Search Console positions fill in that range.

Add the page and the day the edit went live to the Watchlist. After 21 days plus Search Console's two day reporting delay, it compares two equal 21 day windows either side of the change for that exact page. It calls Improved or Declined only when clicks moved by at least 15 percent and at least 5 clicks, and Not enough data when either window has under 100 impressions. It reports an observed difference, not proof that the change caused it.

Search is included in the Compete plan at $60 a month, alongside Compete and Answer Radar. By default a site tracks up to 50 keywords and an account has 500 Google result checks a month. A keyword already checked in the last 7 days is answered from a shared store at no cost, every research run shows its cost before it starts, and the Watchlist uses no checks at all.

Yes. The Linkeddit MCP connector has five Search tools: search_visibility_get for ranks and AI Overview impact, search_tracked_update to add or remove keywords, search_research_run and search_research_get for topics and keyword maps, and search_competitors_get for the domains that beat you. Your assistant reads the data and decides what to write; Linkeddit does not write the page for you.

A rank tracker records where your pages appear on Google for the keywords you care about, on a schedule, so you can see movement over time instead of searching by hand. Teams use it to catch a drop early, to confirm a rewrite helped, and to see which competitor took a position. Linkeddit's Search also records the AI Overview on each check.

Open Search, press Add site, enter your domain and the competitors you rank against, then add keywords in Manage keywords: type them, upload a file, or press Add top Search Console queries. The next hourly run queues the first check, and every keyword is checked again weekly after that.

Google Search Console is free and reports your average position per query from Google's own data. What it does not give you is the rest of the results page: who holds position one, whether an AI Overview appeared, and which competitor pages outrank you. That is the part a rank tracker adds on top of Search Console.

No, rankings work from typed or uploaded keywords alone. Search Console adds three things: one click to track your top queries, the AI Overview impact verdict, and the Watchlist's before and after numbers. Without it, those features say they need a connection rather than showing empty numbers.

Add Linkeddit's read only service address as a user on your Search Console property inside Google, then press Check for properties in Linkeddit and pick the property. There is no Google login and Linkeddit stores no Google credential. Only properties on the site's own domain are offered.

Up to 50 per site by default. When an upload goes over, the drawer says how many did not fit. Removing a keyword frees its slot and keeps its history, and typing it again turns it back on.

A check is one look at Google's first page of results for one keyword. Each account has 500 checks a month by default. Tracking 50 keywords weekly uses about 200 a month, which leaves room for keyword research runs.

A keyword whose Google results were already checked in the last 7 days is answered from a shared store, so it does not draw on your allowance. Research run estimates list these as Free from recent checks before you start.

No. Setting up a site and adding or removing keywords is free; only the weekly checks draw on the monthly allowance. The connector tool search_tracked_update is free for the same reason: it runs no checks itself.

Add top Search Console queries leaves out queries that contain your brand terms, such as your brand or domain name, because ranking first for your own name is rarely worth tracking. You can still type a branded keyword yourself.

Yes. Search does not keep its own list of sites; a site is the Answer Radar project with the same domain, brand and competitors. Add it once and both products use it, so Google rankings and AI engine recommendations sit side by side.

The Compete plan at $60 a month, the only plan sold. It includes Compete, Answer Radar and Search, in the web app and through the MCP connector.

The checked keywords where your best page ranks inside those positions. Under Top 10 a line says whether that count went up, down or stayed the same this week, comparing each keyword's newest check with one at least seven days older.

None of your pages was among the first ten results on that check. It is a measured result, not a missing value. A keyword that has never been checked reads Not checked yet instead.

It was added after the site's last weekly check. It is picked up at the next one, when the site's newest result is a week old. A brand new site gets its first check from the next hourly run.

It compares the newest check with the one before: Up or Down by a number, No change, Entered top 10, Left top 10, or New when there is only one check so far.

Your best ranking page for that keyword, shown in the Our page column. Any subdomain of your domain counts as yours. When two or more of your pages rank for the same topic, the Topics view flags it as cannibalised.

The publisher at position one on the latest check, whoever it is, including you. It shows at a glance whether a keyword is held by a competitor, a large publisher or a marketplace.

Show history on a checked keyword lists up to eight weeks of ranks, oldest first. With a single check it says there is no history yet. Through the connector, search_visibility_get with view history can return up to 52 weeks.

Nothing is written. A timeout or blocked request never shows up as Not in top 10, so a failed check cannot look like a ranking loss. The keyword is tried again on a later run.

The banner appears when the site's newest check is more than 14 days old, and gives the date of the last check. Checks normally refresh weekly, so a stale banner means recent checks have not landed.

Not today. Every check is Google in the United States, and every number on the page says so with its date. Search Console fills in other countries for your own site.

Your own search is personalised by location, history and device, and results shift during the day. The tracker reads Google's United States results for each keyword once a week, which is comparable week to week even when it differs from your screen.

Yes, a .csv or .txt file of up to 1 MB, one keyword per line or in the first column. A header row such as keyword or query is ignored, repeats are dropped and keywords over 120 characters are left out. You see a preview before anything is added.

Yes. Download rankings CSV appears once there are ranks. For very long lists the file may hold only the first rows, and it says so in the file.

Yes. On a narrow screen the rankings table becomes cards that carry the same facts as the desktop columns.

Two ways that answer different questions. Search Console's generative AI performance report counts impressions of your links in AI Overviews and AI Mode, by page. A rank tracker that records the Overview on each check tells you, per keyword, whether an Overview appeared and whether it cited you.

No. The generative AI performance report groups impressions by page, country, date and device only; there is no query dimension. It also cannot show an Overview that appeared on your keyword without citing you, because that produces no impression for your site.

AI Overview shown counts tracked keywords whose latest check showed an Overview. AI Overview cites you counts those where the Overview's sources included your domain. Both carry a note that Overviews vary from run to run.

No. An Overview can cite a page that ranks low or not at all on the same results page, and skip the page in position one. That is why rank and citation are recorded as separate columns rather than one score.

As a sample. Google may show a different Overview, or none, on a repeat of the same search. Read the AI Overview columns across several weekly checks before concluding that a keyword has or lacks one.

Your own data can say, where industry averages cannot. With Search Console connected, the AI Overview impact card compares your clicks on keywords with an Overview against keywords without one, and gives one of four plain verdicts with the numbers and caveats beneath.

One of four plain statements, such as AI Overviews are taking clicks or Not enough data for a verdict yet. The verdict carries a version, so a change in method is visible, and the numbers it was drawn from are shown underneath.

The comparison needs Search Console connected and enough clicks on your tracked keywords to support a verdict. When either is missing it says so plainly rather than guessing a direction.

The rank checks record AI Overviews on the classic results page. Google AI Mode is measured by Answer Radar, which asks AI Mode your buying questions alongside ChatGPT, Gemini, Perplexity, Claude and AI Overviews and records who it recommends and cites.

Yes. Since 31 August 2026 Search Console has a Search generative AI setting that includes or excludes a site from AI Overviews and AI Mode. Excluding it also removes the impressions and clicks those features send. The usual nosnippet and max-snippet controls still apply too.

Grouping keywords by the pages Google returns for them rather than by how they are worded. If two keywords share enough of the same top results, Google treats them as one need, and one page of yours can target both. In Search, keywords that share at least three top ten results form one topic.

Because similar wording can hide different intent. Two phrases that read alike may return a guide for one and product pages for the other. The results page is Google's own answer to what each search means, so grouping by it matches how pages actually rank.

Your active tracked keywords and your top Search Console queries, expanded into related searches and People Also Ask questions, with brand terms dropped. A run covers 300 keywords by default.

Striking distance: your best rank is 11 to 20. Gap: a competitor is in the top 10 and you have no page in the top 20. Cannibalised: two or more of your pages rank. Protected: you rank 1 to 3. Hold: nothing is flagged.

Two or more of your own pages ranking for the same topic, which usually splits signals so neither ranks as well as one strong page would. A cannibalised topic lists Our competing pages so you can decide which to keep, merge or redirect.

A gap means a competitor holds a top ten position where you have no page in the top 20. Open the topic to see the competing pages, then decide whether an existing page can be extended or a new page is needed.

Each check reads only the first ten results, so a position from 11 to 20 is not recorded by the check and the topic falls back to Gap. Your Search Console positions show those ranks.

Getting the estimate is free, and nothing is spent until you press Start run. The expansion only uses results pages already checked in the last 7 days, and the panel shows how many checks the run would use against what is left this month.

No. Runs keep going in the background. The page refreshes every 10 seconds while you watch, and a Search history list shows past runs with their status and checks used.

No, by design. Each topic has an Ask Claude box with a prompt to paste into your own assistant, which writes the brief from the topic's keywords, ranks and competing pages. Linkeddit supplies the data and leaves the writing to you.

A tree of the searches around a few root keywords: each keyword grows into the related searches, People Also Ask questions or AI follow-up searches attached to it, level by level. It shows the shape of a topic, and which branches you already rank on, before you plan pages.

Your tracked keywords, or up to 50 keywords you type, one per line. Each keyword can expand into related searches, People Also Ask questions, or AI follow-up searches, which starts from the searches AI answer engines ran for your questions.

The web searches AI answer engines ran before answering your buying questions in Answer Radar. Growing a map from them shows the searches an engine performs on your topic, which are often more specific than what people type.

One to three levels below the roots and one to ten keywords per keyword, up to 150 keywords in all, one check each. The estimate says at most, because a map can finish with fewer keywords than it was priced for.

Your rank, the domain in position one, a difficulty proxy, whether an AI Overview appeared, and an intent label: Alternatives, Comparison, Pricing, Review, How to, Best of or Other.

As the share of the top ten results held by very large sites, from 0 to 100. It is a rough guide to how crowded a results page is, not measured ranking difficulty, and it is labeled as a proxy everywhere it appears.

Search does not publish modeled volume estimates. Demand comes from your own Search Console impressions, which are real counts for your site, and the map shows whether you rank, who leads and whether an AI Overview sits on top.

As a Diagram, a Tree or a Table. The Diagram is a flowchart you can drag, zoom with a pinch or Ctrl and scroll, and open or close by branch; clicking a keyword shows its details. Download PNG saves the tree as an image.

Look at who holds the results for your keywords rather than who you sell against. The Competitors view lists every domain that appears in the results you have checked, most visible first, so publishers and marketplaces show up next to direct rivals.

Keywords in the top 10, average position, keywords where it beats you, how often it was cited in AI Overviews, and how often each AI answer engine cited it in your latest Answer Radar run.

No. It needs no run and reads the results already checked by rank tracking and by topics and map runs.

Select a domain in the Competitors view. Its panel lists the Pages that beat us and the keywords where each one does.

A read of the competitor's public sitemap, grouped into Editorial, Templated and Other sections, so you can see whether they rank with hand written articles or with pages generated from a template. It costs no checks, and if the sitemap cannot be read you get the reason.

The Competitors view puts both on one row: top ten keywords and average position next to AI Overview citations and the per engine citation counts from your latest Answer Radar run. A domain that ranks modestly but is cited often by AI engines is one to study.

Compare equal windows of Search Console data for the changed page, before and after the day the edit went live, and leave the change day out of both. The Watchlist does this for you: 21 days either side, measured once enough days have passed.

The Watchlist waits 21 days, plus 2 days for Search Console's reporting delay, so a page is measured 23 days after the change. Shorter windows mostly measure noise and the time Google takes to recrawl.

Clicks, impressions, click-through rate and position for that exact page, in the 21 days ending the day before the change and the 21 days starting the day after. It also lists up to five queries whose clicks moved most, and a line for your main query if you set one.

Only when clicks moved by at least 15 percent of the before window and by at least 5 clicks. Anything smaller is Flat. Under 100 impressions in either window it says Not enough data.

Average position is an average over whichever queries showed the page, so it can move when the mix of queries changes even if nothing improved. It is reported and explained, but the verdict rests on clicks.

No. It is an observed difference between two windows. Seasonality, other edits and Google updates affect both, and the result lists those caveats, including when clicks and position moved in opposite directions.

The day the edit went live, which cannot be in the future. That day is left out of both windows because the edit went live part way through it.

No. It uses only Search Console data already synced, so it spends no checks and no credits.

The Watchlist shows Google's own index status for each watched page: Indexed, Not indexed, Partly indexed or Unknown, with Google's coverage wording, the last crawl date, and a note when Google chose a different canonical than the page declares.

Usually Search Console is not connected, or the page sits outside the connected property. Index status comes from Google's URL inspection, run by the daily sync for watched pages, up to 100 pages per run.