Links too close together on page resize

grgalex · Post by **grgalex** » Mon Apr 06, 2015 9:10 am

Hello to all! I think Google just hates me personally. I always seem to get the weird stuff go wrong.
According to Googles Mobile friendly tester, my home page is "Awesome" but my product pages and search pages are not
Google says "Links too close together' and "Content wider than screen".
I did R10 boostrap upgrade so I could get ahead of the deadline.
How can some pages be "awesome" and some not when they are all being resized by the same constraints?
There must be an easy way to fix this. If anyone has an idea on how it would greatly appreciated.
This is the first page google is complaining about. http://www.discountautoac-compressorpar ... earch.aspx

Post by **Katie** » Tue Apr 07, 2015 8:12 am

Are you sure it isn't your lengthy linked product titles? They seem a bit excessive and a little confusing too.

Example: "1980-1991 BMW 318i 320i 325 325e 325es 325i 325is 325ix Behr Bosch AC Compressor"

Can you point to a page that doesn't use these extremely long product titles to see if this is the problem? Because of the length, they might be pushing the content out wider than the screen because we don't try to truncate the linked product titles.

Please let us know.

Katie

grgalex · Post by **grgalex** » Tue Apr 07, 2015 2:31 pm

Hi Katie,
Thanks for the reply. I checked and you are correct, it must be the lengthy titles. Is there a specific character limit I should stay under?
It is very hard to get search engine recognition for an auto compressor when it fits many different years and vehicles. If I generalize the title I do not come up on the search engines very well. People look for a combination of year make model engine to find there compressor and if those keywords aren't in the title then we don't come up. I would greatly appreciate any ideas you would have as a remedy to my title dilemma. Also, the title makes a huge difference in the position in the feeds as to how your listed.

Thanks

jmestep · Post by **jmestep** » Wed Apr 08, 2015 1:29 am

You could try having two different names- one in product name, the other in product title. Or split out part of it into the product summary and put that on the page.

Post by **Katie** » Wed Apr 08, 2015 6:20 am

There are also the Meta Keywords and Meta Description fields. There is massive info out there on SEO best practices.

Here is an article published by Google - https://support.google.com/webmasters/a ... 5624?hl=en

Unfortunately, some of the information is slightly conflicting.

Optimal Length for Search Engines. Google typically displays the first 50-60 characters of a title tag, or as many characters as will fit into a 512-pixel display. If you keep your titles under 55 characters, you can expect at least 95% of your titles to display properly.

But another source says 65 max. I don't think there are standards for the links though. As Judy said, you can have different info for the title and link.

In your above example, for "1980-1991 BMW 318i 320i 325 325e 325es 325i 325is 325ix Behr Bosch AC Compressor", I would suggest using "1980-1991 BMW Behr Bosch AC Compressor". Then you can add the models into the description and meta info.

Hope this helps.
Katie

grgalex · Post by **grgalex** » Wed Apr 08, 2015 1:41 pm

Thank you both for your insight. I changed all the titles in a section that I know google doesn't like and it immediately tested good on the mobile tester.
However, Ever since Gold I have not been able to get the product export to work. If I could export and import it would make changing everything go much faster. I get the following error when I try.

An error has occured at https://www.discountautoac-compressorpa ... ducts.aspx
Exception: Exception of type 'System.Web.HttpUnhandledException' was thrown. Stack Trace: at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) Inner Exception: Maximum request length exceeded. Inner Exception Stack Trace: at System.Web.HttpRequest.GetEntireRawContent() at System.Web.HttpRequest.FillInFormCollection() at System.Web.HttpRequest.EnsureForm() at System.Web.HttpRequest.get_HasForm() at System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) at System.Web.UI.Page.DeterminePostBackMode() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Export

any help would be greatly appreciated
Thanks

grgalex · Post by **grgalex** » Wed Apr 08, 2015 2:44 pm

Wow!! I found something that may help others if they are having similar issues as I am.
I was doing as Katie said and decreasing my titles but got stuck on one page that would not please googles mobile tester no matter how small my titles were. I logged into my webmaster account and did a fetch as googlebot and then forwarded to the rendered page and noticed that my robots.txt file had disallow themes images and script which google now requires. I deleted the lines and now google is saying all my pages, including the long title pages, are mobile friendly. At this point I am still going to do as Katie said and reduce the titles to under 65 but am extremely pleased that it was something simple. I would still love to be able to use the product export if anyone can help.

Thanks ssoooo much!

Post by **Katie** » Wed Apr 08, 2015 3:20 pm

Hi,

I'm glad you were able to figure out the problem. I believe our stock version of robots.txt has -

