Examiner.com - Official Response and Analysis Regarding the Problems with their New Platform


Last Saturday I broke the news about Something is Broken on Examiner.com - Writers in Uproar. In it I listed several problems with the new platform revealed to my by a source. These issues has since been confirmed in the comments or via direct feedback to me.

I also notified Examiner.com about my post and invited them to comment on it. I have now received their response from Justin Jimenez, Director of Marketing & PR at Examiner.com. Below you can read their full, un-edited, responses to my questions. You will also find my analysis at the end of this post.

1. Why did Examiner.com opt to launch on Drupal 7 this early?

Examiner.com’s long-term strategic vision leverages social media for improving online content distribution, which Drupal readily supports. Our commitment to supporting the success and satisfaction of our Examiners fueled the need to improve our publishing tools. Drupal provided a customizable and scalable solution for our specific needs. 

Our goal is to provide the most value to our contributors, readers, and stakeholders. With that goal comes the responsibility to not only be a leader in local content generation, but online technology as well. If we built our infrastructure on Drupal 6, by the time this upgrade was finished it would be out of date. Examiner.com is striving to be at the forefront of CMS and web development and we are working with the leaders of the Drupal community to complete the cutting edge framework, helping to not only shape the future of Examiner.com, but the Drupal platform as a whole. Whereas most publishers are racing to adopt web 2.0 strategies, we are creating the next generation of web applications with technologies like RDF and NO-SQL database systems. We have the capabilities, the talent and knowledge to accomplish this as we employ the top Drupal contributors in the world.

While we understand Drupal 7 isn't appropriate for broad use, we have two of the most prolific contributors to Drupal 7 and we work closely with Acquia, the Drupal consultancy founded by the creator of Drupal, who also uses Drupal 7.  We have been pleased with the performance, stability, and functionality of Drupal 7.

2. Why was the new Examiner.com pushed out before it was ready?

The Examiner.com consumer experience was launched on schedule, and with the approval of both engineers and QA testers. This is and continues to be a very ambitious project. Not only did we have a complete a redesign, but a new technology platform, CMS and a new back office suite. All of these are tightly integrated to fuel the coming years of explosive growth. The site was as complete as possible when we launched. However, with over 1.5 million article in our archives and such sweeping changes occurring all at once, we expected and anticipated glitches in the system. All of these issues are in the process of being corrected, and none are critical.

Furthermore it's difficult to get solid feedback until users are exposed to it. We felt that we'd have a significantly better and stronger system over the long term if we released and had an opportunity to get feedback and fold that feedback into the system as we iterate. This is the foundation on top of which we plan to build a rich and robust set of tools and features for our community of readers and users.

3. What are you doing to fix these problems?

Examiner.com has some of the most talented and experienced Drupal developers in the world working around the clock to continue the evolution of the site. While there are still some outstanding issues to be addressed, we are very pleased with the enhanced functionality of Examiner.com and consider the launch a success and a huge leap forward.

4. Have writers that have complained got their status terminated, lost pay or not got responses to their support tickets?

No. We encourage our Examiner.com community to stay active and vocal. Every ticket submitted receives a response, and a notification upon resolution. We have over 50,000 contributors and we have seen support tickets citing problems submitted from approximately only five percent of them. That number is still higher than our average and we are working diligently to resolve all outstanding issues, but we are seeing a steady decline in these types of issues on a daily basis.  Also, due to an increased volume of tickets around similar issues, we also have a support center where all Examiners can see a list of known problems and progress in resolving them.

We are on schedule to launch our publishing tool on Drupal, and Examiners currently have the opportunity to practice and test the new system in a special fully functional testing area. The feedback they’re providing has been invaluable in helping to shape the features and functionality of both that tool and the site as a whole.

From previous post: “Examiner.com has 40-50,000 writers experiencing these problems right now.”

We have over 50,000 contributors, and of that number we have seen support tickets submitted from approximately five percent of them. That number is still higher than our average and we are working diligently to resolve all outstanding issues, but we are seeing a steady decline in these types of issues on a daily basis.

“The writers are of course not happy with losing income and all the other problems, and they have complained about it. My source reveals that Examiner.com is giving complainers a hard time, cutting their pay or not acting on their support tickets. The source even claims that one writer has got their Examiner status terminated after complaining about this in a forum.”

Inaccurate, unfounded and bordering on libelous. Please see above answer on question No. 4.

