Indinoor — AI Search / Answer-Engine Optimization (AEO) Audit

Generated 2026-08-24. Domain: https://indinoor.in (Shopify D2C fashion-jewellery brand, sub-brand of House of Isharya). Business context: see business-analysis.md.


Executive Summary

Indinoor is in an unusually strong starting position for AI search — far ahead of most D2C brands its age. It is one of the few Shopify stores that has already deployed the full agentic-commerce stack: live llms.txt, agents.md, a Universal Commerce Protocol (.well-known/ucp) discovery endpoint, a working UCP MCP endpoint, and an agentic-discovery sitemap. It publishes 56 well-structured blog posts (kundan, temple, jadau, polki, festival guides) — the single most-citable content type for AI engines. Product pages carry Product + Offer schema with price and availability.

The gap is not accessibility or content — it is entity richness, structured-data completeness, and third-party presence.

Concrete findings (all verified against live raw HTML / API responses, not inferred):

  1. Branded queries = owned by Indinoor. "indinoor jewellery," "Shanaya Kapoor Indinoor," "indinoor vs voylla," and "indinoor review" all return indinoor.in at or near position 1. AI engines answering these will cite Indinoor.
  2. Category / discovery queries = lost to third parties. "best fashion jewellery brands india," "what is kundan jewellery," and competitor-comparison roundups surface Voylla, GIVA, Rubans, Nuyug, and blog/affiliate sites — not Indinoor, even though Indinoor has a better kundan article than several that rank. This is the classic "brands are 6.5x more likely to be cited via third-party sources" problem, compounded by thin entity signals.
  3. Organization schema has an EMPTY sameAs array (nine blank strings). Google/Claude/Gemini cannot tie Indinoor to its Instagram (94K), Facebook, Shanaya Kapoor, or House of Isharya — so entity recognition is weak and knowledge-graph confidence is low.
  4. No FAQPage schema despite FAQ sections on blog posts (e.g. the Kundan article ends with "Frequently Asked Questions"). Direct Q&A extraction is being left on the table.
  5. No BreadcrumbList, AggregateRating, or Review schema on product pages — AI sees products as "unreviewed" and loses category hierarchy.
  6. /pricing.md returns 404 — AI buying-agents evaluating Indinoor programmatically get no machine-readable price sheet (the UCP endpoint covers transactional pricing, but a static /pricing.md helps non-transactional agents and Perplexity-style summarizers).
  7. Under-linked social presence — the About page and schema don't connect to the brand's real social graph, weakening entity signals.

Net: Indinoor already "shows up" for AI answers on its own name. The upside is in (a) entity/schema hardening so it gets cited for category and comparison queries, and (b) seeding third-party surfaces (Wikipedia, Reddit, roundups) so it enters AI answers where it currently does not.


1. AI Bot Access Check (robots.txt)

Result: PASS — no AI crawlers blocked.

Verified the live robots.txt. There are no Disallow rules targeting GPTBot, ChatGPT-User, PerplexityBot, ClaudeBot, anthropic-ai, Google-Extended, or Bingbot. The file explicitly welcomes agents:

# Agent instructions: https://indinoor.in/agents.md
# UCP discovery: https://indinoor.in/.well-known/ucp
# UCP/MCP endpoint: https://indinoor.in/api/ucp/mcp

Only transactional/private paths are disallowed (/admin, /cart/, /checkout, /orders, /account, /services, /sf_*). This is correct — AI search-and-cite bots are fully permitted.

Notes:

  • The store is also opted into Shopify's agentic-discovery sitemap (/sitemap_agentic_discovery.xml → lists agents.md), signaling to agentic crawlers.
  • The MCP endpoint (POST /api/ucp/mcp) returned HTTP 200 with a valid tools list — Indinoor is already "agent-buyable" via UCP. This is a genuine differentiator versus competitors (none of Voylla/Rubans/Zaveri are UCP-enabled yet).

2. Machine-Readable Files

