> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/troubleshooting/domain-verification/troubleshooting-verify-domain-meta-tag.md).

# Troubleshoot domain verification with meta tag

How to troubleshoot domain verification with a meta tag in Snyk API & Web

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## Troubleshoot domain verification with meta tag

For Snyk API & Web to run full scans, you must verify your domains. Visit [Verify domain ownership](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership.md) to learn why domain verification is required.

### The problem

Domain verification using a meta tag fails with the error: `Meta tag not found.`

### Troubleshoot the problem

Work through the following steps to identify the possible causes and solutions.

#### Check the index page source

Test if the meta tag is present in the index page source in one of the following ways:

* Use the browser:
  1. Type the URL to the index page: `https://<domain_to_verify>`, for example: `https://example.com`.
  2. Right-click the page and select **View Page Source**.
* Use a curl command like this: `curl -i https://<domain_to_verify>`, for example: `curl -i https://example.com`.

Analyze the HTML of the index page source, check the following possible causes, and apply the solution:

| Cause                                                                                                                                          | Solution                                                                                                                   |
| ---------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| The meta tag is not on the index page.                                                                                                         | Review the implementation to add the meta tag before the closing `</head>` tag on the index page.                          |
| The meta tag is on the index page, but not inside the `<head>` tag.                                                                            | Review the implementation to have the meta tag before the closing `</head>` tag on the index page.                         |
| The meta tag is on the index page inside the `<head>` tag, but it is being injected using JavaScript (for example, a Single-Page Application). | Review the implementation to add the meta tag before the closing `</head>` tag on the index page without using JavaScript. |

After following these steps and applying the solutions, you can verify your domain using a meta tag.

### Related articles

* [Verify domain ownership](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership.md)
* [Verify domain with meta tag](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership/verify-with-meta-tag.md)


---

# 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.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/troubleshooting/domain-verification/troubleshooting-verify-domain-meta-tag.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.