Example result
Kinetiq Studio: 4 verified problems
This is the EdenLens free check, run on an invented business and published as it came out, so you can read a whole result without running one. Checked 6 October 2026; 10 of 40 criteria read from one page, robots.txt and the sitemap.
An invented business. The result is the engine's own output for its fixture page; the domain is a display name. It is not a client.
The quick check found 4 verified problems.
The 3 that matter most are below, each computed from your own site and citing the evidence it rests on.
The site is not served over HTTPS
The secure https address answers (HTTP 200) and then hands visitors to the insecure http copy of the site. Search engines and assistants store the insecure address, and browsers warn visitors. Every other finding sits behind this one.
Evidence EV-030, EV-031
Little readable content in the initial HTML (11 words)
Only 11 visible words arrive in the initial HTML, which is what a crawler that does not run JavaScript receives. That is either a page whose content loads afterwards, or simply a very short page; a one-page check cannot tell which. Either way, to those crawlers this page is effectively empty.
Evidence EV-002
No machine-readable business identity
The homepage carries no Organization or LocalBusiness node. Search and AI systems have no machine-readable statement of who this business is, where it is or how to reach it, so they must infer it from the page text or from what third parties say.
Evidence EV-032, EV-033, EV-034
Four foundations
Each one is a gate: if it fails, nothing downstream can work, however good the page is.
- Fail The site is served securely
The secure https address answers (HTTP 200) and then hands visitors to the insecure http copy of the site. Search engines and assistants store the insecure address, and browsers warn visitors. Every other finding sits behind this one.
Evidence EV-030, EV-031
- Pass Search engines can reach and index the site
The homepage answers with HTTP 200, carries no noindex directive, and robots.txt does not block Googlebot or Bingbot.
Evidence EV-001, EV-018
- Pass AI assistants are allowed to read the site
robots.txt does not block the crawlers that fetch pages for ChatGPT, Claude and Perplexity answers. This reads the published directives only; whether each provider actually reaches the site needs server logs, which a public check cannot see.
Evidence EV-005, EV-021, EV-022
- Fail Content is readable without running JavaScript
Only 11 visible words arrive in the initial HTML, which is what a crawler that does not run JavaScript receives. That is either a page whose content loads afterwards, or simply a very short page; a one-page check cannot tell which. Either way, to those crawlers this page is effectively empty.
Evidence EV-002
Who machines think this is
Fail The homepage carries no Organization or LocalBusiness node. Search and AI systems have no machine-readable statement of who this business is, where it is or how to reach it, so they must infer it from the page text or from what third parties say.
Evidence EV-032, EV-033, EV-034
Three readiness readings
Each reading is its signals counted against the number tested. There is no band, no total and no percentage; the count is the result.
SEO: 2 of 5
Can search engines find, fetch and file these pages?
- Yes the pages can be indexed
- No a sitemap lists more than the homepage
- No a canonical URL points at this site
- Yes the title says which page and which business this is
- No the description says something the title does not
Evidence EV-004, EV-011
AEO: 1 of 4
Can a clear answer be lifted from this page?
- No one clear top-level heading names the page
- No enough section headings for a machine to lift one part
- No the description offers an answer, not a greeting
- Yes facts are in text, not locked inside images
Evidence EV-036, EV-037, EV-017
GEO: 1 of 4
Can an assistant identify this business and corroborate it?
- Yes the crawlers that fetch pages for answers are allowed
- No a business node identifies the organisation
- No that node carries the facts an answer needs
- No declared profiles connect the business to where else it appears
Evidence EV-032, EV-033, EV-005
What this check could not see
- Site-wide consistency beyond the homepage
- Whether pages answer the questions customers actually ask
- Whether the business identity agrees across the registers, maps and profiles where it appears
- Whether search engines and assistants actually reach the site, which needs server logs
- Whether assistants mention or cite the business today
This free check reads one page, robots.txt and the sitemap. It reports readiness signals only and does not measure live visibility in AI answers. Anything it could not see is left unassessed, never counted as a failure.
Evidence appendix (45 facts)
| Id | Fact | Value |
|---|---|---|
| EV-001 | HTTP status of the public homepage fetch | 200 |
| EV-002 | Visible words in initial HTML (pre-JavaScript) | 11 |
| EV-003 | JSON-LD @types parsed from initial HTML | none |
| EV-004 | Canonical link declared | none |
| EV-005 | robots.txt HTTP status | 200 |
| EV-006 | XML sitemap HTTP status | 404 |
| EV-007 | Business name as discovered | Kinetiq Studio |
| EV-008 | Postal address as discovered | none |
| EV-009 | Telephone as discovered | none |
| EV-010 | Description/category as discovered | none |
| EV-011 | Page <title> text and length | Kinetiq Studio (14 chars) |
| EV-012 | Meta description present and length | no |
| EV-013 | H1 headings found on the page | no |
| EV-014 | Viewport meta tag present (mobile readiness signal) | no |
| EV-015 | Open Graph title/description present | no |
| EV-016 | Hreflang alternates declared | no |
| EV-017 | Image alt-text coverage | no <img> elements in initial HTML |
| EV-018 | noindex directive present in initial HTML | no |
| EV-019 | robots.txt names Googlebot | not named (wildcard rules apply) |
| EV-020 | robots.txt names Bingbot | not named (wildcard rules apply) |
| EV-021 | robots.txt names OAI-SearchBot | not named (wildcard rules apply) |
| EV-022 | robots.txt names ChatGPT-User | not named (wildcard rules apply) |
| EV-023 | robots.txt names ClaudeBot | not named (wildcard rules apply) |
| EV-024 | robots.txt names Claude-User | not named (wildcard rules apply) |
| EV-025 | robots.txt names PerplexityBot | not named (wildcard rules apply) |
| EV-026 | robots.txt names GPTBot | not named (wildcard rules apply) |
| EV-027 | robots.txt names Google-Extended | not named (wildcard rules apply) |
| EV-028 | robots.txt names CCBot | not named (wildcard rules apply) |
| EV-029 | Wildcard 'Disallow: /' blocking all agents | no |
| EV-030 | Homepage served over HTTPS | no |
| EV-031 | Plain http request redirects to https | no (HTTP 200) |
| EV-032 | Organization or LocalBusiness node in structured data | no |
| EV-033 | Identity fields present on the business node | no business node |
| EV-034 | Required identity fields missing from the business node | name, address, contact, url |
| EV-035 | sameAs profile links declared in structured data | no |
| EV-036 | Level-one headings in the initial HTML | no |
| EV-037 | Section headings (h2, h3) outside navigation | 0 |
| EV-038 | Meta description text | no |
| EV-039 | Email address as discovered | none |
| EV-040 | robots.txt names Claude-SearchBot | not named (wildcard rules apply) |
| EV-041 | robots.txt names Perplexity-User | not named (wildcard rules apply) |
| EV-042 | robots.txt names Applebot-Extended | not named (wildcard rules apply) |
| EV-043 | Share title (og:title) | none |
| EV-044 | Share description (og:description) | none |
| EV-045 | Share picture (og:image) | none |