LLMrefs Review 2026: Pricing, Accuracy and Limits (6.6/10)

LLMrefs review 2026: what the $79 AI visibility tracker measures, its pricing history since 2025, the API, the weekly-data catch and who should pick it.

· BugViso Team

18 min read

LLMrefs scores 6.6 out of 10 in our review. It is an AI search visibility tracker that turns your SEO keywords into AI prompts and reports share of voice, position and citations across about ten answer engines. One plan costs $79 a month for 500 prompts, which is cheap per prompt. The catch: data refreshes weekly, and the sampling method is undocumented.

By the end you'll know what LLMrefs measures, how its pricing changed since launch, what the API really returns, what the terms mean for agencies, and when another tracker fits better. For the wider field, see our comparison of the best AI visibility tools.

How we reviewed it: we read LLMrefs' public site, pricing card, Terms of Service (last updated 20 May 2025) and OpenAPI spec (v1.0.0) on 15 November 2026. We traced pricing through Internet Archive snapshots from September 2025 to February 2026, then fetched five llmrefs.com pages as GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot. We did not buy the trial, so paywalled features are described from LLMrefs' own pages and labelled as such. Disclosure: BugViso sells a competing AI visibility tracker. We've scored LLMrefs on public evidence, and we say where it beats us.

LLMrefs Review at a Glance: The 6.6/10 Scorecard

LLMrefs is the budget pick for teams that want many prompts on many engines and can live with weekly numbers. It loses points on freshness, on methodology it doesn't publish, and on support reports from users.

CriterionWhat we foundScore
Engine coverageChatGPT, AI Overviews, AI Mode, Gemini, Perplexity, Claude, Grok, Copilot, Meta AI, DeepSeek9
Price per prompt$79 a month for 500 prompts, about $0.16 per prompt per month9
Free tools8 free tools, no login, including a crawlability checker and a fan-out generator8
Agency fitUnlimited projects and seats; no white-label reports listed; terms limit sharing results7
API and exportCSV export; read-only API with 6 endpoints at 10 requests a minute6
Data freshnessEvery keyword updated "at least once per week"5
Support and trustPublic complaints about support and cancelling; "Limited time" price running since December 20255
Methodology transparencyDocs page says "Coming soon"; prompts per keyword and scoring formula unpublished4
OverallAverage of the eight scores, equally weighted6.6

Best for: agencies and in-house SEO teams that report monthly trends across many brands and want the lowest cost per prompt. Not ideal for: teams that need daily movement, a documented sampling method, or client-ready branded reports.

What Is LLMrefs?

LLMrefs is a London-based AI search analytics platform that tracks how often AI answer engines mention and cite a brand. Its Organization schema names James Berry as founder and lists a founding date of 1 May 2025. That was also the day it launched on Product Hunt, where it finished third for the day with 309 upvotes. Product Hunt's company data lists it as bootstrapped, with no funding raised.

The founder's public profile lists earlier roles as Head of Organic Growth at VEED and as a core maintainer of tRPC, the TypeScript RPC library. That engineering background shows in the product. It's built around automation, not consulting.

The positioning is one line on the homepage: you track keywords, not prompts. You import an SEO keyword list, and LLMrefs writes the conversational prompts for you. The homepage says more than 10,000 marketers use it. That figure read "more than 6,000" in the December 2025 snapshot and "more than 10,000" by February 2026. Neither number comes with a source.

How LLMrefs Tracks Keywords Instead of Prompts

LLMrefs expands each keyword into a set of "fan-out" prompts, runs them across AI engines, and rolls the answers up into one ranking per keyword. You see a brand table per keyword with share of voice (SoV), average position and cited URLs, filterable by engine and country.

That design fixes a real problem. A prompt like "best payroll software for a 20-person startup" has endless phrasings, and tracking one phrasing tells you little. Grouping many prompts under one keyword gives you a steadier number, and it mirrors the query fan-out technique Google says AI Overviews and AI Mode use: one question becomes several related searches.

