Skip to main content
replaced http://webmasters.stackexchange.com/ with https://webmasters.stackexchange.com/
Source Link

For a long time I wondered if navigation links would negatively impact SEOnavigation links would negatively impact SEO, and as a precaution in designs that allowed for this solution, I've put the entire navigation at the bottom of the source code and fixed its position at the top of the viewport.

I've always thought that in source code, the earlier your actual content is encountered, the better that is for your SEO. Big navigation menus push your actual content down in the source code. So naturally, my solution was to put them at the very end of the page and use CSS to visually place them where I need them.

I'd like to know if this is really beneficial or if I've just been believing a myth.

For a long time I wondered if navigation links would negatively impact SEO, and as a precaution in designs that allowed for this solution, I've put the entire navigation at the bottom of the source code and fixed its position at the top of the viewport.

I've always thought that in source code, the earlier your actual content is encountered, the better that is for your SEO. Big navigation menus push your actual content down in the source code. So naturally, my solution was to put them at the very end of the page and use CSS to visually place them where I need them.

I'd like to know if this is really beneficial or if I've just been believing a myth.

For a long time I wondered if navigation links would negatively impact SEO, and as a precaution in designs that allowed for this solution, I've put the entire navigation at the bottom of the source code and fixed its position at the top of the viewport.

I've always thought that in source code, the earlier your actual content is encountered, the better that is for your SEO. Big navigation menus push your actual content down in the source code. So naturally, my solution was to put them at the very end of the page and use CSS to visually place them where I need them.

I'd like to know if this is really beneficial or if I've just been believing a myth.

added 111 characters in body
Source Link

For a long time I wondered if navigation links would negatively impact SEO, and as a precaution in designs that allowed for this solution, I've put the entire navigation at the bottom of the source code and fixed its position at the top of the viewport.

I've always thought that in source code, the earlier your actual content is encountered, the better that is for your SEOthe earlier your actual content is encountered, the better that is for your SEO. Big navigation menus push your actual content down in the source code. So naturally, my solution was to put them at the very end of the page and use CSS to visually place them where I need them.

I'd like to know if this is really beneficial or if I've just been believing a myth.

For a long time I wondered if navigation links would negatively impact SEO, and as a precaution in designs that allowed for this solution, I've put the entire navigation at the bottom of the source code and fixed its position at the top of the viewport.

I've always thought that in source code, the earlier your actual content is encountered, the better that is for your SEO. Big navigation menus push your actual content down in the source code. So naturally, my solution was to put them at the very end of the page and use CSS to visually place them where I need them.

I'd like to know if this is really beneficial or if I've just been believing a myth.

For a long time I wondered if navigation links would negatively impact SEO, and as a precaution in designs that allowed for this solution, I've put the entire navigation at the bottom of the source code and fixed its position at the top of the viewport.

I've always thought that in source code, the earlier your actual content is encountered, the better that is for your SEO. Big navigation menus push your actual content down in the source code. So naturally, my solution was to put them at the very end of the page and use CSS to visually place them where I need them.

I'd like to know if this is really beneficial or if I've just been believing a myth.

Tweeted twitter.com/StackWebmasters/status/735811494911344640
Source Link

Menu code in footer, visually fixed on top

For a long time I wondered if navigation links would negatively impact SEO, and as a precaution in designs that allowed for this solution, I've put the entire navigation at the bottom of the source code and fixed its position at the top of the viewport.

I've always thought that in source code, the earlier your actual content is encountered, the better that is for your SEO. Big navigation menus push your actual content down in the source code. So naturally, my solution was to put them at the very end of the page and use CSS to visually place them where I need them.

I'd like to know if this is really beneficial or if I've just been believing a myth.