브라우저 내부 처리
Inspect title, description, OG, and canonical tags from a URL or pasted HTML.
Recalculated as you type — no button to press.
The "60 characters" rule assumes Latin text. Google truncates titles at roughly 600px on desktop and 480px on mobile, and one Korean glyph measures about 17px at Arial 20px against about 10px for a lowercase Latin letter.
Pure-Korean titles fill the desktop width at roughly 34 characters and mobile at about 27. Applying the Latin 60-character rule to Korean overshoots by nearly double. This tool measures actual pixel width and shows where each view truncates.
Overflowing the width gets an ellipsis, but Google rewriting your title entirely is a different decision — triggered by titles that mismatch the content, keyword stuffing, or repeated site names. Passing the width check does not guarantee your title appears verbatim.
Google has never published official limits; 600px/480px are observed values. Korean has no Arial glyphs, so the substituted font varies by environment. If a title sits right at the boundary, leave a few pixels of margin.
No. It runs in the browser, so many third-party pages will block direct fetches with CORS. That is why the pasted HTML route is built in.
No. This page is for rapid diagnosis and prioritization. Real SEO still depends on the body content, search intent, internal linking, and trust signals.
The UTM Generator, URL Query Builder, and API Request Tester often help when you need to trace campaign links or reproduce response markup.
Search performance still depends far more on content quality and search intent, but empty titles, missing descriptions, broken canonicals, and weak sharing tags are baseline problems you should catch immediately. This tool is tuned for that first pass.
Check title, description, H1, canonical, and robots together before you spend time on deeper SEO questions.
Missing OG title and description tags often hurt link previews even when the page is otherwise fine for search.
JSON-LD is not always required, but this page helps you see quickly whether it exists on pages that might benefit from it.
If the page is same-origin or explicitly allows CORS, a direct URL check is the fastest path.
Many external sites block browser fetches. In that case, paste the raw source into the HTML field instead of fighting CORS.
Missing tags, weak title and description lengths, and accidental noindex directives are easier wins than abstract SEO theory.
SEO is not a one-time score. It is an ongoing fit between search intent and page quality. Still, these are the baseline items worth checking before a new page is published.
Each page should have a unique title that puts the search intent and page purpose near the front.
The description helps users decide whether to click. It should explain the page value clearly and specifically.
If duplicate or variant URLs can exist, pick a representative canonical URL to reduce mixed signals.
An accidental noindex tag can keep an otherwise useful page out of search results.
Search is not the only preview surface. Check how links appear in social, chat, and community posts.
FAQ, HowTo, and WebApplication schema can help search engines understand clearly structured pages.
The utility matters, but search engines and ad review also need to see that the page explains a real problem well. Examples, FAQs, and related guides help.
Putting “JSON formatter” or “UUID generator” in a title is not enough. The body should naturally explain use cases, failure modes, and next steps.
After an SEO check, users often need UTM links, query strings, or API response checks. Good internal links make that path obvious.
