[MAGNOLIA-3385] Render flat navigation hierarchies for SEO Created: 12/Nov/10 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | Boris Kraft | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
By default, our navigation elements reflect the hierarchy of a site. For SEO reasons it would be good if the hierarchies are as flat as possible, at best having only top level pages. For understanding the logical structure of a site, hierarchies are however very desirable. What I imagine is that the navigation elements actually render as they do now but point to top-level "aliases". In fact, no deep links should ever be rendered anywhere (to avoid duplicate content violation). So while my page hierarchy is as follows: The menu would look: home
But e.g. history would always link to www.a.com/history.html not www.a.com/home/about/history.html One problem that I see is that we would need to ensure that in such a case all page names are unique. (Observation?) As a related issue, I think the "folder" concept discussed for STK goes in a similar direction; possible with better control over which hierarchies are flat and which are not. |
| Comments |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |