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://hubpages.com/privacy-policy#gdpr"

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)
jump to last post 1-5 of 5 discussions (7 posts)

At what point is it better to split a long hub ( approx 3000 words ) into multip

  1. PeterV profile image80
    PeterVposted 3 years ago

    At what point is it better to split a long hub ( approx 3000 words ) into multiple hubs?

    Apologies from this noob if this is covered somewhere and I can't find it.  Question: If I am at 3000 words and plenty of photos, is it best to divide it up and make two articles ( aka part I and part II) in a group, or to leave it as one lengthy article? Pros and Cons?

    https://usercontent1.hubstatic.com/12179980_f260.jpg

  2. Tusitala Tom profile image68
    Tusitala Tomposted 3 years ago

    I'd say split it into two.  Find an appropriate place around half-way.   If you look at the site when you make up a Hub you'll see that Hub Pages advocate around 1200 to 1500 words to get maximum points for a Hub (not considering pictures and videos)

    I could be wrong, but I'd say very few people will read one long Hub of 3,000 words or so all the way through.   And even with the shorter Hubs the Headers on each part of it need to be attractive enough to keep them reading.   We live in an era where 'attention spans' have declined to an almost frighteningly short amount of time.  I blame a lot of it on the 'Information Overload' we're all subjected to nowadays - especially from the world of Marketing and Advertising.

    Split it into two, mate.  More people will read it; both parts, instead of just the first half of it before tuning out.

  3. peachpurple profile image83
    peachpurpleposted 3 years ago

    wow, 3000 words are way too long, you better split into 3 hubs, I would get bored reading the 1st paragraph

  4. Maina Ndungu profile image97
    Maina Ndunguposted 3 years ago

    In my own opinion, writing hubs with the same title and branding them as "PART 1" etc is not the best way to go. I'd advice you to use Google adwords to create different titles and then group them together.

    1. MarieLB profile image81
      MarieLBposted 3 years agoin reply to this

      I second that suggestion.

  5. somethgblue profile image87
    somethgblueposted 3 years ago

    The sad pathetic truth is, that in the digital age in which generations of humans have been conditioned into watching videos, TV Shows and movies where another persons imagination is used to share ideas, limiting the viewers own ability to imagine and create their own images, people get bored reading.

    These are the kinds of people that prefer others to do their thinking for them, tell them what the point is, provide one-sided evidence and lead them to a conclusion without showing the other side or version of events.

    So when you write in depth lengthy articles you lose these slow, narrow minded dolts as they're incapable of focusing their attention on anything that requires they use their own brains.

    Peachpurple, proves my point in the comment below admitting to seeing a 3000 word article frightens these readers and they get bored after reading the first paragraph.

    I would say any article longer than 3,000 words should be broken into two articles but with only a related title, do not use part II, make the second article stand on its own.

    1. PeterV profile image80
      PeterVposted 3 years agoin reply to this

      I am afraid I too have become one of those readers that would rarely take the time to sit and read 3000 words in one sitting.  I agree it needs to be split up.  Thanks.

 
working