Follow up Questions

The above responses are from my original post, they didn't supply an answer my follow up post the same day, nor the updates I made to the posts a few days later. Therefor I them asked a few follow up questions before publishing this post.

First I referred to the added quote from J Craig Canada's blog post about his claim about being suspended after complaining.

I also referred to that comments to my posts, as well as direct feedback, has confirmed that many of the serious issues with the new platform was raised during the beta period:

Also, your answer to question 2 says that the new site was launched on schedule. In my other post, Examiner.com President Jim Davidson Talks About the Problems I asked the following question:

Wouldn't it have been better to postpone the launch until all old content had been migrated, navigational problems sorted and the new publishing tool ready?

The same post also just got this comment to it:

Improvements seem to be temporary. Problems listed as fixed are turning out to be broken again.

There are STILL Examiner writers who can't even access the publishing tool, and there are still links being directed to the wrong places --and that's just the tip of the iceberg.

Don't believe the PR hype that calls these "bumps in the road."

These are issues that my sources says was raised during the beta testing. How come they then managed to pass through the QA?

The response to this follow up from Justin at the Examiner.com was:

The answers I have provided are all I have for you at this time. However, I have provided a response on why Examiners may be suspended. Using one “source” out of 50,000 (.002%) would not be something to be considered an accurate statement to base sweeping accusations around the entire site or our company’s general practices.

No contributor has ever been suspended for complaining about the site. We only suspend access due to a violation of the terms of use which all Examiners enter into upon becoming an Examiner. That can include such things as plagiarism, fraudulent page views, unprofessional behavior among others. Each case is thoroughly investigated and each Examiner is given the opportunity to respond before the suspension is final.

Analysis

Regarding if an Examiner writer has been suspended or not for complaining about the new system is words against words. In my posts I have been clear about that I only heard about one such case, including linking to that writers claim about it. It has never been a "sweeping accusation". If it is true, then it is still one to many. Until the involved parts discloses the real reasons for this writers suspension, we are only left to draw our own conclusion about what has happened.

In their response to the first question Justin says "If we built our infrastructure on Drupal 6, by the time this upgrade was finished it would be out of date.". I can understand the reasoning behind that, but Drupal 6 is still a solid platform and I don't believe it will be outdated any time soon. It is still the official main release of Drupal and development of it, as well as contributed modules, have not slowed down, quite the opposite.

The answer to my second question starts with "The Examiner.com consumer experience was launched on schedule, and with the approval of both engineers and QA testers.".

Everyone involved in the Drupal community, or following it, knows that the development of Drupal 7 has taken much longer than expected. The beta release haven't happened yet because there are still big problems with for example the upgrade path. I have written several posts about this, such as Why is Drupal 7 Not Released Yet?. None in the Drupal community is happy about the delays, we want Drupal 7 out yesterday. But we accept the delays because we want a solid product to be launched.

I don't dispute that Examiner.com employs some terrific Drupal developers because I know they do. Nor do I dispute that they work closely with Acquia. But their answers confirms that the new Examiner.com was "launched on schedule". Developers or partners are not the ones taking that decision, management at Examiner.com does that.

I completely agree with "Furthermore it's difficult to get solid feedback until users are exposed to it.". Developers as well as a small selected test group can only test a product so far. A big, complex project like the new Examiner.com is bound to have bugs and other problems even after release, its just how things are.

In this case, Examiner.com decided to build their new platform on a bleeding edge product that has not even been released yet. The new site has been in development for over nine months according to Jim Davidson, President of Examiner.com. They are fully aware about that Drupal 7 is being delayed and is far from ready. During the beta testing period a lot of serious issues with the new platform was raised. Then, Instead of launching it on schedule they should have adopted a flexible launch schedule, adjusting it based on the development of Drupal 7 as well as the feedback from the beta testers.

To their defense I have received feedback from writers saying that some problems have been fixed. There's also no question about that they are working around the clock to sort the remaining problems out.

Still, much of this situation could have been avoided if the launch had been pushed forward a few weeks, giving the developers the needed time to fix the most sever problems, instead of being "Launched on schedule".

Comments

Re: Examiner.com - Official Response and Analysis Regarding ...

I seriously doubt that J Craig Canada was suspended. Maybe he hit a bug where he was unable to login but he has been posting daily, several times a day on the examiner.com writers community forums and if he were suspended he wouldn't have access to them.

