Is there a way to exclude hubbers who do not have idled hubs from the 24 hour review for new articles? This may be the wrong place to enter this request, and maybe it is an impossibility. It would be nice if staff could facilitate the process of newly written material.
What you are suggesting is that those who have idled hubs are substandard writers, whereas hubs are also idled through lack of traffic.
The other point is that there is nothing to stop a hubber of previously good standing from bringing out a substandard hub.
I have issues with new hubs being idled until checked as I do believe there is a window for opportunist theft left open, but the day a division is brought in to allow some hubbers to have their work indexed straight away, and others not, is the day I leave.
Perhaps Hubbers with a score of 80 or above do not get idled on first publication?
Great suggestion as we place our trust in Hubpages, perhaps the trust could be reciprocated?
Izzy why are you afraid of theft during the 24-hour period?
How would someone steal it if it isn't published? I must be missing something.
But it is published. It is still available on Hubpages, just not in Google.
Ohhh. So some nefarious HP surfer could take it and publish elsewhere. I hadn't considered that possibility. I would think that these hubs would be hard to find. Unless you were following a specific hubber and it showed up under their profile.
I think that hubbers, who have not had hubs unpublished for over-promotional, spun, copied or low-quality content in the last x months (x to be defined by HP) should not be subjected to the 24-hour moratorium on new hubs.
I do not see what is supposed to happen over those 24 hours of non-activity for a new hub. I do not believe that all these new hubs are being subjected to manual review, given the small number of staff. Certainly the content coming up in the hopper does not show any real quality control is being applied.
A better option in my view would be to delay publication of new hubs by people who have had hubs unpublished in the last x months and by all brand new hubbers and subject them all to manual review over a defined period. After that period has elapsed, they could have the privilege of immediate publishing, which of course could be revoked again if they get something unpublished.
This would immediately remove a lot of the one-off garbage that spammers put out constantly here. As it stands at the moment, all of us are being treated as guilty until proved innocent!
LOL, does this mean you agree, maybe just a little bit?
Go for it. A great agreement!!! We can all support each other.
LOL, yes, I am in agreement, as you can tell. I think it's a great idea. Once a hubber has been through a trial period and proven they have a good command of English grammar and are not spamming, allow their hubs to be published immediately. It feels like those of us who follow the basic HP standards are being punished for others' subpar practices. I know there are other sites that give new members a trial period. Why not HP?
@izzy. Try to think of a better way to speed up the process of pending hubs? What is best action on other writing sites?? We want to move forward faster and not sit in a black hole.
Yes I agree. I have loads of hubs in various states of composition, but am not working on any of them until I see whether or not this new HP change is going to work.
I really don't like this 24 hour delay in indexing, which we have already seen from some other hubbers can turn into several days.
I like WriteAngled's idea of applying this new change to substandard hubbers or new hubbers (until they have proved their worth), but I fear the way HP is going, the differentiate will be between elite or alum hubbers, and ordinary members.
The day that happens, I will walk.
Uh oh. I've been really busy in real life lately and hadn't followed this sleeping thing very well. I didn't realize that HP is intentionally delaying indexing for any period of time, let alone 24 hours.
What are they doing in that time? Certainly not reading every hub produced - they don't have nearly the people necessary for that. Why delay a hub? Is it going to make a difference in whether or not it's indexed or even published?
I knew it was "pending", but thought that was just a period between "sleep" and and "featured" - not that it would not be indexed!
I don't see why HP doesn't put brand new hubbers on a trial period, as well as hubbers who have had recently unpublished hubs. I had to go through a trial period for Knoji; you had to write 10 consecutively approved articles before you gained the privilege of being able to self-publish and there is always the risk of losing that privilege if you start publishing substandard material. It is a good way to set a standard.
I really don't like the idea of idle hubs, I understand the concept, I just don't think its a good idea. But that's just me.
That is the way InfoBarrel does it too. After 10 good hubs, they automatically publish. I think Hubpages needs to change this policy.
It makes sense, especially if your a large website like HP, Knoji, Infobarrel, etc. There needs to be a certain standard set by the site, otherwise it gets spammed with crap. There are so many great writers on HP, and HP is the easiest site to make money on, but they need to provide some guidance and standards. Writers do need something to strive for, and the threat of losing publishing privileges and having to re-earn them is enough to keep us on our toes.
I agree with you. It would save all the anguish. There must be a reason for not doing it, possibly not enough staff to handle a new system. I do believe that the pendings are improving in time frame, so that is a step in the right direction. Also, my traffic is up a little today, which is unusual for a weekend.
They could allow proven hubbers to publish immediately AND keep the dle hubs feature to alert us to hubs that are not getting much traffic. That would be a nice compromise, right HP?
When do HP ever compromise?
They simply impose changes dictatorially, knowing that new people will always flood in to replace those who walk away.
I don't really care for it either, even though I didn't get any Zzs on my hubs.
Thanks for the suggestion, brakel2 and all of the discussion it has invoked.
Before I respond, let me clarify a misconception: the date that your published work enters the Google index has nothing to do with your copyright. Google is not the system of record for copyright control. When you create an original work on HubPages, your copyright is from the date published on HubPages (even if you later un-publish it, you can still enforce your copyright).
In those first 24 hours after you publish a Hub, it is live on the Internet: it has a URL, it is linked to from your profile page, it has a "first published" date in our system that you can see in your My Account Stats page. It's not available to Google to index, but that does not mean it doesn't exist.
The Learning Center entry on Idle Hubs reflects this (and specifically calls out enforcing DMCA complaints and Idle Hubs): http://hubpages.com/learningcenter/Feat … -Idle-Hubs
With that out of the way, let me address the suggestion...
The reason that all new published work is held in a pending state is that we need 24 hours to run our automated processes on it: check for duplicates, spam, spun content, violations, allow our moderators to run through flagged stuff, and so on.
We need to do this because if ANY of this stuff gets into the Google index, it hurts us all. Under our previous policy of letting everything get indexed and then taking down the bad stuff, it means that Google's index had the opportunity to see the bad staff.
Those bad apples spoil it for all of us. Hence, everyone--evenly applied with no favoritism--is subject to the 24 hour index delay--even me, a high level staff member with 45 published Hubs and none of them idle.
In the long run, this will make us all look a LOT better in the eyes of Google.
Additionally, I will add that even the best of writers can't keep 100% out of idle 100% of the time. Every writer has work in their portfolio that is less than the best. Idle is way for HubPages to tell you which work may be dragging down the rest of your sub-domain.
Well, that shut us all up Micki.
Maybe it's just the terminology of "Idle" hubs that 's putting people off. If HP had called the change "Held for moderation/revision" there wouldn't have been so much fuss about the new feature. I for one support any attempt at weeding out the crap on this site, even my own.
If you look at the legend at the bottom of my account the idle status of hubs that are getting their 24 hour review is referred to as "pending", and if you click on "pending" it says:
The status of Hubs that are new and updated will be established after a 24-hour processing period. Please note that editing any Hubs with a pending status resets the 24-hour processing period.
Perhaps there are ways we can make that more clear, though. A lot of people probably don't scroll down and look at the legend.
I accidentally hit the edit button on a hub that I just published (I was aiming for the one below it) and it completely reset the 24 hour thing. Now that SUCKS! Maybe they need to add a "Are you sure you want to edit this right now?" or "Sorry this hub cannot be edited for 24 hours" message for those of us (like myself) who happen to click too fast!
When that happens if you don't change anything in the Hub, it should not reset the pending clock (just click done editing or use your back button). But if you edit a capsule or change the title or something it will.
But, yes, perhaps we will add a little warning.
Exactly Paul, a lot of people don't scroll down and look at the legend.
Perhaps the statement:
"The status of Hubs that are new and updated will be established after a 24-hour processing period." should also appear in the first paragraph of the "Start a new Hub" page. Then there will be no arguments and disappointments (at least from new Hubbers).
Bottom of "My accounts" page. When you click on the legend for "Idle" you get:
"Very few people are visiting this Hub right now. While it is fine to leave this Hub as is, consider updating it with fresh, high quality text and media."
Here you could add "Title Tuning, Summary and Keyword revision."
[b.t.w. the summary capsule should allow no more than 140 characters.]
I still feel that "Zz & Idle" is negative. "Re-awaken", "Kick up the butt", "Shake Back to Life" or any other more fun, more positive terminology would perhaps not have caused such a major uproar.
Anyway, it's done now. We'll get used to "Zz & Idle", don't worry.
So therefore please explain, MIckiS, why I have, in the last 5 minutes, been able to flag a hub, published 2 hours ago, which is an exact copy of another article on the Net, plus a second complete duplicate, which was published 12 hours ago.
Your algorithm seems incapable of picking up 100% duplicates, so I have my doubts that it has any capacity to identify spun stuff.
Yet this is your excuse for why we are all being treated like spammers and cheats!
I strongly agree that newly published hubs should not be fettered with a NOINDEX attribute.
Example: I just wrote a hub on a topic which will be a major news item tomorrow morning. As soon as I hit publish, I Tweeted it and linked to it from a forum post. Since I have established author clout, Googlebot will probably be by within half an hour to crawl the hub.
If it does come, Googlebot will see the NoIndex tag. It will NOT index the page. Then, Googlebot may not return for weeks; why should it recrawl a page it's been told not to index?
Which means that when we first publish on Hubpages, we dare not promote or advertise a new hub in any way, lest Googlebot come by and discover the NOINDEX tag. We can't even risk sharing on social media, because sometimes, Google follows Tweets or other publicly-viewable shares to discover new pages.
If I had published this content on Squidoo, it would be be getting search traffic RIGHT NOW, perhaps several hundred by morning. (But of course, Squidoo doesn't prorate advertising revenue and doesn't pay for a partial month; this was why Hubpages has become my favorite platform for posting on fresh/current/trending content.)
As it is, that hub won't be getting any traffic besides social traffic.
Before, Hubpages was a great site to publish on topical, trending topics, drawing a big intial traffic and earnings spike which would then die down to a low, steady trickle, thanks to the natural links dropped by some of the initial surge of visitors.
Example: For the Mars Landing, I pulled in many thousand visitors during the 48 hours around the landing. Nearly all of those visitors were Google search traffic, since I was posting images as it was happening. The backlinks I got from those initial visitors mean that hub now enjoys a modest but steady trickle of traffic. If "Idle Hubs" had been enacted then, Hubpages would've lost out on thousands of visitors and quite a bit of ad revenue, and that page might still be struggling to break through on search traffic.
I created this new hub today in order to put the "trending topic" problem to the test, since I wasn't 100% sure whether a pending hub got a noindex tag. I see it does.
For the reasons I explained above, I think this is a problem that needs to be fixed. Reserve "Idle Status" for hubs that have had their chances, and really have gone idle. Don't lump "pending" into the NOINDEX bucket — it cuts off Hubpage's opportunities to rank for fresh or trending search queries.
I strongly agree, also. This is big problem for writers and IMHO HP needs to work with us on this. Keep your hard line of ignoring our opinions on other matters but please take some action to resolve this particularly problematic issue.
Followup: I gave up and created a semi-asinine Squidoo on the same event -- written from scratch so the textual content was original -- as a test. The hub had better on-page optimization, richer and more thoughtful content, and should've ranked higher on Google's quality ratings score.
I promoted the Squidoo lens with one Tweet. I posted a link to it from a small no-name forum where Squidoo/Hubpages members hang out. That's exactly the same steps I followed yesterday to promote the hub.
Checking Google's cache with cache:url shows the just-published lens is now indexed by Google 33 minutes after publish, whereas yesterday's hub on the same topic is still getting the "not in Google cache" 404 message 16 hours after publish. [Update: first image search traffic from Google has now arrived on the lens, 51 minutes after publish.]
Again, I'd much prefer to be doing this kind of thing on HP, because Squidoo doesn't start paying for ad revenue (i.e. impressions) until the first of the next month, whereas Hubpages starts paying us as soon as we start earning ad impressions/clicks.
Leverage that advantage, HubTeam; it's one thing that makes Hubpages more appealing for pragmatists who consider ROI when deciding which platform to use for publishing.
And another followup:
32 hours after the new hub was published:
PENDING status remains. Google has seen the NOINDEX tag on the hub, and may not come back for weeks, since it now knows that's a page Hubpages doesn't want it to see.
16 hours after the new lens was published:
48 search engine visits have come by, mostly image search. It's been scooped and gotten a few backlinks. Visitors have clicked on an Amazon module I added as an afterthought (also on the hub) in case anyone looking for photos and info about the topic might also want to buy a video related to the topic.
Modest numbers, but it shows the potential for ad impressions and sales during an unfolding event.
Conclusion: Before Pending Status was added to Hubpages, Hubpages was absolutely the best place I'd found to publish on newsbreaking, trending, and unfolding events. My best mark so far was over 9 thousand visits in the first day and a half of an event, and I was starting to refine my technique now that I'd figured out HP's great potential here.
Now, it is no longer possible to reap the benefits of posting a timely article on Hubpages.
Remember, once Google crawls a page and determines that it shouldn't be indexed, Google may not be back for weeks and weeks to re-check. Ditto other search engines, which are generally slower at recrawling than big G.
Google strongly favors fresh content. I think you're hurting HP by making it mandatory that Google NEVER SEE fresh content on Hubpages, only stale content. What will Panda make of that?
This is another reason why good writers at HubPages need to publish immediately. I do not know what procedure would work. However, if good writers leave, HubPages would suffer. Maybe staff could reconsider and come up with a procedure that would work. I read about the assumption that all good writers have bad articles once in a while. How bad could they be? I am happy about the views, and appreciate what staff has done to improve the site.
I was just listening to a BBC radio profile about Pete Cashmore, founder of Mashable.com.
It said there that what flung his website to superstardom was breaking the news of the Hudson River plane crash of 2009.
As an avid social network user, Pete saw the Tweets from witnesses and immediately published an article on it, long before the news sites.
Obviously he must have already been in Google's good books, as it was indexed straight away.
With this 24 hour delay, it seems that hubbers would be far better off starting their own sites, even if it is only a free blog, and building up a good standing with Google by publishing regularly.
Then when some big story does break, they are in the ideal position to get first place in Google by being the first to write about it.
Hubpages WAS a great place to write about 'breaking news' or the anniversary of something or other.
With the new 24 hour delay, it now isn't, which can be nothing but harmful.
That's a very valid point. No breaking news stories on HubPages unless maybe some hubbers can see into the future. The only future we see at the moment is slashed views and income.
by Carolee Samuda 11 years ago
I was hub hopping and had to flag a few hubs for being substandard (word count). One hub had exactly 10 words and 2 photos. There should be a way the system prevents you from publishing a hub like that except if it's in the poetry section.
by sonnetwolf1 12 years ago
I'm new here at HUB and every one of my hubs has warnings and I've been told that I will be terminated soon because everything I post is substandard. I have read all the Terms. I don't understand what I'm doing wrong and since I'm "punished" and none of them can be viewed, I...
by Williamjordan 13 years ago
How all of sudden some of the best Hubs on my account are substandar I'll be the first to say I am not the best wirter but I have improved and I have a and average amount of follwer 471 and I have 56,000 pageviews and I have deleted about 13 hubs. I am not deleting anymore tell me to leave in I...
by Dan Harmon 13 years ago
Along with the Google effect lately I've seen a lot of forum posts about spam, and every time I hub hop it is obvious that there is a lot submitted here of both spam and simply substandard hubs.I would suggest that the following rules apply to the first 5 (or 10 or 20?) hubs by any new...
by Kate Swanson 13 years ago
I recall a thread where it was suggested HubPages use the word "non-compliant" instead of "substandard" in their email when a Hub is unpublished.I think that idea was adopted?I'd love to see the word "substandard" banished altogether from HubPages and replaced with the...
by VivBounty 8 years ago
Can someone please help me? I've seen some really sub quality hubs out here. I write well and yet my hubs are being unpublished and continuously picked on for sub quality. I'm offended. You're making it not fun to be a hubber. http://vivbounty.hubpages.com/hub/firew … -plus-help
Copyright © 2024 The Arena Media Brands, LLC and respective content providers on this website. HubPages® is a registered trademark of The Arena Platform, Inc. Other product and company names shown may be trademarks of their respective owners. The Arena Media Brands, LLC and respective content providers to this website may receive compensation for some links to products and services on this website.
Copyright © 2024 Maven Media Brands, LLC and respective owners.
As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.
For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy
Show DetailsNecessary | |
---|---|
HubPages Device ID | This is used to identify particular browsers or devices when the access the service, and is used for security reasons. |
Login | This is necessary to sign in to the HubPages Service. |
Google Recaptcha | This is used to prevent bots and spam. (Privacy Policy) |
Akismet | This is used to detect comment spam. (Privacy Policy) |
HubPages Google Analytics | This is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy) |
HubPages Traffic Pixel | This is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized. |
Amazon Web Services | This is a cloud services platform that we used to host our service. (Privacy Policy) |
Cloudflare | This is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy) |
Google Hosted Libraries | Javascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy) |
Features | |
---|---|
Google Custom Search | This is feature allows you to search the site. (Privacy Policy) |
Google Maps | Some articles have Google Maps embedded in them. (Privacy Policy) |
Google Charts | This is used to display charts and graphs on articles and the author center. (Privacy Policy) |
Google AdSense Host API | This service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy) |
Google YouTube | Some articles have YouTube videos embedded in them. (Privacy Policy) |
Vimeo | Some articles have Vimeo videos embedded in them. (Privacy Policy) |
Paypal | This is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy) |
Facebook Login | You can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy) |
Maven | This supports the Maven widget and search functionality. (Privacy Policy) |
Marketing | |
---|---|
Google AdSense | This is an ad network. (Privacy Policy) |
Google DoubleClick | Google provides ad serving technology and runs an ad network. (Privacy Policy) |
Index Exchange | This is an ad network. (Privacy Policy) |
Sovrn | This is an ad network. (Privacy Policy) |
Facebook Ads | This is an ad network. (Privacy Policy) |
Amazon Unified Ad Marketplace | This is an ad network. (Privacy Policy) |
AppNexus | This is an ad network. (Privacy Policy) |
Openx | This is an ad network. (Privacy Policy) |
Rubicon Project | This is an ad network. (Privacy Policy) |
TripleLift | This is an ad network. (Privacy Policy) |
Say Media | We partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy) |
Remarketing Pixels | We may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites. |
Conversion Tracking Pixels | We may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service. |
Statistics | |
---|---|
Author Google Analytics | This is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy) |
Comscore | ComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy) |
Amazon Tracking Pixel | Some articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy) |
Clicksco | This is a data management platform studying reader behavior (Privacy Policy) |