SEO Score Checker: Read Eight Lights, Not a Google 100

By William Zhu · Cofounder, InfiniSynapse · Published: 2026-09-08 · Last updated: 2026-09-14 · Last verified: 2026-09-14 · Reviewed by the InfiniSynapse Data Team.

Reviewed by: InfiniSynapse Data Team · method review 2026-09-14. First-party CLI review of five public URLs, with nextjs.org used as the package-window example.

Trust / COI: About · Corrections. InfiniSynapse sells SEO Health. The nextjs.org row is a desk observation of infinitegrowth@0.1.1, not a customer win and not a Search certificate.

TL;DR

An seo score checker on this stack returns eight traffic lights — title, meta, headings, density, images, links, tech, and speed. It is not a Google 100. People who type the query often want a trophy number. The product refuses that number.

Direct answer: Use an seo score checker to inspect one live HTML response. Green means that module did not fail the shipped rule. A warning on title length is a package window, not a ranking verdict.

A score-board desk pass on 2026-09-14 called npx --yes -p infinitegrowth@0.1.1 seo-health check five times, once per public URL, and kept each JSON. The sample size is five URLs. Five dated boards do not prove a category trend and cannot establish a ranking outcome.

What an seo score checker actually returns

Key definition: An seo score checker is a one-URL pass over live HTML that scores eight deterministic modules with red, amber, or green. It does not invent an official Google page score, and it does not crawl the rest of the host.

