Øyvind Hognestad
Feb 19, 2010
  9808
(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
Telemetry correlation for Scheduled Jobs in Optimizely

I previously demonstrated how to correlate telemetry to Azure Application Insights within a Hangfire job. But how about those jobs that are built a...

Stefan Holm Olsen | Mar 23, 2023 | Syndicated blog

Fixing Optimizely Content Syncing/Caching Issues on the DXP pre CMS.Core 12.13.0

Hi all, With our recent deployments to the DXP for .NET 6 projects (one a new build and one an upgrade) our clients had raised issues where there...

Scott Reed | Mar 23, 2023

Handle hostnames, schedule jobs and role access when synchronizing content

The Environment Synchronizer module helps you to set your environment into a known state after synchronizing databases between environments. In thi...

Ove Lartelius | Mar 23, 2023 | Syndicated blog

4 tips and tricks for Hangfire on Optimizely CMS

Here are four useful tricks I always apply to any site where I use Hangfire (code included).

Stefan Holm Olsen | Mar 21, 2023 | Syndicated blog