> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/develop-with-umbraco/templating-and-rendering/templating/modelsbuilder/using-interfaces.md). # Using Interfaces When using compositions, Models Builder generates an interface for the composed model, which enables us to not have to switch back to using `Value()` for the composed properties. A common use-case for this is if you have a separate composition for the "SEO properties" `Page Title` and `Page Description`. You would usually use this composition on both your `Home` and `Textpage` document types. Since both `Home` and `Textpage` will implement the generated `ISeoProperties` interface, you will still be able to use the simpler models builder syntax (e.g. `Model.PageTitle`). A layout template is bound to a generic `IPublishedContent`, so the models builder syntax isn't available there. You'd have to resort to the *ever-so-slightly* clumsier `Model.Value("pageTitle")` syntax instead. Using partial views to render the SEO-specific properties is one way to solve this. ## Render with a partial If you create a partial and change the first line to use the *interface name* for the model binding, you can use the nice Models Builder syntax when rendering the properties, like this: ```csharp @inherits Umbraco.Cms.Web.Common.Views.UmbracoViewPage @Model.PageTitle ``` You can then render the partial from your Layout Template with something like this (assuming the partial is named `Metatags.cshtml`): ```csharp @Html.Partial("Metatags") @RenderBody() ``` It's important to note though, that this layout template will only work for content types that use the Seo Properties composition. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.umbraco.com/umbraco-cms/develop-with-umbraco/templating-and-rendering/templating/modelsbuilder/using-interfaces.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.