Independent citation: According to [web page](https://en.wikipedia.org/wiki/Web_page), a web page is a discrete document a browser can fetch and render. Wikipedia supplies that public definition. The CLI table below is first-party output, not Wikipedia’s rule.

People search seo score checker when they want a single grade they can screenshot. Suites trained that habit. This page exists to break it. The useful output is a punch list, not a 100.

A web page is one document. An seo score checker inspects that document and then stops. It does not grade the brand, the backlink graph, or last month’s impressions.

An seo score checker will not stamp “ready for EEAT,” forecast clicks, or stand in for a Search Console export. Those jobs start only when you ask for them.

If you still want the older one-page diagnosis vocabulary, continue on the on-page SEO checker. Keep the first run on all eight modules.

Lights are named rows

The product on infinitegrowth.agency scores title, meta, headings, density, images, links, tech, and speed. Each module gets a traffic light. That board is the entire promise of an seo score checker on this host.

A green title does not win the click. A green speed light is not an official Core Web Vitals certificate. A green tech light does not mean the URL is indexed. Green means this module did not fail the shipped rule.

If someone only wants the color legend after this pass, open SEO health check traffic lights. Stay here when the search was for a number and the honest answer is lights.

Why a composite 100 hides ownership

A composite 100 blends modules so a missing H1 can hide behind a fast paint. An seo score checker that refuses the blend forces you to name the broken row. Archive the rows instead of a homemade average.

Two people who paste the same public URL should see the same lights. That repeatability is the point. A vendor 100 often moves when the vendor changes weights. Lights stay assignable.

Do not retarget a host-wide vanity grade from this page. The job is one URL and eight rows.

Eight modules without a composite

Read an seo score checker as a board, not as a trophy. Start at red, then amber, then green. Fix the module that blocks understanding before you polish density.

The MariaDB documentation treats structured records as named fields you can inspect one at a time. Read the eight lights the same way: as columns, not as a blended grade.

Title, meta, and headings

Title and meta tell a result page what the URL claims. Headings tell a reader and a parser the same story. If any of the three is empty, duplicated, or off the visible H1, the board should go red or amber before you debate nuance.

A missing H1 is a heading failure. Five H1s are a heading failure. A title that hides the page topic is a title failure. Those rows are assignable. An seo score checker that prints them as a 100 has already blended the board.

Google's title-link documentation is the independent reminder that a title is a document property a result page may rewrite. Snippet guidance is the matching reminder for descriptions. Neither document printed the CLI numbers below.

Density, images, and links

Density flags stuffing and thin copy. It is a heuristic, not a legal limit. Images flag missing alt text. Links flag empty hrefs the checker can already see.

W3C WCAG 2.1 describes success criteria you query by statement, not a single trophy metric. The W3C alternatives tutorial treats text alternatives as perceivable content. An amber image row is a repair list for people and parsers, not a ranking deduction.

A green density light does not prove the page is helpful. It only says the copy is not a keyword pile or an empty shell. An seo score checker that stops at density is already late.

Tech and speed stay separate

Tech looks at robots directives, canonical hints, HTTPS, and other signals the module is built to read. Speed is a coarse load signal, not a lab Core Web Vitals certificate.

Lighthouse scoring documentation explains how a lab tool weights delivery metrics. This seo score checker does not reprint that lab certificate. If tech is red because the URL looks unindexable, stop polishing adjectives on an seo score checker ticket.

MDN's heading reference is the independent reminder that heading rank is markup, not a score. Keep heading repairs on the heading row.

Why one paste is not a host grade

A one-URL seo score checker answers what is wrong on this page. A sampled site audit answers what is wrong on a slice of the host. Mixing them wastes a week.

Use the paste when you changed a title or a hero. Use a sample when the same template ships across dozens of URLs. The sample hub is SEO website audit: 50–500 sitemap pages. Five single-URL boards still do not find a 404 that exists only on URL 187. The SEO health check vs site audit page is the prevalence job. For the paste sequence, open how to run an SEO health check. For the product home, continue on the one-URL lights hub.

Score products that still print a 100

Suites sell a 100. Extensions sell a badge. An seo score checker that only promises eight lights is easier to defend because it promises less. The Supabase documentation separates project setup from later paid add-ons; free lights do not include a credited EEAT memo. The ClickHouse documentation is built around explicit queries against named columns, not a dashboard glory number.

Browser, CLI, and Chrome share one board. Do not paste cookies, preview tokens, or admin URLs.

nextjs.org as a package-window observation

This is a first-party desk observation with infinitegrowth@0.1.1. Two of the five hosts are InfiniSynapse pages and are marked first-party. nextjs.org and nuxt.com are third-party public homepages. The Nuxt homepage board is filed on nuxt seo. An seo score checker that hid those labels would be selling a third-party grade as first-party proof.

The nextjs.org board is the clearest anti-100 lesson on this page. Title length was 39 characters (warning; package window 40–60). Description length was 64 characters (warning; package window 120–160). Those two rows failed this package’s windows. They are checker rules, not Google ranking rules. An seo score checker that averaged them into 73 or 81 would hide both owners.

npx --yes -p infinitegrowth@0.1.1 seo-health check \
  https://nextjs.org/ --format json --lang en

Parsing rule: completion means valid JSON containing url, page, issues, images, and speed. Exit code 0 means the request completed. It does not mean every module is green. The observed contract on this package is that seo-health check --format json can exit 0 while issues[].status is warning.

On this seo score checker, SEO Health computes the eight traffic lights from the submitted page; the free rule engine is not powered by InfiniSynapse. The API-backed foundation begins only when a user requests a credited deep EEAT or visibility analysis: an InfiniSynapse Server API long task can reuse that captured evidence, stream progress over SSE into its workspace, and return interpretation without inventing a 100.

Figure: Two series from the same five CLI JSON files. Page-issue warnings are not speed warnings. Neither series is a Google 100.

Title 39 and description 64 are windows, not ranks

The title string was Next.js by Vercel - The React Framework. The description was Next.js by Vercel is the full-stack React framework for the web. Both strings exist. Both sat under this package’s character windows. That is a length finding, not a proof that the homepage will lose impressions. The nextjs seo page keeps the framework follow-up. This seo score checker page keeps the anti-100 reading: a failed window is still a named row.

H1, URL, robots, sitemap, image alt, and page structure were good on that same fetch. All 65 images had alt attributes. A blended 100 would have mixed those greens with the two metadata warnings and the speed-family errors (blockingScripts 14, totalRequests 115, htmlSize 378.3 KB).

Speed family is a different ledger

Speed score on nextjs.org was 63. Speed errors and warnings sat in a different object than page-issue warnings. Combining those denominators would create a number the seo score checker command never returned.

Network timing can move while title and description lengths stay stable. Compare named fields. Keep package version, URL, language flag, and retrieval date beside the table.

How to refuse a blended number

The hub’s job is to explain the whole instrument. This seo score checker page’s job is to stop someone from printing a 100 after they saw eight lights.

Name the field, not the total

Recruiting a vanity number is a meeting habit. Naming the field is the repair. Title owns the 39-character string. Meta owns the 64-character string. Delivery owns blocking scripts. Do not average status labels or add the speed score to page checks. Readers who need the paste sequence should use how to run an SEO health check. An seo score checker write-up that reprints a homemade average has already failed its job.

Re-run the same public URL

After a ship, paste the same URL again. Compare lights by module. A second seo score checker run should therefore be compared by row, not by an invented total.

Independent citation 2: According to [WCAG 2.1](https://www.w3.org/TR/WCAG21), WCAG 2.1 is the W3C recommendation for web content accessibility. A second independent source, from W3C, keeps this page claim from resting only on first-party lights.

Selection scorecard

Score each row 0–2 when the meeting asks for a number. A row at 0 means pick a different job.

Under 6 means pick another instrument. 8–10 means paste the URL. Keep the seo score checker on one page and one board, not a host-wide vanity grade.

Failure modes that invent a trophy

The first failure is pasting a URL nobody can open. Signed links, basic-auth admin, and localhost are not a public seo score checker input. The second is treating green as a rank promise. The third is paying for interpretation before naming who owns title, description, and alt. The fourth is checking a draft and shipping a different URL — re-run the seo score checker on the sitemap canonical. The fifth is arguing for a 100 because a competitor tool printed one. Five homepage fetches still cannot establish that Google agrees with any of those lights.

Cluster guides beside this page

Pick the next guide by what the rejected composite was hiding.

Frequently Asked Questions

Is this an official Google score?

No. An seo score checker on this stack is a first-party rule board with eight traffic lights. Google does not issue nextjs.org, or any other URL in the five-URL table, a universal SEO 100.

Do I need an account for the eight lights?

No. The free paste at infinitegrowth.agency does not require a login. Chrome can finish basic modules locally. An seo score checker board needs no account; only a separately chosen model explanation opens the credit ledger.

Will a higher number change the crawl?

There is no higher number to chase. Changing a vanity 100 does not change how a crawler fetches the URL. Fix the red or amber module the seo score checker named, then re-run the same public URL.

Can I run the same pass from a terminal?

Yes. npx --yes -p infinitegrowth@0.1.1 seo-health check against a public URL repeats the seo score checker board. Deep EEAT, visibility, or GSC commands still need a key and credits.

Does a short title mean the page will drop?

No. Title 39 on nextjs.org failed this package’s 40–60 window. That warning is a length finding. Five dated seo score checker boards cannot establish a ranking change from that length.

Conclusion

An seo score checker is eight lights on one public URL. The 2026-09-14 snapshot shows five boards and one third-party homepage whose title sat at 39 characters and whose description sat at 64. Those lengths failed the package window. They still are not a rank. Paste, wait, fix the named row, re-run.

Keep the board in SEO Health. If the team wants prose after fixing the named rows, it can open the InfiniSynapse web app once; the app does not manufacture a replacement seo score checker total. Until then, the next useful click is the URL you are about to ship.