Are you a Google Analytics enthusiast?
More SEO Content
Date Google Uses For Aging Delay
Posted 29 August 2006 - 08:09 AM
aging delay: If your site is less than 6 months old, it is being repressed on Google by some sort of aging delay. Tweaking, linking, resassembling your pages, and begging Google to tell you what is wrong will not help. This could go away at any time, but as of today, we believe this to be the case.
6 months is the earliest we've had anyone report normal rankings for a new site. Some sites are 8-9 months old and still repressed. At this time it is not clear what triggers the removal of this filter. In fact it is not even clear if it is removed on a site-by-site basis. It may even be a case where all sites started within a several week or month timeframe may be released enmasse.
Posted 29 August 2006 - 09:23 AM
Posted 29 August 2006 - 09:37 AM
Seeing that my domain is 5 months old, I was getting ready to get funky, but I guess that will have to wait.
Posted 29 August 2006 - 10:07 AM
Is it the first time they know about and spider a site? Or is it keyed to the first time they start seeing links pointing to the site? The two don't have to be the same thing yanno.
If I were planning on anything for a new site I would plan on it being after they started finding links to the site.
Posted 29 August 2006 - 11:05 AM
Posted 29 August 2006 - 12:25 PM
Posted 29 August 2006 - 01:22 PM
Posted 30 August 2006 - 05:02 PM
Anyway, you may want to check your internal links. I can find your main site with two URLs and that is usually an indication of split linkage, which is not helpful.
Also, judging by your title tag, I think you may be going for too many expressions on the front page.
Have you requested a site review?
Posted 30 August 2006 - 06:28 PM
When your site answers to both domain.com and www.domain.com, and there are other sites (and often your own) linking to both versions. The engines start out treating these as two distinct pages, with the links point to domain.com counting towards that page and links to www.domain.com counting for that page.
You can fix it with a little bit of redirect magic so that whenever someone goes to say domain.com they get redirected via a 301 over to www.domain.com.
Posted 30 August 2006 - 07:10 PM
I am pretty sure that's working so I am still confused by Michaels comments.
Posted 30 August 2006 - 07:20 PM
In your case, you have both "example.com" and "example.com/index.php" showing in the Google index. They are two different addresses for the same page that have their own links pointing to them.
Hence, you are getting split linkage.
You need to have all your links either point to the domain name alone or the domain name plus "index.php" if you have mixed linking styles internally.
If other people are linking to your site differently from the way you link to it, I'm not sure what you can do. I once crashed a server by trying to redirect an index page to itself to compensate for a similar problem.
I don't recommend you try that. Not unless someone with more technical savvy than me can explain the right way to do it.
Posted 30 August 2006 - 08:01 PM
I do see google has both versions, but am not sure how to fix that. I guess I could do a rewrite in .htaccess. Something like rewriting /index.php?act=Help to /help.html. Not sure that would fix anything since like I said this is all built on Invision Power Board forums.
Oh what to do.
Now that I think about and look at it further, all dynamic pages should be seen as url friendly html pages based on my .htaccess configuration. So, I am wondering where google is seeing index.php, unless my .htaccess and robots.txt aren't working properly.
Edited by seo_challenged, 30 August 2006 - 08:52 PM.
Posted 31 August 2006 - 08:31 AM
I haven't looked at the site in question, but based upon what Michael says he's seen, the main thing that could be splitting your link juice is www.domain.com/ and www.domain.com/index.php
What kind of server are you on? If it's a Unix/Linux -> Apache system you may be able to use something we've discussed around here a few times before. In fact, I think the original time it came up was concerning a forum as well.
Do a search of the forums for the phrase THE_REQUEST --with the underscore in there-- and you should find these threads. As Michael mentioned, you have to be careful not to throw the server into an endless loop when trying to work with the default index files. Apache's THE_REQUEST is the perfect tool to use for such situations since it keys to the actual user's request and not where the server happens to be pulling the file from.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users