Enchant Home — AI SEO / Answer Engine Optimization (AEO) Audit

Prepared 17 August 2026. Technical audit performed directly against the live site (enchanthome.in) via raw-HTML inspection (curl), sitemap/robots parsing, and 10 priority-query web-search visibility checks. Business context drawn from business-analysis.md. All findings are verified against source, not inferred.


0. Executive Summary

Enchant Home has done two things well that most D2C brands have not: it ships a working /llms.txt + /agents.md and does not block any AI crawler in robots.txt. But those agent files are generic Shopify/UCP boilerplate — they tell an AI agent how to buy, not what Enchant Home is or sells — so they do zero discovery/AEO work for the brand.

The deeper problem is structural and authority-shaped:

  1. The homepage carries ZERO JSON-LD (no Organization, WebSite, or

breadcrumb) — AI engines get no entity signal for the brand.

  1. Product pages have no aggregateRating / review schema despite Judge.me

being installed — every AI agent reads the catalog as "unreviewed."

  1. Product availability is malformed ("http://schema.org/ instock " with

a trailing space, and "http://schema.org/ outstock" — not a valid value), so availability data is unreliable to machines.

  1. Collection pages carry no schema at all, and there is **no FAQPage or

BreadcrumbList anywhere** on the site.

  1. A /pricing.md file is missing (404) — the exact machine-readable pricing

artifact the AI-SEO playbook recommends for agent-driven commerce, and the single most useful thing for a value-tier linen brand (median variant ₹900) to expose to comparison/agent engines.

  1. Organic visibility is thin: in 10 priority-query checks Enchant Home

appeared in the top 5 only twice (both weakly) and was absent for 8 — meaning AI engines, which lean on indexed/ranked pages, have little surface to cite.

  1. Third-party authority is near-zero: no Wikipedia, Reddit, Quora, Pinterest,

TikTok, or review-site (Trustpilot) footprint — exactly the sources non-Google AI engines over-index on.

Net: the brand is technically reachable by AI but structurally invisible and untrustworthy to it. The fixes below are mostly theme/liquid or app configuration changes with high leverage and low effort.


1. AI Crawler Access (robots.txt) — PASS

https://enchanthome.in/robots.txt is the standard Shopify storefront file.

  • User-agent: *Allow: / (everything public is crawlable).
  • **No Disallow rules target GPTBot, ChatGPT-User, PerplexityBot, ClaudeBot,

anthropic-ai, Google-Extended, or Bingbot.** All AI search-and-cite crawlers can read the site.

  • Only transactional/private paths are disallowed (/admin, /cart/,

/checkout*, /orders, /account, AJAX surfaces, filter/sort crawl-traps).

  • Sitemap: points to /sitemap.xml (which indexes products, collections,

pages, blogs, and an agentic_discovery sitemap).

Verdict: No action needed. The brand is not blocking its own citation.


2. Machine-Readable Agent Files

FileHTTPStatusNotes
/llms.txt200Present but boilerplateGeneric Shopify/UCP text promoting the "Shop skill" + Universal Commerce Protocol. Contains the brand name twice (title/URL) but no product categories, manufacturing story, pricing, FAQ, or discovery context. Does not help AI understand or cite the brand.
/agents.md200Present but boilerplateMirrors /llms.txt. Same gap.
/sitemap_agentic_discovery.xml200PresentLists only /agents.md. Correct infra, but the target is boilerplate.
/pricing.md404MISSING — gapNo machine-readable pricing summary. The AI-SEO playbook explicitly recommends /pricing.md for agent-driven commerce; for a 396-variant value-tier catalog this is the single most useful artifact to expose.
/.well-known/ucp + /api/ucp/mcpreferencedPresent (UCP infra)Agentic-commerce endpoints, not AEO per se, but correctly wired.

Verdict: Infra exists; content of the agent files is generic and a brand-specific /pricing.md is absent.


3. Structured Data (Schema) Audit — raw-HTML verified

Method: fetched raw rendered HTML per page type and grepped for <script type="application/ld+json"> (NOT markdown/cleaned text, which strips script tags). One block per relevant page type.

Page typeJSON-LD?Schema types foundCritical gaps
HomepageNONE (0 blocks)No Organization, WebSite, or breadcrumb. AI has no brand entity signal from the home page.
Product (8/8 sampled)1 blockProduct, Brand, OfferNo aggregateRating (all 8 zero) → products read as unreviewed. No review. No BreadcrumbList. No FAQPage (prose "Common Questions" exists but unmarked). availability malformed (see §3a).
Collection (40)NONE (0 blocks)No ItemList, no breadcrumb. Catalog hierarchy invisible to machines.
Blog post1 blockArticle, WebPage, Organization, PersonAuthor = "Nesters Hub" (generic agency name, no real person/bio/credentials) → weak E-E-A-T. No FAQPage.
About / Hotel-Linen / other pagesno FAQPageNo FAQ schema anywhere on the site.

