SEO report for
https://liinx.vercel.app/
Overall grade
A
Category breakdown
How ready is this site for AI answers?
We found 2 GEO and 2 AEO issues affecting whether ChatGPT, Perplexity & Google AI Overviews cite this site.
See your AEO & GEO scores and how to fix each issue.
Your action plan
We found 0 critical issues and 4 improvement opportunities.
Unlock your full action plan
Create a free SeoJama account to see every prioritized recommendation, save this site, and track your score over time.
Create your free SEO accountAlready have an account? Log in
All checks
Content & Meta
-
Pass
Title tag
Title is well-sized (45 characters).
-
Pass
Meta description
Meta description is well-sized (97 characters).
-
Pass
H1 heading
Exactly one <h1> heading is present.
-
Improve
Heading structure
Heading levels are skipped (e.g. an H2 is followed by an H4). This weakens the content outline.
-
Pass
Content depth
The page has roughly 1201 words of content.
-
Pass
Image alt text
All 25 images have descriptive alt text.
Technical SEO
-
Pass
HTTP status
The page returns a healthy 200 OK response.
-
Pass
HTTPS / SSL
The page is served securely over HTTPS.
-
Pass
Mobile viewport
A responsive viewport meta tag is present.
-
Pass
Robots meta tag
The page is not blocked by a robots meta directive.
-
Pass
Canonical URL
A canonical URL is declared.
-
Pass
Structured data
Found 1 JSON-LD structured-data block(s), which helps machines understand the page and can unlock rich results.
-
Improve
XML sitemap
No XML sitemap was found. Sitemaps help search engines discover all of your pages.
-
Improve
robots.txt
No robots.txt was found. It helps crawlers understand which URLs they may fetch.
-
Pass
Language declaration
The document language is declared as "en".
-
Pass
Character encoding
A character encoding is declared.
-
Pass
Favicon
A favicon is declared.
Social Sharing
-
Pass
Open Graph tags
Open Graph title, description, and image are all set for rich social previews.
-
Pass
Twitter Card
A Twitter Card is configured (summary_large_image).
Performance
-
Pass
Server response time
The server responded quickly (430 ms).
-
Improve
HTML page weight
The HTML document is fairly heavy (187 KB), which slows first render.
-
Pass
Resource requests
The page references 28 sub-resources — a reasonable count.