Re: Examiner.com - Official Response and Analysis Regarding ...

Hi,

Obviously I don't have access to the writers forums, but the last public post, on the Examiner.com, by him was August 15th.

/thomas

Re: Examiner.com - Official Response and Analysis Regarding ...

J Craig Canada has not made an entry to his personal blog since the post you mentioned. Maybe he is suspended from that as well.

Have contacted Mr. Canada directly to ask him?

Also it is not clear from your article was J Craig Canada a part of the beta testing?

Your blog reads like tabloid journalism, "Last Saturday I broke the news about Something is Broken on Examiner.com - Writers in Uproar."

Are you writing about the advancement of Drupal? Or just trying to make a name for yourself off of this event?

Re: Examiner.com - Official Response and Analysis Regarding ...

Hi Anonymous,

Yes, I have been in contact with J Craig Canada. I have also linked to his own public blog post which I quoted from. In that he details and confirms many of the issues I have listed in my own posts. I wasn't aware of his post until after I posted mine, thus the update a few days later.

Whether he has been part of the beta testing or not has nothing to do with the part he has in this. Other writers have confirmed that to me.

Did you even read my original post? If you didn't I suggest you do. In it I point out the difference between proprietary and open source and the difference between how the organisations behind it can control the products.

For me these differences are a problem, as well as a challenge, for open source. It is also something I am going to try and address in future posts.

/thomas

Re: Examiner.com - Official Response and Analysis Regarding ...

Actually, I've been very busy on my personal blog. I've spent a couple of days detailing it, and making sure it looks the same in Chrome, Internet Explorer, and Firefox. I've never before spent much time with the format and display.

I've also loaded 54 of my examiner.com articles into it, all of which may be viewed by clicking "Examiner.com" under categories in the sidebar.

In the process, I ran across an entry on March 16th which had completely slipped my mind. In it I note that Google had resumed indexing the articles in Google News only a couple of weeks previous, and that now they were telling the writers that anything over 400 words would not be indexed in the news.

I can't write my last name in 400 words or less, and I started a thread with a title something like that in the forum.

Needless to say, the next article I wrote was 2,975 words, and I was trying to be brief.

Coincidentally, they removed the reporting of current days views and completely ignored writers request for more metrics, not less.

Coincidentally, they also cut the pay per view, without telling anyone.

When the stuff was hitting the fan over their latest administrative debacle a number of writers were complaining that now they were being paid at a higher % if people stayed on the page longer and they were under the impression they were supposed to be writing under 400 words...

...all I know is that every time I started to get some traction and it was becoming worth the time, they pulled the rug out from under me, with great consistency, about every 3 months.

Being under the impression that anything over 400 words was not going to be indexed in Google News meant I didn't write much of anything for several months.

What's really frustrating is since examiner.com has suspended me for being "too aggressive" (They still have bothered to tell me what terms of service I violated, or how) some of my recent articles have been mentioned and linked in publications with some serious readership numbers - and I can't even check my page views.

Oh, yeah, about 80% of my articles now have empty boxes with "Courtesy so-and-so/AP Photo" in them .... another one of examiner.com's 'upgrades'.

Re: Examiner.com - Official Response and Analysis Regarding ...

Examiner.com staff are fond of tossing out the number 50K+ active examiners. But here's the thing - there are some serious problems with that number and those problems mean it's essentially a number designed to give a false impression. To base the percentage of writers who have submitted support tickets on that number only extends the misconception.

If Examiner.com won't be straight in public statements about the exact number of active examiners, and they want to use the 50,000+ number to make the number who have filed support tickets/complaints look smaller, I'll be happy to do some extrapolating to make the numbers look more real. After all, two can play this cook-the-books game.

First, some markets are small enough to quickly count the names of those who are listed as examiners. I discovered by looking at the sitemap for individual editions that Ex counts every **column** as a separate **examiner,** even when the column is written by the same person. If an examiner has two columns, s/he counts as two of the X number of *examiners* in the edition.

Some examiners who have been writing for the company for awhile have multiple columns - 2, 3, 5, even 10 columns. If Examiner.com counts every column in every edition as a separate *examiner,* that's a quick way to get to 50K examiners, even if some of them are the same person, counted twice. To check this out, compare the number of examiners listed in the (name of edition) Examiners box on the front page of any edition (6 of N) to the list of examiners for that edition which you can find in the Examiner.com Resources | Sitemap | (name of edition) examiners list. See the issue?

