Wow, splitting this up 8 pages was really unnecessary. If you view this I think it's best to click the print view, as the article really isn't that long.
That's one way to increase page-views. In fact, I would consider building this into the CMS. If pages per visit is below the goal, adjust the page break factor to create more pages. If the server is under load, make it generate less pages. If the user has a history of not clicking "next page", make his web experience show less pages per article.
There is a lot of fun stuff that can be done with these idea.
Yea, like getting rid of refreshes and swapping content, counting that as a pageview. Or measuring if user is gradually scrolling, as you'd have to for reading. Or swapping display ads and counting that as impressions, which is what they really want.
I tend to click print-view (if I can find one) each time I see multiple-page article. I'm not sure why anyone designing those websites thinks that paging articles is a good idea, but even if it is, it's probably not intended to benefit the readers.
"Ruby, for example, was intended to marry Smalltalk semantics with Perl syntax. Why anyone thought this was a good idea is unclear."