I was quite excited, and hopeful about this new feature. Now, am very frustrated.
A New Hub was created/published 31-Aug-12 and cleared 1-Sept-12.
That was a week ago.
If the algo is going to make it so Hubs must wait until Next Crawl, then
a. am caught between a rock-hard place, in Limbo. The Hub is not even showing in the HP Breadcrumb sections.
b. Hubbers who realize this are going to just wait until the 8th or 9th of each month to publish in order to be indexed? This cannot be good thing.
Have checked all 3 major engines, link directories, DMOZ, Site Stats, Quantcast and more, and the link is nowhere to be found. Not even showing up, except as an H3 on my profile analysis and from 2 inbound from a Like & Tweet.
Yes, granted it is a product hub, but not overly promoted -in fact no link to the software is listed -not even the Amazon capsule where the software is being stored for download. I wanted to wait for response before having a go.
...am miffed.
James.
Miffed is simply not good enough, James. You have to upgrade that to hostile! ...irate! ...incensed!
lol. duly noted! Upgraded to somewhere between irate and vivid.
I'm having the same problem, but mine have at least been indexed by Bing and Yahoo. I have submitted them manually to those engines, though. And I'm hostile, irate and incensed!
Hollie - how do you submit to Bing and Yahoo manually?
It asks for your homepage but I just submit url of each new published page.
http://www.bing.com/toolbox/submit-site-url.
Submitting here also ensures that you are indexed by Yahoo.
I am ever so flattered to be quoted by one so graceful.
You possess a silver tongue, Niteriter.
The other two have since been sold for top dollar to the PR8 sites.
This new Hub is product//software based.
Same scenario.
James.
I was similarly 'worried' about a hub I published on 29th August, which went out of twirly mode after 24 hours but is still not indexed. However mine was indexed by Bing (at least it got views from bing, so I assume its indexed), without me doing anything.
I've just tried to manually submit it to Google through WebMasters Tools. Will see whether that helps. Although my understanding is that if you make a link to your hub from somewhere that gets crawled a lot, it will be indexed. So shouldn't liking or tweeting it do the trick? Or perhaps Google pulsing it?
Mind you I remember reading something from potpie girl over at Squidoo, that you shouldn't Google plus etc. a page until it is indexed, because that would get the Google+ entry indexed rather than the lens, or hub. I didn't believe that, but I think this happened to a lens I made. I google+'d it too soon,and it wouldn't get indexed for ever until I deleted the entry. When I searched for it, all I could find was the summary in my Google+ profile.
I don't understand this thread at all.
Hubpages is not allowing hubs to be published?
Hubs are published as normal, but they now go through a 24 hour waiting period before they are indexed.
If you look at your stats you will see a grey circle beside the new hub, which is there for a 24 hour period after publication, before it turns into a yellow dot to signify it is ready for indexing.
Some hubs are not indexing for days afterwards. Its as if Google bots visited, saw the no-index tag and left. The hub must then wait for the next bot visit.
Newly published hubs are not even available on the HP feed until the 24 hours are up. Check out the times in explore>hubs>latest.
If you edit a newly published hub at all within the first 24 hours, the time resets to the time of the edit.
I published a new hub 25 hours ago. Unfortunately 11 hours after publication, I added in more tags (without thinking) and so now it has to wait another 13 hours before it is released, and who knows when it will finally be indexed.
And what purpose is this 24 wait serving?
Does this affect older hubs when we update them too?
I guess this is published somewhere since everyone seems to know about it, but I didn't see any notice.
I think you should read the thread "introducing idle hubs" in Official HubPages Announcement.
Well you would probably need a whole day to read the whole thread now, but at least Paul E's announcement. It explains stuff.
I've waited three weeks for a hub to be indexed and, according to Google, the two hubs I now have waiting to be indexed have a robots.txt file. I'm confused.
Don't look at me for a reply to that one, because I haven't a clue with this whole robots.txt thing!
My latest hub hasn't yet been indexed after (I think) 3 days, and so loses out on that lovely boost new hubs used to get. I added it into 'Fetch' after the featured symbol appeared beside it, but no joy.
I am a bit disturbed, however, that in webmaster tools home page, I have a message on one of my other subdomains (not this one) that "Googlebot can't access your site".
It happened in early August, apparently, but I only noticed yesterday.
I sent in a Fetch message for the whole subdomain, but the message is still there. This account suffered a complete withdrawal of Google traffic about a week after the message first appeared.
Nothing has changed, and I don't know how to fix it. In fact, I'm pretty sure I can't as the robots.txt thing is controlled by HP.
All I know about the robots.txt thingy, is that it prohibits G from crawling your site. I've emailed HP and they've said not to worry about it and posted a link to the FAQ but I haven't had chance to read it yet. I couldn't do the fetch thing, either!
Yeah, I am not wasting my time on that million page thread.....
I've read the blog announcement now, thanks for the link.
Having just read the blog entry again, it doesn't answer Isabella's questions either, though perhaps the Learning Centre entry does (linked from the blog).
I have no idea the purpose of the 24 hour waiting period. It's not as if HP has enough staff to vet every hub.
And no, it doesn't affect older hubs when they are updated, but idled hubs can enter a reconsideration phase (the grey circle), and become featured again.
The Learning Center entry is actually what I read, I was just thanking you for the link.
by Dr. John Anderson 11 years ago
The Googlebot visits new hubs within 30-60 minutes while they are in 'Pending' mode and the NOINDEX tag is in place for 24 Hours. This means that the bot does not index the page, and does not return for days or weeks. New pages do not get indexed for days or weeks. This causes lost traffic and lost...
by David Stillwell 11 years ago
Staff@hubpages.com:So I published my second hub in a very long time. The last hub publised was not crawled by google for days on end. I ended up having to manually submit it. Fine! A few days ago, I published a new hub... http://davenmidtown.hubpages.com/hub/En … ving-money This hub...
by Yvonne Spence 11 years ago
I love HubPages, I feel that I have learned so much here and my confidence in writing non-fiction took such a huge leap when I was invited onto the Apprenticeship program last year. I have met some wonderful people here - both staff and other Hubbers. But as may other people have said, the idling...
by Sophia Angelique 11 years ago
Please can someone explain to me why, if one decides not to wait 24 hours to put up one's hub, one then has to wait three or four weeks for Google to index. This has absolutely nothing to do with Google, but has everything to do with punitive action from HP.
by Carolee Samuda 9 years ago
I did a little experiment with opting into the EC program for three months. To begin with,last year one of my better performing hubs become Editor's Choice. That hub was getting an average of 20o+ views per day, peak. The day after being selected as EC, the views dropped to zero. I watched it for a...
by Carolee Samuda 11 years ago
Usually I can find my articles on Google within a few hours, sometimes minutes. Now it seems I can't even find my articles on the site for more than 36 hours after they are published.I believe the new idle feature is affecting how hubs are indexed. Doesn't this affect traffic? What is causing this...
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) |