Subdomains, Freshness and Publishing Frequency

Jump to Last Post 1-2 of 2 discussions (6 posts)
  1. EricDockett profile image96
    EricDockettposted 8 years ago

    For a long while I have noticed a correlation between publishing frequency and improved traffic. This seems to reflect search engines' alleged affinity for fresh and updated blogs and websites. Our subdomains are crawled and indexed, not just the individual Hubs but our main page as well. So, it stands to reason that frequent updates (publishing new Hubs) would serve to keep your subdomain (site/blog) "fresh" in the eyes of search engines.

    However, this only makes sense if search engines view subs as somewhat independent from the main domain. If all of HP is lumped together as one big site it shouldn't matter a whit if an individual author suddenly posts 10 Hubs on a dormant account. Again, in my experience anyway, it does seem to matter. And, no, I'm not simply talking about the extra traffic from the new Hubs. Older Hubs seem to benefit too.

    I'm sure I'll get a few theories from Hubbers, which I will certainly appreciate. However, what I am really hoping is that HP staff (Paul?) might jump in with some data or theories on how subdomains are treated these days, specifically in regard to publishing frequency and freshness.

    1. Paul Edmondson profile imageSTAFF
      Paul Edmondsonposted 8 years agoin reply to this

      @ericdocket

      My thoughts are freshness matters.  I"m going to try and break it down a bit based on what I see.

      Sites that add content and update do better than those that stop adding content (including subdomains on HP).  If they stop updating, they tend to wither over time.  To me, this means that adding content or updating existing pages is essential for long term health.  We've also run experiments where we update old pages and on average they see significant gains.  We've never done a study where we update old pages and leave the quality unchanged to see if it's really freshness that drives the traffic change.  Regardless, any Hubber can improve their traffic on a page by page basis by making steady improvements to their pages.  A good place to start is making sure the title and subtitle use proper casing.  Grammar and spell check.  Remove unnecessary content (extra products, low quality links).  Add relevant content to enhance the Hub such as nice imagery that breaks the Hub into logical sections.

      The more difficult question you asked is HubPages treated as a bunch of sites or as a single site.  For certain things page level updates can have an impact outside of the entire site.  However, I feel like there are a number of algorithms that do impact the entire site. 

      In the recent end of April Phantom update, the entire site lost traffic.  Google later said it was a quality update that was supposed to impact sites page by page.  Our data didn't show this.  My feeling is if subdomains were treated completely as separate sites we would have seen our highest quality subdomains outperform our lowest quality.  That wasn't the case. 

      To me, we need Hubbers help to continually improve pages that they create and we need to do a better job at site wide quality control.   

      I can say this.  Each month we are getting a bit better together.  Quality is steadily improving.  I'd like to see the entire site get a nice bump up in the future:)

      1. Fiction Teller profile image61
        Fiction Tellerposted 8 years agoin reply to this

        I am doing this, ever more aggressively.

        I do still think there are types of pages that are consistently seen as "quality" in Google's eyes but that do not follow your current quality standards. It's tricky to move 'em to my own sites after all this time. Worse, it's tricky to edit them to improve them, because your new quality standards would eliminate my most converting links. (They're for highly relevant products I haven't personally used.)

        I wish there were a way of "babying" the more successful hubs through the editing process to avoid the deep financial risk for individual hubbers.

        Thanks for the detailed answer.

        1. TIMETRAVELER2 profile image84
          TIMETRAVELER2posted 8 years agoin reply to this

          For some time now I have made it a point to check my stats page for problems.  When I see an article faltering, I jump in and do upgrades.  Often I find that the quality was much worse than I realized, so by doing this, I am able to tighten things up.  It doesn't always work out, but sometimes it does, and I am able to save an article that otherwise would have failed.

      2. EricDockett profile image96
        EricDockettposted 8 years agoin reply to this

        Thanks Paul! That was very informative. "Wither over time" is exactly what I see with a subdomain I neglect for several months. Updating old content seems to help, but in my experience they have to be significant updates to really matter. Publishing several new, fresh Hubs usually seems to be what it takes to get the gears turning again.

  2. Fiction Teller profile image61
    Fiction Tellerposted 8 years ago

    Great topic. I'm also interested in feedback from Paul or other HP official voice.

    On my subdomains, I've never seen any correlation between freshness and traffic.

 
working

This website uses cookies

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 Details
Necessary
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 googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
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)
Marketing
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.
Statistics
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)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)