FileStatusNotes
/llms.txt✅ 200Full agent instructions, UCP flow, store policies, read-only browsing paths. Excellent.
/agents.md✅ 200Mirrors llms.txt; canonical agent-facing description.
/.well-known/ucp✅ 200Valid UCP merchant profile (v2026-04-08 + 2026-01-23), shopping/cart/checkout/fulfillment capabilities, Google Pay + Shopify card handlers.
/api/ucp/mcp✅ 200Working MCP endpoint (tools/list succeeds).
/pricing.md404Gap. No static machine-readable price sheet for AI agents/summarizers.

Recommendation: Add /pricing.md with the structured tiers from business-analysis.md §11 (Under 2000 / Under 5000 / Under 7000 / Above 5K, median ₹2,390, 925-silver premium tail to ₹36,120, discounting norms). Link it from llms.txt/agents.md and the main pricing page. This is the lowest-effort, highest-leverage fix for agentic buying journeys.


3. Schema Markup (Raw-HTML Verified)

Method: fetched raw rendered HTML with curl and parsed <script type="application/ld+json"> blocks directly (NOT markdown/JSON-API extraction, which strips scripts). Per-page results:

Page type@type presentGaps
HomepageOrganization, WebSite (+ SearchAction)Organization.sameAs = 9 empty strings (no social/entity links); no BreadcrumbList
Product (/products/...)Organization, Product (+ Offer list w/ price ₹290, currency INR, availability)No AggregateRating, no Review, no BreadcrumbList; brand only "Indinoor" (no parent Isharya linkage)
Collection (/collections/...)Organization onlyNo ItemList/CollectionPage schema for the 280+ collections
Blog post (/blogs/blogs/...)Organization, Article (author "Akhilesh Singh", datePublished 2025-08-26, publisher Indinoor)No FAQPage despite on-page FAQ sections; no BreadcrumbList

Critical: empty sameAs

The homepage Organization block contains:

"sameAs": ["", "", "", "", "", "", "", "", ""]

This is a broken/null entity graph. Fix: populate with the real profiles — Instagram (indinoorjewellery, 94K), Facebook (Indinoor page), Shanaya Kapoor, House of Isharya (isharya.com), LinkedIn (parent), YouTube. Until then, AI engines cannot confirm "Indinoor = the House of Isharya brand co-created by Shanaya Kapoor," which is the brand's core differentiator.

Schema fixes (priority order)

  1. Populate Organization.sameAs with real entity URLs (highest impact — fixes entity recognition everywhere).
  2. Add FAQPage schema to blog posts that already have FAQ sections (kundan, temple, jadau, zircon, chandbali, etc.). These are directly extractable Q&A blocks.
  3. Add BreadcrumbList to product, collection, and blog templates (helps AI understand category hierarchy — "kundan → earrings → specific product").
  4. Add AggregateRating + Review to Product schema once on-site reviews are enabled (see §6).
  5. Add ItemList/CollectionPage to collection pages so AI can enumerate the catalog by craft/occasion.

All schema is theme-rendered JSON-LD (verified present in raw HTML), so these are template edits — no platform migration needed.


4. AI Visibility Audit (Query Testing)

Queries tested via web search (proxy for how AI engines retrieve/cite). "Cited" = indinoor.in appears in the answer set.

QueryTypeIndinoor Cited?Who Gets Cited Instead
indinoor jewellery brandBranded✅ #1— (indinoor.in, about-us)
Shanaya Kapoor jewellery brand IndinoorCelebrity✅ #1–2LocalSamosa, IndianRetailer, MadAboutMarketing (PR echo)
indinoor vs voylla jewelleryComparison✅ #2Voylla, Nuyug comparison blog, Eternz roundup (which actually mentions Indinoor in body)
indinoor jewellery price range reviewBranded+intent✅ #1Ajio, Flipkart listings, JewelBuzz PR
best fashion jewellery brands india under 2000CategoryLuminaPicks, SouthIndianJewels, LBB, Nykaa, Kalin Couture
what is kundan jewellery typesInformationalGlamaya, Jewelove, Navrathan, GIVA, Indriya

Pattern (high confidence):

  • Branded + celebrity + "vs competitor" queries: Indinoor wins or co-ranks. Its own domain and earned PR dominate. AI answers for these will cite Indinoor.
  • Generic category + informational queries: Indinoor is invisible. Even though it has a 1,600-word Kundan article with an FAQ (better than some ranking pages), it does not surface. Reasons: (a) weak entity graph (no sameAs), (b) no FAQPage schema, (c) low domain authority for non-branded terms, (d) third-party roundups (LBB, GIVA, Eternz) are what AI engines cite for "best brands" — and Indinoor isn't in them.

