AEO / GEO Audit
Gynoveda — AI Search Optimization (AEO / GEO / LLMO) Audit
Report generated: 25 August 2026. Prepared from live-site technical inspection (raw HTML, schema, robots.txt, sitemap), business-analysis.md context, and query testing against Google/Bing organic results (proxy for what AI engines retrieve). Confidence levels noted where estimates are used.
Executive Summary
Gynoveda is unusually well-positioned for AI search relative to a typical D2C brand. It already publishes the structural signals AI engines reward most: server-rendered (non-JS-dependent) content, rich medical/FAQ schema, doctor-attributed medical content, per-city comparison hubs, and original clinical evidence with cited statistics. It ranks #2 behind only its own domain for the high-intent "IVF vs Ayurveda" cluster and owns the answer surface for "does Gynoveda work."
The gaps are not structural — they are presence and extraction gaps:
- It is invisible on the highest-volume generic condition queries ("Ayurvedic medicine for PCOS," "irregular periods treatment") where clinic-style Ayurveda sites (Adyant, Svasthvida, Karma Ayurveda, Jiva) currently get the click and will get the AI citation.
- No machine-readable agent files (
llms.txt,pricing.md,agents.mdon the main domain) — so autonomous buying agents evaluating Gynoveda programmatically will skip its JS/Shopify-gated pricing. - Author is branded, not a named clinician — every blog post attributes to "Gynoveda" (Person name) rather than Dr. Aarati Patil or a stated doctor, losing the single biggest AI citation booster (named expert attribution, +25–30%).
- No Wikipedia / third-party entity presence — 7.8% of ChatGPT citations come from Wikipedia; Gynoveda has no article and ranks only on Crunchbase/Tracxn/YourStory for brand-definition queries where it is not the canonical answer.
Top 3 priorities: (a) build an /llms.txt + /pricing.md on gynoveda.com, (b) re-attribute all medical content to named doctors with credentials and add a visible "Last updated" date, (c) win the generic condition-product queries by adding comparison/definition blocks ("PCOS medicine vs Ayurveda") to the existing condition hub.
1. Current AI Visibility — Query Test Results
Method: ran 6 representative queries through web search (Google/Bing organic, which is the corpus AI Overviews and Perplexity/ChatGPT draw from). "Gynoveda cited" = Gynoveda URL in the top organic results for that query.
| # | Query (intent) | Gynoveda in results? | Who ranks instead | Implication |
|---|---|---|---|---|
| 1 | "best Ayurvedic medicine for PCOS PCOD in India" (high-volume product) | No | Adyant Ayurveda, Svasthvida, Aasha Ayurveda, Karma Ayurveda, MissMe, Shivveda | Generic condition queries are owned by clinic-style Ayurveda sites. Biggest citation gap. |
| 2 | "IVF vs Ayurveda for fertility which is better" (high-intent brand) | Yes — #2 (gynoveda.com/compare-ivf-vs-ayurveda) | Gynoveda #2, Hiims #1 | Strong. This is Gynoveda's money query and it wins. |
| 3 | "Gynoveda review PCOS medicine does it work" (brand/trust) | Yes — #1 + #2 (own blog posts) | Gynoveda owns it; Reddit/MouthShut also surface | Excellent. Controls its own reputation narrative in AI. |
| 4 | "Ayurvedic treatment for irregular periods natural" (high-volume product) | No | Ayurcentral, Jiva, AyurvedaOne, Devkalpa, Ask-Ayurveda | Same gap as #1 — condition-level product queries. |
| 5 | "what is gynoveda company about" (brand-definition) | Yes — #1 (About page) + Tracxn/PitchBook/Crunchbase/CBInsights/YourStory | Gynoveda About #1 | Good, but only "About" ranks; no Wikipedia/knowledge-graph entry. |
| 6 | "Ayurveda vs allopathy for PCOS" (comparison) | No | HospitalSuggest, Dr Priyanka Mangla, Boloji, Traya, Vedam | Comparison-query variant owned by clinics/blogs, not Gynoveda. |
Reading: Gynoveda wins on brand and anti-IVF positioning queries (where its content engine is built), but loses on generic condition-product and Ayurveda-vs-allopathy queries — the top-of-funnel surface where AI engines currently cite competitors. Because AI Overviews fan out from the typed query to related sub-queries, losing #1/4/6 means Gynoveda is not retrievable for the "PCOS medicine" fan-out that surrounds its core product.
2. AI Bot Access (robots.txt)
Verified live: https://gynoveda.com/robots.txt
User-agent: *
Allow: /
Disallow: /_next/image
Disallow: /sentry/
Disallow: /_next/static/
Disallow: /_next/image(.*)
Host: gynoveda.com
Sitemap: https://gynoveda.com/sitemap.xml
Verdict: PASS. No Disallow rules target GPTBot, ChatGPT-User, PerplexityBot, ClaudeBot, anthropic-ai, Google-Extended, or Bingbot. All AI search crawlers can index and cite the site. The only disallows are Next.js internal assets and Sentry — harmless for content.
3. Machine-Readable Files for AI Agents
Verified live via HTTP status (25 Aug 2026):
| File | Main domain (gynoveda.com) | Shop subdomain (shop.gynoveda.com) | Status |
|---|---|---|---|
/llms.txt | 404 | — | Gap |
/pricing.md | 404 | — | Gap |
/pricing.txt | 404 | — | Gap |
/agents.md | 404 | 200 (Shopify auto-generated) | Partial — only on shop |
/.well-known/ucp | 404 | — | Not adopted (emerging) |
/api/ucp/mcp | 404 (after redirect) | — | Not adopted (emerging) |
Findings:
- The main content/telehealth domain has zero agent files. Only Shopify auto-generates an
agents.mdon the store. That file describes store capabilities but not pricing in extractable form. - Pricing for the 12 SKUs lives behind the Shopify storefront (JS/theme). An autonomous buying agent (or a Perplexity/ChatGPT agent answering "how much does Gynoveda PCOS medicine cost") cannot parse it from the main domain and gets no
pricing.mdfallback.
Action: add llms.txt and pricing.md to the root of gynoveda.com (the domain AI engines associate with the brand), mirroring the 12-SKU pricing table from pricing-data.csv.
4. Schema Markup (verified via raw HTML, not markdown extraction)
Per the skill's required method, all checks were done against curl raw HTML preserving <script> tags. Findings by page type:
| Page type | URL checked | Schema present | Verdict |
|---|---|---|---|
| Homepage | gynoveda.com/ | MedicalOrganization, Physician | Strong entity signal |
| Comparison hub | /compare-ivf-vs-ayurveda/ | FAQPage (14 Q&A), BreadcrumbList, Question/Answer | Excellent — directly extractable by AI |
| Clinical evidence | /clinical-evidence/ | MedicalStudy, MedicalEntity, MedicalOrganization, FAQPage, Physician | Excellent — original-research schema |
| Blog post | /blogs/gynoveda/gynoveda-review-does-gynoveda-really-work/ | MedicalWebPage, FAQPage, Person (author), BreadcrumbList, ImageObject, Organization | Strong, but author = "Gynoveda" (see §6) |
| FAQ page | /pages/frequently-asked-questions-about-gynoveda-in-first-month/ | none detected | Gap — a dedicated FAQ page with no FAQPage schema |
| Product (Shopify) | shop.gynoveda.com/products/pcos-pcod | 2 application/ld+json blocks incl. Product + AggregateRating + price/SKU | Good — star ratings machine-readable |
| Author/editorial | /pages/editorial-policy/dr-aarati-patil/ | (not directly checked) | Dr. pages exist (good E-E-A-T raw material) |
Verdict: Strong foundation. The main site uses medical-grade schema (MedicalWebPage, MedicalStudy) that most D2C brands lack, and the comparison hub's 14-question FAQPage is exactly the extractable structure non-Google AI engines reward. Two fixes: add FAQPage to the standalone FAQ page, and fix author attribution (next section).
5. Content Extractability
| Check | Result | Detail |
|---|---|---|
| Clear definition in first paragraph? | Yes on medical pages | SSR text confirmed ("IVF Success Rate", "Ayurvedic medicine for fertility" present in raw HTML) |
| Server-rendered (not JS-only)? | Yes | Raw curl returns real body copy — agents see content without rendering |
| Self-contained answer blocks (40–60 words)? | Partial | Comparison FAQ uses Q&A schema (good); blogs are long-form without snippet-optimized lead blocks |
| Statistics with sources? | Yes (strong) | clinical-evidence cites "European Journal of Pharmaceutical and Medical Research, 2022, 190 participants"; FDA/NABL referenced |
| Comparison tables for "X vs Y"? | Yes for IVF-vs-Ayurveda | 317 city-level + 1 master comparison page; but no "Ayurveda vs Allopathy" or "Ayurveda vs PCOS pills" comparison |
| FAQ section w/ natural-language Qs? | Yes | FAQPage on comparison + clinical-evidence + blog |
| Expert attribution (name + credentials)? | Partial — see §6 | Dr. pages exist; blog author shows brand name only |
| Freshness ("Last updated")? | Not visible | No prominent "Last updated" date on medical pages in observed HTML |
| Heading structure matches queries? | Partial | Headings geared to brand/IVF framing, not "PCOS medicine" phrasing |
Strength: the SSR + medical schema + sourced-statistics combo already satisfies Google's E-E-A-T guidance and gives non-Google engines extractable structure. This is better than ~80% of D2C health brands.
6. Authority / E-E-A-T Gaps (highest-impact fixes)
6.1 Author attribution is branded, not named. Every blog post's Person author is "name":"Gynoveda" — a brand, not a clinician. The site has the raw material (Dr. Aarati Patil, gynecologist co-founder; editorial-policy pages for 5 named doctors), but it is not attached to the content that AI engines extract.
- Princeton GEO research ranks "Add quotations / expert attribution" at +25–30% citation boost — the second-largest lever after citations/statistics.
- Fix: set
authorto the writing physician withjobTitle/affiliation(e.g., Dr. Aarati Patil, Gynecologist, Gynoveda) and render a byline + 1-line bio on each medical post. This converts existing content into citable, expert-attributed passages at near-zero cost.
6.2 No visible "Last updated" date. Medical/health content loses to fresher content in AI ranking (recency is weighted). Add a prominent "Medically reviewed / Last updated: [date]" block to every condition and comparison page.
6.3 No Wikipedia / knowledge-graph entity.
en.wikipedia.org/wiki/Gynoveda→ 404. Gynoveda has no encyclopedic entry.- 7.8% of ChatGPT citations are Wikipedia; absence means a whole citation channel is closed.
- Third-party brand-definition queries surface Crunchbase/Tracxn/PitchBook/CBInsights/YourStory — none are "the answer," and none feed AI answer snippets reliably.
- Fix (authentic only): pursue a neutral Wikipedia article citing the ET/Forbes/Mint coverage already earned; ensure Crunchbase/Tracxn entries are accurate and cite the official site.
7. Presence — Where AI Looks
| Channel | Status | AI-search implication |
|---|---|---|
| Own site (882 URLs) | Strong | Primary citation source; well-structured |
| YouTube (@Gynoveda, 78K, 793 videos) | Present | YouTube is frequently cited by Google AI Overviews — underleveraged; transcribe/embed top videos in related blog posts |
| Reddit (r/PCOS Gynoveda thread) | Organic, mixed | Authentic community discussion; AI may cite — monitor sentiment, don't astroturf |
| Circle of Sisterhood (FB, 1.5L members) | Private | Not crawlable; cannot be cited — keep as retention, not AI visibility |
| Instagram / Facebook | Login-walled | Not extractable by AI; follower counts unknown |
| Wikipedia | Absent | Closed citation channel (see §6.3) |
| Review sites (MouthShut) | Present | Surfaces for "Gynoveda reviews" — ensure accurate, respond to negatives |
| Marketplaces (Amazon/Flipkart/Nykaa) | Present | Product-level presence; AI may cite marketplace listings |
8. Prioritized Recommendations
Ordered by impact-to-effort for AI citation gains.
P0 — Quick wins (days, dev + content)
- Add
/llms.txtand/pricing.mdto gynoveda.com root. Mirror the 12-SKU table (handle, condition, pack sizes, INR price range, per-tablet cost, rating). Lets autonomous agents and ChatGPT/Perplexity answer "how much is Gynoveda PCOS medicine" from a parseable file. (Effort: low; impact: high for agentic commerce.) - Re-attribute all medical/blog content to named doctors with
jobTitle/affiliationin schema + visible byline. Use Dr. Aarati Patil and the 5 editorial-policy physicians. (Effort: low; impact: +25–30% citation, per GEO research.) - Add "Medically reviewed / Last updated" date to every condition, comparison, and blog page. (Effort: low; impact: recency weighting.)
P1 — Content expansion (weeks)
- Win generic condition-product queries (gap #1, #4). Build "Ayurvedic medicine for PCOS / irregular periods / white discharge" definition + comparison blocks on the existing condition hub, using the 40–60-word answer-block pattern and FAQ schema. Target the fan-out Gynoveda currently misses.
- Add "Ayurveda vs Allopathy for PCOS" comparison (gap #6) — a natural extension of the IVF-vs-Ayurveda hub; currently owned by clinics/blogs.
- Add FAQPage schema to the standalone FAQ page (currently none) and to any condition page missing it.
- Embed/cross-link top YouTube videos into related blog posts — YouTube is an AI-Overview citation source Gynoveda underuses.
P2 — Authority / presence (months)
- Pursue a neutral Wikipedia article (authentic, citing existing ET/Forbes/Mint coverage) to open the Wikipedia citation channel.
- Monitor AI visibility monthly (top 20 queries across ChatGPT/Perplexity/Google AI Overviews) using the DIY spreadsheet method or a tool (Peec AI / Otterly / LLMrefs). Baseline today: wins on brand + IVF-comparison queries, loses on generic condition + Ayurveda-vs-allopathy queries.
- Keep robots.txt as-is (correct — all AI bots allowed). Do not block CCBot unless training-opt-out is a deliberate choice; blocking search bots would kill citation.
9. What NOT to Do (Google's guidance + skill warnings)
- Do not write separate "for AI" content variants — risk of scaled-content-abuse spam flag; the byline/schema fixes serve both people and AI.
- Do not chunk pages into AI-bait fragments — keep normal heading/paragraph structure (already correct here).
- Do not block GPTBot/PerplexityBot/ClaudeBot — they are allowed today; keep them allowed.
- Do not fabricate Wikipedia content or spam Reddit — authentic participation only.
10. Methodology & Confidence
- robots.txt, sitemap, schema, and machine-readable-file checks: direct, live, high confidence (raw
curlHTML, Aug 25 2026). - Query visibility: tested via web search (Google/Bing organic proxy for AI retrieval); medium confidence — AI engines' live cited sources can differ from organic SERPs, and ChatGPT/Perplexity were not queried directly in this environment. Treat the query table as directional, not definitive.
- Author-attribution and freshness findings: high confidence (observed in raw HTML JSON-LD).
- Wikipedia absence: high confidence (HTTP 404 verified).
- Business context (SKUs, pricing, funding, audience): from business-analysis.md (parent task t_307ebaa5), Aug 25 2026.
Citations
- https://gynoveda.com/robots.txt — AI bot allow rules verified
- https://gynoveda.com/sitemap.xml and /sitemap-0.xml — 882 URLs (317 compare-ivf-vs-ayurveda, 261 pages, 159 blogs, 125 success-stories)
- https://gynoveda.com/compare-ivf-vs-ayurveda/ — FAQPage (14 Q&A) + BreadcrumbList schema; ranks #2 for "IVF vs Ayurveda"
- https://gynoveda.com/clinical-evidence/ — MedicalStudy / MedicalEntity / FAQPage schema; cites European Journal of Pharmaceutical and Medical Research 2022, 190 participants
- https://gynoveda.com/blogs/gynoveda/gynoveda-review-does-gynoveda-really-work/ — MedicalWebPage + FAQPage; author "Gynoveda" (branded, not named clinician); ranks #1 for "does Gynoveda work"
- https://gynoveda.com/pages/editorial-policy/dr-aarati-patil/ — named-physician E-E-A-T raw material (not attached to blog author schema)
- https://shop.gynoveda.com/products/pcos-pcod — Product + AggregateRating JSON-LD (star ratings machine-readable); /agents.md auto-generated by Shopify (200)
- https://en.wikipedia.org/wiki/Gynoveda — 404 (no encyclopedic entity)
- pricing-data.csv (workspace) — 12 SKU pricing source for proposed /pricing.md
- Query SERPs (web search, 25 Aug 2026): Adyant Ayurveda, Svasthvida, Karma Ayurveda, Jiva, Hiims, Traya, HospitalSuggest for generic/comparison queries where Gynoveda is absent
- business-analysis.md (parent task t_307ebaa5) — company/funding/audience/SKU context
- AI SEO skill (cro-skills/ecommerce/ai-seo v2.1.0) — Princeton GEO citation-boost stats, schema-verification method, robots.txt bot list, machine-readable file guidance