Scan complete

167.233.65.119

1 page · 1.0s · Scanned just now

0/ 100

AI automation score

Mostly human-written

35% confidence

How to read this score

0–35 · Mostly human35–65 · Mixed signals65–100 · Mostly AI

The score is a fingerprint of automation, not a quality judgment. A high score means the page reads as machine-generated. It doesn't mean the page is bad.

What we scanned

Page title: ARMONIA — ΔΠΘ Εστίες
Meta description: Σύστημα Διαχείρισης Φοιτητικών Εστιών — Δημοκρίτειο Πανεπιστήμιο Θράκης
Final URL: http://167.233.65.119:3000/login(after redirect from http://167.233.65.119:3000/)
Language: el
Built with: Next.js

What we saw

This is a functional login page for a Greek university student housing system with only 38 words of text, almost entirely UI labels and legal boilerplate. The presence of a "🧪 Mock Σύνδεση (DEV)" debug button strongly suggests active human development. There is far too little content to make a reliable judgment — confidence is low by design.

Top findings

Worth notingContent
Only 38 words present — almost entirely UI labels, making AI-detection unreliable on this page
Evidence
- “🧪 Mock Σύνδεση (DEV)”body
- “Το SSO δεν έχει ενεργοποιηθεί από τον διαχειριστή.”body
Try this
Score this domain by crawling a content-rich page (e.g. homepage, about, or a student guide) for a meaningful signal.

What's working

Signals of human authorship the page is doing well.

Tone
Debug label '🧪 Mock Σύνδεση (DEV)' is a clear marker of active human development, not AI-generated copy.
Structure
Role-split login UI (students vs staff/admin) with SSO status notice reflects purpose-built, custom application logic.

SEO auditFair

71/100

AI breakdown by category

Content15
Minimal functional UI text in Greek — login labels, copyright, SSO notice — no generic LLM phrasing or filler prose
Structure20
Login page with role-split (students vs staff) and a DEV mock-login button — custom functional layout, not a template hero/features/CTA pattern
Imagery10
Single image present, alt text provided, no stock-photo grid or AI-generated imagery signals
Tone15
Terse, institutional Greek — "🧪 Mock Σύνδεση (DEV)" debug label suggests real developer authorship, not AI marketing copy

By the numbers

Words38
Images1
Alt coverage100%
Internal links0
External links0
Schema blocks0
HTML size35 KB

SEO audit detail

Meta tags
Missing canonical
Why this matters
Why it matters. Title and description are the two strings Google shows in search results. They decide whether anyone clicks. A canonical tag tells Google which URL is the source of truth when the same content lives at multiple paths.
Passing looks like. A non-empty title under 60 characters, a meta description under 160, and a self-referencing canonical link.
Fix. Add the missing tags inside the page head. Treat the title as a headline you'd want to read in a SERP, not a brand slogan.
Heading structure
No H1
Why this matters
Why it matters. Headings are how crawlers and assistive tech understand a page's outline. One H1 names the page. H2s break it into sections. Skipped levels and missing H1s confuse both.
Passing looks like. Exactly one H1, at least one H2, and no skipped levels (no H1 to H3 jumps).
Fix. Replace the missing or duplicate H1 with a single, descriptive heading. Promote section titles to H2. Demote sub-points to H3.
Mobile readiness
Responsive
Why this matters
Why it matters. Google indexes mobile-first. A page without a responsive viewport renders zoomed-out on phones, fails Core Web Vitals on touch, and loses its mobile ranking.
Passing looks like. A meta viewport tag with width=device-width and a layout that reflows under 600px.
Fix. Add a viewport meta tag set to width=device-width and initial-scale=1, then audit your largest blocks at mobile widths.
Page speed signals
1.0s · 35 KB
Why this matters
Why it matters. Page weight and response time directly feed Core Web Vitals. Slow LCP and oversized HTML hurt rankings more than people expect.
Passing looks like. First-byte under 1.5s, HTML payload under 500 KB, fewer than 30 images on the initial render.
Fix. Trim render-blocking scripts, defer non-critical CSS, and serve compressed images sized to the viewport. Move heavy components below the fold.
Schema markup
No JSON-LD
Why this matters
Why it matters. JSON-LD structured data is how you earn rich results: review stars, FAQ accordions, breadcrumbs, article cards. Skip it and Google has nothing structured to pull from when it builds your SERP card.
Passing looks like. At least one valid JSON-LD block matching schema.org types relevant to the page (Article, Product, FAQPage, Organization).
Fix. Add an application/ld+json script block describing the page. Validate with Google's Rich Results Test before deploying.
Broken links
No internal links
Why this matters
Why it matters. Broken internal links waste crawl budget, degrade UX, and signal to Google that the site isn't well-maintained. They also cap how deep crawlers reach.
Passing looks like. Every internal link in the sample returns 2xx or 3xx. No dead anchors, no stale paths.
Fix. Use the link list above to spot the broken paths. Either restore the missing pages or update the links to point at live URLs.
Image alt text
All have alt
Why this matters
Why it matters. Alt text is what screen readers read aloud, and what Google reads instead of pixels. Skip it and you lose on both fronts.
Passing looks like. Every meaningful image has a descriptive alt attribute. Decorative images can use alt="" to be skipped intentionally.
Fix. Audit images in /assets and CMS uploads. Write alts that describe what's in the image, not what it links to.

Was this report useful?

Share this scan

Every CrawlRanker scan gets a public, shareable URL. Send it to a client, post it in a thread, or benchmark a competitor.

Scan another site

Preview scan. SEO checks are live. AI scoring is in beta.