Unlike the other tools on this site, this one cannot run in your browser: it needs live search results. The URL you enter is sent to our server, which queries the search provider and returns the results. Nothing is stored.
A content analyzer fetches a page and reports how well its on-page elements are set up for search and for readers. It reads the title tag, the meta description, the heading structure, the images and their alt text, the internal and external links, and the body copy, then measures each against a published threshold and returns a score. It is the same pass an SEO would make manually on a page, done in a couple of seconds and applied consistently.
The seven checks are the ones with a defensible number behind them. A title between 30 and 60 characters is what Google renders before truncating; a meta description between 120 and 160 is the same constraint applied to the snippet. Exactly one h1 is the HTML outline rule rather than an SEO superstition. Six hundred words is the point below which a page usually cannot cover a topic well enough to satisfy the query. Alt text is an accessibility requirement first and an image-search input second. Three internal links is a floor, not a target, and it exists because orphaned pages are the single most common structural problem on a site.
Readability is scored with Flesch Reading Ease, which weighs average sentence length against average syllables per word. Sixty to seventy is plain English; below thirty is the register of a legal contract. The syllable count is a heuristic and it is wrong on individual words, but across a page of prose the aggregate is stable and useful. Alongside the score you get the ten most frequent meaningful words, with stopwords removed, which is the fastest way to see whether a page is actually about what you intended it to be about.
The limits are worth stating plainly. It reads the HTML the server returns, so a page that renders its content with JavaScript will report almost no words and fail several checks that it would pass in a browser. It follows redirects but refuses to fetch anything that resolves to a private or internal address. Pages over three megabytes are rejected rather than buffered. And a high score is not a ranking: these checks measure whether the page is set up competently, not whether it deserves to outrank anything, which depends on the content and the competition rather than on the markup.
Enter any public page address. The scheme is optional; https is assumed when you leave it off.
The page is fetched server-side and reduced to its structural facts, then measured against the seven checks.
Each check reports pass, warning or failure with the measured value, so you can see how far off it is rather than just that it is off.
Look at the ten most frequent words. If the topic you intended is not among them, the copy is about something else.
Title, description, h1, length, alt text, readability and internal linking, each with the measured value shown
Sentence length against syllables per word, reported with a plain-English difficulty band
The ten most common meaningful words with stopwords removed, so you can see what the page is really about
Internal against external link counts, resolved relative to the page rather than counted naively
Find sites in your niche that accept guest posts, using the search footprints those pages leave behind. Deduplicated by domain, with the page that matched.
Generate SEO, Open Graph, and Twitter Card meta tags for any page, with live preview and length checks
Build valid schema.org JSON-LD for Organization, Article, Product, FAQ, LocalBusiness, Breadcrumb, and more - copy the ready-to-paste script tag. 100% client-side.
Find the questions people are actually asking about a topic on Reddit in the last two months, cleaned into headings you can build an article around.
0 comments
No comments yet. Be the first to share your thoughts!