Methodology
This page explains how NameIO counts what AI answers say about your store: what each figure measures, where the answers come from, how a question gets its funnel step, how sure a figure is, and when NameIO calls a change. The figures, tables and rules below are printed from the code that counts your answers, so they always match it. A dated changelog at the end lists every change to the method.
What we measure
NameIO asks the questions shoppers ask AI and reads every answer. Each question belongs to one funnel step: Awareness, Consideration or Conversion. For each step, on each engine and on all engines together, NameIO counts three things:
- Named: how often AI names your store.
- Share of brand mentions: your part of all the brand mentions in those answers.
- Place: where the wording of the answers puts you among the brands they name, always a place such as "2nd to 4th of 6 brands named", never a percentage.
Named and share of brand mentions come with a likely range, or as counts when there are few answers. All three only use questions that don't name your store. These figures describe what AI answers say. They are not visits or sales.
What one answer is
An answer is what one engine said to one question in one check. NameIO keeps its text, finds every brand it names and reads the words around each name. A question asked again gives a new answer, and it can differ.
How brands are found in an answer
No AI model reads your answers for NameIO. Word rules find the brands, so the same answer and the same brand list always give the same brands. Your store and the competitors you track are matched by name. Other brands are found from how the answer is laid out, such as list items, bold names, headings and tables, and are counted once they pass the checks below.
Brand finder version 4, on a labelled set of 77 answers with made-up brands, written the way each engine writes, last run on Nov 11, 2026:
| How the answer names brands | Answers | Precision | Recall | Bar to pass |
|---|---|---|---|---|
| Lists, bold names and headings | 57 | 98.0% | 93.4% | Precision 95%, recall 85% |
| A table only | 6 | 100.0% | 80.0% | Reported, not gated |
| Sentences only | 14 | 100.0% | 88.5% | Reported, not gated |
Precision is how many of the names found are brands a reader would count. Recall is how many of those brands were found. Retailers count here as brands, in the names found and in the labels, though shares leave them out.
On the structured answers, recall is 30.0% for brands named under one question only, and 87.7% when each question is read only with the brands found under the other questions.
A name counts as a brand once you mark it as one, once it links to a site with its name and is also written outside the link, once an answer leads with it and names it again, or once it leads under 2 different questions with at least one of those leads a list item, a table row or a link. Unless you mark it, a name that any answer used as a common word never counts. Review sites and publications never count; retailers are sorted onto their own line. A name written only as a link to a site with its name, or found only in a link's address, a citation or an image, is not counted.
Names are sorted by word rules, not by an AI model. A product written right after its brand counts as that brand; specs, section labels and joined phrases are not names; a site that sells other brands' products is a retailer. Names the rules can't sort count as competitors until you sort them. Your choices always win.
You can correct the list at any time: mark a name as Not a brand, or as Same as another brand.
Where answers come from
NameIO asks your questions on each engine you track and saves the answers. A data service that NameIO pays collects most of them: ChatGPT and Gemini answers are captured from their apps, as a shopper sees them; Google AI Overviews come from Google search results; other engines' answers come from the engine's own service for other apps (an API), so they can differ from what its app shows. Where answers come from has the details for each engine.
The three steps and the rule
Shoppers ask AI at every step of buying, so each question is sorted into one step:
- Awareness: before they know which brand, such as "What should I look for when buying trail running shoes?"
- Consideration: while comparing, such as "Which brand of trail running shoes has the best reviews?"
- Conversion: before they buy, such as "Is Fernline a trustworthy brand?"
Each step is its own set of questions, not the same shoppers moving through. Word rules sort the questions, with no AI model:
These are stage rules version 1. The rules run in this order, and the first one that fits decides:
| Rule | Step | Fires on | Confidence |
|---|---|---|---|
conv.trust | Conversion | A named brand or store with a trust word: safe to order from, safe to buy from, safe, legit, legitimate, scam and 16 more | High |
conv.purchase | Conversion | Where to buy or order (where to buy, where can i buy, where to order, where can i order, where can i get, where to get and 8 more); about a named brand, discount, coupon, promo, promo code, voucher, deal and 18 more; about one named brand, its price or whether it is worth it (price, cost, how much, worth it, worth the money, worth the price and 2 more); with no brand named, a deal on a product type (deal on, discount on, coupon for) | High about a named brand; low with no brand named |
cons.compare | Consideration | vs, versus, difference between, compare, alternative, instead of and 6 more; over about a named brand; two brands named with or, and, better, which | High |
cons.shortlist | Consideration | recommend, review, top rated, rated, rating, trusted and 10 more; with a product type, best, top, which, who makes, who sells, looking for and 5 more; about a named brand, quality, any good, good; with no brand named, buy, purchase; a price used as a filter, such as under $50 | High |
aware.learn | Awareness | No brand named, with how, why, what causes, what is, what are, what makes and 25 more; or a problem stated without a product type, such as help with, get rid of, deal with, struggle with, suffer from, i have and 5 more | High |
fallback | Awareness with no brand named; Consideration with a brand named | Any question no rule above fits | Low: the app marks the step with a dot |
Where two rules could fit:
- A bare
buywith no brand named is Consideration, not Conversion. - A price used as a filter (
under $50) is Consideration; the price of one named brand is Conversion. - Price,
worth itandbuycount as Conversion only about exactly one named brand. Safecounts as a trust word only about a named brand or store.- A problem stated without a product type or a brand is Awareness, before any Consideration word counts.
- Days, months, holidays and places are never brands, so
Black Fridaynames no brand.
Setup questions keep the step they were written for. For a store that sells one product type, they start as 4 Awareness, 11 Consideration and 5 Conversion questions. A step you set yourself stays when the rules change or the question is reworded.
You can change a question's step on the Questions tab. Your earlier weeks are then counted again with the new step, free.
The formulas
What each figure estimates, and what it leaves out:
- One answer is one engine's reply to one wording of one question in one check. Each weekly check asks each question once on each engine. A question can carry up to 2 more wordings of your own; they are asked once a check takes more than one answer a question.
- Named is the share of answers that name your store, over the last 4 counted weeks of the step's questions. Inside a question each wording counts the same. Questions are asked equally often, so each counts about the same.
- A change in Named is the average, over the questions asked in both periods, of each question's change. Each question counts the same, and a question asked in only one period is left out.
- All engines is the average of the engines' figures, each engine counting the same. A change uses only the engines with at least 3 counted weeks in both periods. A new engine joins the all-engines level after 4 counted weeks and the all-engines change after 8.
- Share of brand mentions is your mentions divided by every brand's mentions in the same answers. A brand counts once per answer, however often that answer names it. Shares count brands only; names not yet sorted count as competitors. A change compares the two shares on the questions asked in both periods.
- Place is your average standing among the brands each answer names (below).
- What is left out, and why. Questions that name your store are left out of all three: AI names a store the question names, so those answers say little about whether it would name you unasked. NameIO shows them apart as answers about you. A brand the question itself names is not counted in that question's answers. An answer that can be missing, such as an AI Overview Google didn't show, is left out rather than counted as not naming you.
- Fewest answers. A percentage needs 30 effective answers from 5 questions; a change needs 6 questions asked in both periods. Effective answers count answers to the same question as fewer than they are, since they tend to agree.
Place among the brands named
- In one answer, each brand named gets points from the words around its name: praise, caution, and roles such as top pick. Brands are ranked by their points. Brands with equal points share the middle place: two brands tied for first and second both get place 1.5. Your standing is 1 when you are first and 0 when you are last.
- Named alone. An answer that names only your store adds no place. The app counts those answers on their own, as named alone.
- Decisive answers. An answer counts toward your place only when your points differ from at least one other brand's. A place needs 30 decisive answers from 5 questions; below that the app shows the count.
- The field. Your place is among your store and the brands ranked in at least 5 answers or 10% of the step's ranked answers, whichever is more: the 9 with the most, so at most 10 brands. A brand ranked once never moves your place.
- The range. 1,000 redraws of whole questions give the likely range of your place, shown as "2nd to 4th of 6 brands named". An exact place is shown only when your range overlaps no other brand's.
- A change in place is never an arrow. The app says AI's wording placed you higher or lower than in the 4 weeks before only from 30 decisive answers and 6 questions, and only when the likely range of the change in your average standing leaves out zero.
- Rough guide. Until the word rules pass a check against a person's reading (see How far the rules agree with a person), the place is shown as a rough guide.
- What place means. Place describes the wording around brand names in AI answers, not what shoppers think of a brand. The word lists are English, so place reads English answers only.
Why results vary
AI answers change from one ask to the next, even when nothing changed on your site. The same question can name your store on Monday and leave it out on Tuesday. Engines also change how they answer, for everyone at once, when they update a model or show AI Overviews on more searches. Your own figures move when you add, remove or reword questions.
So NameIO never reads a single answer or a single question as a verdict. It reads many questions over several weeks, it compares the same questions with themselves, and it checks every change against how much your figures usually move from week to week.
Ranges and minimums
A percentage comes with its likely range: the values the true figure probably lies between, given how many answers there are and how much they agree. Answers to the same question tend to agree, so 12 answers to one question tell you less than 12 answers to 12 questions. NameIO counts them as fewer effective answers.
With few effective answers a step shows counts, such as "Named in 5 of 12 answers", not a percentage. With more, it shows a percentage with its range as a rough guide; with more again, in full. The numbers are in Every rule and its value. Adding questions to a step narrows its range more than more weeks do.
The smallest change a step can show
The smallest change, in points of Named, that each comparison shows 4 times in 5, for a step with 7, 15 or 27 questions that don't name your store. Calculated at a level of 50%, where answers vary most, and a correlation of 0.5 between answers to the same question (the starting value until your own is measured). A change smaller than the floor of 10 points is never called, so no cell shows less. "Weeks after a change" counts the weeks until the comparison covers the change, plus one week for an Up or Down on the last 4 weeks to be confirmed.
All 3 engines together:
| Comparison | Answers a week | Weeks after a change | 7 questions | 15 questions | 27 questions |
|---|---|---|---|---|---|
| Last 4 weeks vs the 4 before | 1 | 5 | 18 | 11 | 10 (floor) |
| Last 4 weeks vs the 4 before | 3 | 5 | 11 | 10 (floor) | 10 (floor) |
| This quarter vs the one before (13 weeks each) | 1 | 13 | 10 | 10 (floor) | 10 (floor) |
| This quarter vs the one before (13 weeks each) | 3 | 13 | 10 (floor) | 10 (floor) | 10 (floor) |
| One check vs the 4 weeks before | 1 | 1 | 29 | 18 | 13 |
| One check vs the 4 weeks before | 3 | 1 | 17 | 10 | 10 (floor) |
One engine:
| Comparison | Answers a week | Weeks after a change | 7 questions | 15 questions | 27 questions |
|---|---|---|---|---|---|
| Last 4 weeks vs the 4 before | 1 | 5 | 32 | 19 | 14 |
| Last 4 weeks vs the 4 before | 3 | 5 | 18 | 11 | 10 (floor) |
| This quarter vs the one before (13 weeks each) | 1 | 13 | 18 | 11 | 10 (floor) |
| This quarter vs the one before (13 weeks each) | 3 | 13 | 10 | 10 (floor) | 10 (floor) |
| One check vs the 4 weeks before | 1 | 1 | 50 | 31 | 22 |
| One check vs the 4 weeks before | 3 | 1 | 29 | 18 | 13 |
These figures leave out the swings that move every question at once, such as an engine update, so real figures are larger. When a change can't be told yet, the app gives the figure for your own questions: "a change smaller than about … points can't be told from normal variation".
How a change is called
Each step compares the last 4 weeks with the 4 weeks before, on the questions asked in both, in points, with its likely range. NameIO calls a change only when all of these hold:
- the questions moved more than they usually do, compared question by question;
- the weeks moved more than they usually do, so a change that hits every question at once, such as an engine update, isn't read as yours;
- the move is at least the floor, a few points that are normal drift;
- it holds for two weekly readings in a row.
What the app then says:
- Up or Down: all of the above, two weeks in a row. For example: "Up 12 points vs the 4 weeks before (likely +4 to +20), on 26 questions asked in both."
- Provisional: the first week of such a change; it is confirmed if next week agrees.
- Steady: the whole likely range sits inside the floor.
- Can't tell yet: the likely range reaches past the floor, so the change can't be told from normal week-to-week variation yet. More weeks narrow it.
- Watch: recent weeks sit outside the usual range, but this is not a confirmed change.
- Not enough weeks yet: there are not yet enough counted weeks to compare.
Three more comparisons are read again every week, at a stricter level: since you started tracking these questions, since your latest change in this step, and this quarter vs the one before, once there are two quarters of weeks. A confirmed change leaves a mark on the chart, which stays after the 4-week comparison goes back to steady.
Fixes. A fix gets one reading, at Day 28. NameIO compares the questions the fix touched with your untouched questions over the same weeks and engines, so a change that moved every question doesn't count for the fix. The reading is then kept as it is; a new method version can restate it, with the day. None of these readings says why a figure moved.
How often a change is called by chance
NameIO tests its rules on simulated stores where nothing changed, so every change it calls there is a false one:
Measured on Nov 11, 2026 with the rules in use, on simulated stores where nothing really changed, so every change called is a false one. Each store was simulated 500 times, each time for a year of weekly checks on 3 engines.
| Simulated store | Questions | Answers a week | Years with a false Up or Down |
|---|---|---|---|
| Named in about half the answers, correlation 0.4 | 27 | 3 | 0.0% |
| Named in about half the answers, correlation 0.4 | 27 | 1 | 1.2% |
| Named in about half the answers, correlation 0.6 | 27 | 3 | 0.0% |
| Named in about half the answers, correlation 0.6 | 27 | 1 | 0.4% |
| Matched to a real store's week-to-week flips, correlation 0.4 | 27 | 3 | 0.0% |
| Matched to a real store's week-to-week flips, correlation 0.4 | 27 | 1 | 0.0% |
| Matched to a real store's week-to-week flips, correlation 0.6 | 27 | 3 | 0.0% |
| Matched to a real store's week-to-week flips, correlation 0.6 | 27 | 1 | 0.2% |
| A small awareness step | 7 | 3 | 4.2% |
| A small awareness step | 7 | 1 | 0.0% |
- Up or Down, all engines together: at most 1.2% of years at 1 answer a week and 4.2% at 3. Our bar is 10%.
- Since you started tracking: at most 7.8% of years at 1 answer a week and 1.2% at 3. This quarter vs the one before: 0.0%.
- One engine on its own: a false Up or Down on some engine in up to 18.0% of years at 3 answers a week (0.2% at 1). Read one engine's arrow with more care than the all-engines one.
- Watch: shown at least once in 47.0% of steady 104-week series (our bar: 25%), and it caught 68.0% of real steps within 6 weeks (our bar: 80%). Both miss our bars, so Watch stays a grey note with no arrow, and its limits are under review.
- Fixes: on 2,000 placebo fixes that changed nothing, put on the questions AI named least, the Day 28 reading said "moved the right way" for 1.5% (3 questions) and 1.3% (5 questions). Our bar is 5%. The earlier rule, one check against one check, said "moved the right way" for 75.1% and 75.9% of the same fixes: questions AI named least are often named more next time by chance alone. That is why a fix is now compared with your untouched questions.
How far the rules agree with a person
Steps and place come from word rules. To check them, a person labels the same questions and answer pairs once, without seeing what the rules said, and the two are compared:
Stage rules (version 1, questions of Nov 8, 2026). Not yet measured: this fixture is waiting to be labelled. The rules are unsure (low confidence) on 8 of its 150 questions.
Wording around brand names (word list version 4). Not yet measured: this fixture is waiting to be labelled. Until it passes, the rank is shown as a rough guide.
Hidden or partial data
Some weeks hold less than a full picture, and NameIO says so instead of filling the gap:
- Recounting. While earlier checks are being counted again, such as after a brand correction or a new method version, a step shows counts only, with no range and no change, until the recount ends.
- Extra checks. A check you run yourself in a week that already has a weekly check is shown as an extra check. It is never added into a comparison, so running more checks doesn't move your figures.
- Repeated answers. If many answers in a check are exactly the same, the app flags that the engine may have sent repeats, not new answers.
- Answers about you. When a step has too few questions that leave your store's name out, the step shows how AI talks about you there instead: links to your site, caution words and competitors named in those answers.
Limits
- Answers that can be missing. Google doesn't show an AI Overview for every search. A search with none is left out, not counted as a miss: Named on AI Overviews is out of the searches that showed one, and the Answered with text line shows how often one was shown. A move of 15 points in that rate is marked on the chart.
- Failed answers. An answer that couldn't be collected is not counted. A check counts as a week on an engine only when it collected at least 90% of the answers it asked for; otherwise it stays out of the trend and the chart says so.
- English word lists. Brands are found in any language, but the word lists for steps and for place are English. In other languages Named and share of brand mentions are counted, and place reads English answers only.
- What these figures describe. These figures describe what AI answers say, not visits or sales; NameIO has not yet checked how they track AI-referred visits.
- When the way a question is asked changes. When you add or edit a wording, or a check takes a different number of answers, a comparison uses only each question's first answer in its original wording until both periods are asked the same way.
- When the method changes. A new method version counts every stored check again with the new rules, free, so both periods of a comparison are always counted the same way. A line counted one way is never joined to a line counted another way.
- Corrections count all history again. When you mark a name as Not a brand or Same as another brand, or set a question's step yourself, every stored check is counted again with the correction, free. The chart marks the week of the correction, and a change mark it alters shows the day it was restated.
- One check is one sample. AI answers change from one ask to the next, so one check is one sample of what the engines said that week. Changes are read over weeks and many questions, never on one question in one week.
Every rule and its value
These are the rules of method version 3, with the same values since version 3 (Nov 14, 2026).
| Group | Rule | Value | What it means |
|---|---|---|---|
| Level | MIN_EFFECTIVE | 30 | A step shows a percentage only from this many effective answers; below that it shows counts. |
| Level | FIRM_EFFECTIVE | 80 | From this many effective answers a percentage is shown in full, not as a rough guide. |
| Level | MIN_CLUSTERS | 5 | A percentage also needs answers to at least this many different questions. |
| Level | DEFAULT_RHO | 0.5 | How alike answers to the same question are taken to be (0 not at all, 1 always the same) until your own answers can measure it. |
| Level | RHO_PRIOR_WEIGHT | 20 | When your own measure is blended with that starting value, the starting value counts as much as this many questions' answers. |
| Level | RHO_MIN | 0.05 | The blended value is kept at this or more. |
| Level | RHO_MAX | 0.95 | The blended value is kept at this or less. |
| Change | ALPHA | 0.05 | The chance of calling a change that isn't there, accepted for one test. |
| Change | ALPHA_SINGLE | 0.01 | The stricter chance used while an engine gives one answer per question a week. |
| Change | ANCHOR_ALPHA | 0.01 | The stricter chance for comparisons read again every week: since you started, since your latest change, and this quarter. |
| Change | MIN_CHANGE_CLUSTERS | 6 | A change needs at least this many questions asked in both periods. |
| Change | EXACT_BELOW | 15 | Below this many questions, the test counts every possible pattern instead of using an approximation. |
| Change | WINDOW_WEEKS | 4 | One period is this many counted weeks. |
| Change | QUARTER_WEEKS | 13 | A quarter is this many counted weeks. |
| Change | MIN_COUNTED_WEEKS | 3 | A period needs at least this many counted weeks. |
| Change | CONFIRM_WEEKS | 2 | An Up or Down is confirmed, or cleared, by this many weekly readings in a row. |
| Change | BASKET_OVERLAP | 0.8 | At least this share of each period's questions must be asked in both periods. |
| Change | PANEL_BREAK | 0.1 | A line splits where more than this share of a step's questions changed. |
| Change | SAME_BASKET_SHARE | 0.75 | The same-questions line keeps the questions asked in at least this share of the weeks shown. |
| Change | PRESENCE_FLOOR_MIN | 5 | The smallest floor for Named, in points. A move under the floor is never called a change. |
| Change | PRESENCE_FLOOR_MAX | 10 | The largest floor for Named, in points. The floor is half the room left to move, kept between the two. |
| Change | SHARE_FLOOR_POINTS | 4 | The smallest floor for share of brand mentions, in points. |
| Change | SHARE_FLOOR_SHARE | 0.15 | The floor for share of brand mentions is at least this part of the earlier share. |
| Change | NEW_ENGINE_LEVEL_WEEKS | 4 | A new engine joins the all-engines level after this many counted weeks. |
| Change | NEW_ENGINE_TEST_WEEKS | 8 | A new engine joins the all-engines change after this many counted weeks. |
| Watch | EWMA_LAMBDA | 0.2 | How much weight the newest week gets in the moving average behind Watch. |
| Watch | EWMA_L | 3 | How wide the Watch limits are, in multiples of the usual week-to-week spread. |
| Watch | EWMA_BASELINE_WEEKS | 8 | Counted weeks collected after each restart before Watch starts. |
| Fix | SPREAD_CHECKS | 4 | Before a fix: at most this many counted checks. |
| Fix | SPREAD_DAYS | 35 | Before a fix: checks from this many days before it was added. |
| Fix | AFTER_CHECKS | 4 | After a fix: at most this many counted checks. |
| Fix | MIN_AFTER_CHECKS | 3 | A fix is read only with at least this many counted checks after it. |
| Fix | FIX_NAMED_FROM | 0.5 | A question on one engine counts as named in the check that found the gap when at least this share of its answers named your store. |
| Fix | MIN_FIX_CELLS | 6 | A fix needs at least this many question and engine pairs that changed. |
| Fix | MIN_CONTROL_INTENTS | 10 | A fix is compared with your untouched questions only when there are at least this many. |
| Fix | PLACEBO_DRAWS | 1000 | Random redraws behind a fix's comparison with untouched questions and behind the range of your place. |
| Fix | FIX_ROLLUP_Q | 0.1 | When fixes are counted together, the share of false calls allowed among those called. |
| Movers | MOVERS_Q | 0.1 | In the list of questions that moved most, the share of false calls allowed. |
| Movers | MOVERS_POINTS | 20 | A question is listed only when it changed by at least this many points. |
| Movers | MOVERS_MAX_ROWS | 5 | The list shows at most this many questions. |
| Movers | MOVERS_CONCENTRATION_ROWS | 4 | When at least this many listed questions share one engine and one direction, the list says most of its moves are on that engine, in one direction. |
| Rank | MIN_DECISIVE | 30 | A place needs at least this many decisive answers. |
| Rank | RANK_FIELD_MIN | 5 | A brand joins the field of your place when it is ranked in at least this many answers, or in the share below of the step's ranked answers if that is more. |
| Rank | RANK_FIELD_SHARE | 0.1 | That share of the step's ranked answers. |
| Rank | RANK_FIELD_OTHERS | 9 | At most this many other brands are in the field. |
| Data quality | MIN_COVERAGE | 0.9 | A check counts as a week only when it collected at least this share of the questions asked on that engine. |
| Data quality | TRIGGER_EVENT_POINTS | 15 | A move of this many points in how often Google shows an AI Overview is marked on the chart. |
| Data quality | CACHE_RATE | 0.1 | When more than this share of answers in a check are exactly the same, the app flags that answers may be repeats, not new asks. |
| Data quality | FORMAT_RECALL_DROP | 10 | A drop of this many points in how many brands are found in one answer format is marked on the chart. |
| Site checks | SMALL_SAMPLE | 10 | Site checks and older readings: a change is shown only when both readings count at least this many. |
| Site checks | FLAT_POINTS | 2 | Site checks and older readings: a change under this many points is shown as no change. |
| Site checks | FLAT_COUNT | 2 | Site checks and older readings: a change under this many answers is shown as no change. |
| Names | NAME_LABEL_MAX_WORDS | 4 | A lead of at most this many words can be read as a section label, not a name. |
| Names | NAME_NOUN_MAX_WORDS | 3 | Only names of at most this many words are tested as everyday words. |
| Names | NAME_HEAD_MAX_WORDS | 2 | The first part two names share, or a known brand's name inside a longer one, is at most this many words. |
| Names | NAME_MAX_HOSTS | 3 | The most linked sites kept for each name. |
| Names | NAME_ADJ_MIN_HITS | 3 | A name counts as a brand's product when answers write it right after that brand at least this many times, and the next two rules hold. |
| Names | NAME_ADJ_MIN_SHARE | 0.1 | Those times are at least this share of the times the name is written. |
| Names | NAME_ADJ_OTHER_MAX | 0.2 | No other brand is written right before the name in more than this share of those times. |
| Names | NAME_CARD_ADJ_MIN | 2 | A name also counts as a brand's product when at least this many product card titles open with that brand and go on with the name. |
| Names | NAME_LOWER_MIN | 2 | A name answers write in lower case mid-sentence at least this many times can be an everyday word, not a name. |
| Names | NAME_LOWER_RATIO | 10 | It is one when it is written in lower case at least this many times as often as with a capital. |
| Names | NAME_WORDS_MAX_NAMES | 100 | The most names read in one answer for the words written around them. |
| Names | NAME_WORDS_MAX_SPELLINGS | 200 | The most brand spellings looked for right before a name in one answer. |
| Names | NAME_WORDS_MAX_AFTER | 5 | The most brands kept for each name as the ones written right before it. |
| Names | NAME_CARDS_MAX | 50000 | The most product cards read when names are sorted, the newest first. |
| Names | NAME_LIST_EVENT_NAMES | 3 | The brand list's change log gets an entry when at least this many names move in or out of the count. |
| Names | NAME_LIST_EVENT_SHARE | 0.05 | It also gets one when the names that moved held at least this share of the brand mentions counted. |
| Names | NAME_C2_ON | 1 | 1 when a name sold as a product on your store's site or a tracked brand's site counts as that brand; 0 when off. |
| Names | NAME_C3_ON | 1 | 1 when a name listed as the seller on product cards is a retailer; 0 when off. |
| Names | NAME_A2_ON | 1 | 1 when product card titles can make a name a brand's product; 0 when off. |
| Names | NAME_F2_ON | 1 | 1 when names that share a first word answers never write in lower case can count as one brand; 0 when off. |
Changelog
Each method version is dated the day it took effect. A version that counts history again says so, with the figures that moved; a change mark or a Day 28 fix reading that comes out differently is shown as restated, with the day.
Version 3, Nov 14, 2026
- Shares and places count brands only: your store, the competitors you track and other brands AI names. Retailers, publications, sites AI only linked to and names that are not brands are left out; retailers get a line of their own. A store named beside only retailers counts as named alone.
- New word rules sort the names: a product written right after its brand counts as that brand, in shares, places and Named; a spec, a section label or a joined phrase is not a name; a site selling other brands' products is a retailer; a name the rules counted is matched only where written with a capital, unless you counted it. Names the rules can't sort count as competitors until you sort them, and your choices always win. The rules' thresholds join the method.
- Every stored check is counted again with version 3, free. Every change mark that stood under version 2 is restated from 14 November 2026. The answer-shape watch is rebuilt from the recounted weeks. Each Day 28 fix call is read again at a coming weekly sweep and shows the day it was restated; a call whose answers are no longer kept stays as it was.
- History counted again: yes. Series that moved:
vis.mentionShare,vis.trackedShare,vis.named,rep.rank,rep.rankedFirst,brandsPerAnswer,noBrandShare,cuesPerMention,structuralRecall,answer_format_changed, Day 28 fix calls.
Version 2, Nov 9, 2026
- Two rules joined the method under version 1 without an entry of their own: the same-questions line keeps the questions asked in at least 75% of the weeks shown, and your place is counted among your store and at most 9 other brands, each ranked in at least 5 answers or a tenth of the stage's ranked answers, whichever is more.
- No counting rule changed value. Likely ranges drawn at random are drawn again, so your place, a mention share or place change, or a Day 28 fix reading can shift slightly, and a change mark or fix call close to the line can come out differently.
- Every stored reading is counted again with version 2. Every change mark that stood under version 1 is restated from 9 November 2026. Each Day 28 fix call is read again at a coming weekly sweep and shows the day it was restated; a call whose answers are no longer kept stays as it was.
- History counted again: yes. Series that moved:
rep.rank,vis.mentionShare, Day 28 fix calls.
Version 1, Nov 8, 2026
- First method: a percentage is shown from 30 effective answers, and a change is called only when the same questions moved more than normal week-to-week variation.
- History counted again: no. Series that moved: none.