Frequently Asked Question

Through SEBI's SCORES platform under the Accessibility complaint category. Regulated entities must remediate the reported issue to close the complaint. This makes ongoing Webflow site maintenance part of compliance, not a one-time project.

Yes. SEBI requires circulars, notices, and investor documents to follow accessible document standards — tagged PDFs with logical reading order, headings, and alt text on figures. Uploading a flat PDF to Webflow CMS does not make it compliant.

Yes — Webflow outputs semantic HTML and supports ARIA attributes, but conformance depends on implementation. Skip links, keyboard-safe interactions, form labels, contrast, alt text, and accessible PDFs must be built deliberately. Webflow does not guarantee WCAG compliance out of the box.

March 31, 2026 for readiness status submissions, April 30, 2026 for IAAP-certified audits, and July 31, 2026 for full remediation of audit findings. Annual audits begin from April 30, 2027.

All SEBI-regulated entities: stock exchanges, depositories, brokers, mutual funds, portfolio managers, investment advisers, research analysts, and other intermediaries. Any investor-facing website, app, portal, or published document is in scope.

SEBI Circular 2025/111 mandates WCAG 2.1 Level AA or the latest version. In practice, aim for WCAG 2.2 AA — it is the current W3C recommendation and covers focus visibility and accessible authentication criteria auditors increasingly test for.

Add a health guard before you write: if not every constituent prices cleanly and the benchmark isn’t valid, exit with a non-zero status before writing the file. A failed run becomes a no-op instead of an outage, and the live page keeps the last good snapshot. Pair it with an inline baked fallback on the front end so a failed fetch never shows an empty box.

yfinance handles Yahoo’s cookie-and-crumb authentication for you, so it works where a bare curl or fetch now returns 429 — including GitHub’s runners. It also exposes clean fields like last_price, previous_close, and market_cap, and is the same library many source-of-truth dashboards use, so your numbers match theirs.

Yes. A JSON file committed to a public repo is served over GitHub’s CDN via the raw URL — CORS-enabled and cached — so any front end can fetch it. It absorbs traffic spikes for free, costs nothing, and every update is a commit, which makes the git history an audit log of the data over time.

Run a Python builder on a schedule (GitHub Actions), have it fetch prices with yfinance and write a single JSON file, then commit that file back to the repo. GitHub serves it over its CDN as a free static API, and your Webflow front end fetches the JSON on page load and renders it with Chart.js. The only moving part is a cron that commits a file — no server, no database.

It usually isn’t rate-limiting. Yahoo’s public endpoints now reject bare, unauthenticated requests and expect a cookie-and-crumb session: you fetch a session cookie, request a short crumb token, then send both on every call. The easy fix is the yfinance Python library, which performs that handshake automatically on first use — from any IP, including CI runners.

A well-built B2B Webflow site usually takes 6 to 12 weeks: about 1–2 weeks of discovery and architecture, 2–4 weeks of design, 2–4 weeks of development and CMS setup, and 1–2 weeks of testing and launch. Rushing the planning and CMS phases is the most common cause of expensive rebuilds later.

Build forms natively in Webflow and connect them to HubSpot, Salesforce, or your CRM via native integrations, webhooks, or a connector like Zapier or Make so leads land where sales works. Keep required fields minimal, add conversion tracking and consent at build time, and keep your primary CTA above the fold and in the navbar.

Create Collections for solutions, industries, case studies, integrations, resources/blog, team members, and testimonials, then link them with reference and multi-reference fields. That way a case study automatically appears on the solution it proves, the industry it serves, and the homepage proof section. Marketing publishes new content and it propagates everywhere with no developer involvement.

Start with the buyer, not the build. Map your audiences and how they decide, then design the sitemap and decide which page types repeat — solutions, industries, case studies, integrations, resources. Anything that repeats should be a CMS Collection, not static pages. Settle your CMS model and component system before you open the Designer; that's what makes the site scale instead of needing a rebuild.

Webflow combines visual design control with a powerful CMS, clean semantic markup, native SEO controls, and integrations to your CRM and marketing stack. For B2B, that means a site marketing can update without engineering, page types that scale through the CMS, and the performance and structured data that modern search and AI answer engines reward.

Four things: clarity (turn complex science into a story non-experts grasp), trust (precise design, transparency on team, safety, milestones, and backers), differentiation (specific, evidenced claims), and reach (SEO and AEO so investors, partners, and journalists — and AI answer engines — find and cite you). It should serve investors, regulators, partners, and talent without diluting the message.

