Hi DP, Wonder if anyone else out there is experiencing the same thing. I have a couple of new sites I launched at the very end of February, a few days after googles most recent PR update. The main difference I am noticing is my site's all show the PR as being "N/A" when they are now indexing and one is starting to get a trickle of organic traffic. In the past I would see my sites have PR 0 after a few days or just over a week of being launched, and it would definitely be a 0 when they were starting to get organic traffic. Has anyone experienced this before or is this just something starting up now? Another weird detail, I did have a domain parked with GoDaddy for a few months before building a site on it, and at the beginning of last week it was a PR0 as soon as launching, but the old GODaddy parking page was what was indexed in googles cache. My guess this has something to do with Feb's PR update. Possibly it will take a lot longer, or even for the next update for a site to show any kind of PR. Maybe some kind of anti-PR passing link sales strategy? This would be a move in the right direction on their part to get rid of low quality brokers and spammers.
This would be a strange policy which resisted buying a PR while not admitting it completely, maybe just something broken or is it due to the acquisition of the first links of the same sources. Indeed, something may change. Time will tell if this trend will continue.
Can you clarify a bit more on what you mean by the acquisition of the first links of the same sources?
It's question of indexing methodology. Often we get lazy and get the first links from the same or similar sources. It is possible that Google look for the websites that link to and too often some newly indexed pages. This is just my theory, not fully tested.
Ah I understand now. I too have been worried about stuff like that. I usually refrain from placing outbound links on any of my sites until they are indexed, but sometimes I will start link building to my site before indexing to get a head start. Possibly this is causing an issue?