On Wed, 2002-01-09 at 09:51, Matt Sergeant wrote:
> On 9 Jan 2002, Brian Wheeler wrote:
> 
> > On Wed, 2002-01-09 at 09:35, Robin Berjon wrote:
> > > On Wednesday 09 January 2002 15:24, Sebastian Rahtz wrote:
> > > > On Wed, Jan 09, 2002 at 03:22:22PM +0100, Robin Berjon wrote:
> > > > > On Tuesday 08 January 2002 22:38, Brian Wheeler wrote:
> > > > > > Our site isn't showing up on various search engines (google, alta
> > > > > > vista) properly.  Is anyone else seeing this on axkit-driven sites?
> > > > > > We're running axkit 1.4.
> > > > >
> > > > > Pretty much all of our sites that are running axkit show up in Google,
> > > > > with proper descriptions and all.
> > > >
> > > > As one would expectl; how can Google possibly know its an axkit site?
> > > > the result is, after all,  just HTML.....
> > >
> > > Yes but there have been cases of dynamic generation systems or publishing
> > > systems that caused search engines to run away (or downgrade the content). I
> > > think this is what Brian was concerned with.
> > >
> >
> > *sniff* I just want it to work :)
> >
> > Seriously, though, the search
> >
> > site:icpac.indiana.edu xml
> >
> > on google returns hits, but no summaries or titles...but not nearly all
> > the pages on our site (somewhere near 39,000)
> 
> Could it be anything to do with the massive number of carriage returns
> before the data? Or the PICS header? Those are the only things I can see
> that are in any way different to axkit.org.

Any way to strip the CRs from the beginning?  They get included because
we do several <!--#include>s.

I'll talk to our content people and find out what the heck that PICS
header is for!

Brian

> 
> -- 
> <!-- Matt -->
> <:->Get a smart net</:->
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to