homepage Welcome to WebmasterWorld Guest from
register, free tools, login, search, pro membership, help, library, announcements, recent posts, open posts,
Become a Pro Member
Visit PubCon.com
Home / Forums Index / Google / Google SEO News and Discussion
Forum Library, Charter, Moderators: Robert Charlton & aakk9999 & brotherhood of lan & goodroi

Google SEO News and Discussion Forum

https: image filepath on an http: page

 5:30 pm on Oct 17, 2007 (gmt 0)

There has been lots of helpful WebmasterWorld discussion on web sites being indexed as https://domain.com instead of the desired [domain.com....]

Way back when (6 or more months) we used some of the techniques posted in those discussions for one of our online stores and thought we had everything "clean" and had kept G from reaching our https: pages.

However, we neglected to spot some absolute https: refs being used for button images in a left navigation panel which appears for every http: page in the online store. This came to light last week and we changed them to relative references resolving to an http: image.

Now for the question.. (w.r.t. Google) has any of the "https-ness" rubbed off onto:
the link associated with the image,
to the page where the images were located or
to the SITE?

The reason I ask is that prior to this, even though we thought we had everything "clean", one could, on occasion, a site:domain.com and get https://domain.com as the first entry.

I know a rewrite rule or some way of doing a re-direct would probably have been best, but the storefront software generates the actual references from a config file and we have no way of making changes to the code.

What I'm curious about is how Google treats an http: page with https: image references in the context described above.



 5:42 pm on Oct 17, 2007 (gmt 0)

The key is this - how does your server respond to a request that uses the https: protocol for a non-secure page.


 6:16 pm on Oct 17, 2007 (gmt 0)

We spotted our problem when migrating to a new server last week.

Prior to last week, https: to a non-https (non-secure page) would complete as normal. Ie, the certificate was tied to domain.name, so https://domain.com and [domain.com...] both worked

On our new server, the https is being handled by https://secure.domain.com and any reference of https://domain.com (non-secure) will result in 401.\


 6:40 pm on Oct 17, 2007 (gmt 0)

Sounds good - any leftover https: urls in the Google index should disappear. Can you also place a "disallow: /" rule at https://example.com/robots.txt? That's the Google recommendation.

Global Options:
 top home search open messages active posts  

Home / Forums Index / Google / Google SEO News and Discussion
rss feed

All trademarks and copyrights held by respective owners. Member comments are owned by the poster.
Home ¦ Free Tools ¦ Terms of Service ¦ Privacy Policy ¦ Report Problem ¦ About ¦ Library ¦ Newsletter
WebmasterWorld is a Developer Shed Community owned by Jim Boykin.
© Webmaster World 1996-2014 all rights reserved