In my estimation. Alexa needs to be thoroughly spanked.
At the very least, this company needs to offer an easier platform so that information can be updated easier, keeping in mind that
1. Not every website owner has activated the email@example.com feature. For Poets.net, my registrar charges extra for domain-based email, and I don't need this to conduct my business, so I'm not inclined to pop for this so that I can do Alexa's job for them.
2. Not everyone is tech-savvy enough to place a code .txt code on one's site. In fact, I'm not even sure my blogger site offers this feature, and even if it did, I wouldn't know how to use it.
So I emailed Alexa directly FROM MY EMAIL OF DOMAIN RECORD along with a link to my WHOIS information and asked that they please update my information manually. I recieved this email from Alexa's customer NO SERVICE:
Thank you for contacting Alexa regarding the contact information for your website.
In order to protect our users, Alexa's contact information submission tool (http://www.alexa.com/data/details/editor?type=contact ) only accepts submissions for sites when the submitter's email address matches the site's domain. In other words, if you are trying to submit/change/de-list information for mydomain.com, you must use an email address that ends in mydomain.com. You can use any address from that domain; firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, etc. This is the easiest automatic way that Alexa can confirm that you are a legitimate representative of the site, and allows us to process your submissions more quickly.
In cases where the email address does not match the domain of the site, you can submit your changes to be verified automatically by following the instructions on the Contact Information Editor page. These are just below the field where you would have submitted your domain-matching email address if you had one.
This method involves placing a text file we will generate for you on the root of your site, verifying that the text file is in place, and sending our crawler to "fetch" the contact info. This process essentially demonstrates that you are authorized to make site-level changes and expediting your updates. For example, if your site was www.mydomain.com, the info.txt file would go at www.mydomain.com/info.txt.
In order to use this method, proceed through the Contact Information Editor until you reach the page that shows an overview of the data you've changed on the previous page's web form. Look just below the "Continue" button for the section titled "Or, Place a file called info.txt on the root of your site" and follow the instructions.
If the "info.txt" method will not work in your case, you may reply to this message with the information you would like to have us update, and a link to somewhere on your site that our editors can visit to verify the legitimacy of the request (somewhere that has your contact information and lists this e-mail address, for example--to be sure nobody's trying to change your information without permission), we'll be happy to make the changes manually. Please use the info.txt format, for clarity.
Changes made to contact information will appear in our live Service within one to two weeks.
We appreciate your interest in Alexa.
Alexa Internet Customer Service
Huh? You got that? I sure didn't.
I don't put personal contact information on my website, and I use a different email that I give out to web users, which is why I emailed them directly from my email of record. I don't WANT my Whois email to appear on my site.
So this was my admittedly snarky response (which was never answered, by the way):
I don't use domain-based emails, and I'm not going to start now. My registrar charges extra for this, and I have discovered that the domain ends up on the black list because spammers LOVE hitching onto domain emails. I'm not sure what the problem is; I gave you to my Whois link for the domain--it's big as day there. And THIS email is the email of record. I don't have time to figure out your coding system, and I certainly don't want to download your toolbar (or anyone else's for that matter). If you want to maintain incorrect information for people's websites, knock yourself out. In the end, it's your company that will look like a big doofus corporation.
Meanwhile, my website will continue chugging along as usual and my traffic is recording with or without you. Have a nice day.
Let me make this clear: the WRONG information remains on the Alexa site. I'm sure that Edmund Skellings of Florida would prefer that his personal information be taken off Alexa's site, and I would sure like to see the following information put in its place:
Site Owner: Jennifer International
Email: Bugzita[at]gmail.com [which, for obvious reasons is different from my Whois email, which is why I originally emailed Alexa from my Whois email]
The rest of the fields to be left blank.
Would that be so difficult?
Wednesday, June 11, 2008
Alexa: The Web MIS-Information Company
Posted by Bugzita at 2:36 PM
Subscribe to: Post Comments (Atom)
THE Domain Page Cloud
.co (1) .co aftermarket (1) .co domains (1) .gov sites (1) .me (1) .mobi TLD (1) .Tel (3) .tv (2) .xyz Domains (1) 3D (1) 3D domains (1) 9/11 (1) A New Name (1) ABC (1) ABC Domains (1) ABC Song (1) acquisition (2) addy domains (3) advertising (1) advice (2) aftermarket domains (5) Aggregate news feed (2) aggregator (1) Airlines (1) Alexa (1) alma mater (1) Alpha Domains (1) Alphabet Domains (1) Alphahol (1) Alphahol.com (1) alternate viewpoints (1) anniversary (1) Anti-Phishing Consumer Protection Act of 2008 (2) Apple (5) Avatars (1) baby boomers (1) BabyBanana.com (1) BabyBanana.com UDRP Grab Denied (1) backorders (1) Bad Customer Service (1) bad history domains (1) Beanies (1) beta site (1) black list (1) blacklist (1) Blogging (1) boomersd (1) boutique TLDs (2) brand (3) brand protection (1) branding (4) browsers (1) buy-out (1) cars (2) Caution (1) Citizen Journalism (1) clone sites (1) Coined words (1) Created Baby Names (1) customer no-service (2) customer service (2) CVVC domain (1) Cybersquatters (1) cybersquatting (2) dawnm5723 (1) Defensive registrations (3) definitions (1) defunct websites (1) deleting domains (1) Democratic Party (1) dictionary (1) discussion (1) domain (7) domain aftermarket (5) domain auctions (8) domain deletions (1) domain do-overs (1) Domain donations (1) domain dumping (1) domain fire sale (6) Domain for Sale (1) domain kiting (1) domain list (4) domain mistakes (2) domain names (11) domain names in novels (1) domain parking (1) domain portfilios (1) domain registrar (1) domain registrars (1) domain sales (1) domain sales page (2) domain tasting (2) Domain Tools (1) Domain tools auctions (1) Domain Tools Blog (5) domain typos (3) domainers (9) domaining (10) domaining biz (1) domaining corruption (3) Domaining feed list (1) domaining feed sites (1) domains (12) dot-com (2) dot-coms (1) dot-me (1) dot-tel (1) dot-us (1) drop catcher (2) drop catching (1) dropped domains (1) Eastern Europe (1) eBay (1) EDAG (1) editorial (2) Elliot's Blog (2) end-users (1) essays (1) ethical domaining (3) ethics (4) expired domains (1) expired trademarks (1) FAFSA (1) fan fiction (1) Farewell (1) featured domains (1) feedburner (1) feeds (1) female domaining forum (1) feminist domainer (1) fiction (1) Fiction Headquarters (1) fire (1) fire safety (2) fire-sale domains (3) Flights (1) foreign domains (3) Frank Schilling (2) freedom of speech (1) Front-running (3) Furbies (1) Future of domaining (1) gambling (2) Gambling domains (1) generic domains (3) GoDaddy (2) going viral (1) good advice (3) Goodbye (1) Google (1) Google Chrome (1) greed (2) halvarez (1) Hernandez Family (2) holiday greetings (1) I.R.S. (1) ICA (4) ICANN (4) iCar (4) Idete (1) Idete.com (1) images (1) immigrants (1) Inauguration (1) Introducing our new name: THE Domain Page (1) Investing (1) iPhone (1) IRS (1) It's been real (1) It's JUST War (1) Jennifur.com (2) Jordan Fox Seales (1) Landrush (1) law (3) lawsuits (2) Learning curve (2) legal (2) letter confusion (1) Life is a brand (1) literary agent domains (1) literary language (1) Literary.me (1) literature (1) Lord Acton (1) Lotteries (1) Macedonia (1) micro-scamming (1) Microsoft (1) misspelling (1) mobi TLD (1) mobile apps (1) Mobile poetry (1) Montenegro (1) Ms Domain (1) msdomain.com (1) music.mobi (2) Name Change (1) name domain names (2) NameJet (1) negative domains (1) netsol (4) Network Solutions (4) New Blog (1) New TLDs (4) newbie advice (1) newbie domain mistakes (1) newbie domainers (1) News feed site (1) Newspapers (2) NewsVroom (1) NewsVroom.com (1) non-domaining post (2) novel (1) odd domains (1) Off-topic (2) one-word domains (1) Oversee.net (1) parking stats (1) Pending Delete Process (1) Pennsylvania (2) Pennsylvania Primary (1) phishing email (3) phone apps (1) poems (1) poetry (1) Poets.org (1) political domains (1) PoorWriter.com (1) prejudice (1) premium domains (1) President Barack Obama (1) Presidential Election (1) Pump and Dump (1) putnik (2) Putnik TV (1) Quill (1) Quill City (1) Quill College (1) racketeering (1) Registrant Search (1) Registrars (1) Review (3) Reviews (1) Rick's Blog (1) Sahar Sarid (1) scams (3) Sedo (4) self interests (1) Self SEO (1) selling domains (1) shill bidding (4) short stories (1) Snapnames (3) Snark.me (1) Snark.tv (1) Snowe Bill (1) spam (1) speculation (1) spelling (1) spoof meaning (1) spoofs (1) Squidoo.com (1) statistics (1) stereotypes (1) Student Loans (1) successful business people (1) Ta Ta (1) Tax (1) Tax domain (1) Tax Preparation (1) technology (4) telnic (2) The ABC Song (1) The Alphabet Craze (Let’s Sing the ABC Song) (1) THE Domain Page (1) THEDomainPage.com (1) Time to move forward... (1) TLDs (3) TM domains (1) trademark infringement (5) Trademark TLDs (1) trademarks (6) Traditional Journalism (1) traffic (2) Travel (1) travel site (1) travel sites (2) Travel TV (1) TV Putnik (1) typos (3) U.S.P.S (1) UDRP (1) UDRP rulings (1) Uniregistry (1) Uniregistry.com (1) Universal Postal Union (1) unregistered domains (1) UPU (1) usage (2) user-generated content (1) USPTO (2) vanity TLDs (2) viral marketing (1) Volkswagen (4) VW (4) w or vv (1) Warnings (1) Warren Buffet (1) Web 2.0 (1) WIPO (1) writing (1) Yahoo (1) York College of Pennsylvania (1) York Daily Record (1) York Pennsylvania (1) York Sunday News (1) Yugoslavia (1)
Post a Comment
Word verification has been enabled to circumvent spammers, not to censor bona fide posts. ;=)
I welcome your comments!
Note: Only a member of this blog may post a comment.