If the server responds 200 OK and then shows a page is that ok though?
example: http://www.lyricsmode.com/lyrics/b/britdey_does_not_exit_spears/ shows a 200 with links that then feed other pages SEO ranking but at
the same time there are over half a million of these indexed in google
which also pick up on hundreds of thousands of key words meaning more
visitors.
> If the server responds 200 OK and then shows a page is that ok though?
> example: http://www.lyricsmode.com/lyrics/b/britdey_does_not_exit_spears/ > shows a 200 with links that then feed other pages SEO ranking but at
> the same time there are over half a million of these indexed in google
> which also pick up on hundreds of thousands of key words meaning more
> visitors.
> On Aug 20, 8:15 am, webado wrote:
> > You can use any kind of custom 404 page PROVIDED your server FIRST
> > responds with the response code 404.
> example: http://www.lyricsmode.com/lyrics/b/britdey_does_not_exit_spears/ > shows a 200 with links that then feed other pages SEO ranking but at
> the same time there are over half a million of these indexed in google
> which also pick up on hundreds of thousands of key words meaning more
> visitors.
> On Aug 20, 8:15 am, webado wrote:
> > You can use any kind of custom 404 page PROVIDED your server FIRST
> > responds with the response code 404.
It's not FROWNED upon. It just constitutes a messed up website if you
cannot control this elementary server response.
Any garbage url will "exist" since there's nothing to say otherwise in
the manner that robots recognize: a 404 response code.
> > If the server responds 200 OK and then shows a page is that ok though?
> > example: http://www.lyricsmode.com/lyrics/b/britdey_does_not_exit_spears/ > > shows a 200 with links that then feed other pages SEO ranking but at
> > the same time there are over half a million of these indexed in google
> > which also pick up on hundreds of thousands of key words meaning more
> > visitors.
> > On Aug 20, 8:15 am, webado wrote:
> > > You can use any kind of custom 404 page PROVIDED your server FIRST
> > > responds with the response code 404.