> For the complete documentation index, see [llms.txt](https://docs.codpeller.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codpeller.com/en/html-validator/getting-started.md).

# Getting started

HTML Validator 2.0 FREE lets you check the HTML of an open webpage in **Google Chrome's Side Panel**. This guide walks you through your first validation, from opening the extension to reviewing the results.

## Before you start

Make sure HTML Validator 2.0 FREE is installed in Google Chrome. Open a webpage that you are allowed to inspect.

This guide covers regular webpages. To check HTML files stored on your computer, Chrome must also allow the extension to access local file URLs. See the **User Guide** for details.

## Step 1. Pin HTML Validator to the Chrome toolbar

1. Click the **Extensions** (puzzle-piece) icon in the Chrome toolbar.
2. Find **HTML Validator** in the menu.
3. Click the **Pin** icon next to HTML Validator.

The HTML Validator icon will remain visible in the browser toolbar, making the extension easier to open.

![Chrome Extensions menu showing how to pin HTML Validator to the toolbar](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/fXfM03zN6i37lSgjOYSI/images%2F01_pin_extension.png)

*Pin HTML Validator from the Chrome Extensions menu.*

## Step 2. Open the Side Panel

1. Open the webpage you want to check.
2. Click the pinned **HTML Validator** icon.

HTML Validator opens in Chrome's **Side Panel**, alongside the webpage. The panel has three tabs: **Validate**, **Results**, and **HTML**. You do not need to open DevTools.

![Webpage beside HTML Validator Side Panel with the Validate tab and validation controls](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/fODLusbtgZ6Fu4V1hTDL/images%2F02_sidepanel_validate.png)

*Open the Side Panel and use the Validate tab. The Validate tab shows the Current DOM option, both engines, and the Validate HTML button described in Step 3.*

## Step 3. Validate the Current DOM

In the **Validate** tab, the **HTML to validate** section shows **Current DOM**. This is the page's HTML as represented in the browser when the snapshot is captured, including changes made by JavaScript. It may differ from the HTML originally returned by the server.

Under **Validation engine**, select one of the following:

* **W3C Nu (online)** — checks HTML using an external, standards-focused validator. **The HTML being checked is sent to `validator.w3.org`.** Use this option only when sending the page content to an external service is appropriate.
* **HTML Tidy (offline)** — performs basic HTML checks locally in the extension. Its results may differ from W3C Nu: it can flag valid modern HTML or miss some conformance errors.

Click **Validate HTML** to start the check.

## Step 4. Review the results

In **Results**, review the validation status, error and warning counts, and individual messages. A message can include a line and column when this information is available.

* Expand an issue to view its HTML excerpt in **Results**.
* Click **Copy** to copy the details of that issue to the clipboard. Copying does not send a report automatically.
* Click **Locate** to open the relevant location in the separate **HTML** tab.

Before sharing copied issue details, review their contents: page paths and filenames may contain information you do not want to disclose.

![HTML Validator Results tab with an example error, issue details and available actions](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/8RRcGrPEmC8gwWQIfLIx/images%2F05_results_expanded.png)

*Example: an expanded validation issue with Locate, Copy, and the related HTML excerpt.*

## Step 5. Find the issue in the HTML viewer

Click **Locate** on an issue in **Results**. HTML Validator switches to the **HTML** tab, displays the HTML snapshot used for that validation, and highlights the corresponding location.

**Locate does not highlight an element on the live webpage.** The HTML viewer is read-only; use your own project or editor to fix the markup.

![HTML tab showing a highlighted error line in the validated Current DOM snapshot](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/p22PboDU6BJrbmP5yMyN/images%2F06_html_viewer_locate.png)

*Example: Locate opens a highlighted line in the HTML tab. This screenshot uses a different demonstration error from Step 4.*

## Step 6. Check your changes with Revalidate

After fixing your website's HTML, refresh the webpage if necessary. Then click **Revalidate** to capture and check the page again. Previous results do not update automatically when the page changes.

A successful check can display **No HTML errors found**. The exact result depends on the chosen engine and the HTML being checked.

![Results tab showing a successful W3C Nu check and the Revalidate button](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/wTUTh65b3uYICezoNY9B/images%2F07_revalidate.png)

*Example: the successful validation state and the Revalidate button.*

## Next steps

Read the [User Guide](https://docs.codpeller.com/en/html-validator/user-guide.md) for more about W3C Nu, HTML Tidy, local HTML files, Settings, and the HTML viewer. If validation or file access does not work as expected, see [Troubleshooting](https://docs.codpeller.com/en/html-validator/troubleshooting.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.codpeller.com/en/html-validator/getting-started.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.
