Nikola Arsić
CostFreeSign-upNoneChecksRendering, meta, schema

SEO analyzer

Point it at a URL and get the technical picture: what renders server-side, what the metadata claims, and what a crawler actually comes away with.

What it does

4 capabilities

Rendering
What is in the server response versus what appears after JavaScript runs - the gap that decides whether your content gets indexed at all.
Metadata
Title, description, canonical, robots directives and OpenGraph, read as a crawler would read them rather than as you intended them.
Structured data
Whether your JSON-LD is present, parses, and says what you think it says. Broken schema fails silently, which is why it stays broken.
Headings and links
Document outline and internal linking, so you can see the structure a crawler infers instead of the one you designed.

How it runs

  1. Step 1

    Enter a public URL. The page is fetched and rendered server-side for the check.

  2. Step 2

    Read the rendering, metadata and structured-data results together - they are usually only meaningful in combination.

  3. Step 3

    Fix what it found, or send it to whoever can.

Accepted input

Works on

  • Server-rendered pages
  • Client-rendered React, Vue and Angular apps
  • Shopify, BigCommerce, PrestaShop and WooCommerce storefronts
  • WordPress

Reports on

  • Server HTML versus rendered DOM
  • Title, description, canonical and robots
  • OpenGraph and Twitter cards
  • JSON-LD validity
  • Heading outline

Nothing is uploaded. Nothing is stored.

It runs entirely in your browser, with no account and no server round-trip. Close the tab and it is gone.