: SEO impact of breaking one nested menu into two flat menus So, I have a menu with this structure: <ul> <li> <a>First Level Menu item</a> <ul>
So, I have a menu with this structure:
<ul>
<li>
<a>First Level Menu item</a>
<ul>
<li><a>Second Level Menu Item</a></li>
</ul>
</li>
</ul>
And for design Purposes, I consider moving the second level menu out of the original menu and create a new one:
<ul>
<li>
<a>First Level Menu item</a>
</li>
</ul>
.
.
<ul>
<li><a>Second Level Menu Item</a></li>
</ul>
I suspect that there will be an SEO impact since I will have two menus instead of one tree structured menu.
Will there be a negative SEO impact on that?
Is there a way that I can tell the crawler that those two menus are connected, or some how semantically connect them?
More posts by @Odierno851
3 Comments
Sorted by latest first Latest Oldest Best
After looking at your given code, I think there will be no impact as far as the keyword ranking is concern.
Normally changing h tags fluctuate the organic ranking, but in your case the html is looking simple so the change in the navigation bar will not create big problem for you.
The content, UX, linking of the pages should be the same.
There will be no negative impact on this from the SEO vantage point. Maintaining a navigation tree is more of an UX thing than an SEO thing. As long as both the pages are crawlable by spiders, you should be fine.
If you still want to indicate a relation between the links, then create a tree on your HTML sitemap.
Okay. This gets a bit complicated. While no-one short of a search engineer can tell you what any search engine will do specifically, we know a few things based upon what Google tells us in a whole host of places. I will explain.
Google will parse the HTML DOM objects from top to bottom assigning each HTML element with an ID that will uniquely identify the HTML element, assign an order to the element, assign parent-child relationships between elements such as in ordered lists, and finally, when how one element relates to another such as paragraphs following a header. Using the IDs, the original HTML can be reconstructed as well as be referenced in semantic block elements and dependencies from one to another. Keep this in mind.
Also, keep in mind that Google will compare pages to know what HTML DOM elements exist on several or all pages so that it can properly identify content from other elements such as header, navigation, side-bar, footer, etc.
Semantics is based upon this.
Taking what we know, both of your list elements will be taken as templated HTML DOM elements separate from content. Your first list will be given more importance simply because it appears first, however, since you are using list elements (at least in your example), the importance difference would be small. Your example does not use the nav tag. I invite people to comment if this tag is necessary or important. I use it.
It may be to your advantage to use the tag to signal that both lists are navigation. The tag may help search engines see your navigation properly. Search engines, consider navigation as very important signals to your most important pages. Using the tag, in theory, should tie your two list elements semantically as important (navigation) DOM elements and weigh them higher than (templated) content elements.
While I am a believer that navigation should be as simplified as possible to avoid issues, I rather suspect that your two list elements should be seen okay. I prefer a single list element, however, I rather suspect having two lists should be fine. Just know that it is very possible that the second list element would be seen as less important, though not much. For this reason, be careful to keep this in mind and organize your links accordingly.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.