Audit titles, meta descriptions, Open Graph and Twitter cards across up to 25 URLs in one paste. Spot duplicates and missing tags fast.
SEO at scale is a meta-tag problem before it is a content problem. Duplicate titles cannibalise rankings. Missing descriptions kill click-through. Half-finished Open Graph tags turn social shares into ugly link-only cards. Bulk meta-tag analysis surfaces all of that in one table.
## What this tool does
Paste up to 25 URLs — your top traffic pages, your catalogue PDPs, your blog posts. We fetch each one, parse the HTML head, and extract every tag that matters for SEO and social. The result is a table you can sort, scan for duplicates, and export to CSV for a content audit.
## Common patterns this catches
Two product pages with identical titles. A blog post with the default 'Untitled' meta description. Pages with og:title but no og:image. Canonical tags pointing at the wrong URL (or at the homepage — a classic SEO killer). All of it in one paste instead of 25 single-page audits.
Missing or duplicate titles are the most common SEO bug at scale. Across a catalogue, blog, or multi-tenant SaaS, manual auditing misses dozens per portfolio.
We GET each URL with a normal browser User-Agent, follow up to 5 redirects, and parse only the document <head> using a lightweight HTML parser. We extract <title>, <meta name="description">, all og:* properties, all twitter:* properties, and <link rel="canonical">. Length counts are character counts (not pixel widths) for portability — pixel widths vary by SERP rendering. We do NOT execute JavaScript: if your title is set client-side (via React Helmet without SSR/prerender), you may see an empty title here — that is a real SEO problem worth fixing.
Most search-engine crawlers (and our checker) read the initial HTML. If your title only appears after JS runs, fix that with SSR or prerendering — search engines do not always wait for JS.
Under 60 characters keeps you safe from SERP truncation. Under 50 is comfortable.
120–160 characters. Under 70 is too short to be useful; over 160 truncates.
No — use the single-URL Schema Markup Checker (or wait for the upcoming bulk version) for that.
No — only publicly accessible URLs.
We fetch the page either way and report noindex as a row warning so you know which pages are intentionally hidden.