3a. Product schema defects (verified on live JSON-LD)

  • availability values observed in the wild:
    • "http://schema.org/ instock "invalid (trailing space, should be InStock)
    • "http://schema.org/ outstock"invalid (typo; should be OutOfStock)

Both are non-standard and will be ignored or misread by Google Rich Results and AI shopping agents. This is a theme/formatting bug, not a data gap.

  • aggregateRating: absent on every sampled product even though Judge.me is

installed and the DOM contains 10 "review" strings. The review data exists in the widget but is never emitted as structured data, so AI engines (and Google star-rich-results) cannot see it.

Verdict: Product schema is the highest-leverage fix. Foundation exists (Product/Brand/Offer) but is incomplete and partly broken.


4. Current AI Visibility — 10 Priority Queries

Method: live web-search proxy for each query (top 5 organic results, checked for enchanthome.in presence). This is an organic-ranking proxy — it does not directly query ChatGPT/Perplexity/Gemini (no access in this environment), but because Google AI Overviews correlate with rankings and Perplexity/Claude cite indexed pages, organic absence is a strong signal of low AI citation.

#QueryCited?Who ranks instead
1best cotton bedsheets online IndiaNoGinnora, Amazon, bedsheetsindia, BlueDahlia, SootiSyahi
2waffle bath robe IndiaNoMyntra, Amazon, Etsy, madeliving
3factory direct bedsheets manufacturer IndiaNojaipurbedsheetwholesale, srishtitextile, accio, kearahome
4hotel linen supplier India bulk bedsheetsNothedecorstudio, ekanshglobal, jindalecotex, IndiaMART
5corporate gifting towels customized IndiaYes (5th)tapwell, krishvana, wellwoven, enchanthome, matsyaluxury
6dohar vs comforter differenceNoUrbanJaipur, WeaveAndDecor, Homemonde, urbanspacestore, bedguides
7what GSM towel is bestNogoza, cottonhouse, sleekdudes, cottonwithlove, cottonshades
8Enchant Home bedsheets reviewYes (branded)enchanthome (own), Flipkart, enchanthome x3
9bamboo pillow IndiaNoAmazon, WoodenStreet, AliExpress, homekode, tuckthem
10premium bedding brands IndiaNobedlam, spaces.in, mytrident, beddingbliss

Result: 2/10 queries show any presence (both weak — 5th place and a branded self-search). 8/10 = zero organic footprint. Competitors winning the high-intent "education" queries (doihar vs comforter, GSM, thread count) are exactly the topics Enchant Home's own blog already covers — the content exists but is not ranking or being cited.


5. Content Extractability

Strengths (raw material already on-site):

  • Product pages contain detailed, answer-shaped prose — feature lists, "Size &

