Getting found online · Updated October 23, 2026
Does it matter if my website hides content on phones?
Updated October 23, 2026
It matters only if the content is gone from the phone version, not tucked away. Google ranks your site from the phone version, so text in an accordion or tab still counts, but a section the phone page leaves out, or loads only after a tap, counts for nothing. Check what Google sees with URL Inspection.
If the content is folded away on phones, leave it; if it is removed, put it back
If your website hides content on mobile that it shows on a computer, what matters is how it is hidden. Text folded into an accordion, a tab or a "read more" is still in the page, and Google reads it. Text the phone version leaves out, or fetches only after someone taps, is not in the page Google reads, and it stops helping you rank.
This matters because Google reads the phone version first. Google's documentation says it "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." Google finished moving every site that works on phones to this in October 2023, when it announced that "a mobile web page now needed to be as complete as the corresponding desktop version." The desktop page your customers see at the office is no longer the one being judged.
So the question is not whether a section is visible on a small screen. It is whether its words are in the phone page at all. Three kinds of hiding cover almost every site, and each has a different answer.
Find out which kind of hiding your site does
Run a live test in Search Console and search the tested page for the hidden words
If you have Search Console, open URL Inspection, paste the page's address and select Test live URL. Then select View tested page. Google's help says it shows "a screenshot of the rendered page, the raw HTML returned, the HTTP headers" and more, so you can see the page as Google's crawler fetched it. Google crawls with its smartphone agent, so read it as the phone page.
Search that HTML for a sentence from the section you hid. If the sentence is there, the content is folded away and Google reads it. If it is missing, the phone page does not carry it, and Google ranks the page without it.
- In Search Console, paste the page's address into the search bar at the top to open URL Inspection.
- Select Test live URL and wait for the result.
- Select View tested page and open the page's HTML in the panel.
- Search the code for a sentence from the hidden section.
What if I do not have Search Console?
Open the page on your phone and use the browser's Find in page for a word from the hidden section. Text marked hidden until found is found and opened by Find in page; MDN says content in that state "will be accessible to the browser's 'Find in page' feature." No match does not prove the words are gone, since many accordions hide text in ways Find in page skips, so treat it as a quick first look and use Search Console to settle it.
Know the three kinds before you change anything
Each kind needs a different fix, and only one of them is safe to leave as it is.
Folded away.
An accordion, a tab, a slider or a "read more" link. The words are in the page and appear when someone taps. Google reads them.
Removed on phones.
A builder's "hide on mobile" switch that leaves the section out of the phone version, or a separate mobile site with less on it. Google does not read what is not there.
Loaded on tap.
The section is fetched only when someone scrolls, swipes or taps. Google does not tap, so it never sees the words.
What to do about each kind
Leave accordions and tabs alone: Google reads them and its spam rules allow them
If your phone page folds long sections into accordions or tabs, nothing needs fixing. Google's own mobile guidance suggests it: "Instead of removing content, consider moving content into accordions or tabs to save space."
Some owners worry that hidden text is a spam signal. Google's spam policies do list hidden text, such as "white text on a white background" or "setting the font size or opacity to 0," but they describe it as hiding content "solely to manipulate search engines." The same policy then names designs that "don't violate our policies," starting with "accordion or tabbed content that toggle between hiding and showing additional content." A drop-down a customer can open is not what that rule is about.
If a section is removed on phones, put it back, folded if it is long
If the live test shows a section missing from the phone page, turn off the "hide on mobile" setting for it in your site builder or ask your developer to include it. Google's guidance is direct: "Make sure that your mobile site contains the same content as your desktop site." It also says what happens if you do not: "you can expect some traffic loss when your site is enabled mobile-first indexing, since Google can't get as much information from your page as before."
The sections owners hide most are often the ones that rank. A list of the towns you serve, a block of reviews, a detailed description of each service, or a frequently asked questions section all look like clutter on a small screen, and they carry the words a local customer types into Google. If a section is long, fold it into an accordion rather than cutting it.
Google's own warning
Some traffic loss
is what Google says to expect when the phone page carries less than the desktop page.
For example
A roofing company's service page listed the 14 towns it covered, with a short paragraph about storm work in each. On phones the builder's "hide on mobile" switch dropped that whole block to keep the page short. Searches that named a town showed the page less and less, because the version Google ranked no longer named any of them. Moving the list into an accordion that started closed kept the phone page short and put every town back in front of Google.
If a section loads only when someone taps or scrolls, have it load with the page
If the section's words appear in your browser but not in the live test's HTML, the site is probably fetching them on demand. Google's lazy-loading guide explains why that fails: "Google Search does not interact with your page." Its mobile guidance says the same in one line: "Don't lazy-load primary content upon user interaction."
Ask your developer for one of two fixes. Either load the text with the page and fold it with an accordion, or load it when it comes into view on the screen rather than on a tap. Google says loading content "whenever it is visible in the viewport" works, using the browser's built-in lazy loading or the IntersectionObserver API, because those "don't rely on user actions, such as scrolling or clicking." Then run the live test again and confirm the words are in the HTML.
Match more than the text: headings, structured data, titles and image alt text
If your phone page is built separately from the desktop page, check that everything around the words matches too. Google's mobile guidance asks for each of these on both versions:
- Headings: "the same clear and meaningful headings on the mobile site as you do on the desktop site."
- Structured data: "make sure that your mobile and desktop sites have the same structured data." Missing structured data on the phone page is the first error in Google's troubleshooting list.
- Title and description: the title element and meta description should be "equivalent across both versions of your site."
- Images: the same important images and "the same alt text for images as the desktop site."
- Robots tags: the same robots meta tags on both, since a noindex on the phone page means "Google won't index your page."
A site built with responsive design avoids all of this. Google calls it the design that "serves the same HTML code on the same URL regardless of the users' device," and says that with it, "the content and the metadata are the same on the mobile and desktop version of the pages." Most modern builders and themes work this way.
What if my site has a separate mobile address, like m.example.com?
A separate mobile site needs extra care, because every mobile page is a different address. Google asks that the desktop page carry a rel=alternate link to the mobile page and that both name the desktop address as canonical, that both versions return the same error status, and that mobile pages not "redirect to the same URL (for example, to the home page on mobile devices)," which it says leaves "all these pages" missing from the index. Verify both versions in Search Console. Moving to a responsive design removes the whole category of problem.
Before you hide anything, think about the people reading on phones
Fit the content to the screen instead of hiding it, and hide nothing from screen readers by accident
If a section is hidden because it breaks the layout on a phone, fix the layout instead. The accessibility standard most websites are measured against, WCAG, asks that content be readable "without requiring scrolling in two dimensions" at a width of 320 CSS pixels, and notes that a common way to meet it is a page that can "adjust to a single column of content." A section that stacks into one column on a phone rarely needs to be hidden at all.
Some ways of hiding remove content for everyone, not just for small screens. MDN says the hidden attribute "must not be used to hide content just from one presentation," because something marked hidden "is hidden from all presentations, including, for instance, screen readers." A customer using a screen reader on a phone loses that section completely. An accordion built on the details element is the safe pattern: it starts closed, opens on a tap or the space bar, and keeps its contents in the page.
Then measure the phone version, not the desktop one
If you check your site's speed or quality, check the phone results first. PageSpeed Insights reports "on both mobile and desktop," with lab data from Lighthouse covering "performance, accessibility, best practices, and SEO." Since the phone page is the one Google ranks, its score is the one that counts. Run it on the pages that bring you work: the home page, each service page and your contact page.