Understand title, H1, content, and metadata checks
Learn how TechDash monitors content quality, changes, and cross-page duplication.
Last checked 21 August 2026
TechDash monitors rendered titles, H1s, visible text, and meta descriptions. Some results compare a page with its baseline; others compare the complete Monitored Page set. A pass can mean present, unchanged, unique within that set, absent without an incident, or baseline stored. It does not certify relevance, usefulness, or SEO quality.
Title presence and change
Empty title tag is Warning because missing titles weaken page identification and snippet control. It is an absolute-state check and fails whenever the rendered title is missing or whitespace-only, including on the first observation. It passes when any non-empty title exists. Evidence states that a non-empty title was expected and that the current title is empty; it does not judge uniqueness, relevance, or likely truncation.
Title tag cohort change is Advisory despite its name: the current check compares each page independently. After a baseline, it fails when a previously non-empty title differs from the current title, including removal. A pass means unchanged, or baseline stored when no prior non-empty value exists. The previous and current title are evidence, but a changed title can be an approved editorial improvement.
Title tag too short and Title tag too long are informational product documentation opportunities for roughly under 15 and over 70 characters. The current check does not emit them as incidents. Their absence is not proof of an effective title.
Restore a missing or accidental template title, or confirm an intentional rewrite against page intent and expected snippets. Run Check & Verify. Recovery means a non-empty title and no unaccepted change, not that search engines will use that title.
H1 change
H1 cohort change is Advisory and also runs per page. It fails when a previously non-empty extracted H1 differs from the current H1. It passes when unchanged or when the first non-empty baseline is stored. Evidence is the prior and current first extracted H1. It does not count all headings or judge hierarchy, uniqueness, visibility, or topical fit.
CMS edits, localization, and planned redesigns can be benign. Restore accidental heading changes and verify the rendered mobile page. Check & Verify recovers when the H1 matches the accepted baseline or an intentional new baseline is accepted.
Cross-page duplicates
Duplicate titles across monitored pages and Duplicate H1s across monitored pages are Warning. After all enabled monitored pages for the website have current results, TechDash normalizes non-empty values, groups matches, and fails when two or more Monitored Pages share a title or H1. They can fail on the first complete set. A pass means no duplicate non-empty values among monitored HTML pages; empty values are handled elsewhere or ignored.
Evidence lists each normalized duplicate cluster and colliding path. The graph is limited to Monitored Pages, so a pass does not prove site-wide uniqueness. Shared headings on deliberate variants, legal pages, or paginated pages can be benign, but should match their search intent and canonical strategy.
Give distinct pages specific titles and headings or confirm that the URLs are intentional equivalents. Recovery requires all enabled pages to have current snapshots and finalization to find no duplicate cluster.
Visible content
Main content disappeared or thinned is Warning. It fails only when the prior rendered extraction had at least 80 words and the current count is below 35% of that baseline. A pass means the threshold was not crossed, including pages that started thin. Evidence is previous and current visible word counts. It does not assess accuracy, originality, location in the main content, or search intent.
Body content changed is Advisory by default and may be raised to Warning when the page has a custom check. It fingerprints extracted displayed text and fails when a previously non-empty fingerprint changes. Evidence uses up to 500 characters of previous and current body text, with the fingerprint as fallback. Highlighted stored HTML can add context, but rotating promotions, stock, dates, consent, personalization, and tests can create benign changes. A pass means unchanged or baseline stored, not high-quality content.
For collapse, restore substantive rendered copy or fix the template. For change, identify the responsible release or CMS edit and accept it only if intentional. Check & Verify must show restored word count or a stable accepted fingerprint.
Meta description tracking
Meta description tracking has no alert and always passes after storing the current extracted description. Missing, changed, or poor descriptions do not fail. The value supports change intelligence only and does not predict the snippet Google will choose.
Use a custom check when a known pattern is mandatory. Review descriptions editorially and in rendered HTML, then verify the custom rule if used; there is no automatic meta-description recovery incident.