Free SEO Tool · by overrank

Free Website Metadata Checker

Enter any URL. We fetch the page server-side, parse the <head>, and give you a one-screen report of every SEO-relevant tag — what's present, what's missing, what's too long, what's too short, and exactly how to fix it.

Covers <title>, meta description, canonical, robots, viewport, Open Graph (Facebook / LinkedIn), and Twitter Card. No signup, no quota.

✦ This is 1 of 30+ things overrank automates

Want overrank to check, fix, AND write every meta tag for every article on your site?

The fixes from this tool would take hours to apply by hand. Overrank does it on every article automatically.

No credit card · takes 60 seconds

Frequently asked questions

What does this tool actually check?

We fetch your URL, parse the <head> section, and report: <title> length, meta description length, canonical URL, robots directive, mobile viewport, HTML lang attribute, Open Graph tags (og:title, og:description, og:image, og:type, og:url), and Twitter Card tags. For each one we tell you what's present, what's missing, and what to fix.

What is the ideal length for a meta description?

140-160 characters. Below 70 and you're leaving SERP real estate unused; above 160 and Google truncates with an ellipsis. Aim for 150 with the keyword in the first 100 characters.

Do Open Graph tags actually affect SEO?

Not directly — Google doesn't read OG tags for ranking. But they massively affect click-through rate on social shares (Facebook, LinkedIn, Slack previews) and rich-card SERPs on some queries. Higher CTR → more traffic → indirect ranking boost. Worth adding to every page.

Why does my page need a canonical tag?

Canonical tags prevent Google from treating multiple URL variants (https vs http, www vs non-www, with/without query params) as separate pages competing with each other. Without a canonical, page authority gets split and rankings suffer. Every indexable page should have one pointing to itself.

Does this tool store the URL I check?

We fetch the URL server-side to bypass browser CORS restrictions, parse it, return the result, and discard the input. Nothing logged, nothing stored.