Traffic has not recovered from https switch a year ago.
-
I have an ecommerce site that was switched to https a year ago almost to the day. Our category pages are about half of what they were. The redirects were put in properly, and everything in webmaster tools looks good. Anything out there I may not have thought of?
Want to add that the drop is only in Google, Bing stayed just fine.
-
I have read in so many places that it caused a dip for others as well. I had a really bad experience with a site move once so I had a checklist of everything and double and triple checked it, but it has just been a slow decline.
-
We experienced the same thing and I am fairly certain that we did EVERYTHING right. I just think the algorithms are messed a little. I even made a competitor analysis and found that all the websites that did the https move have experienced a major dip in the past. I cannot tie it to the move date, but it is clearly visible on semrush.
I have a feeling that google endorsed this https move because they need the referer data to make their analytics product work better over time, but while this whole web wide move is happening they accept some collateral damage. I even hired consultants and there is no proof anywhere that https is that "positive ranking signal" Matt Cutts vaguely indicated...but then again he said it is a ranking signal and it might as well be a negative ranking signal by that wording. My hunch so far.
-
Hi Cyrus,
1. I believe that pagination is implemented correctly. Is there anything specific you think I should check?
2. Canonicals are in place.
3. The category pages do not have their own introductory text.
4. We have the title tags and descriptions set.
Wanted to also add that we have the correct schema on the pages as well.
-
We've actually seen Google get harsh on category-type pages across a wide number of industries and sites. It's even happened here at Moz. If your HTTPS is implemented correctly (and sounds like you are reasonably certain it is) you might want to look to other areas.
I'd look at your category pages and make sure:
- Pagination is implemented correctly
- Canonical are in place, where appropriate
- If possible, each category should have it's own introductory text, i.e. https://moz.com/ugc/category/link-building
- Basically, do everything you can to treat your category pages like actual landing pages worthy of search traffic, including unique content, value, title tags, descriptions, etc.
-
I don't see where he asked about the site structure, but no it didn't change.
Reporting has not changed, no new filters, we block our company's visits, tracking code is consistent.
-
You didn't answer Dirk's question (above). Has the site structure changed at all?
Has your reporting changed? Added any new filters? Forgot to block your own company's visits from being tracked? Is the tracking code consistent on all pages? (Although it's probably not a reporting problem if, as you say, rankings and sales have also dropped.)
It's good you're doing the audit. Doesn't appear to be an obvious problem.
-
All pages have dipped a little but the category pages seems to have lost the bulk. We have had rankings and sales drops. Canonicals are in correctly and sitemaps have been updated properly.
-
1. The traffic decline wasn't sudden or initially very much. If you look at our traffic it looks like a pyramid with the peak being when we switched to https. It has just been a slow gradual decline every since.
2. The migration was Sept 11 last year, I don't think there was anything that week.
3. User behavior has stayed constant.
4. No spike in errors, the migration went very smooth.
-
Is it just the category pages that have lost traffic? Have rankings and sales also changed significantly? Are canonicals pointing to https? Have sitemaps been updated?
-
Did the traffic drop occur right after the migration to https or a few months/weeks later?
Was the migration close to the date of an algorithm change?
Did you see any change in behaviour of your users after migration (time on page, bounce rate, avg. pages/session,...)?
Was there a spike of errors in WMT after migration or did everything go quite smoothly?
Was it just a migration to https - or did other elements change on the website?
To be very honest - trying to figure out one year after migration what went wrong is an almost impossible task - especially because you don't have access to the WMT data from migration.
The best you can do is to dive deep in to your analytics figures (search traffic) and compare data before/after migration and try to understand what might have had an impact.
rgds,
Dirk
-
I am in the middle of doing an audit to see if I may have missed something. We are fully mobile optimized. Maybe it was a penalty but there has never been a single black hat trick used on the site. Panda hit that month but we have just been on a slow decline for the last year so that it is now 50%. As an ecommerce site I can't think of a scenario where Panda would hit us unless we were doing something we shouldn't have.
-
HTTPS did cause the site speed to slow down a little bit, we knew that was coming so right after launch we did some optimizations so it is now faster with https then before with http.
-
It's impossible to say without seeing the site and, likely, without seeing analytics. What I can tell you is that the issue may not have anything to do with HTTPS. There have been updates to Google's algorithms, and many other things. Mobile optimization has become a huge point, for instance. I would run an audit of your site for both technical and SEO issues to see if those might help.
-
Moving to https could have an impact on your site's perfomance - which may counter the potential benefits of migrating to https. If you compare page load times in Analytics before/after migration - did they go up/down or remained stable?
Dirk
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
50% Organic Traffic Drop In the last 48 Hours
Hello, My site had a 50% decrease in the last 48 hours (9/26/18) and I looking for ideas/reasons what would cause such a dramatic drop. Year to year organic traffic has been up 40% and September was up 30%. The site has a domain authority of 39 according to Moz and keywords positions have been flat for a few months. I made a change to the code and robots.txt file on Monday, pre-drop. The category pagination pages had a "NoIndex" with a rel =canonical and I removed the "NoIdnex" per: https://www.seroundtable.com/google-noindex-rel-canonical-confusion-26079.html. I also removed "Disallow" in the robots.txt for stuff like "/?dir" because the pages have the rel =canonical. Could this be the reason for drop?? Other possible reasons:
Intermediate & Advanced SEO | | chuck-layton
1. Google Update: I dont think this is it, but ti looks like the last one was August 1st: "Medic" Core Update — August 1, 2018
2. Site was hacked
3. All of keyword positions dropped overnight: I dont think this is it because Bing has also dropped at the same percentage. Any help, thoughts or suggestions would be awesome.0 -
Redirect chains from switch to HTTPS
Hi, We have a client who recently switched their site to https:// The rule to force redirect non-secure URLs to https is in their .htaccess file: RewriteEngine on if non-SSL and one of these, redirect to SSL RewriteCond %{HTTPS} !on
Intermediate & Advanced SEO | | roundabout
RewriteRule ^(.*)$ https://www.clientdomain.com/$1 [R=301,L] However, they also have simple redirects below this rule that redirect one page to another, such as: Redirect 301 /old.php https://www.clientdomain.com/new.php This is causing redirect chains like this: (A) http://www.clientdomain.com/old.php > (B) https://www.clientdomain.com/old.php > (C) https://www.clientdomain.com/new.php Is there any way to rewrite the rules in .htaccess to get rid of these redirect chains? So that URL A goes directly to URL C? Thank you!1 -
Screaming Frog returning both HTTP and HTTPS results...
Hi, About 10 months I switched from HTTP to HTTPS. I then switched back (long story). I noticed that Screaming Frog is picking up the HTTP and HTTPS version of the site. Maybe this doesn't matter, but I'd like to know why SF is doing that. The URL is: www.aerlawgroup.com Any feedback, including how to remove the HTTPS version, is greatly appreciated. Thanks.
Intermediate & Advanced SEO | | mrodriguez14400 -
Community Discussion - Are annotations an overlooked avenue for driving traffic from YouTube?
Happy Friday, Q&A friends! This week's discussion question comes from Amir Jaffari's YouMoz post from Thursday, January 28. Amir explains how he was able to use annotations to massively increase his YouTube videos' views without using ads, and raise his annotation CTR 22,400%. Have you tested annotations to see if they dramatically improve conversion rates? What were the results? What other strategies have you tried?
Intermediate & Advanced SEO | | MattRoney3 -
Dealing with non-canonical http vs https?
We're working on a complete rebuild of a client's site. The existing version of the site is in WordPress and I've noticed that the site is accessible via http and https. The new version of the site will have mostly or entirely different URLs. It seems that both http and https versions of a page will resolve, but all of the rel-canonical tags I've seen point to the https version. Sometimes image tags and stylesheets are https, sometimes they aren't. There are both http and https pages in Google's index. Having looked at other community posts about http/https, I've gathered the following: http/https is like two different domains. http and https versions need to be verified in Google Webmaster Tools separately. Set up the preferred domain properly. Rel-canonicals and internal links should have matching protocols. My thought is that we will do a .htaccess that redirects old URLs regardless of the protocol to new pages at one protocol. I would probably let the .css and image files from the current site 404. When we develop and launch the new site, does it make sense for everything to be forced to https? Are there any particular SEO issues that I should be aware of for a scenario like this? Thanks!
Intermediate & Advanced SEO | | GOODSIR0 -
SEO implications of serving a different site on HTTPS vs. HTTP
I have two sites: Site A, and Site B. Both sites are hosted on the same IP address, and server using IIS 7.5. Site B has an SSL cert, and Site A does not. It has recently been brought to my attention that when requesting the HTTPS version of Site A (the site w/o an SSL cert), IIS will serve Site B... Our server has been configured this way for roughly a year. We don't do any promotion of Site A using HTTPS URLs, though I suppose somebody could accidentally link to or type in HTTPS and get the wrong website. Until we can upgrade to IIS8 / Windows Server 2012 to support SNI, it seems I have two reasonable options: Move Site B over to its own dedicated IP, and let HTTPS requests for Site A 404. Get another certificate for Site A, and have it's HTTPS version 301 redirect to HTTP/non-ssl. #1 seems preferable, as we don't really need an SSL cert for Site A, and HTTPS doesn't really have any SEO benefits over HTTP/non-ssl. However, I'm concerned if we've done any SEO damage to Site A by letting our configuration sit this way for so long. I could see Googlebot trying https versions of websites to test if they exist, even if there aren't any ssl/https links for the given domain in the wild... In which case, option #2 would seem to mostly reverse any damage done (if any). Though Site A seems to be indexed fine. No concerns other than my gut. Does anybody have any recommendations? Thanks!
Intermediate & Advanced SEO | | dsbud0 -
UK Company Major drop in traffic & rankings on one primary keyword since March
I am helping out a small UK company who have had a sudden drop in organic search traffic since March 24th. Investigation highlights some issues with the site,e.g. Potential canonicalization of home page, a few html errors, some inbound links to the /index.html version of the homepage rather than /. But, nothing particualrly major and nothing that is different to pre-March 24th. The indexed pages looks ok in Google (although Bing is ranking the non-www version of the homepage) but this does not appear in Google's index. Searches for the company name on Google.co.uk show it as top result & some keywords are ranking reasonably well (based on homepage). Selecting blocks of text from the homepage and it ranks #1, but its Google rank for the primary keyword has gone from #2 pre-March 24th to not in the top 100 results since. SEOMOZ is grading the page A for the keyword which appears prominently on the page & keyword is the first characters of the title. It is not a particularly competitive keyword. Adding UK to the keyword and the page is Google.co.uk ranked #3. It's almost as if they are being penalised for a single keyword which I've never seen or heard of before. Any ideas? ** The company has never carried out any SEO - white hat or black hat. The site is perfectly normal, nothing dodgy or concerning about it at all.** Thanks in advance for your advice.
Intermediate & Advanced SEO | | bjalc20110 -
Push for site-wide https, but all pages in index are http. Should I fight the tide?
Hi there, First Q&A question 🙂 So I understand the problems caused by having a few secure pages on a site. A few links to the https version a page and you have duplicate content issues. While there are several posts here at SEOmoz that talk about the different ways of dealing with this issue with respect to secure pages, the majority of this content assumes that the goal of the SEO is to make sure no duplicate https pages end up in the index. The posts also suggest that https should only used on log in pages, contact forms, shopping carts, etc." That's the root of my problem. I'm facing the prospect of switching to https across an entire site. In the light of other https related content I've read, this might seem unecessary or overkill, but there's a vaild reason behind it. I work for a certificate authority. A company that issues SSL certificates, the cryptographic files that make the https protocol work. So there's an obvious need our site to "appear" protected, even if no sensitive data is being moved through the pages. The stronger push, however, stems from our membership of the Online Trust Alliance. https://otalliance.org/ Essentially, in the parts of the internet that deal with SSL and security, there's a push for all sites to utilize HSTS Headers and force sitewide https. Paypal and Bank of America are leading the way in this intiative, and other large retailers/banks/etc. will no doubt follow suit. Regardless of what you feel about all that, the reality is that we're looking at future that involves more privacy protection, more SSL, and more https. The bottom line for me is; I have a site of ~800 pages that I will need to switch to https. I'm finding it difficult to map the tips and tricks for keeping the odd pesky https page out of the index, to what amounts to a sitewide migratiion. So, here are a few general questions. What are the major considerations for such a switch? Are there any less obvious pitfalls lurking? Should I even consider trying to maintain an index of http pages, or should I start work on replacing (or have googlebot replace) the old pages with https versions? Is that something that can be done with canonicalization? or would something at the server level be necessary? How is that going to affect my page authority in general? What obvious questions am I not asking? Sorry to be so longwinded, but this is a tricky one for me, and I want to be sure I'm giving as much pertinent information as possible. Any input will be very much appreciated. Thanks, Dennis
Intermediate & Advanced SEO | | dennis.globalsign0