MenuClose
SEO & answer-engine check
See how your site reads to search and answer engines.
Paste a public URL. Routelint returns an SEO score and a GEO score before you create an account, so you know what crawlers and answer engines can already see.
Who this is for
Builders shipping a public site who need a clear read on discoverability.
Use this check when the question is how the page presents itself—not whether an API leaks data across accounts.
Founders and marketers
Confirm title, description, and structure before a launch, without waiting on a full security review.
Teams shipping from builders
Cursor, Lovable, and v0 ship the interface. They do not write robots.txt or llms.txt. This check shows what is missing.
Editors preparing for AI answers
See whether answer engines are allowed, whether the raw HTML has sentences, and whether dates and schema are present.
What you receive
Two scores. Named rows. Evidence when you are ready.
The public result is enough to prioritize work. An account adds the tag or URL behind each row.
- SEO score
- Technical, on-page, and on-site signals that help a page read clearly to search engines.
- GEO score
- Crawler access, raw HTML text, structure, and schema plus dates for answer engines.
- Row statuses
- Pass, warn, or fail on each check. Names are public. Evidence opens after signup.
What the check covers
The signals a public page should already expose.
Each area is scored from HTML anyone can fetch. Nothing behind a login is in scope here.
01
Technical foundations
robots.txt, the XML sitemap, HTTPS, redirects, a viewport tag, and how long the page takes to answer.
02
On-page clarity
Title length, the meta description, a single h1, image alt text, and whether the page has enough words for a reader to understand the offer.
03
On-site authority
A link to About, a link to Contact, an author, and a date a person can find on the page.
04
Answer-engine access
GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and CCBot, plus a short /llms.txt map of the public site.
05
Readable without JavaScript
Sentences that are already in the HTML, so a crawler that never runs a script can still read the page.
06
Structure and dates
Headings, lists, and JSON-LD for the organization, an article, a product, or a person, with a modified date.
How it works
A short path from a URL to two scores.
The check stays on the public surface. It does not record authenticated API traffic.
01
Paste a public URL
No account is required to start. The check fetches the page anyone can already open.
02
Read the public surface
Routelint loads the page, a few same-host links, robots.txt, an XML sitemap when one is named, and llms.txt.
03
Receive two scores
SEO and GEO each return with pass, warn, and fail counts. Row names and statuses are visible immediately.
04
Open evidence after signup
The tag or URL behind a row stays on the server until you sign in. The security suites stay on the API scan product.
Questions
Before you paste a URL.
Ownership proof and the five security suites belong to the API leak scan, not this page.
- Do I need to prove I own the site?
- No. The SEO and GEO check reads public HTML only. Ownership proof is required for the API leak scan, not for this public check.
- What do I see without an account?
- The SEO score, the GEO score, and each row’s name and status. The evidence behind a row opens after you create a free account.
- Is this the same as the security scan?
- No. This check scores how a public site reads to search and answer engines. The API leak scan records calls from a running interface and replays them across identities.
Check the public site in one paste.
Scores and row names are immediate. Evidence opens with a free account.