SEO Inspector

Check a page's title, meta description, social tags, headings and images. Render JavaScript to add a screenshot, speed metrics and a bot vs user comparison.

In 30 seconds

The on-page SEO checkup for any URL

Paste in a URL and the SEO inspector shows the handful of things that decide how a page looks in Google and when someone shares it:

By default it reads the raw HTML your server sends, which is fast and is what crawlers get first. Tick Render JavaScript and it loads the page in a real Chrome browser instead, then adds three things:

Reading the results

Title length

Your title is the blue headline people click in Google, and the strongest on-page clue to what the page is about. The inspector flags titles over 60 characters and under 30. Google cuts titles by pixel width rather than an exact count, but 50 to 60 characters usually shows in full.

Quick fix

Put the most important words first, so they survive if the end gets cut. Make every page’s title different.

Description length

The description doesn’t move rankings directly, but it’s often the snippet under your title, and a good one gets more clicks. Over 160 characters and it’s likely to be cut off; under 120 and you’re leaving space unused.

No Open Graph or Twitter Card tags

Without them, every app guesses what to show when your link is shared. It usually guesses wrong: the logo instead of the product photo, or a blank card.

Quick fix

Add og:title, og:description, og:image and og:url, plus twitter:card. The meta tag generator writes them for you.

Missing or multiple H1s

One H1 that names the page topic is the clearest structure. A missing H1 is usually a styled <div>; extra ones usually come from a logo or theme using heading tags for looks. The heading analyzer shows the full outline.

Images without alt text

Alt text describes an image to people who can’t see it and helps it appear in image search. Only images with no alt attribute at all are counted, so decorative images marked alt="" on purpose aren’t flagged.

When to tick Render JavaScript

React, Vue, Angular and Svelte sites often send an almost empty HTML shell and build the page in the browser. Visitors see the finished page. Crawlers start with the shell.

Google renders JavaScript, but later, in a second pass, and it can fail if a script errors or times out. Many other crawlers, including most social preview bots and a lot of AI crawlers, never render it. Run the check both ways and compare:

Watch out

Look at the screenshot first. If it shows a cookie wall, a login screen, a spinner or an error, a crawler may see the same thing, and nothing else in the report matters until that’s fixed.

Quick fix

If you can only do one thing, move the page’s main text, H1 and meta tags into the server response with server-side rendering or static generation.

A quick on-page checklist

  1. One unique, descriptive title, with the main topic near the start.
  2. A meta description that matches what the searcher wants.
  3. One visible H1 that agrees with the title.
  4. H2s for the main sections, in a sensible order.
  5. Alt text on every image that means something.
  6. A share image of about 1200 by 630 pixels.
  7. All of the above in the raw HTML, not only after JavaScript.

Quick answers

Why does Google show a different title from mine?

Google rewrites titles it thinks are too long, stuffed with keywords or a poor match for the search, often using the H1 instead. A concise title that agrees with your H1 is the best way to keep yours.

Why does Render JavaScript take longer?

Loading a page in a real browser and waiting for its scripts takes time, usually 10 to 30 seconds.

Can I check a whole site?

This checks one page at a time. A site audit runs similar checks across up to 100 pages.