Welcome to the Q&A Forum

Hi David, yes, we moved from site.com to site.org. We are running off WP and have the SEO plugin activated which has a rel=canonical feature. Pages on new site have canonical tags pointing to the new .org page. So no, we're not pointing back to the old .com pages. We fixed the duplicate content issue so just need to wait and see if that helps. It's been over a month and old site still showing up in index when I use directive site:mysite.com. I also submitted change site address in search console.

No problem! Good Luck!

Making sure that the https pages are canonicalized to https pages should be relatively easy and within your control. I would get that done right away. If the canonicalization wasn't done right in the migration, it makes me wonder what else may not be right with the move to https. You might want to look here https://moz.com/blog/seo-tips-https-ssl, especially the links under "best practices" and double check all that. The unnatural link clean up and reconsideration request will be more work intensive and take a lot more time and is on some level not entirely within your control, as you are left at Google's mercy. Both need to be done, but they seem like very different sized problems with very different timelines to payoff. Best of luck! ... Mike

I don't think the best hosting has to be the most expensive, so going by what you can afford isn't the best guideline. If your site is performing well, you have no security concerns, and the hosting company is responsive to support requests, then I'm not sure why you'd need to look for anything else. If you feel you are having trouble ranking well, attracting visits to the site, or converting those visits to customers/members/subscribers (or whatever conversion is appropriate for your business model) then you might want to consider the benefits of a hosting upgrade. Is there a specific issue you are trying to solve?

Hi there Sometimes, this is what Google does. They do it for some of our clients as well. Here's more information at SEW. There are recmomendations from Google saying that your homepage title should have your brand toward the front, while internal pages should have target keywords toward the front of the title tag. I would leave your titles the way they are because if Google wants to change it, they will. Let me know if you have any questions or comments - good luck! Patrick

Google is capable of executing javascript. Here's a post from Google on the subject. You can see how Google sees your page by using Search Console, then fetching and rendering the page. https://www.google.com/webmasters/tools/ With that said, I'd opt for the version of Wix, especially if it's limiting your ability to use tools that aren't quite as sophisticated as Google.

Hi Dan, Thank you so very much!!  I think things have caught up...I chatted with Google a few days ago and they said everything is ok.  I am starting to see some keywords surface; it probably will kick in shortly, as I did quite a bit of SEO work with the new site. I very much appreciate your help! Best, Sharon

I think the way you have it is fine. If you must change it, I'd go with /product/the-product/345897345123/ . However, again I think this way is good: /product/the-product345897345123/ . That is a lot of sub-categories for that amount of product. You might consider adding a Noindex,Follow tag on some of them if you're not writing unique static copy for each of those pages.

Yes, they have keywords in Meta Title, but to me it looks more like keyword stuffing - it just repeating keywords in different language. When you look on the other competitors they usually do much better content wise and social media wise. It seems that age of the website is an important ranking factor here. Pioneer privilege?

Hello Rick, If you consider this answered please list the questions which you believe cover your points as answered!

Hi Francisco, Google suggest to do the sitemap as your third option. Check this article: https://support.google.com/webmasters/answer/2620865?hl=en My way of doing it, is creating a sitemap for every language, uploaded all of them to the root of the site and create a sitemap stating the latter sitemaps. This is an example: <sitemapindex<span class="html-attribute"> xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"</sitemapindex<span>><sitemap></sitemap>https://www.domain.com/sitemap-en.xml<sitemap></sitemap>https://www.domain.com/sitemap-pt.xml<sitemap></sitemap>https://www.domain.com/sitemap-es.xml Hope it helps. GR.

Thanks for the response! I already have the rel=next and prev added to the page but I'm still getting Duplicate Page Title errors in my dashboard for all of my subpages (such as http://thelemonbowl.com/breakfast/page/2). Should I be setting a 'noindex' to my subpages to prevent this from happening? Thanks again!

School boy error! I put http: version into the crawler so it assumes www. is a subdomain of that. Therefore naturally at level 1. By crawling www.version it shows that to be level 0

HI Harry, He should be able to set this up dynamically. Otherwise, yes I do feel sorry for him but then he didn't he didn't built it right the first time anyway. Martijn.

Would you say that this just have "psychological" impact on the customer?

Hello, There was a Google Update Quality in June, so this update may have been impacted your rankings. More info here : http://www.gsqi.com/marketing-blog/june-2016-google-algorithm-update/

Hi, I would track both. Post-Hummingbird, Google has gotten much better at understanding synonymity - if you choose to optimize for one consistently, Google is going to understand your pages are still relevant for related queries, even when you may not have specifically optimized for them. This is why a lot of people are noticing that Google is modifying their how their Title Tags display in the SERPs - they're tailoring them to the queries for improved CTR but they can do that only because they know the modifications are still highly relevant to the listed page. Hope this helps. Thanks

Deacyde, Your response about the user was good. You spend days and days researching keywords and sometimes you get lost in the weeds and forget what the whole thing is all about.

We haven't tried the plug-in yet.  The pages not found route to a custom 404 page so we can see a 302 redirect to that and then the 200 because the custom page was displayed.  Per other forums we tried forcing the 404 return code prior to the page being loaded but this seems to be getting ignored or overwritten by GoDaddy. I understand some people view the 200 as being correct as a page was loaded correctly but Google does ask for a 404 for a page not found.

No problem, glad to help!