Hello all, I'm new to SEO and am tryin my best to get some positive results in Google for my company's website: www.dawsonmeetings.com for the keywords: Corporate Meeting Planning. The domain was registered back in 1998, although I recently put it on a new host with all new content. It has been indexed by Google since then, but I cannot get it rank at all in the DP keyword ranking tool. It appears to be sandboxed, although I thought that only applied to new domains? It does have some backlinks from the old days and a Page Rank of 4, which to me should be reasonably competitive (top 10) by my evaluation. I studied pretty hard on optimization techniques, but I hope that I haven't taken things too far. If anyone would be willing to take a look at it and give an opinion I'd much appreciate it. I did re-submit the site to Google which I later learned was not necessary. I hope that did not sandbox me. I did try the seomoz tool and did not get a definitive result.
Your are not sandboxed. You just need a few more inbound links. Try to work your way into directories, and submit your website, with keyword rich titles.
http://www.google.com/search?site=w...c2coff=1&q=www.dawsonmeetings.com&btnG=Search why is the result url different?
Seems like you founf the issue. Either a 302 hijack or server problems. Expertu, I was only joking with my sandbox: command.
hey i just found out you use the "sandbox" query to find out if a site is in the google sandbox. its something which wanted to know. great. i used the site command earlier today and my site went up from 73 to 690 pages in the google cache and now its come back to 89. any idea why?
i guess its pretty easy to fool people when its owt to do with google and seo, its what everyone wants to know.
LMAO that'd be unfortunate if I had discovered, by accident of course, the 'add my site to the sandbox' command. That'd be a goldmine if I knew that. Competitors will be eating their hair from despair. Man, that'd be awesome. *Runs off to code a script that tries all relevant commands...*
Thanks for the advice guys. I was not aware of the url www.dawsonmeetings.com coming back with the wrong resulting domain www.usarrangers.com in google. We actually own both domains, but the www.usarrangers.com site is being hosted/managed by another company and I am doing www.dawsonmeetings.com myself as a replacement. It includes information about the Company U.S.Arrangers (one of our divisions) within the new site. I plan to eventually do away with the content currently listed at www.usarrangers.com. There was a time previously when www.dawsonmeeetings.com pointed to the www.usarrangers.com website. About a 2 months ago we changed the dns to point to a new location for www.dawsonmeetings.com. Google has obviously indexed the new website, but why is it still showing www.usarrangers.com as the resulting url on the search for www.dawsonmeetings.com? I don't know if there are any redirects but perhaps there is something in place at the usarrangers.com host that is causing this? I am going to check with them to see if they have a 302 redirect in place. So if I have them remove it it should fix it the next time Google crawls? Thanks again - especially for the sandbox: command. Ultra useful! You probably didn't know about this one though: removefromsandbox:url /addtotop5 /FreeSponsorResults180days or this one is even better: googlesearchresults:url /redirectall (directs all Google Search Results worldwide to redirect to your site - warning: causes very heavy server load - be prepared if you use this one) I found that one on hillbillyhackers.net I figured that a 6 year old domain shouldn't be subject to sandboxing, but I wondered if resubmission with all new content at a new IP might still get you there.
You were close Tops. This is a command I didn't think I would share... but I've wanted to contribute more lately. So here is the screenshot of the command... I used it on a site from your sig. Hope you don't mind... Edit: Just a side note, I didn't make use of the "Erase Google cache of this site"
Yeah... that's the tricky one. Haven't nailed down what that command actually is yet... but I think I'm getting closer. Glad you liked it though.