What LLMrefs doesn't publish is the sampling:

  • Prompts per keyword. The homepage demo shows 25 prompts for one keyword. The December 2025 pricing card listed "50 Keywords" next to "Monitor up to 500 prompts a month", which works out to 10 prompts per keyword.
  • Runs per prompt. Not stated. AI answers vary from run to run, so the number of samples decides how much a weekly change means.
  • Scoring. A 2025 FAQ described a proprietary "LLMrefs Score" built from ranking weight and consistency across models, prompts, temperature and top_p. No formula was published, and the current site no longer mentions the score.
  • Refresh. The FAQ says results are checked "in real-time" and that every keyword is updated "at least once per week". The plan card says "Weekly AI visibility reports". Read it as weekly.

The site is also inconsistent about coverage. The features block promises geo-targeting in "20+ countries and 10+ languages", while the pricing card on the same page says "50+ countries & 20+ languages". The homepage lists ten engines, and the plan card names nine of them. These are small things, but in a measurement tool the published facts should agree.

LLMrefs Pricing in 2026: One $79 Plan, and How It Got There

LLMrefs costs $79 a month for one "All in One" plan with 500 prompts, every listed engine, unlimited projects and unlimited team members. There's a 7-day free trial and no annual price. The card has said "Limited time only" since at least December 2025.

The plan changed shape twice in its first year. We read these snapshots on the Internet Archive (September 2025 example):

Date seenPlans on the pricing cardWhat changed
7 Sep 2025Free: 1 keyword, monthly report · Pro: $79, 50 keywords · Enterprise: custom, unlimited keywordsThree tiers; FAQ promised daily updates on Pro
11 Dec 2025Pro: $79 "Limited time only", 50 keywords, up to 500 prompts a month, weekly updatesFree and Enterprise tiers gone from the card
5 Feb 2026All in One: $79 "Limited time only", 500 prompts, 7-day free trialLimit now counted in prompts, not keywords
15 Nov 2026All in One: $79 "Limited time only", 500 prompts, 7-day free trialUnchanged; FAQ still talks about "more than 50 keywords"

Two things follow from that table. First, Pro moved from daily updates in the 2025 FAQ to weekly. Second, a price marked "limited time" for 11 months is a normal price. Budget as if it could rise.

Is LLMrefs free? Not as a plan. The homepage still says "No credit card required" and lets you create an account, and a free account shows a small preview. Ongoing tracking needs the $79 plan after the 7-day trial. The terms give no refund window. They only say refund requests go to the support email.

On cost per prompt, $79 for 500 prompts is about $0.16 per prompt per month. LLMrefs doesn't say whether every prompt runs on every engine each week, so you can't turn that into a cost per AI answer.

What LLMrefs Does Well

LLMrefs gets four things right: breadth for the money, flat pricing for agencies, useful free tools, and a site that follows its own AI-search advice.

  1. Engine breadth. Ten engines, including Grok, Meta AI, Copilot and DeepSeek, which many trackers skip. If your buyers use those engines, this matters.
  2. Agency maths. One subscription covers unlimited projects and unlimited seats. A 15-client agency pays the same $79 as a single brand, until the 500 prompts run out.
  3. Free tools. Eight tools with no login: an AI crawlability checker, an llms.txt generator, a Reddit threads finder, a query fan-out generator, a ChatGPT search query extractor, a prompts database the site says holds "4.5M+" conversations, a content A/B tester and a content humaniser.
  4. Setup speed. VisibilityLand's hands-on review from 8 November 2026 timed about four minutes from "Start tracking" to a first ranking.

Where LLMrefs Falls Short

The weak spots are freshness, undocumented sampling, a thin API and terms that agencies should read before they share client reports.

Weekly data limits what you can conclude

Weekly refresh gives you about four data points per prompt per month. A content change, a PR mention or a model update shows up a week late. Small samples also make week-over-week moves noisy: the same VisibilityLand review ran LLMrefs' free preview twice, 15 minutes apart, and saw its test brand at rank 131 and then 169. Our guide on how often to track AI visibility explains when weekly is enough and when it hides the story.

The method isn't published

