Vicente Paul Posted June 27, 2017 Share Posted June 27, 2017 (edited) There is a big SEO issue with MENU CMS sub-categories links in mobile (see in the 2 atachments), because spaces between the CMS sub-categories links are too close. The problem is that as this is part of the menu, all pages are considered as non-mobile friendly!! The same problem occurs with the CMS Page links which are too close. => ANYBODY KNOWS HOW TO MODIFY THE CSS TO HAVE BIGGER SPACES BETWEEN THESES MENU LINKS? It also seems the Google bot cannot read the Menu css, because it shows the menu without any styling. Because it indent each link level, the Google bot also says that the content is wider that the screen size (which is not true). Edited June 27, 2017 by Vicente Paul (see edit history) Link to comment Share on other sites More sharing options...
Vicente Paul Posted June 27, 2017 Author Share Posted June 27, 2017 The extra-spaces between the menu links, I already solved like this (in bold): /public_html/themes/classic/templates/cms/category.tpl {block name='page_content'} {block name='cms_sub_categories'} {if $sub_categories} <p>{l s='List of sub categories in %name%:' d='Shop.Theme' sprintf=['%name%' => $cms_category.name]}</p> <ul> {foreach from=$sub_categories item=sub_category} <li><a href="{$sub_category.link}">{$sub_category.name}</a></li> <span> </span> {/foreach} </ul> {/if} {/block} {block name='cms_sub_pages'} {if $cms_pages} <p>{l s='List of pages in %name%:' d='Shop.Theme' sprintf=['%name%' => $cms_category.name]}</p> <ul> {foreach from=$cms_pages item=cms_page} <li><a href="{$cms_page.link}">{$cms_page.meta_title}</a></li> <span> </span> {/foreach} </ul> {/if} {/block} {/block} 1 Link to comment Share on other sites More sharing options...
Vicente Paul Posted June 27, 2017 Author Share Posted June 27, 2017 (edited) The second issue was explained by the Google Search Console, see in attachment... Put in robots.txt: Allow: */themes/classic/assets/cache/*.css Allow: */themes/classic/assets/cache/*.js Allow: */themes/classic/assets/css/*.css Allow: */themes/classic/assets/js/*.js Edited June 27, 2017 by Vicente Paul (see edit history) 1 Link to comment Share on other sites More sharing options...
jose neva Posted September 28, 2017 Share Posted September 28, 2017 Hi, thank you very much for the help, I had the same problem after changing the code, I have to tell google one by one each web, or just send sitemaps and expect to see the changes ?? sorry but i'm very new, thank you Link to comment Share on other sites More sharing options...
Vicente Paul Posted September 28, 2017 Author Share Posted September 28, 2017 Google will discover that automatically, but sending the URLs in the search console will be quicker... 1 Link to comment Share on other sites More sharing options...
jose neva Posted September 29, 2017 Share Posted September 29, 2017 Agree. thank you very much Vicente Paul 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now