Welcome to the Q&A Forum

Hi there,

I don't think there are any tools out there that collect this sort of information and share it as a competitive intelligence tool.

Google Analytics has a 'Benchmarking' section which you can find under 'Behaviour' > 'Benchmarking' in which it compares your site performance to that of other competitors within your industry anonymously. It's more of a rough guess (as default industries in the interface can be quite large) but it's a good place to start.

I hope that helps,

Sean

Hi there,

I would check your server logs for pages that have been serving up 404 errors when accessed via Google Search.

You can then add in the necessary 301s for these and you'll be good as new!

Alternatively, if you want a catch-all approach, you can use screaming frog to identify the 404 pages on the site. If you have a URL export from your old site, run these URLs through using the 'upload list' function on screaming frog to check their response codes individually.

All the best,

Sean

Would this be anything to do with the space you have between the 'equals' sign and the opening quote marks:

Hey,

When you opt into this, your GA data is anonymously shared amongst others in your niche to go towards average figures. No one will be able to look at your site specifically, but your site stats will contribute to overall figures.

Cheers,

Sean

Hey Kirupa,

Short answer is that you're all good. The canonical is correct.

All the best,
Sean

Apologies, my mistake.

The Mozbar picks up your meta descriptions correctly so I don't know what's going on. Perhaps flag this question as 'Moz Support' and see what the tech guys say?

Sean

Hi there!

You're absolutely correct, you would just need a domain-level server redirect to take all http URLs to their https equivalent.

Best practice is to ensure you've also got the non-www. version of the website covered in that same redirect too, to avoid any chains. You'll see what I mean if you run your domain through this > https://varvy.com/tools/redirects/

Depending on what stack you're using, here are the 2 guides. One for htaccess and one for IIS:

• https://stackoverflow.com/questions/10489895/http-to-https-through-htaccess
• https://blogs.msdn.microsoft.com/kaushal/2013/05/22/http-to-https-redirects-on-iis-7-x-and-higher/

You shouldn't need to, but just to be on the safe side, I would also add canonical tags to the http pages, pointing to their https equivalent prior to putting the server level redirect in place. This is to ensure that you won't be causing yourself issues if the redirect fails for any reason. Details here:

• https://searchengineland.com/https-setup-causing-seo-issues-254236

Once you've got your redirection planned in, make sure you set up a Google Search Console account for the https version to ensure there are no crawl issues and to check that the http version of the site stops receiving traffic.

That should just about cover it!

Hope it all goes well,

Sean