> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/languages/html.md).

# HTML

## Language-specific properties <a href="#language-specific-properties" id="language-specific-properties"></a>

You can discover and update HTML-specific [Analysis parameters](/sonarqube-server/2026.1/analyzing-source-code/analysis-parameters.md) in: **Administration** > **Configuration** > **General Settings** > **Languages** > **HTML**

## PHP code analysis <a href="#php-code-analysis" id="php-code-analysis"></a>

PHP and HTML analyzers both analyze files with extensions: `.php`, `.php3`, `.php4`, `.php5`, `.phtml`.

File metrics, such as the number of lines of code, can only be measured by one of the languages, PHP or HTML. They are handled by the PHP analyzer by default, and by HTML analyzer if for some reason the former is not present.

The HTML analyzer inspects PHP files even if the PHP file extensions are not included in the list of file extensions to analyze.

## In-line suppression of issues <a href="#in-line-suppression-of-issues" id="in-line-suppression-of-issues"></a>

Adding the `//NOSONAR` comment at the end of the line will suppress all issues on that line.

{% hint style="warning" %}
Rather than relying on this method, we suggest refining your analysis scope to avoid creating major gaps in your code review. Because the `NOSONAR` comment silences all current and future issues on a line without regard for their severity, it is an imprecise tool. Even if you only intend to hide a minor stylistic point, you could unintentionally obscure a serious security flaw.
{% endhint %}

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Analysis parameters](/sonarqube-server/2026.1/analyzing-source-code/analysis-parameters.md)
* [Analysis scope](/sonarqube-server/2026.1/instance-administration/analysis-functions/analysis-scope.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/languages/html.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.