Favicon & Web App Tag Checker

The seven summary checks inspect stored HTML for the first crawled page, plus a crawler viewport field when available. They look for favicon, Apple touch icon, manifest, theme-color, viewport, charset, and lang= patterns. The report also shows viewport, charset, and lang= pattern detection for up to 20 crawled pages.

No. It does not request icon or manifest URLs, inspect image format or dimensions, parse manifest JSON, test a service worker, or reproduce browser installation. Use the separate Favicon Checker for bounded URL response probes, then use browser and PWA developer tools for functional validation.

No. A manifest is relevant when you offer an installable web app, while theme-color is an optional hint that supporting browsers may use for surrounding interface. Their absence should not be treated as a defect on every content or business website.

A viewport declaration helps responsive pages control the mobile layout viewport. A character-encoding declaration helps browsers decode the document consistently. This checker detects selected stored-HTML patterns but does not test responsive layout or inspect the HTTP Content-Type header.

An initial guest scan is available without signing up. Enter a public URL to review the first-page declarations and selected per-page patterns in the completed crawl.

No. It detects whether the first page contains a rel='apple-touch-icon' link. It does not fetch the file, validate its dimensions or format, or determine which Apple device would select it. Add one when Home Screen bookmarks matter, then test the supported devices.

A valid lang value on the html element helps assistive technology choose appropriate language and pronunciation rules and supports WCAG 3.1.1. Google says it uses visible content, not the HTML lang attribute, to determine page language. This checker only finds a lang= pattern; confirm that it is on html and contains the correct language tag.