大网数据广告活动
网站运营与故障问答

Content hidden on mobile responsive design

· 52CE 我爱测

As much as this should have been a well-covered issue, I couldn't find a definite answer to this specific question anywhere. We run a scientific website which displays lots of well-established data about biological entities (such…

问题原文

原帖链接 · Ofer Zelig · CC BY-SA 4.0

As much as this should have been a well-covered issue, I couldn't find a definite answer to this specific question anywhere.

We run a scientific website which displays lots of well-established data about biological entities (such as proteins, enzymes, RNA and more).

The site is currently not mobile-friendly (i.e. no meta viewport, horizontal scrolling due to the width of the tables and some of the elements etc.), and we're about to turn it into being mobile-friendly, using media queries and all that.

The site has some info pages (not a problem) but the heart of the site, the vast majority of pages, are one-page-per-each-main-entity (such as a protein or well-known RNA sequence), where each entity page is full of data: text, tables, images, in-page searches.

Obviously, making these entity pages mobile-friendly is the primary challenge, since these are the harder to convert and are the long-tail of the site.

There are 2 issues though:

  1. Some of the content is very hard to alter to make it mobile-friendly, specifically those multi-column tables (and they can't just turn from horizontal to vertical, since it would make no sense from scientific and usability points of view), or wide images that display genomic mappings.

  2. We think (still need to be confirmed by A/B testing but this is going to be lengthy and expensive) that most of the scientific usage of the site is done by desktop, while mobile users are more interested in the main pieces of data which can be several summary texts, one main image etc. - about 1/3 of the full entity page.

These make us want to implement the mobile-friendly design such that about 2/3 of the content is only visible on tablets and desktops, but not on mobile phones. It probably won't hurt the mobile phone users who don't do deep scientific research from their phones, but it will provide very useful pieces of data for them; basically answering their main question: "What is this entity about?"

  • It's not '98-style black hat keyword hiding
  • It's not cloaking
  • It's genuine and aimed to provide usable mobile phone experience and usable tablet/desktop experience.

But, It's still hiding lots of portions of the site.

My questions are:

1. First and foremost, is this going to penalize us in any way?

2. Will it cause Google to only consider the mobile-phone-visible content for its ranking?

已采纳解答

原帖链接 · Emirodgar · CC BY-SA 4.0

Nice question. I'm afraid we will only be able to know the truth after a test. Nevertheless, I answer you based on my experience in similar situations.

We faced in the past the same situation when decided to use AMP. Some content was missing in the AMP version and that caused that some mobile visitors where redirected -by Google- to de non-AMP version with the full information.

Where we find that an AMP page doesn't contain the same critical content as its non-AMP equivalent, we will direct our users to the non-AMP page. Source

Despite you are not using AMP, I'll say that there are a lot of probabilities that you face the same scenario. Luckily we were able to analyze those visits and after knowing exactly which content they were searching for, we included it in the mobile version.

Quickly answers to your questions:

1. First and foremost, is this going to penalize us in any way?

I doubt it, you could lose some traffic if the mobile/desktop versions are not well formed or linked.

2. Will it cause Google to only consider the mobile-phone-visible content for its ranking?

That could happen so, I'll start making a test with one subfolder and analyze the results. After that, check which Google-Bot user-agent gets first and what kind of organic visitors Google send us. That will provide enough information to set up the next steps.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2019-01-07)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。