Official statement
Other statements from this video 38 ▾
- 21:28 Do sitemaps really trigger a quick recrawl of your modified pages?
- 21:28 Can you really force Google to recrawl immediately after a price change?
- 40:33 Does CSS font size really impact your positions on Google?
- 70:28 Is it true that content concealed behind a Read More button is actually indexed by Google?
- 70:28 Is it true that content hidden behind a 'Read More' button is actually indexed by Google?
- 98:45 Does internal linking truly overshadow the sitemap in signaling your strategic pages to Google?
- 98:45 Is Internal Linking Really More Crucial Than a Sitemap for Prioritizing Your Pages?
- 111:39 Why Doesn't the Search Console API Show Referring URLs for 404 Errors?
- 144:15 Why does Google keep crawling 404 URLs that are years old?
- 182:01 Should you really be worried about having 30% of URLs as 404s on your site?
- 182:01 Can a high 404 rate really hurt your SEO rankings?
- 217:15 How can you effectively target multiple countries with a single domain without losing your local SEO?
- 217:15 Can you really target different countries on the same domain without using subdomains?
- 227:52 Should you really use hreflang when targeting multiple countries with the same language?
- 227:52 Should you really combine hreflang and geographical targeting in Search Console?
- 276:47 Why do your structured data breadcrumbs not show up in the SERPs?
- 285:28 Why do your rich results vanish from the standard SERPs while still appearing in site searches?
- 293:25 Do Invisible Breadcrumbs Really Block Your Rich Results on Google?
- 325:12 Should you really be optimizing JavaScript hydration for Googlebot in SSR?
- 347:05 Is it true that word count doesn't matter for ranking on Google?
- 347:05 Is the number of words really a ranking factor for Google?
- 400:17 Does the traffic volume of your site affect your Core Web Vitals score?
- 415:20 Does traffic volume really influence your Core Web Vitals?
- 420:26 Does content relevance truly outweigh Core Web Vitals in Google rankings?
- 422:01 Can Core Web Vitals Really Boost Your Ranking Without Relevant Content?
- 510:42 Is it true that Google can't always show the right local version of your site?
- 529:29 Is it really necessary to duplicate all country codes in hreflang for targeting multiple regions?
- 531:48 Why does hreflang in Latin America require each country code individually?
- 574:05 Does PageSpeed Insights really measure your site's performance?
- 598:16 Is it really possible to shift from long-tail to short-tail without changing strategy?
- 616:26 Can you really hide dates from Google search results?
- 635:21 Should you stop updating publication dates to boost your SEO?
- 649:38 Does Google really rewrite your titles to help you out?
- 650:37 Can you really stop Google from rewriting your title tags?
- 688:58 Should you really report SERP bugs with generic queries to expect a response from Google?
- 870:33 Should new e-commerce sites prove their legitimacy outside of Google first?
- 937:08 Is it true that the length of the title really impacts Google rankings?
- 940:42 Is it true that the length of title tags really impacts Google's rankings?
Mueller clarifies: the difference between 12px and 14px has no impact on your positioning. What matters is mobile compatibility, which remains an active ranking factor. The rest is pure UX — important for conversions, invisible to the algorithm.
What you need to understand
Why does Google differentiate between font size and mobile-friendliness?
Mobile-friendliness measures the overall accessibility of a page on smartphones: configured viewport, spacing of touch links, absence of content wider than the screen. It's a binary criterion tested via Mobile-Friendly Test.
Font size, on the other hand, is a design element. 12px or 14px affects visual comfort but does not break mobile navigation. Thus, Google clearly separates what obstructs usage (ranking criterion) from what improves it (UX with no direct algorithmic effect).
Does this statement contradict the Core Web Vitals?
Not really. CWV measure perceived performance: loading, interactivity, visual stability. Text size is not included in these metrics.
However, text that is too small can cause unintentional zoom on mobile, degrading the experience and potentially impacting CLS if the layout shifts. But Mueller is talking about direct ranking here — and in that case, font size alone doesn’t matter.
Should typography be ignored then?
No. Illegible text drives visitors away, destroys engagement rates, and kills conversions. Google may not rank based on font, but behavioral signals (dwell time, pogo-sticking) certainly speak.
Mueller’s message is clear: optimize for humans first. If your 12px causes massive bounce rates, your ranking will suffer — but by ripple effect, not by direct penalty on font size.
- Mobile compatibility has been an official ranking factor since 2015 (mobile-friendly update).
- Font size is not an isolated algorithmic criterion, contrary to popular belief.
- Indirect UX signals (engagement, conversions) can compensate for or amplify the effect of poor design.
- The Mobile-Friendly Test checks 16px minimum recommended for readability, but it's a recommendation, not a ranking threshold.
- A font that is too small can trigger automatic iOS zoom (16px threshold on form fields), which degrades the experience.
SEO Expert opinion
Is this statement consistent with real-world observations?
Yes and no. Over thousands of audits, I have never seen a site rank better after switching from 12 to 14px with all else being equal. No SEO A/B test shows a direct correlation. [To check], however: the indirect impact via engagement is measurable.
Sites with 11px in light gray on a white background show catastrophic metrics (40% higher bounce). When corrected, time on page increases, organic CTR improves — and six months later, pages gain 5-10 positions. But Google will attribute that to behavioral signals, not to CSS font size.
What nuance does Mueller deliberately omit?
He doesn't mention critical accessibility thresholds. Below 12px, some browsers force a minimum zoom, break the viewport, and trigger the flag “text too small” in Search Console. There, one transitions into non-compliance with mobile standards — and Mueller has said that does matter.
Another blind spot: heavy custom fonts that hurt LCP (Largest Contentful Paint). A Montserrat at 14px that takes 300ms to load can kill your CWV. Mueller discusses size, not weight — yet it's the weight that impacts ranking via Core Web Vitals.
In what cases does this rule not apply?
If your font triggers Search Console errors (“Content wider than screen”, “Clickable elements too close together”), you are no longer in the 12 vs. 14px debate. You are in non-compliance with mobile-friendliness, and then ranking suffers.
Finally, for high commercial intent queries (“buy X”, “best Y”), microscopically small text spikes e-commerce bounce rates. Google does not view it as “bad font”, but as “page not satisfying intent”. Identical results: you drop.
Practical impact and recommendations
What should be done concretely on your pages?
Focus on overall mobile compliance, not on typography pixels. Run Google’s Mobile-Friendly Test on your main templates. If it turns green, you are clean on the ranking side.
For font size, aim for 16px minimum on mobile body — not because of algorithmic obligation, but because that's the universal comfort threshold. Below that, you force zoom on iOS, which breaks UX and triggers negative indirect signals.
What mistakes should be absolutely avoided?
Don't fall into the trap of typographical over-optimization. I've seen clients spend days A/B testing 13 vs. 14px hoping to snag some ranking. Zero impact. That time would be better spent correcting 404 links, improving internal linking, or working on content depth.
Another classic mistake: unoptimized custom fonts. A poorly compressed .woff2 file delays text rendering (FOIT), degrades First Contentful Paint, and can kill your CWV score. Use font-display: swap, preload critical fonts, and limit yourself to 2-3 variants at most.
How can I check if my site is compliant?
Open Search Console, go to Mobile Usability. If Google flags “Text too small to read”, you have a problem — but it’s rarely just the font size; often it's an issue with the viewport or zoom turned off in the meta viewport.
Then test on real devices: iPhone SE (small screen), Galaxy S10, iPad mini. If you have to zoom to read, your visitors will too — and Google will see that through low engagement signals. Correct this before it impacts your traffic.
- Check Search Console > Mobile Usability for blocking errors
- Validate the viewport meta (width=device-width, initial-scale=1) on all templates
- Test actual readability on a 5-inch smartphone (current minimum threshold)
- Optimize font loading (woff2, font-display swap, preload)
- Measure UX impact: time on page, scroll depth, mobile vs. desktop bounce rate
- Prioritize quick wins (contrast, line-height) before refining pixels
❓ Frequently Asked Questions
Une police de 12px peut-elle pénaliser mon site ?
Le passage de 12px à 16px améliore-t-il le SEO ?
Quelle est la taille de police recommandée pour le mobile ?
Les Core Web Vitals prennent-ils en compte la typographie ?
Comment savoir si ma police pose problème sur mobile ?
🎥 From the same video 38
Other SEO insights extracted from this same Google Search Central video · duration 985h14 · published on 26/02/2021
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.