GEO/AEO readiness

neetalulla.com

Checked 18 September 2026

91
out of 100

Fix these first

Ranked by how much each one affects whether an assistant can use your site.

  1. 01
    Returns or refunds page
    HTTP 404

    Assistants are asked what happens if it does not fit, when it arrives and who to contact. Without a page to read they answer about someone else.

Machine access10%
100
Server-rendered content12%
90
Product & offer data30%
99
Entity & structured data22%
89
Answer-readiness6%
81
Identity & trust8%
97
Merchant facts & policies10%
70
AI-surface hygiene2%
88

Page by page

30 pages checked

Sampled from your sitemap. Assistants rarely land on a homepage - inner pages are what get retrieved and quoted, so these are scored individually.

Weakest pages first.

Machine access

100/100
Homepage responds
HTTP 200
Served over HTTPS
Secure
HTTP redirects to HTTPS
Redirect in place
robots.txt found
HTTP 200
AI crawlers allowed
None of the major AI crawlers are blocked
Page is indexable
No noindex directive
XML sitemap available
Declared in robots.txt
Server response time
486 ms

Server-rendered content

90/100
Content present without JavaScript
1730 words in the raw HTML
Not a JavaScript-only shell
Server-rendered markup found
Text-to-markup ratio
3%
Very little of the payload is readable content.
Headings in raw HTML
15 headings
Links crawlable without JavaScript
168 links in the HTML

Product & offer data

99/100
Product markup
Product found in structured data
Offer attached
Product carries an offer
Price in markup
INR 79500.0
Availability stated
InStock
Price in served HTML
Found without running JavaScript
Product identifier
sku, mpn
Brand stated
Brand present
Product description
428 characters

Entity & structured data

89/100
Structured data present
5 valid JSON-LD block(s)
Organization identified
Organization or LocalBusiness node found
Entity corroboration (sameAs)
17 profiles linked
Stable @id references
@id in use
WebSite node
Present
Breadcrumb markup
Not found
Breadcrumbs give machines your site hierarchy.
FAQ markup
Not found
FAQ markup is a clean way to answer the questions buyers actually ask.

Answer-readiness

81/100
Exactly one H1
1 found
Question-shaped headings
1 found
Headings phrased as questions match how people prompt assistants.
Readable paragraphs
47 paragraphs, ~34 words each
Lists or tables present
19 found
Content dates exposed
No dates found
Assistants prefer content they can confirm is current.
Authorship stated
Author or publisher declared

Identity & trust

97/100
Title tag
63 characters - will truncate
Meta description
168 characters
Canonical URL
https://www.neetalulla.com/
Open Graph tags
Title, description and image present
Language declared
html lang set
Contact details discoverable
Phone or address found

Merchant facts & policies

70/100
Returns or refunds page
HTTP 404
Assistants are asked what happens if it does not fit, when it arrives and who to contact. Without a page to read they answer about someone else.
Shipping or delivery page
Published
Contact details page
Published
Business registration
No GSTIN or CIN found
A registration number is verifiable against a public register, which is the difference between a claim and a fact.
Public product feed
30 products readable

AI-surface hygiene

88/100
llms.txt present
Found
Compression enabled
br
Image alt text
61% of 83 images
Alt text is the only description a machine gets of an image.
Favicon declared
Present

What this score is not

This measures technical readiness - whether assistants can reach, read and quote your site. It does not measure whether ChatGPT, Gemini or Perplexity currently name your brand. That takes a prompt set run across each assistant with the answers recorded over time, and it is the natural next step once the foundations here are in place.

Talk through these results

Ready to become the answer?

Let's build a search strategy that wins across Google, ChatGPT, Gemini, Claude, AI Overviews, and every platform shaping the future of discovery.