Simple Ways to Reduce the Impact of NOINDEX tag on Indexing of Hubs

Jump to Last Post 1-2 of 2 discussions (6 posts)
  1. janderson99 profile image57
    janderson99posted 5 years ago

    The forum is full of discussion about how the NOINDEX tag assigned to all hubs during Pending and to hubs that have been Idled can cause delays for indexing by Google. For great Hubs that get Featured immediately after the pending period, or for hubs that get amended after being idled and featured again, this is an unnecessary penalty on authors who write quality hubs.

    There are two ways of reducing the inappropriate penalties associated with the NOINDEX tag.

    1. Incorporate the QAP process and ‘Pending’ step into the publishing process. That is, don’t publish a hub until it has been approved as meeting quality standards. This means that good quality hubs will never appear on the site with a NOINDEX tag (why should they?). Once published they can be immediately available for Google to crawl and index. In the past hubs were indexed within an hour of being published. The only hubs to get the NOINDEX tag would be those that have inferior quality.. If it is too hard to incorporate the needed changes into the publishing - why not simply impose a 24 hour delay for publishing to allow the QAP process to be completed, elsewhere.

    2. Delay adding the NOINDEX Tag to hubs that get idled by 48 Hours. This would allow authors to amend the hubs and not be subject to the risk that Google will de-index the hub before it can be edited. Surely this delay would not affect HP because most hubs would have been ‘featured’ for a month of more before being idled.

    => Quality Hubs should never get the NOINDEX tag  - the way it should be

  2. profile image0
    Casimiroposted 5 years ago

    The first of these suggestions doesn't make much sense to me. Maybe I'm not understanding it correctly. If you use QAP then you're going to have a delay in getting the hub out anyway, perhaps more than the 24 hours it takes now to go from pending to featured. What is the "penalty" of sitting in idle for 24 hours? It's not like Google is going to count that against you, because they don't even see it while it's non-indexed.

    The second suggestion has some merit. It could be implemented by adding another state, which would be a "pending idle" state that gives the hubber 2 or more days to anticipate the idle state and make some changes. I don't see, though, how you get around the 24 hour idle state. The hub has to be checked.

    Perhaps what you are thinking is that some hubbers who have a good quality track record could be given a pass on the idle state. Sort of like special status for frequent travelers with the TSA?

    1. janderson99 profile image57
      janderson99posted 5 years agoin reply to this

      "Google is going to count that against you, because they don't even see it while it's non-indexed."

      The point is that while a hub is pending it has the NOINDEX Tag added to it. If the Googlebot sees that tag it does not index the hub and says "bye, bye see you next time" maybe a few days or a few weeks. This can delay the hub being index when it is featured and the NOINDEX tag is removed (days or weeks delay).
      If the hub was not published until it was through QAPthere is no way the bot would see the NOINDEX tag - this would stop any indexing delays.
      The point about the changes is to never have the NOINDEX tag dsplayed on a quality hub!! Surely that is the way it should be!!!

      1. profile image0
        Casimiroposted 5 years agoin reply to this

        Thanks for the clarification. I didn't realize there would be such a long delay between bot visits.

      2. Blake Flannery profile image95
        Blake Flanneryposted 5 years agoin reply to this

        I really like the idea of delaying publishing until the hub has been reviewed.  Maybe hubbers could choose whether they want a pending hub for 24 hours (Google visits and is told "There's nothing important here) or an unpublished hub for 24 hours (Google only finds your hub and indexes it before people can rip you off). I know I'd choose the unpublished 24 hour review.

        1. Melovy profile image94
          Melovyposted 5 years agoin reply to this

          janderson99, this idea seems good to me. I would prefer that hubbers with a proven track record of quality hubs didn't have pending at all, but if the pending period is to remain for all hubs, I am also in favour of hubs remaining unpublished while in pending. Since search engines can't see a hub that's in pending there is no benefit at all to it being published before the process is done.


This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, 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:

Show Details
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis 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 ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis 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 LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis 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 YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis 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 LoginYou 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)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe 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 PixelsWe 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.
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore 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 PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)