Welcome to the Q&A Forum

Hi, Moz is hosted on Amazon. See this sample log entry from today: 54.146.235.41 - - [17/Sep/2017:09:48:13 +0200] "GET /best-deals.html/page/12/ HTTP/1.0" 200 15803 "-" "rogerbot/1.2 (https://moz.com/help/guides/moz-procedures/what-is-rogerbot, rogerbot-crawler+aardwolf-production-crawler-97@moz.com)"[XF 54.146.235.41] That IP is part of Amazon's ASN. whois -h whois.radb.net -- '-i origin AS16509' | grep ^route You can either use something like mod_authz to allow the domain amazonaws.com to connect or you can get each IP from AS16509 and allow that. Hope it helps. Regards Chris

Hi Wendy! Kristina from Moz's Help Team here - I wanted to chime in here as I had a chance to look over your site and it appears that your site is blocking AWS. We are getting a "403 Forbidden Error" when attempting to access your site as AWS: http://screencast.com/t/P858BVEQk Additionally, this 3rd party tool, hurl.it which also uses AWS is getting an Internal Server Error when trying to access your site as well: http://screencast.com/t/N5T822Zpdo Please re-connect with your developers and make sure they're addressing the issue with your site blocking AWS and that should resolve the issue you're seeing currently in Moz. I hope this helps but please let us know if there's more we can assist with! -Kristina

Hi Kerry! There is a way you can dictate within the stylesheet what content will show up where (i.e. desktop vs. mobile). What you would need to do is create two custom classes for mobile-only and desktop-only. This is an example of what would need to be added to your stylesheet: //medium+ screen sizes @media (min-width:992px) { .desktop-only { display:block !important; } } //small screen sizes @media (max-width: 991px) { .mobile-only { display:block !important; } .desktop-only { display:none !important; } } Learn more about creating two different custom classes so you can display different content via desktop and mobile here. In response to will this hurt your rankings—I found this article that discusses how to properly go about hiding content on mobile WITHOUT hurting your rankings on SERPs. There is a statement from Google that says, "Hidden content can be discounted in ranking, but if the content is visible on the desktop version of your site, we can crawl it and use the information for ranking your mobile site as well since we can share indexing signals between the desktop and mobile versions." So, as long as the content is visible on the desktop site, Google can utilize this information to properly rank you on the mobile search results. Hope this helps and answers your question!

Hey Stu! In a case like this we recommend purchasing a listing for the new company (xy) overall. We have tools that allow you to enter alternate names/addresses/phone numbers for the old listings that will help us identify, update, and/or remove them. If you already have an existing Moz Local listing for company x or company y, you can shutter those listings, but we do not recommend buying new Moz Local listings for outdated company information. You only need one account to manage this new listing! Also, please be aware that we expect updates through Moz Local to generally take 8-12 weeks, so if you're looking for immediate effects by purchasing the new listing right before the company merges, there may be some lag time before the listings are updated.

Hi Sanjay, Appreciate you searching the community for similar questions. Do you have comments allowed on that page? Curious if it could have picked up any link spam from that. Agree with Brian to scan your website and reach out to your server provider to see if they have any more details on a potential hack. Do you happen to also have Bing Webmaster Tools? It would be interesting to confirm if they also picked up any sort of hack. Hope this helps!

Hi Andrew, If you can send me the domain I'll have a look at the DNS and see if there's anything that looks unusual. Drop me a message on here, or email me on david@bringdigital.co.uk Cheers David

Not a problem Brian. I'm interested to see what sort of impact these changes make!

Sorry I misread your issue. Since you are online only I would not claim any local listings. I would clean up and remove all those citations if possible though.

Thank you, Russ! Google confirmed me that this change is due to an update, it won't be rolled back and there's no way to fetch data for each variant individually. Details are here. Your tool will help us a lot.

Have a read of what Google say about them here. And yes, image search is huge. As for the way it's used, I can't comment on what everyone else does. -Andy

Hi Jackson! Kristina from Moz's Help Team here. I'm sorry to hear you are experiencing issues with your paused listings this morning. I'm afraid we experienced an issue with our connection to Google which has already been resolved and our engineers are in the process of un-pausing all affected listings. Paused listings have no impact on what we have already distributed to our data partners. When this situation occurs under normal circumstances (deleted Google page, street address hidden), this would only prevent you from making new changes or updates. I had a chance to peek into your account and was able to verify that your listing is active again. I apologize for any inconvenience. As always, you can reach out to our team directly if any issues of this nature pop up again in the future by sending a note to help@moz.com. Sorry again for the trouble on this one - I hope you have a great day! -Kristina

Thanks for the contribution Patrick - I am gonna go ahead and disavow the domain, as well as the affiliate link.

Hi there - Tawny from Moz's Help Team here. This is something we'd love to help you out with! If you write in to help@moz.com or use our Contact Form with your question, we should be able to help get things straightened out!

Not Working

Thanks David, will do!

Hreflang tags should point to the canonical version of the page. So yes, please remove the ?d=Womens from all your Hreflang URLs. Here are the results of a test run on this URL to check for Hreflang errors: https://app.hreflang.org/results.php?runid=f622e3d03dbf4a03958c6a6d2d180bd020160719202039 You will see that all errors are because of the ?d=Womens in the URLs.

Not the parameter, specifically speaking, You need to have the canonical on the mobile URL exactly match the primary URL of the non-mobile page. So removing the /mobile/ directory from the URL. (Technically, a parameter is something added at the end of a URL with a "?" so /product/product-code?sort=desc for example, which you didn't show on your examples. Canonical URLS should never include such parameters. In fact one of the main reasons for using canonicals is to fix issues with extra unwanted parameters being indexed as separate page. Didn't want to risk confusion here.) Paul

Hi Paul! It sounds like ThompsonPaul has answered your question. Are you all set, or can we be of more help?