Technical SEO · 21 Nov 2026 · 5 min read
Page experience and mobile usability: what still matters for search
Google has changed how it talks about page experience and has retired some mobile reports. This guide explains what remains useful and what order to fix things in.
The short answer
Google says page experience is not one single ranking signal. Its systems favour helpful content first, and aspects such as Core Web Vitals, security and mobile use still count towards a good experience. The old Mobile Usability report and Mobile-Friendly Test were retired, so you now check mobile use yourself. Fix blocked content and unreadable layouts before small speed gains.
Is page experience a ranking factor?
The honest answer is: partly, and not as one score. Google's Search Central guidance has said that it looks at many aspects of how a page works for people, not at a single page experience number. Its ranking systems reward helpful, relevant content first. Having a good experience can contribute to success in search, but it does not make up for a page that does not answer the question.
The older idea of a "page experience update", which combined Core Web Vitals, secure connections, mobile-friendliness and intrusive pop-up rules, has been superseded by that broader guidance. Google has also changed the page experience report in Search Console so that it points to general guidance, with views of Core Web Vitals and secure connection data. Because this area has changed more than once, check the current documentation before relying on any older advice.
What this means in practice: do not chase tiny technical scores at the expense of content. Do remove the things that make a page hard to use, because those cost you visitors whatever search engines do.
What changed in the reports
Two tools that many owners used are no longer available. Google retired the Mobile Usability report in Search Console and the Mobile-Friendly Test in late 2023. Its announcement said mobile usability remains part of its page experience guidance, because so many people browse on phones. The tools went, the principle stayed.
Core Web Vitals reporting still exists in Search Console for pages with enough data. The set of metrics has changed over time, for example Interaction to Next Paint replaced an older responsiveness measure. Our guide to checking a mobile-friendly website shows hands-on ways to test now that the dedicated report is gone.
If you see an old article telling you to pass a mobile test or to fix a specific report, check the date. Much of it is out of date.
What mobile usability problems look like
The retired report used to flag a handful of common faults. Those faults still hurt visitors, so use them as a checklist.
- Text too small to read without zooming.
- Buttons and links too close together to tap accurately.
- Content wider than the screen, forcing sideways scrolling.
- The page not set up for different screen sizes, so it shows a shrunken desktop layout.
- Pop-ups or banners that cover the content, especially on first load.
- Forms that are hard to complete on a phone, with fields that do not use the right keyboard.
- Menus that do not open, or open and cannot be closed.
It also helps to test the whole path, not single pages. Start from a search result on a phone, open the page, read it, find the contact or buy step and complete it. Note every moment where you hesitate, zoom or go back. Those moments are the real list of problems, and they usually matter more than any number from a tool.
Test on a real phone as well as in a desktop browser's mobile view. Use a slower connection if you can, and test the pages that matter: the home page, a service page, a contact page and any page with a form.
What should I fix first?
Put things in this order, from most harmful to least.
- Anything blocked, broken or hidden behind something that fails on a phone comes first.
- Layout faults that stop use: sideways scrolling, overlapping elements, buttons that cannot be pressed.
- Intrusive overlays that cover the page before anyone has read a word.
- Slow loading of the main content. Use Search Console's Core Web Vitals report and a speed tool to find the worst pages.
- Unstable layout, where things jump as the page loads.
- Readability: font size, line length and contrast.
- Small speed gains after that.
Do not forget the content itself. A readable page on a phone has short paragraphs, descriptive headings and tables that fit the screen or scroll cleanly. Long unbroken blocks of text are tiring on a small display, whatever the speed score says.
Keep a short record of what you change and when. If traffic or enquiries move afterwards, you will know which change to look at, and you will not be guessing from memory. Fix one group of problems at a time where you can, so the effect of each change is easier to see.
Fixing the first three often matters more than a modest gain in a speed score. A page that loads a fraction faster but still has an unreadable layout is no better for the visitor.
A page-type view
Different pages call for different priorities.
| Page type | Main thing to check on mobile |
|---|---|
| Home page | The first screen: is it clear what you offer and how to get in touch? |
| Service page | Reading comfort, and a visible way to enquire |
| Contact page | Tappable phone and email, a short form, a clear map or address |
| Landing page | Speed and one clear action |
| Blog post | Text size, images that fit, tables that do not overflow |
Our guide to what a contact page should include covers the page where mobile problems cost the most, since a visitor who cannot tap to call or send a message is a lost enquiry. A page built to convert has different needs from a blog post, a difference explained in landing page SEO versus blog post SEO.
Where page experience shows up in real data
You do not need a score to know when a page frustrates people. Look at behaviour: where visitors leave, which pages have high exits on mobile only, and what they search for next. Your own site search often reveals a navigation problem, as shown in our piece on internal search data. If phone users search for your contact details, the menu is not helping them.
Ask someone who did not build the site to try it, ideally someone older or with a smaller screen than yours. Fresh eyes find faults that the team has stopped noticing, and the sessions cost almost nothing.
Files that open badly on a phone are another source. A large PDF that is hard to read on a small screen gives a poor visit, which is one reason for the advice in our guide to PDFs and downloads in search.
If you want an independent review of mobile and technical issues, our SEO service includes a technical check.
Related guides
- SEO services
- Contact page what to include
- Landing page seo vs blog post seo what changes
- Mobile friendly website what it means and how to check
Questions and answers
Is page experience a ranking factor?
Google says it is not a single signal. Its systems favour helpful content, and aspects of experience such as speed, stability and mobile use can contribute. It will not make up for a page that fails to answer the question. Check the current documentation for the latest wording.
What do mobile usability reports flag?
The retired Search Console report flagged small text, tap targets too close together, content wider than the screen and a missing viewport setting. The report is gone, but those problems still affect visitors, so test on a real phone.
What should I fix first?
Fix anything that stops content being read or used on a phone, then layout faults, then intrusive overlays, then slow main content. Small speed gains come last.
Is there still a mobile-friendly test?
Google retired the Mobile-Friendly Test and the Mobile Usability report in 2023. You can test using a real phone, your browser's developer tools and speed tools. Check the current documentation for tools Google offers now.
Do Core Web Vitals still matter?
They are still part of how Google describes good page experience, and Search Console reports them where data exists. Treat them as a guide to real problems, not as a score to chase beyond what helps visitors.
Do pop-ups hurt search?
Overlays that cover the content can make a page hard to use, and Google has long advised against intrusive ones. Banners required by law, such as consent notices, are a different case, but keep them small and easy to dismiss.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.