Feb 19, 2010
  10865
(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 PaaS + Figma + AI: Auto‑Generate Blocks with Cursor

What if your design handoff wrote itself? In this end‑to‑end demo, I use an AI Agent (inside Cursor) to translate a Figma design into an... The pos...

Naveed Ul-Haq | Feb 5, 2026 |

Graph access with only JS and Fetch

Postman is a popular tool for testing APIs. However, when testing an API like Optimizely Graph that I will be consuming in the front-end I prefer t...

Daniel Halse | Feb 4, 2026

Best Practices for Implementing Optimizely SaaS CMS: A Collective Wisdom Guide

This guide compiles collective insights and recommendations from Optimizely experts for implementing Optimizely SaaS CMS, focusing on achieving...

David Knipe | Feb 4, 2026 |

A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026