Why I Design Webflow About Pages With Five Sections, Not Twelve

Why I Killed Half of My Standard About-Page Template

For three years my standard Webflow About page template had twelve sections: hero, mission, story, founder bio, team grid, values, awards, partners, press, locations, careers CTA, and contact. I shipped it on dozens of client sites. It was thorough. It was also where most clients lost interest in their own About page within six months and where I lost time in every kickoff trying to justify sections nobody had content for. In April I cut it down to five. The pages got better, faster to build, easier to update, and noticeably more cited by AI search.

About pages are the second most-visited non-pricing page on most B2B Webflow sites, according to Webflow's own 2025 analytics benchmark. They are also the page AI systems lean on most heavily when answering entity-recognition queries like who is X or what does X do. A bloated About page dilutes both jobs. A focused five-section About page does both well.

This piece walks through the five sections I keep, why I cut the other seven, and the structural and schema decisions that make a slim About page outperform a maximalist one.

What Are the Five Sections That Stay?

The five sections are the hero with a one-sentence mission statement, the story section with a clear founding moment and reason, the team section with named individuals and roles, the values or principles section written as prose paragraphs, and a closing section that explains how to start working together. Hero, story, team, principles, contact. Five.

Each section answers a question the visitor or AI parser would naturally ask. Who are you. Why do you exist. Who is on the team. What do you believe. How do we start. Five questions, five sections, one page. The structure mirrors the question-driven H2 pattern I use for blog posts and it works for the same reason. When the page is organized around questions, every section earns its keep.

The order matters. Hero first because it sets context. Story second because it sets reason. Team third because it sets faces. Principles fourth because they set tone. Contact last because by the time the visitor has read the first four sections, they should be ready to act. Inverting the order works in some cases, but for most B2B Webflow sites this sequence is the working default.

Why Did I Cut Mission, Values, Awards, Partners, Press, Locations, Careers?

I cut mission because the one-sentence version belongs in the hero and the longer version was always boilerplate. I cut values because they overlap with principles, and pages with both feel like two committees wrote the same page. I cut awards because they belong in a trust bar above the fold or on a press page. I cut partners because they belong on a partners page. I cut press because it belongs on a press page. I cut locations because they belong in the footer. I cut careers because it belongs on a careers page.

The pattern is that each cut section had a better home elsewhere on the site. The About page was acting as a dumping ground for content that did not have its own surface. Once I built the other surfaces, the About page could breathe. The five remaining sections then had room to be specific and substantive instead of crowded and shallow.

How Does a Slim About Page Help AI Citations?

AI systems cite About pages when answering entity queries because the About page is the canonical entity description for the company. A slim page with clear answer blocks to who is X and what does X do gets cited cleanly. A bloated page with twelve competing narratives confuses the entity resolution and gets cited less. Princeton's GEO-bench research from January 2026 found that entity-recognition citation rates are 1.4x higher for About pages under 1,200 words than for pages over 2,500 words.

The trick is keeping the page dense with concrete information without padding. My five-section structure usually lands between 600 and 900 words of body text, which is in the sweet spot for entity citation. Each section contains specifics: founding year, team headcount, named individuals, specific principles with examples. No filler. No passionate about excellence abstractions.

The Organization schema in the page head ties everything together. The About page is the canonical source for the Organization schema across the site. If you have not yet added organization schema, my walkthrough on organization schema in Webflow for AI covers the exact JSON-LD block I paste into the About page head section.

What Should the Hero Section Say?

The hero should answer what does this company do, for whom, with what differentiator in one or two sentences. Not we are passionate about helping our clients succeed. Not your trusted partner for digital transformation. A specific declarative sentence like We are a Bengaluru Webflow studio building marketing sites for B2B SaaS founders who need to ship in under six weeks. That sentence carries the page.

The hero visual should be either a single photograph of the team or workspace, or a clean type-led composition. Avoid stock illustrations of abstract teamwork. Avoid mood boards of office plants. The visual has to anchor a real specific company. Generic visuals make AI systems hesitate to confidently associate the page with a unique entity.

For the design pattern of how the hero sits in the page, my note on left-aligned B2B hero sections covers the broader layout decisions that work across hero contexts including the About page.

How Should the Story Section Be Written?

Write the story as a three to four paragraph narrative with a specific founding moment, a specific obstacle, and a specific present. Not founded in 2020 with a vision. Not we believe technology can change the world. A specific moment, a real challenge, a clear current state. Concrete dates, real numbers, real frustrations. Stories with specifics get cited because they are quotable.

The Bengaluru architecture studio I rebuilt for in March opens their story with In 2019 our founder, Anjali, returned from a corporate firm in Singapore because she could not stomach designing one more glass-walled office tower. That sentence is more memorable, more citable, and more honest than any passionate vision opener. It is also clearly attributable to a unique entity, which is what AI systems need to confidently surface the page.

What Belongs in the Team Section?

Names, roles, and a sentence about each person. For teams under twelve, show everyone. For teams over twelve, show leadership plus a and 18 more across India and Singapore line. Each person needs a photo or a clean visual placeholder. Each name should be a structured entity in the page schema, linked to a Person schema object with a sameAs URL pointing to their LinkedIn or personal site.

The sameAs links matter for AI entity resolution. If your About page lists Pravin Kumar, Founder with a sameAs link to a verifiable LinkedIn profile, AI systems can confidently disambiguate me from the other Pravin Kumars in the world. Without that link the entity is fuzzy and the citation likelihood drops. This is one of the highest-leverage 30-minute investments you can make on any About page.

What Is the Right Closing Section, and Why Not a Contact Form?

The closing section is a soft-but-direct explanation of how to start working together, with a single CTA. Not a contact form embedded directly on the About page. The contact form belongs on a dedicated contact page where the visitor's full attention is on filling it. The About page closing should be a sentence about what working together looks like, the next concrete step, and a link.

For my own About page the closing reads Most projects begin with a 25-minute discovery call where I learn what you are building and we figure out if I am the right Webflow partner. The call is free and is not a sales call. Book one below. Then a single button that links to the discovery page. The structure mirrors the broader retainer flow I described in my walkthrough on the 25-minute discovery call structure.

How Do You Test Whether the Slim About Page Is Working?

Watch three signals. Time on page should rise because the page reads quickly and people actually finish it. Scroll depth should hit 85% or more because there is less to scroll past. Conversion to the next step CTA should rise because the page does not exhaust the visitor's attention before they get to it. All three measurable in Webflow Analyze in two weeks of post-launch data.

For AI-citation signal, watch the entity-recognition queries in Perplexity and ChatGPT Search for your brand name and category. The About page should start appearing as a cited source within four to six weeks of being rebuilt with clean structure. If it does not, audit the schema and the photo assets first.

How to Rebuild Your About Page This Week

Open your current About page and list every section. Map each to one of the five canonical sections. For anything that does not map, decide whether it deserves its own page or can be deleted entirely. Build the new five-section page from scratch in Webflow rather than editing the old one, since a rebuild forces you to confront each section freshly. Most studios can rebuild an About page in a single afternoon once they have committed to the five-section structure.

For the broader design context, my note on the Webflow spacing scale for brand systems covers the rhythm decisions that hold the five sections together visually. The structure is only half the work. The other half is making the visual cadence calm enough that the slim page does not feel sparse.

If you want help cutting your About page down to five sections without losing what matters, I am happy to walk through it. Let's chat.