That is only truth if the new theme that you are going to use has errors. If it has been SEO'ed and all the content will be the same, you may some rankings decline until Google spiders the new site and re index it. But that shouldn't take very long.

You need to think on the users first, will the users love the new site? If they will, then Google will follow, don't worry about that.

If there's no way to access site.com why will you set a canonical?

If, for example, your sites serves the same content on site.com and www.site.com what you need is a "global" 301 redirect from site.com to www.site.com to avoid duplicate issues. As the file is the same in both domains, a canonical would help, but not appropriate in that case.

Is that what you need?

Equity is passed to a 404 page, which does not exist, therefore that equity is lost.

I found the problem myself.

My site is under cloudflare, and apparently they were blocking the IP requesting the favicon file.

As a fix, I added the favicon to the CDN (which does not go through cloudflare) and the issue is now fixed.

Hi Chris,

It's been proven that the main issue with h1 and h2 tags is that people uses them everywhere within the design, while there's a reason for the 1, 2, 3, etc. h2 is used to denote your primary heading, h3 to denote your h2, and so on.

You could change the other h1, h2 (that are less important) and use h3 and h4 accordingly by styling the h3 and h4 in the CSS.

The only bad thing to do there would be to hide (display:none) any of the headings.

Hope that helps!

Hey Mike,

So basically if the page is unique and there's no other copy with another URL you shouldn't use the canonical tag in that unique page pointing to itself?

I know it's like saying "the original copy of this page is here" while "here" is the same page, but that solves lots of duplicate content issues that might arise while using URL rewrite.