SEO check
The SEO check reads your page the way a search engine first sees it and scores what decides whether it can be crawled, indexed and shown well.
Use it before a launch, after a redesign, or when a page you expected to rank doesn't appear.
Every finding comes with the fix, and Weekly Unpack subscribers get a prompt that hands the whole list to their coding agent.
Built by the IndieHacked team
Enter an address and run the check. The score and what to fix show here.
How the check works
What it reads
The check fetches your page the way a search engine's first pass does, without running JavaScript, along with /robots.txt and your sitemap. It scores four topics out of 100 and averages them. A rule that passes counts in full, one to improve counts half, and a problem counts nothing.
Crawling and indexing
The page should answer 200 over HTTPS, robots.txt should let Googlebot reach it, and nothing should say noindex. A robots.txt that answers with a server error counts as a full block, as RFC 9309 sets out. The canonical link should be the page's own absolute address, and a sitemap should list your pages, named in robots.txt or at /sitemap.xml.
Page basics
A title of its own, a meta description, an h1, a mobile viewport, a lang attribute and alt text on images. Google says heading order doesn't affect ranking; Bing asks for a clear hierarchy, so a missing h1 counts as one to improve. Google doesn't use the lang attribute, so it weighs least.
Share cards and structured data
The Open Graph protocol requires og:title, og:type, og:image and og:url, and expects og:image:alt beside an image. Structured data should parse as JSON-LD and name what the page is, with an Organization on the home page. Google's guidelines ask that it match the page's visible content.
What it leaves out
Speed, backlinks and rankings. Those need a browser run or data from Google itself: PageSpeed Insights and Search Console are where to read them.
Questions founders ask
Why doesn't the check measure page speed?
Speed needs a real browser loading the page several times, and Google already measures it for you in PageSpeed Insights and Search Console. The check sticks to what the HTML and your site files show.
My score went up but I don't rank higher. Why?
The check tells you whether search engines can crawl, read and present your page. Ranking also depends on what the page says, who links to it and what else answers the same search. A clean score removes the technical reasons not to rank.
What does the fix prompt do?
It turns the findings into instructions for your coding agent (Claude Code, Cursor, Codex, Lovable or Bolt), written for what your site is built with when the check can tell. Paste it in, review the changes, then run the check again. Fix prompts are part of Plus, free with Weekly Unpack: subscribe with your account's address and every prompt opens.
Why do I need an account to run a check?
Each check reads a live site and asks Claude to write the verdict, which costs money every time. An account lets us keep it free with a daily limit of 10 checks, and keeps your past runs so you can compare a new score with the last one.
What happens to the address and the results?
We store the address, the score, the findings and the verdict with your account so you can see them again. The page's text goes to Anthropic, which runs Claude, to write the verdict and the prompt; the copy check also sends the address to Firecrawl to read the page as a visitor sees it. Runs are deleted after 12 months, or with your account.
Report an error. Spotted a factual or language mistake? .