Enter a URL to request its HTML through the server. Tag detection depends on markup format; length hints are not search-engine requirements.
| Label | Contents | Content Length | Recommendations for optimization |
|---|---|---|---|
| Web Title (Title) | - | - | - |
| Web KeyWords | - | - | - |
| Content Description | - | - | - |
Enter a page address and the checker asks the VoriTools server to request that page, then reads the raw HTML it returns. It reports the title element and the keywords and description meta tags as they appear in the source, each with a character count and the tool's own review range.
Because the server reads the delivered HTML rather than a rendered page, what you see is what a crawler receives in the response body: tags added later by JavaScript, values injected by a tag manager or content behind a login never appear. The fetched page is not stored.
The request is made by the VoriTools server, not by your browser, so the target site sees the server's address rather than yours. Only plain HTTP and HTTPS addresses are accepted, private and internal addresses are refused, and checks are rate-limited per visitor.
The response body is read as text and searched for the title element and for meta tags whose name attribute is keywords or description. Attribute order, quote style and the optional self-closing slash do not matter. Entities are decoded and runs of whitespace collapse to one space; tags inside a title are dropped, while a meta content value is shown as written, because that attribute is plain text.
Each row holds the value found in the source, its character count and a short comment. A title longer than 80 characters, more than 100 characters of keywords or a description longer than 200 characters is flagged — these are the tool's review ranges, not requirements published by search engines.
A row that says no tag was found means the delivered HTML really does not contain one. For keywords that is common and usually harmless: major search engines ignore the keywords meta tag, so many sites no longer write one. The title and the description are the fields that still shape a search result.
The checker reads one response body. It does not run JavaScript, follow frames or log in, so tags inserted at runtime, content that needs a session or pages that answer bots with a challenge are reported as missing or unreadable. Text in UTF-8 and common Chinese encodings is converted correctly; a page served in another legacy encoding can arrive garbled.
The address you type is sent to the VoriTools server to make the request. The fetched page is not saved and the result view keeps only what is needed to render the table; for sensitive internal pages, remember that the request comes from the public internet.