diff --git a/16/umbraco-cms/reference/searching/examine/indexing.md b/16/umbraco-cms/reference/searching/examine/indexing.md
index 0a5983d2804..13c6f5c7095 100644
--- a/16/umbraco-cms/reference/searching/examine/indexing.md
+++ b/16/umbraco-cms/reference/searching/examine/indexing.md
@@ -54,6 +54,7 @@ using Umbraco.Cms.Core.DependencyInjection;
 
 namespace Umbraco.Docs.Samples.Web.CustomIndexing;
 
+[ComposeAfter(typeof(Umbraco.Cms.Infrastructure.Examine.AddExamineComposer))]
 public class ExamineComposer : IComposer
 {
     public void Compose(IUmbracoBuilder builder)
@@ -63,6 +64,10 @@ public class ExamineComposer : IComposer
 }
 ```
 
+{% hint style="info" %}
+The use of the `ComposeAfter` attribute guarantees that the composer will run after the core composer responsible for setting up the default index details.
+{% endhint %}
+
 ### Changing field value types
 
 By default, Examine will store values into the Lucene index as "Full Text" fields, meaning the values will be indexed and analyzed for a textual search. However, if a field value is numerical, date/time, or another non-textual value type, you might want to change how the value is stored in the index. This will let you take advantage of some value type-specific search features such as numerical or date range.