<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Santiago Morla</title><link href="http://world.optimizely.com" /><updated>2026-02-12T22:18:45.0000000Z</updated><id>https://world.optimizely.com/blogs/santiago-morla/</id> <generator uri="http://world.optimizely.com" version="2.0">Optimizely World</generator> <entry><title>Technical SEO That Ships: Building Google News Sitemaps Into the CMS</title><link href="http://opticmsxperience.com/?p=333" /><id>Technical SEO is full of work that sounds small in a planning meeting and turns out to be product infrastructure once you start building it. &amp;#8220;Add a news sitemap&amp;#8221; is one of those requests. If the goal is to be discoverable in Google News, the work is not just about generating XML. You need publication-specific&lt;a class=&quot;more-link&quot; href=&quot;https://opticmsxperience.com/2026/02/12/technical-seo-that-ships-building-google-news-sitemaps-into-the-cms/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Technical SEO That Ships: Building Google News Sitemaps Into the&amp;#160;CMS&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2026-02-12T22:18:45.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Gated Media Without Fragile Redirects in Optimizely CMS</title><link href="http://opticmsxperience.com/?p=343" /><id>Restricted media usually looks simple on the whiteboard. If the user can read the asset, serve it. If they cannot, redirect them to sign in. In practice, document protection breaks in much more interesting ways than that. The rendered page may expose a direct asset URL before the request pipeline ever sees it. A redirect&lt;a class=&quot;more-link&quot; href=&quot;https://opticmsxperience.com/2025/12/09/gated-media-without-fragile-redirects-in-optimizely-cms/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Gated Media Without Fragile Redirects in Optimizely&amp;#160;CMS&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2025-12-09T14:22:41.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Moving SSO Configuration From `appsettings` Files to PaaSPortal Without Rewriting the App</title><link href="http://opticmsxperience.com/?p=347" /><id>That was the interesting part of this configuration update. The visible code change was tiny: the committed value for SSO:AzureAD_ClientSecret was removed from appsettings.json and appsettings.Production.json, leaving the key present but empty. The actual secret was then expected to come from PaaSPortal-managed application settings at deployment time. On paper, that sounds almost too small to&lt;a class=&quot;more-link&quot; href=&quot;https://opticmsxperience.com/2025/11/05/moving-sso-configuration-from-appsettings-files-to-paasportal-without-rewriting-the-app/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Moving SSO Configuration From `appsettings` Files to PaaSPortal Without Rewriting the&amp;#160;App&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2025-11-05T15:56:29.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Why `/episerver/health` Failed Behind CMS Security Layers and How We Fixed It</title><link href="http://opticmsxperience.com/?p=352" /><id>Health check failures are often diagnosed as an infrastructure problem first. The app must be down. The load balancer must be wrong. The probe configuration must be off. But sometimes the endpoint is perfectly fine and the real issue is much closer to the request pipeline. That was the shape of this fix. The failing&lt;a class=&quot;more-link&quot; href=&quot;https://opticmsxperience.com/2025/10/08/why-episerver-health-failed-behind-cms-security-layers-and-how-we-fixed-it/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Why `/episerver/health` Failed Behind CMS Security Layers and How We Fixed&amp;#160;It&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2025-10-08T23:02:55.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>How We Stopped Deleted CMS Pages from Showing Up in Personalized Recommendations</title><link href="http://opticmsxperience.com/?p=319" /><id>A small recommendation bug can quietly damage trust when deleted or unpublished pages keep showing up in personalized content modules. Here is a practical pattern for validating third-party recommendation URLs against live CMS content before rendering them.</id><updated>2025-08-14T13:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Extending UrlResolver to Generate Lowercase Links in Optimizely CMS 12</title><link href="http://opticmsxperience.com/?p=282" /><id>When working with Optimizely CMS 12, URL consistency is crucial for SEO and usability. By default, Optimizely does not enforce lowercase URLs, which can lead to duplicate content issues and inconsistent link structures. In this blog, we&#39;ll explore how to extend UrlResolver to ensure all generated URLs are in lowercase.</id><updated>2025-03-07T15:23:52.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Building an Interactive Hotspot Editor in Optimizely CMS 12</title><link href="http://opticmsxperience.com/?p=290" /><id>Have you ever wanted to let content editors place interactive hotspots directly on an image—without leaving the CMS? In this post, I’ll walk through how we built a custom Hotspot Module in Optimizely CMS 12 that does exactly that. What We BuiltThis solution allows editors to:* Upload a background image.* Click directly on the image&lt;a class=&quot;more-link&quot; href=&quot;https://opticmsxperience.com/2024/10/10/building-an-interactive-hotspot-editor-in-optimizely-cms-12/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Building an Interactive Hotspot Editor in Optimizely CMS&amp;#160;12&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2024-10-10T16:06:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Custom ContentArea Converter for Optimizely CMS 12 in a Headless + PaaS Architecture</title><link href="http://opticmsxperience.com/?p=307" /><id>When building headless websites with Optimizely CMS 12 using the Content Delivery API, ContentArea properties can be tricky. By default, they return minimal references to nested content—not the rich, expanded content structures modern frontends need. In this post, I’ll walk through how we solved that by implementing a custom ContentArea converter, giving full control over&lt;a class=&quot;more-link&quot; href=&quot;https://opticmsxperience.com/2024/05/15/custom-contentarea-converter-for-optimizely-cms-12-in-a-headless-paas-architecture/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Custom ContentArea Converter for Optimizely CMS 12 in a Headless + PaaS&amp;#160;Architecture&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2024-05-15T16:48:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Enhancing the Authoring Experience: Extending the LinkItem</title><link href="http://opticmsxperience.com/?p=251" /><id>The LinkItem field is one of the most demanded properties by the community, allowing editors to effortlessly create and manage links across pages and blocks. It was introduced on CMS 12 &amp;#8211; EPiServer.CMS 12.11.0 and this blog post will show how it can be extended to have a better authoring experience. This is how you&lt;a class=&quot;more-link&quot; href=&quot;https://opticmsxperience.com/2024/04/10/enhancing-the-authoring-experience-extending-the-linkitem/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Enhancing the Authoring Experience: Extending the&amp;#160;LinkItem&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2024-04-10T15:42:03.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS – Allow Forms to Redirect to Media Assets</title><link href="http://opticmsxperience.com/?p=239" /><id>Optimizely Forms is a powerful add-on that can improve the experience for authors to create custom forms as needed with plenty of capabilities. It can be also extensible, so a developer can implement custom form elements and add complex logic to forms to accommodate the user&amp;#8217;s needs and the client&amp;#8217;s requirements. Forms can be configured&lt;a class=&quot;more-link&quot; href=&quot;https://opticmsxperience.com/2023/08/16/optimizely-cms-allow-forms-to-redirect-to-media-assets/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Optimizely CMS &amp;#8211; Allow Forms to Redirect to Media&amp;#160;Assets&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2023-08-16T16:41:28.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS 11 – Download Blob items from Production</title><link href="http://opticmsxperience.com/?p=203" /><id>This post will walk you through the process of getting the blob assets from production to get the images working locally.</id><updated>2023-04-04T15:26:07.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS 12 – Unable to Import Data</title><link href="http://opticmsxperience.com/?p=194" /><id>Are you unable to import data from another instance? If you are getting a non-explanatory error message &amp;#8220;No file uploaded&amp;#8221; when you click on &amp;#8220;Upload and Verify File&amp;#8221; or &amp;#8220;Begin Import&amp;#8221;, this post will help you. I exported some content items from a lower environment and I wanted to import them to an upper environment,&lt;a class=&quot;more-link&quot; href=&quot;https://opticmsxperience.com/2023/01/11/optimizely-cms-12-unable-to-import-data/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Optimizely CMS 12 &amp;#8211; Unable to Import&amp;#160;Data&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2023-01-11T15:10:16.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Restricting Environment Access “/Episerver”</title><link href="http://opticmsxperience.com/?p=182" /><id>As a web administrator, you would probably want to restrict the editing portal to the public and one way to achieve this is applying rules directly on yout configuration file so the access can be restricted by IP. You probably have read this article from Optimizely (CMS 11) https://docs.developers.optimizely.com/digital-experience-platform/v1.3.0-DXP-for-CMS11-COM13/docs/restricting-environment-access where it describes how you can&lt;a class=&quot;more-link&quot; href=&quot;https://opticmsxperience.com/2022/08/08/restricting-environment-access-episerver/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Restricting Environment Access &amp;#8220;/Episerver&amp;#8221;&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2022-08-08T17:37:10.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Hide Field From Local Block</title><link href="http://opticmsxperience.com/?p=163" /><id>There are times when you have a local block that is shared across multiple blocks or pages and you want to hide a specific field based on the content type. Here is a guide on how you can achieve this with a custom attribute. Imagine that you have a block which used by other content&lt;a class=&quot;more-link&quot; href=&quot;https://opticmsxperience.com/2022/01/06/hide-field-from-local-block/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Hide Field From Local&amp;#160;Block&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2022-01-06T19:57:17.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely Forms Issue with Claims</title><link href="http://epicmsxperience.com/?p=145" /><id>This is a quick fix for an Optimizely Form issue when your implementation integrates Azure AD with OpenID Connect to sign-in/sign-out users on your application. If you try to browse your page that contains an Optimizely Form and there is an active user session, you could probably get the following error: A claim of type&lt;a class=&quot;more-link&quot; href=&quot;https://epicmsxperience.com/2021/06/30/optimizely-forms-issue-with-claims/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Optimizely Forms Issue with&amp;#160;Claims&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2021-07-01T01:43:38.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Invalidate Cache After Publishing</title><link href="http://epicmsxperience.com/?p=129" /><id>In order to improve performance and enhace the page loading time while using Search and Navigation, Optimizely provides an extension to cache the search results for a specific period of time. StaticallyCacheFor lets you store your query results, using a timestamp, in a cache with an auto-generated key. Once the defined timestamp has reached, the&lt;a class=&quot;more-link&quot; href=&quot;https://epicmsxperience.com/2021/05/31/invalidate-cache-after-publishing/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Invalidate Cache After&amp;#160;Publishing&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2021-05-31T07:47:26.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Allowed Types By Interface</title><link href="http://epicmsxperience.com/?p=113" /><id>Sometimes, you will have a flexible content area where you will be able to add a large number of blocks. In this blog post, I will show you how you can replace a large list of allowed types in a property by using an interface. First, let&amp;#8217;s go with a real scenario, where we have&lt;a class=&quot;more-link&quot; href=&quot;https://epicmsxperience.com/2021/05/15/allowed-types-by-interface/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Allowed Types By&amp;#160;Interface&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2021-05-15T14:44:25.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Exact Time Picker</title><link href="http://epicmsxperience.com/?p=100" /><id>Time picker field is always useful when authors need to manage the time separated from the date. Episerver stores dates as UTC and it dynamically displays the datetime of the content editor&amp;#8217;s machine but what happen if time zone is also managed as a separated field. In this post I will show you how can&lt;a class=&quot;more-link&quot; href=&quot;https://epicmsxperience.com/2021/03/09/exact-time-picker/&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;&quot;Exact Time Picker&quot;&lt;/span&gt;&lt;/a&gt;</id><updated>2021-03-09T22:48:33.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Add Link to Edit Media Asset Fields</title><link href="http://epicmsxperience.com/?p=76" /><id>Finding a media asset sometimes can be challenging if the management is not well-done. Use an EditorDescriptor to let your content authors find you assets easily.</id><updated>2021-01-29T20:04:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Date Range Facets</title><link href="http://epidevmaster.wordpress.com/?p=11" /><id>Faceted search adds powerful search functionality to websites and allows web users to narrow down the results in a listing page, letting the users find what they really want. Sometimes, we need to add a date range facet as part of our search page.  This post will give you some guidance on how to create facets based on DateTime fields using Episerver Search &amp;#38; Navigation (formerly called Episerver Find). </id><updated>2021-01-29T17:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry></feed>