calculator · August 10, 2026

Valuefy operator publishes 28-day GSC audit: US dominates impressions at 5,328 while clicks stay at 2, and the discount calculator still ships duplicate og:title tags

What the sources reported

What changed in the 28-day window

Valuefy site operator Aimiten released an audit on 2026-08-09 measuring Google Search Console performance across a 28-day window. 5 clicks per day, up from a 90-day baseline of 45 clicks. The audit links that lift to an automation cadence of one calculator-page commit per day since June 30, with the prior seven days covering ROAS, Burn Rate, CPA, CTR, CPC, Valuation Multiple, and Book Value calculators, following 33 earlier pages in real estate, startup finance, equity, valuations, and compound interest.

The country split is the most striking change in the data set. Eight weeks earlier the USA did not appear in the top-20 countries by impression volume. In this 28-day window it ranks first.

4, which the audit places on page five or six of Google. 7, Philippines at 541 impressions and 1 click, and Indonesia at 511 impressions and 2 clicks. India still produces the most actual clicks, 12 of 37 country-level clicks, but the USA now contributes the largest impression share.

The report explicitly states that no hosting region was changed and no US-specific content hooks were added during the period in question, leaving the cause unstated.

The discount calculator at position 18.1

The discount calculator page is the case study in the report, and the page-level data set it apart. 1. 9, which is where the report says genuine purchase intent lives.

Visible query rows account for 85 impressions, only 6% of the 1,400 total, with the rest hidden below GSC's privacy threshold. 0. None of those queries converted into clicks.

0, also with zero clicks. The report argues that these fragments are arithmetic-style queries, not discount intent, and that Google's auto-complete behaviour is surfacing a calculator-style page at position 1 for queries with no purchasing purpose. 9 is presented as direct evidence that mismatched-intent impressions are pulling the aggregate downward, and that the real competitive position is far weaker than the rolled-up number suggests.

Mismatched intent and the arithmetic-noise hypothesis

The report's central analytical contribution is naming a new failure mode distinct from the long-tail averaging trap it flagged earlier. That earlier trap built a flattering aggregate from many small relevant queries. The new failure mode, labelled arithmetic noise in the audit, ranks the page at position 1 for queries whose intent does not match the page at all.

", "1490", "4600", and "450 mil", all single-number or fragment queries that return the discount calculator page as a numeric answer surface, register an impression, and never click. The result is an impression total inflated by users who were never shopping for a discount calculation. 9, with the query breakdown pending.

9 would suggest, and contaminates engagement signals sent back to Google. The report does not soften this. It states that the user typing "1490" into Google does not want this calculator, and concludes that the discount calculator's 1,400-impression total contains an unknown share of non-converting noise below the privacy threshold, meaning the true performance figure could be materially worse than the visible 85 impressions imply.

The og:title duplication that survived the first audit

The report's second high-risk finding is a bug that was supposed to be fixed and was not. html and one page-specific tag injected by React Helmet at prerender. " A curl of the discount calculator page during the week of this audit shows both tags still present.

" The dynamic tag reads "Free Discount Calculator — Sale Price, Stacked & Reverse," with data-rh confirming React Helmet. The report treats this as a confirmed ongoing bug, not a rumour, and the duplication is observable in the served HTML. Because Open Graph tags control how links preview on social surfaces and feed some crawler signals, shipping two competing og:title values per page is treated in the audit as a measurable defect with a known fix that has not landed.

The report attributes no traffic consequence to the duplication in this 28-day window and offers no estimate of click or impression lift from fixing it, but the framing leaves the bug as an open liability rather than a closed item, and readers tracking the operator's earlier promise have a clean before-and-after to verify once the static tag is removed.

What readers should watch next

Three items are worth monitoring, and the audit itself does not commit to a date for any of them. 9; confirming or disproving the hypothesis there would tell readers whether the 1,400-impression discount case is a one-off or a pattern across the calculator suite. html, which would convert the second high-risk claim from open to closed, since the same curl test used this week can be re-run.

4. The report frames all three as open, and the deterministic test for each is the same shape of audit work the operator has already published.

Evidence

Tools that already cover this

calculator decision room

Decision · EXPERIMENT · confidence 65/100

Theo Ashby closed the calculator thread with EXPERIMENT, owner Sloane Barrett, fourteen-day window, success metric a completed calculation event on the Discount Calculator, and kill metric under twenty completions or zero repeat visits. Confidence is moderate: Sloane, Felix Brandt, Maeve Carver, and Evan Marsh support the experiment, while Ellis Pryce, Vera Sinclair, and Viktor Salz oppose locking the category into a one-tap widget before completion evidence arrives. The panel's central trade-off is intent interpretation, since a snippet that reads like price-chasing may simply be a number hunt. The decision reverses if completion logs stay flat for seven consecutive days, or if a server-rendering bug is identified that explains the position-18 placement.

Discussion

10 messages · grounded in the same frozen signal set

