Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

All supplemental except index page

9 month old site penalized?

         

southernmost

7:14 pm on Dec 18, 2005 (gmt 0)

10+ Year Member



I have a 9 month old site that still doesn't rank for any terms. It has a modest number or backlinks, very slowly growing.
When doing a site:www.mysite.com search, all pages except the home page are listed at supplemental results.
Will someone tell me if this is bad news? Any cure?

texasville

3:41 am on Dec 19, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I would say that's a penalty. Usually because of duplicate content. Did you write the content?

mycutegoddess

6:37 am on Dec 19, 2005 (gmt 0)

10+ Year Member



Do you update these pages regularly? If not these pages can be supplemental....

southernmost

2:30 pm on Dec 19, 2005 (gmt 0)

10+ Year Member



Yes, the content is all original, although there are only 10 pages so far. It has not been updated much though...just sort of built it have been waiting for it to rank for something before I build more.
I've searched for some unique long phrases from the site, and I don't see anyone copying it (only my site comes up in the serp)
Should I start to continually adding content? Will this get the site on it's feet?

g1smd

10:16 pm on Dec 20, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Make sure the title and meta description is different for each page, and that each represents what is actually on that page.

Run Xenu LinkSleuth over the site to check for problems.

southernmost

2:29 am on Dec 21, 2005 (gmt 0)

10+ Year Member



I ran the linksleuth and there was nothing wrong there.
Each of the pages has it's own unique title and description accurate to the pages content.
If it's a dup penalty, there is no evidence of it anywhere...no quotes returned other than my own.
I am running Adsense on the site, and one of the pages has affiliate posters. Could this be the penalty?

imweb

5:11 am on Dec 21, 2005 (gmt 0)

10+ Year Member



I had a similar problem for my 20-page site. Then I started to do the following 2 months ago:
1. Fixed www and non-www URL via 301 redirect
2. Cleaned pages from on-page styles resulted from DW. Use off-page css file and edit manually using text editor.
3. Removed JS code from header.
4. Reduced site interlinking. Remove common links like Contact, About, privacy, link page from every page except homepage. Only add link in the right context.
5. Validated all pages.
6. Add more pages with "new addition" link at homepage.
7. Add RSS feeder as I plan to add more pages.

Last week 35 pages have been in index correctly without supplementals. I have focused on content and spent little on link exchange.

Shurik

6:24 am on Dec 21, 2005 (gmt 0)

10+ Year Member



Imweb, i did none of what you described and yet today most of my pages on one of the subdomains went from supplemental to fully indexed. Go figure...

imweb

7:16 am on Dec 21, 2005 (gmt 0)

10+ Year Member



Shurik,

Tell us what you did. I 'd like to learn if you have a silver bullet.

reseller

7:24 am on Dec 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Shurik

>>Imweb, i did none of what you described and yet today most of my pages on one of the subdomains went from supplemental to fully indexed. Go figure...<<

No go figure, please :-)

Tell us which DCs you have noticed that happening on. Thanks.

southernmost

2:56 pm on Dec 21, 2005 (gmt 0)

10+ Year Member



shurik - do tell. what did you do to move the site out of the supplemental index?
Of all the possibilities, it may be that the site is stale and not been updated. My plan has always to build the site up, but I was waiting for the site to tell me it's ready.
On the other hand, I don't want to pour too much effort into a site that has some sort of permanent penalty.

southernmost

3:24 pm on Dec 21, 2005 (gmt 0)

10+ Year Member



Maybe it's the www vs non www issue.
Here are the symptoms.
1) all pages, except homepage, are supplemental.
2) homepage has no cache, and, again, is not listed as supplemental.
3) a site: search without the www returns an extra result - a url-only listing of the homepage, and not indicated as part of the supplemental index.

