Pages Indexed With Secure URL

Google spidered our pages using our secure URL... What now?

[SEOgle]

Sometime during the last update Google spidered a secure page on our site and from there seems to have continued to spider the site through our secure URL even though the page has no links to any other pages. I don’t know how this happened, but now I have many of our pages showing up through the secure url as follows:

[wXXXX.securedweb.net...] mypage.asp

instead of:

[domain_name...]

What happened and what can I do to fix this? I tried to use Google’s remove page tool, but it says it does not work on https pages.

Will Google mistake this as a duplicate page and penalize?

Help!

[SEOgle]

OK, I found out why it happened... Now I just wish there was something I could do to remove the bad listings.

A new section of the site that another developer is working on had a page that was accessed using the secured url and it had a link back to the home page that did not disable the secured connection, so from there Google indexed about 30 other key pages that have now bumped the unsecured version out of the results. The pages are not doing near as well as the previously correctly indexed pages did. Duplicate content penalty?

I fixed the problem that caused it and cursed out the other developer, but is there anything I can do to nuke the bad listings? Will they eventually drop off by themselves or is there anything I can do to speed this up? What are the chances that Google would respond if I emailed them and asked them to remove the bad listings?

Thanks in advance for any help or suggestions!

Patrick

[mediaman]

Contact Google and tell them of the mistaken SSL listing.

They can manually remove it.