tech

How to fix: Mobile rendering: viewport + no fixed widths

Why this matters

Google's mobile-first indexing means a page that fails mobile rendering is indexed in a degraded state — bad for both rankings and CTR. Basic signals: viewport meta tag, no fixed-width containers, no horizontal scroll.

Background

Google's mobile-first indexing means a page that fails mobile rendering is indexed in a degraded state — bad for both rankings and CTR. Basic signals: viewport meta, no fixed widths, no horizontal scroll.

References

Google Mobile-Friendly Test · Mobile-first indexing

How to fix

Code snippet for each stack we cover. Pick the one matching your server / framework.

nginx

No server config.

apache

Same.

cloudflare

Same.

wordpress

Pick a responsive theme (most modern ones are). If your theme has fixed-width containers in its CSS, switch.

flask

Audit CSS for fixed `width: NNNpx` declarations >= 480px. Replace with `max-width: 100%` or media queries.

express

Same.

rails

Same.

Verify it's working

Open the page in Chrome DevTools → Device Mode → iPhone. No horizontal scroll. Text legible. Tap targets >=48px.

Want to know if your site has this issue?

Run a free 53-check audit — security, GDPR, NIS2, and technical SEO.

Audit my site →