Whitespark below header forums

User Tag List

Thanks Thanks:  1
Likes Likes:  2
Results 1 to 4 of 4
  1. #1
    Member Since
    Dec 2013
    Location
    Indiana
    Posts
    182
    Thanks (Received)
    6
    Likes (Received)
    9
    Mentioned
    1 Post(s)
    Tagged
    2 Thread(s)

    Client went to https, but also went to non-www. from www.domainname.com

    Hi All,

    One quick question. I had a client that suddenly went to https without telling me, but, they also went from Home - www.domainname.com to Home - domainname.com

    Google has gone out of the way to communicate that these kinds of changes are not to be penalized anymore (at least, http to https). I'm not sure if they meant ALL types of redirects.

    My advice to my client is to move it back to the original subdomain, with the https. My question is, am I being too sensitive? Will they be ok just as is?

    I just think, you can't risk it with these sorts of things, and even though Google says one thing, and their outward pronouncements may be correct, I don't want to misinterpret it - or apply it to a different situation.

    (and, I'm kind of pissed at myself for not noticing the www. non www issue)

  2. GradeUs in threads
  3. #2
    Member Since
    Jun 2012
    Location
    Ottawa, Canada
    Posts
    2,346
    Thanks (Received)
    195
    Likes (Received)
    168
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)

    Re: Client went to https, but also went to non-www. from www.domainname.com

    Switching to https may result in a temporary period of time where re-indexing needs to be redone. The change from www may also cause that. But it shouldn't last more than a few months. The switch to https is absolutely a good idea and you may as well take care of the other switch at the same time.

    Make sure the redirects are done correctly. Make sure you make the correct corrections to the preferred version in GMB, etc.

  4. #3
    Member Since
    Oct 2012
    Location
    Pittsburgh, PA
    Posts
    946
    Thanks (Received)
    26
    Likes (Received)
    48
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Client went to https, but also went to non-www. from www.domainname.com

    Make sure they did the switch right as well. Crawl the site and look for any mismatched internal links. The biggest fails i've seen is in migrations like this where the team implementing overlooked something major.

    Switching both protocols will kill the site if it was done incorrectly. Cover all bases by crawling, identifying any missed links, redirecting the old versions, and then of course fixing the internal links so they're coded correctly on the site. No use in sending users through redirects if it's not needed. Also check for redirect loops/chains when you do that.

    Basically anything you look at and think "well... duh of course you need to do that," check anyway. You wouldn't believe how many "basic" things experienced webmasters miss. If they had a quality assurance (QA) checklist when making the changes - which they should have if they were organized - then ask for that too. It's always good to double check what passed or failed QA.

    For your question, "My advice to my client is to move it back to the original subdomain, with the https. My question is, am I being too sensitive? Will they be ok just as is?"

    Depends. All depends on the rationale for the subdomain switch and whether it was implemented correctly.
    My rarely updated website (I should fix that) - https://www.ericrohrback.com
    Follow me on Twitter
    Want to talk? Book time with me here
    Marketer / Operations Director @ RedShift

  5. Thanks djbaxter thanked this post
    Likes djbaxter liked this post
  6. #4
    Member Since
    Sep 2014
    Location
    San Marcos, CA
    Posts
    557
    Thanks (Received)
    25
    Likes (Received)
    40
    Mentioned
    2 Post(s)
    Tagged
    2 Thread(s)

    Re: Client went to https, but also went to non-www. from www.domainname.com

    I'd also add these suggestions:

    Claim all four versions of their URL in four different Google Search Console accounts and then indicate to GSC which one is the preferred version (the non-www https one).

    For the preferred one, in that one's GSC, do these things:
    • Add a sitemap and test it
    • Do a Fetch and Render
    • Request Indexing on the completed fetch and render

  7. Likes djbaxter liked this post

Similar Threads

  1. HTTPS Settings and How They Affect SEO
    By djbaxter in forum Organic SEO
    Replies: 0
    Last Post: 02-20-2016, 02:30 AM
  2. Replies: 5
    Last Post: 08-19-2015, 08:48 PM
  3. Embedding Google Map on non-https page
    By Lloyd Silver in forum Google Maps
    Replies: 2
    Last Post: 10-27-2014, 03:55 AM
  4. SMX: Google and Bing have different views on HTTPS
    By Dustybones in forum Local SEO & Ranking
    Replies: 0
    Last Post: 10-03-2014, 05:10 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
GradeUs above footer forums