Hi,

That sounds like a definite candidate for duplicate content issues. A true responsive design only has one set of page elements coded, which then rearrange based on screen size, that's what makes responsive the optimal solution for SEO. Search engines only have to read one code set per page and they know it'll render for most devices. In your case, I believe search engines will view that as a tactic to game the system; one version of the content is essentially cloaked when the other is displayed.

Hi,

Found the source of your issue: this URL (https://www.aerlawgroup.com/sex-crimes.html) has a link pointing to it from a HTTP URL (http://www.aerlawgroup.com/sex-crimes/new-allegations-emerge-in-sexual-misconduct-case.html), which is probably how SF found all the other secure URLs.

All of your HTTPS page return 200. If you want to go back to non-secure, those secure URLs will need to be redirected back to HTTP, the same as you probably did when you went to secure.

Also, looks like you've still got a couple HTTPS pages indexed: https://www.google.com/search?q=site%3Aaerlawgroup.com+inurl%3Ahttps&oq=site%3Aaerlawgroup.com+inurl%3Ahttps&gs_l=serp.3...5577.15088.0.15655.24.24.0.0.0.0.150.1864.19j5.24.0....0...1.1.64.serp..3.0.0.bf5ZiosfHMI

Hi John,

I recommend grouping your keywords into similar topics and associating them with either an existing URL on your site, or if the topic isn't currently discussed on your site, proposing a new URL. This process is called keyword mapping, where you take each keyword your tracking and pair it with a preferred URL. I start all of my SEO projects off with one, here's why:

1. Provides a road map of what _existing _content needs to be updated
2. Lays out what new content I need to create
3. Prevents me from diluting the emphasis of one keyword by addressing a very similar one on another page
4. Helps me set priorities on which content should be updated/generated first (I aggregate search volume for all associated URLs and work in a descending order)

Hi Steven,

You'll definitely want to apply 301 redirects to any site that you move to HTTPS. For most sites, this can typically be done with a single redirect rules that essentially replaces http with https, so you won't have to comb through each URL and apply one-to-one redirects.

No need to worry about losing link juice, Google views these types of 301s differently than a typical 301, and all authority will pass through them.

Canonical should also be applied, this will help search engines learn your new URL structure and ensure they index the new HTTPS URLs.

Cryus Shepard wrote a great post with all the necessary steps for a secure migration, check it out here: https://moz.com/blog/seo-tips-https-ssl

Good luck!

The best way to mitigate this problem would be to update the destination URLs in your Adwords Campaigns. You can do this in bulk relatively quickly using the Adwords Editor desktop application.

You'll definitely want to keep that canonical tag in place. Some tools don't recognize canonicals, so I wouldn't worry too much about duplicate notifications due to parameters like that. If you noindex that page, it will apply to the root of that URL, not strictly the parameter'd version.

That's the only method I know of deter unqualified clicks, interested to see if anyone else chimes in with some useful nuggets of info on this topic!