Forum Moderators: Robert Charlton & goodroi
Pls help how can I do now? how to explain this to my boss?
Still, it can't hurt to work your way through these threads about site issues that sometimes cause trouble:
Checklist for Sudden Drops in Rank [webmasterworld.com]
Dropped from Google - a checklist to find out why [webmasterworld.com]
Dropped Site Checklist [webmasterworld.com]
As for the immediate problems, we are in Google's hands -- no one has a good handle on this right now.
Why pages are dropping in Big Daddy and not Non-Big Daddy I dont understand.....it would have made more sense the other way around.
Oops - sorry should say aswell. When Big Daddy seems to be handling the hijack correctly.
Also you may want to consider redirecting non-www to www as both the domain.com and the domain.com homepages are appearing.
Also you may want to consider redirecting non-www to www as both the domain.com and the domain.com homepages are appearing.
Can it be helpful?
We had installed vbulletin sitemap and aftering running that for sometime noticed that FORUM pages were dropping(was 39000+ and now stays in area of 600s to 700s).
some introduce the old site, it has PR 7, traffic is more then 40,000 dailly, google's refer is 50%, is an excellent and authority site. but it's sub-domain name, so we buy the newexample domain name.
yes, the new and old one are the same, so we use the 301 redirect. and we create a google site to push it to be indexed by SE.
What a pity, on the google site map account, I can see there are some 404 erro links here,
At present, the newexample site has a PR 2, and from some SEO tools, I can see its live PR is 7.
Question: its indexed pages are drop from 256,000 to 3 now.
Traffic drop to about 1,000 daily from Google.
How can I do?
It's the 301 redirect effect? or google sitemap? or others?
and it seems not redirect process for the home page.
there are:
[newexample.com...]
[newexample.com...]
http://www.example.com/HOME.HTM
That would be another problem?
[webmasterworld.com...]
Does SE knows 301 redirect very well? we use the 301 redirect from old site to new site.
Your goal is to ensure that you have only one url for any page. A 301 redirect is fine, because before the page is served the url changes, and you can see that in the location bar. 302 redirect is NOT fine, even though the location in the address bar changes. 302 is a "temporary" and not a "permanent" redirect. It can be handled differently by search engines. So definitely check the server headers thoroughly for a variety of urls.
Here are some things you can check:
Do both the no-www and the with-www versions of the old site redirect with a 301?
Is it really a 301 and not a 302?
Do all the urls from the old site redirect or just the home page?
Do you use a custom error page for either domain?
If so does that page return a 404 header -- or is it a 200?
Does the no-www version of the old site 301 redirect to the with-www version?
If yes, on all pages or just the home page?
Do you link to the home page by using the domain name only, or do you use index.htm, home.asp or some other page name?
Do you do any click-path tracking in a query string, rather than with a cookie or webbug?
Are you using session ids in the url query string?
Are you doing any content negotiation and serving different content at the same url to different user?
Any of these things can cause excessive duplicate content issues and cause pages to vanish, over time.
Here are some things you can check:
Do both the no-www and the with-www versions of the old site redirect with a 301?
Is it really a 301 and not a 302?
Do all the urls from the old site redirect or just the home page?
Do you use a custom error page for either domain?
If so does that page return a 404 header -- or is it a 200?
Does the no-www version of the old site 301 redirect to the with-www version?
If yes, on all pages or just the home page?
Do you link to the home page by using the domain name only, or do you use index.htm, home.asp or some other page name?
Do you do any click-path tracking in a query string, rather than with a cookie or webbug?
Are you using session ids in the url query string?
Are you doing any content negotiation and serving different content at the same url to different user?
Any of these things can cause excessive duplicate content issues and cause pages to vanish, over time.
Find another way to do what you need to do for sessions -- cookies or some other method that does not require a different url for each session.
You also could replace in-site home page links with http://www.example.com/ -- instead of home.htm. This is probably not the cause of your pages vanishing, but it could help your home page PR. Even after you fix the session ID issue, your in site links as they are will mean that home.htm can accumulate its own PR, separate from http://www.example.com/ -- and fixing internal links will stop that split from happening. But as I said, this is quite secondary.
Linking internally to "home.htm" can cause the "duplicate content" problem. Google sees your domain name and the "home.htm" as 2 separate pages with duplicate content and/or can not disseminate the links from the domain name through the site as none of the internal pages link back to the root (the domain name). It sounds strange, because it is. But that is what the Big Daddy update is meant to be fixing, unfortunatley it seems to be making it worse.
Either way, linking all internal pages to the root domain and replacing session URLS with another form of session tracking like cookies would seem to be the best change you could make if any.
My site, www.newexample.com is a new one, lanuched on Nov 2005, and www.oldexample.com is an old site
New domains, even with a 301 from an old domain, can take months to get their urls established in the Google index. This has been called the "Sandbox Effect" -- and before Big Daddy started to dominate this forum there were many, many, many threads about it. There is a chance this may also play out in the future of your new domain. Google is attempting to protect themselves from spamming by new, "disposable" domains.
Get any links you can to point to the new domain name, including some "deep" internal links. And other than that, continue to build quality in every way you can. It sounds like you've got lots of traffic and that should help make any sandbox effect you suffer relatively short.
Get any links you can to point to the new domain name, including some "deep" internal links
We get about 10 back links to this new site. most of their PR are 6-8, but still now track on Google, the new site's back link also zero, don't know why.
May I still need to deal with the session ids? and the home page?
In summary all those things mentioned are the current hurdles to get in to Google - it highlights the issues that need to be looked at when addressing Google.
I would say sort all 3 things to be sure, but it is hard to say which one(s) are the cause - although de-ranking on new domains with full page counts in Google would more than likely be the sandbox, and drastic reduction in page counts could be the other issues.
I have correct the duplicate homepage already.
What happened? The PR update, and our site gets a good PR 7, but the indexed pages drop a huge.
dropped from 250, down to 170, down to 150, now 120 :(
VERY bad, have no idea what's wrong.