The only docs page reads "Coming soon". Without knowing prompts per keyword, samples per prompt or how share of voice is weighted, you can't put an error bar on a number. A 40 % share of voice from 10 answers and from 250 answers are very different claims.

The terms restrict sharing results

Section 6 of the Terms of Service gives you a licence to use results internally, but says you may not "make the Results available to unaffiliated third parties". An agency's client is arguably an unaffiliated third party. Ask LLMrefs in writing whether client reporting is covered before you build a service on it. The same terms also ban "automated access, bots, and crawlers", so use the API rather than scraping the dashboard.

No branded reports are listed

The plan card lists CSV export and API access. It doesn't list white-label PDFs or client share links. Agencies will be pasting data into their own report templates.

Support complaints are public

On Reddit, an agency user running 15 clients praised the price and the Reddit finder in May 2026, but noted that there was no sentiment tracking and that data updated only weekly. Replies in August 2026 complained about slow support, and a February 2026 thread in r/GEO_optimization was about a user who couldn't find how to cancel. These are a handful of posts, not a survey. But with zero reviews on G2 and one on Product Hunt, they are most of the public user feedback.

We Checked LLMrefs.com the Way AI Crawlers See It

LLMrefs' own site passes the basic AI-crawler checks. All four AI crawlers got HTTP 200, robots.txt allows them, and the marketing pages are server-rendered. The exception is the API documentation, which is nearly empty without JavaScript.

On 15 November 2026 we fetched five pages with each crawler's user agent. We counted the visible words in the raw HTML, which is what a crawler that doesn't run JavaScript reads. Then we rendered the same pages in headless Chromium:

PageAI crawlers (4)robots.txtRaw-HTML wordsRendered words
Homepage200 for allAllowed1,3911,195
AI search visibility page200 for allAllowed1,4061,272
About page200 for allAllowed801786
AI crawlability checker tool200 for allAllowed439423
API documentation200 for allAllowed8349

Raw counts run slightly higher than rendered ones because the HTML holds collapsed FAQ answers and menus that aren't on screen. The site also serves a 29,304-character llms.txt, and its robots.txt blocks only /account, /dashboard and /api. The API reference renders client-side, so crawlers that don't execute JavaScript see 8 words there. The llms.txt file links straight to that page.

Run the same check on any site, yours or a vendor's:

python
#!/usr/bin/env python3
"""See a page the way AI crawlers do: HTTP status per crawler user agent,
robots.txt verdict, llms.txt presence and how many words are in the raw HTML
(what crawlers that don't run JavaScript read).

Usage: python3 ai_crawler_view.py https://example.com/ [more URLs...]
Stdlib only. One request per bot per URL, 1 s apart.
"""
from __future__ import annotations

import html
import re
import sys
import time
import urllib.error
import urllib.request
import urllib.robotparser
from urllib.parse import urlparse

BOTS = {
    "GPTBot": "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; GPTBot/1.2; +https://openai.com/gptbot)",
    "OAI-SearchBot": "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; OAI-SearchBot/1.0; +https://openai.com/searchbot)",
    "ClaudeBot": "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)",
    "PerplexityBot": "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; PerplexityBot/1.0; +https://perplexity.ai/perplexitybot)",
    "Browser": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0 Safari/537.36",
}


def fetch(url: str, ua: str) -> tuple[int, str]:
    req = urllib.request.Request(url, headers={"User-Agent": ua})
    try:
        with urllib.request.urlopen(req, timeout=20) as r:
            return r.status, r.read().decode("utf-8", "replace")
    except urllib.error.HTTPError as e:
        return e.code, ""
    except Exception:
        return 0, ""


def visible_words(page: str) -> int:
    page = re.sub(r"(?is)<(script|style|noscript|template|svg)\b.*?</\1>", " ", page)
    text = html.unescape(re.sub(r"(?s)<[^>]+>", " ", page))
    return len(re.findall(r"[A-Za-z0-9][\w'-]*", text))


