Developer SEO Utility

SEO Head Checker

Paste HTML head code to check title, description, canonical, robots, Open Graph, and Twitter Card tags in one place.

Basic SEO tag check Check whether title, meta description, and canonical URL exist and are in a recommended state.
Social sharing tag check Check missing Open Graph and Twitter Card tags to improve shared preview quality.
Improvement report Review missing tags, length issues, noindex settings, and items that need fixes.

HTML Head Input

Paste the <head> section code of the HTML you want to check.

Basic meta check Prioritize title, description, canonical, and robots tags that are important for search results.
Share preview check Check og:title, og:description, and og:image tags used by KakaoTalk, social media, and messengers.
Title 0 chars Description 0 chars Meta tags 0 items Waiting to check
SEO Head score 0 pts

Enter head code and run the check.

0%

Check result

Review important SEO tags by good, warning, and error status.

Ready
No check result yet.

Detailed report

Copy or download the check result as an SEO fix checklist.

Enter HTML head code and click the SEO Head check button.

SEO Head check items

Review key tags that affect search visibility and social sharing quality.

Basic search tags

title, description, canonical, and robots relate to search result title, description, representative URL, and indexing behavior.

Open Graph tags

og:title, og:description, og:image, and og:url are used for KakaoTalk and social sharing card previews.

Twitter Card tags

twitter:card, twitter:title, twitter:description, and twitter:image improve X/Twitter share preview quality.

Practical guide

Reading an SEO head report as a checklist, not a ranking score

Inspect pasted head code for missing or duplicate metadata and basic URL issues. The percentage is a win-j checklist score, not a Google score or a prediction of indexing.

Who this helps

  • Developers checking rendered HTML
  • Editors investigating search or sharing tags

When to use this tool

  • Find duplicated title, description or canonical tags.
  • Review robots and optional OG/Twitter fields together.

From input to a checked result

  1. 1

    Copy the final head HTML rather than an unrendered template.

  2. 2

    Paste up to 500,000 characters.

  3. 3

    Choose whether to include length, Open Graph and Twitter checks.

  4. 4

    Run the inspection and address specific messages before the score.

  5. 5

    Run it again after editing, then copy or download the new report.

  6. 6

    Check live HTTP responses and indexing separately.

Example 1

Duplicate canonical tags

Input
<link rel="canonical" href="https://example.com/a/"><link rel="canonical" href="https://example.com/b/">
Result
A duplicate core-tag error

Fix the final template rather than trying to improve the percentage alone.

Example 2

Explicit noindex

Input
<meta name="robots" content="noindex,follow">
Result
A noindex warning/error in the report

It may be intentional for a private or excluded page. Decide based on that page's publication policy.

How it works

DOMParser reads head metadata and detects duplicate title, description and canonical tags. Optional internal length bands are 15–65 for titles and 50–160 for descriptions. URL checks include HTTP(S), credentials and a 2,048-character limit. Scores summarize selected checks.

Limitations

  • It does not crawl the site, execute its scripts or inspect HTTP X-Robots-Tag headers.
  • The robots check reads the first robots meta value; review additional robots and crawler-specific directives yourself.
  • Content quality, structured data, internal links and performance are outside this report.
Your data

The supplied head is parsed locally and is not saved to win-j. Remove confidential values from copied source.

Related tools

Frequently asked questions

Does a high score guarantee search visibility?

No. It only summarizes the selected local checks.

Is a missing robots meta always an error?

No. A page can be indexable without an explicit index,follow meta tag.

Why does this use different length bands from the title checker?

These are separate internal heuristics, not search-engine rules. Use clarity and page relevance to decide the final wording.