> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/developer-guides/error-messages/0088-to-0723/aur0709.md).

# AUR0709

Template compilation error: local element template needs to be defined directly under root of element "yyyy".

### **Error message**

Template compilation error: local element template needs to be defined directly under root of element "{{0}}".

### **Parameters**

1. `elementName`: The name of the custom element being compiled.

### Error explanation

This error occurs during template compilation when a local element definition (`<template as-custom-element="...">`) is found nested inside another element within the main template, rather than being a direct child of the root `<template>` element. Local elements must be defined at the top level of the parent component's template content.

### Common causes

* Placing a `<template as-custom-element="...">` tag inside a `<div>`, `<span>`, or any other element within the main `<template>`.

### How to fix

* Move the `<template as-custom-element="...">` tag so that it is a direct child of the root `<template>` element of the parent component.

### Example of Incorrect Usage:

```html
<!-- my-component.html -->
<template>
  <div>
    <!-- Error: Local element definition is nested inside a div -->
    <template as-custom-element="local-one">
      <span>Content for local-one</span>
    </template>
  </div>
  <local-one></local-one>
</template>
```

### Example of Correct Usage:

```html
<!-- my-component.html -->
<template>
  <div>
    <!-- Use the local element here -->
    <local-one></local-one>
  </div>

  <!-- Define the local element as a direct child of the root template -->
  <template as-custom-element="local-one">
    <span>Content for local-one</span>
  </template>
</template>
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aurelia.io/developer-guides/error-messages/0088-to-0723/aur0709.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.