diff --git a/src/components/HomepageFaq.astro b/src/components/HomepageFaq.astro index 04f1e1e..3e9c767 100644 --- a/src/components/HomepageFaq.astro +++ b/src/components/HomepageFaq.astro @@ -1,17 +1,12 @@ --- -// HomepageFaq — Money & process FAQ rendered just above the final CTA band. +// HomepageFaq — single homepage FAQ section rendered just above the final +// CTA band. Covers both buyer-stage objections (cost, timeline, NDA, IP, GeM, +// stack) and the process/support/security questions that used to live in the +// older "Common Questions" block higher up the page. That earlier block was +// removed to avoid a duplicate FAQ rendering and a duplicate FAQPage JSON-LD +// emission — this component is now the canonical homepage FAQ. // -// Why a dedicated component instead of reusing the "Common Questions" block -// further up the page: -// - The questions here target buyers in late-stage evaluation (cost, -// timeline, NDA, IP, GeM, stack). They convert better when surfaced next -// to the final CTA, not next to the testimonials. -// - Emitting FAQPage JSON-LD only once per page is the recommended pattern -// for rich-result eligibility. The existing FAQ block above also emits a -// FAQPage via — so this component renders ONLY the visible UI; the -// schema for these questions is appended to the parent's `faq` array in -// src/pages/index.astro so Google still sees a single, valid FAQPage with -// all 12 Q&A pairs. +// Emits a single FAQPage JSON-LD inline (below) for rich-result eligibility. // // Accessibility: // - Each question is a real -
-
- {faq.answer} -
-
- - ))} - - - - - - + @@ -865,18 +797,8 @@ const faqs = [ font-variant-numeric: tabular-nums; } - /* FAQ accordion styles */ - .faq-answer { - transition: max-height 0.3s ease-out; - } - - .faq-question[aria-expanded="true"] + .faq-answer { - max-height: 500px; - } - - .faq-question[aria-expanded="true"] .faq-icon { - transform: rotate(180deg); - } + /* (FAQ accordion styles moved into , which now renders the + only homepage FAQ section.) */