How to resolving mobile affinity error in Google Console in 2020

A few days after switching from FastBoot skin to JB skin, an email came from Google Console.

It was an email notifying us that there was a problem with mobile user convenience.

There were two types of errors.

 

-"Text is too small to read"

-"Clickable elements too close to each other"

As I went through the problems one by one, the above two errors were almost always corrected if only one was corrected.

In the picture below, there are 2 errors, but in another operation blog, the term is mostly 30.

This problem is a relative concept, and such an error cannot be defined as fixing this part.

This is because, depending on the situation of the page causing the error, even if it is the same error message, the cause may be different.

Therefore, in my case, I would like to replace the cause identification by checking the error page one by one and enumerating the corrections to the problem.

 

-A chart with the text format you wrote on the page

On the mobile, the chart hits the screen horizontally and goes out on the PC screen by riding the sidebar.

This case occupied a lot of odds.

When quoting various statistics, there were many pages in which the chart was directly written and inserted in the thought that the text format would bring more data when crawling rather than images.

In this case, after capturing the chart, the image was reduced and then uploaded, and most page errors were fixed.

 

-When the tag list is inserted at the bottom of the page body, etc.

In this case, the tag itself did not seem to be a problem, but it seemed to be a problem when there were tags with spaces among the words in the tag or with long-word tag words.

This was fixed by replacing long words in tags with short words and reducing the number of tags.

 

-If you review the html source of other problematic pages and fix the questionable part, and the parts that are difficult to understand, try to load the corresponding address on the mobile and review it. .

In conclusion, most of the mobile-friendly errors seemed to be a problem when the text content was attempted to go out horizontally among the body content.

For example, the horizontally long diagram mentioned above, and a list of tags with words that you want to extend horizontally.

 

-If the number of mobile-friendly errors is large, change the suspicious option to a general setting among the options that are applied to the entire blog, such as the total number of advertisements, excessive number of advertisements, or abnormal aspect ratio, and then re-validate mobile convenience in the Google console. I think it's a good idea to reduce the number of errors while making a request. 

 

It's hard to see a mobile-friendly error as a serious error, but I'm sure it's not good for the blog index because it slows down loading and eventually makes access to that page difficult.

That doesn't mean that you have to be too sensitive, but you need to check if there are any errors on the actual mobile screen of the problem pages listed in the table tab of Excel after downloading it as an Excel file through export.

If there is no singularity to watch on mobile during this process, you can leave it alone.

Pages with no real problems will disappear on their own in the Google Console's list of problem pages over time.

My personal opinion about this error is to check the problem page if possible, so it is better to solve the problem and skip the pages that actually cause problems on the mobile screen. There is no need to do.