Welcome to the Q&A Forum

Thanks! I went about using my Yoast SEO plugin on my Wordpress site to simply input the canonical URL I wanted to advance the credit to

The search engines will recognize it, only if you tell it to recognize it. So if you're dealing with a small site I think the second option is better but if we are talking about a big ecommerce more than 100,000 product maybe 3 options is better

Thank you, Christy!

I  really like survey monkey and type form. https://www.typeform.com/lp/surveys/ http://www.capterra.com/survey-software/ hope pe that helps, Tom

Completely agree, just 1 character might not influence anything. Search engines are very well able to understand what that specific character means in the context if you add 360 next to it.

Thanks David! That definitely makes sense. We claimed photos.tagible.com in GSC, so hopefully that does it. And yes, they are, but in an unusual way: http://tagible.com/project/denver-colorado/

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

Yes, definitely fix this issue, as sooner or later Google will see that your website speed is experiencing errors. I would check with your website host for speed, optimization and reliability.

It seems fixed now.  I have just checked again and fortunately new update results appears.

Hi Ironically MOZ will pick this up as a problem as it reports anything that is noindexed! For me I just ignore noindex as a problem in certain cases as clearly it makes perfect sense to noindex certain pages and indeed sometimes whole directories. I sometimes find that developers have noindexed directories like /new-products or /sale but clearly there are better ways of handling the potential duplicate problem here by adding a canonical. In you case it makes no sense having Google index the checkout pages. Regards Nigel

+1 to both of the above comments! It's hard to say why a website ranks higher in mobile than in desktop without actually seeing it. However, a few factors could be at play here: 1. Site Speed 2. Not having pop-ups or flash enabled on your mobile site 3. Structured Data is present More data is certainly needed in order to answer your question in a more specific way. Good question!

This is not an SEO function, this has to do with how your site is coded and how that code interacts with the app.  You will need to bring in a Dev to troubleshoot your code and find a solution.

It would be useful to see an example of what you mean, but the answer is probably not. What to do first is: Ensure you set up hreflang correctly, so that Google understands your Chinese-language page on New York and your English-language page on New York are functionally equivalent. Use a good rank tracker, and configure it to check your keywords on each of the country-level Google sites you're interested in (Google.co.kr for Korea, and so on). See whether the correct page is showing up when you track ranks for the foreign-language name, and for the phonetically-translated name. Check Search Console for the appropriate pages, using the country filter to look only at the kinds of queries and clicks you're getting from each of the countries you're interested in. See whether people are actually searching with the Asian-language name for the city, or with a phonetic translation. See whether people are searching for the English name (they might be). If, after looking at your rank tracking and search console results, you think there are many people in Asia putting English-language city names into their queries, at that point you could consider going ahead with this idea. Even then, try it on just a few of your city pages at first—not all of them—and continue to refer back to your rank tracker. What you don't want to see is any direct competition between different language versions of the same page, in the same SERP.

Thanks for this update, Pete!

Hi I would not noindex a "/" version because you will simply lose all of that traffic. I would make sure as Martin has said that here is a proper directive in the .htaccess.txt that automatically redirects "/" to the non "/2 version - knocking the "/" off. Any competent web developer can do this for you. If this is a shared server then you will need to ask Squarespace for help as you may not have access to an .htaccess.txt file. Regards Nigel