Investors research heavily before they reply, so a site that makes your traction, team, and milestones legible directly supports fundraising. In a brutal deep-tech talent market, strong mission, team, and careers pages help you win engineers over competitors. The website does this work continuously, before and between conversations.

The nuclear renaissance has produced a sea of similar-sounding pitches. Your website is where you stake out exactly what's different — your technology, deployment model, timeline, and proof points. Specificity wins: concrete milestones, real test results, and named partnerships separate you from companies trading in vague 'reinventing energy' language.

Lead with outcomes — safer, cheaper, scalable, deployable — and put the deep technical detail one layer down for those who want it. Use diagrams, interactive explainers, and motion to walk visitors through how your reactor or system works. The goal is that an investor or utility executive can leave your homepage able to explain, in a sentence, what you build and why it's different.

Because nuclear companies sell complex, high-stakes technology to skeptical, high-value audiences — investors, regulators, utilities, governments, and rare engineers — and almost all of them form their first opinion on your website, before any conversation. A strong site makes the science clear, builds the trust the industry runs on, and differentiates you in a crowded clean-energy field.

The big ones: the AI Site Builder and Assistant (plus AI credits), AEO and AI-assisted SEO so you're cited by AI answer engines, the next-gen CMS with Content Delivery APIs (REST + GraphQL) for headless/hybrid use, Webflow Cloud for backends, and real-time collaboration, localization, and DevLink. Together they let one platform cover design, content, AI, and backend.

Webflow Cloud lets you deploy real backend code — Next.js or Astro — right alongside your Webflow site, with compute quotas built into your plan. B2B teams use it for payment webhooks, form handlers, authentication endpoints, and small APIs, without standing up and paying for a separate host like Vercel or Render.

It can now. The next-gen CMS handles over a million items per collection — removing the limit that used to force migrations — and Content Delivery APIs (REST + GraphQL) let you feed apps and other channels from the same CMS. Add real-time collaboration, publishing workflows, localization at scale, Webflow Cloud for backend logic, and Enterprise-grade security and governance.

Yes. For pre-seed to seed companies, Webflow lets a founder or single marketer run the whole site — launch fast with the AI Site Builder, look credible, start a CMS-powered blog and case studies for SEO, and use native forms and simple integrations. You get a site that punches above your headcount with no dev hire and a low monthly cost.

Because your website is core pipeline and credibility, and Webflow lets marketing own it — shipping and editing pages without a dev queue — while keeping design quality high. It iterates fast for campaigns and A/B tests, and the same platform scales from a 5-page seed site to a 5,000-page enterprise presence, so you don't replatform as you grow.

Use Webflow when you want visual editing for non-technical teams plus the ability to feed content to other channels, or when you previously hit its old item limits. Reach for a dedicated headless CMS when you need complex content modeling beyond Webflow's fields, heavy programmatic write/ingest pipelines (the Content Delivery API is read-only), or advanced multi-brand, workflow, and localization features.

Webflow's next-gen CMS supports over one million items per site and per collection. This removes the ceiling that previously pushed large companies to migrate off Webflow to dedicated headless CMS platforms.

They're read-only APIs for retrieving your published Webflow CMS content and delivering it anywhere. They serve published content only (nothing staged leaks), are available over REST and GraphQL, and are delivered from a global CDN/edge network that returns cached content in a fraction of a second at high traffic volumes.

Yes. The Content Delivery APIs support GraphQL alongside REST, so developers can query exactly the fields they need in a single request instead of over-fetching from rigid endpoints. That's the developer experience teams expect from dedicated headless platforms.

Yes — much more so now. Webflow's Content Delivery APIs let you read published CMS content over REST and GraphQL and deliver it to any front end (web apps, mobile apps, kiosks, chatbots) from a global CDN. Combined with the next-gen CMS scaling past a million items per collection, Webflow now works as a credible headless or hybrid CMS, not just a coupled site builder.

Webflow now offers AI-assisted schema generation, which is great for scaling. But for full control — exact types, CMS-bound values, and ensuring schema matches your content — adding your own JSON-LD via custom code is the most reliable approach. Many teams use both: AI to draft, custom code to lock it down.

Run the page through Google's Rich Results Test and the Schema Markup Validator (validator.schema.org) to catch invalid JSON or missing fields. Then view source on the published page to confirm the