A simple tip which earnt me an extra $300 per day.

Span scrolling pages across several pages

[Chris999]

A simple tip which earns me an extra $300 per day...

Convert all of your pages so that they do not scroll down more than half a page.

Span large pages across several pages. This prevents users scrolling past your Ads too quickly.

[ken_b]

I'm surpized to see the duplicate content issue raised here. I've broken up a number of long pages and have not had any problem with the duplicate content issue.

My concern has been how fast I could get the new pages indexed. I add a temporary note on my homepage about the breakup when I do one, with links to the new pages, that works for my site, but might not fit well on all sites.

[pageoneresults]

My concern has been how fast I could get the new pages indexed.

You may want to look into using the Link Relationship element to group those pages together. ;)

B.4 Notes on helping search engines index your Web site
[w3.org...]

[Sweet Cognac]

Well, in my situation it was better to have more content on one page. For instance say I have a page called Blueberry recipes. The page is real real long, filled with recipes for blueberries.

So I take this page and split it up into Blueberry cake recipes, blueberry muffins, blueberry pancakes, bla bla
So I create 5 separate blueberry pages.

The 1st blueberry page was ranking anyway, and I was being found for anything with blueberries in it.

So what happened is by splitting the page into several new pages, it caused the keyword density to drop. Having one or two blueberry recipes on one page did not rank for that recipe (and still doesn't) and when visitors came to the blueberry page they did not find their recipe, they found a link to a new page with that recipe on it.

Then, not only did I have to interlink the blueberry pages, but it also made them level 3, and it took forever for the serps to find them.

So I wound up having to put links on the index pages, telling the serps there were new pages, and the navigation got ridiculous. I felt the visitors were doing too much clicking around to find what they were looking for.

Now some people may want it this way, and maybe that's why their visitors are clicking out of the page via adsense, I do not know.

[fischermx]

A simple tip which earns me an extra $300 per day...

How much you were doing?
It is important to know, because if you were doing $300 that means it doubled your income.
But if you were a high player with thousands a day, then it might not be representative.

[Process]

Sweet Cognac has a point: In our case only the first page seems to ever rank in the SERPs and decreasing the per page/ first page content would lead to decrease in natural search ranking.

[Chris999]

Sorry i should have said.

$550 per day before
$900 per day now

[farmboy]

Suppose you have a long page and break it up into 5 pages. Create 5 channels (Channel 1, Channel 2, etc.) and put the Channel 1 code on the first page, Channel 2 code on the second page, etc.

On your reports page, the channels will show up listed together and in order. It's interesting to see that line-up and see how many people made it from page 1 to page 2 then on to page 3, etc.

FarmBoy

[Whoa]

Great tip. I come here every so often and it's so great to get good tips like this, even if they seem like common sense after you hear them.

Speaking of tips, I just did a Google search on

site:www.webmasterworld.com "Great tip"

and it turns out that's a good way to cut through a lot of the noise here and find some good tips quickly.

[BillDex]

So, what's the HTML-code for the pages so that they don't scroll down more than half a page?

[Juan_G]

Whoa wrote:

Speaking of tips, I just did a Google search on

site:www.webmasterworld.com "Great tip"

and it turns out that's a good way to cut through a lot of the noise here and find some good tips quickly.

That's a great tip as well. :)

[unperturbed]

seanpecor wrote:

If anyone wants the code I can paste it here.

I'd appreciate it.

Cheers

[Chris999]

In addition to this another good reason to split your pages up is that Googlebot only indexes the first 101k of each webpage. Other bots have similar size limits.

Splitting pages will allow Googlebot to index the content past the first 101k of a large page.

Alternatively you can compress you html so that it is less that 101K for each page. Absolute HTML Compressor is a good freeware app to do this. Removes extra white spaces, unnecessary tags etc.

From experience I know that many publishers don't know about these indexing limits.

[seanpecor]

Hey folks, got the PM request from Unperterbed, and boiled down the code to paginate article text by adding [page title="title here"] tags at desired page break locations. It's PHP, and only 70 or so lines, so I thought I'd post it here. If you can't do PHP then the code is simple enough to be translated into other languages without too much fuss.

<?php
function article_titles($strings)
{
$GLOBALS['a_page_total']++;
$GLOBALS['a_titles'][$GLOBALS['a_page_total']] = preg_replace(array("/\"$/", "/^\"/"), array("",""), trim($strings[1]));
$result = "¦¦¦G" . ($GLOBALS['a_page_total']) . "¦¦¦";
return ($result);
}

function article_display($body)
{
$GLOBALS['a_titles'] = array();
$GLOBALS['a_page_total'] = 0;
// ** Replace fake page title tags with an index token and store the title in the a_titles global array.
$body = preg_replace_callback("/<[ ]*[Pp][Aa][Gg][Ee][ ]+[Tt][Ii][Tt][Ll][Ee][^=]*[=]([^>]*)>/", "article_titles", $body);

if ($GLOBALS['a_page'] < 1) $GLOBALS['a_page'] = 1;
if ($GLOBALS['a_page'] > $GLOBALS['a_page_total']) $GLOBALS['a_page'] = $GLOBALS['a_page_total'];

$a_title = $GLOBALS['a_titles'][$GLOBALS['a_page']-1];

// Shrink $body (containing the entire article text) to just the text on the page being displayed.
if ($GLOBALS['a_page'] == $GLOBALS['a_page_total'])
{
$token = "¦¦¦G{$GLOBALS['a_page']}¦¦¦";
$body = substr($body, strpos($body, $token)+strlen($token));
} else
{
$token = "¦¦¦G{$GLOBALS['a_page']}¦¦¦";
$token_b = sprintf("¦¦¦G%s¦¦¦", $GLOBALS['a_page']+1);
$body = substr($body, strpos($body, $token)+strlen($token), strpos($body, $token_b)-strlen($token_b));
}

if ($GLOBALS['a_page'] < $GLOBALS['a_page_total'])
{
$next_title=$GLOBALS['a_titles'][$GLOBALS['a_page']+1];
} else
$next_title="";

if (($GLOBALS['a_page']<$GLOBALS['a_page_total']) && ($GLOBALS['a_page_total']))
{
$body .= sprintf("<p><div align=\"right\"><a href=\"article.php?a_id=123&a_page=%s\">Next Page%s</a></div>", $GLOBALS['a_page']+1, $next_title? " - $next_title":"");
}

if ($GLOBALS['a_page_total']>1)
{
$body .= "<p><div class=\"H3\">Contents</div></p>";

$body .= "<p>";
for ($n=1; $n<=$GLOBALS['a_page_total']; $n++)
{
if ($n == $GLOBALS['a_page'])
{
$body .= sprintf("%s. %s<br>", $n, $GLOBALS['a_titles'][$n]);
} else
{
$body .= sprintf("%s. <a href=\"article.php?a_id=123&a_page=%s\">%s</a><br>", $n, $n, $GLOBALS['a_titles'][$n]);
}
}
$body .= "</p>";
}

echo str_replace("\n\n", "<p>", $body);

echo "<br clear=all>";
}

if (!isset($a_page)) $a_page=1;
echo "\n";
article_display("<page title=\"Introduction\">Hello Folks. This is page one. Hello Folks. This is page one. Hello Folks. This is page one. Hello Folks. This is page one. Hello Folks. This is page one. Hello Folks. This is page one. Hello Folks. This is page one. Hello Folks. This is page one. Hello Folks. This is page one. Hello Folks. This is page one. <page title=\"Pondering Navel\">Here I am pondering my navel. This is page two. Here I am pondering my navel. This is page two. Here I am pondering my navel. This is page two. Here I am pondering my navel. This is page two.<page title=\"Page three is cooler\">Wheee this is fun. This is page three. Wheee this is fun. This is page three. Wheee this is fun. This is page three. Wheee this is fun. This is page three. ");
echo "\n";
?>

[1][[b]edited by[/b]: jatar_k at 9:52 pm (utc) on April 1, 2006][/1]
[1][edit reason] no urls thanks [/edit][/1]

[fischermx]

From experience I know that many publishers don't know about these indexing limits.

In my experience I have, right now, pages with 200KB-400KB indexed and ranking.
Did they make an exception with me? :)