Fit," and "Common Questions" Q&A blocks (e.g., "Is it hot in summer?", "How do I wash it?"). These are ideal 40–60 word answer blocks and FAQPage candidates but are currently unstructured.

  • Blog has 30+ educational posts (doihar vs comforter, GSM, thread count,

festive guides) — high-intent informational content AI engines love to cite.

  • Concrete specs (350 GSM, 200/250/300 TC, ₹ prices, "factory-direct

Ichalkaranji") are present as factual claims — good citation fodder.

Weaknesses:

  • No FAQ schema, no comparison tables ("Enchant Home vs X"), no

"Best bedsheets India" listicles (the ~33% most-cited content type).

  • Blog lacks statistics-with-sources, comparison tables, and named expert

bylines.

  • Manufacturer/entity claim (Ichalkaranji facility, vertically integrated) is a

strong unique E-E-A-T signal but lives only in product copy, not surfaced as entity/Organization data.


6. Authority & Presence (E-E-A-T)

SignalStatus
Founder / team transparencyWeak — About page has no founder name or year; LinkedIn lists a possible CEO but unconfirmed.
Blog author bylineWeak — generic "Nesters Hub" (agency), no credentials/bio.
WikipediaNone found
Reddit footprintNone found
Quora / Pinterest / TikTokNone
Review sites (Trustpilot etc.)None located
YouTube8 videos (@enchanthome) — present but thin
LinkedIn~2,048 followers — present
Amazon.in StoreLive — present (helps marketplace citations)
MyntraPossible listing (unconfirmed ownership)

Non-Google AI engines (Perplexity, Claude, ChatGPT) over-index on Reddit, Wikipedia, and review sites — Enchant Home has none of these. Its third-party presence is limited to YouTube/LinkedIn/Amazon, which are real but low-leverage for AI citation compared with the missing channels.


7. Prioritized Recommendations

Ordered by leverage-to-effort. Items 1–6 are technical (theme/liquid or app config) and achievable quickly; 7–10 are content/authority (ongoing).

Tier 1 — Fix what's broken (days, highest ROI)

  1. Repair product availability values. Emit valid InStock / OutOfStock

(camelCase, no trailing space). Pure theme-format fix; currently breaking machine readability.

  1. Add aggregateRating + review to Product JSON-LD. Judge.me already

holds the data — map it into the Product block (or use a schema app). Turns "unreviewed" products into "reviewed" for Google Rich Results and every AI agent. Single highest-leverage change.

  1. Add Organization + WebSite schema to the homepage (and a global site

template). Currently zero entity signal on the most-linked page.

Tier 2 — Add missing structure (1–2 weeks)

  1. Add BreadcrumbList schema to product, collection, and blog templates so

AI understands catalog hierarchy (40 collections, 387 SKUs).

  1. Add FAQPage schema to product "Common Questions" blocks and the top

~10 educational blog posts (doihar vs comforter, GSM, thread count). Natural- language Q&A is the most extractable AEO format.

  1. Add ItemList / collection schema to the 40 collection pages.

Tier 3 — Machine-readable + agent context (1–2 weeks)

  1. Create /pricing.md with structured, machine-readable pricing: per-

category ranges and the catalog median (~₹900), tiers (value/mid/premium), and a link from the homepage + sitemap. Directly recommended by the AI-SEO playbook; essential for AI shopping agents comparing value-tier linen.

  1. Rewrite /llms.txt + /agents.md to be brand-specific. Replace UCP

boilerplate with real context: who Enchant Home is, the Ichalkaranji manufacturing story, full product-category list, B2B verticals (Hotel Linen, Corporate/Wedding Gifting), FAQ pointers, and a link to /pricing.md. Make the file describe the brand, not just how to check out.

Tier 4 — Authority & content (ongoing)

  1. Win the education queries the blog already targets. Upgrade the

doihar-vs-comforter / GSM / thread-count posts with statistics + sources, comparison tables, FAQ schema, named author bylines, and internal links so they rank and get cited over UrbanJaipur/Homemonde/etc.

  1. Build third-party authority where AI looks: authentic Reddit

participation (r/IndiaShopping, r/HomeDecor), Quora answers on bedding, a Trustpilot/profile presence, and Pinterest/TikTok for visual discovery.

  1. Add real bylines + About-page founder/team info (named authors with

credentials; founder story) to lift E-E-A-T.

  1. Produce comparison + best-of content: "Enchant Home vs [competitor]"

pages and "Best bedsheets India 2026" listicles with structured tables (~33% of AI citations are comparisons).

Monitoring

  • Monthly manual AI-visibility check across **ChatGPT, Perplexity, Google AI

Overviews, Gemini** for the 10 queries in §4 (direct testing not possible from this environment — recommend the brand run it, or use Otterly AI / Peec AI / ZipTie for share-of-AI-voice tracking). Google Search Console has no AI-specific report; standard Performance/Coverage remains the Google signal.


8. Google-Specific Note

Google's official stance: no special markup or files are required for AI Overviews/AI Mode, and content should be written for people (same E-E-A-T standards). Everything recommended above — valid schema, clean indexability, original manufacturing detail, FAQ structure — is also good traditional SEO and therefore good for Google AI features. The agent files (/llms.txt, /pricing.md) and FAQ/comparing structure specifically help non-Google engines (ChatGPT/Claude/Perplexity), which reward extractable, machine-readable content. None of it harms Google.


9. Citations (verified sources)

  • https://enchanthome.in/robots.txt — AI crawler allow rules, sitemap pointer
  • https://enchanthome.in/llms.txt — present, boilerplate (200)
  • https://enchanthome.in/agents.md — present, boilerplate (200)
  • https://enchanthome.in/pricing.md — 404 (missing)
  • https://enchanthome.in/sitemap.xml + sitemap_agentic_discovery.xml — agentic infra
  • https://enchanthome.in/ (homepage raw HTML) — 0 JSON-LD blocks
  • https://enchanthome.in/products/enchant-home-premia-...waffle-design-bath-robe (raw HTML) — Product/Brand/Offer schema, malformed availability, no aggregateRating
  • https://enchanthome.in/products/enchant-home-satin-stripe-king-bedsheet-with-2-pillow-covers (raw HTML) — same defects; 8/8 product sample consistent
  • https://enchanthome.in/collections/slumber-comforters (raw HTML) — 0 JSON-LD
  • https://enchanthome.in/blogs/news/diwali-bedding-collection-with-enchant-home (raw HTML) — Article/Organization/Person schema, author "Nesters Hub"
  • https://enchanthome.in/pages/about-us — 200, thin founder info
  • 10 priority-query web-search visibility checks (§4) — performed 17 Aug 2026
  • business-analysis.md — catalog (387 SKU/40 collections), pricing (median ₹900), manufacturing (Ichalkaranji), B2B verticals, social footprint

Schema findings were verified by fetching raw rendered HTML and inspecting <script type="application/ld+json"> blocks directly — not via markdown/text extraction, which would have hidden them.