Competitor note: The Eternz "best jewellery brands 2026" roundup does quote Indinoor's homepage description in its body — proof that Indinoor's copy is getting scraped into third-party AI-cited content, but it is not the primary cited source. Getting into those roundups as a named entry (not just a quoted snippet) is the lever.


5. Content Extractability Assessment

PageDefinition in first para?Self-contained answer blocks?Stats w/ source?Comparison tables?FAQ?Author attr?Updated signal?
Blog posts (56)✅ strong⚠️ thin✅ (text only, no schema)✅ (Akhilesh Singh)⚠️ 2025 dates, not refreshed 2026
Product PDP⚠️ product-name only⚠️
About Us✅ story blocks⚠️ Shanaya/Gauri named, no bios❌ "Last updated" absent
Collections⚠️⚠️

Strengths: Blog content is genuinely citable — 1,600-word average, 11 H2/H3 headings, natural-language FAQ sections, named author, Article schema, real craft depth (kundan/temple/jadau/polki). This is the asset most competitors lack.

Weaknesses to fix for AI extraction:

  • FAQ sections exist but aren't schema-tagged → AI can read them but won't extract them as clean Q&A. Add FAQPage.
  • No statistics with sources on blog/product pages. The GEO study shows citations (+40%) and statistics (+37%) are the top visibility boosters. Indinoor should add citable facts: "2,183 designs across 20+ Indian festivals," "1-year plating warranty," "median price ₹2,390," "backed by 20-year House of Isharya craft heritage (est. 2004)."
  • No comparison tables ("Indinoor vs Voylla vs Rubans" / "Kundan vs Polki vs Temple") — the #1 most-cited content format (~33%). Indinoor should publish 2–3 comparison articles; it already ranks for "indinoor vs voylla," so it owns the intent.
  • About Us lacks a dated "last updated" and founder bios/credentials. Gauri Tandon (Isharya co-founder since 2004) and Shanaya Kapoor (co-creator) should have short, attributed bio blocks — E-E-A-T fuel for AI.
  • Freshness: Blog posts dated 2025; for fast-moving "trending" queries (e.g. "kundan making a comeback 2026"), a 2025 date loses to 2026-dated competitors (GIVA, Glamaya). Add "Last updated: 2026" refreshes.

6. Third-Party Presence (Pillar 3: Presence)

AI engines cite third-party sources more than owned domains. Indinoor's current third-party footprint:

SurfaceStatusAI impact
Instagram✅ 94K (@indinoorjewellery)Strong social signal, but not linked from site schema (empty sameAs)
Facebook✅ Active (Meta Ads Library ~90 ads)Not entity-linked
PR coverage✅ IndianJeweller, IndianRetailer, MadeInMedia, JewelBuzz, MadAboutMarketingGood — these get scraped into AI answers (proven by Eternz roundup)
Wikipedia❌ No Indinoor pageMajor gap — Wikipedia is 7.8% of ChatGPT citations
Reddit❌ Not foundGap — authentic community presence
Roundup/affiliate sites (LBB, GIVA, Eternz, SouthIndianJewels)⚠️ Mentioned as snippet, not a named entryOpportunity — pitch inclusion
Marketplaces (Myntra/Ajio/Flipkart)✅ ListedIndirect presence; AI may cite marketplace listings
YouTube⚠️ Integration ID in source, no confirmed channelGap for "how-to" queries

Recommendations:

  • Entity-link everything: fix sameAs (above) — this alone improves how AI connects the social/PR graph to the brand.
  • Pursue a Wikipedia mention via the House of Isharya entry (not a paid stub — earn it through the verified launch PR). Even a sentence in Isharya's article citing Indinoor's 2025 launch helps.
  • Seed authentic Reddit/Quora participation in r/IndianBeauty, r/DesiWeddings, jewellery threads — answer "best affordable kundan brand" with genuine expertise (not spam).
  • Pitch roundup inclusion to LBB / GIVA / Eternz-type sites as a named "best fashion jewellery brand" entry; Indinoor's 925-silver line and 1-year warranty are differentiators worth a bullet.

