Many of us here are working hard to upgrade our hubs so that they can be moved to the niche sites. I think it would be a good idea if those upgrades are viewed by the team the same way as new posts so that they can more quickly addressed. It's a shame to let much better upgraded articles sit idle while new ones are moved. What think you?
That mechanism already exists - if you think you've improved your Hub to the required standard, you can submit it. But only one every 60 days, of course.
I'm sure they've put that limitation on for a reason - because they've worked out that if they don't, they'll be swamped!
I know they are looking at new Hubs, but new Hubs need to go through QAP anyway so it's not much extra work to assess them for the niche sites.
Christy mentioned on another thread that they're still choosing Hubs using traffic as the main criteria. So if you improve Hubs enough to get more traffic, that will move them up the queue.
Yes that makes a lot of sense to me. We and anyone else (people not on the forums) would only be updating to make it better. And that being said, they are going to be better than most of the new hubs being published. So why not look at these just the way you would a new hub.
Time is an issue for the low man power right now, that's a point for sure, but it would make sense to look at updated hubs before trying to get to the remaining hubs that are not being updated. I'm going to guess that any hub with even a decent daily traffic has already been moved or considered as that's what's happened to my account.
The question is, how would the process work? It would have to work the same as the current "submit every 60 days" system - if you expected editors to consider a Hub every time someone did an edit, then they would be getting Hubs in their queue every time someone fixed a typo.
So really what you're saying is, allow us to submit any time, not just every 60 days.
The problem with that is your assumption that people understand the standards, and wouldn't waste the editors time bombarding them with Hubs that weren't improved enough. I, for one, am still getting a handle on what's acceptable (having just had one rejected). What if I'd been able to submit five Hubs instead of just that one? I would've wasted the editors' time.
What I would suggest is a pretty simple system really. But before that:
Hubs that are edited automatically go to the QAP again if I'm not mistaken? If that's possible they can probably also be put into a queue for niche site consideration.
And as a few of us suggested earlier (but the team couldn't do it for various reasons) was that you can only submit a hub once one of your previously submitted hubs is approved. If you get a reject, then you wait like 10 days before you can submit again. It would prevent people from misusing the system.
This is just talk though, we all know that it's not going to happen as the team have a system in place and it would take time and resources to do it any other way. So all we can do is trust their process, they got the stats with them and I'm sure they are doing what's right for the site. They have been doing a great job all these years.
Actually, I always believed Hubs that were edited automatically go through QAP again - but apparently that's not the case. We had a discussion about it a few months ago and we decided it wasn't true. A Hub that's edited does get checked by the automated filters but it doesn't look as though it's seen by a real person.
I see. Interesting I missed out on that conversation I guess. Thanks for the update.
I was surprised too! It took a lot of persuasion from Glenn Stok and others to persuade me it was the case, but I'm convinced now.
I didn't realize that and thought the same as lobobrandon that if they were going through QAP again, why not just add them to the batch of new hubs. If we're going to do extra work on our articles to update them, we should at least be placed in the line with the new hubs. His suggestion would be the easiest one to implement but, of course, would lengthen the amount of time it takes for hubs to be moved. I don't think random submissions are a good idea, but doing it through the QAP is. In fact, I've often thought that a hub that has been upgraded should appear once more on the feed, too.
Oh goodness no! Can you imagine, seeing the same Hub in your feed again every time someone changed a date or added a photo?
There would have to be some mechanism to say, don't show a Hub in the feed UNLESS a lot of work has been done to it. But that would mean a programmer needs to paid to develop that mechanism - and I can't think what measures could be used. Would it be based on the number of words that were changed? or added? or the number of new photos?
I see your point, but I wasn't referring to minor updates. In many cases I wind up reworking an entire hub with a different title, better pix, etc. However, it is obvious that this idea isn't a good one. I haven't asked the team to move any of my hubs yet because they continue to take one or two every week or so from both of my sites and my views are still (amazingly) good! So, I'll just shut up now and go back to writing lol!
By asked do you mean you are not submitting any every 60 days? You should give them a good but also your lowest trafficked hub.
Regarding that update feature if I remember right it's possible to set a status right. If people are really interested why not set a status saying you updated XXX
No, I have not submitted any because they seem to be picking them up regularly from both of my sites. Also, I need time to see how hubs are doing so that if they do need upgrades I can do them before they get moved. Things are better than they have ever been for me, and I know the team is swamped, so I'm content to just take a "wait and see" attitude for now.
I assumed you weren't referring to minor updates.
My question was, how would it work? How would the system know the difference between a minor update and a major one?
They could probably design a system which measured how many words had changed in a Hub, or how much the score had increased. But how will the system know the difference between a Hub where you've made most of the changes, but had to save it because you had to go pick up the cat from the vet, and a Hub which is totally "renovated"? Surely it would be a dreadful waste of moderators' time to have a system where they might be looking at Hubs you haven't finished working on.
The only way it would work, as far as I can see, is that the Hubber would have to give some kind of signal that the Hub was ready for reconsideration. Which means, basically, a system where you have to manually submit the Hub. So we're back where we started!
Got it! It was just a thought that seemed good, but obviously it won't work.
I agree. There also seems to be a major delay in looking at submitted Hubs. I submitted one for this account back on Oct 12 and haven't heard anything yet.
Nothing for it but patience, I suppose. I get the sense that now that the niche sites are doing well the Team is moving more cautiously and fine-tuning the process.
They get some money, they party, lol. Who wouldn't?
I would certainly hope so. The worst that could happen is that HubPages starts accepting Hubs from the old site too easily, and transplants the old site's problems to the new one.
Yup, I updated one of mine and submitted it on the 21st no news yet. Happy to know there are others too.
Having just submitted my first hub for a niche site I was wondering how long it took and whether I would ever hear anything back one way or another. Just getting feedback on why it is rejected would be a key point so as I develop new hubs I can strive for the niche standard. Right now I'm not sure what the standard is. I just recently began to write hubs after probably 5 years away and I received Pro Hub status so I was wondering if that meant inclusion into a niche site but I guess not.
Feedback is the key, once I know why my hub doesnt make the grade then it's up to me to improve my writing/presentation.
It has been several months having not visited my HubPages account and I'm quite surprised on the new changes here particularly on the niche sites. This reminds me of Triond to submit articles to its appropriate niche according to the topic. Sadly, Triond's now gone. Am not active here anymore because I'm enjoying and earning much more on my own niche website which started a year ago.
You should add your site to your profile so we can have a look!
by promisem 8 years ago
I'm very happy with the results of the niche sites. It's a win-win for HubPages and writers like myself. But I'm a bit curious about the process for choosing Hubs that go on those sites.One of my most successful Hubs on a niche site has more than 1,250 words, multiple photos and an original video....
by Michael Kismet 2 years ago
I already have a number of hubs moved to the Hubpages network sites, but haven't really seen a drastic traffic change in said hubs. So, is it worth the risk to submit one of my hubs that already receives a decent amount of daily views to a vertical site?I'd hate to see aforementioned hub drop in...
by Caren White 6 years ago
I was under the impression that we could only submit one hub every two weeks for niche sites. I submitted a hub and an editor replied with changes that I needed to make before it could be moved. As I'm making those changes, I have received two emails that another two of my hubs are...
by Sarah Spradlin 6 years ago
I pretty much have the same amount of traffic everyday but last week 5 of my hubs were moved to niche sites and since then I've has less half the traffic as normal. What could cause that?
by Mark dos Anjos, DVM 7 years ago
Over 1/4 of my hubs have not been moved to a niche site. They do not have much traffic from Google, so it is not HPs fault that they have not been selected. There is nothing wrong with them, but they do not have "Google love" so are only moved in the slow process where I ask HP to move...
by Eric Dockett 8 years ago
I've been feverishly updating my old Hubs, not so much on this account but on my big niche account, in hopes that they will be noticed and moved to a niche site. But, it appears this process has come to a dead stop. It is extremely disheartening to think older, quality Hubs can only be up for...
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) |