Welcome to the Q&A Forum

Hello Shanidel, Jo from the Moz help team here. I've had a look at your site and I've not been able to access your robot.txt file, this is what I'm seeing in the browser https://screencast.com/t/JjQI1WTH3ni I'm also seeing this error when I check your robots.txt file through a third party tool https://screencast.com/t/pxsP9pL5 So it looks to me like may be some intermittent issues with your robots.txt file. I would advise reaching out to your web developer to see if they can check your robots.txt file and make sure it's accessible. If you're still having trouble please let us know at help@moz.com Best of luck! Jo

Thank you.  I think the issue is the lifts are identical except for the capacity, so it's difficult other that differentiating in the title, url & headers that one is 18,000 and the other is 12,000.  I'm thinking that combing them on one page might be the best option.

Hi Andy, You are saying right but the point is Google was not treating my company name as the brand name. But thanks to Google, now everything is solved. I have changed the meta tags of every webpage of my site and things goes right.

Thanks so much I'll try that right away

Oh that's a good idea. I just tried it (link) and it actually doesn't seem so bad

You're welcome!

Thanks for the response! Yes, I was wondering if having dots in the on page elements "ie: tile tags, h1, description, etc" would hurt SEO or confuse bots when crawling. My understanding is that it doesn't due to the semantic approach Google bots use when crawling but I wasn't 100% sure Thanks for confirming! Youssef

The rule of thumb is a 301 redirect passes 90-99% of page rank. If the 301 is redirecting to another page on the same domain, it's probably closer to 99%. I would not worry about the 1% loss. Redirecting to https on the same domain actually improves page rank. Google likes HTTPS, and it is a positive ranking factor.

Hi All, I think nobody know anything about my question. So Now i have solution of my question. This is the solution - http://www.gsqi.com/marketing-blog/how-to-set-up-pagination-rel-next-prev/ if any body suffer like me. Thanks Rajesh

Thanks. Yea, I did consider those options. I assumed there was a more complicated way to do this then deleting the page and then re-creating it after. All of those make sense though. Thank you for your time. Much appreciated.

I'm trying to fix these 3 blocking CSS resources https://fonts.googleapis.com/css?family=Audiowide https://fonts.googleapis.com/css?family=Raleway:300,400,700 https://www.legendslimotn.com/code/css/style.css?ver=3.1 I tried this: <link rel="preload" href="path/to/mystylesheet.css" as="style" onload="this.rel='stylesheet'"> <noscript><link rel="stylesheet" href="path/to/mystylesheet.css">noscript> <script> /*! loadCSS. [c]2017 Filament Group, Inc. MIT License */ (function(){ ... }()); /*! loadCSS rel=preload polyfill. [c]2017 Filament Group, Inc. MIT License */ (function(){ ... }()); </script> Adding this to the code improved the load speed results but it caused other page problems on the browers other than the Chrome browser.

You are welcome!

Hi Lina, This definitely could impact SEO. The key here is: what pages do you want to be in Google's index? If you just want one blog homepage, the best strategy is canonicals, like Cesare said, plus telling Google that it should ignore the parameters that you use for the ESG and News blog. If you want the standard homepage, ESG, and News blog all to be  in Google's index, you'll want to canonical the homepage to it's URL with no parameters, then update the canonicals for the ESG and News blog once the filters are applied, so the canonicals include the parameters that make the ESG and News sections unique. You can update which parameters Google pays attention to or ignores in Google Search Console, which we explained how to do in another Moz post here: https://moz.com/community/q/how-can-i-remove-parameters-from-the-gsc-url-blocking-tool Good luck! Kristina

I know this is four years old, but there's value in having a blank robots.txt as some tools (including the latest version of the Moz crawler) will baulk at sites without a robots.txt file.