7. Prioritized Recommendations

Tier 1 — Schema & entity (do first; template edits, weeks not months)

  1. Populate Organization.sameAs with real entity URLs (Instagram, Facebook, Shanaya Kapoor, Isharya, LinkedIn, YouTube). Unlocks entity recognition everywhere.
  2. Add FAQPage schema to the 56 blog posts that already have FAQ sections.
  3. Add BreadcrumbList to product/collection/blog templates.
  4. Add /pricing.md (static, linked from llms.txt) with the pricing tiers from business-analysis.md §11.

Tier 2 — Content for category & comparison queries

  1. Publish 2–3 comparison articles ("Indinoor vs Voylla vs Rubans", "Kundan vs Polki vs Temple jewellery", "Best fashion jewellery under ₹2000") with comparison tables — Indinoor already owns "indinoor vs voylla" intent.
  2. Add citable statistics + sources to blog/product copy (catalog size, warranty, price median, Isharya heritage since 2004).
  3. Refresh blog dates to 2026 ("Last updated") and add 3–4 new trend pieces ("kundan comeback 2026", "festive gifting guide 2026").

Tier 3 — Authority & presence

  1. Enable on-site product reviews (Judge.me / Shopify native) → populate AggregateRating + Review schema; currently PDPs show no ratings (trust + AI "unreviewed" gap).
  2. About Us founder bios — attributed Gauri Tandon & Shanaya Kapoor blocks with credentials.
  3. Third-party seeding — Wikipedia (via Isharya), Reddit/Quora, roundup pitches.
  4. Fix inconsistent product_type taxonomy (Earring vs Earrings, Necklace vs Necklaces) — fragments collection/entity logic and AI category understanding (from business-analysis.md §14).

What NOT to do (per Google's AI guide + GEO research)

  • Do not write separate "for AI" pages or chunk content into fragments — risk of scaled-content-abuse flag.
  • Do not keyword-stuff (active −10% AI visibility penalty).
  • Do not block AI bots (currently fine — keep it that way).
  • Do not gate the blog behind JS — it already renders server-side (good); keep it that way.

8. Citations (verified live this session)

  • https://indinoor.in/robots.txt — agent welcome, no AI-bot disallows
  • https://indinoor.in/llms.txt — agent instructions (verified 200)
  • https://indinoor.in/agents.md — canonical agent description (verified 200)
  • https://indinoor.in/.well-known/ucp — UCP merchant profile (verified 200)
  • https://indinoor.in/api/ucp/mcp — MCP endpoint (POST tools/list → 200)
  • https://indinoor.in/sitemap_agentic_discovery.xml — lists agents.md
  • https://indinoor.in/ — homepage raw HTML (Organization/WebSite schema; empty sameAs confirmed)
  • https://indinoor.in/products/🎁-solitaire-red-traditional-rakhi — Product schema (price ₹290 INR, OutOfStock; no rating/review)
  • https://indinoor.in/collections/9-to-5-classics — Collection schema (Organization only)
  • https://indinoor.in/pages/about-us — entity/brand-story copy; social/entity not linked
  • https://indinoor.in/blogs/blogs/kundan-jewellery-timeless-elegance-for-every-occasion — Article schema (author Akhilesh Singh, 2025-08-26), FAQ section present (no FAQPage schema)
  • https://indinoor.in/sitemap_blogs_1.xml — 56 blog posts confirmed
  • https://indinoor.in/pricing.md — 404 (gap)
  • Query tests (web search, 2026-08-24): "indinoor jewellery brand" → #1 indinoor.in; "best fashion jewellery brands india under 2000" → no Indinoor (LBB/GIVA/etc.); "what is kundan jewellery types" → no Indinoor (Glamaya/Jewelove/GIVA); "indinoor vs voylla" → #2 indinoor.in; "indinoor jewellery price range review" → #1 indinoor.in

Methodology: all schema findings verified via raw rendered HTML (curl + ld+json block parse), not via markdown/text extraction which strips <script> tags. AI-visibility queries assessed via search-engine retrieval as a proxy for AI-engine citation behavior.