[Chris999]

they index the pages but not the keywords after 101k.

I'm not saying they ignore pages larger than 101k

[jatar_k]

part of the reason this tip works may just be because everyone's pages are disgustingly big

isn't really an adsense tip so much as a usability tip

>> 200KB-400KB

no reason for any page to be that big, pages shouldn't even be over 40k if you ask me

[Whoa]

I have ads on right nav separate from my article content but I also have ads in the article. It goes something like this:

Article title
Article summary (one paragraph)
One or two sentences of the article
Adsense Ads
Rest of Article

At 1024x768, they usually see three ads above the fold (2 on the right nav and 1 in the center in the article content).

If they scroll down to read the article, they see 2 more ads in the center section and three more on the right.

If the article is long and they skim or read it all the way to the bottom, I don't have ads down there.

I was thinking about splitting up the longer articles into multiple pages, but I think it might annoy them if they scroll down past my center section ads to see the article and they only get a few more paragraphs, then have to jump to another page, then have to scroll through more center section ads, etc.

My current setup garners 10%+ CTR so I'd hate to put that at risk. Is anybody out there splitting long articles into multiple pages but still making readers jump over ads in the middle of an article? Does that work?

What I really need to figure out is traffic. I've got good CTRs but not enough people coming. Sticky me if you have good ideas on traffic building. Thanks.

[unperturbed]

seanpecor,

Thanks, I really appreciate that,

Cheers.

[deenybird]

what do you guys mean, the first 101 k of the page?
That doesn't include images right?
Just the text?

[j3r0m3]

definitely food for thought for me.

will need to push through with my implementation of the advice. SO much to do, so little time.

[Whoa]

what do you guys mean, the first 101 k of the page?

You're right. It's the text, not the graphics. If you load a page up in your browser and do a View Source and save that text file, that's the size we're talking about.

When you see a result in Google in the results page for a search, it will tell you how big Google says the file is. If you see 101k, it means you may have some content and links that Google is ignoring.

Not sure if it's still the case, but you used to be able to view the Google cache for your file and you would only see the first 101k of data, so you could see exactly where it stopped.

Now, just doing a quick look, I see a file in the results that 155k but that's for a big name company. Not sure if they've expanded beyond 101k for everyone or just for the "important" sites out there.

In any case, it's best to get as small as possible. Put javascript in .js files, etc. All things being equal between two sites and two web pages, Google will put the smaller one higher in the results in my experience.

[g1c9]

Very good tip, thank you.

[malasorte]

Implemented this tip last week and split some of my long pages in multiple chapters. Bad idea. When using site:www.mydomanin.com Google shows the new pages (resulted from the split) as supplemental. Traffic is down for the pages I split...

The CTR is a little up, but not enough to compensate for the loss in traffic.