Sloane Barrett
Shareability Strategist · Marketing · #1 · Conditional · Concerned
Yesterday our team caught something weird on the Discount Calculator page: someone ranked at position 18 for the queries "130?" and "Da," and the snippet reads like a user chasing a price. That is a real discount intent signal, not noise. For our calculator category it means users are hunting for a specific number on the cheap. I would build a one-tap "is this 130 worth it?" widget and A/B test it on the page to see if recipients finish a calc. Worth opening a thread, or am I chasing a ghost query?
1. Felix Brandt
  Rendering and Discovery Specialist · Seo growth · #2 · Conditional · Concerned · Reply to Sloane Barrett
  Sloane, that "130?" ranking is a server-rendering question hiding inside a marketing read. If the Discount Calculator ships its primary answer behind hydration, position 18 is the loudest clue that crawlers never see the calculation path. Anonymous-fetch the page with scripts disabled and confirm whether the discount result appears in the static HTML before any interaction; that single snapshot will prove whether the widget can even be indexed. The concrete consequence for our calculator category is that users hunting a number get a blank shell where the math should be.
2. Maeve Carver
  Monetization Strategy Lead · Revenue · #3 · Conditional · Concerned · Reply to Sloane Barrett
  Sloane, "chasing a price" is not the same thing as willingness to pay for a calculator - they could just want the $130 number for anything. One query at position 18 is not trade-off evidence; watch whether repeat users return and what alternative they abandon before we build that widget. Run a 30-day behavioral test on ad-supported vs subscription packaging before shipping anything.
3. Evan Marsh
  Product Outcome Lead · Product · #4 · Conditional · Concerned · Reply to Sloane Barrett
  Sloane, Maeve already halved your theory - "130?" is a number hunt, not a price hunt, so a one-tap "worth it" widget would test the wrong behavior and waste the calculator category's clearest intent signal. Let's ship a thin results page that simply answers the bare query, then measure completed calculations before adding anything else.
4. Ellis Pryce
  Frontend Performance Engineer · Engineering · #5 · Oppose · Skeptical · Reply to Sloane Barrett
  Sloane, I will give you this: a position-18 hit on "130?" is a real SERP signal worth tracking, not fiction. Where it breaks for me is the read of intent - one snippet reads like price-chasing, but a calculator path demands the full numeric journey, and a one-tap "worth it" widget will execute JavaScript on the critical path before the user even enters the figure, which on a low-end phone pushes INP past 200ms and burns bytes no one asked for.
5. Vera Sinclair
  Trend and Opportunity Analyst · Trend · #8 · Oppose · Skeptical · Reply to Sloane Barrett
  Sloane, you are right that a position-18 SERP hit on the Discount Calculator page is a real artifact, not nothing. It breaks where you call "130?" a price hunt, since Maeve and Evan already split that into a bare number hunt with no willingness-to-pay reading behind it. For the calculator category that means shipping a one-tap "worth it?" widget tests the wrong behavior and risks a quiet metric rebound. I would hold a seven-day watch on repeat queries and completion logs before any build.
6. Viktor Salz
  Backend Data Engineer · Engineering · #9 · Oppose · Skeptical · Reply to Sloane Barrett
  Sloane, you're right that a position-18 hit on "130?" is a real SERP artifact and worth tracking, not fiction, and I'll concede the user is clearly hunting a specific number on the Discount Calculator page. Where the thread breaks is that nobody has proven what happens after the click, so we cannot bind durable writes to intent we have not measured. The trade-off is a widget that persists no verified task completion while locking the category into a template before evidence arrives.
Theo Ashby
Chief Executive · Product · #6 · Question · Curious
Sloane, Maeve, Ellis, I need Tess to weigh in here before I commit anything to the calculator category. The whole debate rests on whether that position-18 hit is a stable rendering quirk or a real query the SERP keeps rewarding us for, so if we bet calculator roadmaps on "130?" being a buyer signal and it turns out to be a server artifact, we have shipped a widget nobody actually wanted.
1. Tess Rowan
  Site Reliability Engineer · Engineering · #7 · Conditional · Concerned · Reply to Theo Ashby
  Theo, I won't greenlight calculator roadmap bets on a position-18 "130?" SERP hit until we prove a real user completed a task, not just observed the page. From the on-call chair, position 18 with a snippet reading like a price chase is consistent with a server-rendering artifact surfacing during a Discount Calculator prerender, not evidence of buyer intent. Concrete consequence for the calculator category: we would ship a one-tap widget against a stable rendering quirk, then watch success metrics look healthy on dashboard averages while the Discount Calculator subgroup quietly serves nothing.
Theo Ashby
Chief Executive · Product · #10 · Conditional · Decisive
Closing the calculator thread: Tess is right, a position-18 hit on "130?" is a number hunt, not proof someone finished a calculation, so I will not greenlight roadmap work yet. We treat the artifact as evidence the page gets found, not evidence the calculator solved a job. Concretely, the calculator category carries zero conversion signal until we prove a real user completed a task. Next move: EXPERIMENT, owner Sloane, fourteen-day window, success metric a completed calculation event on the Discount Calculator, kill metric under twenty completions or zero repeat visits.