I'll use Syracuse as the example. According to the front page widget, there are 86 examiners in the edition. According to the sitemap, there are 86 columns. If I count author names, not columns, Syracuse only actually has 79 people writing those 86 columns for Examiner - a difference of 9% - but Examiner still counts their columns, not the number of people. Since Syracuse is a very new market, it's likely that fewer people have more than one column - so let's round that up to 10% (I can cook books, too...) and take 10% right off the top of that number Examiner.com uses for active examiners - 50K+. Since I can't cook an estimated book, I'll use 50K even, and when I subtract 10%, I get 45,000 examiners.

Now, let's take a look at "inactive" examiners, people who don't meet Examiner.com's own standard to earn payment - they have to write one article in the current month. Hmm. Out of the 79 people in Syracuse who are writing, only 22 have written at least one article in the month of August (which is almost over.) That's only 27.8% of the people who have ever written for Syracuse's edition who fit the definition of an "active" examiner. I'll round that up to 28% (because when cooking books, there's no need to make the calculations complicated.)

Now for the extrapolation.
If only 28% of the 45,000 human beings who have ever written for Examiner.com are active, then that's only **12,600 people.** Of course, my disclaimer is that it is only an estimate based on probabilities and using one young edition as representative. The real number could be higher - or lower. Anyone want to start doing an actual count with me?

Now - back to that sorta firm number, 5% of ~50K, which I called 2500 examiners who have needed support. By my math, 2500 real support tickets from 12,600 active examiners means that 19.8% have filed support tickets - so hey, we're book-cooking, and I vote we call it an even 20% of active, human examiners who have had to report some issue with the migration. ;)

I make no guarantees about my numbers, but I can count examiners, columns, and numbers of people in one edition who've published within the month of August. I hope that my interpretation of these numbers illustrates that there is more than one way to interpret Examiner.com's claims about the impact this migration to Drupal7 has had on their writers' community. They like to trot out the 50K+ examiners number (which is real - that is likely how many people have ever written for the company.) But the point is that only a small percentage of that number are actually active writers. And if the 2500 support tickets ballpark is even close to correct, then it should be called a percentage against the number of **active** writers, not against the number of everyone who has ever contributed to the site. Writers who are long gone or long inactive aren't likely to have even noticed that the site migrated, because they've moved on to other things.

Re: Examiner.com - Official Response and Analysis Regarding ...

All good points. And some interesting data here that Examiner will have to address sometime, but again to my point about the reporting here. It was the blogger who first published high and mighty that "40-50,000 writers are having problems!"

Re: Examiner.com - Official Response and Analysis Regarding ...

Hi Raymond,

Those numbers are the official Examiner.com numbers. In their answers to my questions they even said "We have over 50,000 contributors". As others have pointed out, there is no way I can verify that. I can only go by the numbers they make official.

/thomas

Re: Examiner.com - Official Response and Analysis Regarding ...

Yes, these are the numbers given by examiner.com and are probably 100% accurate. Examiner never said they had 50,000 active users, the word active has been added by others. 50,000 people probably have contributed to examiner since the site began.

Re: Examiner.com - Official Response and Analysis Regarding ...

Some shoddy reporting here. "Words against words"?? You ask for comment from a top 100 site, then still lean on the one obviously disgruntled writer? Nice work on helping Drupal too. The site obviously has a few kinks to work out, but sorry, I have a feeling they know what they are doing. After reading the posts here, not sure I can say the same about this blog.

Re: Examiner.com - Official Response and Analysis Regarding ...

Raymond, you are shooting at one small part of my posts.

With these posts I wanted to put focus on how incidents like this one can harm open source. That is the reason why I compared how proprietary software vendors can control what versions their customers are using, while open source project has no such options.

In my posts I have pointed out that Examiner.com is using a a version of Drupal that is not yet officially released, nor a version that anyone within the community would recommend being used for a production site.

It would have been wrong of me not to notify and invite Examiner.com to comment to explain why they decided to go ahead with an unreleased product.

Due to that Drupal is open source, there is of course nothing that stops anyone from using whatever version they want. I am running this blog on Drupal 7 for example. Even though my blog counts as a productions site, I have been clear about my reasons for using it. That it is an experiment, that it is my way of testing it in live conditions and so on.

I have nothing against Examiner.com using an unreleased version of Drupal, quite the opposite, and they have their full right to do so. But opting to release it "on schedule" was their big mistake. Not only did it have a negative affect on traffic, but more importantly it made the people who make the site possible lose income. These people are the Examiner writers that have an agreement with them to produce content and being paid for it based on page views. Examiner has a responsibility to make sure that their writers content will get best possible exposure.

As I ended the above post with, a lot of this could have been avoided if they had just moved the launch a few weeks forward instead of launching it "on schedule".

/thomas

Re: Examiner.com - Official Response and Analysis Regarding ...

Thomas--so why do you think Examiner.com chose to keep their launch of their new site on schedule, rather than push it back? Did they not know that all of these problems would exist? Or did they just not care?

There has to be a logical reason, because why would Examiner attempt to frustrate their loyal writers and hurt their pay? How does that help them in the long run? I would think it would damage their reputation by word of mouth alone.

So there has to be a reason...

Re: Examiner.com - Official Response and Analysis Regarding ...

Raymond - bloggers aren't "reporters." But please note that the 40K - 50K "examiners" number is the one that Examiner.com publishes. It's on their website, it's on their press releases, it's their go-to number. And as I point out, it's not a lie, exactly. However, it represents every column title that's ever been written for Examiner.com since it launched. It doesn't translate accurately into actual numbers of people/writers, and it has no relationship to the number of people who are actively writing today. Examiner.com won't even reveal the actual number of active writers to the active writers. All anyone, including this blogger, have to go by are those numbers Examiner publicly shares...unless they want to do a lot of math and they know where to look and have the time to open every single column in the edition to see when the person published last. No, there isn't enough time in the world to do that for every edition.

Active writers have known for awhile that not everyone listed as a columnist on their editions fits Examiner's requirement for payment - they haven't written anything within the current month (or longer.) Now, unfortunately, the readers are being exposed to this every day with a widget on each edition's front page that features the icon picture of a rotating list of (name of edition) examiners. Readers who may not have known about the careers or writing examiner are being enticed to click on a face - and then after clicking, discover that the person hasn't written anything for a month (or much, much longer.)

As for supporting Drupal7, I suspect what Examiner's early deployment on a platform that is still in alpha will do to Drupal7's reputation is far worse than the effect of someone taking a look at the results and pointing out the flaws. The "few kinks" you mention in the migration to Drupal7 and execution of the new site are affecting writers' livelihoods. These are people who know how to use words for a living and who have writing platforms and contacts in the freelance world. That's not exactly a group of people that it's in Examiner's best interests to inflame.

Re: Examiner.com - Official Response and Analysis Regarding ...

Thanks Gaelen for adding the point that "few kinks" is a gross understatement and that thousands of writers have been kicked in the butt, losing up to 90% of their average income since the new site launched. The tickets are slowing down because Examiner's inaction and double-speak gives writers a sense of hopelessness, that makes them stop reporting problems. The drop in page views has now trumped the still awful look of the site and the lack of functionality. As for a writer being terminated, well that might be, but there is documentation of a writer being punished for writing about exactly what Thomas is writing about here. Writers can't review Examiner even if their topic would naturally include the subject. It has happened before when the site couldn't pay people on time for months at a time. Writers were forced to submit tickets to support center as if it was a technical problem and the run=around was ridiculous. They blamed all sorts of sources for their problems when the truth was no one felt like paying attention to how it could be done right. Once the legal talk started flying around the problems suddenly disappeared, but anyone who had the temerity to report on it was slapped into submission. It's just their way.

Re: Examiner.com - Official Response and Analysis Regarding ...

It's not "just their way" it's part of the TOS every examiner had to agree to before posting their first article.

"You agree that you will not post to the Site, or use the Site to transmit or make available any Content that:

* violates any laws or regulations, contains any threats, is abusive, tortuous, harassing, vulgar, obscene, indecent, violates any person's rights of privacy or publicity, is defamatory, libelous, hateful, contains any disparaging statements or opinions regarding racial, gender or ethnic background, or is otherwise objectionable; "

and:

"In addition, you are prohibited from interfering with or disrupting the Site, or servers or networks connected thereto. "

Posting some of the things that people have "reported" could certainly be considered defamatory and libelous as well as being reported in order to "disrupt the site". those people should be removed as examiners. They complain about their traffic but they are hurting their own traffic more than the troubles with the upgrade have. And as a side note, my income has DOUBLED since the upgrade...why? Because I keep writing new articles and promoting them instead of sitting in the examiner community whining like a 2 year old.

Re: Examiner.com - Official Response and Analysis Regarding ...

Thomas, I've been reading your articles since the upgrade at Examiner.com. Some of it is dead on.

One point I will differ with you on is the claim that people are being silenced for complaining or criticizing Examiner. If that were the case, I'd have been suspended long ago. I've been very critical. I'm using my real name in this response, so feel free to check with any writer you may know at Examiner to verify that I am quite vocal when I disagree or am dissatisfied with their actions. I have not been asked or told to stop, nor has it been implie or hinted at by anyone from the corporate staff. To the contrary, I've been told to call it like I see it.

Re: Examiner.com - Official Response and Analysis Regarding ...

You are no longer welcome in the Drupal community. Seriously. Get out. Congrats on making a name for yourself by distorting the facts. You should know that all launches are hard and that as soon as the end of this month this launch will be good for Drupal and the Examiner.

Re: Examiner.com - Official Response and Analysis Regarding ...

Hi Dpl,

You are of course entitled to your opinion. However, I have a very hard time to understand what it is you are trying to accomplish with your comment.

Could you please try and be a bit more specific about what I, in your opinion, have done wrong regarding this.

/thomas

Re: Examiner.com - Official Response and Analysis Regarding ...

Wouldn't you think that anyone who spoke for the community or even had the slightest bit of authority to banish anyone would have a verified identity? I'm just saying........

Re: Examiner.com - Official Response and Analysis Regarding ...

I wish some of the Examiners who are making good money -- and the ones who get even more pageviews than I receive in those top 5 reported positions -- would post up their income numbers to prove that folks are still making good salaries with Examiner, even after the switch to Drupal.

They are silently still raking in the money while all this debate goes back and forth.

Re: Examiner.com - Official Response and Analysis Regarding ...

Good luck finding them. I used to be # 2 in my channel. Now I'm making a little over a dollar a day. Anyone who is making a lot of money now is either lying, doing something shady, or making it on the backs of those of us who are suffering the broken URLs pointing to the wrong pages.

Examiner has fallen

Pageviews drop at Examiner -- http://bit.ly/FallenDown

I believe I got pushed out for my comments in the community forums. Examiner seldom uses the words "Omniture" or "Next Jump Inc" but that is exactly who they sleep with at night.

The Examiner business model has enormous similarities to a paper writen by Prof. Axel Bruns :

http://produsage.org/files/2010/Exploring%20the%20Pro-Am%20Interface%20between%20Production%20and%20Produsage.pdf
-

Re: Examiner.com - Official Response and Analysis Regarding ...

Examiner has 16,500 "active writers" across the USA and Canada

http://bit.ly/NewsWreck

UPDATE (10/12/10): Examiner.com CEO Rick Blair responded in an email

We actually have had more than 62,000 total Examiners contribute on our site since we launched in 2008; we still actively communicate with more than 55,000, which is what that number is based on. Currently we have an average of about 60 percent that have actively contributed in the past 90 days. We use that timeframe in monitoring engagement to take into account our daily publishing frequency is always fluctuating -- as some titles like sports are seasonal, others like music are dependant upon new information or movement, for example.

"""Our 30-day average reflects this oscillation, as we range between 30 to 40 percent active in that timeframe. """"

30% of 55,000 = 16, 500 and that comes from the CEO of Examiner

Re: Examiner.com - Official Response and Analysis Regarding ...

You got fired from Examiner! LOL. No wonder you are so malcontent!

Re: Examiner.com - Official Response and Analysis Regarding ...

I love that this guy has not posted anything else. He has nothing else to talk about! No one knows who he is in the drupal community, and he tries by posting using discontent sources and random rumors. Nice try!

Re: Examiner.com - Official Response and Analysis Regarding ...

It's all good now ;)
Alex @ http://thejojobaoil.com/

Re: Examiner.com - Official Response and Analysis Regarding ...

All good now? Only because those of us with hundreds and hundreds of broken backlinks in the pre 2.0 articles have just given up on them. Page views are about 1/4 of what they were before the Drupal switch, but current Examiners don't know that, so they're content with their pay. Most of the longtime writers are gone. The few hanging on are pretty jaded about the whole thing.