def main(urls: list[str]) -> None:
    origin = "{0.scheme}://{0.netloc}".format(urlparse(urls[0]))
    rp = urllib.robotparser.RobotFileParser(origin + "/robots.txt")
    rp.read()
    llms_status, llms = fetch(origin + "/llms.txt", BOTS["Browser"])
    print(f"{origin}  llms.txt: {llms_status} ({len(llms):,} chars)")
    for url in urls:
        print(f"\n{url}")
        for name, ua in BOTS.items():
            status, body = fetch(url, ua)
            allowed = rp.can_fetch(name, url)
            print(f"  {name:<14} HTTP {status:<4} robots: {'allow' if allowed else 'DISALLOW'}"
                  f"  raw-HTML words: {visible_words(body):,}")
            time.sleep(1)


if __name__ == "__main__":
    if len(sys.argv) < 2:
        sys.exit(__doc__)
    main(sys.argv[1:])

Two caveats. Python's robotparser is close to, but not identical with, RFC 9309 matching. And a spoofed user agent tests your server's rules, not a firewall that checks the crawler's published IP ranges. OpenAI lists its crawlers and what each one does in its bot documentation.

Is LLMrefs Accurate?

Nobody has published an accuracy test of LLMrefs, so treat its numbers as estimates and check them yourself during the trial. AI answers are non-deterministic: the same prompt on the same engine can name different brands an hour later. A tracker's accuracy depends on how many samples sit behind each number, and LLMrefs doesn't disclose that.

A 7-day trial is enough for a basic check:

  1. Day 1: add 10 keywords you know well, including 2 where you're sure you appear in AI answers and 2 where you're sure you don't.
  2. Day 1: export the raw answers and citations as CSV. Keep that file.
  3. Day 2: ask 5 of the generated prompts yourself in ChatGPT and Perplexity with web search on. Note whether your brand appears.
  4. Day 7: compare the weekly update with day 1. Any keyword that moved more than 20 points of share of voice with no change on your side is noise. Note how many there are.
  5. Decide: if your "sure yes" and "sure no" keywords land where you expect, and the noise is small, the data is usable for monthly trends.

Our breakdown of how an AI visibility score is built shows why sample size and weights matter more than the headline number.

The LLMrefs API: What It Actually Returns

The LLMrefs API is read-only: six GET endpoints behind a bearer token, limited to 10 requests per minute. The OpenAPI spec (v1.0.0) lists organizations, projects, keywords, search engines, locations and the data for one keyword. There's an official JavaScript SDK on GitHub.

bash
curl https://llmrefs.com/api/v1/keywords \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN'

That's enough to pull weekly keyword data into a spreadsheet or a dashboard. It isn't enough to create projects, add keywords or trigger a run from your own tools. One more thing to watch: an LLMrefs blog post about API integration, updated in September 2026, describes prompt, citation and share-of-voice endpoints, plus webhooks. None of those are in the published spec. Build against the spec.

LLMrefs vs BugViso's AI Visibility Tracker

The two trackers make different trade-offs. LLMrefs gives you more engines and more prompts for a flat $79. BugViso runs fewer engines but publishes its scoring formula, can run daily, and adds fact checks and an action plan to every report.

The BugViso AI Visibility Tracker asks ChatGPT, Gemini, Perplexity, Claude and Google AI Overviews, with web search on, a set of buyer prompts. By default that's 50, drafted from your site and editable, measured against at least 3 competitors. One run sends every prompt to every engine. Each report shows mentions, rank and share of voice per engine, sentiment, the sources AI cites (and the ones it cites for competitors but not for you), a fact check of AI claims against your own site, and a ranked plan with AI-written drafts.

LLMrefsBugViso AI Visibility Tracker
Engines~10, including Grok, Copilot, Meta AI, DeepSeek5: ChatGPT, Gemini, Perplexity, Claude, AI Overviews
InputKeywords, expanded into promptsBuyer prompts drafted from your site, editable
RefreshAt least weeklyOn demand, daily, weekly or monthly
Scoring methodNot publishedPublished: index = 0.35 visibility + 0.20 share of voice + 0.20 position + 0.15 citations + 0.10 sentiment, with a 95 % Wilson interval on visibility
Beyond trackingCitations, free toolsFact check, source gaps, action plan with AI drafts, email alerts on index drops
ReportsCSV, read-only APIPDF, CSV, shareable report links
Price$79/month, 500 prompts$5 per run with no plan, or $139/month for 30 runs

