Technical Readiness

Animated stat counters can read 0 to AI crawlers: how to check and fix them

A count-up counter looks right in a browser, ticking from 0 to the real number as the visitor scrolls. Whether an AI engine reads that number depends on what's in the HTML underneath.

Updated 2026-11-02

Questions this guide answers

Can AI crawlers see animated number counters?
Why does my page source show 0 instead of my stat?
How do I make an Elementor counter readable to AI search?
Do Divi number counters show up for search engines?

Direct answer

If a stat on your page counts up as visitors scroll to it, check the HTML your server sends, because that's the copy a crawler that doesn't run JavaScript reads. Counters built with Elementor, Divi, and Kubio put a 0 or an empty slot there and keep the real number in an attribute that only their script reads.

To check, open the page's source and look at the number each counter shows as text, not the one in its attributes. To fix it, make the HTML carry the real number: in Elementor, set Starting number to the same value as Ending number; in Divi and Kubio, replace the counter with a text or heading block that shows the number.

Why crawlers can miss the number

A crawler that reads the HTML without running the script gets the placeholder, so a model working from that copy reads a stat like "40 hours saved per month" as "0 hours saved per month."

Google renders JavaScript but notes that "not all bots can run JavaScript," and OpenAI, Perplexity, and Anthropic don't say whether their crawlers do (how each engine fetches pages). A number that exists only after a script runs is one you can't count on an AI engine to read.

Builder	What the HTML shows	Fix
Elementor (Counter widget)	The Starting number, 0 by default	Set Starting number to the Ending number. The count-up stops.
Divi (Number Counter module)	Nothing; the number's slot is empty	Divi counts "up from zero" and has no setting to change that. Use a Text module.
Kubio (Counter block)	The start value, usually 0	Use a heading or paragraph block.

Check your pages

Start with the pages that carry your proof, such as the homepage, product and pricing pages, and case studies. On each one:

Open the source. In Chrome, type view-source: before the URL, or right-click and choose View Page Source. Don't use Inspect: it shows the page after scripts ran, so the real number appears there and hides the problem.
Find the counters. Search for data-to-value (Elementor), data-number-value (Divi), or data-kubio-component="counter" (Kubio). Each match is one counter.
Read the number it shows as text. That's the text inside the counter's tag; for Divi, inside its percent-value span. If that text isn't the real number, the counter needs the fix.
After the fix, reload the source and check that the real number now appears as text.

How SolCrys checks for it

A SolCrys Content Audit checks for this: it flags counters whose HTML doesn't show their real number and gives the fix.

Sources

FAQ

Do other parts of a page hide content the same way?

Yes. Anything a script adds after the page loads can be missing from the HTML the same way. The view-source test works for all of them, and the AI crawler and answer readiness checklist covers the rest of what a crawler needs.

Free ChatGPT visibility check

See where AI answers skip your brand — then fix it, free

Start a free workspace with your domain: 10 buyer-intent prompts through ChatGPT show where you are mentioned, cited, or skipped, and who gets recommended instead. A free content audit in the same workspace hands you the first fix to ship.

Start Free

Free · No credit card · About 5 minutes

Related guides