Community Forums › Forums › General Genesis Framework Discussions › Old topic again: Text too small to read, clickable elements are too close
- This topic is empty.
-
AuthorPosts
-
September 21, 2021 at 3:44 pm #504469
EugeneHunt
ParticipantGreetings,
Got a warning from Google saying that I have issues with mobile usability: text too small, elements are two close to read.
Searched this forum, found 2 threads on the subject:
1st - suggesting to increase the font: https://studiopress.community/topic/how-to-fix-text-too-small-to-read-in-google-search-console-gsc/
2d- suggesting to ignore Google https://studiopress.community/topic/page-is-not-mobile-friendly-issues/
I am not certain if I can follow any of these suggestions and have a number of questions.
1) isn't the themes from Studiopress mobile-friendly by default? I use MagazinePro, didn't change anything...
Not sure why I am having this issue in the first place. Any ideas?
2) In Console, all my posts are indexed except the next 2:
Which are said to be not mobile-friendly while they are identical to all other posts, which are indexed with no issues.3) I am completely confused by this Google alert because it doesn't help at all to understand if (A) Google is unhappy with all my posts or (B)only two of them. If it is (A), why Google indexes all my posts except two, which he considers not mobile-friendly; it should have exluded all my posts from index and send me alert. If it is (B), why Google sends me this message (without explaining which part of my website Google doesn't like) as I already know it excluded 2 posts from my index?
I should probably address the 3d question to the Google community, which I will do later. Just wanted to check about the mobile-friendliness of MagazinePro, which I got from Studiopress and why it has issues with Google.
Any thoughts would be appreciated.
Cheers,
https://moneysaurus.com
EugeneSeptember 23, 2021 at 8:33 am #504472AnitaC
KeymasterThe two issues you have are very generic and Google hasn't defined any settings to say where they see them. I personally disregard that. But this is a question for Google Forums and not this forum as again...it's very generic and applies to most themes...StudioPress and others.
Need help with customization or troubleshooting? Reach out to me.
October 8, 2021 at 3:03 pm #504524EugeneHunt
ParticipantThank you! I somehow missed your answer as I was looking for an alert for new answers in my Gmail. Will check on Google forums.
November 6, 2021 at 4:47 pm #504562codeshim
ParticipantI'm late in replying to this thread, but I wanted to point out that in my experience, this usually happens when Google fails to completely load the site's CSS files, resulting in broken styles, which Google then complains about. If you ask Google to validate (without changing anything) and the errors go away, then you know it wasn't a real problem. If the errors don't go away, you might want to dig deeper to see what it causing them.
Performance optimization and caching can help reduce how often this happens. Try testing your site with a tool like https://webpagetest.org/ to see how you can optimize. Inlining critical CSS may also help, since it may provide certain important styles even when Google fails to load the main CSS file.
November 8, 2021 at 5:33 am #504563karchervietnam
ParticipantThis reply has been marked as private.November 8, 2021 at 5:33 am #504564karchervietnam
ParticipantNovember 11, 2021 at 1:28 pm #504581EugeneHunt
ParticipantHi @codeshim,
Thank you for the feedback! Noted on CSS issues.
Still, what puzzles me is why some blog posts are indexed while others, done using the same template and theme, are excluded from the Google index.
Example of indexed post:
Examples of non-indexed posts:
1. https://moneysaurus.com/wines-and-spirits/scotch-vs-bourbon-vs-rye-why-you-should-try-them-all/
2. https://moneysaurus.com/gems-and-gold/how-to-pick-a-diamond-and-engagement-ring/I believe that both indexed and non-indexed posts have the same CSS (as they are based on the same template and theme) but Google treats them differently, saying that non-indexed pages have Mobile Usability issues, namely 'text is too small to read' and 'clickable elements too close together.' (which isn't true as far as I can judge).
Could it be that Google keeps a certain portion of blog posts (for example, 3 posts out of 20 as in my case) out of the index all the time, indexing them as long as new posts are added?
December 1, 2021 at 11:24 am #504608codeshim
Participant@eugenehunt Sorry for the delay, I thought I had this topic set to notify me of followups, but apparently not.
Excluded pages are usually a separate issue. Mobile usability problems may affect search ranking, but they are not usually a reason for a page being excluded altogether.
I have never heard of Google treating indexed and non-indexed posts differently for mobile usability, but I suppose anything is possible.
If a page is excluded, Search Console should provide a reason for the exclusion. For example, "Duplicate page without canonical tag". More info on the specific messages here: https://www.curiousants.com/game-plan/technical-seo/google-search-console-coverage-excluded/
December 2, 2021 at 6:20 am #504612EugeneHunt
ParticipantHi @codeshim
I have the same issue about forum's notifying me about new replies to this thread because I don't get any. Probably we have to raise a flag to forum admins because it looks like "Notify me of follow-up replies" function doesn't work. Checked my Social/Promotion/Spam but I haven't found any notifications.
I have asked the same question on Google Forums and received an answer that "these are both related to crawl Budget Issues. Ie Google DIDNT fetch the page/resource...
There is no 'magic fix' to crawl budget issues, other than there being 'too many' to crawl."Here is the link to the answer: https://support.google.com/webmasters/thread/137142809/non-indexed-page-is-mobile-friendly-and-not-mobile-friendly-at-the-same-time-in-search-console?hl=en
So I have decided to put it on hold for now as I don't see a clear answer to that.
-
AuthorPosts
- You must be logged in to reply to this topic.