We are seeing Googlebot crawl URL's on our site without interpreting the XHTML & as an & character. For example we do a proper XHTML href on our pages (note the & entity reference):
> We are seeing Googlebot crawl URL's on our site without interpreting > the XHTML & as an & character. For example we do a proper XHTML > href on our pages (note the & entity reference):
Just a guess, but you probably need to change the 'Content-type' <meta> tag. Your server is sending Content-Type "text/html" in the response header for these URLs, and then you reinforce that with the <meta> tag which comes AFTER your <!DOCTYPE>. Try "text/xhtml" in the <meta> tag, and set up code 301 redirects in your .htaccess file to fix the ampersand problems you've already got in Google.
> Just to clarify, what we're seeing is that GoogleBot is requesting the > URL with & between arguments instead of &.
> On Feb 7, 3:14 pm, thuss wrote:
> > We are seeing Googlebot crawl URL's on our site without interpreting > > the XHTML & as an & character. For example we do a proper XHTML > > href on our pages (note the & entity reference):
Rainborick, Wow!! The subject of 301 comes up here a LOT but I would have never thought of creating a 301 to fix a bug in a URL like that, no matter where the error came from.
> Just a guess, but you probably need to change the 'Content-type' > <meta> tag. Your server is sending Content-Type "text/html" in the > response header for these URLs, and then you reinforce that with the > <meta> tag which comes AFTER your <!DOCTYPE>. Try "text/xhtml" in the > <meta> tag, and set up code 301 redirects in your .htaccess file to > fix the ampersand problems you've already got in Google.
> On Feb 7, 3:18 pm, thuss wrote:
> > Just to clarify, what we're seeing is that GoogleBot is requesting the > > URL with & between arguments instead of &.
> > On Feb 7, 3:14 pm, thuss wrote:
> > > We are seeing Googlebot crawl URL's on our site without interpreting > > > the XHTML & as an & character. For example we do a proper XHTML > > > href on our pages (note the & entity reference):
> Just a guess, but you probably need to change the 'Content-type' > <meta> tag. Your server is sending Content-Type "text/html" in the > response header for these URLs, and then you reinforce that with the > <meta> tag which comes AFTER your <!DOCTYPE>. Try "text/xhtml" in the > <meta> tag, and set up code 301 redirects in your .htaccess file to > fix the ampersand problems you've already got in Google.
> On Feb 7, 3:18 pm, thuss wrote:
> > Just to clarify, what we're seeing is that GoogleBot is requesting the > > URL with & between arguments instead of &.
> > On Feb 7, 3:14 pm, thuss wrote:
> > > We are seeing Googlebot crawl URL's on our site without interpreting > > > the XHTML & as an & character. For example we do a proper XHTML > > > href on our pages (note the & entity reference):
> Is text/xhtml a legitimate MIME type? I've never seen it before. I > always thought XHTML used the text/html MIME.
> Fred
> On Feb 7, 6:43 pm, RainboRick wrote:
> > Just a guess, but you probably need to change the 'Content-type' > > <meta> tag. Your server is sending Content-Type "text/html" in the > > response header for these URLs, and then you reinforce that with the > > <meta> tag which comes AFTER your <!DOCTYPE>. Try "text/xhtml" in the > > <meta> tag, and set up code 301 redirects in your .htaccess file to > > fix the ampersand problems you've already got in Google.
> > On Feb 7, 3:18 pm, thuss wrote:
> > > Just to clarify, what we're seeing is that GoogleBot is requesting the > > > URL with & between arguments instead of &.
> > > On Feb 7, 3:14 pm, thuss wrote:
> > > > We are seeing Googlebot crawl URL's on our site without interpreting > > > > the XHTML & as an & character. For example we do a proper XHTML > > > > href on our pages (note the & entity reference):