Pick LLMrefs if engine breadth and prompt volume across many small clients matter most. Pick BugViso if you need daily movement, numbers you can explain to a client, and a list of fixes rather than only a ranking. Weekly tracking of 50 prompts on BugViso is about four $5 runs a month.

Who Should Use LLMrefs, and Who Shouldn't

Use LLMrefs if you want a cheap monthly read on AI share of voice across many brands, your clients care about Grok, Copilot or DeepSeek, and you already have a reporting template to paste CSVs into.

Skip it, or pair it with something else, if:

  • you need to see a change the day after you ship it;
  • a client or your boss will ask how the number was calculated;
  • you need branded PDF reports or client links;
  • you plan to show raw results to clients and the terms' third-party clause hasn't been cleared with LLMrefs.

Whichever tracker you choose, keep the prompt set fixed for at least a month, so trends reflect the engines rather than your edits. Our guide to AI share of voice covers how to set competitor lists so the percentages mean something.

Frequently Asked Questions

Is LLMrefs free?

Only partly. LLMrefs offers a free account with a small preview and a 7-day free trial of its only plan, All in One, at $79 a month. The free plan it offered in 2025 (1 keyword, monthly report) no longer appears on the pricing card as of November 2026.

How much does LLMrefs cost?

LLMrefs costs $79 a month as of 15 November 2026. That covers 500 prompts, all listed AI engines, unlimited projects and unlimited team members. The price has been labelled "Limited time only" since December 2025, and no annual or enterprise price is published.

Is LLMrefs legit?

Yes. LLMrefs is a real, working product from a London company founded by James Berry, launched on 1 May 2025 and bootstrapped. Its weak points are transparency and support: the methodology isn't published, and some Reddit users report slow support replies and trouble cancelling.

Does LLMrefs have an API?

Yes, a read-only REST API with six GET endpoints (organizations, projects, keywords, search engines, locations, keyword data), a bearer token and a limit of 10 requests per minute. It can't create keywords or trigger runs. There's also an official JavaScript SDK.

What do Reddit users say about LLMrefs?

Reddit posts from 2026 praise the $79 price, unlimited domains and seats, and the Reddit threads finder. The recurring complaints are weekly-only data, no sentiment tracking, results grouped by keyword rather than by prompt, slow support and a hard-to-find cancel option. These are a few posts, not a survey.

What is the best LLMrefs alternative?

It depends on what LLMrefs lacks for you. If you need daily runs, a published scoring formula, fact checks of what AI says about your brand and an action plan, BugViso's AI Visibility Tracker is an alternative that runs from $5 per run with no subscription.

Our Final Verdict on LLMrefs

LLMrefs earns 6.6/10: the best price per prompt we've seen, wide engine coverage, and a method you have to take on trust. Use the trial to export raw answers and check them against reality before you report the numbers to anyone. And before tracking whether AI engines mention you, make sure their crawlers can read your site at all. That is the first thing the AI search readiness check in a BugViso website audit looks at.

Written by

· BugViso Team

Kazi writes BugViso’s guides on website audits, Core Web Vitals, technical SEO, accessibility and AI search. The data in them comes from audits BugViso runs in a real Chromium browser, including our 219-site study of website health.

Found this useful? Share it.

Summarise with AI

Open this guide in your assistant.

Follow BugViso

New guides and audit data as we publish them.

AI visibility tracker

Is your brand in AI answers?

See how often AI assistants mention you, cite your site and rank you against your competitors.

  • ChatGPT
  • Gemini
  • Perplexity
  • Claude
  • AI Overviews
See how it works

See where your site stands

Run a free BugViso audit for SEO, speed, accessibility and AI search readiness — with fixes you can ship today.