Feb 19, 2010
  10907
(1 votes)

PageName vs UrlSegment Report

When editors start putting content in their empty site, they will probably start with some test pages or not a well thoughtful page name in the structure. Later the editors often change page names several times until they are satisfied and at the end the site goes live.

What many of the editors don’t know is that the Url Segment of the page only are set the first time the page is published. Since the Url Segment property is found on the Advanced Panel in Editmode, many editors do not see nor have the necessary permissions rights to access this panel / property.

PageNameVsUrlSegment

So, to help the editors in their daily work, I created a simple report which displays the pages that differ between the page name and the expected Url Segment. This report will give the editor a quick overview of the pages that differ. I don’t see how an editor can find these pages in a sensible time another way.

Remember that changing the Url Segment after the site is live will have an impact on the SEO and previously indexed url’s. A nice feature would be to combine the change of the Url Segment with this logic http://world.episerver.com/Blogs/Magnus-von-Wachenfeldt/Dates/2010/2/Update-to-the-Url-Mapping-Module/ and the 404 Handler from EPiCode.

You can download the project from EPiCode:
https://www.coderesort.com/p/epicode/browser/EPiCode.ReportCenter.Reports

 

Would be nice with some ajax functionality on this report, feel free to update the report with improvements.

Feb 19, 2010

Comments

Sep 21, 2010 10:33 AM

This is awesome! I often see pages with differences in name and urlsegment. This way, people can fix it easily. :)

Apr 3, 2017 11:15 AM

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |