How do you have include files that spiders don't see?

Simply too much code at the top of my pages...

[RoosterTail]

(Split off, relative to: [webmasterworld.com...]

My issue is this... I have a page that is 34KB in size, and the keyword phrases I'm targeting are allover the place, but in the best ways possible. Heading tags, awesome META tags, and excellent, unique content.

Yet, my KW density (according to kwda.cgi) is only at 7.5% at best. If you look at the page, in terms of text, it's easily 15% to 20%, but the sites header and left hand navigational items are killing the code.

I took a long hard look around the forums, and could not find the exact information needed to address the situation.

Basically, I am looking to do the following:

1.) Pull out the heading table (about 14KB alone!) and put it into some sort of an include file

2.) Make sure that the include file is NOT read through by the spiders.

** - the header is consistent throughout the entire site. While I could edit the CSS properties and move the table to the bottom of the page, the page SIZE would still be too large to get my KW density in the range I want (15% to 20%).

-- How can you make an include file available to the browsers, but not the SE agents? I don't want to cloak, I just want them to realize that there's a lot of legit content there -- and they never actually pull the real content because of all this bloated code...

[Birdman]

Without cloaking, the only way I can think of is client-side JavaScript, which could alienate some users. Probably better to minimize the header and nav menu code and present the content first.

[jdMorgan]

RoosterTail,

Without cloaking, if content is fed to a browser, it will be fed to a search robot as well. Using JavaScript (which is generally ignored by SE robots) to present your navigation is a flawed approach, since ~10% of users disable JavaScript. Adding a <noscript> section to support these JavaScript-disabled users would only exacerbate your problem.

You might consider re-arranging your page so that it is rendered by a browser in a different order than that implied by the source code order. One of the more widely-used methods is to use the table trick [webmasterworld.com]. Another method is absolute positioning with CSS <div>s. In this way, the important content of your page can be placed first in the source code, but display "further down" on the page when rendered by a browser.

HTH,
Jim

[RoosterTail]

While i really dislike the idea... Could an inline frame help this, no bars, no scrolling?

[Oaf357]

Hmm... I think your screwed on this one. Perhaps you should slowly work filler and stop words out of the web page.

[RoosterTail]

Crapola... That stinks. Thanks all for your help.