User-Agent: *
Disallow: /Admin/
Disallow: /App_Themes/
Disallow: /Assets/
Disallow: /Checkout/
Disallow: /ClientApi/
Disallow: /ConLib/
Disallow: /images/
Disallow: /Install/
Disallow: /Layouts/
Disallow: /Members/
Disallow: /Scripts/
Disallow: /webcharts/
Disallow: /Basket.aspx
Disallow: /BuyProduct.ashx
Disallow: /*.axd$

So, you removed Disallow: /Scripts/ and /App_Themes/ ? Is that right?

Strange. I have to wonder why that is.

On the export issue....can you try exporting a single product? Preferably one that has the product name length decreased. Do you still get the error? If so, can you take a close look at all the product fields and try to see which one might have lots of data? We're trying to solve this error -

Maximum request length exceeded

If we can narrow down the field, then it should be easy to fix.

Thanks for the info. on the robots.txt. This is something very important for all customers to know about.

Katie

grgalex · Post by **grgalex** » Wed Apr 08, 2015 4:44 pm

Hi Katie,

Thanks for all the help.
Ok, so when I did a fetch and render and then did what google asked for me to allow I ended up with the following as a robots.txt file

User-Agent: *
Disallow: /Admin/
Disallow: /Checkout/
Disallow: /ClientApi/
Disallow: /ConLib/
Disallow: /Install/
Disallow: /Layouts/
Disallow: /Members/
Disallow: /webcharts/
Disallow: /Basket.aspx
Disallow: /BuyProduct.ashx
Disallow: /*.axd$

and now both the fetch and render in tools and the mobile site tester love everything except the following which I assume is the share links

Googlebot couldn't get all resources for this page. Here's a list:

https://oauth.googleusercontent.com/gadgets/js/core:rpc:shindig.random:shindig.sha1.js?c=2
Script Blocked

https://ssl.gstatic.com/accounts/o/3417060037-postmessagerelay.js
Script Blocked

https://syndication.twitter.com/i/jot?l=%7B%22language%22%3A%22en%22%2C%22message%22%3A%22%3Am%3Awithcount%3A%22%2C%22widget_origin%22%3A%22http%3A%2F%2Fwww.discountautoac-compressorparts.com%2FCalsonic-Kansei-AC-Compressors-C52.aspx%22%2C%22_category_%22%3A%22tfw_client_event%22%2C%22triggered_on%22%3A1428536750456%2C%22dnt%22%3Afalse%2C%22client_version%22%3A%2200acfee3245f3f642e5906f96a723b4de878ea08%3A1428536135025%22%2C%22format_version%22%3A1%2C%22event_namespace%22%3A%7B%22client%22%3A%22tfw%22%2C%22page%22%3A%22button%22%2C%22section%22%3A%22share%22%2C%22action%22%3A%22impression%22%7D%7D
Image Blocked

http://cdn.syndication.twitter.com/widgets/tweetbutton/count.json?url=http%3A%2F%2Fdiscountautoac-compressorparts.com%2FCalsonic-Kansei-AC-Compressors-C52.aspx&callback=__twttr.receiveCount
Script Blocked

As far as trying a single product export it did not work again and here is the error

An error has occured at https://www.discountautoac-compressorpa ... ducts.aspx
Exception: Exception of type 'System.Web.HttpUnhandledException' was thrown. Stack Trace: at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) Inner Exception: Maximum request length exceeded. Inner Exception Stack Trace: at System.Web.HttpRequest.GetEntireRawContent() at System.Web.HttpRequest.FillInFormCollection() at System.Web.HttpRequest.EnsureForm() at System.Web.HttpRequest.get_HasForm() at System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) at System.Web.UI.Page.DeterminePostBackMode() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Thanks again

Post by **Katie** » Wed Apr 08, 2015 6:19 pm

The error doesn't give us enough information, so we need to do some more digging. Can you take a close look at all the product fields and try to see which one might have lots of data?

Another quick test would be to create a test product and only have a short product title. Leave everything else as-is. Try the export and see if this works. I can try some testing on my end as well.

Thanks
Katie

ps. Thanks for the info on robots.txt. I will have the dev team look at the google results and make adjustments.

jmestep · Post by **jmestep** » Wed Apr 08, 2015 9:40 pm

If it has to do with this error in your message above, you could try setting the length to larger in the web.config file

Inner Exception: Maximum request length exceeded.
Web.Config:
<httpRuntime maxRequestLength="4096" requestValidationMode="2.0" />

I just wouldn't know what to advise for a new setting, but you could Google some on it.

grgalex · Post by **grgalex** » Thu Apr 09, 2015 10:24 am

Hi Katie,

Well last year I paid for Able to fix this problem and the best they could do was get the products page to come up. It was because of the large amount of categories connected to each product (make, model, year, engine). They said they were going to research on how to get the export to work and I guess they forgot. Anyways they played with the database tables to get the products page to load which it still does. Still waiting for a remedy on exports. was hoping R10 would have addressed it. Anyways the full product export takes a long time but will produce a zip file. Its when I try to filter results things crash. I tried what you said : export product/filter products/manage products even when I try to search for a single small title item on this page it throws the error after the processing icon keeps turning for minutes. I would just use the full product file to make changes and import but when i tried in the past i had to recover the database because things got messed up. So i am afraid to try again.

Thanks

edinos · Post by **edinos** » Fri Jul 15, 2016 12:22 pm

Where do you go to allow or delete /scripts/ and or /images/??

AbleCommerce Shopping Cart Software

Links too close together on page resize

Links too close together on page resize

Re: Links too close together on page resize

Re: Links too close together on page resize

Re: Links too close together on page resize

Re: Links too close together on page resize

Re: Links too close together on page resize

Re: Links too close together on page resize

Re: Links too close together on page resize

Re: Links too close together on page resize

Re: Links too close together on page resize

Re: Links too close together on page resize

Re: Links too close together on page resize

Re: Links too close together on page resize