I use a javscript slider called LayerSlider. In Google Webmaster tools it is telling me I have a 404 error with the following link: http://www.example.com/js/layerslider-5/skins/. It says that my home page links to that file path. When I check my home page I have code as follows:

  //Other LayerSlider Options
  skinsPath: '/js/layerslider-5/skins/'

This is the JS used to call LayerSlider. The skinsPath tells the script where to find the appropriate skin and apply it. Evidently Google is seeing this as a broken link.

How do I tell Google that this isn't a broken link? I can mark the URL as fixed but it just reappears.

On site there are no errors or problems, just in the webmaster tools.

Will this negatively effect the site in anyway?

  • 1
    Marking as fixed just resets the counter. Google will keep trying as long as you say it is fixed. Not every 404 in Google's list has to be dealt with. The list therefore is confusing to some (hell a lot of people). Google will eventually stop requesting the resource, but not until you figure out what about your JS makes Google think it is JS link and change it. – closetnoc Sep 29 '14 at 0:53

Error 404 can actually mean your site is WORKING... Not BROKEN!

It's commonly mistaken by a lot of webmasters that error 404 means something is broken and the site must be fixed! when in reality 50% of the time errors 404 occur when a user or bot requests a URL that no longer exists or never has existed meaning a 404 return means everything is working as intended.

When 404's can hurt SEO

Generally 404's will not harm a site unless you have hundreds to thousands actually on the page that would dampen the user experience for your visitors. One way of this not helping SEO is that Google will often use on page external links to associate relevancy of content, obviously if the link is not working the page can't be rewarded. So often you may get an decrease in SEO on a page its unlikely to harm the site unless you got far too many which in your case you don't.

Fixing it for Webmaster Tools

A simple fix would to actually create a page on the same path that Google is requesting. In the header response use GONE 410 and no-index. This will tell Google and other search engines that this page no longer exists. You could actually use a robots.txt solution as well but the prefer methods are doing the status actually on the page that way you keep your robots and htaccess clean.

Yet another solution...

Another solution would be to address Layerslider, rather than setting the path skin you could just copy the folder to the default path /layerslider/skins/. Then if you have a custom skin you just set it using skin : 'myskinexample'. You could even edit the JS to make your own path the default. Since you've purchased this skin you should be able to get support from CC.

Not the answer you're looking for? Browse other questions tagged or ask your own question.