So this may be a duplicate content issue generated by the www vs. non-www version. And if so, would necessitate some type of 301 work (something I'll need to learn).

Make sense?

g1smd

4:06 pm on Dec 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I am involved with a lot of sites that are correctly indexed and do have the 301 correctly set up, and only a few that have been mis-indexed by Google.

For every properly listed site, the alternative URL for the main index page (domain.com vs. www.domain.com) is always shown as a URL-only listing.

I think this is normal behaviour. Google knows that the domain exists, but makes a note that it redirects elsewhere, and then doesn't list any of the internal pages.

For sites where it all goes wrong, Google starts showing a bunch of internal pages from the "wrong version" as supplemental results, and these are impossible to shift.

One way that this happens is if you have both www and non-www indexed (with a whole load of pages filtered out as duplicate content) and you then set up the redirect, what happens is that Google then indexes more and more of the www pages and appears to drop the non-www pages out of the index. If you then change the content of some pages, the non-www pages that had been filtered out as duplicates have their old cache of non-www compared to the more recent cache of www, are found to no longer be duplicate content (the www was updated remember) and so the non-www pages reappear in the index (with Google completely forgetting to check that the pages are actually now just 301 redirects) and have an ancient cache (because no content can be fetched directly from that URL because the URL just redirects elsewhere).

g1smd

4:28 pm on Dec 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I am involved with a lot of sites that are correctly indexed and do have the 301 correctly set up, and only a few that have been mis-indexed by Google.

For every properly listed site, the alternative URL for the main index page (domain.com vs. www.domain.com) is always shown as a URL-only listing.

I think this is normal behaviour. Google knows that the domain exists, but makes a note that it redirects elsewhere, and then doesn't list any of the internal pages.

For sites where it all goes wrong, Google starts showing a bunch of internal pages from the "wrong version" as supplemental results, and these are impossible to shift.

One way that this happens is if you have both www and non-www indexed (with a whole load of pages filtered out as duplicate content) and you then set up the redirect, what happens is that Google then indexes more and more of the www pages and appears to drop the non-www pages out of the index. If you then change the content of some pages, the non-www pages that had been filtered out as duplicates have their old cache of non-www compared to the more recent cache of www, are found to no longer be duplicate content (the www was updated remember) and so the non-www pages reappear in the index (with Google completely forgetting to check that the pages are actually now just 301 redirects) and have an ancient cache (because no content can be fetched directly from that URL because the URL just redirects elsewhere). These ghost entries sit in the SERPs for ever more. There is no way to get them removed. Google sees the redirect, but still doesn't drop the ancient cached page for that URL out of the index.

southernmost

4:38 pm on Dec 21, 2005 (gmt 0)

10+ Year Member



A header check returned this for a non-www request:

Server Response: [mysite.com...]
HTTP Status Code: HTTP/1.1 200 OK
Date: Wed, 21 Dec 2005 16:17:00 GMT
Server: Apache/1.3.33 (Unix) mod_gzip/1.3.26.1a mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 PHP/4.3.11 FrontPage/5.0.2.2635 mod_ssl/2.8.22 OpenSSL/0.9.6b
Last-Modified: Wed, 21 Dec 2005 16:11:41 GMT
ETag: "668801-1ec9-43a97ebd"
Accept-Ranges: bytes
Content-Length: 7881
Connection: close
Content-Type: text/html

Is this the problem?

g1smd

4:49 pm on Dec 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



You need to set up a 301 redirect for all non-www requests to be redirected to the same requested page but at www.

This question gets asked every day in this forum.

southernmost

5:41 pm on Dec 21, 2005 (gmt 0)

10+ Year Member



g1 - thank you, thank you for being patient enough to hear the same problem.
i noticed that when you do a header check for http:google.com they do what you are suggesting...a permanent 301.
Unfortunately, my host's redirection interface doesn't let me do it...it ends up redirecting all pages with a 301 error.
It's a cpanel host. I'm waiting to hear back from the host on the fix. Any ideas?

Shurik

7:00 pm on Dec 21, 2005 (gmt 0)

10+ Year Member



>>Shurik,
Tell us what you did. I 'd like to learn if you have a silver bullet. <<

I'm referring to a subdomains (non www) that was indexed by google at one time. Then it all went supplemental after allegrs (if i'm not mistaken) probably because it resembled a link farm too much. I gave up all hope of ever revitalizing it but was still actively exchanging links from it since it was doing very well in MSN and Yahoo. Just yestorday i noticed that it is now back from supplemental and almost fully indexed again. The subdomain never had a 301 issue, dup content or any other problems. It just had more outgoing links then incomong but not anymore. Maybe that is the secret...

g1smd

7:32 pm on Dec 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Add this code to your existing .htaccess file in the web root:

Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^domain\.com [NC]
RewriteRule ^(.*)$
http://www.domain.com/$1 [L,R=301]

southernmost

8:39 pm on Dec 21, 2005 (gmt 0)

10+ Year Member



I assume I replace my site name with the domain.
Also, is that backslash correct in the third line?
Sorry for being clueless. Actually, I just found the .htaccess file (it's blank)

Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^domain\.com [NC]
RewriteRule ^(.*)$ [domain.com...] [L,R=301]

Edit: I pasted the above into the htaccess file but it hasn't effected the header check info...still giving a 200 without any redirect.

southernmost

9:14 pm on Dec 21, 2005 (gmt 0)

10+ Year Member



O.k. Fixed!
Now it's working correctly.
Non www requests return a 301 Permanent redirect and then the www page returns a 200.
Nicely done.
I'll let you know if this improves things.

southernmost

9:19 pm on Dec 21, 2005 (gmt 0)

10+ Year Member



ignore, sorry.

southernmost

5:19 pm on Dec 26, 2005 (gmt 0)

10+ Year Member



Hopefully, this is a sign of better things to come.

The 301 permanent redirect is in place a week.

On the BigDaddy datacenter, 64.233.179.104 , the site is now indexed correctly and no longer listed as supplemental.

Thanks for your help!

g1smd

5:34 pm on Dec 26, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



What is the cache date for most of the pages?

southernmost

7:48 pm on Dec 26, 2005 (gmt 0)

10+ Year Member



Most pages are cached December 9 or 10. Some are also December 5 or 13.

The newest cache date is Dec 17 (it is the index page, the only one that didn't go into the supplemental index).

g1smd

7:56 pm on Dec 26, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



The cache dates predate your placing of the redirect?
Google may have fixed the problem algorithmically then.

southernmost

8:03 pm on Dec 26, 2005 (gmt 0)

10+ Year Member



Yes, it seems to be that the cache dates predate the 301 implementation.
Either way, thanks for your help.
One a side note: GoDaddy doesn't give access to the htaccess file. Is there another way to implenent the 301 permanent fix? I noticed on another site of mine that the www vs non-www versions show different PR.
(does a dedicated IP address help solve this?)

g1smd

8:37 pm on Dec 26, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



The .htaccess file lives in your web root. If there is none there, simply create a new one.

You need to set the preferences in your FTP program to show all files that begin with a dot to make sure that you are not overwriting an existing file.

southernmost

9:57 pm on Dec 26, 2005 (gmt 0)

10+ Year Member



Are you familiar with how to do this in Dreamweaver MX?
Where are the FTP preferences?

g1smd

10:20 pm on Dec 26, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Get yourself a proper, standalone, FTP program for this job: FileZilla, CuteFTP, FTP Explorer, whatever....