# BrandingLab — Full Content for AI Engines > Complete content of brandinglab.io as plain markdown, designed for ingestion by AI search engines (ChatGPT, Perplexity, Claude, Gemini, AI Overviews). Each section corresponds to one page or article on the live site. URLs are absolute and canonical. --- ## Site overview **BrandingLab** is a B2B website and Answer Engine Optimization (AEO) studio for ambitious mid-market teams. We combine three capabilities: Webflow design and development, AI-native React applications, and Answer Engine Optimisation. Our specialism is making B2B websites that get cited by AI search engines, not just ranked by Google. - Website: https://www.brandinglab.io - Founded: 2018 - Location: Israel (serving clients in IL, US, UK, EU, globally) - Accreditation: Webflow Partner, Certified Lovable Partner --- ## Page: Home **URL:** https://www.brandinglab.io/ BrandingLab is a B2B website and Answer Engine Optimization (AEO) studio for ambitious mid-market teams. We design and build websites that get cited by AI search engines (ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews) — not just ranked by Google. We work across three stacks and pick the right one for the job: - **Webflow** — for marketing sites where visual storytelling, CMS flexibility, and editorial independence matter most. - **AI-native React (Lovable, Cursor)** — for sites and apps that need custom logic, integrations, or AI features built into the product. - **Internal tools and MVPs** — dashboards, ops tools, client portals and founder MVPs, built on Lovable as code you own. **Six signs you've outgrown your current site:** 1. Your site loads slowly and Core Web Vitals are red. 2. Your CMS requires a developer for routine content changes. 3. Your brand has evolved but the site still reflects an older positioning. 4. You're invisible in AI search results — ChatGPT and Perplexity don't cite you for your category. 5. Your design system is inconsistent across pages and the marketing team is patching as it goes. 6. You can't ship landing pages or campaign experiments without engineering bottlenecks. If two or more of those resonate, we should talk. --- ## Page: About **URL:** https://www.brandinglab.io/about BrandingLab is a small senior team — strategists, designers, and engineers — who have been shipping B2B websites since 2018. We're a Webflow Partner, but we're not a Webflow agency. We're a website and AEO studio that uses Webflow when it's the right tool, and uses AI-native React or custom builds when it isn't. **How we work:** - Senior people, no juniors-as-billing-hours. - Strategy and design lead; engineering follows. We don't open Figma until the positioning is clear. - AEO is treated as a first-class requirement, not a post-launch add-on. Every site ships with structured data, semantic HTML, and content architected for AI citation. - Fixed scope, fixed timeline, no surprises. Most projects ship in 6–12 weeks. **Who we're for:** Mid-market B2B companies — typically $5M–$200M revenue — where the website is a material part of how the business wins customers, and where design, performance, and AI visibility actually move the number. --- ## Page: Webflow Agency **URL:** https://www.brandinglab.io/webflow-agency We design and build Webflow sites for B2B teams who need a marketing site that looks senior, performs on Core Web Vitals, and gives the marketing team full editorial independence after launch. **What's included in a typical Webflow engagement:** - Discovery and content strategy — sitemap, messaging hierarchy, and CMS architecture before any design work. - High-fidelity design in Figma — typography system, component library, page templates. - Webflow build — pixel-perfect, responsive, accessible, and structured for editor independence. - CMS architecture — collections for case studies, articles, team, jobs, and resource hubs. - AEO foundations — JSON-LD schema, semantic HTML, FAQ patterns, llms.txt and llms-full.txt. - Migration — from WordPress, HubSpot, Squarespace, or custom CMS, with full URL redirect mapping. - Training and handover — your team owns the Webflow project after launch. **Timelines:** 4–12 weeks depending on scope. **Ownership:** You own the Webflow project. **Support:** Optional retainers for content, iteration, and new pages. --- ## Page: AEO Services **URL:** https://www.brandinglab.io/aeo-services Answer Engine Optimization (AEO) is the discipline of making your website citable by AI search engines — ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews. It is not SEO. The unit of success is being the source the AI cites when a prospect asks a question, not being the tenth blue link on a search engine results page. **What our AEO engagements typically include:** - **Audit** — a full readout of how AI engines currently represent your brand, what schema you have, what citation gaps exist, and what to fix first. - **Structured data** — Organization, Service, Article, FAQPage, BreadcrumbList, AggregateRating schemas in the initial HTML payload (not injected by JavaScript). - **Content rewriting for AI citation** — clear definitions in the first paragraph, TL;DR boxes, comparison tables, numbered steps, FAQ sections at the bottom, quotable statistics with sources. - **AI-native discovery files** — llms.txt and llms-full.txt for AI crawlers that prefer markdown over HTML. - **Prerendering or SSR** — real semantic HTML in the body of every page so AI crawlers can read content without executing JavaScript. - **Entity authority** — Wikidata entries, third-party citations, AggregateRating from Clutch/G2 to strengthen your brand entity in AI knowledge graphs. - **Citation tracking** — monitoring which queries surface your brand across each AI engine and tracking changes over time. The goal isn't to rank in Google. The goal is to be the answer. --- ## Page: Lovable Partner **URL:** https://www.brandinglab.io/lovable-partner BrandingLab is a **certified Lovable Partner**. We brand, build, and ship real working products for founders and teams in weeks — not months. Certification means our work has been reviewed and approved by Lovable itself, paired with over 20 years of brand, product, and conversion experience. **What we actually build:** - **Investor / demo-day MVPs** — a clickable, working version of your product idea, ready before your next raise or demo day. - **Cap table & SAFE tracker** — a simple internal tool for pre-seed/seed rounds instead of one fragile spreadsheet. - **Milu'im (reserve duty) roster & workload tracker** — who is called up, who is covering what, and where delivery risk is building. - **Investor update generator** — pull metrics into a clean monthly update instead of rebuilding the same email by hand. - **Grant & Innovation Authority compliance tracker** — milestones, spend and reporting deadlines against an IIA (or other) grant. - **Pilot / POC tracker for enterprise sales** — one view of stage, blockers and next steps per pilot. - **Bilingual (Hebrew/English) client onboarding portals** — info, contracts and payment in one guided flow. - **Multi-currency invoicing & expense dashboards (NIS/USD/EUR)** — for teams billing US or European customers while reporting locally. **Who it's for:** pre-seed and seed founders who need a working product rather than a slide deck; growing companies still running on spreadsheets and manual handoffs; agencies and consultants who need a quiet delivery partner. **How it works:** Discover (Day 1–2) — a free 20-minute scoping call to map the core user flow and agree scope, timeline and fixed price. Build (Week 1–3) — built in Lovable with you in the loop, working screens within days. Launch (Week 2–4) — a live, working product ready to demo, test with users, or hand to a dev team to scale. **Packages (fixed scope, fixed price):** | Package | Best for | Typical timeline | Starting at | | --- | --- | --- | --- | | Validation MVP | One core user flow, clean UI, ready to demo | Within two weeks | $8,000 | | Internal Tool / Dashboard | Logins, data views, reporting, basic integrations | 2–3 weeks | ₪35,000 (~$9,500) | | Full Product Build | Multi-feature product with accounts, payments, integrations | 3–6 weeks | ₪65,000 (~$17,500) | Every package includes a fixed-price quote after the scoping call — no hourly billing, no scope creep. Optional iteration and support retainer from ₪3,500/month (~$950) once your product is live. --- ## Case studies ### Case study: Threadworks _21 warehouse homes in Bethnal Green — Capri's design intent, translated one-to-one into a Webflow site the sales team can run._ **URL:** https://www.brandinglab.io/work/threadworks **Industry:** Real Estate Development **Stack:** Brand Launch, Real Estate, Webflow **Timeline:** 2 weeks **Challenge:** When a branding agency delivers a Figma, what you've received is brand equity in visual form. Every type choice, every image ratio and every hover state has been argued over for a reason. The moment that file hits a developer who doesn't care about the reasons, the whole thing starts leaking value. The site ships, it looks 'fine,' but the feel is gone — and no one can quite explain why the brand isn't landing the way it used to. **Approach:** The fix is not hiring a bigger agency that tries to do both brand and build. It's choosing a developer who treats design intent as something to protect, not approximate. Pelumi led development for us on Threadworks and translated Capri's Figma one-to-one — every Crittall detail, every image rhythm, every breakpoint — then wired it into a Webflow CMS so the sales team could update the site without going back to a developer for every change. **Results:** - Homes marketed: 21 - Figma to live: 1:1 translation - CMS: Sales-team managed - Delivered for: VFUND **FAQs:** **Q: Why does the Figma-to-build handoff matter so much?** A: A Figma file is brand equity in visual form. Every decision in it has been argued over for a reason. If the developer treats it as a rough reference rather than a spec, the site will look 'fine' but the feel will be gone — and the brand stops landing the way it used to. **Q: How did you protect Capri's design intent on Threadworks?** A: Pelumi led development and translated Capri's Figma one-to-one — every Crittall detail, image rhythm and breakpoint — rather than approximating it. That precision is what keeps the brand feel intact when the site goes live. **Q: Can the sales team update the site themselves?** A: Yes. The build is wired into a Webflow CMS the sales team can run themselves, so day-to-day edits and content updates don't require a developer each time. **Q: What should I ask before commissioning my next site?** A: Treat the Figma-to-build handoff like the transaction it is. Ask who specifically is building it. Ask for a side-by-side of a previous Figma and the live site they shipped from it. A good developer costs more; they also save you from rebuilding the site in eighteen months because the brand stopped working online. --- ### Case study: Gazette Search _SA Government Gazette intelligence platform — 900,000+ notices searchable by ID number in seconds; bulk-screens 50,000 IDs in under 60 seconds._ **URL:** https://www.brandinglab.io/work/gazette-search **Industry:** Legal & Financial Services — Collections **Stack:** AI Product, SaaS **Timeline:** 6+ months (in production) **Challenge:** Large SA collection agencies and BPOs run hundreds of thousands of searches per month against the Government Gazette — verifying deceased estates, insolvencies, liquidations, sales in execution and name changes. Every existing access path was broken in a different way: the official government source rejects programmatic search, the popular community mirror had started returning broken files, and the legally-clean public archive was frozen at 2021. A false 'nothing found' isn't cosmetic here — it puts lawyers in courtrooms and collections analysts into recoveries that should never have been opened. **Approach:** I led the build as one developer, one repo, a pragmatic stack — starting in Lovable for UI velocity, then moving to Claude for the repo-wide query and index work needed to hit sub-second search against millions of rows. Hundreds of prompts later — over several months — the system returned matches in seconds against a 2GB database from a single web instance. When a data audit surfaced a 29.6% silent gap in historical coverage, I backfilled from the authoritative public archive, wired a weekly fetch against the official source for everything from 2022 onward, and quietly created retroactive watchlists for 507 previously failed searches — no 'we're sorry' email, just the answer users originally came for. **Results:** - Gazette notices indexed, 25 years of coverage: 900,000+ - Bulk-screened in under 60 seconds: 50,000 IDs - Search turnaround vs the manual baseline: Seconds vs 8 months - Per-search pricing across the volume curve: R35 → R0.55 --- ### Case study: Tabono _20+ page industrial website built in 3 weeks for a conference launch_ **URL:** https://www.brandinglab.io/work/tabono **Industry:** Mining & Industrial **Stack:** Webflow, Industrial, Animation **Timeline:** 3 weeks **Challenge:** Three weeks. Twenty-plus pages. A conference date that wasn't moving. The site needed to balance African heritage with global credibility, deliver a genuine 'wow factor' for conference attendees, and perform on mobile devices over unreliable exhibition hall WiFi. **Approach:** I led the project with parallel workflows replacing sequential design-build cycles: while a partner specialist was finalising later pages, development had already begun on core architecture. The visual system drew from African design principles — geometric precision, bold structural forms, earthy tones — without relying on decorative motifs. Hardware-accelerated CSS and GSAP animations were tested specifically for conference conditions. **Results:** - Pages Delivered: 20+ - Build Time: 3 weeks - Conference Launch: On time - Animation System: Custom GSAP **FAQs:** **Q: How did you deliver 20+ pages of Webflow in three weeks?** A: I replaced sequential design-build cycles with parallel workflows — development began on the core architecture and reusable components while a partner specialist was still finalising later pages, compressing the critical path significantly. **Q: How did you balance African heritage with global credibility?** A: The visual system drew from African design principles — geometric precision, bold structural forms and earthy tones — without leaning on decorative motifs. The result reads as proudly African and globally serious at the same time. **Q: How does the site perform on conference WiFi?** A: Animations were built with hardware-accelerated CSS and GSAP and tested specifically for the conference environment, so the experience held up on mobile devices over unreliable exhibition hall connections. --- ### Case study: Protego Ventures _Defense technology VC website built for authority and restraint_ **URL:** https://www.brandinglab.io/work/protego-ventures **Industry:** Venture Capital — Defense Tech **Stack:** Webflow, Finance, Brand Translation **Timeline:** 4 weeks **Challenge:** Most VC websites go too clinical or overcorrect into aggressive design. Protego needed authority through restraint — every element had to communicate precision, not noise. Three weeks of colour exploration alone were needed to get the exact beige that held the weight of CAPRI's design intent on screen. **Approach:** I directed monochromatic photography of defense technology hardware and structured navigation around three distinct visitor mental models: founders, LPs, and due-diligence evaluators. My specialist network built a utility-first class architecture for independent content management, with SEO foundations built in from day one — structured heading hierarchy and clean URL structure. **Results:** - Prospect Prep: Pre-meeting understanding - Build Time: 4 weeks - Navigation Iterations: 7 versions - Core Web Vitals: All green **Client quote:** "Working with BrandingLab was like finding a partner who could read our minds. They understood that in our world, subtlety and precision matter more than flash." — Protego Ventures, Founding Team **FAQs:** **Q: Why did Protego need 'authority through restraint'?** A: In defense-tech venture capital, credibility and discretion are non-negotiable. Most VC sites either go too clinical or overcorrect into aggressive design — Protego needed every element to signal precision rather than noise. **Q: How did you translate CAPRI's brand into Webflow?** A: I worked from CAPRI's existing visual identity and led the rebuild natively in Webflow — including three weeks of colour exploration to land on the exact beige that held the design intent on screen, and monochromatic hardware photography across the site. **Q: How does the navigation handle different visitor types?** A: I structured navigation around three distinct mental models — founders, LPs and due-diligence evaluators — and went through seven versions to make sure each audience reached the content they needed without friction. **Q: Were SEO foundations built in from day one?** A: Yes. Structured heading hierarchy, clean URL structure and Core Web Vitals were treated as first-class requirements — the launched site shipped with all Core Web Vitals green. --- ### Case study: CHRU _Rebuilding South Africa's leading HIV research unit website_ **URL:** https://www.brandinglab.io/work/chru **Industry:** Clinical Research & Healthcare **Stack:** Webflow, Healthcare, CMS **Timeline:** 6 months **Challenge:** Three distinct audiences — anxious patients, evaluating researchers, and assessing funders — arriving at the same site with entirely different needs. Navigation assumed prior knowledge, visual inconsistencies undermined credibility, and authority signals were buried. Patient pathways were unclear and anxiety-inducing. **Approach:** I spent weeks on information architecture mapping before any design work, then structured layered navigation around recognisable categories with each section serving its primary audience first. My specialist network built a Webflow design system of reusable components to ensure visual consistency structurally, with CMS collections for research, trials, team, and news giving the client's team full editorial independence. **Results:** - Audience Paths: 3 distinct journeys - CMS Independence: Full editorial control - Project Duration: 6 months - Content Sections: Research, Trials, Patient Info **FAQs:** **Q: How do you serve patients, researchers and funders on one site?** A: I mapped three distinct user journeys and structured layered navigation around recognisable categories, with each section serving its primary audience first — so patients aren't asked to read like researchers and vice versa. **Q: Why did the rebuild take six months?** A: Most of the early work was information architecture, not design. I spent weeks mapping content, audiences and patient pathways before opening a design tool, which is what made the launched site coherent rather than just refreshed. **Q: Can the CHRU team manage content without a developer?** A: Yes. My specialist network built CMS collections for research, trials, team and news inside a Webflow design system of reusable components — the client's team has full editorial independence while visual consistency is enforced structurally. --- ### Case study: Mind Ventures _4-month Webflow build with custom GSAP animation system_ **URL:** https://www.brandinglab.io/work/mind-ventures **Industry:** Value Creation & Investment **Stack:** Webflow, Finance, GSAP **Timeline:** 4 months **Challenge:** Financial services websites converge on the same stock photography, abstract language, and navy palettes. Mind Ventures' sophisticated clients — high-net-worth individuals and experienced operators — pattern-match for genericness as a signal of undifferentiated thinking. Animation needed to serve authority, not undermine it. **Approach:** I led the build of a custom GSAP animation system: scroll-driven text highlighting, staggered character entrance animations, subtle parallax, and crafted hover interactions. Typography mirrored the firm's intellectual approach — accessible at top level, progressively detailed deeper in. Animation hosted via GitHub/jsDelivr CDN with data-attribute targeting for CMS resilience. **Results:** - Discovery Phase: Multi-week - Animation System: Custom GSAP - Build Duration: 4 months - Meeting Quality: Prospects pre-informed **FAQs:** **Q: Why did the Mind Ventures project take four months?** A: The timeline reflected the depth of discovery required — understanding the firm's investment thesis, ideal client profile and competitive landscape thoroughly enough to design something that didn't pattern-match the rest of financial services. **Q: How does the GSAP animation system serve authority rather than distract?** A: Animations are restrained and purposeful: scroll-driven text highlighting, staggered character entrances, subtle parallax and crafted hover states. They reinforce the firm's intellectual rigour rather than performing for its own sake. **Q: How is the animation kept resilient when content changes?** A: Animation code is hosted on a GitHub/jsDelivr CDN and targets elements via data attributes, so editors can update copy and CMS items in Webflow without breaking the motion system. --- ### Case study: Voxeon Communications _Turning a whispering PR brand into one that shouts_ **URL:** https://www.brandinglab.io/work/voxeon-communications **Industry:** Public Relations **Stack:** Webflow, PR, Brand Expression **Timeline:** 4 weeks **Challenge:** Voxeon's fractional PR model — their key differentiator — wasn't explained on the site. Prospects arrived at meetings confused about what they were buying. The 'good guys' positioning wasn't visible, and the visual identity had implementation issues: poor contrast ratios, overused accent colour, inconsistent typographic hierarchy. **Approach:** I ran a forensic audit of the existing brand implementation, fixed contrast ratios throughout, and reserved the purple accent for specific functions only — CTAs, key data, selected emphasis — restoring its visual significance. I gave the fractional model prominent homepage placement with a plain-language explanation, and structured the CMS for easy content publishing. **Results:** - Meeting Quality: Prospects pre-informed - Client Self-Selection: Right-fit inbound up - Publishing Cadence: Monthly → Weekly - Build Time: 4 weeks **FAQs:** **Q: What was wrong with Voxeon's previous site?** A: The visual identity was strong on paper but poorly implemented — weak contrast, overused purple accent, inconsistent type hierarchy — and the messaging was cautious. For a PR agency, that quiet posture was actively losing business. **Q: How did you make the fractional PR model clearer?** A: We gave the fractional model prominent homepage placement with a plain-language explanation, so prospects arrive at the first meeting already understanding what they're buying instead of needing it spelled out. **Q: How did you fix the brand implementation issues?** A: I ran a forensic audit, fixed contrast ratios across the system and reserved the purple accent for CTAs, key data and selected emphasis only — which restored its visual significance instead of letting it go flat. --- ### Case study: Opsi Systems _Enterprise transportation technology website — built for credibility, authority, and the B2B buyer._ **URL:** https://www.brandinglab.io/work/opsi-systems **Industry:** Enterprise Transportation Technology **Stack:** Webflow, Enterprise, AEO **Timeline:** 4 weeks **Challenge:** Enterprise software buyers evaluate risk as much as they evaluate features. Opsi needed a website that would earn the trust of logistics directors, CIOs, and procurement teams in the first scroll — without a generic SaaS template, without startup energy, and without simplifying the technical depth of the product. The challenge wasn't just design. It was communication architecture: how do you present GPU-powered route optimization, ISO 27001 compliance, multi-fleet TMS, and 25 years of domain expertise to four different global buyer audiences in one coherent digital experience? **Approach:** I built opsisystems.com on a dark, authoritative visual foundation — a deliberate departure from the startup aesthetic. Every design and content decision was made around one question: what does an enterprise procurement team need to see to move forward? The content architecture was structured around buyer questions, not product features: Who is this company and how long have they been doing this? What does the platform actually do at enterprise scale? Can this handle our complexity — multi-fleet, multi-principal, global? Are they compliant with ISO 27001, GDPR, and POPIA? How do we start a conversation? I also implemented Answer Engine Optimization (AEO) — structuring every page with correct heading hierarchy, FAQ schema markup, and semantic content blocks so Opsi appears in AI-generated research answers, not just traditional search results. For Lottie animations, I generated custom files by feeding the site content into Claude Code and prompting it to build Lottie diagrams in line with the Opsi brand style — #0A0A1A background, orange accent — then exported them as lightweight JSON files and embedded them inline in Webflow via the Lottie Player component. **Results:** - Global Regions: 4 - Years Expertise: 25+ - Figma to Live: 4wks - AEO: Optimised - Active Users (90d): 406 - Organic Search Users: 69 - Contact Page Bounce: 12% - Delivery Page Bounce: 0% **Client quote:** "BrandingLab understood exactly what we needed — a website that communicates the weight and credibility of what we've built over 25 years. The result speaks for itself." — Opsi Systems Team, opsisystems.com **FAQs:** **Q: Why was Webflow chosen for an enterprise build?** A: Webflow gives Opsi Systems full CMS control with no ongoing developer dependency for content updates. It produces clean, semantic HTML that is both performant and structured correctly for SEO and AEO. For an enterprise company managing content across a global audience, that independence is critical. **Q: What is AEO and why does it matter for B2B companies?** A: Answer Engine Optimization (AEO) structures your website content so it appears in AI-generated answers from tools like ChatGPT, Perplexity, and Google's AI Overview. Enterprise B2B buyers increasingly use AI to research platform decisions before visiting any vendor website. AEO ensures Opsi Systems is part of those answers. **Q: How did BrandingLab handle the technical complexity of the product?** A: I built the content architecture around buyer questions rather than product features. Technical depth (GPU optimization, multi-principal fleet management) was framed in terms of what it means for the buyer's operation — not in engineering language. This makes the site accessible to procurement teams and technical evaluators simultaneously. **Q: How were the Lottie animations created?** A: The Lottie files were generated using Claude Code — I fed the site content into the AI and prompted it to build Lottie animations in line with the Opsi brand style. This produced bespoke, on-brand motion graphics without generic stock animation libraries. Each file was exported as lightweight JSON and embedded via Webflow's Lottie Player component. **Q: How long did the project take?** A: The full project — from Figma design to live published site — was completed in 4 weeks. This included Webflow design and development, AEO content architecture, custom Lottie animation generation, and CMS setup. **Q: Can BrandingLab build something similar for my business?** A: Yes. If you're running a B2B company that needs a website built for enterprise buyers — with Webflow, AEO strategy, and content architecture that earns trust — get in touch at brandinglab.io. --- ### Case study: Jabali Mining Services _Mining expertise at the scale of the machinery — a site built to feel the size of the operation, not just describe it._ **URL:** https://www.brandinglab.io/work/jabali-mining **Industry:** Contract Mining & Mineral Processing **Stack:** Webflow, Mining, Brand Expression **Timeline:** 4 weeks **Challenge:** The sector's visual convention actively works against companies that are good at the work. Buyers evaluating a contract miner are assessing capability and safety — but the standard mining website flattens fleet, blasting capability and rehabilitation practice into a bulleted list that reads identically to every competitor's. Jabali also runs a genuinely wide service line — open cast mining, drilling and blasting, load and haul, crushing and screening, bulk material handling, rehabilitation, equipment hire, quantity surveying, stockpile management, construction and operator training. Presented conventionally, that breadth reads as unfocused. Presented well, it reads as the reason you don't need three contractors. **Approach:** I designed the site around the physical reality of the operation rather than around a services taxonomy. The homepage opens on blast footage — a live detonation on the mine face — which sets the register for everything below it: heavy, controlled, expert work at scale. The services section pairs each capability with its own site photography and runs a sticky index down the left-hand side, so the visitor scrolls through the operation the way you'd walk it — men, machines and process in sequence — rather than clicking through a menu of abstractions. The brand meaning does structural work rather than decorative work: the Swahili derivation gets its own moment on the page, with pronunciation and translation, so the name becomes a positioning statement. The sustainability commitment is handled the same way — 'put back more than we extract' is treated as the operating principle, with rehabilitation presented as a planned discipline from before a mine opens. Video does the narrative work throughout, not just in the hero — mining is a process, and motion shows the sequence where static photography can only show a frozen instant of it. The drone and ground photography carried a substantial share of this, and the design decision that mattered most was giving it room: full-bleed, uncropped, at scale. Committing to that much video created the obvious constraint — the site had to stay fast on a mine site in southern Africa, on mobile, on a connection that isn't guaranteed. Assets were compressed and served at appropriate sizes per breakpoint, type was kept to system-safe stacks, and the responsive behaviour reflows the full-bleed treatment rather than abandoning it on small screens. **Results:** - Service Lines Documented: 11 - Commodities Mined: 10 - Projects Completed: 21 - Years' Experience: 30+ **FAQs:** **Q: How do you make a mining company website feel like the actual operation?** A: Scale has to be shown, not claimed. On Jabali we opened on live blast footage from the mine face and gave the drone and site photography full-bleed treatment at full scale. The alternative — cropping strong photography into small uniform cards — is what makes most industrial sites feel smaller than the businesses behind them. **Q: How do you present a wide service line without it reading as unfocused?** A: Sequence and continuity. Jabali's eleven service lines run as a single scrollable narrative with a sticky left-hand index that tracks position, so a visitor moves through the operation in a logical order instead of navigating a menu of abstractions. Breadth then reads as capability rather than dilution. **Q: Why does a brand's name matter to the website structure?** A: Jabali is Swahili for rock or outcrop — strong as rock. Rather than leaving that buried in an About page, the site gives the derivation its own moment with pronunciation and translation, which converts the name into a positioning statement a buyer actually remembers. **Q: Why Webflow for an industrial or mining business?** A: Webflow handles heavy video and image assets without a plugin stack, produces clean semantic HTML that indexes properly for both search and AI answer engines, and lets the client's team update project and service content without a developer on retainer. **Q: How do you keep a video-heavy site fast on poor connections?** A: Compress and serve assets at the size each breakpoint actually needs rather than shipping one large file to every device, keep type to system-safe stacks so nothing blocks first render, and make the responsive rules reflow full-bleed media instead of dropping it on mobile. On Jabali this mattered specifically because the audience includes people opening the site from a mine site on an unreliable connection. --- ## Articles ### Article: B2B Webflow Agencies: Global & US/UK Buyer's Guide (2026) **URL:** https://www.brandinglab.io/articles/best-b2b-webflow-agencies **Published:** 2026-09-16 **Read time:** 9 min read **Author:** Russel Shalom Davis, Founder, BrandingLab **Category:** Webflow **Key takeaways:** - Credible B2B Webflow studios sit in five lanes — engineering depth, brand and motion, ongoing operations, growth and AEO, and narrow specialists - Naming the lane you need eliminates most of a shortlist in ten minutes and matters more than picking the single "best" studio - Verify any partner tier in Webflow's own directory; "Webflow partner" on a homepage is a label, not a credential - Focused sites run $8,000–$15,000, full B2B builds $15,000–$40,000, enterprise builds $40,000 into six figures - Subscription pricing looks cheaper monthly and often costs more across a year — ask what a comparable project actually landed at - AEO is a build-time decision, so ask for a live AI citation rather than a framework name - Webflow is the wrong answer for application-like products, very deep localisation, or budgets under about $8,000 **Short answer:** the best B2B Webflow agencies fall into five lanes — engineering depth (Finsweet, Flow Ninja), brand and motion (Refokus, Edgar Allan), ongoing website operations (Webstacks, Flowout), growth, SEO and AEO (Veza Digital, Amply, BrandingLab), and narrow specialists. Full B2B builds typically cost $15,000–$40,000. Pick the lane that matches your problem first, then compare agencies inside it. If you are choosing a B2B Webflow agency, the problem is not a shortage of options. It is that every agency website says the same thing: conversion-focused, design-led, strategic partner. Twelve tabs open, no shortlist. This guide does something narrower. It sorts the studios working in B2B Webflow into five lanes, sets out what actually differs between them, and gives honest price ranges. We build [Webflow sites ourselves](/webflow-agency), so read the section about us accordingly. Everything else is drawn from each agency's own public positioning and from published comparison lists, and we have described competitors as they describe themselves. ### What is a B2B Webflow agency? A B2B Webflow agency builds marketing websites on Webflow for companies that sell to other businesses. The defining trait is the combination: Webflow as the platform, a long multi-stakeholder buying cycle as the context, and a marketing team that needs to publish without filing an engineering ticket. That is narrower than "Webflow agency" and broader than "Webflow developer". A developer takes your Figma file and builds it. An agency decides what should be built — information architecture, CMS structure, messaging, and increasingly whether AI answer engines can read the result at all. ### The five lanes Almost every credible studio sits in one of five lanes. Working out which lane you need takes ten minutes and eliminates most of your shortlist. **1. Engineering depth.** Complex CMS logic, custom integrations, technical migrations. The teams other agencies call when something is too hard to build. - **Finsweet** — Webflow Enterprise Partner, author of the widely used Client-First naming framework, known for deep CMS logic and custom API work. - **Flow Ninja** — positions around embedded "WebOps" for high-volume, multi-stakeholder sites, large multilingual builds and enterprise migrations. **2. Brand and motion.** Where the site itself is the differentiator and the budget reflects that. - **Refokus** — Enterprise Partner known for interactive, motion-led builds for design-forward brands. - **Edgar Allan** — premium brand storytelling at enterprise scale, and one of the most Webflow-awarded studios. **3. Ongoing website operations.** Not a project, a standing team. - **Webstacks** — positions specifically around website operations and ongoing management of a marketing site. - **Flowout** — flat monthly pricing with a large in-house team, aimed at continuous output rather than one-off builds. - **Creative Corner Studio** — fast-start builds and transparent retainer tiers, with migration as a stated specialism. **4. Growth, SEO and AEO.** The build is a means to pipeline, and search visibility sits inside the same engagement. - **Veza Digital** — Webflow builds tied to growth outcomes, with a published framework for AI search visibility. - **Amply** — B2B marketing sites built around scalable Webflow systems tied to SEO and long-term marketing ownership. - **BrandingLab** — B2B websites and [answer engine optimisation](/aeo-services), Webflow and AI-native React. Us. **5. Narrow specialists.** One vertical or one job, done unusually well. - **SVZ** — B2B SaaS positioning and demand-generation sites, strong on design systems. - **BRIX Agency** — focused on pricing-page and landing-page conversion mechanics. - **Omnius** — narrow SaaS specialisation with its own AI-search analytics tooling. Where to verify any of this yourself, rather than trusting a list — including this one: - [Webflow's own partner directory](https://webflow.com/partners/experts) — Certified and Premium are the vetted tiers, and an Enterprise distinction sits on top. Everything else on agency listicles is marketing. - [Clutch](https://clutch.co) — reviews are verified by interview. - The agency's own case studies. Named clients and live URLs, or it did not happen. ### What actually separates them? Capability lists are near-identical. The real differences sit elsewhere. | Dimension | What to ask | Why it matters | | --- | --- | --- | | Partner tier | Certified, Premium, or Enterprise? Verified where? | Tiers reflect assessed project volume and review history, not self-description | | Pricing model | Fixed project, retainer, or flat subscription? | Determines whether you can afford iteration after launch, which is where most value sits | | Who does the work | Are the senior people who pitched still on it in week six? | The most common complaint about larger agencies is the quiet handoff to juniors | | CMS ownership | Can marketing publish a case study without you? | The most common post-launch complaint is dependency on the agency | | Migration discipline | Show me your URL mapping and redirect plan | A sloppy migration quietly deletes years of search equity | | AI search visibility | Can you show a site you built being cited by ChatGPT or Perplexity? | Most B2B research now starts in an answer engine, and very few agencies measure this | The last row is the one that has changed most since 2024. Several studios now advertise AEO methodology inside the build. Ask for evidence, not a framework name: a live query, an engine, a citation. ### What does a B2B Webflow build cost? Published ranges across the market, by scope: | Scope | Typical range | What you get | | --- | --- | --- | | Focused marketing site | $8,000 – $15,000 | 5–8 pages, existing brand, light CMS | | Full B2B build | $15,000 – $40,000 | Strategy, design system, CMS architecture, migration, AEO foundations | | Enterprise build | $40,000 – $250,000+ | Multi-language, deep integrations, large migrations, multiple stakeholders | | Ongoing retainer | $2,500 – $10,000+/month | Continuous pages, experiments, content, iteration | Two things distort these numbers. Subscription studios quote monthly rather than by project, which looks cheaper per month and often costs more across a year. And "from" pricing on an agency site usually describes a smaller engagement than the one you are about to buy. Ask what a project like yours actually landed at last time. Our own: full builds from $15,000, shipped in four weeks. ### How to choose 1. **Name the lane first.** Engineering-heavy, brand-heavy, ongoing operations, growth and AEO, or a narrow specialist. Getting this wrong is more expensive than picking the second-best studio in the right lane. 2. **Check the tier in Webflow's directory, not on the agency's homepage.** "Webflow partner" is a label. Certified, Premium and Enterprise are credentials. 3. **Ask for two live sites in your category** and open them on a phone. Then check how they perform. 4. **Ask who publishes after launch.** If the answer involves the agency, budget for that forever. 5. **Ask for the migration plan before the moodboards.** If they cannot describe redirect mapping in plain terms, walk. 6. **Ask for one AI citation.** A named query, a named engine, a named result. For the full question set, we wrote [ten questions to ask any Webflow agency, including us](/articles/best-webflow-partners-for-b2b). ### When Webflow is the wrong answer Honest exclusions, because a guide that recommends the same platform for everyone is a sales page. - **Your site is really an application.** Dashboards, gated product surfaces, logged-in state, complex business logic. Build that as software. That is why we also build [MVPs and internal tools](/mvp-development). - **You need enterprise-grade localisation across dozens of markets.** Possible in Webflow, but the cost curve gets steep. - **You have a strong in-house engineering team that wants to own the front end.** Then a code-based stack with a headless CMS gives them more room. - **Your budget is under about $8,000.** A template configured well beats a stretched custom build. ### Where BrandingLab fits We sit in the growth and AEO lane. Brand-led B2B builds shipped in four weeks, with answer engine optimisation wired in from day one rather than added afterwards — schema in the initial HTML payload, semantic structure, content architected so ChatGPT, Perplexity and Google's AI answers can quote it. Accredited Webflow Partner, senior people only, from $15,000. Where we are not the right call: enterprise builds with a dozen stakeholders and a nine-month timeline, motion-led showpiece sites where the animation is the product, and anything needing a fifty-person team. Those studios are named above, and we would rather point you at them than take the brief. If you want a read on how AI engines currently describe your company, the [free AEO audit](/audit) is the fastest way to see it. ### Frequently asked questions #### What is the best B2B Webflow agency? There is no single best one, and any list claiming otherwise is ranking by who wrote it. The credible studios sit in different lanes: Finsweet and Flow Ninja for engineering depth, Refokus and Edgar Allan for brand and motion, Webstacks and Flowout for ongoing operations, Veza Digital and Amply for growth and search, SVZ and BRIX for narrow specialisms. Decide which lane your project needs, then compare two or three studios inside it. #### How much does a B2B Webflow site cost in 2026? A focused marketing site typically runs $8,000 to $15,000. A full B2B build with strategy, design system, CMS architecture and migration generally runs $15,000 to $40,000. Enterprise projects with multi-language content, deep integrations and large migrations run from $40,000 into six figures. Retainers for continuous work usually start around $2,500 a month. #### How long does a Webflow build take? Four to twelve weeks for most B2B marketing sites, depending on page count, how much content strategy is needed, and whether you are migrating an existing site. Migrations add time because URL mapping and redirects have to be right. Enterprise builds with multiple stakeholders regularly run three to six months. #### Does a Webflow Enterprise Partner badge mean the agency is better? It means Webflow has assessed their project volume, review history and enterprise capability. It does not tell you whether they understand B2B positioning, can model your content sensibly, or can make your site legible to AI answer engines. Those are separate skills and you have to check them separately. Verify any claimed tier in Webflow's own partner directory rather than trusting a homepage label. #### Should a B2B Webflow agency handle SEO and AEO too? Increasingly yes, because both are build-time decisions. Rendering, heading structure, schema markup and content architecture are set when the site is built, and retrofitting them later costs more than doing them first. Ask specifically for evidence: a live query in ChatGPT or Perplexity where a site they built is cited by name. #### Can our marketing team update a Webflow site without a developer? That is the main reason B2B teams move to Webflow, but it depends entirely on how the build is structured. A site built from a documented component library with well-modelled CMS collections lets a marketer publish pages and case studies unaided. A site hand-built page by page does not. Ask to see the CMS as an Editor would, not as a designer, before you sign. --- ### Article: Webflow Agencies in Israel: Local Buyer's Guide (2026) **URL:** https://www.brandinglab.io/articles/discover-leading-webflow-agency-israel-innovating-web-design-and-development **Published:** 2026-09-09 **Read time:** 8 min **Author:** Russel Shalom Davis, Founder, BrandingLab **Category:** Webflow **Key takeaways:** - Israel's market splits into specialist B2B studios, product consultancies and generalist agencies — establish which you are talking to first - Capability lists are identical everywhere; partner tier, bilingual experience, accessibility approach and AI visibility are what differ - Bilingual Hebrew/English work is genuinely difficult — ask for a live example - IS 5568 has been in force since 2017; an overlay widget is not compliance - Full B2B builds generally run $15,000–$40,000; focused builds start around $8,000 - Verify any agency independently through Webflow's own directory and Clutch If you are a B2B company in Israel choosing a Webflow agency, the hardest part is not finding one. It is working out how the options differ, because most agency websites describe the same capabilities in the same words. This guide names the studios working in Webflow and adjacent B2B web design in Israel, sets out what actually separates them, and explains what a build costs. We build [Webflow sites ourselves](/webflow-agency), so treat the section about us accordingly — everything else is drawn from public positioning and directory listings, and we have tried to describe competitors as they describe themselves. ### Who builds Webflow and B2B websites in Israel? The Israeli market splits into three groups, and confusing them is the most common mistake buyers make. **Specialist B2B web studios.** Small teams focused on B2B technology companies, usually combining brand, UX and Webflow build in one engagement. - **Hello. design** (Tel Aviv) — branding, UX/UI, product design and Webflow for B2B technology startups, with stated focus on cybersecurity, AI, developer tools, cloud infrastructure, fintech and enterprise software. - **Airfleet** — tech B2B websites positioned explicitly around pipeline generation, spanning design, development, SEO and CRO. - **BrandingLab** (Ramat Beit Shemesh, working internationally) — B2B websites and [answer engine optimisation](/aeo-services), Webflow and AI-native React. Us. **Product and UX consultancies that build websites as an adjacent service.** - **5IVE UX** — UX strategy, product design and user research for complex digital products including B2B SaaS. **Generalist digital agencies and directories.** Broad web design firms serving many sectors. Israeli directory listings frequently surface Butcher.studio, Moburst, Zissu, ARMOUR, Richkid, Leos Media, Marc Friedman Design and Magal Global, among others. Quality varies widely and Webflow is rarely their specialism. Where to look for yourself, rather than taking anyone's list on trust: - Webflow's official Tel Aviv directory: [webflow.com/hire/web-design/il/tel-aviv](https://webflow.com/hire/web-design/il/tel-aviv) — the only listing that verifies Webflow capability - [Clutch Israel web designers](https://clutch.co/il/web-designers) — reviews are verified by interview - TechBehemoths, GoodFirms and Sortlist — broader, less filtered - Israeli Webflowers — a community of Webflow designers and developers in Israel, useful for finding individuals rather than agencies ### What actually separates these studios? Capability lists are near-identical across agency websites. The real differences sit elsewhere. | Dimension | What to ask | Why it matters | | --- | --- | --- | | Webflow partner tier | Accredited, Certified, or Enterprise Partner? | Tiers reflect verified project volume and review history, not just self-description | | Bilingual and RTL | Have you shipped Hebrew/English sites? | Bidirectional layout, per-element dir and lang, mirrored focus order. Very few studios do this properly | | Accessibility | Do you build to IS 5568 / WCAG AA, or install a widget? | IS 5568 has applied since 2017. Overlay widgets do not deliver compliance | | AI search visibility | Can you show a site you built being cited by ChatGPT or Perplexity? | Most B2B research now begins in an answer engine. Very few agencies measure this | | What happens after launch | Can your marketing team publish without us? | The most common post-launch complaint is dependency on the agency for routine edits | | Who does the work | Who is actually on my project? | Small studios often mean the founder; larger ones often mean a delivery team | Two of these deserve expanding, because they are where Israeli buyers get caught. #### Bilingual sites are harder than they look An Israeli B2B site is usually Hebrew and English, which makes it bidirectional. Hebrew runs right-to-left, English left-to-right, and the two interleave inside single paragraphs — a Hebrew sentence containing an English product name or a Latin-script figure. Done properly this needs correct dir and lang attributes at document and element level, layout that mirrors rather than flips, focus order following reading order in both directions, and testing with a screen reader in both languages. Done improperly it produces sites that look right and are unusable with assistive technology. Ask for a live bilingual example. Not a mockup. #### Accessibility is a legal obligation in Israel, not a nice-to-have IS 5568 has required WCAG Level AA conformance since October 2017. Enforcement is unusually direct: fines reach NIS 50,000, and private individuals can bring claims without proving damages. We write about this in more detail in our guide to [nonprofit websites in Israel](/nonprofit-websites-israel). Many agencies answer this by installing an accessibility overlay widget. The evidence against that approach is public — WebAIM survey data found 2.4% of disabled users considered overlays effective, and in April 2025 the FTC required accessiBe to pay $1 million over claims that its widget could make any site WCAG-compliant. If an agency's accessibility answer is a widget, that is not compliance. ### What does a Webflow build cost in Israel? Published pricing is rare, so treat these as market shape rather than quotes. | Engagement | Typical range | | --- | --- | | Landing page or focused single-purpose site | $3,000–$8,000 | | Full multi-template B2B marketing site | $15,000–$40,000 | | Brand plus site, strategy through launch | $25,000+ | | Ongoing retainer | $2,500–$6,000/month | BrandingLab projects start from $8,000 for a focused build; full multi-template B2B sites start from $15,000. Most builds run as four-week sprints. Cheaper than this usually means a template with your logo on it. More usually buys brand strategy, custom motion or engineering complexity rather than more pages. ### How to choose 1. Ask for two live sites in your category, not a portfolio grid. Open them on a phone. Tab through them with a keyboard. 2. Ask who publishes content after launch. If the answer involves the agency, budget for that permanently. 3. Ask for a bilingual example if you need Hebrew. 4. Ask how they handle IS 5568. A widget is the wrong answer. 5. Ask what happens if you outgrow Webflow. Some sites eventually need an application framework; an agency that only builds Webflow will not tell you that. 6. Get fixed scope and price in writing before work starts. Hourly arrangements on marketing sites reliably overrun. ### Where BrandingLab fits — and where we don't We build B2B websites in Webflow and AI-native React, and we specialise in answer engine optimisation: structuring sites so ChatGPT, Claude, Perplexity and Google AI Overviews cite them. That is the part most agencies do not yet measure. The [Opsi Systems site we built](/work/opsi-systems) now receives referral traffic from claude.ai and gemini.google.com. Founded in 2019, we are an Accredited Webflow Partner based in Ramat Beit Shemesh, working internationally — clients in Israel, South Africa, the US, the UK and Europe. Recent work includes Opsi Systems (enterprise logistics technology, Johannesburg) and Targo Logistics in South Africa; Mind Ventures and Mosaic United, a nonprofit, in Israel; and Protego Ventures and Threadworks, delivered for Capri. Gazette Search is our own product — we build and market it ourselves, which is where a good deal of our AEO practice was worked out before we sold it to anyone. You work directly with me on strategy and every judgement call; specialist delivery comes from a vetted partner network. We are not the right choice if: - You want the cheapest possible site. We are not, and templates exist. - You need a large in-house delivery team for a multi-market enterprise rollout. Studios like Flow Ninja or Veza Digital are built for that shape of work. - You want pure product UX rather than a marketing site. A product consultancy will serve you better. - You need Hebrew-first brand copywriting. We build the bilingual site; we do not write Hebrew brand copy. Saying this costs us occasional work and saves everyone the wrong engagement. ### Frequently asked questions #### Who are the leading Webflow agencies in Israel? Studios working in Webflow and B2B web design in Israel include Hello. design, Airfleet and BrandingLab, alongside product consultancies such as 5IVE UX and a wide range of generalist digital agencies. Webflow's official Tel Aviv directory and Clutch's Israel listings are the most reliable places to verify capability independently. #### How much does a Webflow website cost in Israel? A focused single-purpose build typically runs $3,000–$8,000, and a full multi-template B2B marketing site generally runs $15,000–$40,000. BrandingLab projects start from $8,000, with full multi-template B2B sites starting from $15,000. #### What should I ask a Webflow agency before hiring them? Ask for their Webflow partner tier, two live sites in your category, a live bilingual Hebrew/English example if you need one, how they handle IS 5568 accessibility compliance, who publishes content after launch, and whether scope and price are fixed in writing before work begins. #### Do Israeli websites need to meet accessibility requirements? Yes. IS 5568 has required conformance with the Web Content Accessibility Guidelines at Level AA since October 2017. Fines reach NIS 50,000 and private individuals can bring claims without proving damages. #### Is an accessibility widget enough for an Israeli website? No. Overlay widgets modify a page after it loads without changing the underlying code assistive technology reads. WebAIM survey data found only 2.4% of disabled users considered overlays effective, and in April 2025 the FTC required accessiBe to pay $1 million over claims its widget could make any site WCAG-compliant. #### What makes bilingual Hebrew and English websites difficult to build? The content is bidirectional. Correct handling requires per-element language and direction attributes, layout that mirrors rather than flips, focus order that follows reading order in both directions, and screen reader testing in both languages. --- ### Article: Tabono Case Study: From Name to Brand to Website **URL:** https://www.brandinglab.io/articles/tabono-case-study **Published:** 2026-08-18 **Read time:** 5 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** Case Study **Key takeaways:** - Tabono, the African investment group, is named after the Adinkra symbol for "oar" — a symbol of unity of purpose, strength, confidence and hard work toward a destination. - The strongest brand names are concepts, not sounds: Tabono's name generated its logo, its values and its messaging without a separate exercise for each. - Russel Davis's role on Tabono ran from naming and logo concept through brand direction to the design of the current tabono.com website — the fractional creative director model over the life of one brand. - A good naming concept is tested years later, when the company outgrows the original deck — Tabono's oar still carries a group spanning mining, energy, minerals and logistics. - Fractional creative direction is the thread that keeps a brand coherent across different designers, redesigns and years — that continuity is the service, not any single deliverable. - When the name is a concept, a website redesign becomes a reinterpretation of the idea, not a reinvention of the company. Tabono, the African investment group behind mining, energy and logistics operations across the continent, is named after a symbol that means "oar." I found that symbol, proposed the name, and set the creative direction the brand still runs on today — through the original identity and, years later, the current tabono.com website. This is what fractional creative direction looks like over the life of one brand: different designers, different years, one accountable creative holding the concept. ### Where does a brand name actually come from? Not from a word generator. The brief was a South African investment firm with a clear promise — helping African businesses realise their full potential — and a conviction I stand behind: boring companies have boring names. So instead of shortlisting safe finance words, I went looking in the Adinkra symbols of West Africa, a visual language where each mark stands for a proverb or a value. One symbol stopped the search. **Tabono**: four paddles joined at the centre. It means "oar," and it stands for unity of purpose, strength, confidence and hard work to reach a destination. For an investment firm built on partnering — not just funding — it wasn't a name that suited the strategy. It *was* the strategy, compressed into three syllables. The proverb that anchored the original presentation made the same point: *if you want to go fast, go alone; if you want to go far, go together.* ### The logo I didn't draw I'll say this plainly, because case studies that blur credit are worthless: I did not produce the final logo artwork. Brand Smiths developed the finished logo and CI — the strategy phase ran as a BrandingLab collaboration with Jack Be Nimble. What I brought was the concept and the direction: the tabono symbol itself as the mark, rendered in orange against deep navy, sitting beside a clean wordmark with one orange accent on the T. That division of labour is how strong identities usually get made. The test of a logo concept is whether it survives someone else's hands. This one did, because it could be described in a single sentence before it was drawn: *the name is a symbol — use the symbol.* ### From name to brand system The rest of the brand fell out of the name rather than out of a values workshop. Unity and inclusion. Purpose. Hard work. Commitment. Those became Tabono's stated values because the symbol already meant them — the CI document, the palette (navy and orange), and the first website's positioning all extended one idea instead of inventing four. That's the practical payoff of concept-first naming: every downstream deliverable gets cheaper and more coherent, because nobody has to re-decide what the brand is at each step. I've written about treating a website as [a business system rather than a brochure](/articles/website-as-business-system) — the same logic applies a level up. A name can be a system too. ### Does the concept still hold years later? This is the only test that matters, and most naming case studies are written too early to run it. The company Tabono is today has outgrown the original deck several times over — the group now spans minerals and metals, energy, sourcing and procurement, logistics and transaction due diligence. The current website, which I designed together with Pelumi in Figma and which is live at tabono.com, looks nothing like the first one. It's bold and editorial: oversized type, "Where resources meet results" as the opening line, "Equity. Expertise. Experience." as the frame, and the tabono symbol used as a window cut into photography of the operations themselves. Different design language. Same oar. That's the point. When a name is just a sound, every redesign is a small identity crisis. When the name is a concept, a redesign is a reinterpretation — the idea stays, the expression moves with the company. ### What does a fractional creative director actually do? A fractional creative director owns the brand's creative decisions end to end without being a full-time hire — and Tabono is the long-form proof of what that ownership buys. The deliverables are easy to list: name, logo concept, identity direction, two websites. The service underneath them is the continuity — one senior creative holding the thread while Jack Be Nimble ran strategy alongside me, Brand Smiths executed the CI, and Pelumi built the current site with me. Direction is the constant; execution is cast per project. That's the model I run at BrandingLab — brand, build, ship, owned by one accountable creative — and it's the same discipline I apply when the client is me: the [Gazette-Search build](/articles/gazette-search-case-study) is the software version of this story. If your company has grown past its name, its identity, or the website wrapped around them, [talk to me](/contact). ### Frequently asked questions #### What does the name Tabono mean? Tabono is an Adinkra symbol from West Africa depicting four paddles joined at the centre. It means "oar" and represents unity of purpose, strength, confidence and hard work in reaching a destination or goal — which is why it was chosen as the name for the African investment group. #### Who created the Tabono brand? Russel Davis of BrandingLab developed the name, the logo concept and the creative direction, with the strategy phase run in collaboration with Jack Be Nimble; Brand Smiths developed the finished logo and CI. Years later, BrandingLab designed the current tabono.com website with Pelumi. #### What is the difference between brand naming and brand identity? Naming decides what the brand means; identity decides how that meaning looks and sounds. When the name itself carries a concept — as Tabono's does — the identity work becomes an extension of the name rather than a separate invention, which keeps the brand coherent as it grows. #### What is a fractional creative director? A fractional creative director is a senior creative who owns a brand's strategy, identity and expression on a part-time, embedded basis — directing the work across whichever designers and developers execute it. Tabono shows the model over years: the name, concept and direction stayed with one person while execution partners changed. #### Does BrandingLab handle everything from naming to website design? Yes. The model is brand, build, ship under one accountable creative — naming, brand concept and direction, identity development, and website strategy and design — delivered directly or by directing vetted partners, so one concept holds from first presentation to live site. --- ### Article: Investors and Buyers Ask AI First — Are You in the Answer? **URL:** https://www.brandinglab.io/articles/investors-and-buyers-ask-ai-first **Published:** 2026-08-17 **Read time:** 9 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** AI Search **Key takeaways:** - Investors and enterprise buyers increasingly form a shortlist inside an AI answer before they ever visit a company's website, which means the shortlist is decided before your site gets a turn. - Being absent from AI answers is a diligence problem for a venture-backed company, not only a marketing one, because the same tools are used to research a market and to research you. - AI systems answer from what they can extract about a company as an entity, so a startup that is only described inside its own marketing copy has little for them to work with. - Third-party corroboration — coverage, directories, customer evidence, founder bylines — is what makes an AI answer willing to name you alongside better-known competitors. - Absence compounds: every month you are missing from category answers is a month competitors accumulate the citations that make them the default answer. - The fastest structural fix is making your site machine-readable — server-rendered HTML, clear entity pages, and answer-shaped content — before spending on more traffic. - Run your own category query in ChatGPT, Perplexity and Google AI Overviews monthly; presence or absence in that answer is the metric, not rankings. A partner at a fund you want on your cap table types your category into ChatGPT the night before a first call. Not your company name — the category. "Who are the leading companies doing X for enterprise?" The model returns six names with a short line on each. Three of them are competitors you consider peers. Two you have never heard of. You are not in the list. Nothing about that interaction shows up in your analytics. No session, no referrer, no form fill. But by the time that partner opens your website — if they open it at all — the shortlist has already been formed somewhere you had no presence, and your site is being read as a check on a conclusion rather than as an argument for one. ### Why do investors and buyers start with AI instead of Google? Investors and buyers start with AI because a single answer replaces an hour of tab-opening. A category question that used to mean ten search results, five vendor sites and a comparison post now returns a synthesized shortlist with reasoning attached. For someone doing market mapping or early diligence, that is a straight time trade, and it is the same trade an enterprise buyer makes when they ask for "the main vendors for X and how they differ." The consequence is that the moment of selection has moved upstream. Your website used to be where a prospect decided whether you were credible. Now the answer engine decides whether you are considered, and the website only gets to confirm it. This is the fourth of [the six signs you've outgrown your website](/articles/six-signs-youve-outgrown-your-current-website), and it is the only one where the damage happens entirely off your property. ### What does this have to do with diligence? The same tools used to research your market are used to research you, which turns AI visibility into a diligence surface. An analyst preparing for a partner meeting will ask an AI system what your company does, who your competitors are, and what is publicly known about your traction. What comes back is assembled from whatever the system can find and corroborate — not from what your homepage claims. Two failure modes matter here. The first is silence: the system says little or nothing about you, which reads as a company that has left no trace in its own category. The second is worse — the system answers confidently with outdated or wrong information, describing the product you sold two pivots ago or attributing you to a category you deliberately left. Neither is fatal on its own. Both are small negative data points arriving at the moment you least want them, and both are invisible to you unless you go looking. For a venture-backed company there is a compounding version of this. Enterprise buyers your new headcount was hired to win run the same query. Senior candidates run it. Press run it. One structural gap produces the same absence across every audience the raise was supposed to unlock, which is why a post-raise site is better treated as a diligence artifact than as a marketing asset — and why fixing it belongs in the quarter after the close, not after the next board meeting. ### Why isn't our startup showing up in AI answers? Most startups are missing from AI answers because there is not enough about them, outside their own website, for a model to safely say. Answer engines assemble responses from sources they can retrieve and corroborate. A company described only inside its own marketing copy is a single unverified source; a company described in coverage, directories, customer case studies, partner pages and founder bylines is an entity the system can name with confidence. There is usually a technical layer underneath the visibility one. If your site is a client-rendered single-page app, crawlers that do not execute JavaScript receive an empty shell — I rebuilt brandinglab.io on an SPA and watched AI-search visibility disappear until we prerendered it. Thin or missing structured data, no clear page that defines what the company is, and content written as narrative rather than as answers all reduce what a system can extract. The full mechanics of how these engines select and cite sources are in [why your B2B website isn't showing up in AI search](/articles/b2b-ai-search-visibility). Newness is a factor but not an excuse. Young companies with clear positioning, real third-party coverage and machine-readable sites get named. Older companies with better funding and an opaque website do not. ### How is this different from an SEO problem? Ranking and being cited are different outcomes with different mechanics. A page can rank on the first page of Google and never be quoted in an AI answer, because the answer is drawn from content that can be extracted as a direct response and attributed to a recognizable entity. Position is about competing for a click; citation is about being the most usable, most corroborated source for a specific claim. The practical difference shows up in what you fix. SEO work pushes a page up a list. AI visibility work makes your company legible as an entity and your content extractable as answers — clear definitional pages, question-shaped headings with the answer in the first sentence, consistent naming across the web, and structured data that connects it all. Google's own AI Overviews sit between the two disciplines, which is why they deserve separate treatment; that is covered in [AI Overview optimization for B2B](/articles/ai-overview-optimization-for-b2b). ### What does the absence cost while you wait? Absence compounds, because the systems that answer these questions get more confident about the companies they already cite. Every month a competitor is named in category answers is a month of accumulating references, mentions and corroboration that make naming them the safe default next time. You are not standing still relative to them; you are falling behind at the rate they are being cited. The cost is also hard to see in the only place founders usually look. There is no line in the analytics for a fund that never called or a buyer who never made the shortlist. What you observe instead is a pipeline that feels harder than the market suggests it should be, and inbound interest that skews toward people who already knew your name. The pattern is consistent with a company that is fine at converting the demand it sees and absent from the moment demand is being shaped. ### What should we actually do about it? Fix what a machine can read before you spend on more traffic. Make sure your pages are served as full HTML rather than assembled in the browser, that you have a clear page defining what the company is and who it serves, and that your highest-intent pages answer the questions buyers actually type — with the answer in the first sentence, not the fourth paragraph. This is unglamorous infrastructure work and it is the part that gates everything else. Then build the corroboration. Get named accurately in the places a system can verify: category directories, partner and customer pages, analyst and press coverage, founder writing published somewhere other than your own blog. Consistency matters more than volume — the same company name, the same category language, the same one-line description everywhere. A step-by-step version of this is in [how to show up in ChatGPT and Perplexity](/articles/how-to-show-up-in-chatgpt-and-perplexity). ### What to do first Run the query your investors and buyers would run. Open ChatGPT, Perplexity and a Google search that triggers an AI Overview, and ask each one for the leading companies in your category — the way someone who has not heard of you would ask. Then ask each one directly what your company does. Save the answers. Three outcomes, three responses. If you are absent, the gap is corroboration and machine-readability, in that order. If you are named with wrong information, the gap is a stale, contradictory footprint that needs correcting at the source. If you are named accurately, note the date and re-run it monthly, because the answer will drift. [Talk to BrandingLab](/contact) — we help venture-backed teams rebuild sites so they hold up in AI search and in diligence, and you can see the kind of work we mean on our [case studies](/work). ### Frequently asked questions #### Do investors really use ChatGPT and Perplexity for diligence? They use them the way anyone doing research uses them — for fast market mapping, competitor lists and background on a company before a first call. It is not a replacement for formal diligence, but it shapes the shortlist and the first impression that formal diligence starts from. The risk is not that an AI answer decides your round; it is that it decides whether you are in the conversation. #### Why is our startup missing from AI answers when our site ranks fine on Google? Ranking and being cited are different outcomes. Search ranking rewards pages competing for a click; AI answers draw on content that can be extracted as a direct response and attributed to a company the system recognizes across multiple sources. A site with good rankings but thin third-party corroboration, or one that renders in the browser rather than serving full HTML, is often invisible to the systems generating those answers. #### How long does it take to become visible in AI search? The technical work — server-rendered HTML, structured data, answer-shaped content — can be done in weeks and is what makes everything else possible. The corroboration layer takes longer, because it depends on third parties describing you accurately, and it accrues over months. Teams usually see changes in AI answers first for specific, narrow queries about their own company, and later for broad category questions. #### What if the AI answer describes our company incorrectly? Wrong information usually means the systems are drawing on stale sources — an old about page, an outdated directory listing, coverage from a previous positioning. Fix it at the source: update your own definitional pages first, then the third-party listings and profiles that repeat the old description. Consistency across sources is what eventually overwrites the old answer. #### Is this a marketing problem or an engineering problem? Both, and that split is why it stalls. The extractability and rendering issues are engineering work; the positioning, entity clarity and answer-shaped content are marketing work — and neither team owns the outcome by default. On a site where marketing cannot restructure pages without an engineering ticket, the fix moves at the speed of the sprint queue rather than the speed of the problem. #### Do we need to be a well-known brand to get cited? No — recognition helps, but what these systems need is corroboration, not fame. A young company with clear positioning, consistent naming across the web, real customer evidence and a machine-readable site gets named more reliably than a better-funded competitor with an opaque site and no third-party footprint. Specificity is an advantage here: it is easier to be the cited answer for a narrow category than a broad one. #### How do we measure AI search visibility? Presence or absence in the answer is the metric. Run your 20 most important category and company queries in ChatGPT, Claude, Perplexity and Google AI Overviews on a fixed monthly schedule, three times each, and log what comes back. Track whether you are named, whether the description is accurate, and which competitors appear alongside you. You can run this check by hand or have BrandingLab monitor it weekly; either way it is closer to reading a shortlist than to reading a rankings dashboard. *BrandingLab is a B2B website and AI studio and an accredited Webflow Partner — we help venture-backed teams build sites that hold up in AI search and in diligence.* --- ### Article: Pipeline Plateaued? It Might Be a Website Problem **URL:** https://www.brandinglab.io/articles/pipeline-plateau-website-problem **Published:** 2026-08-16 **Read time:** 8 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** Web Strategy **Key takeaways:** - A pipeline plateau with steady traffic is usually a conversion problem, and the website owns most of the conversion between a click and a booked call. - When traffic holds but demos fall, the leak is in the stretch the website controls — landing on the site and deciding to book. - A/B tests optimize the surface of a page; they cannot fix a funnel whose structure sends the wrong buyer down the wrong path. - Rising CAC on flat conversion means you are paying more to push traffic into the same leaky funnel, not that the channel has stopped working. - The plateau shows up first as longer sales cycles and more unqualified demos, because the site is not filtering or convincing before the call. - A website only a developer can restructure cannot keep pace with what you learn about the funnel, so the plateau hardens instead of lifting. - If you have A/B tested for two quarters and conversion is still flat, the problem is the structure, not the button. The dashboard on the board deck looks healthy: traffic up and to the right, three straight quarters of growth in sessions. The next slide is the problem. Demos booked, flat. Qualified pipeline, flat. And the number nobody wants to explain out loud — cost to acquire a customer — creeping up every quarter. More people are arriving, the same number are converting, and you are paying more for each one. A pipeline plateau while traffic still grows is almost never a top-of-funnel problem. It is a conversion problem, and the website owns the part of the funnel where conversion is won or lost — the stretch between landing on the page and deciding to book a call. When that stretch stops working, more traffic just means a bigger crowd walking past the same locked door. ### Why has our pipeline plateaued when traffic is still growing? A plateau with rising traffic means your funnel is converting a shrinking share of a growing crowd, and the website is where most of that share is decided. Ad spend and content can pull more visitors in, but the site is what turns a visitor into a booked call. If acquisition keeps improving while pipeline stays flat, the constraint has moved downstream — out of the channel and onto the page. This is the third of [the six signs you've outgrown your website](/articles/six-signs-youve-outgrown-your-current-website), and it is the one that hides the longest, because every top-line metric that leadership watches still looks fine. Sessions grow, so marketing reports a good quarter. Pipeline is flat, so sales reports a hard one. The two teams describe different companies, and the disconnect between them is the website nobody is looking at. ### Where exactly is the funnel leaking? The leak is in the stretch the website controls: the path from landing on the site to booking a call. Traffic gets someone to the page; the page has to qualify them, convince them, and route them to a next step. When that middle section is built for an earlier, smaller company, higher-intent visitors arrive and bounce because the site answers the questions last year's buyer had, not the ones this year's buyer is asking. You can see it in the shape of the demos, not just the count. Sales cycles get longer because prospects show up to calls under-informed — the site didn't do the pre-selling it should. More demos are "just browsing" because nothing on the page filtered out the wrong-fit visitors before they booked. The funnel is a system, and when one section is structurally wrong the whole thing under-converts — the case for treating the site that way rather than as a set of pages is in [your website is a business system](/articles/website-as-business-system). ### Why can't A/B testing fix a conversion plateau? A/B testing optimizes the surface of a page and cannot change the structure underneath it. Button color, headline wording, and hero image are surface variables; which buyer the page speaks to, in what order it makes its argument, and where it asks for the booking are structural ones. If the structure sends a VP-level buyer down a path built for a practitioner, no amount of testing the call-to-action copy will fix the mismatch — you are optimizing a route that leads to the wrong place. There is a math reason the tests stall, too. A/B testing needs volume to reach significance, and most B2B sites converting a few hundred demos a quarter never gather enough signal to validate small tweaks — so teams run tests for months and read noise as results. Two quarters of flat conversion after a testing program is not bad luck; it is the tool telling you the problem is a size it can't touch. The fix is to rebuild the path, then test at the margins. ### What does the plateau cost a venture-backed company? A conversion plateau shows up on the board deck as rising CAC, and rising CAC is the metric that turns a website problem into a fundraising problem. When conversion is flat and you push more spend through the same funnel, cost per customer climbs by definition — you are buying more traffic to win the same number of deals. The board sees the CAC line, asks why efficiency is dropping, and the honest answer is often that the site is leaking, though that is rarely where anyone looks first. For a venture-backed company the timing makes it worse. Growth-rate and efficiency expectations reset upward the moment you raise, and a plateau that would have been tolerable pre-round becomes the thing the next diligence process probes. Every quarter the funnel leaks, you compensate with spend, and the CAC that spend produces becomes a data point in your next raise. Meanwhile the same structural weakness usually cannot be fixed fast, because changing the funnel means changing the site — and if every change needs an engineering ticket, the plateau hardens while you wait in the queue, which is [the real cost of a dev-dependent website](/articles/dev-dependent-website). ### What does fixing it actually involve? Start by finding the structural leak, not by testing the surface. Map the real path from a high-intent landing to a booked call and ask, at each step, whether the page qualifies the current buyer and answers the current objection. The fix is usually a rebuild of that path — the messaging, the order of the argument, the proof, and the placement of the booking — for the buyer you are chasing now, not the one the site was built to convert. Then build it so you can keep tuning it without a developer in the loop. The reason plateaus recur is that teams learn something about the funnel and can't act on it for a sprint or two; a site marketing can restructure directly is what lets the funnel keep improving after launch. A focused B2B version of this runs 8–12 weeks, the range we walk through in [what a B2B website rebuild actually looks like](/articles/b2b-website-rebuild-process), with the conversion path — not the visual design — as the part that earns the work. ### What to do first Pull two numbers next to each other: total sessions over the last four quarters, and demos booked over the same period. If the first is climbing and the second is flat, you have a conversion plateau, and the website is the first place to look — not the ad channel. Then walk your own site as a first-time, high-intent buyer would: land on a paid page, and count how many steps and unanswered questions sit between you and a booked call. If the path is longer or vaguer than it should be, that gap is your rising CAC in slow motion. [Talk to BrandingLab](/contact) — we help venture-backed teams rebuild the conversion path so more of the traffic you already pay for turns into pipeline, and you can see the kind of work we mean on our [case studies](/work). ### Frequently asked questions #### Is a pipeline plateau always a website problem? Not always, but if traffic is still growing while demos and pipeline stay flat, the website is the most likely cause, because it owns the conversion between a click and a booked call. Rule out the obvious first: a change in traffic quality, a pricing shift, or a sales-capacity constraint can all flatten pipeline too. If acquisition metrics look healthy and conversion is what's stuck, the site is where to look. #### How do I tell the difference between a traffic problem and a conversion problem? Compare sessions and booked demos over the same multi-quarter window: a traffic problem shows both falling together, a conversion problem shows sessions rising while demos stay flat. Rising cost per acquisition alongside flat conversion is the clearest signal that you're paying more to push traffic through a leaky funnel. Once you know it's conversion, the website and the funnel structure are the first things to examine. #### Why won't A/B testing fix our conversion rate? A/B testing changes surface elements — copy, color, layout — but a plateau is usually caused by structure, such as which buyer the page argues to and where it asks for the booking. Most B2B sites also lack the traffic volume to reach statistical significance on small tests, so months of testing produce noise rather than answers. When the underlying path is wrong for your current buyer, you have to rebuild the path, then test at the edges. #### How does a conversion plateau affect our CAC and fundraising? A flat conversion rate forces you to buy more traffic to win the same number of customers, which mechanically raises cost to acquire a customer over time. That rising CAC becomes a line the board questions and a metric your next raise scrutinizes, since efficiency expectations climb after a round. Fixing the funnel leak is often a faster CAC improvement than optimizing ad spend, because it lifts conversion on all the traffic you already pay for. #### We just raised — why is the plateau showing up now? A raise resets growth and efficiency expectations upward, so a plateau that was survivable before becomes the number everyone watches after. The capital is meant to move you up-market, which sends higher-intent, more senior buyers to a site built to convert an earlier audience — widening the exact gap that causes the leak. Post-raise is when the conversion path most needs to match the company you've become. #### How long does it take to fix a website conversion plateau? Diagnosing the structural leak takes days; rebuilding the conversion path is typically part of a focused 8–12 week B2B rebuild. The timeline depends on how much of the messaging and structure has to change versus how much still fits the current buyer. Building the new site so marketing can keep tuning the funnel without engineering is what keeps the plateau from returning after launch. #### Should we rebuild the whole site or just the pages that convert? If the plateau is isolated to a few high-intent pages and the rest of the site still fits your buyer, start with the conversion path and leave the rest. More often the same structural mismatch runs across the site, because it was all built for an earlier company — in which case a focused rebuild of the funnel and the pages around it is faster than patching page by page. The diagnostic is whether the leak is one broken step or a whole path built for the wrong buyer. *BrandingLab is a B2B website and AI studio and an accredited Webflow Partner — we help venture-backed teams rebuild the conversion path so the traffic they already pay for turns into pipeline.* --- ### Article: Repositioned But Your Website Still Pitches Last Year **URL:** https://www.brandinglab.io/articles/repositioned-but-your-website-hasnt **Published:** 2026-08-03 **Read time:** 8 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** Web Strategy **Key takeaways:** - Repositioning is a decision the company makes internally; the website is where the market finds out — and most sites find out last. - A site that still pitches last year's company forces sales, founders and recruiters to compensate live, which is positioning debt accruing interest. - The clearest tell is that your best salespeople no longer send prospects to the homepage before a call. - Investors read a mismatch between the pitch deck and the website as a signal that the new story isn't real yet. - AI answer engines keep describing your old positioning until the source they read — your site — actually changes. - The fix starts with messaging, not design: a restyle of the old argument leaves the positioning gap intact. - If you can name the day the strategy changed but not the day the site did, the site is the thing lagging. Your company repositioned six months ago. Pricing moved up-market, the ideal customer changed from a team lead to a VP, maybe the category name itself is different now. Everyone internal knows this. The pitch deck knows it, the sales team knows it, the board knows it. Your website does not. It still opens with the headline you wrote for the company you used to be. Repositioning is a decision you make in a room. The market finds out through your website — and the website is almost always the last asset to catch up. That lag has a cost, it compounds, and it is quietly paid by everyone who has to work around a homepage that argues for last year's company. ### Why does repositioning leave the website behind? Repositioning changes strategy faster than it changes assets, and the website is the heaviest asset to move. A deck gets rewritten in an afternoon; a homepage, product pages, and the messaging underneath them do not. So the strategy ships, the sales narrative updates on the next call, and the site stays frozen at the last version everyone agreed on — often the one built during the previous fundraise or launch. The gap hides because the people closest to it stop reading the site. Founders and sales leaders internalize the new positioning so completely that they forget the homepage still says the old thing. The market hasn't forgotten. Every first-time visitor is reading the old story as if it were current. ### How do I know my website is behind our positioning? The clearest tell is that your best salespeople no longer send prospects to the homepage before a call. When the site undersells or mis-sells the company, the people whose job depends on the pitch route around it — they lead with a deck, a Loom, a personal explanation. That workaround is the symptom. A few more signs, in plain terms. Your sales deck and your homepage describe two different companies. You catch yourself saying "ignore the website, here's what we actually do" on calls. New hires get their understanding of the company from onboarding docs, not the public site. And the case studies or logos featured up front are from the customer you're moving away from, not the one you're moving toward. Any one of these means the site is lagging the strategy. This is the second of [the six signs you've outgrown your website](/articles/six-signs-youve-outgrown-your-current-website), and for repositioning companies it's usually the loudest. ### What does an out-of-date site actually cost between now and the rebuild? A stale site turns positioning debt into interest the rest of the go-to-market pays every week. Every person who has to compensate for the homepage — the rep building a custom deck, the founder over-explaining on a call, the recruiter sending a Notion doc instead of a careers page — is spending time to patch a gap the site should be closing for free. None of it shows up as a line item, which is exactly why it runs unchecked. The mechanics of that hidden cost are the same ones behind [the real cost of a dev-dependent website](/articles/dev-dependent-website): work that should be self-serve gets done by hand, repeatedly. Two costs are sharper for venture-backed companies. The first is diligence. Investors evaluating your next round read a mismatch between the pitch deck and the public site as a tell — either the new positioning isn't real yet, or the company can't execute on its own story. The second is AI search. Answer engines describe you based on what they can read, and the freshest thing they can read is your site; until it changes, ChatGPT, Perplexity and Google's AI Overviews keep repeating your old category and old value prop to anyone researching you — the reasons for that are in [why your B2B website isn't showing up in AI search](/articles/b2b-ai-search-visibility). You can reposition in every room you walk into and still be described as the old company in the rooms you're not in. ### Doesn't a repositioning just need new copy on the homepage? New copy on the old structure is the most common repositioning mistake, and it rarely holds. Repositioning usually moves who you sell to and what you claim to be — a VP instead of a practitioner, a platform instead of a tool, a new category instead of a feature. That changes what the site has to argue, in what order, with what proof. Swapping the hero headline while the page structure, the navigation, and the proof points still serve the old buyer leaves you with a site that contradicts itself halfway down. The website is one of the places positioning becomes real, alongside pricing and product — the argument for treating it as a system rather than a brochure is in [your website is a business system](/articles/website-as-business-system). A genuine repositioning earns a genuine rebuild of the argument, not a reskin of it. ### What does fixing it involve? Start from the new positioning and let the site follow, in this order. Write down who the company sells to now and what it claims to be — the actual repositioning, not a softened version. Rebuild the messaging around that buyer and that claim first, before anyone touches design. Then let structure, proof and copy flow from the new argument: the pages a VP needs, the case studies that match the customer you're winning now, the category language you want to own. Build it so the next repositioning doesn't strand you again. Companies that reposition once usually reposition again, and a site only marketing can update — without an engineering ticket for every change — is what keeps the message current between the big rebuilds. A focused B2B version of this runs 8–12 weeks, the range we walk through in [what a B2B website rebuild actually looks like](/articles/b2b-website-rebuild-process), with the messaging work as the long pole rather than the design. ### How do I test whether my site has caught up? You can run this in ten minutes with your current pitch deck open next to your homepage. No developer needed. 1. **Read the first screen of each.** For the deck and the homepage, write down three things: who it is for, what category it puts you in, and the one claim it makes. 2. **List the logos and case studies on the homepage.** Mark each one: the customer you are chasing now, or the one you are moving away from? 3. **Ask the answer engines.** In ChatGPT and Perplexity, type "What does [your company] do, and who is it for?" Write down the buyer and category each one names. **How to read it.** If all three match — same buyer, same category, same claim across the deck, the site and the AI answers — the site has caught up, and whatever is slowing pipeline lives somewhere else. If the deck and the homepage disagree, the site is lagging the strategy, and that is the gap your sales team is patching by hand. If the site matches the deck but the AI answers still describe the old company, the change is too recent or too shallow for crawlers to pick up; re-run the check in a few weeks, and make sure the new pages are readable without JavaScript. If most of the logos belong to the old customer, the proof is still arguing for the company you used to be, even where the copy is new. **What this test can't tell you.** It shows whether there is a gap, not what the new argument should be. It won't tell you which pages a VP buyer needs, what order to make the case in, or which proof will land with them — and it can't tell you whether the positioning itself is settled enough to build on. That is messaging work, and it is where a rebuild starts. If the test shows a gap, [talk to BrandingLab](/contact) about rebuilding the site around the company you've become, or see the kind of work we mean in our [case studies](/work). ### Frequently asked questions #### How do I know if our website is behind our positioning? The fastest check is whether your salespeople send prospects to the homepage before a call — if they route around it with a deck or a personal explanation, the site is lagging. Other tells: the homepage and the pitch deck describe different companies, new hires learn what you do from onboarding docs rather than the public site, and the featured customers are the ones you're moving away from. Any single one of those means the strategy has moved and the site hasn't. #### We already updated the homepage copy — is that enough? Usually not, because repositioning changes who the site argues to, not just the words on the first screen. If pricing, ICP or category moved, the page structure, navigation and proof points underneath still serve the old buyer, and new copy on top of them creates a site that contradicts itself. New copy is enough only when the positioning shift is small; a real repositioning needs the argument rebuilt, not restyled. #### How does an outdated website affect fundraising? Investors read a gap between your pitch deck and your public website as a signal — either the new positioning isn't real yet or the team can't execute on it. During diligence they check whether the story you're pitching matches the one the market can see, and a site two strategies behind becomes a small negative data point at the worst moment. Aligning the site to the current story before you raise removes an easy objection. #### Why does AI search still describe our old positioning? Answer engines describe you based on the sources they can read, and your website is the most authoritative and current one they have. Until the site actually changes, ChatGPT, Perplexity and AI Overviews keep repeating your old category and value proposition to everyone researching you. Updating the site is what updates the answer — there's no separate switch for the AI description. #### How long does it take to realign a website after repositioning? A focused B2B rebuild runs roughly 8–12 weeks from discovery to launch, with the messaging and positioning work as the long pole rather than the design or build. If only the copy and a few pages need to change and the underlying structure still fits, it can be faster. The timeline depends far more on how settled the new positioning is than on the engineering. #### Should we wait until the repositioning is fully settled before rebuilding? If the core of the new positioning — who you sell to and what you claim to be — is decided, the site should reflect it now, even if details are still moving. Waiting for total certainty usually means the old site stays live through the exact period when the most people are forming a first impression of the new company. Build for the positioning you've committed to; refine the edges as they firm up. #### Is this just a bigger company problem, or does it apply to startups too? It applies most sharply to startups, because early-stage companies reposition more often and have the least slack to absorb the cost. A seed or Series A company that shifts ICP or category is asking every investor, buyer and candidate to judge it on a site built for a different plan. The smaller the team, the more expensive it is to have people compensating for the website by hand. *BrandingLab is a B2B website and AI studio and an accredited Webflow Partner — we help venture-backed teams rebuild the site to match the company they've repositioned into.* --- ### Article: Your Website After You Raise: The Post-Funding Rebuild **URL:** https://www.brandinglab.io/articles/website-after-you-raise **Published:** 2026-07-27 **Read time:** 7 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** Web Strategy **Key takeaways:** - A raise changes your audience before it changes your product, and the website is the first thing the new audience sees. - The people who land on your site after a round — next-round investors, enterprise buyers, senior candidates — are higher-stakes than the traffic the old site was built for. - The strongest window for a rebuild is the first quarter after closing, when budget, mandate and momentum all exist at once. - A post-funding website is a diligence artifact: it is read as evidence of how the company operates, not just as marketing. - Positioning debt compounds — every month the site pitches the pre-raise company, sales decks and founders quietly paper over the gap. - A focused B2B rebuild runs 8–12 weeks, which means starting at close puts a current site in front of the next raise, not after it. - Rebuild for the company you just became, not the one you were when you wrote the last homepage. A term sheet closes and, within a week, three groups of people who never visited your website start visiting it: the investors who might lead your next round, the enterprise buyers your new headcount is hired to win, and the senior candidates deciding whether to leave a safe job for yours. All of them land on the site you built for a smaller, earlier company. Raising money resets the bar overnight. Rebuilding the website is not a victory-lap indulgence to schedule for "once things calm down" — it is one of the highest-leverage things you can do in the first quarter after a close, and one of the cheapest to get wrong by waiting. ### Why does raising money change what your website needs to do? A raise changes your audience before it changes your product. The capital is meant to move you up-market — bigger deals, more senior buyers, a category you now claim to lead — and every one of those people forms a first impression on the same homepage that converted early-adopter traffic a year ago. The site was tuned for a company that no longer exists. The gap is rarely about visual polish. It is about who the site is arguing to. A pre-raise site talks to a practitioner who already feels the pain. A post-raise site has to also convince an economic buyer, a procurement reviewer, and an investor doing pattern-matching — audiences the early site never had to satisfy. ### Who actually looks at your site after a raise? Four audiences arrive after a round, and none of them are the traffic your funnel was built for. Next-round investors check your site before a first call and again during diligence — the homepage, the team page, and whether the story matches the deck. Enterprise buyers, the ones your new sales hires are chasing, treat the website as the first trust test before they will take a meeting. Senior candidates weighing your offer read the site as a signal of whether the company is real. And analysts and press, newly interested because you just raised, quote whatever the site says you are. These are higher-stakes visitors than the self-serve early adopters who forgave a rough edge because the product solved their problem. A CFO evaluating a six-figure contract does not extend that grace. ### Isn't a rebuild a distraction right after a raise? The quarter right after closing is the best window a company gets for a rebuild, not the worst. Three things line up only briefly: the budget exists because you just raised, the mandate is unambiguous because the round is explicitly about scaling, and the whole team has momentum. Wait two quarters and the money is committed to headcount, the mandate has fragmented into competing priorities, and "the website" becomes the thing everyone agrees is embarrassing but no one owns. There is also a sequencing argument. A focused B2B rebuild runs roughly 8–12 weeks — the realistic range we walk through in [what a B2B website rebuild actually looks like](/articles/b2b-website-rebuild-process). Start at close and you have a current site in front of buyers and next-round investors within a quarter. Start "later" and the old site is still live during the exact stretch when the most consequential people are looking. ### What does the old site cost you between now and then? Positioning debt compounds — every month the site pitches the pre-raise company, the rest of the go-to-market quietly pays interest. Sales builds custom decks to say what the homepage doesn't. Founders over-explain on calls to bridge the gap between the story they're telling investors and the one the site is telling everyone else. Recruiters send candidates a Notion doc instead of a careers page because the real one undersells the company. None of that shows up as a line item, which is exactly why it runs unchecked. Two specific costs are worth naming. The first is diligence: a post-funding website is read as evidence of how the company operates, and a stale, dev-blocked, or thin site becomes a small data point in a much larger judgment. The second is AI search. Investors and enterprise buyers increasingly open ChatGPT or Perplexity to build a category shortlist before they open a browser tab, and a site that is invisible to those systems is absent from the exact research that forms the shortlist — the mechanics of that are in [why your B2B website isn't showing up in AI search](/articles/b2b-ai-search-visibility). Absence there compounds week over week, silently. ### What does a post-raise rebuild actually involve? Start with positioning, not design — the rebuild is a chance to make the site argue for the company you just became. Re-anchor the messaging to the up-market buyer and the category you now claim, then let structure, copy and design follow from that. The common mistake is to brief a "refresh" that restyles the old argument; the money bought you the right to make a bigger one. Build it so marketing can run it without engineering. Post-raise, your engineers are the most expensive people to have editing landing pages, and every hour they spend on the marketing site is an hour off the roadmap the raise is supposed to fund — the case for a marketing-led setup is in [the real cost of a dev-dependent website](/articles/dev-dependent-website). A site your team can update in hours, not sprints, is what keeps the rebuild from going stale by your next board meeting. If you're not sure the timing is right, the diagnostic is [the six signs you've outgrown your website](/articles/six-signs-youve-outgrown-your-current-website) — a fresh raise is the first and clearest of them. ### What to do first Look at your own site the way your next lead investor will. Open the homepage and ask whether it describes the company in your last board deck or the one from two rounds ago. Check the team and careers pages against who you're hiring now. Then run your category through ChatGPT and Perplexity and see whether you're named at all. If the answer to any of those is uncomfortable, that is the signal. [Talk to BrandingLab](/contact) — we help venture-backed teams rebuild the site to match the company the raise turned them into, and you can see the kind of work we mean on our [case studies](/work). ### Frequently asked questions #### When should we rebuild our website after raising a round? Ideally in the first quarter after the close, while budget, mandate and momentum all exist at once. A focused B2B rebuild takes 8–12 weeks, so starting at close puts a current site in front of buyers and next-round investors within a quarter rather than after it. Waiting until "things calm down" usually means the money is already committed elsewhere and no single owner is left for the site. #### Does our website really matter to investors? Yes — investors check it before a first call and again during diligence, and they read it as evidence of how the company operates. It is not weighted like a financial metric, but a site that contradicts the deck or looks two rounds behind becomes a small negative data point at the exact moment you want none. For your next round, the site is part of the story you're being judged on. #### Isn't a rebuild a distraction from using the money to grow? The rebuild is part of using the money to grow, because the site is the first thing every new high-value audience the raise unlocks will see. Enterprise buyers, senior candidates and next-round investors all form a first impression there. Leaving the pre-raise site live during that window costs more than the rebuild does. #### How long does a post-funding website rebuild take? Most focused B2B rebuilds run 8–12 weeks from discovery to launch, depending on scope and how much new messaging and content is involved. The positioning and content work is usually the long pole, not the design or build. Starting right after the close is what keeps the finished site ahead of your next milestone instead of behind it. #### Should we just refresh the design instead of rebuilding? A visual refresh restyles the old argument, which is the wrong problem after a raise. The change that matters is who the site argues to — an up-market buyer and a new category — and that flows through messaging, structure and content, not just look. If the positioning is genuinely still right and only the design has aged, a refresh can be enough; after a raise, it rarely is. #### How does a raise change our AI search visibility needs? A raise raises the stakes on being found in AI answers, because the more senior buyers and investors it attracts increasingly build shortlists through ChatGPT, Perplexity and Google's AI Overviews. If your site is invisible to those systems, you're absent from the research that forms the shortlist — and that absence compounds quietly. Rebuilding is the moment to fix the technical and structural gaps that keep you out of AI answers. #### We're pre-product or still small — is this overkill? If the raise is meant to move you up-market or is public enough to draw investor, buyer and candidate attention, it applies regardless of headcount. The trigger is the change in audience, not company size. If nothing about who visits your site has changed, you can wait — but a raise almost always changes exactly that. *BrandingLab is a B2B website and AI studio and an accredited Webflow Partner — we help venture-backed teams rebuild the site to match the company the raise turned them into.* --- ### Article: The Silent SEO Bug Breaking AI-Built Websites **URL:** https://www.brandinglab.io/articles/react-helmet-async-v3-silent-seo-failure **Published:** 2026-07-21 **Read time:** 7 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** AEO **Key takeaways:** - react-helmet-async v3.0.0, released in March 2026 after two years of abandonment, is reported broken by the community that maintains its successor fork. - The failure mode is silent: no error, no console warning — the page renders perfectly while titles, canonicals and schema never reach the head. - AI coding agents install "latest" by default, so any site built or updated with Lovable, Cursor, v0 or Bolt after March 2026 may carry the broken version. - The ten-second check: open any inner page, read document.title in DevTools, and if it shows your homepage title, your head layer is dead. - Google's Rich Results Test can pass a site with this bug, because valid sitewide schema masks the missing per-page layer. - Our own site ran with this failure for weeks while every monitoring theory pointed at the wrong layer. - Pin your dependencies: the bug entered our build through an unpinned npm install that resolved to the broken major. There is a class of website failure that produces no error message, no broken layout, and no alarm in any dashboard — and a popular React SEO library shipped one to npm in March 2026. If your site was built or updated by an AI coding tool since then, there is a real chance every page is presenting to Google and AI engines with your homepage's title and none of its own schema. We know because it happened to brandinglab.io. We sell AEO. Here is the bug, the ten-second check, and the fix. ### What is the react-helmet-async v3 bug? react-helmet-async v3.0.0 — a release that appeared in March 2026 after roughly two years of project abandonment — can fail to apply head tags at all: no page titles, no meta descriptions, no canonicals, no JSON-LD, with zero errors thrown. The library loads, the page renders, and the head-management layer silently does nothing. The backstory explains how a broken major ends up on npm. react-helmet-async's last stable release, v2.0.5, shipped in December 2023. When React 19 arrived in December 2024 it broke the library, [issues piled up with no maintainer response](https://github.com/staylor/react-helmet-async/issues/254), and in February 2025 the community forked it as [@dr.pogodin/react-helmet](https://www.npmjs.com/package/@dr.pogodin/react-helmet) — the fork's own documentation describes the original as "unmaintained and stale". Then, in March 2026, the absent maintainer abruptly published v3.0.0. The fork maintainer's assessment: v3 broke core behaviour — it stopped deduplicating tags and dropped features. What we verified on our own React 18 site was a different, quieter symptom of the same release: the library no-opped entirely. Zero managed tags in the head. Whether your symptom is duplication or silence, the input is the same — a broken major on npm, wearing the name of a package that ten thousand tutorials still recommend. ### Why are AI-built websites hit hardest? AI coding agents install "latest" by default, and since March 2026 "latest" is the broken version. Ask Lovable, Cursor, v0 or Bolt to "add SEO to my React site" and the standard playbook is `npm i react-helmet-async` — no version pin, no glance at the issue tracker, no awareness that the informed part of the ecosystem quietly migrated to a fork a year before the broken release landed. That is exactly how it entered our build: an unpinned install, run by an agent, during a routine SEO improvement. Installed four months earlier it would have resolved to working v2.0.5. Installed in July, it resolved to v3. A human developer who follows the React ecosystem might have known. An agent executing an install command does not read GitHub issues — and the population of sites built this way is precisely the population least likely to have anyone checking DevTools afterwards. ### Why doesn't anything catch it? Every standard check passes, which is what makes this failure dangerous rather than merely annoying. The page renders perfectly — users see nothing wrong. The console shows no errors — the library fails silently by design of its failure, not by anyone's intent. Googlebot renders JavaScript and still indexes the pages, so rankings don't collapse overnight; they erode. And Google's Rich Results Test can come back green: ours did, because valid sitewide organisation schema in the static HTML masked the dead per-page layer. One valid item detected — and no tool that tells you it should have been three. We ran with this for weeks. Every theory chased the delivery layer — crawlers, prerendering, hosting — because that is where SEO problems usually live. The actual failure was one layer up, and the test that found it takes ten seconds. The full investigation, method and findings are in [what an AEO audit actually looks like](/articles/what-an-aeo-audit-actually-looks-like). ### How do I check my site in ten seconds? Open any inner page of your site — an article, a service page, anything that is not the homepage — press F12, and type `document.title` into the console. If it returns your homepage's title, your head-management layer is not running, and everything it was supposed to manage — descriptions, canonicals, OG tags, article schema — is missing with it. Two follow-up checks confirm it. Search your page source for `data-rh` — react-helmet-async marks every tag it manages with that attribute, so zero matches means the library is doing nothing. Then view source (not DevTools — actual view-source) and check whether your body contains your content at all: if it's a near-empty div, non-JS crawlers like GPTBot and ClaudeBot see nothing regardless, which is the [SPA invisibility problem](/articles/b2b-ai-search-visibility) compounding the head problem. ### What is the fix? You have three options, in ascending order of robustness. Pin the library back to v2.0.5, the last stable release — smallest change, still leaves you on an unmaintained package. Switch to the maintained fork, @dr.pogodin/react-helmet, whose v2 line is a drop-in replacement. Or do what we did: remove the dependency entirely and replace it with a small native head manager — with React 18-19, `document.title` and a few createElement calls in a useEffect need no library at all, and a dependency that cannot exist cannot silently break. Whichever you choose, verify the same way you diagnosed: `document.title` must change per page, and your managed tags must be present in the head. Then check the second layer — that your prerendered or server-rendered HTML carries those tags for non-JS crawlers, because a head manager that only works after JavaScript executes only fixes half the audience. And pin your dependencies. The unpinned install is what turned an ecosystem problem into our problem. ### The wider lesson for AI-era teams The uncomfortable truth is that this bug's natural habitat is the AI-built web, and its population is growing. Sites shipped by agents, checked by humans who look at the rendered page, validated by tools that confirm what exists rather than what's missing — every layer of that stack waves this failure through. The number of sites currently serving their homepage title on every page is unknowable, but the mechanism that creates them runs thousands of times a day. The defence isn't avoiding AI tools — we build with them daily. It's adding the one discipline agents don't have: verifying what machines receive, on a schedule, at every layer. That discipline is a large part of [what AEO actually is](/articles/what-is-aeo) in practice. If you want us to run that check against your site — the head layer, the raw HTML, the schema that should exist and doesn't — [get a free AEO audit](/audit). It catches this bug in the first pass, because since July, checking for it is a standing item on our list. ### Frequently asked questions #### What does react-helmet-async do? It manages the document head in React applications — page titles, meta descriptions, canonical links, Open Graph tags and JSON-LD schema — updating them per route in single-page apps. It became the standard successor to react-helmet and is embedded in years of tutorials and starter templates, which is why it still gets installed thousands of times daily despite being unmaintained. #### Is react-helmet-async v3 safe to use? The community that maintains its successor fork reports v3.0.0 as broken — failing to deduplicate tags and dropping features — and on our own React 18 site we verified it silently applying nothing at all. Until the situation changes, the safe options are pinning v2.0.5, using the maintained @dr.pogodin/react-helmet fork, or replacing the library with native head management. #### How do I know if my site has this bug? Open any inner page, press F12, and read document.title in the console. If it shows your homepage's title instead of the page's own, the head layer is dead. Confirm by searching the page source for data-rh — zero matches means react-helmet-async is managing nothing. #### Why didn't Google flag this? Googlebot renders JavaScript and indexes the visible content, so pages don't vanish — they just compete with wrong titles and missing schema, which reads as gradual underperformance rather than a breakage. Validation tools like the Rich Results Test check that existing markup is valid; they don't know what markup should exist and doesn't. #### My site was built with Lovable, Cursor or v0 — am I affected? Possibly, if SEO or meta-tag work was done after March 2026: agents install "latest" by default, and latest is the broken major. The ten-second document.title check answers it definitively for your site. If the head layer is fine, still check your raw HTML — AI-built SPAs frequently have the separate problem of serving empty shells to non-JS crawlers. #### Should I stop letting AI agents manage dependencies? No — but add the guardrails agents lack: pin versions, review dependency changes in diffs, and verify behaviour after any install rather than trusting a clean build. A dependency that installs successfully and a dependency that works are different claims, and this bug lives exactly in the gap between them. --- ### Article: AI SEO vs Traditional SEO: What Actually Changes **URL:** https://www.brandinglab.io/articles/ai-seo-vs-traditional-seo **Published:** 2026-07-20 **Read time:** 7 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** AEO **Key takeaways:** - AI SEO is not a replacement for traditional SEO; it is a second layer that runs on the same crawlable, indexable foundation. - Traditional SEO optimises a page for a position; AI SEO optimises a passage for a citation. - The biggest practical difference is measurement: rank tracking cannot see AI answers, so presence in ChatGPT, Perplexity and AI Overviews has to be logged manually. - Keyword targeting gives way to question coverage, because AI systems break one query into several sub-queries before answering. - Off-site mentions matter more in AI SEO than in classic SEO, because AI systems synthesise across sources rather than ranking one. - Nothing you do for AI SEO is wasted on traditional SEO — the causation runs one way, from structure to both. - If your site is only readable after JavaScript executes, both disciplines fail at the same point. Two years ago the brief was "get us to page one". Now the same marketing lead asks a different question: why does ChatGPT recommend three competitors and not us? Both questions are about visibility. They are not answered by the same work. AI SEO and traditional SEO share a foundation and then diverge — on what gets optimised, how success is measured, and where the work actually sits. Here is the honest split, without the pretence that everything you learned is obsolete. ### What is AI SEO? AI SEO is the practice of getting your content cited inside AI-generated answers — Google AI Overviews and AI Mode, ChatGPT, Perplexity, Claude, Copilot — rather than only ranked in a list of blue links. It goes by several names: answer engine optimization (AEO), generative engine optimization (GEO), LLM optimization. The label matters less than the shift underneath it: the unit of visibility moves from the page to the passage. Confusingly, "AI SEO" is also used to mean *using AI tools to do SEO work* — drafting briefs, clustering keywords, generating schema. That is a productivity story, not a strategy one. This article is about the first meaning: optimising for AI systems, not with them. ### How is AI SEO different from traditional SEO? Traditional SEO competes for a position in a ranked list; AI SEO competes to be one of the sources an answer is assembled from. Everything else follows from that one change. | | Traditional SEO | AI SEO | |---|---|---| | Unit optimised | The page | The passage | | Goal | Rank in the top results | Be cited in the answer | | Query model | One keyword, one target page | One question fanned out into sub-questions | | Success signal | Position, clicks, impressions | Citation, mention, share of answers | | Off-site role | Links | Links *and* mentions across sources the model reads | | Feedback loop | Daily rank data | Manual, non-deterministic spot checks | We mapped the conceptual version of this comparison in [AEO vs SEO](/articles/aeo-vs-seo). This piece is the operating-model version: what changes on Monday morning. ### What stays the same? The technical foundation is unchanged, and it is still the majority of the work. Crawlability, indexation, site speed, clean information architecture, internal linking, and genuine subject authority all still decide whether you are in the candidate pool at all. AI systems overwhelmingly draw from content that conventional search already surfaces — if you are not indexed, you are not cited. This is where most "SEO is dead" takes fall apart. Sites that were invisible to Googlebot are also invisible to GPTBot, PerplexityBot and Google-Extended. The failure mode is identical, and so is the fix. We hit this on our own site: a client-side React build that rendered fine for humans and returned an empty shell to crawlers — the fix and the schema patterns are in [JSON-LD for React SPAs](/articles/jsonld-for-react-spas-schema-markup-guide). ### What changes in the actual work? Four things change in the day-to-day: content structure, question coverage, off-site presence, and measurement. **Content structure.** Traditional SEO tolerated a warm-up paragraph before the answer. AI SEO does not. The first sentence under every heading has to work as a standalone, quotable answer, because that sentence is the unit a model lifts. Headings phrased as buyer questions, one idea per section, short paragraphs — this is formatting as a ranking factor, in the literal sense. **Question coverage over keyword targeting.** AI systems decompose a question into sub-questions, search each, then synthesise. A page that answers only the head term gives the model one thing to cite. A page that also covers the timeline, the cost drivers, the comparison and the risks gives it five. Cluster architecture — a pillar plus supporting posts that interlink — does the same job at site level; the [AEO maturity model](/articles/aeo-maturity-model) is a useful way to see where you currently sit. **Off-site presence carries more weight.** Classic SEO cared about links as a ranking signal. AI SEO cares about mentions as a source signal: review sites, category roundups, Reddit and LinkedIn threads, comparison articles. If the "best X for Y" lists in your category do not name you, an AI answer about your category can be built without you — regardless of how strong your own site is. **Measurement is rebuilt from scratch.** There is no rank tracker for a conversation. Answers vary by phrasing, by session, by model version. The workable substitute is a monthly manual log: take your 20 most important buyer queries, run them in Google, ChatGPT and Perplexity three times each, and record whether an AI answer appeared, whether you were cited, and who was cited instead. Presence or absence is the metric. It is cruder than rank tracking and considerably more honest. ### Should I stop doing traditional SEO? No — and framing it as a choice is the expensive mistake. Traditional SEO determines whether you are eligible; AI SEO determines whether you are chosen. Dropping the first to chase the second removes you from the candidate pool that AI systems draw from. The sequencing that works: fix the technical foundation first, restructure content for extractability second, build off-site presence third, and stand up the measurement log alongside all of it. Every one of those steps also improves conventional rankings, which is why the trade-off people brace for mostly does not exist. For the engine-specific tactics, see [how to show up in ChatGPT and Perplexity](/articles/how-to-show-up-in-chatgpt-and-perplexity) and [AI overview optimization for B2B](/articles/ai-overview-optimization-for-b2b). ### Where to start Start by finding out whether you are cited today, because the answer usually settles the argument faster than any deck. Run your five highest-intent buyer queries through ChatGPT, Perplexity and Google, and write down who gets named. Then check one thing on your own side: view-source on your most important page and confirm the content is in the HTML, not assembled by JavaScript after load. If you would rather not do that manually, [book a free AI-search audit](/audit) — we run the queries, check what the crawlers actually receive, and send back the gaps in priority order. ### Frequently asked questions #### Is AI SEO the same as AEO? Effectively yes. AEO (answer engine optimization), GEO (generative engine optimization) and "AI SEO" all describe optimising to be cited inside AI-generated answers rather than only ranked in a list. The terminology is still settling; the practice is the same. #### Will AI search replace traditional search? Not in a way that makes traditional SEO irrelevant. AI answers are increasingly the first thing a searcher sees, but they are assembled from indexed content, so the crawl-and-index layer stays load-bearing. What changes is that ranking well without being cited now buys you less than it used to. #### Can I track AI SEO performance the way I track rankings? Not reliably. AI answers are non-deterministic — the same question can return different sources on different days — so there is no true equivalent of a rank tracker. Instead, measure presence in AI answers for your 20 most important buyer-intent queries, run each query three times because answers vary, and check monthly by hand — or have [BrandingLab monitor it weekly](/aeo-services/). #### Does schema markup help with AI SEO? Yes, as clarification rather than magic. Organization, Article and FAQPage schema tell AI systems what your entity is and which passages answer which questions, instead of leaving them to infer it. It is a small, cheap, high-leverage piece of the work — not a substitute for structure. #### How long does AI SEO take to show results? Expect months, not weeks, and expect it to move in steps rather than a curve. Content has to be recrawled, and models pick up changes on their own schedule — some surfaces reflect updates within weeks, others lag considerably. Technical fixes that unblock crawlers tend to show first. #### Do I need a separate team or agency for AI SEO? No. The work overlaps heavily with content, technical SEO and web build, so it usually belongs with whoever already owns those. What it does need is someone accountable for the measurement log — without it, nobody can say whether any of it worked. #### Does AI SEO work for B2B specifically? It matters more in B2B than in most categories, because B2B buyers use AI assistants for exactly the early research where vendor shortlists get formed. Being absent from those shortlists happens quietly and compounds — nothing in your analytics reports the deals you were never considered for. *BrandingLab is a B2B website and AI studio and an accredited Webflow Partner — we build sites marketing teams can run, that hold up under AI search.* --- ### Article: What an AEO Audit Actually Looks Like **URL:** https://www.brandinglab.io/articles/what-an-aeo-audit-actually-looks-like **Published:** 2026-07-20 **Read time:** 8 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** AEO **Key takeaways:** - An AEO audit tests six layers: technical foundation, on-page SEO, structured data, content extractability, authority signals, and measurement. - Every finding in an AEO audit should be produced by fetching a URL and reading the response — not by running a theory. - The most dangerous SEO failures are silent: the page looks perfect to humans while serving nothing usable to machines. - Google's Rich Results Test can pass while your per-page schema is completely dead, because sitewide schema masks the gap. - Audit findings must be ranked by impact and effort together — a one-line fix that closes four P1 findings outranks everything else. - The audit's roadmap is only credible if each item names the file, the change, and the verification step. - We ran this exact audit on brandinglab.io and found a sitewide silent failure our monthly checks had missed for weeks. On 20 July we ran our own AEO audit against brandinglab.io — the same audit we sell. It found that every page on our site was serving the homepage's title tag. No page had a meta description. No article emitted BlogPosting or FAQPage schema. Three URLs we invented on the spot returned 200 and rendered as real, indexable pages. Our site looked perfect. Google's Rich Results Test said it was fine. And for weeks, every article we published presented to search and AI engines as a copy of the homepage. That is what an AEO audit is for. Not the checklist — the checklist is table stakes — but the discipline of testing what machines actually receive instead of what the browser shows you. Here is the full anatomy of the audit, using our own failure as the worked example, because a methodology you won't run on yourself is marketing, not method. ### What does an AEO audit include? An AEO audit tests six layers, in order: technical foundation (crawl access, robots.txt, llms.txt, sitemap integrity, 404 behaviour), on-page SEO (titles, descriptions, canonicals), structured data (entity schema sitewide, BlogPosting/FAQPage/Service schema per page), content extractability (answer-first structure, question-phrased headings, FAQ blocks), authority signals (third-party citations, entity consistency, roundup presence), and measurement (whether you can even tell if any of this is working). Each finding gets an ID, the evidence that produced it, why it matters, the specific fix, and a priority from P1 to P4. No finding ships without evidence. In our own audit that rule is what separated the real problem from the two wrong theories that preceded it. ### How is every finding verified? Every claim in the audit comes from fetching a URL and reading what came back — raw HTML the way a non-JS crawler receives it, and the rendered DOM the way a browser builds it. The gap between those two views is where AEO failures live. Our own audit fetched 37 URLs. All 37 returned an identical 5,434-byte shell whose body was 46 characters long. Then we rendered the pages in a real browser and found the second, worse problem: even with JavaScript fully executed, the head tags never changed. A 2,218-word article with a perfect H1 and a full FAQ block was being labelled with the homepage's title and nothing else. The diagnostic that found it takes ten seconds: open DevTools on any article and read document.title. Weeks of theories about crawlers, prerendering and hosting had missed it, because every theory was tested at the delivery layer — and the failure was one layer up, in a head-management library that silently stopped working. We wrote up why absence from AI answers compounds in [why your B2B website isn't showing up in AI search](/articles/b2b-ai-search-visibility); this is the mechanism by which it happens to sites that look healthy. ### Why didn't Google's own tools catch it? Google's Rich Results Test passed our broken site, because our sitewide organisation schema — served statically on every URL — was valid and eligible. One valid item detected. Green tick. What the test doesn't say is that an article page should have produced three items, not one. The static entity schema masked the dead per-page layer. This is the general lesson about validation tools: they confirm that what exists is valid, and stay silent about what should exist and doesn't. An audit's job is exactly that silence — the expected-but-absent. It is why a checklist run by a tool is not an audit. ### How are audit findings ranked? Findings are ranked on impact and effort together, and the ranking's job is to find the fixes that collapse multiple findings at once. In our audit, four P1 findings — wrong titles everywhere, missing descriptions, missing canonicals, missing article schema — traced to a single root cause. One fix, verified with one DevTools check, closed all four. That fix outranked everything else in the report, including findings that were individually more alarming. The output is a 2x2: high-impact/low-effort items are this week's work, high-impact/high-effort items are month one, low-impact/low-effort items fill spare capacity, and low-impact/high-effort items get named and deliberately deferred. If an audit hands you thirty findings of equal weight, you've been handed a liability transfer, not a plan. The [AEO maturity model](/articles/aeo-maturity-model) is the strategic version of the same discipline — knowing which level you're at tells you which fixes are even worth doing yet. ### How is the schema generated? The audit doesn't recommend schema in the abstract — it ships the JSON-LD, pre-filled from your real site data, ready to paste. Organization schema built from your actual name, founding date, locations and social profiles. Service and Offer schema carrying your actual pricing. FAQPage schema generated from the questions already on your pages. On our own site the schema layer is generated programmatically: article pages build BlogPosting and FAQPage JSON-LD from the CMS record, and the FAQ block on each page is parsed into schema automatically. That's the end state the audit points at — schema as a build output, not a plugin bolted on. The distinction matters for AI engines specifically, and we've covered the definitional ground in [what is AEO](/articles/what-is-aeo) and the strategic split in [AEO vs SEO](/articles/aeo-vs-seo). ### How is the roadmap planned? Each roadmap item names the file, the change, and the verification step — because a roadmap you can't verify is a wish list. Ours read: fix the head-management layer, then confirm document.title changes per page and the managed-tag count is above zero. Return real 404s for unmatched routes, then confirm an invented URL renders a noindex 404 page. Regenerate llms.txt from the database, then confirm it lists what the sitemap lists. The phases are honest about time: week one is the quick wins (in our case, one dependency fix closed the worst four findings in an afternoon), month one is the structural work (consolidating duplicate pages, rebuilding stale files), and everything after that is cadence. ### How are updates tracked? Presence or absence in the answer is the metric, and it's logged monthly by hand. Take your 20 most important buyer queries, run them in Google, ChatGPT and Perplexity three times each, and record three things: did an AI answer appear, were you cited, who was cited instead. Alongside that, GA4 tracks AI-referrer sessions — traffic arriving from chatgpt.com, perplexity.ai and their peers — and Search Console confirms what Google actually crawled. The audit repeats quarterly. Ours found a failure our own weekly monitoring had missed, which is the honest argument for the cadence: monitoring watches the metrics you chose; an audit re-tests the assumptions underneath them. ### The uncomfortable part, and why we published it We sell AEO services, and our own site spent weeks presenting every article as a copy of the homepage. We could have fixed it quietly. We published it instead, because the audit that found it is the product, and the find is the proof. The fix went live the same day: correct titles, descriptions, canonicals and a five-block schema stack on every article — verified in the DOM, not assumed. If you want the same test run against your site, [get a free AEO audit](/audit) — it checks the four things that caught our failure: what crawlers receive, what the rendered head contains, what schema actually emits, and whether your invented-URL test returns a real 404. If the results need acting on, the [full audit and programme](/aeo-services) picks up from there. ### Frequently asked questions #### What does an AEO audit include? An AEO audit tests six layers: technical foundation (crawl access, robots.txt, llms.txt, sitemaps, 404 behaviour), on-page SEO (titles, descriptions, canonicals), structured data, content extractability, authority signals, and measurement. Every finding carries evidence, a specific fix, and a priority ranking. #### How is an AEO audit different from an SEO audit? The overlap is large — crawlability, titles, schema and performance matter to both. The difference is the target: an SEO audit optimises for ranking in a list of links, while an AEO audit optimises for being cited inside AI-generated answers, which adds tests for extractable answer structure, entity consistency, llms.txt, and what non-JS AI crawlers actually receive. #### How long does an AEO audit take? A thorough audit of a typical B2B site takes about two weeks: a few days of testing and evidence gathering, then analysis, competitor comparison, and the prioritised roadmap. Ours runs on a fixed six-dimension method, so the timeline is driven by site size rather than scope creep. #### Can automated tools do an AEO audit? Automated tools handle the enumeration — fetching URLs, counting tags, validating schema — but they confirm what exists rather than noticing what's missing. Our own site passed Google's Rich Results Test while its entire per-page schema layer was dead. The judgement layer of an audit is exactly the absence-spotting that tools skip. #### What is a silent SEO failure? A silent SEO failure is one that produces no error and no visible symptom: the page renders perfectly for humans while serving wrong or empty signals to machines. Ours was a head-management library that loaded without error and simply never applied any tags. The only way to catch this class of failure is to inspect what machines receive, on a schedule. #### How often should you re-run an AEO audit? Quarterly, plus after any significant platform or dependency change. Monthly monitoring tracks your chosen metrics; the quarterly audit re-tests the assumptions underneath them. Our July audit caught a failure that weeks of monitoring had missed, precisely because monitoring wasn't looking at the layer that broke. #### What should an AEO audit deliver at the end? Four things: the findings with evidence and priorities, ready-to-paste schema built from your real data, an effort-versus-impact matrix, and a phased roadmap where every item names the change and its verification step. If any of the four is missing, you've bought a report, not an audit. --- ### Article: WordPress for AEO: Flexibility, Plugins, and the Maintenance Trade-Off **URL:** https://www.brandinglab.io/articles/wordpress-for-aeo **Published:** 2026-07-19 **Read time:** 7 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** AEO **Key takeaways:** - WordPress renders pages on the server, so your content arrives as crawlable HTML by default — the core AEO requirement is met. - The plugin ecosystem is its superpower for AEO: Rank Math, Yoast, and AIOSEO now offer 20+ schema types, site-wide structured-data maps, llms.txt support, and AI-citation tracking. - The trade-off is responsibility: plugin dependency, security patching, performance tuning, and the risk of bloat all fall on you or your team. - WordPress rewards technical capacity. With a capable team it can match nearly any platform; without one, it can quietly underperform. WordPress powers a huge share of the web, and with the right configuration it can hold its own on Answer Engine Optimization — getting cited in ChatGPT, Perplexity, and Google's AI Overviews. The catch is that WordPress gives you the pieces but leaves the assembly and upkeep to you. Here's an honest look at where it's strong for AEO and where the work lives. For the full platform-by-platform comparison, see [the best website platform for AEO](/articles/best-website-platform-for-aeo). ### Why WordPress meets the AEO fundamentals WordPress generates pages on the server (rendered from PHP), which means the content is present in the HTML a crawler receives. That matters because most AI crawlers don't execute JavaScript — and WordPress doesn't depend on the browser to assemble content. So unlike a default single-page app, a standard WordPress site is readable by AI engines from the start. The foundation is sound before you install anything. ### The plugin ecosystem is the real advantage Where WordPress pulls ahead is the depth of its SEO and AEO tooling. Modern plugins have moved aggressively into the AI-search era: - **Rank Math** offers a visual schema builder with 20+ schema types in its free tier, added llms.txt support to help AI crawlers understand site structure, and an AI search traffic tracker that shows which content AI engines cite. - **Yoast SEO** takes a standards-focused approach and introduced a Schema Aggregation feature that builds a site-wide structured-data map AI agents can use to understand your whole domain; its schema output is among the most standards-compliant available. - **AIOSEO** consolidates on-page and technical SEO in one workflow and scales cost-effectively across many sites, which suits agencies and multi-site teams. With one of these configured well, WordPress can output clean JSON-LD, enforce good structure, manage sitemaps and redirects, and give you visibility into AI citations — a genuinely complete AEO stack. ### The trade-off: everything is your responsibility The flexibility that makes WordPress powerful is also its cost. You're responsible for keeping the core, theme, and plugins updated and secure. Performance depends heavily on your hosting, theme quality, and how many plugins you stack — poorly built themes and plugin bloat are a common cause of slow sites, which hurts both users and crawlers. Plugin dependency also means a key feature can change, break, or move behind a paywall. None of this is disqualifying, but it means AEO on WordPress is an ongoing operational commitment, not a set-and-forget setup. ### Who WordPress fits for AEO WordPress is a strong AEO choice for teams that want maximum flexibility and ownership and either have technical capacity in-house or are comfortable maintaining the stack (or paying someone to). If you want a large ecosystem, full control over your content model, and no vendor lock-in, it's hard to beat. Teams that want AEO handled with minimal upkeep may prefer a more managed platform like Webflow or modern Wix, while teams wanting a fully custom, developer-led build may lean toward a headless setup like Sanity. ### Run the crawler's-eye test on your own site You do not need a developer, a tool, or a paid audit to find out whether AI engines can read your site. Two minutes, in a browser. **1. Pick the page you most want cited.** Not the homepage — the service or product page a buyer would actually land on when researching your category. **2. View the source, not the inspector.** Right-click, then **View page source** (Ctrl+U on Windows, Cmd+Option+U on Mac). This distinction is the whole test. "Inspect Element" shows the page *after* your browser has executed the JavaScript. View Source shows the raw HTML the server sent — which is all most AI crawlers ever see. Teams check the wrong one constantly and conclude they are fine. **3. Find a sentence from the middle of the page.** Copy about ten words of body copy — not the headline — and search for it in the source with Ctrl+F. **4. Search the source for `application/ld+json`.** Each match is one block of structured data telling engines what the page is. Count them. **5. Open `yoursite.com/robots.txt`.** Look for `GPTBot`, `ClaudeBot`, `PerplexityBot` and `Google-Extended`, and check whether they are allowed or disallowed. Then try `yoursite.com/llms.txt` — most sites return a 404. #### How to read the result on WordPress **Your sentence is in the source.** Expected — PHP renders on the server, so this is the baseline WordPress hands you. **Your sentence is missing.** Rare, but real. The usual culprits are a page builder that lazy-renders sections below the fold, or an aggressive optimisation plugin deferring content in the name of Core Web Vitals. Worth finding, because it will be costing you more than the performance score gained. **Zero `ld+json` blocks.** Your SEO plugin is installed but not configured. Rank Math, Yoast and AIOSEO all emit structured data once set up — zero output means nobody finished the setup. **Now count the plugins.** In the same source view, count ``. It has nothing to read, so it has nothing to cite. You can pass the human grunt test — clear headline, prominent CTA, well-designed page — and fail the AI version simultaneously. The human sees your site. The crawler sees a blank. ### How to diagnose your site in two minutes Run this in a terminal: ```bash curl -A "Mozilla/5.0 (compatible; GPTBot/1.0; +https://openai.com/gptbot)" https://yourdomain.com | grep -i "` was there, waiting for JavaScript to fill it in. The headline, the value proposition, the service descriptions, the CTAs — all of it lived in JavaScript bundles that the AI crawler never executed. To every bot that fetched the page without running JavaScript, our homepage was empty. It was a clean case of passing the human grunt test and failing the AI one. The fix was a Cloudflare Worker deployed in front of the site. The Worker inspects the incoming user agent on every request. If the request comes from a known bot — GPTBot, ClaudeBot, Bingbot, Perplexity's crawler, and a list of others — the Worker intercepts it and routes the request to a headless Chrome prerender service. The prerender executes the JavaScript, waits for the content to load, and returns the fully-rendered HTML to the crawler. Human visitors get the React app as before. Bots get the prerendered HTML with real content. The result: AI crawlers can now parse everything on the page. The implementation took less than a day and required no changes to the frontend codebase. This is the same class of fix available to any JavaScript-heavy site. It's not a full rebuild. It's a routing layer that gives crawlers what they need without changing what humans see. ### What to do about it **Step 1: Run the human grunt test.** Open your homepage. Give yourself five seconds — no scrolling. Close your eyes. Answer: What does this company do? Who does it help? What should I do next? If any of those is unclear, the messaging needs work before anything else. **Step 2: Run the AI grunt test.** Use the curl command above against your own site. If the output is an empty shell, you have an AI visibility problem regardless of how well the human version passes. **Step 3: Fix the human version at the messaging layer.** Rewrite the headline to name what you do and who it's for, plainly. Make the CTA the most visible element in the first viewport. Cut anything on the homepage that doesn't directly serve the visitor's decision in the first five seconds. **Step 4: Fix the AI version with a rendering layer.** For client-rendered JavaScript applications, the options are server-side rendering (rendering content on the server before sending HTML), static site generation (pre-building HTML at deploy time), or dynamic prerendering (a middleware layer like the Cloudflare Worker approach above). Which is right depends on your stack. The point is that one of them needs to be in place. **Step 5: Verify, then re-verify.** After implementing fixes, run both tests again. The curl diagnostic should return meaningful content. A human running the five-second test should be able to answer all three questions cleanly. ### The original principle still holds Donald Miller's insight from 2014 hasn't aged. The brain still filters. Visitors still arrive with limited attention and no prior context about your company. Clarity in the first five seconds still determines whether they stay. What's changed is that websites now have a second audience with different constraints. AI crawlers don't scroll, don't execute JavaScript, and don't give you multiple chances. They fetch once. What they see in that fetch is what they use to decide whether you exist in their index. Running both versions of the grunt test is now part of basic website maintenance. Neither is optional. ### Frequently Asked Questions #### What is the Grunt Test? The Grunt Test is a website clarity framework from Donald Miller (StoryBrand). It says a first-time visitor should be able to identify — within five seconds, without reading carefully — what a company offers, who it helps, and how to get it. If those three questions can't be answered quickly, the homepage needs to be simplified. #### Who created the Grunt Test? Donald Miller, founder of StoryBrand and author of *Building a StoryBrand*, developed the Grunt Test as part of his framework for simplifying brand messaging. The name reflects the idea that even a minimal amount of cognitive engagement should be enough to grasp the core message. #### Why do most B2B websites fail the Grunt Test? Because they're written by people who know the company too well. Insiders assume visitors share their context, which they don't. The result is headlines that mean something internally and nothing externally, service lists instead of clear value propositions, and CTAs that are technically present but visually buried. #### What is the AI grunt test? The AI grunt test is a term we use to describe whether AI crawlers — the systems that feed ChatGPT, Perplexity, Google AI Overviews, and similar tools — can parse meaningful content from your homepage in a single HTTP fetch. If your site requires JavaScript to render its content, crawlers that don't execute JavaScript may see an empty HTML shell. A site that passes the human grunt test can still fail the AI version. #### How do I check if AI crawlers can read my homepage? Run a curl request against your homepage using a bot user agent: `curl -A "Mozilla/5.0 (compatible; GPTBot/1.0)" https://yourdomain.com`. If the output contains your headline and core content, you're likely fine. If it returns an empty shell or a bare HTML frame, AI crawlers are seeing the same thing. #### What causes a site to fail the AI grunt test? The most common cause is a JavaScript-rendered single-page application (SPA) where the meaningful page content lives in JavaScript bundles rather than the initial HTML. AI crawlers that don't execute JavaScript fetch the shell and see nothing useful. This is standard behavior for React, Vue, and Angular applications that aren't configured with server-side rendering or a prerendering layer. #### How do you fix an AI grunt test failure? There are three main approaches: server-side rendering (the server generates complete HTML on each request), static site generation (complete HTML is built at deploy time), or dynamic prerendering (a middleware layer detects bot user agents and serves pre-rendered HTML to crawlers while serving the JavaScript app to human visitors). The Cloudflare Worker approach is an example of dynamic prerendering — it requires no changes to the frontend and can be implemented in less than a day. #### Can a website pass the human grunt test and fail the AI version simultaneously? Yes. That's exactly what happened with brandinglab.io. The site was well-designed, messaging was clear, and human visitors had no trouble navigating it. But because it was a React application without a prerendering layer, AI crawlers received an empty HTML shell. The human test passed. The AI test failed. Both needed to be addressed. #### Does the human grunt test still matter if AI search is taking over? Yes. Human visitors still arrive with limited attention and no prior context about your company. The five-second test for humans is as valid as it was when Miller introduced it. What's changed is that it's no longer the only test your site needs to pass. AI crawlers have their own version with different constraints, and both need to be addressed. #### What's the fastest way to run the Grunt Test on my homepage? For the human version: open your homepage, look at it for five seconds without scrolling, then close your eyes and try to answer the three questions from memory. For the AI version: run the curl command against your homepage with a bot user agent and check whether meaningful content comes back. Both tests take less than five minutes combined and tell you immediately where to focus. --- ### Article: Webflow for AEO: Advantages, Limitations, and How It Compares **URL:** https://www.brandinglab.io/articles/webflow-for-aeo **Published:** 2026-07-19 **Read time:** 7 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** AEO **Key takeaways:** - Webflow serves content as pre-rendered HTML from a CDN, so AI crawlers that don't run JavaScript still see your content — the number-one AEO requirement, handled by default. - The AEO fundamentals are built in: semantic HTML, editable metadata, sitemaps, robots.txt, and llms.txt, with visual control over heading structure. - Webflow has invested heavily in AEO as a category, including an enterprise product that tracks AI citations and recommends fixes. - The limitations are real but manageable: advanced schema can need custom embeds, the deepest tooling is gated to higher plans, and large content operations must plan around CMS limits. If you're choosing a platform partly to get cited in ChatGPT, Perplexity, and Google's AI Overviews, Webflow is one of the few that solves the hardest AEO problem before you do anything. This is a closer look at where Webflow is strong for Answer Engine Optimization, where it isn't, and who it fits. For the full platform-by-platform comparison, see [the best website platform for AEO](/articles/best-website-platform-for-aeo). ### Why Webflow starts ahead on AEO The single most important technical factor in AEO is whether your content exists in the HTML a crawler receives. Most AI crawlers do not execute JavaScript, so a site that builds its content in the browser is effectively invisible to them. Webflow publishes pages as static HTML served from a global CDN. When ChatGPT's or Perplexity's crawler requests a page, the content is already there. You don't have to configure server-side rendering or add a prerender service — it's the default behavior. That one property removes the most common reason businesses never get cited. ### The built-in AEO toolkit Webflow includes the structural pieces AEO depends on without plugins. You get semantic HTML output, full control over title tags and meta descriptions, automatically generated XML sitemaps, editable robots.txt, and native llms.txt support — a file that gives AI systems a clean summary of your most important content. Because Webflow gives you visual control over the document structure, you can enforce a logical heading hierarchy (one H1, ordered H2s and H3s), which is exactly what answer engines use to extract and quote passages. Webflow has also made AEO a headline focus, publishing AEO education and shipping an enterprise product that pairs analytics tracking your brand's presence in AI answers with agents that surface and help execute technical fixes. ### The limitations to plan around Webflow isn't limitation-free. The most advanced schema scenarios — highly customized or nested JSON-LD — can require custom code embeds rather than a purely visual workflow, though common types (Organization, Article, FAQ, Product) are very manageable. The most powerful AEO analytics and agent tooling sits on higher-tier and enterprise plans, so a small business on a starter plan gets excellent fundamentals but not the full citation-tracking suite. And Webflow's CMS has item and plan limits that large, high-volume content operations need to design around. ### Who Webflow fits for AEO Webflow is the strongest out-of-the-box option for marketing teams that want to own their site's structure and content without a developer on call. If you value design control, want the rendering and schema fundamentals handled for you, and don't need a fully custom backend, it removes most of the friction from getting AI-ready. Teams that need deep custom application logic or extremely high content volumes may find its guardrails limiting — those are cases where WordPress or a headless setup like Sanity earn a look. ### Run the crawler's-eye test on your own site You do not need a developer, a tool, or a paid audit to find out whether AI engines can read your site. Two minutes, in a browser. **1. Pick the page you most want cited.** Not the homepage — the service or product page a buyer would actually land on when researching your category. **2. View the source, not the inspector.** Right-click, then **View page source** (Ctrl+U on Windows, Cmd+Option+U on Mac). This distinction is the whole test. "Inspect Element" shows the page *after* your browser has executed the JavaScript. View Source shows the raw HTML the server sent — which is all most AI crawlers ever see. Teams check the wrong one constantly and conclude they are fine. **3. Find a sentence from the middle of the page.** Copy about ten words of body copy — not the headline — and search for it in the source with Ctrl+F. **4. Search the source for `application/ld+json`.** Each match is one block of structured data telling engines what the page is. Count them. **5. Open `yoursite.com/robots.txt`.** Look for `GPTBot`, `ClaudeBot`, `PerplexityBot` and `Google-Extended`, and check whether they are allowed or disallowed. Then try `yoursite.com/llms.txt` — most sites return a 404. #### How to read the result on Webflow **Your sentence is in the source.** Expected. This is the default behaviour described above and the reason Webflow starts ahead — you inherited it without doing anything. **Your sentence is missing.** Uncommon on Webflow, and when it happens the cause is specific rather than structural: a section built with a custom code embed that fetches its content in the browser, or content inside a component that only renders on interaction. It is a build decision, not a platform limit, and it is fixable in the Designer. **Zero `ld+json` blocks.** You have the platform's schema capability and have not used it. Webflow will not add Organization or Article schema on your behalf — someone has to put it there. **One or two blocks.** This is where most Webflow sites stop. It is a baseline, not an advantage. **Nothing about AI bots in robots.txt.** Webflow's default does not block them, but it does not declare anything either, and there is no llms.txt unless you created one. #### What this test cannot tell you Rendering is the floor, not the ceiling. Passing every step above puts you level with every other competently built Webflow site — it does not make you the source an engine picks. Three things decide that, and none of them appear in View Source: whether your page answers the question a buyer actually typed rather than the one you wanted to write about; whether your organisation is defined consistently enough across the web that an engine can tell who you are; and whether anyone other than you corroborates it. Those levers only start mattering once rendering is solved — which, if you passed the test, it already is. That is the point at which a self-serve check stops being useful. [Run our free AEO audit](/audit) if you want the part the browser cannot show you. ### Frequently asked questions #### Is Webflow good for AEO? Yes. Webflow handles the most important AEO requirement automatically by serving content as pre-rendered HTML from a CDN, so AI crawlers that don't run JavaScript can still read it. It also includes semantic HTML, editable metadata, sitemaps, robots.txt, and llms.txt support, and offers enterprise tooling to track AI citations. Its main limitations are that advanced schema can require custom code and the deepest AEO tooling is on higher-tier plans. #### Does Webflow support schema markup for AI search? Yes. Webflow supports common schema types and gives you control over metadata and page structure. Standard types like Organization, Article, FAQ, and Product schema are straightforward, while highly customized or nested JSON-LD may require adding a custom code embed to the page or site. #### Do I need a developer to do AEO on Webflow? Not for the fundamentals. Webflow's visual editor lets marketers control headings, metadata, sitemaps, and common schema without code. You may want developer help for advanced custom schema or complex integrations, but the core AEO setup is achievable by a non-developer. #### Does Webflow render content for AI crawlers by default? Yes. Webflow serves static, pre-rendered HTML from a CDN, so the content is present in the page a crawler receives without any additional rendering configuration — unlike single-page-app platforms that require server-side rendering or prerendering to be added. --- ### Article: The Best Website Platform for AEO: Webflow vs WordPress vs Wix vs Vibe-Code vs Sanity **URL:** https://www.brandinglab.io/articles/best-website-platform-for-aeo **Published:** 2026-07-19 **Read time:** 12 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** AEO **Key takeaways:** - AEO is decided at the platform level, not bolted on later. The three things AI engines need most — content delivered as readable HTML, structured data (schema), and clean semantic structure — are either built into your platform or they're a fight. - The single biggest technical dividing line is rendering. Most AI crawlers do not run JavaScript. If your pages only assemble their content in the visitor's browser, AI engines see a blank shell. Server-side rendering (SSR), static generation, or prerendering is non-negotiable. - No platform makes you invisible forever, and none guarantees citations. The platform sets your ceiling and your effort level. A well-configured WordPress or Wix site can outperform a badly built Webflow one. - Match the platform to your team. Webflow and Wix favor marketing teams who want control without developers. WordPress offers flexibility with maintenance overhead. Sanity offers total control but needs developers. Vibe-code tools are fast to launch but need a rendering fix before they're AEO-ready. Buyers have quietly changed how they find companies. Instead of scrolling a page of blue links, they ask ChatGPT, Perplexity, or Google's AI Overviews a question and get a short, synthesized answer with two or three recommended options. If your business is named in that answer, you're on the shortlist. If it isn't, you're invisible — and you may never know it happened. That shift is what Answer Engine Optimization (AEO) is about: structuring your website so AI answer engines can find, understand, and cite it. And here's the part most people underestimate: your ability to do AEO well is largely decided by the platform your website is built on. Some platforms hand you most of what AEO needs by default. Others actively work against it unless you bring in a developer to fix the foundation. This guide compares the five platforms businesses most often weigh — Webflow, WordPress, Wix, vibe-code tools (like Lovable, Bolt, and v0), and Sanity — through one lens: how well each one lets you get cited in AI answers. ### What AI answer engines actually need Before comparing platforms, it helps to know what you're optimizing for. AEO is different from traditional SEO. SEO tried to rank a page higher on a list. AEO tries to get your content quoted inside a direct answer. The signals that matter shift accordingly, and four of them are technical enough that your platform choice affects each one. **Content that lives in the HTML.** AI crawlers from ChatGPT, Perplexity, Claude, and Google read the HTML your server returns. Research from crawler studies has repeatedly found that most AI crawlers do not execute JavaScript. If your content only appears after the browser runs scripts, those crawlers see an empty page. This is the make-or-break factor, and it's entirely a function of how your platform renders pages. **Structured data (schema markup).** Schema is machine-readable code (usually JSON-LD) that explicitly tells an engine what your content is: an organization, a product, an FAQ, an article, a review. Pages with clean schema get cited more often because the engine doesn't have to guess. Every platform handles schema differently — some generate it automatically, some need a plugin, some need custom code. **Semantic HTML and clear structure.** Pages that use a logical heading hierarchy (one H1, then H2s and H3s) and lead each section with a direct, factual statement are easier for a model to extract and quote. Analyses of cited pages find they score meaningfully better on heading structure than uncited ones. **Crawler access signals.** A correct robots.txt that doesn't block AI bots, an XML sitemap, and increasingly an llms.txt file (a clean summary of your key content for AI systems) all help engines find and prioritize your pages. With that framework, here's how the platforms stack up. ### The comparison at a glance | Platform | Content in HTML by default? | Built-in schema | Native AI-citation tracking | Best for | Main limitation | | --- | --- | --- | --- | --- | --- | | Webflow | Yes (static hosting on CDN) | Semantic HTML, metadata, llms.txt, sitemaps built in; visual control | Yes, on enterprise plans | Marketing teams wanting design + AEO control without developers | Advanced schema can need custom embeds; higher-tier AEO tooling is gated | | WordPress | Yes (server-rendered) | Via plugins (Rank Math, Yoast, AIOSEO) — 20+ schema types | Via plugins (AI traffic tracking) | Teams wanting flexibility, ownership, and a large ecosystem | Plugin dependency, maintenance, security, and performance overhead | | Wix | Yes on newer Wix Studio (SSR); older sites weaker | Structured Data Manager (LocalBusiness, Product, FAQ, Review) + custom JSON-LD | Yes (AI Visibility tool) | Small businesses wanting an all-in-one builder | Less low-level control; SSR strongest only on newer Studio sites | | Vibe-code (Lovable, Bolt, v0) | No by default (single-page apps) — needs SSR/prerender | Only what you or the AI add manually | Rarely built in | Rapid prototyping and launching an app fast | Default output is often invisible to AI crawlers until rendering is fixed | | Sanity (headless) | Depends entirely on your frontend (excellent with Next.js) | You implement it — total control | You build it | Custom builds where developers want full control | Nothing works out of the box; requires developers to build and maintain | ### Webflow Webflow serves pages as pre-built HTML from a global CDN, so your content is already in the HTML when a crawler arrives — the rendering problem is solved by default. It bakes in semantic HTML, SEO metadata, sitemaps, robots.txt, and llms.txt, and gives marketers visual control over structure without touching code. Webflow has also leaned hard into AEO as a category, launching an enterprise product that tracks brand citations in AI answers and recommends technical fixes. The tradeoffs: the most advanced schema scenarios can still require custom code embeds, the deepest AEO tooling sits on higher-tier and enterprise plans, and there are CMS limits to plan around on larger content operations. For a marketing team that wants strong AEO fundamentals without a developer on call, it's one of the most turnkey options. [Read the Webflow deep dive.](/articles/webflow-for-aeo) ### WordPress WordPress renders pages on the server, so content arrives as crawlable HTML — the fundamentals are sound out of the box. Its real strength is the ecosystem: plugins like Rank Math, Yoast, and AIOSEO now offer 20+ schema types, site-wide structured-data maps, llms.txt support, and even AI-citation tracking. With the right configuration, WordPress can match almost any platform on AEO. The cost is responsibility. That flexibility comes with plugin dependency, security patching, performance tuning, and the risk of bloat from poorly built themes and plugins. WordPress rewards teams that either have technical capacity or are willing to maintain the stack. [Read the WordPress deep dive.](/articles/wordpress-for-aeo) ### Wix Wix has changed a lot. For years it was criticized for client-side rendering that hurt SEO, but its newer Wix Studio platform rolled out server-side rendering that resolves those JavaScript issues, and new Studio sites now score well on technical SEO out of the box. Its Structured Data Manager lets you add LocalBusiness, Product, FAQ, and Review schema without code, plus custom JSON-LD, and it offers an AI Visibility tool to track LLM mentions. The caveats: the strongest rendering and schema tooling is concentrated in newer Studio sites rather than older Wix builds, and you trade some low-level control for the all-in-one convenience. For small businesses that want a single tool and don't need deep customization, modern Wix is a legitimate AEO option — a real change from its reputation. [Read the Wix deep dive.](/articles/wix-for-aeo) ### Vibe-code platforms (Lovable, Bolt, v0) AI app builders let you describe a site and get a working one in minutes. The catch for AEO is rendering. By default these tools produce single-page applications (SPAs) that assemble content in the browser with JavaScript — which means an AI crawler that doesn't run JavaScript sees an empty shell. Studies have found these sites frequently invisible to AI engines until the rendering is fixed. The picture is improving: Lovable, for example, now uses server-side rendering for new apps and prerendering for verified crawlers on older ones. But behavior varies by tool and by when your app was built, and the fix (adding SSR or a prerender service) is on you. Vibe-code tools are excellent for speed; treat AEO-readiness as a deliberate step, not an assumption. [Read the vibe-code deep dive.](/articles/vibe-code-platforms-for-aeo) ### Sanity Sanity is a headless CMS: it manages your content but doesn't render your website. That means its AEO performance depends entirely on the frontend you pair it with. Paired with a framework like Next.js, you get full access to server-side rendering, static generation, and incremental regeneration — everything AEO needs — plus a highly structured content model that's ideal for generating clean schema and machine-readable output. The flip side: nothing is automatic. Every piece of AEO — rendering strategy, schema, semantic structure, sitemaps — is something your developers implement and maintain. Sanity offers the highest ceiling of any option here, but only teams with development resources can reach it. [Read the Sanity deep dive.](/articles/sanity-for-aeo) ### So which platform is best for AEO? There's no single winner, because the right answer depends on who's maintaining the site. The honest framing is this: - **If you want strong AEO with minimal technical lift**, Webflow gets you the furthest out of the box, with modern Wix Studio a strong option for smaller businesses. - **If you want flexibility and an ecosystem and can handle upkeep**, WordPress with a capable SEO plugin can compete with anything. - **If you have developers and want maximum control**, Sanity paired with a modern framework offers the highest ceiling. - **If you built on a vibe-code tool**, you can absolutely make it AEO-ready — but confirm how it renders and fix that first. The biggest mistake isn't picking the "wrong" platform. It's assuming AEO happens automatically. On every platform, getting cited in AI answers takes deliberate setup — and on some, it takes fixing the foundation before you can start. ### Run the crawler's-eye test on your own site You do not need a developer, a tool, or a paid audit to find out whether AI engines can read your site. Two minutes, in a browser. **1. Pick the page you most want cited.** Not the homepage — the service or product page a buyer would actually land on when researching your category. **2. View the source, not the inspector.** Right-click, then **View page source** (Ctrl+U on Windows, Cmd+Option+U on Mac). This distinction is the whole test. "Inspect Element" shows the page *after* your browser has executed the JavaScript. View Source shows the raw HTML the server sent — which is all most AI crawlers ever see. Teams check the wrong one constantly and conclude they are fine. **3. Find a sentence from the middle of the page.** Copy about ten words of body copy — not the headline — and search for it in the source with Ctrl+F. **4. Search the source for `application/ld+json`.** Each match is one block of structured data telling engines what the page is. Count them. **5. Open `yoursite.com/robots.txt`.** Look for `GPTBot`, `ClaudeBot`, `PerplexityBot` and `Google-Extended`, and check whether they are allowed or disallowed. Then try `yoursite.com/llms.txt` — most sites return a 404. #### Do it three times Run the test on your own site, then on the two competitors who keep appearing in answers where you do not. Fill in this table: | | Body copy in source? | `ld+json` blocks | AI bots in robots.txt | llms.txt | |---|---|---|---|---| | You | | | | | | Competitor A | | | | | | Competitor B | | | | | Three rows is usually enough to end the platform argument inside your team. Either you are behind on the fundamentals — in which case the gap is visible in the table and the work is obvious — or you match them on every column and are still not cited, which is a different and more interesting problem. #### How to read it **You fail on body copy and they pass.** Platform or rendering is your constraint and it outranks everything else on your list. Nothing further down this page matters until it is fixed. **You match them everywhere.** Your platform is not the problem, and switching it will not help. This is the most common result among sites that have already done some AEO work, and it is the point where most teams keep buying more of what has stopped working. **They fail and you pass, and they are still cited.** The most useful outcome, because it disproves the premise directly. Rendering and schema are qualifying conditions, not competitive advantages. Something else is getting them chosen — most often that they are described consistently across the web and corroborated by sources other than themselves. #### What this test cannot tell you Which platform *you* should be on. That depends on who maintains the site, how much content you publish, whether you have developers, and what your team can operate without help — none of which appear in View Source. The table settles whether your current platform is holding you back. It does not choose the next one. It also cannot tell you why an engine picks one qualifying source over another. Once the columns match, the remaining levers are entity clarity and third-party corroboration, and those are off-page. [Run our free AEO audit](/audit) to get your row of that table filled in automatically, along with the parts of it a browser cannot see. ### Frequently asked questions #### What is the best website platform for AEO? There is no universal best platform; the right choice depends on your team's technical capacity. Webflow offers the strongest out-of-the-box AEO fundamentals for marketing teams, WordPress offers the most flexibility for teams comfortable with maintenance, and Sanity paired with a framework like Next.js offers the highest ceiling for teams with developers. What matters most is that the platform delivers content as server-rendered HTML, supports structured data (schema), and lets you control heading structure — and that you actually configure those things. #### Does the website platform really affect AI search visibility? Yes, significantly. The most important AEO factor is whether your content is present in the HTML that AI crawlers receive, because most AI crawlers do not execute JavaScript. Platforms that render pages on the server or serve static HTML (Webflow, WordPress, modern Wix Studio, or a headless setup like Sanity with Next.js) make content visible by default. Platforms that render content in the browser — such as default single-page apps from many vibe-code tools — can leave AI engines seeing a blank page until rendering is fixed. #### Why can't AI crawlers see JavaScript-rendered websites? Most AI crawlers fetch the raw HTML your server returns and do not run JavaScript the way a human browser does. If a page assembles its content in the browser after the initial load (client-side rendering), the crawler receives a near-empty HTML shell and cannot read the content. This is why server-side rendering, static site generation, or prerendering for crawlers is essential for AEO. #### Is Wix good for AEO in 2026? Modern Wix is far better than its old reputation. Newer Wix Studio sites use server-side rendering, resolving the JavaScript issues that historically hurt Wix on search, and include a Structured Data Manager for schema and an AI Visibility tool for tracking LLM mentions. The strongest capabilities are concentrated in the newer Studio platform rather than older Wix sites, so the specifics of your build matter. #### Can a vibe-code website (Lovable, Bolt, v0) be optimized for AEO? Yes, but usually not by default. These tools often produce single-page applications that AI crawlers can't read until server-side rendering or a prerendering service is added. Some, like Lovable, have introduced SSR for new apps and prerendering for verified crawlers. If you build on a vibe-code tool, verify how it renders content to crawlers and add a rendering solution before expecting AI citations. --- ### Article: How to Show Up in ChatGPT and Perplexity: A B2B Playbook **URL:** https://www.brandinglab.io/articles/how-to-show-up-in-chatgpt-and-perplexity **Published:** 2026-07-19 **Read time:** 8 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** AEO **Key takeaways:** - ChatGPT and Perplexity choose sources differently. Perplexity retrieves live pages and cites them in real time; ChatGPT leans on training data plus live browsing when it searches. You need to be readable by both. - Getting cited is about extractability, not ranking. Lead every section with a direct, factual sentence that stands on its own — that's the unit an answer engine lifts and attributes. - Third-party mentions matter as much as your own site. Perplexity often pulls from listicles, reviews, and comparison pages. If those don't mention you, you're invisible even with a perfect homepage. - Rendering is a silent killer. If your content only appears after JavaScript runs, most AI crawlers see an empty shell. Serve rendered HTML. - Schema and topical depth are the infrastructure. Structured data tells the model what you are; a cluster of related pages tells it you're authoritative on the topic. - You can measure this today. Run your buyer queries in both engines monthly and track whether you're named — presence or absence, not a rank. A prospect opens Perplexity and types "best B2B onboarding platforms for fintech." Three seconds later they have four vendors, a sentence on each, and a set of citation links. They click one, book a demo, and never run a Google search. You already know the stakes — being absent from that answer is the new version of being on page two. What you probably don't have is a concrete list of what actually moves the needle. This is that list: how ChatGPT and Perplexity decide who to cite, and the specific things you can change on your site to become one of the citations. ### How ChatGPT and Perplexity actually pick sources The two engines don't work the same way, and the difference changes what you optimize for. Perplexity is a retrieval engine: for most queries it searches the live web, reads the top results, and synthesizes an answer with citation links back to the pages it used. ChatGPT answers from its training data by default, but when it browses (or via SearchGPT) it retrieves and cites live pages much like Perplexity does. The practical implication: to show up in Perplexity you need to be in the live results it retrieves for a query *and* be clearly extractable once it lands on your page. To show up in ChatGPT you need both a strong presence across the sources it was trained on and clean, crawlable content for when it browses. Neither engine rewards keyword density or backlink volume the way classic SEO did — they reward clarity, structure, and being mentioned in the right places. We unpack the underlying shift in [why your B2B website isn't showing up in AI search](/articles/b2b-ai-search-visibility). ### Make your pages extractable, not just readable An answer engine cites the sentence it can lift cleanly and attribute with confidence. That means the first sentence under each heading has to work as a standalone answer — no throat-clearing, no rhetorical question, no "in today's fast-moving landscape." State the fact, then support it. Structure the page so a model can navigate it: H2 headings phrased the way a buyer would ask the question, short paragraphs, and a clear hierarchy. A wall of marketing copy is hard to extract from; the same content reorganized with direct topic sentences becomes citable. This is the same discipline that separates the sites that get cited from the ones that don't — the difference between [AEO and traditional SEO](/articles/aeo-vs-seo). ### Get mentioned where the engines look Your own site is only half the game. When Perplexity answers "best [category] for [market]," it frequently retrieves third-party pages — roundup listicles, review sites, comparison articles, Reddit threads — and synthesizes from those. If your company isn't named in that ecosystem, you can be absent from the answer no matter how good your homepage is. So the work extends beyond your domain: earn placement in the "best [your category]" roundups, keep your review-site profiles current and specific, and publish comparison content that names competitors honestly. Every credible third-party mention is another source the engine can pull your name from. This is slower than editing your own pages, but it's often the missing piece when a competitor keeps appearing and you don't. ### Fix the rendering problem before anything else If your content only exists after JavaScript executes, most AI crawlers see nothing. I learned this on our own site: I rebuilt brandinglab.io on a modern SPA stack, and within weeks our AI-search traffic vanished — the crawlers were pulling an empty hydration shell and moving on. The fix was serving a fully rendered version of each page to bots. Before you invest in content, confirm the engines can actually read you: view your page source (not the rendered DOM) and check the real text is present in the initial HTML. If it isn't, that's the first thing to fix — everything else is wasted until the content is visible. For React and other SPA stacks, the schema and rendering patterns we ship cover exactly how to do this. ### Add the structured data that tells models what you are Schema markup gives an answer engine a machine-readable statement of what your company is and what each page covers. At minimum: Organization schema site-wide, Product or Service schema on those pages, FAQPage schema where you answer questions, and Article schema on posts. It's the difference between a model inferring what you do and knowing it because you declared it in a format built for parsing. Be precise about this claim, because the primary sources do not support the strong version of it. Google states that [no special schema.org markup is required](https://developers.google.com/search/docs/appearance/ai-features) to appear in its AI features, and it retired FAQ rich results from Search in May 2026. What structured data still does is give a parser an explicit statement of what a page is rather than leaving it to infer — Bing, Perplexity and the RAG crawlers do read it. Schema won't rescue thin content, and on strong content the honest framing is comprehension, not ranking. Pair it with topical depth — a cluster of related pages around each core buyer question — and you're signaling authority in the way these systems actually assess it. To gauge where you stand, run yourself through the [AEO maturity model](/articles/aeo-maturity-model). ### Measure whether it's working There's no rank to track in AI search — you're either named in the answer or you're not. So the measurement is simple: list your 20 most important buyer queries, run each one in ChatGPT and Perplexity three times a month, and record whether you're cited, how you're described, and which competitors appear alongside you. That log is your scoreboard. When a change to your site or a new third-party mention moves you into an answer you were absent from, you'll see it — and you'll know what to do more of. Continuous monitoring is also where [an AEO monitoring service](/aeo-services/) earns its keep, tracking presence across engines so you don't have to check by hand. ### Where this fits in the bigger picture Most of these moves — extractable content, schema at the component level, crawlable rendering, topical clusters — are hard to bolt onto a legacy site and straightforward to build into a new one. That's why AI-search visibility is one of [the clearest signs you've outgrown your current website](/articles/six-signs-youve-outgrown-your-current-website), and why we treat it as a design-time decision in every [B2B website rebuild](/articles/b2b-website-rebuild-process). We did exactly this for Opsi Systems — an enterprise transportation-tech rebuild engineered for credibility and AI-search visibility from the ground up. **Want to know where you stand in ChatGPT and Perplexity right now?** [Book a free AEO audit with BrandingLab](/audit). We'll run your buyer queries, show you who's getting cited instead of you, and map the specific changes that get you into the answer. ### Frequently asked questions #### How do I get my company mentioned in ChatGPT? Getting cited in ChatGPT comes down to two things: being well-represented across the sources it learns from and browses, and having content it can cleanly extract and attribute. Publish clear, entity-specific content on your own site, earn mentions in credible third-party sources (reviews, roundups, comparison pages), implement structured data, and make sure your pages render real HTML that crawlers can read. There's no way to pay for placement — it's earned through clarity, structure, and presence across the web. #### How is showing up in Perplexity different from ChatGPT? Perplexity retrieves live web pages for most queries and cites them in real time, so being in the fresh search results it pulls — and being extractable once it lands on your page — matters most. ChatGPT answers from training data by default and retrieves live pages when it browses, so a strong, consistent presence across the web plus crawlable content serves you in both modes. Optimizing for extractability and third-party mentions helps you in both engines. #### What is generative engine optimization (GEO)? Generative engine optimization is the practice of structuring your content and web presence so generative AI engines — ChatGPT, Perplexity, Google AI Overviews, Claude — find, understand, and cite you in their answers. It overlaps heavily with answer engine optimization (AEO): both prioritize entity clarity, extractable content, and topical depth over the keyword density that traditional SEO chased. Google addresses both terms directly in its [guide to optimizing for generative AI search](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), arguing that from its side this is all still SEO — and it publishes separate [guidance on evaluating third-party SEO and AEO services](https://developers.google.com/search/docs/fundamentals/third-party-seo), worth reading before hiring anyone for this work, ourselves included. #### Why does my competitor show up in AI answers and I don't? Usually it's one or more of four structural gaps: their content states clearly what they are and yours hedges; they have structured data and you don't; they've built topical depth and you have isolated pages; or they're mentioned in the third-party sources the engine retrieves and you aren't. AI-search visibility also compounds — sources cited early get cited more — so the gap widens the longer you wait to close it. #### Does structured data (schema) help with AI search? Yes. Schema markup gives AI engines a machine-readable declaration of what your company is and what each page covers, which improves how confidently they can cite and describe you. At minimum, implement Organization, Product or Service, FAQPage, and Article schema. Schema won't fix thin content, but on substantive content it meaningfully improves extractability and attribution. #### How do I measure whether I'm visible in ChatGPT and Perplexity? Pick your 20 most important buyer queries and run each in ChatGPT and Perplexity three times, once a month, recording whether you're named, how you're described, and which competitors appear. There's no ranking position to track — the metric is presence or absence in the answer. Watching that log over time tells you which changes move you into answers you were previously absent from. --- ### Article: AI Overview Optimisation: What B2B Marketers Need to Know **URL:** https://www.brandinglab.io/articles/ai-overview-optimization-for-b2b **Published:** 2026-07-19 **Read time:** 7 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** AEO **Key takeaways:** - AI Overviews are Gemini-generated answers at the top of Google results, now live in over 200 countries and 40+ languages. They appear mostly on informational, question-style queries — exactly the queries B2B buyers use early in research. - When an AI Overview appears, organic clicks fall. Independent CTR studies consistently measure steep position-one declines on queries with an Overview present; simple definitional queries lose the most. - Being cited in the Overview recovers a meaningful share of those clicks. The brands named inside the answer keep visibility that uncited page-one rankings no longer get. - Google selects passages, not just pages. Query fan-out breaks a question into sub-queries and pulls the clearest extractable answer for each — so a well-structured section can be cited even when the page isn't the #1 result. - Third-party surfaces matter. Reddit threads, LinkedIn posts, review sites, and industry roundups are among the most-cited domains in AI answers; your own site is only half the game. - The fix is the AEO playbook, not a new discipline. Extractable first sentences, question-phrased headings, schema markup, and topical clusters serve AI Overviews, ChatGPT, and Perplexity alike. Open Google Search Console for almost any B2B site and you'll see the same chart: impressions climbing, clicks flat or falling. Your content is showing up more than ever — inside an AI-written answer the searcher never clicks past. That's Google AI Overviews at work, and for B2B marketers it changes the job. The goal is no longer just ranking on page one; it's being one of the sources the answer is built from. Here's how AI Overviews actually work, what they do to your traffic, and what to change. ### What are Google AI Overviews and how do they work? AI Overviews are AI-generated summaries that Google places above the traditional results, built with its Gemini models and linked to the sources they draw from. Launched in the US in May 2024, they have since rolled out to more than 200 countries and over 40 languages, and they sit alongside AI Mode — Google's separate, chat-style search experience. Under the hood, Google uses a technique it calls query fan-out. Google's own [guide to optimizing for generative AI features](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) describes it directly: a complex question is broken into concurrent related sub-questions, each is searched in parallel, and the results are synthesized into one answer with citations. The practical consequence for marketers is that Google is selecting *passages*, not just ranking pages — the clearest standalone answer to each sub-question is what gets lifted, wherever it lives. ### Do AI Overviews reduce clicks to my website? Yes — on queries where an AI Overview appears, organic click-through rates drop sharply, and every major independent study points the same direction. Position-one results lose a large share of their expected clicks when an Overview sits above them, because a meaningful slice of searchers gets the answer without clicking anything. The damage isn't evenly spread. Definitional and "what is X" queries lose the most — the Overview simply answers them. How-to and process queries hold up better, because readers still click through for depth. And the brands *cited inside* the Overview retain visibility and clicks that uncited rankings no longer get. That's the real takeaway: the penalty isn't for AI Overviews existing, it's for being absent from them. We covered why absence happens — and how it compounds — in [why your B2B website isn't showing up in AI search](/articles/b2b-ai-search-visibility). ### How does Google choose which sources AI Overviews cite? Google cites sources that its ranking systems already trust *and* that offer a cleanly extractable answer to one of the fan-out sub-questions. Strong rankings still help — they keep you in the candidate pool — but they no longer guarantee citation, and pages outside the top results get cited when a specific passage answers a sub-question better than anything above it. Two other patterns matter for B2B. First, entity consistency: Google cross-references how your brand is described across the web, so a site that states plainly what the company is — and matches how third parties describe it — is easier to cite with confidence. Second, third-party surfaces punch above their weight: Reddit, LinkedIn, review platforms, and "best of" roundups are among the most-cited domains in AI answers. If your category's roundups and comparison threads don't mention you, an Overview about your category can be built entirely without you. ### How do I optimize my B2B content for AI Overviews? Optimizing for AI Overviews means making every section of a page work as a liftable, attributable answer. The moves, in priority order: 1. **Phrase H2s the way buyers ask questions,** and make the first sentence under each heading a direct, standalone answer. That sentence is the unit Google extracts. 2. **Answer the sub-questions, not just the head term.** Query fan-out means a page that covers the follow-up questions — pricing factors, timelines, comparisons, risks — gives Google more passages to cite. 3. **Add schema markup** — Organization site-wide, Article on posts, FAQPage where you answer questions — so the models know what you are instead of inferring it. Be clear-eyed about what this buys you: Google states that [no special schema.org markup is required](https://developers.google.com/search/docs/appearance/ai-features) to appear in AI Overviews, and it removed FAQ rich results from Search in May 2026. Schema is a comprehension aid and a discipline that keeps metadata honest with visible content, not a lever on this surface. 4. **Build topical clusters.** A pillar page plus supporting articles that interlink signals the topical depth these systems read as authority. Gauge where you stand with the [AEO maturity model](/articles/aeo-maturity-model). 5. **Earn the third-party mentions.** Get into the category roundups, keep review profiles current, and show up where practitioners actually discuss your space. 6. **Make sure crawlers can read you.** If your content only renders after JavaScript, much of this is invisible to the systems doing the citing — the schema and rendering patterns for React SPAs cover the fix. ### Does traditional SEO still matter for AI Overviews? Traditional SEO still matters — it determines whether you're in the candidate pool Google synthesizes from — but it stopped being sufficient. Google's position is stronger than that: it argues optimizing for generative AI search simply *is* search optimization, and that the durable work is [creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) rather than chasing AI-specific tactics. Crawlability, indexation, site quality, and rankings remain the foundation; what's changed is that the last mile is now extractability and entity clarity rather than squeezing out one more position. That's the practical difference between classic SEO and answer engine optimization, and we've mapped it in detail in [AEO vs SEO](/articles/aeo-vs-seo). The good news: nothing you do for AI Overviews is wasted elsewhere. The same structure that gets you cited by Google gets you cited by ChatGPT and Perplexity — the playbook for those engines is in [how to show up in ChatGPT and Perplexity](/articles/how-to-show-up-in-chatgpt-and-perplexity). ### Where AI Overviews fit in your AI-search strategy Treat AI Overviews as one surface in a single AI-search program, not a separate project. One monthly log answers most strategy questions: run your 20 most important buyer queries in Google, ChatGPT, and Perplexity, three times each; record whether an AI answer appears, whether you're cited, and who is cited instead. Presence or absence — that's the metric. Most of what gets you cited — extractable copy, schema, clusters, clean rendering — is hard to retrofit and straightforward to build in from the start, which is why AI-search visibility is one of the [six signs you've outgrown your current website](/articles/six-signs-youve-outgrown-your-current-website) and a design-time decision in every [B2B website rebuild](/articles/b2b-website-rebuild-process) we run. **Want to know whether AI Overviews are citing you or your competitors?** [Book a free AEO audit with BrandingLab](/audit) — we'll run your buyer queries, show you who's in the answers, and map the changes that get you cited. ### Frequently asked questions #### What are Google AI Overviews? AI Overviews are AI-generated answers that Google displays above the traditional search results, built with its Gemini models and linked to the sources they draw from. They launched in the US in May 2024 and are now available in more than 200 countries and over 40 languages. They appear most often on informational, question-style queries. #### How do AI Overviews affect organic traffic for B2B websites? Queries that trigger an AI Overview send fewer clicks to organic results, with independent studies consistently measuring steep position-one CTR declines. Definitional queries lose the most clicks, while how-to and process content holds up better. Brands cited inside the Overview retain significantly more visibility than those ranking beneath it uncited. #### How do I get my content cited in an AI Overview? Structure each section as a liftable answer: a question-phrased heading followed by a direct first sentence that stands alone. Support it with schema markup, a topical cluster of related pages, consistent entity descriptions across the web, and mentions on the third-party surfaces Google cites, such as review sites and category roundups. Rankings keep you in the candidate pool; extractability gets you cited. #### Is AI Overview optimization different from AEO? No — optimizing for AI Overviews is answer engine optimization applied to Google's answer surface. The same fundamentals (extractable answers, structured data, topical depth, entity clarity, crawlable rendering) drive citations in AI Overviews, ChatGPT, and Perplexity. Treating them as one program avoids duplicated effort. #### What is AI Mode and how is it different from AI Overviews? AI Mode is Google's separate, conversational search experience — a chat-style surface powered by Gemini — while AI Overviews are summaries placed on the standard results page. Both use query fan-out and cite sources, so content optimized for one tends to surface in the other. B2B marketers should monitor their buyer queries in both. #### Do AI Overviews appear on B2B search queries? Yes — AI Overviews trigger heavily on the informational and question-style queries B2B buyers use during early research, such as definitions, comparisons, and process questions. Branded and late-stage transactional queries trigger them less often. That makes top- and mid-funnel content the priority for AI Overview optimization. --- ### Article: Webflow vs WordPress for B2B (Which One to Build On) **URL:** https://www.brandinglab.io/articles/webflow-vs-wordpress-for-b2b **Published:** 2026-07-19 **Read time:** 7 min read **Author:** Russel Davis, Founder, BrandingLab **Category:** Webflow **Key takeaways:** - Both Webflow and WordPress serve crawlable HTML by default, so both can be AEO-ready — rendering is not the dividing line. - Webflow fits marketing-led teams: publish without developers, low maintenance, pre-rendered static HTML from a CDN. - WordPress fits developer-led teams: deeper schema and SEO tooling via plugins, but you own patching, security, and performance. - The real decision is team technical capacity and how often marketing needs to ship — not a blanket platform winner. - Cost differs in shape, not just size: Webflow trades platform fees for less maintenance labor; WordPress trades cheaper software for ongoing upkeep. Typical B2B Webflow builds run $15k–$60k over 8–12 weeks. - Migrating WordPress to Webflow is routine if you map URLs and set 301 redirects to preserve SEO equity. Webflow vs WordPress is rarely a question of which platform is technically superior. Both can produce a fast, crawlable, AI-search-ready B2B website. The real question is which one your team can run well — the platform that wins on paper loses in practice if nobody maintains it. This guide compares the two on rendering and AEO readiness, maintenance burden, team fit, content modeling, and cost of ownership, with a verdict framed by team type rather than a blanket winner. ### What is Webflow best at for B2B? Webflow is best at letting marketing teams ship and iterate on a B2B site without waiting on developers. Pages are served as pre-rendered static HTML from a CDN, which means AI crawlers that don't execute JavaScript can read your content by default — no rendering workarounds required. Semantic HTML, metadata, sitemaps, robots.txt, and llms.txt are handled in the platform rather than bolted on. For content operations, Webflow's structured CMS collections give you clean content modeling — resources, case studies, integrations pages — that marketers manage directly. The trade-offs are real: CMS item limits can pinch large content operations, and advanced schema markup sometimes requires custom embeds rather than a native control. We cover the platform in depth in our [Webflow for B2B guide](/articles/webflow-for-b2b). ### What is WordPress best at for B2B? WordPress is best at flexibility and ecosystem depth for teams with engineering capacity. It server-renders PHP into crawlable HTML by default, so — like Webflow — AI and search crawlers see real content without executing JavaScript. Rendering is not the dividing line between these platforms. Where WordPress pulls ahead is the plugin ecosystem. SEO and schema tooling like Rank Math, Yoast, and AIOSEO covers 20+ schema types, llms.txt support, and even AI-citation tracking — capabilities that go beyond what Webflow offers natively. Content modeling is effectively unlimited if you build custom post types, and there's no hard item ceiling. The trade-off is that all of this depends on plugins, and plugins mean ongoing responsibility: security patching, compatibility testing, performance tuning, and general maintenance land on your team. ### How do Webflow and WordPress compare side by side? The honest comparison is a set of trade-offs, not a scoreboard. Here is how the two platforms differ on the dimensions B2B buyers actually weigh: | Dimension | Webflow | WordPress | |---|---|---| | Rendering & AI crawlability | Pre-rendered static HTML from a CDN; readable by non-JS crawlers by default | Server-rendered PHP → crawlable HTML by default | | AEO/SEO tooling | Built-in semantic HTML, metadata, sitemaps, robots.txt, llms.txt | Plugin-based (Rank Math, Yoast, AIOSEO): 20+ schema types, llms.txt, AI-citation tracking | | Schema depth | Solid basics; advanced schema can need custom embeds | Deepest schema coverage via plugins | | Maintenance | Platform-managed; low ongoing burden | Your responsibility: patching, security, performance tuning | | Team fit | Marketing-led teams publish without developers | Developer-led teams who can own the stack | | Content modeling | Structured CMS collections; item limits on large content ops | Effectively unlimited with custom development | | Cost model | Higher platform fees, lower ongoing labor | Lower software cost, higher maintenance labor | ### When should you choose Webflow? Choose Webflow if marketing owns the website and needs to ship without a developer queue. That pattern fits most B2B marketing sites: frequent landing pages, messaging tests, a content library managed by the people who write it. Choose Webflow if: - Your marketing team publishes and iterates often, and developer time is scarce or expensive - You want maintenance, hosting, and security handled by the platform - Your content model fits structured collections and stays within CMS item limits - You'd rather pay platform fees than staff ongoing site maintenance Typical B2B Webflow builds run $15k–$60k and take 8–12 weeks, depending on scope. If you're weighing a partner for the build, see our guide to choosing a [B2B Webflow agency](/articles/b2b-webflow-agency). ### When should you choose WordPress? Choose WordPress if you have a capable technical team and requirements that exceed what a hosted platform allows. This is not a consolation prize — for the right team, WordPress is the stronger choice, and we say so even though we ship mostly Webflow. Choose WordPress if: - You have developers (in-house or retained) who will own patching, performance, and security - You need deep schema coverage or SEO tooling beyond Webflow's native features - Your content operation is large enough that CMS item limits become a real constraint - You need custom functionality the plugin ecosystem already solves The condition is non-negotiable, though: WordPress's advantages only materialize if someone maintains it. An unmaintained WordPress site accumulates security exposure and performance debt that no plugin fixes. ### Which should a mid-market B2B company build on? For most mid-market B2B companies, the deciding factor is team capacity, not platform capability. If marketing leads the website and engineering time is scarce, Webflow's lower maintenance burden and marketer-friendly publishing usually win. If you have a developer-led web team with real ownership capacity, WordPress can match Webflow on AEO — its rendering is crawlable by default, and its plugin ecosystem arguably goes further on schema. Both platforms produce content AI search engines can read; what differs is who does the work to keep it that way. (New to answer engine optimization? Start with [what AEO is and why it matters](/articles/what-is-aeo).) BrandingLab is a B2B website and AEO studio, and a Webflow Accredited agency — we ship mostly Webflow for B2B marketing sites, but the honest verdict depends on your team, and we'll tell you when WordPress is the better fit. If you're deciding which platform to build on, [book a discovery call](/contact) and we'll scope it with you. ### Frequently asked questions #### Is Webflow or WordPress better for B2B? Neither is better across the board — the answer depends on your team. Webflow suits marketing-led teams that need to publish without developers and want low maintenance; WordPress suits developer-led teams that can own patching, performance, and security in exchange for deeper flexibility. Both serve crawlable HTML, so both can be AEO-ready. #### Is WordPress better for SEO than Webflow? WordPress has deeper SEO tooling through plugins — Rank Math, Yoast, and AIOSEO cover 20+ schema types, llms.txt support, and AI-citation tracking. Webflow covers the fundamentals natively: semantic HTML, metadata, sitemaps, robots.txt, and llms.txt, with pre-rendered static HTML that non-JavaScript crawlers read by default. In practice, execution and content quality decide rankings more than the platform; either can compete when run well. #### Which is cheaper long-term? It depends on where your costs sit. Webflow carries platform fees but offloads hosting, security, and maintenance, which lowers ongoing labor. WordPress software costs less up front, but you carry plugin management, security patching, and performance tuning — costs that show up as staff or agency time rather than a subscription line. For context, B2B Webflow builds typically run $15k–$60k over 8–12 weeks. #### Can you migrate WordPress to Webflow? Yes, and it's a common move for B2B marketing teams. The discipline that protects your SEO equity is thorough URL mapping with 301 redirects, so existing rankings and backlinks carry over to the new site. We walk through the full process in our [WordPress to Webflow migration guide](/articles/wordpress-to-webflow-migration-for-b2b). --- ### Article: B2B Brand Identity for AI Search: Building a Citable Brand **URL:** https://www.brandinglab.io/articles/b2b-brand-identity-for-ai-search **Published:** 2026-07-08 **Read time:** 9 min read **Author:** Russel Shalom Davis, Founder, BrandingLab **Category:** AEO **Key takeaways:** - AI engines cite brands as entities, not keywords — your brand needs a machine-readable identity. - Schema.org (Organization, Person, sameAs) is how you tell AI models who you are and what you do. - Consistent naming, descriptions and category positioning across the open web train the models. - Visual identity still matters, but for AI visibility, structured data does the heavy lifting. - The B2B brands winning in AI search treat entity-building as a first-class marketing discipline. Brand identity used to end at a logo, a colour palette and a tone-of-voice guide. In an AI-mediated internet, that is no longer enough. When a buyer asks ChatGPT "who are the best B2B web agencies for AI-native brands?", the model does not look at your Figma files. It looks at whether it recognises your company as a distinct **entity** — and whether the open web agrees on who you are and what you do. This is the shift from brand-as-visuals to **brand-as-entity**. It is the single most important brand strategy question for B2B teams in 2026. ### Why AI engines think in entities Large language models don't index pages the way Google's classic crawler did. They compress the web into a statistical map of entities and the relationships between them. An entity is anything with a stable identity — a company, a person, a product, a place, a concept. When Perplexity or ChatGPT answers a buying question, they retrieve passages from sources they can attribute to a **known entity**. If your brand isn't in that map, you don't get cited — no matter how good your website is. ### The three layers of a citable brand identity #### 1. Structured data on your own site Schema.org markup is how you introduce your brand to machines. At minimum, every B2B site should ship: - An `Organization` (or `ProfessionalService`) schema on the homepage, with `name`, `url`, `logo`, `description`, `sameAs`, `founder`, `areaServed` and `knowsAbout`. - A `Person` schema for each founder or key expert, linked via `@id` from the organization. - A `WebSite` schema with a `SearchAction` so the site is machine-readable as a corpus. The `sameAs` array is the bridge — it points the model at your LinkedIn, Crunchbase, GitHub, Clutch and any authoritative third-party profiles. This is how models resolve "BrandingLab" the string to BrandingLab the entity. #### 2. Consistent identity across the open web Models learn who you are from the sources they trained on. That means every mention of your brand should agree on the basics: the same legal name, the same category, the same founder story, the same city. Discrepancies confuse the model and dilute the entity. Audit your Crunchbase, LinkedIn, Clutch, G2, Wikipedia (if applicable), and personal author bios. If your homepage says "B2B website and AEO studio" but Crunchbase says "digital marketing agency", the model doesn't know which one you are. #### 3. Content that reinforces the entity Every article you publish should either: - Reinforce **what you do** (the services, methods, frameworks you own), or - Reinforce **who you are** (the founder's expertise, the company's point of view). Long-form content with clear author attribution, dates and headings trains the models to associate topics with your brand. Thin, generic content trains them to ignore you — and Google's guidance on [creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) remains the clearest published standard for the difference, whichever engine you are writing for. ### Frequently asked questions #### How is brand identity different for AI search vs traditional SEO? Traditional SEO optimised for keyword-to-URL matching. AI search optimises for entity-to-answer matching. Your brand needs to be a recognisable entity before any of its pages can be cited. #### Does visual identity still matter? Yes — for humans. Logo, typography and design still drive conversion once someone lands on your site. But visual identity is invisible to LLMs. Structured data helps them describe you accurately — with one honest caveat: Google states that [no special schema.org markup is required](https://developers.google.com/search/docs/appearance/ai-features) for its AI features. Schema is how you remove ambiguity about who you are, not a switch that makes you visible. Visibility comes from being a recognised entity across the open web. #### What's the fastest way to become a citable brand? Ship comprehensive Organization and Person schema, align your top five third-party profiles (LinkedIn, Crunchbase, Clutch, G2, personal bios), and publish two or three long-form articles per month that reinforce your category and expertise. #### How long does it take to appear in AI answers? We can only speak to what we have measured rather than an industry average. On the Opsi Systems build — architected for retrieval from the design stage rather than retrofitted — referrals from claude.ai and gemini.google.com appeared in analytics within the first 90 days of launch. A retrofit on an established site typically takes longer, because the content structure has to change before anything else can. ### The takeaway If you want to be recommended by ChatGPT, Perplexity and Google AI Overviews, your brand has to be a **thing the models recognise** — not just a website they can crawl. Structured data, aligned third-party profiles and expertise-rich content are the new brand identity system for B2B. --- ### Article: From Months to Seconds: Building Gazette-Search for the Collections Industry **URL:** https://www.brandinglab.io/articles/gazette-search-case-study **Published:** 2026-07-05 **Read time:** 19 min read **Author:** Shalom Petersen, Founder, BrandingLab **Category:** Case Study **Key takeaways:** - The 5-minute-per-search bar in South African collections was a bar a pre-AI small team had already failed to clear. A one-person shop with Claude cleared it — the unlock is a small operator shipping at a quality bar that used to require a team. - A dashboard that said 0.3% gazette coverage was measuring the wrong thing. Write down every metric on every dashboard and what it is actually measuring — before you need to trust it in a crisis. - When the product was defective, the right move was to absorb the cost of the fix, not pass it back to the user. 507 quiet retroactive watchlists beat one bulk "we're sorry" email. - Subscriptions are for founders who haven't yet learned what they don't know about their pricing. Credits plus Enterprise — usage-based for the long tail, contract-based for the head — is what most B2B products want to be eventually. - The most expensive bugs in a B2B product live at the seams between systems nobody owns: platform scratch space meeting a growing database, a cloud sync product meeting Git internals, a PDF parser meeting scanned pages. ## From Months to Seconds: Building Gazette-Search for the Collections Industry The 5-minute challenge, the Lovable-to-Claude pivot, the data crisis we found, the customer-ethics call I'm proudest of, and who's using it now. An associate of mine in the collections space had been watching me work on a concept. I showed him the prototype one afternoon, with the kind of energy you only have for the first SaaS you've ever built. His response, paraphrased close to verbatim: "Unless you can get search results in under 5 minutes, my industry isn't interested. We've already tried to build something like this — with a developer, before AI — and it was a mess." That's the inciting incident for this whole project. Not a market research deck. Not a competitive analysis. One industry insider, sitting across the table, setting a clear bar and quietly letting me know what had already failed. It's also why this case study is worth your time if you run a collections agency, a BPO, or a financial-services team in South Africa. Because the bar that associate set wasn't just met. It was lapped. And the story of how a one-person shop got from "interesting demo" to "30-year credit management firm on a 3-month professional contract" runs through every interesting infrastructure problem a B2B SaaS can have. Pull up a chair. ### Why <5 minutes is the bar that matters in collections Large collection agencies and BPOs in South Africa run hundreds of thousands of searches per month against the Government Gazette. They're verifying deceased estates. Insolvencies. Liquidations. Sales in execution. Name changes. Every ID they don't clear is a case they can't close, a fee they can't bill, a recovery that doesn't ship. Turnaround time isn't a feature for this segment. It's the entire product. The manual baseline is unspeakable. Searches on government sites take hours, days, and sometimes months. The official government source is technically online but locked behind a corporate authentication layer that rejects anything other than a live browser session — useless for any kind of programmatic search at scale. The most popular community-built mirror, which most previous attempts had been built against, had started returning broken files for parts of the archive. The legally-clean public archive of historical issues was authoritative and complete, but frozen at 2021. Every existing access path was broken in a different way. For due-diligence work, a false "nothing found" is not a cosmetic problem. It's a real one — with legal and financial consequences a search engine isn't supposed to be responsible for. A lawyer who closes an estate without finding an unfiled insolvency notice ends up in a courtroom six months later answering questions about due diligence they thought they'd done. A collections analyst who clears an ID against a stale dataset puts a recovery into a queue that should never have been opened. That's the problem space. The associate had clocked it. So had everyone else in his industry. None of them had a working tool for it. ### The first build, the Lovable wall, the move to Claude One developer (me). One repo. A pragmatic web stack. The kind of stack you ship in, not the kind you put on a slide. I'm a designer who learned to ship — not a career backend engineer. I started in Lovable. Lovable is excellent for what it's excellent for. Fast UI iteration. Opinionated full-stack scaffolding. The kind of platform that gets a working web app standing in an afternoon. If you've never used it and you're building a marketing site, a dashboard, or a structured CRUD application, it's a serious tool. None of those strengths were the problem this product had to solve. The challenge wasn't "ship a search interface." It was: return matches against a database of millions of rows, fast enough that a collections analyst doesn't notice the wait — sub-second in the happy path, in a tool a user might run a thousand times in a shift. That requires query design and index strategy and the kind of repo-wide refactoring an SPA builder isn't designed for. I battled to get the system to return results in time. Not Lovable's fault. The wrong tool for the layer of the build I was on. So I switched to Claude. Claude understood the goal. Not in a marketing sense — in the practical sense of being able to hold the whole codebase in mind. Walking me through database queries I'd designed without thinking hard enough about how they'd be searched. Finding why a specific search was slow and rebuilding the index that fixed it. The engineering decisions stayed mine. The speed of working through them changed completely. Hundreds of prompts later — over several months of iteration — we had a system returning matches in seconds. Against a 2GB database. From a single web instance. For a use case where the manual alternative takes hours, days, sometimes months. The 5-minute bar wasn't met. It was lapped. This is what working with an AI assistant looks like in 2026, in my experience. The AI doesn't replace engineering judgment, and it doesn't write your architecture for you. It removes the cost of moving across unfamiliar territory. The bar an associate gave me was a bar a pre-AI small team had already failed to clear. A one-person shop with Claude cleared it. That isn't "AI builds it for you." It's "a small operator can punch above their weight class." I keep coming back to that distinction because it's the actual unlock — for me, and for every client build I do at BrandingLab. If you've ever been quoted six months for a build that should take six weeks because the agency is staffing five people on it, you've felt the inverse of this principle. ### The day the data started lying Six months into running the product, I caught a pattern I'd been missing. Roughly 29.6% of the historical searches we'd served had been silently coming back empty — not because the IDs weren't in the gazettes, but because the gazettes themselves had never been read correctly on our side. Lawyers had searched for IDs and gotten "nothing found" on cases that were actually there. For due-diligence work, that's not a quality issue. That's a defective product. The first place this showed up was a dashboard that said we had "0.3% gazette coverage" — which almost made me panic before I realised the metric was lying to me. The 0.3% was the share of total rows in the database that were gazettes, not the share of gazettes we'd processed. Each gazette spawns hundreds of child notices, so gazettes are always going to be a small slice of the row count by design. The real problem was buried one layer down, in a different table, where I hadn't been looking. I almost trusted the dashboard. I have written down, since, every metric on every dashboard I run, and what it is actually measuring. That's a habit I owe to a near-miss on a Thursday morning. The why was less mysterious than the what. The historical data source we'd been pulling from had become unreliable — returning broken or substituted files for parts of the archive. On top of that, the PDF parsing library we used couldn't read scanned image-based PDFs at all, and a meaningful slice of the older legal gazettes are scanned image-based PDFs. The two failure modes overlapped, and the result was a real data gap nobody on our side had noticed. The fix was honest work. I investigated every alternative source — official, community, archival, commercial — and most were broken in some way. One legally-clean public archive of historical issues was authoritative and complete, just frozen at 2021. I migrated all historical backfill to that source and rebuilt the missing data. For everything from 2022 onward, the platform now runs a weekly fetch against the official source — matched to the Gazette's own publication rhythm (52 issues a year). Data stays current without manual intervention. So the archive that was 29.6% empty six months ago is now both backfilled to completeness and kept current automatically. The next time we have a data-quality issue, it'll be a new one, not the old one. That's not a flex. That's how compounding investment in infrastructure actually works. ### Five times the platform fought us Even with the application returning matches in seconds, the question of how we kept the data fresh nearly took us down. Five separate times. All while the live product was serving paying users. First try. I ran the data-recovery work inside the same machine that served search traffic. The recovery pegged the CPU. The health check (which was, in retrospect, running a heavy database query — never do this) failed. The cloud platform interpreted the failed health check as a dead service and restarted the whole instance every 60 seconds. The recovery job never completed. The site flickered for an hour while users tried to search and got intermittent errors. The lesson: never put a database query in your health check. I now write this down on a sticky note before every new project. Second try. I made the health check stop doing database queries. Moved the recovery work into a low-priority background process on the same machine. Hit the memory ceiling instead — the recovery job got killed silently every time, even after I upgraded the machine to 5GB of RAM. The old legal gazettes are giant scanned PDFs and parsing them eats memory in ways no documentation warns you about, and the machine was also serving live search traffic in the background, and the kernel just kept choosing the recovery process to sacrifice. Third try. I tried to move the recovery work to a completely separate machine, sharing the database file with the live service. Turned out the cloud platform attaches a database disk to exactly one machine at a time. The architectural path I was on was closed by a platform constraint I should have read about a month earlier. The lesson: sometimes the platform is the boundary, not your code. The mental model you have of "I can just spin up another worker" assumes a degree of decoupling between compute and storage that doesn't actually exist on most managed platforms. The resolution. I took the recovery off the cloud platform entirely. Downloaded the production database to my Mac, ran the recovery work locally where there were no users to disturb and no platform limits to fight, then shipped the fixed database back to production through two new admin endpoints I built specifically for the purpose. Took an evening to wire up. Took a weekend to actually run the recovery. Took a long while to talk myself into the fact that the right move was off-platform after I'd spent so long trying to make on-platform work. The kicker. After the recovered 2.6GB database went live, the whole site started failing every request with a 502 error. Searches returned what looked like JSON to the browser but was actually HTML. The cloud platform's working scratch space had a hard 2GB ceiling. My database had just grown past it. Every time the service booted, it got evicted within 90 seconds, and the cycle repeated. I moved the database off the scratch space onto persistent storage, resized that persistent storage from 2GB to 10GB, and the platform finally stopped fighting me. The line I keep repeating to myself, and now to clients: It wasn't memory. It wasn't health checks. It was disk space. The CPU and RAM I'd been blaming were a red herring. None of this was about search latency. Sub-second search was already solved at the application layer. The five attempts above are the story of keeping that capability alive every time we needed to refresh the data underneath it. Operating a SaaS is mostly the second story, not the first. The first one ends the day you ship the feature; the second one continues for as long as anyone is using it. ### A bug from outside the system One of the worst bugs in the entire project wasn't on the cloud platform at all. It was on my own laptop. The folder I'd put the source code in was being silently synced by a cloud drive product running in the background. Every time I tried to save a change in the source-control system, the sync would write a file in the middle of the lock mechanism, and the save would silently fail. The first hint was that commits were failing on push. The second hint was that the commits had never actually completed locally. The third hint was a stack overflow thread three pages down that mentioned the same product by name. I spent more hours on this than I want to put in writing before I noticed. Moved the folder. Solved. The lesson: sometimes the bug is in a product you weren't even thinking about. The harder a bug is to reproduce, the more likely it's a system you didn't know was touching your system. I now keep a written list of every background-running product on every machine I develop on, just so I have a place to start when a bug refuses to make sense. ### The customer-ethics call This is the moment I'm proudest of in the whole project. It's also the moment that probably tells you the most about how I'd handle a client build, so it's worth slowing down for. The data crisis meant real users had searched for real IDs and gotten "nothing found" — when the gazette had been there the whole time. For collections agencies and lawyers running due diligence, that's not a service issue. It's a defective product they had paid us for and trusted. The expected SaaS move was obvious. Email everyone. Announce the dataset is now improved. Tell them to re-search. They'd pay for the re-searches. We'd technically be in the clear. I didn't do that. Instead, I went through every historical "nothing found" search in the system and quietly created a free retroactive watchlist for each one. 507 of the 728 historically failed searches were identifier-based and matchable against the recovered dataset. When a watchlist entry matches, the user gets an automatic alert at no cost, forever. They never have to know there was a problem. They just get the answer they originally needed, when it became findable. A bulk announcement would have re-opened the trust question. ("Wait — your data was wrong? For how long? What else?") A quiet retroactive watchlist alert, framed as a notification the user signed up for, simply delivers the value they were trying to buy in the first place. No "we apologise" email. No "please re-search at no charge" prompt that turns a defect into a marketing moment. Just the answer they came for. The principle: When the product was defective, the right move was to absorb the cost of the fix, not pass it back to the user. I've been quietly running that test on every operational decision since. It would have been cheap to do the bulk announcement and pocket the upsell. It would also have been the kind of decision I'd be embarrassed to write down in a case study like this one. The fact that you can read about it here without me cringing is, in a small way, the actual proof that it was the right call. ### A lawyer and a BPO walk into the same SaaS This is the title of an act, not the start of a joke. The structural tension Gazette-Search has had to live with from day one is the pricing tension between two completely different ends of the same market. A lawyer running a single estate-due-diligence search on one ID has the potential to surface billable work worth tens of thousands of rand. That one search is worth R35 to them all day, every day — it replaces a manual gazette check that costs R500-plus and takes months. An enterprise BPO running hundreds of thousands of searches a month against a recovery book cannot pay R35 per search. The unit economics of debt collection do not survive it. Same query. Two ends of the market. A several-hundred-thousand-fold volume gap. Completely different economic value per search. My first instinct was wrong. I started with what every SaaS founder starts with: subscription tiers. Three plans at R1,500 / R4,000 / R6,000 a month. It looked sensible on a pricing page. It fit neither persona. The lawyer who runs three searches a year shouldn't be paying R1,500 a month. The BPO running hundreds of thousands of searches a month wasn't going to fit inside a R6,000 ceiling without the spreadsheet starting to argue. The model penalised both ends and only worked for a narrow middle that didn't really exist. The current model is credits plus Enterprise. Credit packs. Eight tiers, R35 a search at the single end down to R0.55 at the 200,000-credit Volume end — a 64× per-credit compression across the volume curve. Pay for what you use. Credits valid 12 months from purchase. The lawyer buys one credit for R35 — or a 100-credit Starter pack at R10 a search — and never thinks about a subscription. The BPO buys the 200,000-credit Volume pack at R0.55 a credit (or steps up to Enterprise), and the per-search cost survives their unit economics. Monthly buyers put any pack on auto-refill and save 10%. Both ends pay a price that matches the value the search is actually delivering to them. Enterprise. From R250,000 for 500,000-plus credits, custom MSA. Banks, bureaus, continuous monthly screening — the segment where contracts and SLAs matter more than per-credit pricing. I'll be honest about what's still in transition. I migrated off the subscription model to credit packs earlier in 2026. The pricing config and every customer-facing page shipped clean. A few of the payment-processor-dependent pieces — the business-verification gate for the bigger packs, the monthly add-ons, auto-refill recurring billing — are still partially shipped. Some pages still advertise things that aren't billable yet. I'm fine telling you that, because honesty about what's not yet shipped is part of what this case study is. The lesson, the kind I'm going to keep repeating to clients: Subscriptions are for SaaS founders who haven't yet learned what they don't know about their pricing. Credits-plus-Enterprise is what most B2B products want to be eventually — usage-based pricing for the long tail, contract-based pricing for the head of the curve, and the discipline to stop pretending one model fits both. If you've ever sat across the table from a buyer and watched them do the arithmetic on a tier that doesn't fit their actual usage, you know how much commercial damage a bad pricing structure does. The damage is silent because the buyer doesn't tell you they're rounding you down to "too expensive." They just don't come back. ### Who's using it now I held off writing this section until the rest of the case study was solid, because traction without a built product to back it up is just a slide deck. Here's where it is today. The anchor customer is a 30-year-old South African credit management firm on a 3-month professional contract. The kind of business that has been doing due-diligence work the manual way for three decades — and decided to test the seconds-not-hours version on a paying contract. They're not named in this article. The point isn't who they are; the point is the kind of customer they are. A large BPO is in commercial discussions with us for an Enterprise contract right now — the right end of the pricing curve described above. Specifics are confidential while we're in negotiation. A handful of other businesses and solo practitioners are running the free demo tier. Some will convert when their first batch of credits runs out and they take a clean look at what they got for it. What this means for the reader: the 5-minute bar an associate set in the opening paragraph is operational at customer scale. The pricing model is not a thought experiment. It's billing real businesses for real searches at the per-credit prices specified. That's enough. I don't want to over-sell what's still a young product. ### The breach runbook, built before the breach (and not yet drilled) South African data-protection law gives a company 72 hours from discovering a breach to notify both the data-protection regulator and every affected user. Most SaaS startups don't think about that until incident one. I built the response runbook first. Five phases — Identification, Containment, Assessment, Notification, Post-mortem. Each phase has the actual database queries, command-line steps, and decision rules you would run while the 72-hour clock is on. Not theatre. Operational steps. The supporting infrastructure is deployed. A structured audit log of every admin action. A notifications table that proves which user got told what, and when. A "preview" admin endpoint that dry-runs the affected-users list and the exact email body before anything sends, so the IC can read every word before any user does. A "notify" endpoint that paces the actual sends to stay inside the email provider's rate limits. The code is in production. The endpoints respond. Why build all of this cold. A runbook you write under stress is a runbook with mistakes in it. Writing it cold meant I could think about edge cases I'd never think of mid-incident — like what to do if email itself is the compromised channel (fall back to LinkedIn messages and a notice on the public site). Here's what I haven't done — and what it's quietly taught me about my own operational discipline. I have never run a drill against the runbook. The runbook itself opens with a line that says "Last drill: never." I keep telling myself I'll do one next quarter. Compliance infrastructure is the kind of thing that's easy to leave alone until you can't anymore — until an incident lands and you find out, in real time, which parts of your runbook actually work and which parts you wrote for a version of the code that has since changed. The honest version: Built it cold. That was the right call. Haven't kept it warm since. That's the next call. I think that's a better closing line than the alternative version of this section, where I'd have told you confidently that the runbook is "battle-tested." The truthful version is more useful — to me, to anyone reading this who's also let a piece of compliance infrastructure go un-drilled too long, and to any prospect of mine who'd want to know what kind of person they're hiring to build their own infrastructure. ### Where it goes from here A roadmap with no overpromising attached. The database migration. The infrastructure war story above is the story of one specific decision — keeping the database on the same machine as the web service. Moving to a managed database (and running data refresh as a fully isolated scheduled job) is the version where the five attempts in Act 4 never repeat themselves. Costed at roughly $45–$105 a month all in. Next major architectural project. International expansion — Sub-Saharan first. Most Sub-Saharan African countries — Zimbabwe, Nigeria, and others — use the same Government Gazette structure as South Africa. The same core search engine works against any of them with minimal change. Sub-Saharan rollout is the active next data project, and it's commercially significant for collection agencies and BPOs with cross-border recovery work — which is the segment Gazette-Search was already built for. UK gazette scaffolding sitting in the repo was the original proof that the architecture generalises; the Sub-Saharan rollout is what's actually next. Image-based PDFs. The scanned PDFs that yielded nothing earlier would yield real text under an OCR pass. That's a quality-of-corpus win sitting right in the backlog and the cleanest path to closing the long tail of historical gaps. Pricing model still in transition. The subscription-to-credit-packs migration is mostly shipped. A few payment-processor-dependent pieces — the verification gate, the monthly add-ons, auto-refill billing — are still pending. No "we're disrupting the industry" close. Just honest sequencing. ### What this taught me about how BrandingLab works Three lessons. Each one shows up in every client build I do, and each one is here because the Gazette-Search build is where I actually learned it. 1. Infrastructure debt compounds quietly, at the seams. Every problem in this build was where two systems met. The cloud platform's working storage meeting a growing database. A cloud file-sync product meeting source-control internals. A PDF parser meeting scanned image-based pages. The lesson isn't "test more." It's: look for the seams between systems and assume there's a hairline crack you haven't found yet. The most expensive bugs in a B2B product are never in one component. They're at the interface between two components nobody owns. 2. The default option is not always the right option. The most popular data source for what I was doing was fine until it wasn't. The official government source was correct but unreachable. A quieter, legally-clean archive — the one nobody talks about — was the one that worked. The same principle holds for every client build I do at BrandingLab. The popular CMS, the standard hosting choice, the obvious stack are correct most of the time and quietly wrong in the cases that matter. The work is knowing which case you're in, and being honest with the client when the obvious answer isn't the right one. 3. AI assistants don't replace engineering judgment. They remove the cost of moving across unfamiliar territory — and they let one-person shops compete with teams. I made every architectural call myself. Claude made it possible for me to make them across hundreds of prompts and several months of iteration, instead of the years it would have taken solo and pre-AI. The associate's 5-minute bar was a bar a pre-AI small team had already failed to clear ("it was a mess"). A one-person shop with Claude cleared it. That's the actual unlock — not "AI builds the product for you," but "a small operator can ship at a quality bar that used to require a team." This is what "B2B website and AI studio" means in practice at BrandingLab. I don't just build websites for clients. I run my own SaaS and feel every infrastructure call before I bring it to a client build. If you're a collections agency, a BPO, or a financial-services team running gazette searches — and you want to see what seconds-not-hours looks like inside your actual workflow — book a demo of Gazette-Search. The demo is real data against the live system, not a sandbox. If you're a B2B team with a project that doesn't fit a normal agency mould — including the kind of build where the only honest answer is "I'll prototype it on my own SaaS first" — talk to BrandingLab. A runbook you write under stress is a runbook with mistakes in it. I've been trying to write everything cold ever since. — Shalom ### Frequently asked questions #### What is Gazette-Search? Gazette-Search is a search product for the South African Government Gazette, built to let legal, collections, and financial-services teams verify deceased estates, insolvencies, liquidations, sales in execution, and name changes. It was built by BrandingLab as a first-party SaaS product rather than a client project. #### Why does a five-minute search time matter in collections? Large South African collection agencies and BPOs run hundreds of thousands of Gazette searches per month, and every ID they cannot clear is a case they cannot close and a fee they cannot bill. An industry insider set five minutes as the bar below which the segment would not be interested. Turnaround time is not a feature for this market — it is the entire product. #### Why did the build move from Lovable to Claude? The first version hit a wall on Lovable where the remaining problems were reasoning problems rather than scaffolding problems. Moving the work to Claude cleared that wall, though the finished product took hundreds of prompts and several months of iteration to reach sub-five-minute search results. The lesson was about matching the tool to the kind of problem, not about one platform being better in general. #### Who is using Gazette-Search now? The product is in commercial use, including a 30-year credit management firm on a three-month professional contract. The primary segment is large South African collection agencies and BPOs, alongside legal and financial-services teams doing the same verification work. #### What does this case study show about how BrandingLab works? It shows the studio building and shipping its own product end-to-end — infrastructure, data integrity, customer ethics, and breach planning included — rather than only advising clients. The same judgement applied here is what BrandingLab brings to client brand and website work. --- ### Article: The Real Cost of a Dev-Dependent Website (And What Marketing-Led Looks Like) **URL:** https://www.brandinglab.io/articles/dev-dependent-website **Published:** 2026-06-16 **Read time:** 9 min read **Author:** BrandingLab, Editorial **Category:** Strategy **Key takeaways:** - The real cost isn't slow turnaround — it's the experiments that never happen. When every change needs a developer, marketing stops testing new messaging, building campaign pages, and iterating on conversion. You lose the data you never collect. - Dev-dependency makes AEO impossible — and that's now a rebuild-level problem. Answer Engine Optimization requires content velocity, structured data on every page, and rapidly published content clusters. None of that happens when every change needs a developer. In 2026, a site that can't support AEO is a site that's losing ground in AI search every week. - Dev-dependency isn't a people failure — it's infrastructure debt. It happens when a website is treated as a one-time project rather than evolving infrastructure. CMS rigidity, eroded design systems, and broken staging environments compound quietly. - Marketing-led doesn't mean engineering-free. It means marketing handles the 80% of changes that don't need custom code — and engineering focuses on the 20% that does. - A marketing-led site runs on modular components, structured CMS collections, visual editing, and a design system that enforces brand consistency automatically — plus built-in AEO infrastructure like schema markup managed at the component level. Platforms like Webflow are purpose-built for this model. - 60-80% of website-related engineering tickets at most mid-market B2B companies are content or layout changes that a marketing team with the right tools could handle in an afternoon. ## The Real Cost of a Dev-Dependent Website (And What Marketing-Led Looks Like) Here's a scene that plays out every week at mid-market B2B companies: Marketing needs a landing page for a campaign launching Tuesday. They've got the copy, the design direction, and a clear conversion goal. They submit a request. Engineering looks at the backlog and says two sprints out — maybe three. The campaign launches without a dedicated page. Traffic goes to the homepage. Conversion is mediocre. Nobody's surprised. This isn't a failure of collaboration. It's a structural problem. The website was built in a way that requires a developer for virtually any change — and that dependency is quietly costing more than anyone has quantified. ### The visible cost vs. the real cost The visible cost is easy to spot: slow turnaround. A landing page takes weeks instead of hours. A testimonial update becomes a Jira ticket. A pricing change sits in a queue behind feature work. But the real cost is what doesn't happen because the friction is too high. Marketing stops proposing landing pages for mid-funnel campaigns because they know the page won't be ready in time. They stop testing new messaging variations because each test requires a dev ticket and a two-week cycle. They stop building out content hubs because adding new templates to the CMS is a project in itself. Over time, the team builds muscle memory around working around the website rather than through it. The site becomes a static artifact — updated quarterly at best — instead of a growth tool that evolves as fast as the business does. That's the real cost: not the slow changes, but the experiments that never run, the campaigns that never get their own page, and the data you never collect because the infrastructure made it too hard to try. And there's a newer cost that's compounding faster than any of these: AEO readiness. Answer Engine Optimization — the practice of structuring your site so AI-powered search engines can find, understand, and cite you — requires exactly the kind of work that dev-dependent sites make nearly impossible. Building content depth across topic clusters. Implementing structured data markup on every page. Publishing new content frequently enough to signal topical authority. Updating entity definitions as the business evolves. All of this requires a marketing team that can move fast and publish independently. If every piece of content needs a developer, you can't build the velocity that AEO demands — and your competitors, the ones who can publish freely, are training the models to cite them instead of you. ### How you got here Nobody builds a dev-dependent website on purpose. It usually happens through a combination of reasonable decisions that compound over time. The site was built by an agency or contractor three years ago. It worked well at launch. Then the team started making changes — a new section here, a custom layout there, a quick fix that became permanent. The original structure got layered over until only the person who built it (who's no longer around) could navigate the codebase confidently. The CMS was configured for the content that existed at launch, not for the content marketing would want to create two years later. Adding a new page type means modifying templates. Adding a new section means touching code. The visual editor, if there is one, breaks if you deviate from the three layouts it was set up to handle. The design system — if it was ever formalized — eroded. Components that were supposed to be reusable became one-offs. Brand consistency now depends on a developer manually matching styles rather than a system enforcing them. Marketing can't tell which components are safe to use and which ones will break something. The staging environment is either broken, confusing, or nonexistent. Publishing a change feels risky because there's no clean way to preview it. So changes get batched, reviewed, and deployed by engineering on their schedule — not marketing's. None of these things happened because someone made a bad decision. They happened because the website was treated as a project (build it, ship it, done) rather than as infrastructure (build it, maintain it, evolve it). ### What marketing-led actually looks like "Marketing-led" doesn't mean engineering is cut out. It means marketing can operate the website independently for the 80% of changes that don't require custom development — and engineering is freed up to focus on the 20% that actually needs them. In practice, that looks like: **Modular, component-based pages.** Marketing builds pages by assembling pre-designed, brand-consistent components — hero sections, feature grids, testimonial blocks, CTA modules. No code involved. The components enforce the design system automatically, so the output always looks right regardless of who assembled it. **A CMS built for how content actually works.** Collections for blog posts, case studies, team bios, product features — each with structured fields that marketing can populate without guessing at formatting. Content relationships (like linking a case study to a product page) are built into the structure, not hacked together with custom code. **Visual editing with real-time preview.** Marketing sees exactly what the page will look like as they build it. No staging environment gymnastics, no "it'll look different on the live site" surprises. What you see is what ships. **Publishing without a deploy cycle.** Content goes live when marketing says it's ready — not when the next deployment window opens. Changes can be scheduled, staged for review, and rolled back without touching a terminal. **A design system that holds.** Colors, typography, spacing, component variants — all governed by a system that marketing can use but can't break. Brand consistency isn't maintained by vigilance; it's maintained by structure. **Built-in AEO infrastructure.** Structured data markup managed at the component level, so every page automatically includes the schema that AI search engines need to parse and cite your content. Structured CMS collections that enforce entity-clear content by design. The ability to rapidly publish content clusters, FAQ sections, and comparison pages that build the topical depth AEO requires — without waiting for a sprint. This isn't a hypothetical. Platforms like Webflow were built specifically for this model — giving marketing teams direct control over their site while maintaining the design and performance standards that engineering cares about. And because AEO depends on content velocity and structural consistency, a marketing-led platform is no longer a nice-to-have — it's the operational foundation that makes AI search visibility possible. It's the same reason most modern B2B teams are moving away from legacy CMS platforms that were designed for a different era of web publishing and a different kind of search engine. ### The math on regaining control Here's a quick way to quantify what dev-dependency is costing you: Count the number of site-change requests that went through engineering last quarter. Estimate the average turnaround time. Now calculate how many of those were content or layout changes that a marketing team with the right tools could have done in an afternoon. For most mid-market B2B teams, that number is somewhere between 60% and 80%. That's 60-80% of website-related engineering time that could be redirected to product work — and 60-80% of marketing requests that could have shipped in days instead of weeks. The pipeline impact is harder to quantify but just as real. Every landing page that didn't get built is a campaign that ran at reduced effectiveness. Every messaging test that didn't happen is data you don't have about what converts. Every quarter the site sits unchanged is a quarter where conversion trends are driven by inertia rather than intention. ### When it's time to fix it If your marketing team has stopped asking for site changes because they know the answer will be "next sprint," the problem has moved past inconvenient into actively harmful. The website isn't a growth tool anymore — it's a bottleneck that's one of the clearest [signs you've outgrown your current site](/articles/six-signs-youve-outgrown-your-current-website/). The fix isn't incremental. You can't bolt marketing-led capabilities onto a dev-dependent architecture. It requires rethinking the platform, the design system, and the content model — which is exactly what [a well-structured rebuild](/articles/b2b-website-rebuild-process/) is designed to do. The good news: for most mid-market teams, this transition takes weeks, not months. And the ROI shows up immediately — in faster campaigns, more experiments, and a marketing team that starts treating the website as their most powerful tool again. Tired of waiting on engineering for every site change? [Talk to BrandingLab](/contact) about what a marketing-led website looks like for your team. ### Frequently asked questions #### What is a dev-dependent website? A dev-dependent website is a site where marketing, content, and design changes require a developer to implement — even for tasks like updating a testimonial, changing a headline, or building a landing page. This dependency typically results from a rigid CMS, an eroded design system, or a codebase that only the original builder understood. It slows marketing velocity and turns the website into a bottleneck rather than a growth tool. #### What does a marketing-led website mean? A marketing-led website is one where the marketing team can independently create, edit, and publish pages without writing code or filing engineering tickets. This is achieved through modular component libraries, a structured CMS with defined content types, visual editing with real-time preview, and a design system that enforces brand consistency automatically. Engineering remains involved for custom integrations and advanced functionality — but the day-to-day operation of the site is in marketing's hands. #### How does dev-dependency affect AI search visibility and AEO? Dev-dependency directly undermines Answer Engine Optimization. AEO requires consistent structured data markup across every page, frequent content publishing to build topical authority, rapid deployment of content clusters and FAQ sections, and the ability to update entity definitions as the business evolves. When every change needs a developer, marketing cannot maintain the content velocity or structural consistency that AI search engines need to recognize your site as an authoritative, citable source. Companies with marketing-led websites can implement and maintain AEO strategies independently — giving them a compounding advantage in AI search results. Learn more in [Why Your B2B Website Isn't Showing Up in AI Search](/articles/b2b-ai-search-visibility/). #### How do I know if my website is too dependent on developers? Common signs include: landing pages taking weeks instead of hours to publish, content updates requiring Jira tickets, a staging environment that's broken or confusing, a CMS that only supports the page layouts it was originally configured for, and a marketing team that has stopped requesting site changes because they know the turnaround will be too slow. If your marketing team works around the website instead of through it, the dependency has become a strategic problem. #### Can I make my existing website marketing-led without a full rebuild? In most cases, no. Dev-dependency is an architectural problem — it's baked into the platform, the CMS configuration, and the design system (or lack of one). Adding a visual editor plugin to a rigid codebase creates the appearance of flexibility without the substance. A proper fix usually requires rethinking the platform, content model, and component system from the ground up. Read our full process breakdown in [What a B2B Website Rebuild Actually Looks Like](/articles/b2b-website-rebuild-process/). #### What is the best CMS for a marketing-led B2B website? The best CMS for a marketing-led B2B website gives marketing direct page-building control through modular components, enforces brand consistency through a design system, supports structured content collections, and publishes without a deploy cycle. Webflow is purpose-built for this model — it combines visual editing, a component-based architecture, and a structured CMS in a single platform. Other options include headless CMS solutions paired with a front-end framework, though these typically still require developer involvement for page creation and layout changes. --- *BrandingLab helps mid-market B2B teams design and build websites that match the pace of their business. We specialize in Webflow builds, brand-driven redesigns, and sites engineered for AI-era discoverability.* --- ### Article: The B2B Guide to AEO: Moving from Search Engines to Answer Engines **URL:** https://www.brandinglab.io/articles/b2b-aeo-strategy-2026 **Published:** 2026-06-08 **Read time:** 14 min read **Author:** BrandingLab, Editorial **Category:** AEO **Key takeaways:** - AEO optimises for citation inclusion in AI answers, not ranking position on a SERP - LLMs retrieve from Bing and Google indexes — traditional SEO crawlability is a prerequisite - B2B AEO mechanics: clean H2/H3 structure, schema markup, named sources, consistent claims - Brand mentions across the web now function like backlinks did in 2015 — a primary authority signal - 90-day plan: baseline audit, fix indexability, rewrite top 10 pages, build authority and monitoring ## The B2B Guide to AEO: Moving from Search Engines to Answer Engines For fifteen years, B2B marketing teams built their pipelines on a single assumption: buyers type a query into Google, scan the blue links, and click. That assumption is breaking. By mid-2026, more than 60% of B2B technical research queries begin in an LLM — ChatGPT, Claude, Perplexity, or Google's AI Overviews — and the buyer never sees a ranked list of ten sources. They see one synthesised answer, sometimes with citations, often without. This is the shift from **Search Engine Optimization (SEO)** to **Answer Engine Optimization (AEO)**. It is not a rebrand of the same playbook. It is a different optimisation target, with different mechanics, different success metrics, and a different competitive landscape. This guide is written for B2B SaaS leaders, advisory firms, and demand-gen teams who already do SEO well and now need to understand what AEO requires — strategically, structurally, and operationally. ### What is Answer Engine Optimization? Answer Engine Optimization is the practice of structuring your content, data, and authority signals so that large language models (LLMs) and AI search engines cite your brand when a buyer asks a question. The "answer engines" that matter for B2B: - **ChatGPT** (with web browsing and the SearchGPT layer) - **Claude** (with web search) - **Perplexity** (citation-first by design) - **Google AI Overviews** (synthesised summaries above traditional results) - **Microsoft Copilot** (Bing-indexed, ChatGPT-grounded) - **Gemini** (Google's consumer and Workspace assistant) Where SEO optimises for *ranking position*, AEO optimises for *citation inclusion*. A page that ranks position 8 on Google is invisible in the traditional sense — most clicks die at position 3. But the same page, if structured cleanly and authoritatively, can be cited by ChatGPT in 40% of the answers it generates on that topic. That citation drives qualified, high-intent traffic to your site — buyers who already trust your brand because an AI named you. ### SEO vs AEO: The strategic shift | Dimension | SEO (2010–2024) | AEO (2025+) | | --- | --- | --- | | Optimisation target | Ranking position on a SERP | Inclusion in a synthesised answer | | Primary asset | Keyword-targeted pages | Structured, citable claims | | Success metric | Organic clicks, position | Citation rate, referral traffic from LLMs | | Content format | Long-form, keyword-dense | Modular, scannable, claim-based | | Authority signal | Backlinks, domain authority | Brand mentions, structured data, factual consistency | | Update cadence | Quarterly refresh | Monthly factual review | | Competitive moat | Domain age and link equity | Distinctive perspective and verifiable data | The mental model that helps most B2B teams: **SEO is a popularity contest, AEO is a credibility contest.** Google ranks pages by signals of relevance and authority that compound over years. LLMs cite sources by signals of factual reliability and structural clarity that can be earned in weeks — *if* you write the right way. ### How LLMs decide who to cite Every B2B AEO strategy starts here. If you don't understand the citation mechanics, you are guessing. #### 1. The corpus LLMs are trained on a snapshot of the open web, plus licensed datasets (news, books, academic papers, code). For *current* queries, they augment training data with live retrieval — typically Bing's index (ChatGPT, Copilot), Google's index (Gemini, AI Overviews), or a custom crawl (Perplexity, Claude). What this means: if you are not indexed by Bing and Google, you do not exist to most answer engines. AEO begins with traditional crawlability. #### 2. The retrieval layer When a user asks a question, the LLM does not search its training data — it issues 2–8 search queries to a live index, reads the top results, and synthesises an answer. The pages it reads are usually: - Top 10 organic results for the query - Pages with high topical authority signals - Pages that match the *structural shape* of an answer (lists, definitions, comparisons) Your AEO job is to be in those top 10, *and* to be structurally easy to extract from. #### 3. The synthesis layer The LLM reads the retrieved pages and generates an answer. It chooses which sources to cite based on: - **Specificity** — concrete numbers, dates, named entities - **Clarity** — clean H2/H3 hierarchy, short paragraphs, definition-style openings - **Consistency** — claims that match what other authoritative sources say - **Authority** — domain reputation, author credentials, schema markup Pages that read like marketing copy get summarised but rarely cited. Pages that read like a well-edited reference document get cited by name. ### The B2B AEO checklist This is the playbook we use with B2B SaaS and advisory clients. Work through it in order — each step compounds on the previous. #### Step 1 — Audit your current AI visibility Before changing anything, measure. For 20–30 queries your buyers actually ask, prompt ChatGPT, Claude, and Perplexity and record: - Is your brand cited? (yes / no / paraphrased without citation) - Which competitors are cited? - What sources are cited *instead* of you? This is your baseline. Re-run quarterly to measure progress. #### Step 2 — Fix indexability LLMs cannot cite what they cannot read. The most common B2B AEO failure is not strategy — it is a single-page-app website that renders content client-side and serves an empty HTML shell to crawlers. Check: - Server-side rendering or prerendering on every page that matters - `robots.txt` does not block GPTBot, ClaudeBot, PerplexityBot, or Google-Extended - Sitemap is current and submitted to Bing and Google - Schema.org markup on Organization, Article, FAQPage, and Product where applicable #### Step 3 — Restructure your top 20 pages Pick the 20 pages that already drive the most pipeline. Rewrite them so each one: - Opens with a one-sentence definition of the topic - Uses H2s phrased as questions or claims a buyer would search - Includes a comparison table if the topic involves a choice - Cites named sources for every non-obvious factual claim - Ends with a clear takeaways block This is not "writing for AI". It is writing for a reader who skims, which happens to be the same shape LLMs extract well. #### Step 4 — Build a claim library Identify the 30–50 factual claims your firm wants to own — statistics, definitions, frameworks, methodologies. Publish each one on a canonical page, with a citation to your primary research or source. Repeat the same claim, in the same words, across multiple pages (blog, product, case study). Consistency is a citation signal. #### Step 5 — Earn unstructured citations LLMs notice when your brand is mentioned across the web — even without a backlink. Prioritise: - Guest posts on industry publications - Podcast appearances with show-note transcripts - Conference talks with public recordings - Customer-driven case studies and review-site presence Brand mention frequency now functions like backlinks did in 2015 — a primary signal of authority for retrieval-augmented LLMs. ### Common B2B AEO mistakes After working on AEO with mid-market and enterprise B2B teams since 2024, the same five mistakes recur: 1. **Treating AEO as a content task.** It is a content, structure, and authority task. Skipping any one of the three breaks the chain. 2. **Optimising for ranking, not citation.** A page that ranks #1 with thin, marketing-heavy copy will be summarised and dropped. A page that ranks #6 with clean, citable claims will be quoted by name. 3. **Blocking AI crawlers in `robots.txt`.** Some legal teams have done this defensively. It means zero AI citations. The right answer is allow + monitor, not block. 4. **Ignoring schema markup.** Schema is not optional for AEO. Organization, FAQPage, and Article schema directly improve citation rates in Google AI Overviews. 5. **Measuring with Google Search Console.** GSC does not show LLM referrals. You need a separate monitoring layer — manual prompt audits, or a tool like our [AEO monitor](/aeo-monitor). ### What stays the same It is easy to read the shift from SEO to AEO and assume the old playbook is dead. It is not. Foundational SEO mechanics still matter — they are now table stakes rather than a competitive moat. - **Crawlable, fast, well-structured sites still win.** AEO requires SEO. - **Topical authority still compounds.** A site with 200 pages on B2B SaaS will out-cite a site with 20. - **Backlinks still help.** They are a stronger signal than ever for *which* of your pages get retrieved. The shift is additive, not subtractive. B2B teams that already do SEO well are 12–18 months ahead of teams starting from scratch. ### What changes for B2B specifically Consumer brands have a different AEO problem — high search volume, low decision stakes. B2B AEO has the opposite shape: - **Lower query volume, higher pipeline value.** A single citation in a CFO's ChatGPT session can drive a six-figure deal. - **Long, multi-turn research sessions.** Buyers ask 8–15 questions across a vendor shortlist. You need to be cited consistently across the funnel, not just on the opening query. - **Trust signals matter more.** Author credentials, customer logos, named case studies, and verifiable data are weighted heavily by LLMs on B2B topics. - **Pricing transparency wins.** LLMs cite pages with concrete pricing, even ranges, far more often than "contact us" pages. ### A 90-day B2B AEO plan If you are starting from zero, this is the sequence we recommend. **Days 1–14 — Baseline.** Run the visibility audit (Step 1 above). Document where you stand on 25 priority queries. Identify your three strongest competitors in AI search. **Days 15–30 — Foundations.** Fix indexability. Add or repair schema markup on every priority page. Resolve any robots.txt or rendering issues blocking AI crawlers. **Days 31–60 — Rewrite the top 10.** Restructure your ten highest-value pages using the format above. Publish a canonical "what is X" definition page for each of your three top-of-funnel topics. **Days 61–90 — Authority and measurement.** Begin a structured outreach programme for unstructured citations (podcasts, guest posts, review sites). Set up monthly LLM visibility monitoring. Re-run the baseline audit and measure delta. By day 90, well-executed B2B teams typically see a 2–4x increase in citation rate across their target query set. ### How BrandingLab approaches B2B AEO We build Webflow and Next.js sites for B2B SaaS and advisory firms with AEO as a first-class concern from day one. That means server-side rendering by default, schema markup baked into every template, content structured for citation extraction, and a monitoring layer to track which LLMs are citing the brand and which competitors are winning queries. If you are a B2B leader thinking about AEO seriously for 2026, start with our [AEO audit](/audit) or talk to us about a [strategic AEO sprint](/aeo-services). ### FAQ #### What is the difference between SEO and AEO? SEO optimises for ranking position in traditional search engines like Google. AEO optimises for citation inclusion in AI-generated answers from systems like ChatGPT, Claude, Perplexity, and Google AI Overviews. SEO is a popularity contest; AEO is a credibility contest. #### Does AEO replace SEO? No. AEO requires SEO as a foundation — LLMs retrieve from the same indexes Google ranks against. The shift is additive: traditional SEO mechanics are now table stakes, and AEO is the new layer of competitive advantage. #### How do I know if ChatGPT is citing my brand? Manually prompt ChatGPT, Claude, and Perplexity with the queries your buyers ask and record citations. For continuous monitoring, use a tool like BrandingLab's AEO monitor to track citation rates across LLMs over time. #### How long does AEO take to show results? Most B2B teams see measurable citation rate improvements within 60–90 days of restructuring their top pages, fixing indexability, and adding schema markup. Authority-driven gains from unstructured citations compound over 6–12 months. #### Should I block AI crawlers like GPTBot in robots.txt? For most B2B brands, no. Blocking AI crawlers guarantees zero citations from those systems. The competitive cost is far higher than the perceived IP risk. Allow + monitor is the right default; only block if you have a specific legal reason. --- ### Article: What is Answer Engine Optimization? The B2B Guide to AEO **URL:** https://www.brandinglab.io/articles/what-is-aeo **Published:** 2026-06-05 **Read time:** 9 min read **Author:** BrandingLab, Editorial **Category:** AEO **Key takeaways:** - AEO is the practice of earning citations inside AI-generated answers from ChatGPT, Claude, Perplexity and Google AI Overviews. - 89% of B2B buyers now use generative AI in the purchase journey — citation share is the new market share. - Citation depends on three layers: technical foundation, content structure, and brand entity signals. All three must be in place. - Open every page with a one-sentence definitional answer. That sentence is what engines extract. - Allow GPTBot, ClaudeBot, PerplexityBot and Google-Extended in robots.txt. Blocking them blocks your future pipeline. - Expect three to six months for citations to start appearing on an established domain. The work compounds. Answer Engine Optimization (AEO) is the practice of structuring your content, brand and technical foundation so that AI answer engines — ChatGPT, Claude, Perplexity, Gemini and Google's AI Overviews — cite your business when buyers ask questions in your category. For B2B teams, AEO is no longer optional. In February 2024, [Gartner forecast a 25% drop in traditional search engine volume by 2026](https://www.gartner.com/en/newsroom/press-releases/2024-02-19-gartner-predicts-search-engine-volume-will-drop-25-percent-by-2026-due-to-ai-chatbots-and-other-virtual-agents) as buyers moved research into conversational AI. That deadline has now passed and the headline number did not land — Google held its share by absorbing AI into the results page rather than losing queries to chatbots. The underlying shift was real even though the forecast was not: buyers now arrive at your site having already asked a model, and the companies named in that answer own the consideration set. This guide explains what AEO is, how answer engines actually pick sources, and exactly what a B2B team should do this quarter to start getting cited. ### What is Answer Engine Optimization? Answer Engine Optimization is the discipline of earning citations inside AI-generated answers. Where SEO optimised for ten blue links, AEO optimises for one synthesised paragraph with two or three named sources. The unit of distribution has changed: a buyer no longer browses a SERP and picks a result. They read an answer and trust the brands the answer mentions. AEO sits at the intersection of three things: - **Technical foundation** — clean HTML, schema markup, server-rendered content, fast load times, indexable pages. - **Content structure** — semantic headings, definitional opening sentences, lists, tables, FAQs, original data. - **Brand authority** — third-party mentions, consistent entity signals across the web, a recognisable point of view. Without all three, your content is invisible to the systems that increasingly mediate B2B research. ### Why AEO matters for B2B specifically B2B buyers are exactly the audience that adopted ChatGPT fastest. According to Forrester, 89% of B2B buyers now use generative AI at some stage of the purchase journey, most heavily in the awareness and shortlist phases — the phases where pipeline is won or lost. Three structural reasons AEO disproportionately affects B2B: 1. **High-intent questions are conversational.** "What's the difference between [vendor A] and [vendor B] for a 200-person engineering org" is a ChatGPT query, not a Google query. The buyer asks the model directly. 2. **Trust is concentrated.** AI engines cite a small number of sources per answer. If the model decides three companies are the canonical players in your category, the rest get no consideration. 3. **The funnel shortens.** Buyers arrive at sales conversations already informed — and already biased toward whoever the model mentioned by name. If your competitors are being cited and you aren't, your pipeline will compress before your analytics shows it. By the time the demo requests drop, the damage is six months old. ### How LLMs actually pick sources Understanding citation mechanics is the difference between guessing at AEO and engineering for it. Each major engine has a slightly different retrieval pipeline, but the shared logic is consistent. #### ChatGPT (with browsing) and ChatGPT Search ChatGPT uses Bing's index as its primary retrieval layer, augmented with OpenAI's own crawler (GPTBot). When a user asks a question, ChatGPT issues several reformulated search queries, retrieves the top results, and synthesises an answer. Sources that appear in the top 10 of Bing for those reformulated queries are the candidate pool. Pages with clear definitional sentences, structured data and recognisable brand entities are favoured in the final cite list. #### Claude Claude's retrieval (via the web search tool) leans on Brave Search and runs heavier reasoning over fewer sources. Claude is unusually sensitive to source credibility signals — domain authority, author bylines, and external mentions — and tends to cite long-form, deeply argued pages rather than thin SEO content. #### Perplexity Perplexity is the most transparent. It runs multiple search engines in parallel, ranks results with its own model, and shows you exactly which sources it used. Perplexity heavily favours pages that answer the question in the first 100 words, have clear sections, and include data or original research. #### Google AI Overviews and Gemini Google AI Overviews use Google's full search index plus the Knowledge Graph. Pages that rank in the traditional top 10, have rich schema markup, and have strong entity associations are most likely to be summarised. AI Overviews are aggressively conservative — they cite high-trust domains and rarely surface unknown brands. The common thread: **rank well in classical search, structure your content for extractive answers, and build entity authority across the web.** No AEO tactic works in isolation. ### The B2B AEO Checklist This is the working checklist we use at BrandingLab when running an AEO programme for a B2B client. Work through it in order. #### 1. Technical foundation - Server-render or pre-render every page that needs to rank. Single-page apps without SSR are largely invisible to GPTBot and Bingbot. - Make sure `robots.txt` allows `GPTBot`, `ClaudeBot`, `PerplexityBot`, `Google-Extended` and `OAI-SearchBot`. Blocking them blocks your future pipeline. - Achieve a Lighthouse performance score above 90 on mobile. Slow pages are deprioritised. - Use semantic HTML — `
`, `
`, `

` through `

` in order, real `` elements, real lists. #### 2. Schema markup Google is explicit that [no special schema.org markup is required](https://developers.google.com/search/docs/appearance/ai-features) to appear in AI Overviews, and it removed FAQ rich results from Search entirely in May 2026. We still ship the markup below for two reasons: Bing, Perplexity and the RAG crawlers do parse it, and maintaining it forces your metadata and your visible content to stay honest with each other. - `Organization` schema on every page, with a complete `sameAs` array linking to your LinkedIn, Crunchbase, GitHub and other authoritative profiles. - `Article` schema on every blog post, with `author`, `datePublished` and `wordCount`. - `FAQPage` schema on any page with question-style headings. - `BreadcrumbList` schema for navigational clarity. - `Product` or `Service` schema on commercial pages, with `aggregateRating` if you have legitimate review data. #### 3. Content structure - Open every page with a one-sentence, definitional answer to the page's core question. This sentence is what answer engines extract. - Use H2s that read like questions. "What is X" / "How does X work" / "When should you use X". - Add a comparison table on any "vs" or category page. Tables get extracted intact. - Include a short FAQ block at the bottom of every pillar page covering the three or four questions buyers actually ask in sales calls. - Publish original data, benchmarks or frameworks. Engines disproportionately cite content that contains numbers nobody else has. #### 4. Brand and entity signals - Maintain a single, consistent brand entity across the web — same legal name, same description, same logo, same `sameAs` profiles. - Earn mentions on third-party sites that the models already trust — industry publications, podcasts, podcast show notes, partner blogs, Crunchbase, G2, Capterra. - Publish an `about` page that reads like an entity definition. Who you are, what category you serve, who your customers are. Models use this verbatim. - Get cited in directories and "best of" listicles in your category. Models lean on these for shortlist construction. #### 5. Measurement - Track citations each month across ChatGPT, Claude, Perplexity and Google AI Overviews for your top 20 buyer-intent queries, running each query three times because answers vary. For ongoing coverage, [BrandingLab's AEO monitoring](/aeo-services/) tracks this weekly so you don't have to check by hand. - Watch referral traffic from `chat.openai.com`, `perplexity.ai` and `claude.ai` in GA4. The volumes are small but the intent is enormous — these visitors convert at multiples of organic. ### Common AEO mistakes B2B teams make - **Treating AEO as a wholly separate discipline from SEO.** Google's [guide to optimizing for generative AI features](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) argues the two are the same work, and on the technical foundation it is right: crawlability, indexation and page experience are identical prerequisites for both. Where the emphasis genuinely differs is the unit of success. SEO succeeds when a page ranks. AEO succeeds when a passage is lifted and attributed. Optimising for the second without doing the first produces nothing. - **Hiding answers behind brand voice.** Witty intros and metaphor-heavy openings get skipped. Lead with the answer; add personality in paragraph two. - **Publishing thin content faster.** Models reward depth, not volume. One 2,500-word pillar beats ten 600-word posts. - **Ignoring third-party signals.** You cannot AEO your way to authority from your own domain alone. Mentions on sites the model trusts are non-negotiable. - **Blocking AI crawlers by default.** Many enterprise IT teams added `GPTBot` to `robots.txt` in 2023 "to be safe". Reverse it. ### How long does AEO take to work? Three to six months for a structured programme on a domain with existing authority. Six to twelve months for a newer domain. Citations are a lagging indicator — the technical and content work compounds, then citations appear in clusters once your brand entity crosses a recognition threshold inside the models. The teams that started in 2024 are already being cited in 2026. The teams starting now will be cited in 2027. The teams waiting until they "see what happens" will not be cited at all. ### Frequently asked questions #### What is the difference between AEO and SEO? SEO optimises a page to rank in a list of links. AEO optimises a page to be extracted and cited inside a generated answer. SEO tactics are a prerequisite for AEO — if you cannot rank in classical search, you cannot be retrieved by answer engines — but AEO adds structural, entity and citation-earning work on top. #### Is AEO the same as Generative Engine Optimization (GEO)? Effectively yes. AEO, GEO and AI SEO are competing terms for the same discipline. The industry has not settled on a winner. We use AEO because it most clearly describes the goal: being cited in answers. Google groups both terms together and publishes [guidance on evaluating third-party SEO and AEO advice](https://developers.google.com/search/docs/fundamentals/third-party-seo) — worth reading before you hire anyone for this, including us. #### Which AI engine should B2B brands optimise for first? Optimise for ChatGPT first. It has the largest user base, the most B2B usage, and its retrieval pipeline (Bing-based) overlaps heavily with what works for Google AI Overviews. Wins on ChatGPT tend to transfer. #### Do I need to publish more content to do AEO well? Not necessarily. Most B2B sites have enough content but the wrong structure. An audit of existing pillar pages — tightening openings, adding schema, restructuring headings, adding FAQs — usually delivers more citations than a new content sprint. #### How do I know if AEO is working? AEO is working when your company appears in AI answers to your buyers' questions, and is described accurately. BrandingLab recommends tracking three signals: citations for your top 20 buyer-intent queries in ChatGPT, Claude, Perplexity and Google AI Overviews, checked monthly and run three times each because answers vary; referral traffic from chat.openai.com, perplexity.ai and claude.ai in GA4; and prospects saying in sales calls that an AI assistant recommended you. There is no ranking position to watch. The measure is whether you are named, how accurately you are described, and which competitors appear alongside you. --- If you want help running AEO for your B2B brand, BrandingLab runs structured AEO programmes for enterprise teams. See our [AEO services](/aeo-services) page for how we work, or [request a quote](/request-a-quote) for your site. --- ### Article: Opsi Systems — Enterprise Transportation Technology Website **URL:** https://www.brandinglab.io/articles/opsi-systems-90-days-data **Published:** 2026-05-08 **Read time:** 8 min read **Author:** Russel Shalom Davis, Founder, BrandingLab **Category:** Case Study **Key takeaways:** - The Opsi Systems site grew out of an existing Tramm retainer — proof of work won the parent-brand brief. - AEO is a continuous retainer activity, not a launch deliverable, in a world of ChatGPT, Perplexity, and Google AI Overview research. - Low bounce on intent pages (Contact 12%, Delivery 0%) signals the right enterprise buyers found the right content. - Referrals from claude.ai and gemini.google.com confirm FAQ schema and AEO architecture surfacing in AI-generated answers. - 4 weeks Figma to live — full Webflow build, custom Lottie animations generated via Claude Code, and CMS handover. ### Overview This project didn't start with Opsi Systems. It started with Tramm. BrandingLab was brought in on a retainer to work on [tramm.global](https://www.tramm.global) — the website for Opsi's flagship transportation management system. That engagement involved ongoing SEO and AEO optimisation, content architecture, and digital strategy for Tramm TMS and the Chora GPU optimization engine. Having seen what BrandingLab could do for the Tramm brand, the team at Opsi Systems — the corporate parent behind Tramm and Chora — decided to brief us on rebuilding the Opsi corporate website. The result was [opsisystems.com](https://www.opsisystems.com). Opsi Systems operates across 4 global regions and serves enterprise logistics environments where complexity is the norm — global 3PLs, private fleets, retail, FMCG, and manufacturing. BrandingLab designed and built opsisystems.com as a full Webflow website that positions Opsi as a credible enterprise technology parent and communicates platform depth, global scale, and governance standards to demanding B2B buyers. Critically, this is not a one-time project. BrandingLab continues to work with Opsi Systems on an ongoing retainer — optimising content, strengthening AEO structure, and ensuring the site is found by the right buyers through AI-powered search tools. In a world where enterprise buyers increasingly use tools like ChatGPT, Perplexity, and Google's AI Overview to research platform decisions before visiting any website, AEO is not a launch activity. It is a continuous one. ### The Challenge Enterprise software buyers evaluate risk as much as they evaluate features. Opsi needed a website that would earn the trust of logistics directors, CIOs, and procurement teams in the first scroll — without a generic SaaS template, without startup energy, and without simplifying the technical depth of the product. The challenge wasn't just design. It was communication architecture: how do you present GPU-powered route optimization, ISO 27001 compliance, multi-fleet TMS, and 25 years of domain expertise to four different global buyer audiences in one coherent digital experience? ### Our Approach We built opsisystems.com on a dark, authoritative visual foundation — a deliberate departure from the startup aesthetic. Every design and content decision was made around one question: *what does an enterprise procurement team need to see to move forward?* The content architecture was structured around buyer questions, not product features: - Who is this company and how long have they been doing this? - What does the platform actually do at enterprise scale? - Can this handle our complexity — multi-fleet, multi-principal, global? - Are they compliant with ISO 27001, GDPR, and POPIA? - How do we start a conversation? We also implemented Answer Engine Optimization (AEO) — structuring every page with correct heading hierarchy, FAQ schema markup, and semantic content blocks so Opsi appears in AI-generated research answers, not just traditional search results. ### Lottie Animations To bring the Opsi Systems brand to life on the website, we generated a series of custom Lottie animations in line with the brand's dark, authoritative visual style. Rather than using generic stock animations, we took a different approach: the Lottie files were generated by feeding the site content into Claude Code and prompting it to build Lottie diagrams in line with the Opsi brand style. This AI-assisted animation workflow allowed us to produce bespoke, on-brand motion graphics that visualise complex technical concepts — GPU-powered route optimization, multi-fleet logistics flows, and enterprise platform architecture — without generic stock animation libraries. Each animation was: - Generated by Claude Code using the site's content as the brief - Styled to match the Opsi dark palette — #0A0A1A background, orange accent - Exported as lightweight Lottie JSON files for fast web rendering - Embedded inline in Webflow via the Lottie Player component The result is a set of animations that feel native to the brand — not borrowed from a generic library — and communicate technical complexity in a way that is immediately clear to an enterprise buyer. ### Results Here's what the project delivered — a complete enterprise digital presence built for the buyers Opsi needs to reach. | Metric | Value | |---|---| | Global Regions | 4 | | Years Expertise | 25+ | | Figma to Live | 4 weeks | | AEO | Optimised | **What was delivered:** - Full Webflow design and development — responsive across all devices - Corporate brand architecture — Opsi as parent, Tramm + Chora as products - Custom Lottie animations generated via Claude Code, styled to brand - AEO-optimised content with FAQ schema (JSON-LD) - Enterprise buyer-focused content hierarchy - Governance credibility signals — ISO 27001, GDPR, POPIA - Global audience-ready copy across 4 regions - CMS setup for ongoing content management without developer dependency ### Performance — First 90 Days Within the first 90 days of launch, opsisystems.com was already demonstrating the results of a well-structured, well-optimised Webflow build. | Metric | Value | |---|---| | Active Users | 406 | | Organic Search Users | 69 | | Contact Page Bounce | 12% | | Delivery Page Bounce | 0% | #### SEO & AEO Working From Day One Google and Bing delivered 69 organic search users within the first 90 days of a new domain — a direct result of the correct heading hierarchy, semantic HTML structure, and AEO content architecture built into every page of the Webflow site. Referral sessions from claude.ai and gemini.google.com confirmed that the FAQ schema markup and structured content blocks were surfacing Opsi Systems in AI-generated research answers — not just traditional search results. #### Enterprise Buyers Engaging Deeply The pages designed for serious enterprise evaluation — Contact (12% bounce), Industries (11.8% bounce), and Delivery & Implementation (0% bounce) — showed that the right audience was finding the right content and taking action. These are not casual visitors. These are buyers in an evaluation process. Referral traffic from Microsoft Teams, active Tramm client deployments, and an enterprise technology company evaluating Opsi from their internal test environment confirmed the site was reaching and engaging the correct audience. #### Global Reach — Built In The site reached buyers across Johannesburg, New York, Nairobi, Cape Town, Shanghai, Dubai, Vienna, Montreal, and 80+ cities worldwide — reflecting Opsi's actual global operational footprint and the content architecture designed to serve four distinct regional audiences from a single coherent digital presence. ### Client Feedback > "BrandingLab understood exactly what we needed — a website that communicates the weight and credibility of what we've built over 25 years. The result speaks for itself." > > — Opsi Systems Team, opsisystems.com ### Frequently Asked Questions #### Why was Webflow chosen for an enterprise build? Webflow gives Opsi Systems full CMS control with no ongoing developer dependency for content updates. It produces clean, semantic HTML that is both performant and structured correctly for SEO and AEO. For an enterprise company managing content across a global audience, that independence is critical. #### What is AEO and why does it matter for B2B companies? Answer Engine Optimization (AEO) structures your website content so it appears in AI-generated answers from tools like ChatGPT, Perplexity, and Google's AI Overview. Enterprise B2B buyers increasingly use AI to research platform decisions before visiting any vendor website. AEO ensures Opsi Systems is part of those answers. #### How did BrandingLab handle the technical complexity of the product? We built the content architecture around buyer questions rather than product features. Technical depth (GPU optimization, multi-principal fleet management) was framed in terms of what it means for the buyer's operation — not in engineering language. This makes the site accessible to procurement teams and technical evaluators simultaneously. #### How were the Lottie animations created? The Lottie files were generated using Claude Code — we fed the site content into the AI and prompted it to build Lottie animations in line with the Opsi brand style. This produced bespoke, on-brand motion graphics without generic stock animation libraries. Each file was exported as lightweight JSON and embedded via Webflow's Lottie Player component. #### How long did the project take? The full project — from Figma design to live published site — was completed in 4 weeks. This included Webflow design and development, AEO content architecture, custom Lottie animation generation, and CMS setup. #### Can BrandingLab build something similar for my business? Yes. If you're running a B2B company that needs a website built for enterprise buyers — with Webflow, AEO strategy, and content architecture that earns trust — get in touch at [brandinglab.io](/contact). ### Built by BrandingLab opsisystems.com was designed and developed by BrandingLab — full Webflow build, AEO content architecture, custom Lottie animations via Claude Code, four weeks from Figma to live. - See the case study: [brandinglab.io/work/opsi-systems](/work/opsi-systems) - Work with us: [brandinglab.io/contact](/contact) --- ### Article: JSON-LD for React SPAs: A Practical Schema Markup Guide **URL:** https://www.brandinglab.io/articles/jsonld-for-react-spas-schema-markup-guide **Published:** 2026-05-01 **Read time:** 9 min read **Author:** BrandingLab, Editorial **Category:** AEO **Key takeaways:** - React SPAs ship empty
HTML; without JSON-LD in the initial payload, AI crawlers see nothing semantic. - Put site-wide schema (Organization/ProfessionalService, WebSite) statically in index.html so it is present before React mounts. - Inject per-route schema (BlogPosting, Service, FAQPage, BreadcrumbList, CreativeWork) via react-helmet-async. - Prefer specific subtypes: BlogPosting over Article, ProfessionalService over generic Organization. - Validate every page type at Google Rich Results Test and validator.schema.org before shipping. ## JSON-LD for React SPAs: A Practical Schema Markup Guide ### TL;DR - React SPAs (Vite, CRA, Lovable, Bolt, v0) ship empty `
` HTML. Without JSON-LD in the initial payload, AI crawlers see nothing semantic. - **Site-wide schema** (`Organization`/`ProfessionalService`, `WebSite`) goes statically in `index.html` so it's present before React mounts. - **Per-route schema** (`BlogPosting`, `Service`, `FAQPage`, `BreadcrumbList`, `CreativeWork`) goes via `react-helmet-async` so each URL ships its own structured data. - Validate everything at https://search.google.com/test/rich-results before declaring victory. - The patterns below are what we ship on every B2B Vite + React SPA we touch. Copy them, change the values, deploy. This is the tactical companion to [our piece on why React SPAs are invisible to AI search](/articles/why-your-spa-is-invisible-to-ai-search). Read that for the *why*. Read this for the *what*. --- ### Why React SPAs need JSON-LD even more than server-rendered sites JSON-LD is structured data — a JSON block in your HTML that tells search engines and AI crawlers what your page is about in a machine-readable format. For server-rendered sites, JSON-LD is a bonus: crawlers can understand most of the page from the rendered HTML alone. For React SPAs, JSON-LD is not optional — it's often the only thing crawlers can read. When a crawler hits a Vite + React SPA without executing JavaScript, the body is `
`. Empty. The only signal-carrying content available is whatever's in the static ``. Title and meta description help. JSON-LD helps far more, because it gives crawlers structured, typed information they can map directly into knowledge graphs. Even crawlers that *do* execute JavaScript benefit. Schema present in the initial payload is treated as more authoritative than schema injected during hydration. ### Where JSON-LD goes in a React SPA Two locations. Use both. #### Static, in `index.html` For schema that's true site-wide and never changes per route. Goes in the `` of `index.html` (the Vite entry HTML). Present before React executes. Visible to every crawler. Use for: - `Organization` or `ProfessionalService` (the entity behind the site) - `WebSite` (with `SearchAction` for sitelinks search box) #### Dynamic, via `react-helmet-async` For schema that changes per route. Mounted in React; updated whenever the user navigates. Visible to JS-capable crawlers; falls back to the static schema for non-JS crawlers. Use for: - `BlogPosting` on each article - `Service` on each service page - `CreativeWork` on each case study - `FAQPage` on FAQ pages and case-study FAQ blocks - `BreadcrumbList` on every page ### The patterns we ship #### Pattern 1 — Static `Organization` (or `ProfessionalService`) in `index.html` `ProfessionalService` is a more specific subtype of `Organization` that extends `LocalBusiness`. If you're a B2B services firm with an address and a price range, prefer it. ```html ``` The `@id` matters — it's the canonical identifier other schema blocks reference (e.g., `"publisher": {"@id": "https://example.com#organization"}`). Use a fragment URL like `#organization`. #### Pattern 2 — Static `WebSite` in `index.html` ```html ``` The `SearchAction` enables Google's sitelinks search box for branded queries. Drop it if you don't have an internal search. #### Pattern 3 — A reusable schema generator module Don't paste JSON-LD inline on every page. Centralise it. A single `src/lib/schema.ts` exports functions for each page type: ```ts const SITE_URL = "https://example.com"; const LOGO_URL = `${SITE_URL}/logo.svg`; export function articleSchema(a: { slug: string; headline: string; description: string; image?: string; datePublished: string; dateModified?: string; authorName?: string; }) { return { "@context": "https://schema.org", "@type": "BlogPosting", headline: a.headline, description: a.description, image: a.image, datePublished: a.datePublished, dateModified: a.dateModified ?? a.datePublished, author: { "@type": "Person", name: a.authorName ?? "Editorial Team" }, publisher: { "@type": "Organization", name: "Your Company", logo: { "@type": "ImageObject", url: LOGO_URL } }, mainEntityOfPage: { "@type": "WebPage", "@id": `${SITE_URL}/articles/${a.slug}` } }; } export function serviceSchema(s: { name: string; description: string; slug: string; serviceType: string; }) { return { "@context": "https://schema.org", "@type": "Service", name: s.name, description: s.description, provider: { "@id": `${SITE_URL}#organization` }, serviceType: s.serviceType, areaServed: ["IL", "US", "GB", "EU", "Worldwide"], url: `${SITE_URL}/${s.slug}` }; } export function faqPageSchema(items: { question: string; answer: string }[]) { return { "@context": "https://schema.org", "@type": "FAQPage", mainEntity: items.map(i => ({ "@type": "Question", name: i.question, acceptedAnswer: { "@type": "Answer", text: i.answer } })) }; } export function breadcrumbSchema(crumbs: { name: string; url: string }[]) { return { "@context": "https://schema.org", "@type": "BreadcrumbList", itemListElement: crumbs.map((c, i) => ({ "@type": "ListItem", position: i + 1, name: c.name, item: c.url })) }; } ``` **Use `BlogPosting`, not `Article`, for blog posts.** `BlogPosting` is a more specific subtype and triggers richer SERP and AI treatment. #### Pattern 4 — Inject per-route schema with `react-helmet-async` ```tsx import { Helmet } from "react-helmet-async"; import { articleSchema, breadcrumbSchema } from "@/lib/schema"; export function ArticlePage({ article }) { const schemas = [ articleSchema({ slug: article.slug, headline: article.title, description: article.excerpt, image: article.ogImage, datePublished: article.publishedAt, dateModified: article.updatedAt, authorName: article.author }), breadcrumbSchema([ { name: "Home", url: "https://example.com" }, { name: "Articles", url: "https://example.com/articles" }, { name: article.title, url: `https://example.com/articles/${article.slug}` } ]) ]; return ( <> {article.title} · Your Company {schemas.map((s, i) => ( ))} {/* page body */} ); } ``` Wrap your app in `` once at the root (`src/main.tsx`): ```tsx import { HelmetProvider } from "react-helmet-async"; createRoot(document.getElementById("root")!).render( ); ``` ### Validate everything Two free tools, both worth running on every page type: - **Google Rich Results Test** — https://search.google.com/test/rich-results — confirms validity and shows which rich results your schema is eligible for. - **Schema.org Validator** — https://validator.schema.org/ — stricter; catches edge cases Google's tool ignores. Run both on: - Homepage (expect: `Organization` or `ProfessionalService` + `WebSite` + `BreadcrumbList`) - One article (expect: + `BlogPosting`) - One service page (expect: + `Service`) - The FAQ page (expect: + `FAQPage`) - One case study (expect: + `CreativeWork` or your domain-appropriate type) ### Common mistakes we see weekly 1. **Two `BreadcrumbList` blocks per page.** Happens when an auto-injector adds breadcrumbs *and* the page also passes `breadcrumbSchema(...)` manually. Pick one source of truth. 2. **`Article` instead of `BlogPosting`.** `BlogPosting` is more specific and triggers richer treatment. Use it for any blog content. 3. **Generic `Organization` instead of `ProfessionalService` (or `LocalBusiness`).** If you have an address and a price range, the more specific type accepts richer fields and signals more confidence. 4. **No `@id` references.** Without `@id`, schema blocks can't reference each other (e.g., `BlogPosting.publisher` referencing the site's `Organization`). Use fragment URLs. 5. **`og:image` URL that 404s.** We've seen this on dozens of sites — the OG image is referenced in `index.html` but the file doesn't exist. `curl -I` every URL in your schema before shipping. 6. **`datePublished` in the future or as a non-ISO string.** Both fail validation silently. Use ISO 8601: `2026-05-01`. 7. **Inline JSON in JSX without `JSON.stringify`.** React will escape quotes and break the JSON. Always serialize with `JSON.stringify(schema)`. ### What this gets you Schema markup is necessary but not sufficient for AEO. It establishes brand entity in AI knowledge graphs, makes your pages eligible for rich results in Google, and gives JS-capable AI crawlers structured signal to work with. It does *not*, by itself, fix the SPA invisibility problem — for that you also need either pre-rendering (build-time SSG via tools like `react-snap`), server-side rendering, or a markdown-based discovery file (`llms.txt` and `llms-full.txt`). For the full strategy — schema plus rendering plus discovery — see [why your SPA is invisible to AI search and how to fix it](/articles/why-your-spa-is-invisible-to-ai-search). ### Frequently asked questions #### Do I need both static and dynamic JSON-LD? Yes. Static schema in `index.html` (Organization/ProfessionalService, WebSite) gives crawlers identity and site context on every URL before React mounts. Dynamic per-route schema (BlogPosting, Service, FAQPage, BreadcrumbList) describes the specific page. Crawlers that don't execute JavaScript still get the site-wide entity; crawlers that do execute it get the per-page detail. #### Will react-helmet-async work for AI crawlers that don't run JavaScript? No — that's the catch. `react-helmet-async` injects schema after React mounts, so non-rendering crawlers (most AI bots, classic Googlebot fallback) won't see it. For those, you need prerendering, SSR, or a markdown discovery file (`llms.txt`/`llms-full.txt`). Use Helmet for the JS-capable crawlers; use one of the other three to cover the rest. #### Which schema type should I use for a blog post — Article or BlogPosting? `BlogPosting`. It's a subtype of `Article` and signals editorial blog content specifically. Google and most AI engines prefer the more specific subtype. Same logic for `ProfessionalService` over `Organization`, `LocalBusiness` over `Organization` for location-based businesses. #### Do I need to validate every page or just the templates? Validate every distinct page type — homepage, article template, service page, case study, FAQ — once. You don't need to revalidate every individual blog post unless you change the template. Run Google Rich Results Test and validator.schema.org on one example of each type before shipping, and after any template change. #### Will Google penalize me for having JSON-LD that doesn't match visible content? Yes. Schema must accurately describe what's on the page. Don't fabricate AggregateRating values, don't mark up FAQs that aren't visible, don't claim authorship that isn't real. Mismatched schema is treated as spam and can trigger manual actions. ### Get a free AEO audit of your B2B site We'll audit your site's schema, rendering, and AI-crawler accessibility — for free. Twenty-minute report, prioritized fix list, no commitment. [Request your free AEO Audit →](/audit) --- ### Article: Why Your SPA Is Invisible to AI Search (And How to Fix It) **URL:** https://www.brandinglab.io/articles/why-your-spa-is-invisible-to-ai-search **Published:** 2026-04-30 **Read time:** 14 min read **Author:** BrandingLab, Editorial **Category:** AEO **Key takeaways:** - AI crawlers like GPTBot and ClaudeBot do not reliably execute JavaScript, so SPAs return a blank shell - A single-page app served as a blank shell is invisible to most answer engines - Schema markup only helps if the surrounding HTML is server-rendered - Three fixes exist: SSR migration, edge prerendering, or build-time static generation - The right choice depends on publishing cadence, not site size ## Why Your SPA Is Invisible to AI Search (And How to Fix It) Open a terminal. Pick any URL on your marketing site. Run this: ```bash curl -A "GPTBot" https://yoursite.com/your-best-article ``` Read what comes back. If your site is built as a single-page application — React, Vue, Angular, Svelte without server rendering — there is a strong chance the response is a near-empty HTML shell. A `
`, a script tag, and almost nothing else. No headline. No body copy. No schema. No author. No publish date. Nothing for an answer engine to read, summarize, or cite. This is the AEO visibility problem in a single command. It is the most consequential SEO issue most marketing teams have never tested for, and it is silently excluding well-resourced brands from the conversations being had inside ChatGPT, Perplexity, Claude, and Google AI Overviews. The good news: it is solvable. The harder news: the solution is architectural, not editorial. No amount of better copy, more backlinks, or richer schema will fix a page that the crawler cannot read in the first place. This article explains exactly why this happens, how to diagnose it on your own site in five minutes, and the three viable paths to fix it — with the trade-offs each one carries. ### Why this matters now For two decades, search optimization meant ranking on a list of blue links. The unit of success was a click. The crawler that mattered was Googlebot. That world is fragmenting fast. A growing portion of high-intent research now happens inside conversational interfaces that synthesize an answer rather than return a list. ChatGPT processes hundreds of millions of queries a week. Perplexity is being adopted as a default research tool by analyst teams, consultants, and procurement leads. Google AI Overviews now sit above the traditional results for a substantial share of commercial queries. Claude is increasingly used inside enterprises for vendor research and technical evaluation. The unit of success in these interfaces is not a click. It is a citation. When a buyer asks an answer engine "who are the best AEO consultancies in Europe?" or "what is the difference between SEO and AEO?", the engine composes a response from sources it has indexed, and it names some of them. Being named is the new ranking. Not being named is the new page two. The crawlers behind these systems are not Googlebot. They are GPTBot (OpenAI), ClaudeBot and Claude-Web (Anthropic), PerplexityBot, Google-Extended, and a dozen smaller ones. They behave differently from the crawler your SEO tooling is designed around. Critically, most of them do not execute JavaScript reliably, do not wait for client-side hydration, and do not return for a second pass. If your site only renders its content after JavaScript runs, these crawlers see your blank shell — and they move on. Your authority, your insight, your case studies, your schema markup all exist only inside a black box they never opened. ### The technical root cause To understand the fix, you have to understand exactly what is happening on the wire. A traditional server-rendered website works like this: the browser asks for a URL, the server runs application logic, queries a database, composes the full HTML for that page, and sends it back. Everything visible to a human is also visible in the raw HTML response. The browser then enhances that HTML with CSS and JavaScript, but the content is already there. A single-page application works differently. The server returns the same minimal HTML file for nearly every URL — a shell containing a script tag and an empty `
`. The browser downloads a JavaScript bundle, executes it, fetches data from APIs, and constructs the page in memory. Content appears only after this process completes, sometimes seconds after the initial response. A human with a modern browser does not notice this. They see a brief loading state, then the finished page. A crawler is not a human. A crawler issues an HTTP request, receives the response, and parses what it gets. Whether it then executes the JavaScript bundle to discover what the page actually contains is a choice — one made by the crawler operator, weighed against compute cost, latency, and the number of pages they need to index. Here is how the major crawlers currently behave with respect to JavaScript execution. Treat this as a directional snapshot rather than a contract — these systems change quietly and frequently: | Crawler | Operator | JavaScript execution | Practical implication for SPAs | |---|---|---|---| | Googlebot | Google Search | Yes (deferred, second pass) | Eventually sees content, often with delay | | Bingbot | Microsoft / Bing | Yes (limited) | Mostly sees content | | GPTBot | OpenAI / ChatGPT | No reliable execution | Sees the blank shell | | ClaudeBot | Anthropic | No reliable execution | Sees the blank shell | | PerplexityBot | Perplexity | Limited | Often sees the blank shell | | Google-Extended | Google AI / Gemini training | Inherits Googlebot behavior, opt-in | Eventually sees content | | LinkedInBot | LinkedIn previews | No | Blank shell — broken social previews | | Slackbot, Twitterbot, FacebookExternalHit | Social previews | No | Blank shell — broken social previews | The pattern is clear. The traditional search crawlers have invested heavily in JavaScript execution because their commercial model demands it. The newer AI crawlers and the social preview bots have not. They prioritize breadth and freshness over completeness on individual pages, and they assume that any site that genuinely wants to be indexed will return meaningful HTML on the first request. This is not an oversight. It is a design choice. And it is unlikely to change soon, because executing JavaScript at the scale these crawlers operate at would multiply their infrastructure costs by an order of magnitude. The takeaway is uncomfortable but precise: if your content is not in the HTML that comes back from the first HTTP request, you should assume AI crawlers cannot see it. ### How to diagnose your own site Before deciding on a fix, confirm you actually have the problem. Three tests, five minutes total, no tools required beyond a browser and a terminal. #### Test 1: The curl test This is the definitive test. It shows you exactly what a crawler sees, with no JavaScript involved. ```bash curl -s -A "Mozilla/5.0 (compatible; GPTBot/1.0)" \ https://yoursite.com/your-most-important-page \ | head -100 ``` A healthy result contains your headline, body copy, structured data, and meta tags in readable HTML. A broken result contains a `` (often generic), a few meta tags, an empty `<div id="root">` or similar, and one or more `<script>` tags. If you see the latter on a content page, you have the problem. Repeat the test on three different page types: a marketing page, an article or blog post, and a product or case study page. Inconsistent results across page types are common and informative. #### Test 2: The view-source test In your browser, navigate to the same page. Right-click and select **View Page Source** — not "Inspect Element". The two are different in a way that matters here. "View Page Source" shows you the raw HTML the server sent. "Inspect Element" shows you the live DOM, which includes everything JavaScript has constructed. Crawlers without JavaScript execution see the former. Make sure that is what you are looking at. If View Page Source on your article page does not contain the article body in readable text, your site is failing the AEO basics. #### Test 3: The schema validator test Paste your URL into Google's Rich Results Test (`search.google.com/test/rich-results`). Choose the option to view the rendered HTML, then switch to the "Page resources" or "More info" tab and look at the raw response. If your JSON-LD schema appears only after rendering, it is invisible to crawlers that do not render. This is the most common false sense of security in AEO work — teams add comprehensive schema, see it appear in their browser, and assume the job is done. The validator will tell you the truth. ### The three viable fixes There are three architectural approaches that actually solve this problem. There are also several that look like solutions but are not — those are addressed at the end of this section. #### Path 1: Server-Side Rendering via framework migration The most thorough fix is to move the site onto a framework that renders HTML on the server by default. In the React ecosystem, this means Next.js. In Vue, Nuxt. In Svelte, SvelteKit. In a multi-framework setup, Astro. These frameworks invert the SPA model. Each request is handled by a server (or serverless function) that runs your components, fetches data, and returns fully populated HTML. The browser then hydrates that HTML into an interactive application. Crawlers receive the same HTML a human does on the first request. **When this is the right choice:** You publish content regularly — articles, case studies, product pages, documentation. You have an editorial workflow where new content needs to be discoverable within minutes, not days. You expect AI search to be a meaningful traffic and citation channel for years to come. **True cost:** A migration is real work. Plan four to six weeks for a content-heavy marketing site, longer if you have a custom admin or complex integrations. Existing components mostly port over, but routing, data fetching, metadata handling, and authentication all change shape. Hosting moves to a platform that supports the framework natively — Vercel for Next.js, Netlify for many others, or self-hosted Node infrastructure. **What you keep:** Your design system, your component library, your CMS or database, your business logic, your domain. The visible product changes very little. **What you gain beyond AEO:** Faster initial page loads, better Core Web Vitals, simpler social previews, working metadata for messaging app previews, and a foundation that scales as content needs grow. **What you lose:** The simplicity of static SPA hosting. You now have a server-side runtime to maintain, monitor, and pay for. #### Path 2: Edge prerendering proxy A second path keeps the existing SPA in place and adds a layer in front of it that detects crawlers and serves them a pre-rendered version of each page. The standard implementation uses a CDN edge worker (Cloudflare Workers, Fastly Compute, AWS Lambda@Edge) combined with a prerender service (Prerender.io, Rendertron, or self-hosted Puppeteer infrastructure). The edge worker inspects the user agent of each incoming request. Human browsers pass through to the SPA unchanged. Recognized crawlers are routed to the prerender service, which fetches the page in a real headless browser, waits for JavaScript to finish, and returns the fully rendered HTML. **When this is the right choice:** You have an existing SPA you cannot or will not [rebuild](/articles/b2b-website-rebuild-process/) in the near term. You have budget for ongoing infrastructure. You need a fix in weeks, not months. **Operational reality nobody warns you about:** This setup has more moving parts than it looks. You are now responsible for a CDN configuration, an edge worker, a prerender service contract, a cache invalidation strategy, and a list of crawler user agents to keep current. When prerendered HTML goes stale, you have to invalidate it. When you publish new content, the prerender cache needs to know. When a crawler arrives with an unfamiliar user agent, your worker needs a sensible fallback. None of this is hard, but all of it is permanent overhead. **Cost reality:** Prerender.io plans start around $90/month and scale with traffic and page count. Self-hosting a Puppeteer-based prerender service is technically free but operationally expensive — you are running and maintaining headless Chrome at scale. CDN edge worker costs are usually negligible. Budget realistically: $100 to $500 per month for a mid-size content site. **What you gain:** Crawlers see fully rendered HTML without changing your application code. Implementation is two to three weeks for a competent infrastructure engineer. **What you should be honest with yourself about:** This is a workaround. It is a perfectly defensible workaround, but it adds permanent complexity to your stack to compensate for an architectural mismatch. Sophisticated technical buyers who inspect your setup will recognize it as such. #### Path 3: Build-time static generation The third path generates static HTML files for every route at build time, then serves those files directly. Tools include `vite-plugin-ssg`, `react-snap`, and the static export modes of frameworks like Astro. The build process renders each route in a headless browser, captures the resulting HTML, and writes it to disk. The output is a folder of fully rendered HTML files that any static host can serve. Crawlers receive complete HTML on the first request. **When this is the right choice:** Your site is genuinely mostly static — a marketing site for a product company, a documentation site, a portfolio. Content changes are infrequent and intentional. You want zero ongoing infrastructure cost beyond static hosting. **The trap that disqualifies this for content publishers:** Build-time static generation means every published page is a snapshot taken at build time. When you publish a new article in your CMS, that article does not exist on the public site until you trigger a new build and deploy. For a static marketing site updated quarterly, this is fine. For a publication that ships content weekly, daily, or in response to news cycles, it is unacceptable. You either spend constant engineering effort wiring up build webhooks that frequently fail, or you accept that new content takes hours or days to appear. **Hidden complexity for dynamic routes:** Routes that depend on parameters — `/articles/[slug]`, `/work/[case-study]` — require enumerating every possible value at build time. This means querying your database during the build, which means your build process needs database credentials, which means your CI environment needs to be configured for it. None of this is impossible, but it is more work than the "just generate static files" pitch suggests. **What you gain:** Best-in-class performance, lowest possible hosting cost, no runtime infrastructure to manage, full crawler visibility. **What you lose:** Real-time content publishing without an engineering loop in the middle. #### What not to do Three approaches surface frequently in conversations about this problem and are worth flagging as dead ends. **A homemade prerender script that runs in CI.** Teams sometimes propose writing their own headless Chrome script that captures every route, commits the HTML to the repo, and serves those files. This works for a week, breaks the first time the script encounters an authentication redirect, a slow API response, or a hydration error, and then sits broken because nobody owns it. **"We will fix it later when AEO matters more."** AEO already matters. The teams winning citations in AI answer engines today made these architectural decisions twelve to eighteen months ago. The compounding nature of crawler trust and content indexing means that catching up requires more effort, not less, the longer you wait. **Adding more schema markup to a blank shell.** This is addressed in detail below, but the short version: if the surrounding HTML is invisible to the crawler, the schema inside it is also invisible. ### A decision framework The right path depends on a single question: how often does your content change? ``` Are you publishing new content weekly or more often? ├── Yes → Path 1: SSR migration (Next.js, Nuxt, etc.) │ Reason: only SSR keeps new content crawlable in real time. │ └── No → Are you actively planning to publish more in the next 12 months? ├── Yes → Path 1: SSR migration │ Reason: invest now, not after the content team is blocked. │ └── No → Do you have engineering capacity for a rebuild? ├── No, but have budget → Path 2: Edge prerendering proxy │ Reason: fastest path to crawlable HTML. │ └── No to both → Path 3: Build-time static generation Reason: cheap, simple, suitable for static sites. ``` Two more honest checks worth running: - **If the AEO channel is strategic to your business, default to Path 1.** SSR is the only path that does not impose ongoing operational cost or content-velocity penalties. Every other path is a workaround. Workarounds are appropriate when they buy time for a real solution, not as the destination. - **If you sell AEO services to clients, your own site cannot be on Path 2 or 3.** Your prospects will run the curl test. They are running it on every vendor they evaluate. The credibility cost of being caught with an invisible site is higher than the cost of any migration. ### What schema markup cannot save you from A common reaction to AEO concerns is to add structured data — JSON-LD schemas for `Article`, `FAQPage`, `BreadcrumbList`, `Organization`, `Product`. This is good practice. It is also insufficient on its own. Schema is metadata. It tells a crawler what the surrounding content means. It does not replace the surrounding content. If your `BreadcrumbList` schema is injected into the page by JavaScript after hydration, a crawler that does not execute JavaScript never sees it. The same applies to `Article` schema, `Person` schema, `FAQPage` schema, and every other type. Schema in a blank shell is invisible. Schema in a server-rendered page is amplified. The order of operations matters. Get the HTML right first. Then layer schema on top to make that HTML easier for machines to interpret. Doing schema first is like putting captions on a film nobody can see. This is also why client-side metadata libraries like React Helmet — useful as they are for managing the document head in an SPA — do not solve the AEO problem on their own. They modify the head of the live DOM after JavaScript runs. Crawlers without JavaScript see the original `<head>` from the HTML shell, with whatever defaults were baked in at build time. If you want the test: open View Page Source on a page where you added schema. Search the raw HTML for the schema string. If it is there, crawlers can see it. If you have to use the browser's Inspect tool to find it in the live DOM, only crawlers that execute JavaScript will ever read it. **Next: the tactical companion.** For the exact JSON-LD patterns we ship on every Vite + React SPA — static site-wide schema in `index.html`, per-route schema via `react-helmet-async`, and the validator workflow — see [JSON-LD for React SPAs: A Practical Schema Markup Guide](/articles/jsonld-for-react-spas-schema-markup-guide). ### Closing AEO is being sold to marketing teams as a content discipline. It is partly that. It is also, more fundamentally, an architectural discipline. The teams winning citations in AI answer engines are not winning because they wrote better articles or added more schema. They are winning because their content is in the HTML that comes back on the first HTTP request, on every page, every time, with no JavaScript required. That single property makes them crawlable, indexable, and citable by every system that has emerged in the last two years and every system that will emerge in the next five. The teams losing visibility are mostly not aware they are losing. Their analytics show traffic, their browsers show beautiful pages, their schema validators show green check marks. The thing they are not measuring is what happens when an AI crawler asks for the page. That is the test that decides whether [their brand appears in the answers their buyers are reading](/articles/b2b-ai-search-visibility/). Five minutes with `curl` will tell you which side of that line your site sits on. Where you go from there is a decision worth making with eyes open — about content velocity, engineering capacity, and how seriously you take AEO as a channel. If you want help running that diagnostic across your most important pages, choosing between the three paths, or executing the migration, that is the work BrandingLab does. Start with the curl test. The rest follows from what you find. Want the SSR fix and the AEO programme run together? That's the standard shape of [BrandingLab's AEO programme](/aeo-services) — rebuild the foundations for teams that have [outgrown their current website](/articles/six-signs-youve-outgrown-your-current-website/), then compound citations on top. ### Frequently asked questions #### Why can't AI crawlers read a single-page application? A single-page application built in React, Vue, Angular, or Svelte without server rendering returns a near-empty HTML shell — a root div, a script tag, and little else. AI crawlers read that raw response and do not wait for JavaScript to build the page. There is no headline, body copy, schema, or author for an answer engine to summarise or cite. #### How do I test whether my site is invisible to AI search? Open a terminal and run `curl -A "GPTBot" https://yoursite.com/your-best-article`, then read what comes back. If you see your headline and body copy, crawlers can read the page. If you see an empty shell, they cannot — and no amount of better copy or more backlinks will change that. #### Will adding schema markup fix an invisible SPA? No. Schema markup describes content that a crawler can already read; it cannot supply content the crawler never received. If your page renders client-side, the schema is injected by the same JavaScript the crawler skipped, so it is absent from the raw response too. The fix is architectural, not editorial. #### What are the options for fixing a client-rendered site? There are three viable paths: migrate to server-side rendering, put an edge prerendering proxy in front of the existing app, or generate static HTML at build time using tooling such as `vite-plugin-ssg` or `react-snap`. Each carries different cost, timeline, and maintenance trade-offs, and the right choice depends on how much of your stack you are willing to move. #### Does this affect Google rankings as well as AI citations? It can, but the AI impact is more immediate and more severe. Googlebot has rendered JavaScript for years, so traditional rankings often survive; the newer answer-engine crawlers are far less forgiving and frequently take the raw response as-is. That is why a site can rank acceptably in Google and still be entirely absent from ChatGPT, Perplexity, and Claude answers. --- ### Article: Google Isn't Cannibalizing Itself. It's Cannibalizing You. **URL:** https://www.brandinglab.io/articles/google-ai-search-cannibalization **Published:** 2026-04-26 **Read time:** 9 min read **Author:** BrandingLab Editorial, AI Search & Strategy **Category:** AI Search **Key takeaways:** - Google is not cannibalizing its ad business — Search ad revenue hit $63B in Q4 2025, up 17% year over year, with total Google ad revenue approaching $80B per quarter. - The "90% of Alphabet revenue from ads" stat is outdated — by 2023 it was roughly 77%, and Google has diversified further since. - The real cannibalization is downstream: publisher referral traffic is down ~10% median (up to 25% on AI Overview keywords), with CTRs collapsing 61% organic / 68% paid on informational queries. - The monetization shift is permanent, not cyclical — Google is successfully moving ad revenue from blue links to AI-generated answers, with Gemini ads rolling out in 2026. - The new rules of organic discovery: the game is no longer ranking, it's being the brand AI systems cite by name in direct answers. If you've been reading marketing Twitter or LinkedIn in 2026, you've probably heard some version of this take: *Google is committing suicide. They're blowing up a $300 billion advertising business to chase AI, and Gemini is eating the golden goose alive.* It's a great story. It's also wrong. Google's ad revenue isn't shrinking. It's accelerating. In Q4 2025, Google Search advertising hit $63 billion — up 17% year over year, the strongest quarterly performance in years. Growth actually sped up through 2025: 10%, then 12%, then 15%, then 17%. On the Q4 earnings call, Sundar Pichai addressed the cannibalization thesis directly and said Google hadn't seen evidence of it. So if Google isn't eating itself, what exactly *is* getting eaten? You are. --- ### The narrative everyone is repeating The story goes something like this: Alphabet generates the overwhelming majority of its revenue from advertising. AI Overviews answer users' questions directly on the search page, which means users stop clicking. Fewer clicks means fewer ad impressions. Fewer ad impressions means less revenue. Therefore, Google is systematically destroying its own business to compete with ChatGPT. The numbers cited in support of this usually include some version of: *90% of Alphabet revenue is from ads*, *$237 billion in ad revenue in 2023*, and projections showing $318 billion by 2026. The implication is that AI is a suicide mission — that Google has to choose between relevance and revenue. This story makes intuitive sense. It's also fundamentally wrong about what is happening, who is benefiting, and who is actually losing money. Start with the 90% figure. That was true in 2017. By 2023, advertising was around 77% of Alphabet's total revenue — still dominant, but Cloud, YouTube subscriptions, and hardware have meaningfully diversified the business. The narrative uses outdated math to set up a scale of risk that doesn't exist anymore. Then look at what's actually happening to the ad business itself. ### Google is winning, not cannibalizing Here is what the last several earnings cycles actually show. Google's ad revenue climbed from roughly $52 billion per quarter in early 2023 to approximately $72 billion in Q3 2025, and Q4 2025 pushed toward $80 billion. Search alone — the piece everyone assumed AI would cannibalize — grew 17% year over year. Gemini reached 750 million monthly active users. AI Overviews are served to roughly 2 billion monthly users. And revenue per query is trending *up*, not down, as Google experiments with new ad formats inside AI-generated answers. Ads inside the Gemini app itself are targeted for rollout in 2026. None of this looks like a company destroying its business model. It looks like a company successfully migrating one. What Google figured out — and what the cannibalization narrative missed — is that the ad business never depended on blue links. It depended on intent. When a user types "best CRM for small businesses," they are expressing commercial intent. Google's job has always been to monetize that moment. Whether the output is ten blue links, a featured snippet, a local pack, an AI Overview, or a Gemini response, the intent capture happens the same way. The interface changes. The monetization does not. In fact, the AI interface *improves* monetization in some ways. It keeps the user on Google's surface longer. It creates new ad placements that are more contextually integrated into the answer. And it removes a leak point — the moment a user clicks through to an external site and Google loses attribution on what happens next. So Google is fine. Better than fine. The cannibalization thesis is dead. The actual cannibalization is happening one layer down. ### The real cannibalization: you If Google is capturing the same advertising dollars — more, actually — and users are getting their answers without clicking through to external sites, then someone is absorbing the loss. Not Google. Everyone else. The data on this is brutal. Premium publishers have seen median referral traffic from Google drop about 10% year over year, with individual sites losing up to 25% when AI Overviews start appearing for their top keywords. Click-through rates on informational queries have collapsed by 61% for organic results and 68% for paid results when an AI Overview is present. Gartner has projected a 25% drop in overall organic search traffic by 2026, with some verticals facing 30-50% declines by 2028. Translation: if your business depends on earned search traffic, a quarter of it is going to disappear over the next few years. Possibly half, depending on what you sell. This is the real story. The value that used to flow from Google to your website — the click, the pageview, the chance to convert a visitor into a lead — is being intercepted. Google is still selling the ad. Google is still capturing the intent. But the reader now gets their answer on the Google surface and never arrives at your site. You keep the cost of creating the content. Google keeps the revenue it generates. For brands whose growth model assumed a steady flow of organic and paid search traffic, this is a structural change, not a cycle. You will not wake up in 18 months and find your traffic has bounced back. The interception is permanent. The buyer journey has moved. The question is not whether this is happening. It's what you're going to do about it. ### The rules have changed. SEO alone isn't the game anymore. For twenty years, the winning move online was to rank. You wrote content, you built backlinks, you earned page one, and traffic arrived. That era is ending. Not because SEO is dead — it isn't, and ranking still matters for some queries — but because "ranking" no longer describes how most discovery happens. The new game is **being the brand the AI cites.** When someone asks ChatGPT, Perplexity, or Google's AI for the best vendor in your category, three to five names appear in the answer. You are either one of them or you aren't. There is no "page two" to grind toward. There is no reranking strategy. You are either the brand the model has learned to recommend, or you're invisible. This is what [Answer Engine Optimization actually is](/articles/what-is-aeo) — not a new acronym for SEO, but a different discipline. The old work was about keywords and rankings. The new work is about entity clarity, structured data, topical authority, and whether your content is *citable* — whether a model can extract a specific, factual statement from your site and attribute it to you by name. If you're weighing how it relates to traditional optimisation, our [AEO vs SEO breakdown](/articles/aeo-vs-seo) goes deeper. The companies that will win the next five years are not the ones with the best keyword coverage. They are the ones AI systems have learned to name — because their brand is clearly defined, their content is structurally extractable, and their authority on specific topics is unambiguous. If that sounds abstract, here's the concrete version: [your website has to be built for this](/articles/b2b-ai-search-visibility). Most legacy sites aren't. The schema markup, the entity architecture, the semantic HTML, the content design that makes extraction possible — none of it is something you can bolt on after the fact. It's foundational. ### What to do next The narrative that "Google is cannibalizing itself" is a comforting story for business owners who don't want to change. It implies the problem will sort itself out — that Google will come to its senses, reverse course, and the old playbook will keep working. The data says otherwise. Google has made its choice. The migration is already happening. The only open question is whether your business finishes the next two years on the winning side of it or the losing one. Here is what we'd recommend, depending on where you are: **If you've [noticed your traffic dropping](/articles/six-signs-youve-outgrown-your-current-website/) and don't know why** — start with a [free AEO audit](/audit). We'll run your target queries through ChatGPT, Perplexity, and Google AI Overviews, show you exactly where you're absent and where your competitors are winning, and map the structural gaps between your site and the brands getting cited. It's free, it takes about a week, and it gives you a concrete starting point. **If you already know your site needs to be rebuilt for the AI era** — that is what we do. BrandingLab builds [Webflow sites engineered for AEO](/webflow-agency) from the foundation: schema markup at the component level, entity-clear content architecture, a CMS that enforces structure, and content designed so AI models can extract and attribute it by name. [See what a rebuild actually looks like](/articles/b2b-website-rebuild-process). **If you're still getting your head around the shift** — explore our [AEO services](/aeo-services) or [start a conversation](/contact). We send one piece a week on what's changing in AI search, how brands are adapting, and the practical moves that are working right now. --- *The companies getting cited in AI answers aren't smarter. They're earlier. The window for cheap, compounding AEO gains is still open — but it narrows every month.* --- ### Frequently asked questions #### Is Google's ad revenue actually growing in 2026? Yes. Google Search advertising reached $63 billion in Q4 2025, up 17% year over year, and total Google ad revenue is approaching $80 billion per quarter. Growth accelerated through 2025 rather than slowing. The popular narrative that AI is cannibalizing Google's ad business is not supported by the current financials — Sundar Pichai addressed the cannibalization thesis directly on the Q4 2025 earnings call and said no evidence of it has materialized. #### If Google isn't losing money to AI, who is? Publishers, websites, and brands that depend on earned search traffic. Premium publishers have seen median referral traffic from Google drop about 10% year over year, with individual sites losing up to 25% on keywords where AI Overviews appear. Click-through rates on informational queries have collapsed 61% for organic results and 68% for paid results when an AI Overview is present. The value that used to flow from Google to external websites is being captured on the Google surface instead. #### What is Answer Engine Optimization (AEO)? Answer Engine Optimization is the practice of structuring a website and its content so that AI systems — including ChatGPT, Perplexity, Google AI Overviews, and Gemini — can find, understand, and cite it in direct answers. Unlike traditional SEO, which targets page rankings on a results list, AEO targets citation in synthesized answers. The work involves entity clarity, structured data markup (schema), topical content depth, and formatting content so individual statements are extractable and attributable. #### Is SEO dead? No, but its role has narrowed. Ranking on Google's traditional search results still matters — especially for commercial queries where users comparison shop. But a growing share of discovery now happens inside AI-generated answers where there are no rankings, only citations. The practical implication is that SEO alone is no longer sufficient as a growth strategy. AEO has become a required complement. #### How soon does this matter for my business? It already matters. Gartner projects a 25% drop in organic search traffic by 2026, with some verticals facing 30-50% declines by 2028. Brands that start building AEO capability now will compound their advantage over the next 18 months; brands that wait will find the gap harder to close. The cost of starting is relatively low. The cost of waiting is losing a significant share of your organic traffic with no replacement channel. --- *BrandingLab helps mid-market B2B teams design and build websites that match the pace of their business — and the mechanics of how buyers now find vendors. We specialize in Webflow builds, brand-driven redesigns, and sites engineered for AI-era discoverability.* --- ### Article: Six Signs You've Outgrown Your Current Website **URL:** https://www.brandinglab.io/articles/six-signs-youve-outgrown-your-current-website **Published:** 2026-04-26 **Read time:** 12 min read **Author:** BrandingLab, Editorial **Category:** Strategy **Key takeaways:** - Post-funding, your site has to match the new valuation — and be discoverable by the AI-powered search tools investors, hires, and enterprise buyers are using to evaluate you. - A repositioning that doesn't reach the website is just an internal memo. If the site still describes last year's positioning, that's what AI search engines will tell buyers you do. - Flat pipeline often points to a structural problem, not a CRO problem. Poor information architecture doesn't just lose human visitors — it also prevents AI models from understanding and recommending you. - AI search visibility compounds — and so does invisibility. Every week your competitors get cited in ChatGPT, Perplexity, and AI Overviews and you don't, the gap widens. - Dev-dependent websites kill marketing velocity — and make it impossible to build the content depth and structured data that AEO requires. - M&A and rebrands reset how AI search engines understand your company. Without AEO built into the new site from day one, you'll be invisible in AI results for months. - A rebuild is the right time to implement AEO strategy. Answer Engine Optimization isn't a bolt-on — it's an architectural decision that shapes structured data, content models, and site architecture from the ground up. ## Six Signs You've Outgrown Your Current Website Mid-market B2B teams rarely rebuild a website for fun. Nobody wakes up on a Tuesday and decides to spend six figures replacing something that technically still loads. They rebuild because something underneath the business changed — and the site is now in the way. Maybe it's a funding round that reset expectations overnight. Maybe it's a repositioning that sales already adopted but the homepage still hasn't. Maybe the pipeline chart is flat and nobody can explain why. The triggers are different. The pattern is the same: the company moved, the website didn't, and now there's a gap between how the business operates and how it presents itself online. Here are six signs that gap has opened up — and why each one costs more the longer you ignore it. ### 1. You just raised — or you're about to New funding changes the rules fast. The pitch that closed a seed round doesn't hold up when enterprise buyers start Googling you after a Series B announcement. Investors want to see a company that looks like the valuation they just wrote a check for. New hires are evaluating your site before they accept the offer letter. Strategic partners are deciding whether you're credible enough to co-sell with. If your site still reflects the scrappy startup you were eighteen months ago, you're creating friction at every one of those moments. Not "brand risk" in the abstract — the kind of friction where a Series B hire pulls up your homepage on their phone, scrolls for four seconds, and quietly recalibrates their counter-offer. The window to fix this is shorter than you think. Post-funding, the clock starts on hiring, on pipeline targets, on board expectations. A site that undersells you makes all three harder. There's also a less obvious dimension here: post-funding is when your category visibility matters most. Investors, analysts, and potential customers are searching for you — increasingly through AI-powered tools like ChatGPT and Perplexity. If your site hasn't been built with Answer Engine Optimization (AEO) in mind, those tools have nothing substantive to cite. You've raised the capital, but the market's discovery layer doesn't know it yet. ### 2. You've repositioned, but the site hasn't caught up This one is sneaky because it happens gradually. Pricing changes. Your ICP shifts up-market. A new product line launches. You stop competing in one category and start owning another. Meanwhile, the website is still running last year's pitch. The hero copy talks to the wrong buyer. The case studies feature logos that no longer represent your target customer. The messaging framework that informed every page is two strategies old. You'll know it's happening when sales starts editing decks and one-pagers because "the website doesn't really say what we do anymore." When the SDR team writes their own cold email copy because the site's value props don't land. When your best closer avoids sending prospects to the homepage. A repositioning that lives in Notion docs and slide decks but not on your website isn't a repositioning. It's an internal memo. Bonus tell: when your CEO opens every prospect meeting by apologizing for the homepage. And it's not just human buyers who are reading the old pitch. AI search engines are too. When a prospect asks ChatGPT or Perplexity what your company does, the model pulls from your site — and if the site still describes last year's positioning, that's the answer it gives. Your repositioning hasn't just failed to reach sales. It's failed to reach the algorithms that are increasingly deciding whether you make the shortlist. ### 3. Pipeline has plateaued — and you can't A/B test your way out of it Traffic looks fine. Maybe it's even growing. But demo requests are flat. The conversion rate from visitor to booked call has been declining for two quarters and no one has a clean answer for why. You've tried the obvious stuff: new hero copy, different CTAs, a chatbot, gated content. Some of it moved the needle for a week. None of it stuck. Here's the part most teams don't want to hear, because we've all paid an agency to tell us the opposite: when the funnel is leaking everywhere, the problem is not the button color. It is not the headline. It is the site. The information architecture, the narrative flow, the way pages connect — or don't. You're A/B testing inside a structure that no longer matches how buyers actually evaluate you. A/B testing assumes the foundation is sound and you're tuning the details. When the foundation has shifted, testing is just rearranging the furniture in a building that needs new load-bearing walls. There's a compounding factor here that most teams miss: a site with poor information architecture doesn't just lose human visitors at the wrong moment — it also fails to surface in AI-powered search. Answer engines need structured, clear content paths to understand what you do and recommend you. If the narrative flow is broken for humans, it's broken for the models too. Rebuilding the site's architecture with AEO strategy baked in doesn't just fix the conversion leak — it opens an entirely new discovery channel. ### 4. You're invisible to AI search This is the one that's moving fastest in 2026. Buyers are asking ChatGPT, Perplexity, and Google AI Overviews for shortlists in your category. They're typing queries like "best data integration platforms for mid-market fintech" and getting direct answers — not ten blue links to click through. Your competitors show up in those answers. You don't. And unlike traditional SEO, where you could grind your way up over months, AI search visibility compounds. The platforms that get cited early get cited more, which trains the models to cite them again. I learned this one the hard way on my own site. A while back I rebuilt brandinglab.io on a modern [SPA](/articles/why-your-spa-is-invisible-to-ai-search/) stack — the kind of stack that makes the browsing experience feel great and the AI crawler experience feel like nothing. Within a few weeks, my AI search traffic flatlined. Not declined. Vanished. ChatGPT and Perplexity were pulling up a hydration shell with no content in it, deciding there was nothing here, and moving on. I had spent months writing for AI discovery and accidentally built a site that AI couldn't read. The fix took an afternoon with an AI assistant: route the URL through a Cloudflare Worker that serves a fully rendered version of the page to bots and the SPA to humans. Traffic came back. The lesson didn't. The lesson is that most B2B sites are doing some version of this without realizing it. The CMS your agency picked in 2022 was optimized for a search engine that ranked pages. The new search engine summarizes, synthesizes, and recommends. That requires a fundamentally different content architecture — structured data, clear entity definitions, topical authority built through depth — and a rendering layer that doesn't hide your content behind JavaScript that bots won't execute. If your site wasn't built with AI discoverability in mind, every week you wait is a week your competitors are training the models to prefer them over you. Worse, the value that used to flow from search to your website is now [being intercepted on the Google surface itself](/articles/google-ai-search-cannibalization/) — the click never happens, and you keep paying to produce content that nobody outside the answer engine ever sees. We break down exactly how AI search visibility works — and what to do about it — in [Why Your B2B Website Isn't Showing Up in AI Search](/articles/b2b-ai-search-visibility/). ### 5. Every change needs a developer Marketing wants to ship a campaign landing page on Tuesday. Engineering says it's in the backlog for next sprint. Someone needs to update a testimonial quote and it turns into a Jira ticket. A typo on the pricing page sits there for eleven days because the person who can edit it is in a feature freeze. This isn't a people problem. It's an infrastructure problem. The CMS was set up years ago by someone who's no longer at the company. The design system — if there was one — is a loose collection of components that only work if you know which ones not to touch. The staging environment is broken and nobody's prioritized fixing it. The cost here isn't speed. The cost is the experiments that quietly stop happening. When marketing can't move independently, they stop testing new messaging. They stop building campaign pages. They stop launching the small bets that would have told them what's working. After a year of this, the marketing team has built impressive muscle memory around working around the website — and somewhere in there, they stopped asking. That's when the website became a static artifact and nobody filed a ticket about it, because there's no ticket to file. We dig into the full cost of this dynamic — and what marketing-led looks like — in [The Real Cost of a Dev-Dependent Website](/articles/dev-dependent-website/). ### 6. M&A or a rebrand is on the table Acquisition, merger, parent-brand consolidation, full rebrand — any of these means the site has to carry a new identity, integrate new products, and often migrate to new domains. The stakes are high and the timeline is always tighter than anyone planned for. The question isn't whether the site needs to change. It's whether your current platform can absorb that change without losing what you've already built. Organic rankings. Backlink equity. Indexed pages that drive pipeline. URL structures that other sites link to. Most legacy B2B sites aren't built for this kind of transition. They're rigid. The six-week migration the agency promised becomes a six-month migration because the technical debt accumulated quietly while everyone was focused on the brand reveal video. If M&A or a rebrand is even in the conversation, the time to assess your site's readiness is now — not after the deal closes and the board wants the new brand live in ninety days. A rebrand also resets how AI search engines understand your company. New entity definitions, new product descriptions, new category associations — all of it has to be communicated to the models through structured data, clear content, and an AEO strategy built into the site from day one. The rebrands that go badly are the ones treated as a visual exercise. New logo, new color system, new typography, a launch post on LinkedIn — and then a 90-day window of total invisibility in AI search while the models slowly catch up to the change. The brand looks new. The pipeline behaves like the new brand doesn't exist. ### The cost of waiting — and why AEO makes it urgent Every one of these signs has one thing in common: the cost compounds. A site that undersells your positioning today doesn't just cost you this quarter's pipeline — it shapes how the market categorizes you for the next twelve months. A site that's invisible to AI search doesn't just miss today's queries — it trains the models to look elsewhere. What's changed in 2026 is that a website rebuild is no longer just about fixing what's broken — it's about building for a discovery layer that didn't exist three years ago. Answer Engine Optimization isn't something you bolt on after the site launches. It's an architectural decision: structured data, entity-clear content, topical depth, and a content model designed for extraction. Every sign on this list — funding, repositioning, flat pipeline, dev-dependency, M&A — has an AEO dimension that makes the rebuild more urgent and the payoff larger. The companies that move on these signals early aren't getting a nicer website. They're getting infrastructure that matches the speed of their business — one that marketing can operate independently, that sales trusts enough to send prospects to, and that shows up where buyers actually look. If two or more of these signs sound familiar, the site isn't outdated. It's actively in the way. If you've already decided you need to act, here's [what a B2B website rebuild actually looks like](/articles/b2b-website-rebuild-process/) — timeline, process, what to expect, and where most teams get it wrong. Want to know where your site actually stands? Book a free audit with BrandingLab. We'll show you what's costing you pipeline, what's costing you AI visibility, and — honestly — whether you need a rebuild or a sharper version of what you've got. ### Frequently asked questions #### How do I know if my B2B website needs a redesign or a full rebuild? A redesign updates the visual layer — colors, layout, imagery — while keeping the underlying structure and platform. A full rebuild replaces the platform, information architecture, content model, and design system. If your problems are cosmetic, a redesign may suffice. If marketing can't publish without developers, your CMS is inflexible, your site doesn't appear in AI search results, or you're going through a repositioning, you likely need a rebuild. The distinction matters because a redesign on a broken foundation will reproduce the same problems with a fresher look. #### How often should a B2B company redesign its website? There is no fixed schedule. The right time to rebuild is when the business has changed in ways the site no longer reflects — after a funding round, a repositioning, a shift in ICP, or when pipeline conversion has plateaued despite optimization efforts. For most mid-market B2B companies, this happens every two to four years, though fast-growing companies may need to rebuild sooner. #### What is the biggest risk of keeping an outdated B2B website? The biggest risk is compounding invisibility. An outdated site doesn't just underperform today — it shapes how the market categorizes you, how AI search models learn to describe (or ignore) you, and how buyers perceive your credibility relative to competitors. Each quarter the gap between your business and your website widens, the cost of closing it increases. #### How long does a B2B website rebuild typically take? Most mid-market B2B website rebuilds take eight to twelve weeks from kickoff to launch. The biggest variable is content readiness — teams that have their positioning and messaging defined before the project starts move faster. Teams that need to develop strategy from scratch should expect the process to lean closer to twelve weeks. Read our full breakdown in What a B2B Website Rebuild Actually Looks Like. #### What does AEO (Answer Engine Optimization) mean for B2B websites? Answer Engine Optimization is the practice of structuring your website so that AI-powered search engines — ChatGPT, Perplexity, Google AI Overviews — can find, understand, and cite your content. Unlike traditional SEO, which optimizes for page rankings, AEO optimizes for direct answers. This requires clear entity definitions, structured data markup, topical depth, and content organized for extraction rather than skimming. Learn more in Why Your B2B Website Isn't Showing Up in AI Search. --- ### Article: Why Your B2B Website Isn't Showing Up in AI Search (And How to Fix It) **URL:** https://www.brandinglab.io/articles/b2b-ai-search-visibility **Published:** 2026-04-21 **Read time:** 9 min read **Author:** BrandingLab, AEO & Digital Strategy **Category:** AEO **Key takeaways:** - AI search engines don't rank pages — they decide whether to cite you. Strong domain authority and page-one rankings don't guarantee visibility in ChatGPT, Perplexity, or Google AI Overviews. - The four structural gaps that keep B2B sites out of AI answers are unclear entity definitions, missing structured data (schema markup), shallow topical coverage, and content formatted for skimming instead of extraction. - AI search visibility compounds. Sites that get cited early get cited more — and absence compounds just as fast, widening the gap every week. - The fix is structural, not tactical. Audit entity clarity, implement schema markup site-wide, build content depth around core buyer queries, and structure every page so the first sentence under each heading is citable on its own. - You can monitor this now. Search your target queries in ChatGPT, Perplexity, and AI Overviews regularly. Track presence or absence — there's no ranking to chase, just whether you're in the answer or not. Something shifted in how B2B buyers find vendors, and most companies haven't caught up. A VP of Operations at a fintech company needs a data integration platform. Two years ago, she would have Googled it, clicked through ten results, and built a shortlist over a few days. In 2026, she opens ChatGPT or Perplexity, types "best data integration platforms for mid-market fintech," and gets a curated answer in seconds. Three or four names. A brief explanation of each. Maybe a comparison table. If your company isn't in that answer, you didn't just miss a click. You missed the shortlist entirely. And the buyer may never know you exist. This is the new front door for B2B discovery — and most websites were built for a different one. (If you're new to the topic, start with our [introduction to Answer Engine Optimisation](/articles/what-is-aeo).) Which is precisely why AI search invisibility isn't just a marketing problem to solve with better content. It's a structural problem that makes rebuilding your website one of the highest-leverage moves you can make right now. ### The old SEO playbook doesn't transfer cleanly This is the core of [how AEO differs from SEO](/articles/aeo-vs-seo). Traditional SEO optimized for rankings. You targeted a keyword, built a page around it, earned backlinks, and climbed the results. The goal was position one on a list of ten blue links. AI search doesn't work that way. There is no list of ten. The model reads thousands of pages, synthesizes what it finds, and produces a direct answer. It doesn't rank your page — it decides whether to cite you. That distinction matters because the signals are different. Google's algorithm weighted backlinks, page authority, and keyword density. AI search engines weight clarity, structure, factual specificity, and whether your content actually answers the question in a way the model can extract and attribute. You can have strong domain authority, a page-one ranking for your target keyword, and still be completely absent from the AI-generated answer for the same query. The two systems are reading the same internet but evaluating it through different lenses. Google itself pushes back on framing this as two disciplines — its [guide to optimizing for generative AI features](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) argues that generative results are built on the same index and the same quality signals, so the durable work is the same work. Our experience is that both things are true: the foundation is shared, and the last mile — being extractable and attributable — is genuinely a different skill. ### Why your competitors show up and you don't If a competitor consistently appears in AI search results and you don't, it's usually one or more of these structural issues: **Their content is entity-clear. Yours isn't.** AI models need to understand what your company is — not just what your page is about. That means clear, unambiguous statements: who you serve, what category you compete in, what you do differently. If your homepage hedges with vague positioning language ("we empower teams to unlock potential"), the model has nothing concrete to extract. **Their site has structured data. Yours doesn't.** Schema markup — organization, product, FAQ, how-to — gives AI models a machine-readable layer on top of your content. It's the difference between a model inferring what your company does and a model knowing what your company does because you told it explicitly in a format it's designed to parse. **They've built topical depth. You've built isolated pages.** AI models assess authority by how thoroughly a site covers a topic. A single landing page about your product category isn't enough. A cluster of content — the product page, a comparison page, three blog posts addressing specific use cases, a case study with results — signals that your site is a credible source on the topic. Depth beats breadth. **Their content is structured for extraction. Yours is structured for skimming.** AI models pull answers from content that's organized with clear headings, direct statements, and logical flow. If your pages are walls of marketing copy with no structural hierarchy, the model can't efficiently pull a citable passage. The same content, reorganized with clear H2s and direct topic sentences, becomes extractable. ### The compounding problem Here's what makes this urgent rather than just important: AI search visibility compounds. When a model cites your competitor in an answer, users click through, engage with the content, and share it. That engagement generates more signals — links, mentions, traffic patterns — that feed back into the model's training data and reinforcement signals. The next time someone asks a similar question, the model is slightly more likely to cite that same source. Meanwhile, your absence compounds too. Every query where you're not cited is a missed signal. Over weeks and months, the model builds stronger associations with your competitors and weaker ones with you. The gap doesn't stay flat — it widens. This is fundamentally different from traditional SEO, where you could always grind your way up the rankings with enough effort and time. In AI search, early movers build a structural advantage that becomes harder to overcome the longer you wait. ### What to do about it Fixing AI search visibility isn't a single tactic — it's a set of structural changes to how your site presents information. (Use the [five-level AEO Maturity Model](/articles/aeo-maturity-model) to honestly assess which level you're starting from.) Here's where to start: **Audit your entity clarity.** Read your homepage and product pages as if you're a model trying to categorize your company. Can you extract a clear, factual statement of what you do, who you serve, and what category you compete in? If not, rewrite until you can. First paragraph, plain language, no hedge words. **Implement structured data across your site.** At minimum: Organization schema on every page, Product schema on product pages, FAQ schema where applicable, Article schema on blog content. One caveat worth stating honestly, because most articles on this topic skip it: Google is explicit that [no special schema.org markup is required](https://developers.google.com/search/docs/appearance/ai-features) to appear in AI Overviews, and it removed FAQ rich results from Search in May 2026. Schema is infrastructure for comprehension and for the non-Google engines that do parse it. It is not a Google ranking lever, and anyone selling it as one is overstating the case. **Build content depth around your core topics.** Identify the three to five queries a buyer would ask an AI model when evaluating your category. Build a cluster of content around each one: a definitive page, supporting blog posts, a case study, a comparison. Aim for topical coverage a model would recognize as authoritative. **Structure content for extraction.** Every page should have clear H2 headings that mirror how a buyer would phrase a question. Lead each section with a direct, factual statement — not a rhetorical question or a clever hook. The first sentence under each heading should be citable on its own. **Monitor your visibility.** Regularly search for your target queries in ChatGPT, Perplexity, and Google AI Overviews. Track whether you're cited, how you're described, and which competitors appear alongside you. There's no ranking to track — just presence or absence. ### This isn't optional anymore — it's a reason to rebuild Two years ago, AI search was an experiment. Today, it's where a growing share of B2B buyers start their evaluation. The companies that restructured their sites early are already seeing the compounding benefits — more citations, more traffic, more pipeline from a channel that most of their competitors haven't even started optimizing for. Here's the uncomfortable truth: you can't meaningfully implement AEO on most legacy B2B websites. The structural changes required — schema markup at the component level, entity-clear content architecture, CMS-driven structured data, semantic HTML hierarchy — go deeper than what a content refresh or plugin can address. And none of it counts until the basics hold: Google's [technical requirements](https://developers.google.com/search/docs/essentials/technical) are the floor, and a site that fails them is invisible to every engine downstream regardless of how good its content is. AEO isn't a layer you add. It's an architectural decision that shapes how the site is built from the ground up. That's what makes AI search invisibility one of the most compelling reasons to rebuild, not just optimize. A rebuild gives you the chance to implement AEO into the foundation — structured data baked into every component, a CMS that enforces entity clarity, a content model designed for extraction. Trying to bolt this onto a legacy site takes months of patchwork and delivers a fraction of the results. If your site was built for the old search engine — the one that ranked pages instead of synthesizing answers — it's not just underperforming. It's one of the clearest signs you've [outgrown your current website](/articles/six-signs-youve-outgrown-your-current-website/). The good news: these changes are structural, not cosmetic. [A well-planned rebuild](/articles/b2b-website-rebuild-process/) can address AI search visibility alongside every other gap your site has accumulated. The key is doing it before the compounding advantage swings too far in your competitors' favor. Want to know where you stand? [Book a free AI search audit with BrandingLab](/contact) — we'll run your target queries, show you who's showing up instead of you, and map out what it takes to get cited. --- ### Continue your AEO learning - [The complete guide to Answer Engine Optimisation](/articles/what-is-aeo) — the foundational pillar with the full framework. - [How AEO and SEO differ for B2B companies](/articles/aeo-vs-seo) — why your existing SEO investment doesn't automatically translate. - [The AEO Maturity Model](/articles/aeo-maturity-model) — diagnose which of the five levels your site sits at today. ### Frequently asked questions #### What is Answer Engine Optimization (AEO)? Answer Engine Optimization is the practice of structuring website content so that AI-powered search engines — including ChatGPT, Perplexity, and Google AI Overviews — can find, understand, and cite it in direct answers to user queries. Unlike traditional SEO, which optimizes for page rankings on a results list, AEO optimizes for inclusion in synthesized answers. Key tactics include clear entity definitions, structured data markup (schema), topical content depth, and content structured so individual statements are extractable and attributable. #### What is the difference between SEO and AEO? SEO (Search Engine Optimization) focuses on ranking a page higher in a list of search results. AEO (Answer Engine Optimization) focuses on getting your content cited in a direct, synthesized answer. SEO signals include backlinks, page authority, and keyword density. AEO signals include content clarity, structured data, factual specificity, and whether the content is organized so an AI model can extract and attribute a citable passage. A site can rank well in traditional search and still be completely absent from AI-generated answers. #### How do I check if my website appears in AI search results? Search for the queries your buyers would use — for example, "best [your category] for [your target market]" — in ChatGPT, Perplexity, and Google AI Overviews. Note whether your company is mentioned, how it's described, and which competitors appear. Repeat this monthly for your 20 most important buyer queries, running each one three times. There is no equivalent of a ranking position to track — you are either cited in the answer or you are not. If the fixes above are more than your in-house team can ship in a quarter, [our AEO services](/aeo-services) cover the architecture, schema, citation work and reporting end-to-end. --- ### Article: Why We Use Webflow to Build High-Converting Brands **URL:** https://www.brandinglab.io/articles/why-we-use-webflow-for-high-converting-brands **Published:** 2026-04-19 **Read time:** 7 min read **Author:** BrandingLab, Studio Editorial **Category:** Strategy **Key takeaways:** - Webflow removes three conversion killers: deploy lag, design compromise, and CMS rigidity. - CMS architecture isn't a backend chore — it's a growth lever. Model your content around how you sell, not how you publish. - We hold every brand site to a strict performance budget: LCP < 1.8s, CLS < 0.05, JS payload < 150KB. - Webflow stops being the right answer when you need bespoke product UX, real-time data, or complex auth — that's where AI Products take over. - The stack decision is downstream of the brand decision. Pick velocity, fidelity and clean HTML, and Webflow falls out as the answer. ### The stack decision behind every brand site When a client asks us "what should we build it on?" they're usually expecting a comparison matrix. We don't do that — though if you want the full head-to-head, our [Webflow vs. WordPress verdict for branding agencies](/articles/webflow-vs-wordpress-for-branding-agencies) lays it out. The stack decision is downstream of the brand decision. We pick the platform that lets us protect three things: **design fidelity, marketing-team velocity, and clean HTML for AI search**. For mid-market B2B brand sites, Webflow wins on all three more often than anything else. That's it. There's no ideology. This piece is the inside view — the actual reasons Webflow keeps winning the vote in our studio after seven years of shipping brand sites. ### Three things Webflow does that move conversion #### 1. It collapses the gap between design and production This only holds when the underlying system is well-built — see [building a design system that actually scales](/articles/design-system-that-scales) for the rules we apply. Most CMSs force a translation step: designer hands a Figma file to a developer, who rebuilds it in code, and 15% of the brand intent gets lost in the handoff. Webflow lets the designer build the production site directly. Spacing, typography, motion, hover states — all of it lives in the same canvas the designer is working in. The brand that ships is the brand that was designed. That fidelity converts. #### 2. It removes the deploy queue This is the single biggest reason [agencies see project timelines drop by up to 40% after switching to Webflow](/articles/benefits-of-webflow-for-agencies). A marketing team that can publish a new landing page, a copy test, or a campaign asset on the same day they decide to is a marketing team that compounds. A team that has to file tickets and wait for a sprint loses 60% of its momentum to coordination overhead. Webflow's editor + staging + one-click publish flow is the single biggest velocity unlock we see, and velocity is the input to every conversion metric that matters. #### 3. It ships HTML AI search engines can actually read Clean semantic markup, server-rendered, lazy-loaded images, schema-ready. We've watched clients gain visibility in Perplexity and ChatGPT answers within weeks of moving off a JS-heavy stack onto Webflow. The page hasn't changed; the machine-readability has. See our [AEO Maturity Model](/articles/aeo-maturity-model) for the underlying framework. ### Migrating clients off WordPress Most of the brand sites we ship aren't greenfield — they replace a tired WordPress install. Our [five-step WordPress to Webflow migration process](/articles/wordpress-to-webflow-migration-for-b2b) is how we move them without losing SEO equity. ### CMS architecture as a growth lever Most teams treat the CMS as a backend chore. We treat it as a growth lever. The way you model your content shapes what your marketing team can do without engineering involvement. A few principles we apply on every Webflow build: - **Model content around how you sell, not how you publish.** A "Solution" collection mapped to buyer personas beats a generic "Page" collection every time. - **Componentise the building blocks** — testimonial blocks, feature grids, pricing modules — so a marketer can assemble a new page from existing parts in 30 minutes. - **Keep the CMS opinionated.** Too many fields and the team freezes. Six well-named fields beats twenty optional ones. - **Bake schema markup into the templates**, not into individual pages. AEO compounds when it's structural. Done right, the CMS becomes the marketing team's launch pad, not their bottleneck. ### The performance budget we hold ourselves to Every brand site we ship has to clear the same bar: - **LCP under 1.8 seconds** on a mid-tier mobile device on 4G - **CLS under 0.05** - **Total JavaScript payload under 150KB** gzipped - **Lighthouse performance score 95+** on the homepage and top three landing pages - **Accessibility score 95+** with full keyboard navigation and visible focus states These aren't aspirational. They're the line we don't ship below. Webflow makes that line achievable without heroics, which is exactly why it's our default. ### Where Webflow stops being the right answer We're not Webflow maximalists. There's a clear line where it stops being the right tool: - **Bespoke product UX** — dashboards, configurators, anything stateful → custom React - **Real-time data or live integrations** with your product → custom React + your API - **Complex authenticated experiences** beyond gated content → custom React with a proper auth layer - **AI-native interfaces** — chat, agents, generative UI → that's our [AI Products](/ai-products) practice When we hit those needs, we stop pretending Webflow is the answer and we build a real application. Knowing where the line is matters more than picking a side of it. ### The bottom line Webflow isn't our default because it's trendy. It's our default because it protects design fidelity, removes the deploy queue, and ships clean HTML — the three things that quietly determine whether a brand site converts or just exists. When the brief is a mid-market B2B brand site, Webflow earns the slot. When the brief is something else, we use something else. ### Continue reading - [Webflow vs. WordPress for Branding Agencies](/articles/webflow-vs-wordpress-for-branding-agencies) — An honest 2026 verdict across velocity, brand fidelity, AEO and 3-year total cost of ownership. - [Benefits of Transitioning to Webflow for Agencies](/articles/benefits-of-webflow-for-agencies) — How Webflow cuts agency project timelines by up to 40% and increases project margins. - [WordPress to Webflow Migration](/articles/wordpress-to-webflow-migration-for-b2b) — A structured five-step process for moving off WordPress without losing SEO equity. - [Building a Design System That Actually Scales](/articles/design-system-that-scales) — Variables, reusable components and conventions that hold up as your team and site grow. ### Frequently asked questions #### Why not use a custom React build for every brand site? Because it's the wrong tool for the job. A bespoke React build for a 40-page brochure site means your marketing team needs a developer to change a headline. That's a six-figure mistake disguised as a sophisticated decision. Use React when state and product UX demand it. #### Is Webflow really fast enough for enterprise? Yes. We ship Webflow sites that hit Lighthouse 95+ and LCP under 1.8s as a default, not a stretch. The platform isn't the bottleneck — the build discipline is. #### How long does a typical Webflow brand site take to ship? For a mid-market B2B brand with 30–60 pages, our typical timeline is 8–12 weeks end to end: discovery, design system, build, QA, launch. Faster than the equivalent custom build by a factor of two to three. #### Can we move off Webflow later if we outgrow it? Yes. Content exports cleanly, URL structure is portable, and the design system you built lives in your tokens, not in Webflow. We've migrated sites both directions without drama. --- Ready to talk specifics? See our [Webflow agency services](/webflow-agency) — or compare stacks in [Webflow vs. WordPress for branding agencies](/articles/webflow-vs-wordpress-for-branding-agencies). --- ### Article: Webflow vs. WordPress for Branding Agencies: An Honest 2026 Verdict **URL:** https://www.brandinglab.io/articles/webflow-vs-wordpress-for-branding-agencies **Published:** 2026-04-19 **Read time:** 9 min read **Author:** BrandingLab, Studio Editorial **Category:** Strategy **Key takeaways:** - For brand-led B2B sites under ~200 pages, Webflow wins on velocity, design fidelity and AEO out of the box. - WordPress still wins for content empires (1,000+ posts), heavy editorial workflows and self-hosted compliance edge cases. - The real cost isn't the licence — it's the deploy queue. Marketing autonomy is the line item nobody puts in the spreadsheet. - Clean, semantic HTML is now an AEO ranking input. Webflow ships it by default; most WordPress themes don't. - Decide on velocity and brand expression first. Stack second. ### TL;DR — the honest verdict For a mid-market B2B brand site under ~200 pages, **Webflow wins**. You ship faster, your designers don't fight a theme, your marketers don't file tickets to change a headline, and your HTML is clean enough that ChatGPT and Perplexity can actually parse it. WordPress still wins when you're running a content empire — 1,000+ posts, complex editorial workflows, or self-hosted compliance constraints. Everywhere else, the deploy-queue tax of WordPress quietly eats your roadmap. This isn't a feature table. It's the framework we use when a client asks us which platform to bet on for the next three years. The studio-level version of the same argument lives in [why we use Webflow to build high-converting brands](/articles/why-we-use-webflow-for-high-converting-brands). ### The real question isn't features — it's velocity Both platforms can technically build the same brochure site. So feature-comparing them misses the point. The question is: **how fast can your team ship a brand-relevant change next Tuesday?** On WordPress, a typical "add a new pricing tier" change touches a custom post type, an ACF field group, a template file, a CSS rebuild, a staging deploy, QA, and a production push. Best case: two days, one developer. Worst case: it sits in a Jira backlog for six weeks. On Webflow, the same change is a CMS field added in the Designer, a binding dropped onto the page, and Publish. Best case: 40 minutes, one designer. There is no deploy queue because there is no deploy. That compounding velocity is what moves position 61 to position 11. ### Design fidelity & brand expression WordPress themes — even the premium ones — encode somebody else's design opinions. Block editor + a page builder gets you 80% of the way to your brand, then the last 20% turns into a custom-CSS knife fight. Anyone who has shipped a Gutenberg site knows the feeling of a designer asking "why is there extra padding here?" and the answer being "because the theme." Webflow inverts the relationship. You build the design system first — tokens, components, interactions — and the CMS slots into *your* layout instead of the other way round. For a branding agency, that's the whole game. The brand isn't decoration applied at the end. It's the architecture. ### Marketing-team autonomy: the deploy-queue tax The single most underrated cost of WordPress at the mid-market is the **deploy queue**. Every meaningful copy change, new landing page, or campaign asset becomes a developer ticket. Multiply that by a marketing team running 4–8 campaigns a quarter and you're paying a hidden tax of 30–50 dev-hours per month just to keep the site current — the exact velocity gap covered from the agency angle in [the benefits of transitioning to Webflow for agencies](/articles/benefits-of-webflow-for-agencies). Webflow lets your marketers: - Edit live copy directly on the page (no admin UI context-switch) - Spin up new landing pages from a template in an afternoon - A/B test layouts without a developer in the loop - Publish to production in one click, with a rollback always one click away That's not a productivity nice-to-have. It's the difference between a marketing team that ships weekly and one that ships when engineering has capacity. ### Performance, Core Web Vitals & AEO This is where the gap has widened most in 2025–2026. AI search engines — ChatGPT Search, Perplexity, Gemini, Claude — don't render JavaScript-heavy pages well. They reward clean, semantic HTML with crisp heading hierarchy and predictable structure. Webflow ships that by default: server-rendered HTML, lazy-loaded images, minimal JS, automatic CDN, schema-friendly markup. Most WordPress installs ship the opposite — a theme, a builder, a caching plugin, a security plugin, and 14 more — bloating the DOM and tanking Largest Contentful Paint. For an in-depth view, see our [AEO Maturity Model](/articles/aeo-maturity-model). The short version: clean HTML is now a ranking input, and Webflow gives it to you for free. ### Total cost of ownership over 3 years A realistic 3-year TCO comparison for a 50-page mid-market B2B site: | Line item | WordPress | Webflow | | --- | --- | --- | | Platform / hosting | $1,500 | $5,400 | | Theme + premium plugins | $2,500 | $0 | | Developer maintenance | $18,000 | $4,500 | | Security / uptime incidents | $4,000 | ~$0 | | Marketing dev tickets | $24,000 | $3,000 | | **3-year total** | **~$50,000** | **~$13,000** | Webflow's licence is more expensive. Everything else is dramatically cheaper. The platform fee was never the real cost. ### When WordPress still wins We're not anti-WordPress. We've shipped on it for years. It's still the right call when: - You're running 1,000+ posts with serious editorial workflows (multi-author, draft → review → publish, scheduled syndication) - You need self-hosted control for regulatory or data-residency reasons - You depend on a mature plugin ecosystem (LMS, complex membership, marketplace) - You already have a WordPress dev team you trust and can't replatform without disrupting the business If any of those describe you, stay on WordPress and invest in headless. If none do, you're paying a tax for software you don't need. ### How we'd decide (the 60-second matrix) - **Brand-led B2B site, < 200 pages, marketing-team owned →** Webflow. Always. The cleanest way to get there from an existing WordPress install is our [five-step WordPress to Webflow migration](/articles/wordpress-to-webflow-migration-for-b2b), built on top of a [design system that actually scales](/articles/design-system-that-scales). - **Content empire, 1,000+ posts, editorial-heavy →** WordPress (or headless WP + a modern frontend). - **Bespoke product or AI-native experience →** Neither. See [AI Products](/ai-products) — that's a custom React build. - **You already ship weekly on your current stack and you're happy →** Don't replatform for the sake of it. ### Continue reading - [Why We Use Webflow to Build High-Converting Brands](/articles/why-we-use-webflow-for-high-converting-brands) — The stack philosophy behind every brand site we ship — design fidelity, no deploy queue, AI-readable HTML. - [Benefits of Transitioning to Webflow for Agencies](/articles/benefits-of-webflow-for-agencies) — How Webflow cuts agency project timelines by up to 40% and increases project margins. - [WordPress to Webflow Migration](/articles/wordpress-to-webflow-migration-for-b2b) — A structured five-step process for moving off WordPress without losing SEO equity. - [Building a Design System That Actually Scales](/articles/design-system-that-scales) — Variables, reusable components and conventions that hold up as your team and site grow. ### Frequently asked questions #### Is Webflow really better for SEO than WordPress in 2026? For most B2B brand sites, yes — primarily because the HTML Webflow ships is cleaner and more semantic than a typical WordPress theme + builder stack. That matters more than ever now that AI search engines weigh structural clarity heavily. WordPress can match it, but only with disciplined headless architecture. #### Can we migrate from WordPress to Webflow without losing rankings? Yes, with a proper redirect map and parity on URL structure, headings and metadata. We've migrated sites with five-figure monthly organic traffic and held rankings within a 5% band through the transition. The risk is real but managed. #### What about Webflow's CMS limits — 10,000 items per collection? For 95% of B2B sites, you'll never hit it. If you do, you're in content-empire territory and probably shouldn't be on Webflow anyway. Pick the platform for the next three years, not the next thirty. #### Does Webflow support enterprise compliance (SOC 2, GDPR, accessibility)? Webflow Enterprise ships with SOC 2 Type II, GDPR tooling, and a strong baseline for WCAG. You still own accessibility at the design level — the platform doesn't do that for you. --- Want the agency view on Webflow specifically? See our [Webflow agency services](/webflow-agency) — or read [why we use Webflow to build high-converting brands](/articles/why-we-use-webflow-for-high-converting-brands). --- ### Article: What a B2B Website Rebuild Actually Looks Like (Timeline, Process, What to Expect) **URL:** https://www.brandinglab.io/articles/b2b-website-rebuild-process **Published:** 2026-04-19 **Read time:** 12 min read **Author:** BrandingLab Team, B2B Website Studio **Category:** Web Strategy **Key takeaways:** - A B2B website rebuild takes 8–12 weeks from kickoff to launch for most mid-market companies. Content readiness is the biggest variable. - The six phases are discovery, messaging, design, build, migration, and launch. Skipping the first two is the most common reason rebuilds underperform. - Messaging comes before design. Write the content first, then design to serve it. - Migration is where SEO equity is won or lost. Map every URL and 301-redirect before launch. - Expect 5–8 hours per week from your team, plus one decision-maker and 2–3 feedback rounds per milestone. - The goal is infrastructure marketing can operate independently — not just a nicer-looking site. - AEO (Answer Engine Optimization) is built in during the rebuild, not bolted on after. Content architecture, structured data, and answer-shaped copy decide whether ChatGPT, Perplexity, and Google's AI Overviews cite you. You've recognized [the signs](/articles/six-signs-youve-outgrown-your-current-website/). The site doesn't reflect the business anymore. Pipeline isn't converting the way it should. Marketing can't move without filing a dev ticket. AI answer engines — ChatGPT, Perplexity, Claude, Google's AI Overviews — don't cite you when buyers ask the questions you should be the answer to. Now comes the question everyone asks next: what does a rebuild actually look like? How long does it take? What does the team need to commit? And what separates a rebuild that works from one that just creates a nicer-looking version of the same problems? This is the practical walkthrough. No abstract frameworks — just what happens, in what order, and what to expect at each stage. ### ### Frequently asked questions #### How long does a B2B website rebuild take? A typical mid-market B2B website rebuild takes eight to twelve weeks from kickoff to launch. The process follows six phases: discovery and strategy (weeks 1–2), messaging and content (weeks 2–4), design (weeks 4–6), build and development (weeks 6–9), migration and QA (weeks 9–10), and launch (weeks 10–12). The biggest variable is content readiness — teams that enter the project with positioning and messaging already defined can compress the early phases significantly. #### How much does a B2B website rebuild cost? Cost varies based on scope, platform, and complexity. For mid-market B2B companies, a full rebuild — including strategy, messaging, design, Webflow development, CMS architecture, and migration — starts from $15,000 (typical range $8,000–$20,000 by scope) for a B2B Webflow project with strategy, design, build and AEO foundation. Larger brand-strategy programmes (positioning, identity, website and sales collateral together) are scoped separately on request. The key cost drivers are the number of unique page templates, the complexity of CMS collections, the number of third-party integrations, and whether the project includes a full rebrand or just a website rebuild. The ROI calculation should factor in the pipeline cost of keeping an underperforming site. #### Will I lose my SEO rankings during a website rebuild? Not if the migration is executed properly. The critical steps are: mapping every existing URL that drives traffic or has backlinks to its new equivalent, implementing 301 redirects before launch, migrating all metadata and alt tags, verifying internal links, and submitting the new sitemap to Google Search Console immediately after launch. Most well-executed rebuilds see organic traffic recover within two to four weeks and improve within eight weeks as the new site's content architecture and performance gains take effect. A rebuild also creates the opportunity to optimize for [AI search visibility](/articles/b2b-ai-search-visibility/), which requires structured data and content architecture that most legacy sites lack. #### What is the difference between a website redesign and a website rebuild? A redesign updates the visual layer — new colors, layouts, and imagery — while keeping the existing platform, CMS, and information architecture. A rebuild replaces the underlying infrastructure: the platform, CMS configuration, content model, design system, and page architecture. If your problems are purely cosmetic, a redesign may work. If marketing can't publish independently, the CMS is inflexible, or the site's structure no longer matches how buyers evaluate and purchase, a rebuild is what's needed. #### What does my team need to do during a website rebuild? Your team's primary commitment is five to eight hours per week. You need one decision-maker (typically a marketing leader or founder) who can approve direction at each phase, availability for weekly check-in calls, and capacity for two to three rounds of feedback at each major milestone (strategy brief, messaging, design, and pre-launch). The rebuild partner handles execution — your role is to provide context, make decisions, and validate that the output matches your business reality. #### Should I write website copy before or after design? Before. Messaging and content should be written before design begins. This is because design should serve the story, not the other way around. When designers work with real headlines at real lengths, real value propositions, and real calls to action, the output is significantly stronger than designs built around placeholder text. Sites designed with lorem ipsum consistently end up with vague, compromise copy shoehorned into layouts that weren't built for the actual message. #### What is AEO and why does it matter for a B2B website rebuild? AEO (Answer Engine Optimization) is the practice of structuring your site so AI answer engines — ChatGPT, Perplexity, Claude, [Google AI Overviews](/articles/google-ai-search-cannibalization/) — can extract, trust, and cite your content when buyers ask questions. For B2B, where buyers increasingly start research in AI tools rather than Google, AEO determines whether you appear in the answer or get omitted entirely. A rebuild is the right moment to implement it because content architecture, structured data, semantic HTML, and component design all need to be built for it from the ground up — retrofitting AEO onto a legacy site is significantly more expensive and slower than building it in during the rebuild. --- *BrandingLab helps mid-market B2B teams design and build websites that match the pace of their business. We specialize in Webflow builds, brand-driven redesigns, and sites engineered for AI-era discoverability.* Most rebuilds we ship are paired with the first 90 days of an [answer engine optimisation programme](/aeo-services) so the new site lands with citation share already moving. --- ### Article: What Is AEO? The Complete Guide to Answer Engine Optimisation **URL:** https://www.brandinglab.io/articles/what-is-aeo-answer-engine-optimisation **Published:** 2026-04-16 **Read time:** 6 min read **Author:** BrandingLab, AEO & Digital Strategy **Category:** AEO **Key takeaways:** - AEO is about being cited by AI engines (ChatGPT, Perplexity, Google AI Overviews) — not just ranking on a results page. - Structure content for extraction: clear questions, concise direct answers, semantic HTML and FAQ schema. - Build entity authority — consistent NAP, structured data, and citations from sources LLMs already trust. - Treat AEO as an extension of SEO, not a replacement: traditional rankings still feed AI training and retrieval. - Measure visibility by tracking when and how AI engines reference your brand, not only by keyword positions. ### What Is Answer Engine Optimisation? **Answer Engine Optimisation (AEO)** is the practice of optimising your site so it gets cited and recommended by AI search engines — ChatGPT, Gemini, Claude, Perplexity, and Google AI Overviews — not just ranked in traditional search results. The shift is fundamental: AI is the new middleman between brands and buyers. When a procurement lead asks ChatGPT *"What are the best enterprise Webflow agencies?"*, your brand either appears in that answer or it doesn't. There is no page two. 93% of marketing leaders say AEO is critical to their strategy, but only 25% of practitioners fully understand how to execute it. **That gap is your opportunity.** --- ### AEO vs SEO: What's the Difference? AEO doesn't replace SEO — it extends it. (For a deeper breakdown, see [how AEO differs from SEO](/articles/aeo-vs-seo).) Traditional SEO targets search engine rankings. AEO ensures your brand is cited when AI tools answer questions about your industry. The structured data, content quality, and authority signals that help with AEO also improve traditional search performance. Think of it as an additional channel, not a replacement. | | **SEO** | **AEO** | |---|---|---| | **Target** | Search engine rankings | AI-generated answers | | **Goal** | Rank on page one | Be cited as the answer | | **Signals** | Backlinks, keywords, technical SEO | Authority, structure, entity clarity | | **Measurement** | Rankings, CTR, traffic | AI mentions, citation frequency, share of voice | --- ### The AEO Maturity Model Not every brand starts from the same place. Use this five-level framework to diagnose where you stand today and what it takes to move up — and read [the five-level AEO Maturity Model](/articles/aeo-maturity-model) for the deeper diagnostic. #### Level 1: Keywords - **Content:** Keyword-focused pages - **Technical:** On-page SEO only - **Authority:** Backlinks - **Measurement:** Keyword rankings #### Level 2: Answers - **Content:** Some answer-oriented content - **Technical:** Basic structure in place - **Authority:** Active E-E-A-T signals - **Measurement:** Ad hoc mention checks #### Level 3: Structure - **Content:** Answering question clusters systematically - **Technical:** Consistent structure, fast site - **Authority:** Proactive PR and thought leadership - **Measurement:** Tracking LLM traffic and mentions #### Level 4: Pillar - **Content:** Answer-hierarchy driven content architecture - **Technical:** Automated structure and schema - **Authority:** Recognised industry pillar - **Measurement:** Share of voice tracking across AI engines #### Level 5: Authority - **Content:** Programmatic and personalised content - **Technical:** MCP integration and early standards adoption - **Authority:** Widespread AI citations across platforms - **Measurement:** Real-time analytics and AI visibility dashboards --- ### The Numbers Behind AEO The data makes the case clearly: - **75%** more monthly organic traffic for brands adopting AI-powered SEO strategies - **93%** of marketing leaders say AEO is critical to their strategy - **25%** of practitioners fully understand how to execute AEO — the gap early movers can exploit - **14x** traffic increase for enterprises that commit to an AEO-first approach --- ### How Webflow Approaches AEO Webflow's AEO system follows a three-phase loop: #### Measure - Track AI crawler activity and crawl patterns - Monitor brand visibility scores across ChatGPT, Gemini, and other AI engines - Identify which pages get cited and by which LLMs - Measure AI-referred visitors and conversion data #### Recommend - Receive site-specific, prioritised AEO recommendations - Get brand-specific guidance — not generic advice - Identify topics, content gaps, and structure fixes #### Act - AEO agents apply changes directly to your site - Review-before-publish safeguards keep you in control - No developer handoff needed - Changes go live on Webflow's CMS and hosting --- ### How to Get Started with AEO #### 1. Run an AI Visibility Audit Query major AI engines with your target buyer questions. Map exactly where your brand appears — or doesn't. This is your baseline. ([Why your B2B site isn't showing up in AI search](/articles/b2b-ai-search-visibility) walks through the most common structural reasons.) #### 2. Assess Your Maturity Level Use the maturity model above to honestly evaluate where your content, technical setup, authority, and measurement capabilities sit today. #### 3. Prioritise Quick Wins Focus on structured data, FAQ schema, and clear entity definitions first. These are the signals AI engines rely on most when deciding which brands to cite. #### 4. Build Authority Signals Invest in thought leadership, PR, and citation networks. AI engines prioritise brands they can verify through multiple trusted sources. #### 5. Monitor and Iterate Track your AI visibility monthly. The algorithms evolve — your strategy needs to evolve with them. --- ### Why Act Now? Less than 5% of B2B companies are actively optimising for AI search. The brands showing up in AI answers today are training future models. Your competitors are moving — the question is whether you want to be ahead or catching up. **The window for first-mover advantage is closing.** [Get a free AEO audit](/contact) and see exactly where your brand stands in AI-generated answers. --- ### Continue your AEO learning - [How AEO and SEO differ for B2B companies](/articles/aeo-vs-seo) — how the two disciplines diverge and where they share foundations. - [The AEO Maturity Model](/articles/aeo-maturity-model) — a five-level framework to diagnose where your site sits today. - [Why your B2B website isn't getting cited in AI search](/articles/b2b-ai-search-visibility) — the structural reasons competitors get cited and you don't, with the fixes that matter. Ready to put this into practice? See [our answer engine optimisation services](/aeo-services) for how we run AEO programmes for B2B mid-market teams. ### Frequently asked questions #### What is Answer Engine Optimisation (AEO)? Answer Engine Optimisation (AEO) is the practice of structuring and optimising web content so artificial intelligence assistants—including ChatGPT, Claude, Perplexity, and Google AI Overviews—cite, quote, and recommend your brand as the direct source in synthesized answers. Unlike traditional SEO, which focuses on ranking clickable links in search engine results pages, AEO aims to win zero-click synthesized answers where an AI delivers a single definitive recommendation to procurement leads and buyers. #### How does AEO differ from traditional SEO for B2B companies? While traditional SEO prioritizes backlink quantity, keyword density, and organic ranking positions on Google, AEO focuses on entity authority, factual consistency, and structured data that AI models ingest. SEO drives traffic through search result page clicks, whereas AEO secures brand authority and citations when buyers ask AI chatbots for market comparisons and vendor recommendations. The two disciplines share foundations, but AEO requires direct-answer formatting and schema that AI crawlers can extract with zero ambiguity. #### How do AI answer engines decide which sources to cite? Answer engines evaluate content on technical clarity, domain authority, and answer structure. They favor pages with explicit Schema.org markup (such as FAQPage and Article schemas), direct definitions placed in the first sentence beneath question headings, and unblocked AI crawler access (such as GPTBot and ClaudeBot). Additionally, models cross-reference claims against external authoritative sources, meaning consistent industry mentions, executive bylines, and unambiguous factual data dramatically increase citation frequency. #### What are the most critical technical fixes to make a site citable? The fastest technical wins for AI citation readiness include adding valid FAQPage JSON-LD structured data, phrasing H2 and H3 section headings as explicit user questions, and providing self-contained, 60-to-120-word answers directly beneath those headings. Sites must also verify that their robots.txt file and Cloudflare firewalls permit verified AI crawlers like GPTBot, ClaudeBot, and PerplexityBot, while ensuring canonical tags and sitemaps accurately index the citable URLs. --- ### Article: The AEO Maturity Model: Where Does Your B2B Website Stand? **URL:** https://www.brandinglab.io/articles/aeo-maturity-model **Published:** 2026-04-01 **Read time:** 7 min read **Author:** BrandingLab, Editorial **Category:** AEO **Key takeaways:** - Most B2B sites sit at Level 1–2 of AEO maturity: SEO-optimised but invisible to AI engines. - Level 3 means structured content, FAQ schema and clear entity definitions LLMs can parse. - Level 4 brands actively monitor AI visibility and iterate on prompts where they should appear. - Level 5 is rare — proactive content engineering for retrieval, with measurable share-of-AI-voice. - Audit honestly before investing: most teams need foundational fixes before advanced AEO tactics pay off. The AEO Maturity Model describes five levels of AI search readiness — from keyword-only content to programmatic authority. (New to the topic? Start with our [introduction to Answer Engine Optimisation](/articles/what-is-aeo).) ### Why a Maturity Model? Most B2B companies know they should be thinking about AI search visibility, but don't know where to start. The maturity model gives you a framework for assessing your current position and planning your next steps. ### The Five Levels #### Level 1: Keyword-Only Content Your site targets traditional search keywords but has no structured data, no FAQ markup, and no content formatted for AI consumption. #### Level 2: Basic Structure You've added some schema markup and your content follows a question-and-answer format in places, but it's inconsistent and not strategically planned. #### Level 3: Intentional AEO Your content strategy explicitly targets AI engines. You have comprehensive schema markup, entity definitions, and a citation-building programme in place. #### Level 4: Authority Position AI engines regularly cite your brand as an authority in your space. You monitor AI mentions and iterate on content based on what's working. #### Level 5: Programmatic Authority You've built systems that automatically generate and update structured content, monitor AI citations in real time, and continuously optimise for new AI engine behaviours. ### Where Do You Start? Run a free AEO audit to find out exactly where your site stands today. For the tactical fixes that move you up the model, read [how to fix B2B AI search visibility](/articles/b2b-ai-search-visibility). --- ### Continue your AEO learning - [The complete guide to Answer Engine Optimisation](/articles/what-is-aeo) — start here for the full definition, signals, and execution roadmap. - [How AEO and SEO differ for B2B companies](/articles/aeo-vs-seo) — why moving past Level 1 means rethinking what "ranking" actually means. - [Why your B2B website isn't getting cited in AI search](/articles/b2b-ai-search-visibility) — the structural changes that get you out of Level 1–2 and into citation-worthy territory. Know where you sit on the model and want to move up two levels in the next two quarters? [Work with our AEO team](/aeo-services) — that's exactly the engagement we run. ### Frequently asked questions #### What is the AEO Maturity Model? The AEO Maturity Model describes five levels of AI search readiness, from keyword-only content through to programmatic authority. It exists because most B2B companies know they should be thinking about AI search visibility but have no framework for assessing where they currently stand. #### What are the five levels of AEO maturity? Level 1 is keyword-only content with no structured data or AI-readable formatting. Level 2 is basic structure — some schema and some question-and-answer content, but inconsistent. Level 3 is intentional AEO, with comprehensive schema, entity definitions, and a citation-building programme. Level 4 is authority position, where AI engines regularly cite you. Level 5 is programmatic authority, with systems that generate structured content and monitor citations automatically. #### What level are most B2B websites at? Most sit at Level 1 or Level 2 — targeting traditional search keywords with no structured data, or with some schema and question-and-answer content that is inconsistent and not strategically planned. Level 3 is where a content strategy explicitly targets AI engines, with comprehensive schema markup, entity definitions, and a citation-building programme in place. #### How do I find out which level my site is at? Run a free AEO audit to see where your site stands today. The audit checks the structural signals that separate the levels, so it tells you both your current position and the specific gap to the next one. #### What moves a site up the maturity model fastest? Fixing the structural fundamentals first — making sure crawlers can read your pages, then adding schema and answer-first content structure. Tactical content work has little effect if the underlying pages are not readable or not clearly attributed to your brand entity. --- ### Article: AEO vs SEO: What's the Real Difference for B2B Companies? **URL:** https://www.brandinglab.io/articles/aeo-vs-seo **Published:** 2026-03-20 **Read time:** 6 min read **Author:** BrandingLab, Editorial **Category:** AEO **Key takeaways:** - SEO optimises for ranking on a results page; AEO optimises for being the answer inside an AI response. - AEO rewards clarity, structure and citation-worthiness over keyword density. - You still need SEO foundations — AI engines retrieve from the same indexed web. - B2B buyers increasingly start research in ChatGPT and Perplexity; missing there means missing the shortlist. - Run both strategies in parallel: SEO for traffic, AEO for visibility inside AI-generated answers. [Answer Engine Optimisation](/articles/what-is-aeo) (AEO) and SEO are complementary disciplines, not competing ones. Understanding exactly how they differ — and where they overlap — helps B2B marketing teams invest in both without duplicating effort. ### The Core Difference **SEO** optimises for search engine results pages — rankings, click-through rates, and organic traffic. **AEO** optimises for AI-generated answers — citations, recommendations, and brand mentions in tools like ChatGPT, Perplexity, and Google AI Overviews. ### Where They Overlap - High-quality, authoritative content - Structured data and schema markup - Strong backlink profiles and brand authority - Fast, well-structured websites ### Where They Diverge SEO focuses on keyword rankings and SERP features. AEO focuses on how AI models understand and reference your brand entity. The signals are related but not identical. ### The Bottom Line Don't choose between AEO and SEO. Invest in both — starting with the foundations they share, then layering in AEO-specific optimisations like entity definitions, citation networks, and AI-readable content structures. --- ### Continue your AEO learning - [The complete guide to Answer Engine Optimisation](/articles/what-is-aeo) — the foundational pillar covering definitions, signals, and where to start. - [The AEO Maturity Model](/articles/aeo-maturity-model) — five levels of AI search readiness, from keyword-only to programmatic authority. - [Why your B2B website isn't getting cited in AI search](/articles/b2b-ai-search-visibility) — the practical, structural fixes that move you from invisible to cited. If you'd rather skip the DIY route, here's [how we run AEO retainers](/aeo-services) for B2B teams that want to be the cited answer in their category. ### Frequently asked questions #### What is the difference between AEO and SEO? SEO optimises for search engine results pages — rankings, click-through rates, and organic traffic. AEO optimises for AI-generated answers — citations, recommendations, and brand mentions inside tools like ChatGPT, Perplexity, and Google AI Overviews. The unit of success shifts from a click to a citation. #### Does AEO replace SEO? No. AEO and SEO are complementary disciplines, not competing ones. AEO extends SEO rather than replacing it, and the foundations they share — quality content, structured data, site speed, brand authority — do double duty for both. #### Where do AEO and SEO overlap? They share high-quality authoritative content, structured data and schema markup, strong backlink profiles and brand authority, and fast well-structured websites. Investing in any of these improves both disciplines at once, which is why the shared foundations are the sensible place to start. #### Where do AEO and SEO diverge? SEO focuses on keyword rankings and SERP features. AEO focuses on how AI models understand and reference your brand as an entity. The signals are related but not identical, so a site can rank well and still go uncited. #### Should B2B teams invest in AEO or SEO first? Invest in both, starting with the foundations they share, then layering in AEO-specific work like entity definitions, citation networks, and AI-readable content structures. Treating them as a choice duplicates effort on the shared foundations while leaving the AEO-specific signals unaddressed. --- ### Article: Benefits of Transitioning to Webflow for Agencies **URL:** https://www.brandinglab.io/articles/benefits-of-webflow-for-agencies **Published:** 2026-03-10 **Read time:** 5 min read **Author:** BrandingLab, Editorial **Category:** Webflow **Key takeaways:** - Webflow gives agencies design control without the maintenance overhead of custom CMS builds. - Client handover is faster — non-technical teams can manage content confidently. - Performance and Core Web Vitals are easier to hit out of the box than on most WordPress stacks. - A reusable component library compounds margin across every future build. - Migrating an agency from WordPress to Webflow is a positioning move, not just a tooling choice. Webflow offers agencies a platform that enhances creative capabilities and streamlines team collaboration, reducing project timelines by up to 40%. ### Why Agencies Are Switching Traditional CMS platforms like WordPress require constant plugin management — exactly the [deploy-queue and maintenance tax we break down in our Webflow vs. WordPress comparison](/articles/webflow-vs-wordpress-for-branding-agencies), security patching, and developer intervention for design changes. Webflow eliminates these pain points. ### Key Benefits - **Faster delivery**: Visual development means less back-and-forth between design and development — the same logic behind [why we default to Webflow for high-converting brand sites](/articles/why-we-use-webflow-for-high-converting-brands) - **Better collaboration**: Designers and developers work in the same environment, which is also what makes a [scalable design system practical to maintain](/articles/design-system-that-scales) - **Reduced maintenance**: No plugins to update, no security patches to manage - **Higher margins**: Less development time means more profitable projects ### The Client Experience Clients get a CMS they can actually use — no developer needed for content updates. This reduces ongoing support requests and increases client satisfaction. ### Making the Switch If the first project is replatforming an existing client, our [five-step WordPress to Webflow migration process](/articles/wordpress-to-webflow-migration-for-b2b) is the cleanest way to do it without losing SEO equity. Start with a single project to build team confidence. Most agencies find that after one successful Webflow project, the team never wants to go back. ### Continue reading - [Why We Use Webflow to Build High-Converting Brands](/articles/why-we-use-webflow-for-high-converting-brands) — The stack philosophy behind every brand site we ship — design fidelity, no deploy queue, AI-readable HTML. - [Webflow vs. WordPress for Branding Agencies](/articles/webflow-vs-wordpress-for-branding-agencies) — An honest 2026 verdict across velocity, brand fidelity, AEO and 3-year total cost of ownership. - [WordPress to Webflow Migration](/articles/wordpress-to-webflow-migration-for-b2b) — A structured five-step process for moving off WordPress without losing SEO equity. - [Building a Design System That Actually Scales](/articles/design-system-that-scales) — Variables, reusable components and conventions that hold up as your team and site grow. ### Frequently asked questions #### Why are agencies switching from WordPress to Webflow? Traditional CMS platforms require constant plugin management, security patching, and developer intervention for design changes. Webflow removes those recurring costs, which is why agencies report reducing project timelines by up to 40% after switching. #### What are the main benefits of Webflow for an agency? Four things: faster delivery, because visual development cuts the back-and-forth between design and development; better collaboration, because designers and developers work in the same environment; reduced maintenance, with no plugins to update or security patches to manage; and higher margins, because less development time means more profitable projects. #### Does Webflow improve the client experience after handover? Yes. Clients get a CMS they can actually use, with no developer needed for content updates. That reduces ongoing support requests and increases client satisfaction, and it removes the agency from the critical path on routine content changes. #### How should an agency start with Webflow? Start with a single project to build team confidence rather than converting the whole book of business at once. Most agencies find that after one successful Webflow project the team does not want to go back. #### What if the first Webflow project is replatforming an existing client? Use a structured five-step migration process, which is the cleanest way to replatform without losing SEO equity. Running the first Webflow project against an existing client is a common starting point precisely because the process is defined and repeatable. --- ### Article: Building a Design System That Actually Scales With Your Team **URL:** https://www.brandinglab.io/articles/design-system-that-scales **Published:** 2026-02-28 **Read time:** 8 min read **Author:** BrandingLab, Editorial **Category:** Design **Key takeaways:** - A design system only scales if it has clear ownership and a documented update process. - Tokens (colour, spacing, type) belong in code as the single source of truth — not in Figma alone. - Components should encode constraints, not just visuals, so misuse is prevented by default. - Version your system and communicate breaking changes the way engineering teams ship libraries. - Adoption beats elegance: a smaller, well-used system always outperforms a perfect, ignored one. A scalable design system in Webflow combines defined variables, reusable components, and documented conventions enabling consistent expansion without visual incoherence. It is also the single biggest reason [Webflow has become our default for high-converting brand sites](/articles/why-we-use-webflow-for-high-converting-brands). ### What Makes a Design System Scalable? The difference between a collection of components and a true design system is documentation and conventions. Components alone don't scale — the rules governing their use do. ### Core Principles - **Variables first**: Define colours, spacing, and typography as variables before building any components — the same discipline that makes [Webflow noticeably faster than WordPress for agency teams](/articles/benefits-of-webflow-for-agencies) - **Composition over customisation**: Build complex layouts from simple, composable pieces - **Document everything**: Every component needs usage guidelines, not just visual specs ### Common Mistakes #### Over-engineering early Don't build for every possible future use case. Start with what you need now and extend as patterns emerge. #### Inconsistent naming Establish naming conventions on day one. Changing names later breaks everything. ### When you are migrating an existing site If the design system is being built as part of a replatform, the cleanest path is to define the system first and then run our [five-step WordPress to Webflow migration](/articles/wordpress-to-webflow-migration-for-b2b) against it. The full platform-level case for the move is laid out in our [Webflow vs. WordPress verdict for branding agencies](/articles/webflow-vs-wordpress-for-branding-agencies). ### The Payoff Teams with well-maintained design systems ship 3–4x faster on subsequent projects. The upfront investment pays for itself within the first quarter. ### Continue reading - [Why We Use Webflow to Build High-Converting Brands](/articles/why-we-use-webflow-for-high-converting-brands) — The stack philosophy behind every brand site we ship — design fidelity, no deploy queue, AI-readable HTML. - [Webflow vs. WordPress for Branding Agencies](/articles/webflow-vs-wordpress-for-branding-agencies) — An honest 2026 verdict across velocity, brand fidelity, AEO and 3-year total cost of ownership. - [Benefits of Transitioning to Webflow for Agencies](/articles/benefits-of-webflow-for-agencies) — How Webflow cuts agency project timelines by up to 40% and increases project margins. - [WordPress to Webflow Migration](/articles/wordpress-to-webflow-migration-for-b2b) — A structured five-step process for moving off WordPress without losing SEO equity. ### Frequently asked questions #### What makes a design system actually scale? A scalable design system combines defined variables, reusable components, and documented conventions, which together let a site expand without losing visual coherence. The difference between a component collection and a true design system is documentation and conventions — components alone do not scale, the rules governing their use do. #### Should we define variables before building components? Yes — variables first. Define colours, spacing, and typography as variables before building any components. This is the same discipline that makes Webflow noticeably faster than WordPress for agency teams, and it pairs with composition over customisation: build complex layouts from simple, composable pieces. #### What are the most common design system mistakes? The two most common are over-engineering early and inconsistent naming. Building for every possible future use case wastes effort on patterns that never emerge, so start with what you need now and extend as real patterns appear. Establish naming conventions on day one, because changing names later breaks everything downstream. #### Is a design system worth the upfront investment? Teams with well-maintained design systems ship three to four times faster on subsequent projects, so the upfront investment typically pays for itself within the first quarter. The return compounds — every project after the first draws on work already done rather than rebuilding from scratch. #### Should we build the design system before or during a replatform? Define the system first, then run the migration against it. If the design system is being built as part of a replatform, sequencing it first means the migration has a target to build toward rather than a moving one, which avoids rework on both sides. --- ### Article: Why Your Brand Matters More Than Ever in the Age of AI **URL:** https://www.brandinglab.io/articles/why-brand-matters-in-age-of-ai **Published:** 2026-02-15 **Read time:** 6 min read **Author:** BrandingLab, Editorial **Category:** Strategy **Key takeaways:** - AI compresses categories — buyers see fewer options, so brand recognition decides who makes the shortlist. - A strong brand acts as a retrieval signal: distinctive language and entities are easier for LLMs to attribute. - Generic positioning is now actively dangerous — AI engines blend you into the average answer. - Invest in proprietary frameworks, named POVs and consistent visual identity across surfaces. - Brand and AEO are complementary: brand makes you worth citing, AEO makes you findable to cite. As AI-generated content becomes increasingly prevalent, authentic brand identity emerges as a critical competitive advantage. It also changes how buyers find you in the first place — see our [introduction to Answer Engine Optimisation](/articles/what-is-aeo) for the discoverability side of the same shift. ### The Homogenisation Problem AI tools produce competent but generic content. When every company uses the same tools to generate the same types of content, the output converges. Distinctiveness disappears. ### Why Brand Cuts Through Strong brands have something AI can't replicate: - **Lived experience**: Real stories from real projects with real outcomes - **Point of view**: Opinionated positions built from years of expertise - **Visual identity**: A distinctive look that's immediately recognisable — protected at scale by a [design system built to actually scale](/articles/design-system-that-scales) - **Voice**: A way of communicating that reflects genuine personality ### The Strategic Implication Companies that invest in brand — in having something genuine to say and a distinctive way of saying it — will stand out more, not less, as AI-generated content floods every channel. ### How this shows up in execution A distinctive brand only compounds if the website it lives on can keep up. That means a platform that protects design fidelity and lets marketing ship without a developer in the loop — the case we make in [why we use Webflow for high-converting brands](/articles/why-we-use-webflow-for-high-converting-brands) — and a process that puts brand foundations before pixels, walked through in [what a B2B website rebuild actually looks like](/articles/b2b-website-rebuild-process). ### What To Do Now Audit your content. If you removed your logo and brand colours, would anyone know it was yours? If not, that's your starting point. ### Continue reading - [What a B2B Website Rebuild Actually Looks Like](/articles/b2b-website-rebuild-process) — The 6 phases, the 8–12 week timeline, and what your team needs to commit from kickoff to launch. - [Why We Use Webflow to Build High-Converting Brands](/articles/why-we-use-webflow-for-high-converting-brands) — The stack philosophy behind every brand site we ship — design fidelity, no deploy queue, AI-readable HTML. - [What Is AEO? The Complete Guide to Answer Engine Optimisation](/articles/what-is-aeo) — Definition of AEO, why it matters for B2B, and how to execute it across your site. Brand is the unlock; AEO is how you compound it inside AI engines. See [our AEO services for B2B](/aeo-services) for the operational layer that turns brand authority into citation share. ### Frequently asked questions #### Why does brand matter more as AI content becomes common? AI tools produce competent but generic content, and when every company uses the same tools to generate the same content, the output converges and distinctiveness disappears. Brand is what survives that homogenisation, so its relative value rises as the volume of generated content grows. #### What can a strong brand do that AI cannot replicate? Four things: lived experience, meaning real stories from real projects with real outcomes; point of view, meaning opinionated positions built from years of expertise; visual identity, meaning a distinctive look that is immediately recognisable; and voice, meaning a way of communicating that reflects genuine personality. None of these can be generated from a prompt. #### Does investing in brand still pay off when competitors publish more content? Yes, and increasingly so. Companies that invest in brand — in having something genuine to say and a distinctive way of saying it — will stand out more, not less, as AI-generated content floods every channel. The scarce thing is distinctiveness, not output. #### How does brand connect to being found in AI search? Brand affects discoverability as well as preference, because AI engines assemble answers from entities they can identify and trust. A clearly defined, consistently described brand is easier for a model to recognise and cite, so brand work and AI visibility work are the same programme viewed from two angles. #### What does brand investment look like in execution? A distinctive brand only compounds if the website it lives on can keep up — a platform that protects design fidelity and lets marketing ship without a developer in the loop, and a process that establishes brand foundations before pixels. Brand strategy that never reaches the site does not change what buyers or AI engines see. --- ## FAQ **URL:** https://www.brandinglab.io/faq ### AEO & AI Search **Q: What is AEO?** A: AEO stands for Answer Engine Optimisation: structuring your site so AI answer engines like ChatGPT, Claude, Perplexity, and Google AI Overviews can find, understand, and cite it. It relies on clear entity definitions, question-shaped headings, direct answers, and structured data (JSON-LD). The goal is being the cited source, not just ranking on a results page. **Q: Why does AEO matter for B2B brands?** A: B2B buyers now run early vendor research through AI assistants before they ever visit a website. If your brand isn't surfaced in those answers, you're absent from the shortlist stage of the buying journey. AEO makes sure your positioning, proof, and differentiators are represented accurately when a buyer asks AI about your category. **Q: Why is AEO becoming more important than traditional SEO?** A: Traditional SEO wins a link on a results page; AEO wins the answer itself. As more research happens inside ChatGPT, Perplexity, and AI Overviews, a growing share of high-intent queries never produce a click at all. The honest trade-off: AEO traffic volumes are smaller than classic organic, but intent is far higher. **Q: How is AEO different from traditional SEO?** A: SEO optimises for ranking signals — keywords, backlinks, crawl health. AEO optimises for machine comprehension: schema markup, explicit entity definitions, sourced claims, and content written as question and answer. Same technical foundations, different output target. **Q: Can AEO and SEO work together?** A: Yes, and they should. Fast load times, clean architecture, and genuinely useful content help both. AEO work — structured data, FAQ schema, entity markup, quotable answer blocks — layers on top of an existing SEO strategy rather than replacing it. **Q: Can you optimize an existing site for AI search, or do we need a rebuild?** A: Most sites can be optimised in place by adding schema markup, restructuring content into answerable sections, and fixing crawlability for AI user agents. A rebuild is only worth it when the current platform is slow, renders content client-side only, or fights you on markup. I'll tell you which case you're in before you spend anything; that is exactly what an AEO audit answers. **Q: Does my choice of tech stack affect my AI Search (AEO) rankings?** A: Yes, significantly. AI crawlers reward clean semantic HTML, fast responses, and content present in the initial server response — many of them execute little or no JavaScript. A client-rendered single-page app can look complete in a browser and be effectively empty to an AI crawler. **Q: How does your tech stack affect AI Search (AEO) rankings?** A: Webflow outputs clean, semantic HTML, and for React builds I prerender every route so crawlers receive full HTML rather than an empty shell. Cursor lets me hand-tune metadata, JSON-LD, and heading structure at the code level. The result is a site AI engines can parse and quote without guesswork. **Q: How do you track if my brand is being 'recommended' by AI engines?** A: I measure your presence in AI answers for your 20 most important buyer-intent queries across ChatGPT, Claude, Perplexity and Google AI Overviews, running each query three times because answers vary. I record whether your brand appears, how it is described and which page is cited. Check it monthly by hand — or have BrandingLab monitor it weekly. It is sampling, not a rank tracker: trends matter more than any single result. **Q: What are the benefits of an 'AI-First' development workflow?** A: Speed and consistency. Tools like Cursor and Lovable remove the repetitive coding labour, so more of your budget goes to strategy, content, and design judgment. It doesn't replace expertise — a senior operator still makes every architectural and editorial decision. ### Webflow **Q: What is Webflow?** A: Webflow is a professional visual web development platform for building fully custom, production-ready sites without hand-writing front-end code. Unlike template builders, it outputs clean semantic HTML, CSS, and JavaScript. That combination of design freedom and clean markup is why it performs well for both SEO and AEO. **Q: What are Webflow Sites?** A: Webflow Sites is Webflow's hosting and publishing tier. Site plans run from Starter through Enterprise and include custom domains, SSL, form handling, global CDN delivery, and automatic backups. Your plan level determines CMS item limits, bandwidth, and collaboration features. **Q: What does a typical Webflow project look like?** A: Four phases: discovery and strategy, design, build, launch. Discovery defines goals, audience, and messaging; design produces high-fidelity screens; build covers Webflow development, CMS architecture, and performance work; launch covers QA, redirects, and handover. Most projects run four to twelve weeks depending on page count and content readiness. **Q: Why hire a Webflow agency instead of building in-house?** A: Platform depth. A specialist brings established design systems, CMS patterns, interaction techniques, and performance practices that take an in-house team months to accumulate. The trade-off is dependency on an external partner, which is why I hand over full ownership and documentation at launch. **Q: Can Webflow handle CMS content and blogs?** A: Yes. Webflow's native CMS supports structured collections, reference fields, rich text, and dynamic filtering, with full visual control over templates. Blogs, case study libraries, and resource hubs all work without plugins. Very large content operations — tens of thousands of items — are where it starts to strain. **Q: Can you migrate our existing site to Webflow?** A: Yes. Migrations from WordPress, HubSpot, Squarespace, and custom platforms are routine work: content transfer, CMS structuring, design refinement, and full redirect mapping. Redirect mapping is the part that protects your existing search equity, so it gets treated as a deliverable rather than an afterthought. **Q: Do we get full ownership of the Webflow site?** A: Yes. The site lives in your own Webflow account, and you can edit content, manage CMS items, change design, and publish independently. You also get documentation and a walkthrough so your team is confident managing it without me. **Q: Is Webflow suitable for enterprise websites?** A: Yes. Webflow Enterprise is SOC 2 Type II compliant and offers a 99.99% uptime SLA, role-based publishing, custom code hosting, and AWS-backed infrastructure with Fastly CDN. Brands including Zendesk, Dell, Dropbox, and Upwork run marketing sites on it. **Q: How does Webflow compare to WordPress?** A: Webflow is one hosted platform combining builder, CMS, and hosting; WordPress assembles the same result from hosting, themes, and plugins. Webflow is faster by default and has no plugin conflicts or patch cycle to manage. WordPress still wins when you need a very specific plugin ecosystem or deep custom server-side logic. **Q: How do you handle complex features that standard site builders can't do?** A: I drop out of the builder and into code. Custom JavaScript, API integrations, and serverless backend logic get written in Cursor and wired into the visual front end, or the feature moves to a Lovable app if it needs a database and authentication. Naming the limit early is part of the scoping conversation. **Q: Am I tied to a specific platform once the project is done?** A: No. Everything is built on open, industry-standard foundations, and code-based projects export to GitHub. You own your assets outright, and any competent developer or agency can take over. Webflow projects stay Webflow projects — that's a platform commitment, but a portable, well-documented one. ### Lovable & AI-Native Development **Q: What is Lovable?** A: Lovable is an AI-powered full-stack development platform that builds production web applications from natural-language instructions. It generates React, TypeScript, Tailwind CSS, and Vite projects, with a built-in backend covering database, authentication, storage, and serverless functions. The output is standard code, not a proprietary format. **Q: What can you build with Lovable?** A: Web applications: SaaS dashboards, client portals, internal tools, booking systems, and data-driven platforms. It's strongest where you need authentication, a database, API integrations, or real-time features without standing up a traditional full-stack team. Pure marketing sites are usually better served by Webflow. **Q: Why does BrandingLab offer Lovable development?** A: Clients regularly need more than a marketing site — a portal, a calculator, an internal dashboard. Lovable lets me deliver those in weeks with the same design and brand discipline as a Webflow build. It also gives me full control over prerendering and JSON-LD, which matters for AEO. **Q: How does Lovable differ from Webflow?** A: Webflow is a visual development platform for content-led marketing websites; Lovable is an AI-native code platform for full-stack web applications that need databases, authentication and custom logic. Webflow gives non-technical editors direct control; Lovable gives developers full control of the codebase. BrandingLab often pairs both — Webflow for the public marketing site, Lovable for client portals, MVPs and internal tools. **Q: Is Lovable code production-ready?** A: Yes. Lovable produces clean, standard React and TypeScript using mainstream libraries, exportable to GitHub and deployable on standard cloud infrastructure. Like any generated code, it still needs a senior review pass for security, data access rules, prerendering and performance before launch — that review is part of every build I ship. ### Tech Stack Philosophy **Q: Why do you use a mix of tools like Webflow, Lovable, and Cursor?** A: Because each one wins a different job. Webflow handles visual, content-led marketing sites; Lovable handles applications that need a database and authentication; Cursor handles bespoke logic and technical SEO or AEO work that neither platform exposes. Choosing per project means you don't pay for workarounds forced by a single-tool agency. **Q: Why does Branding Lab use a mix of tools like Webflow, Lovable, and Cursor?** A: Tool-agnostic by design. Most agencies sell whatever platform they already know, which quietly shapes the solution around their skills instead of your goals. Working across Webflow, Lovable, and Cursor — with trusted partner specialists on delivery — lets the business requirement pick the stack. ### Brand & Strategy **Q: What is the difference between a 'Visual Identity' and a 'Brand Strategy'?** A: A visual identity is what people see: logo, colour, typography, layout system. A brand strategy is what they understand and believe: positioning, audience, messaging hierarchy, and tone of voice. Strategy comes first, because visuals with no argument behind them look good and convert poorly. **Q: We already have a logo; can you help us with the strategy and voice?** A: Yes. Existing marks and assets can be kept and extended into a full system — positioning, messaging, tone of voice, and digital brand guidelines. If the existing identity actively works against the positioning we land on, I'll say so rather than build around it. ### Engagement & Process **Q: How long does the branding and build process take?** A: A full brand identity plus custom site build typically takes four to eight weeks. Site-only projects are usually shorter, complex application work longer. The pace depends less on build time than on how quickly content, approvals, and stakeholder feedback come back. **Q: What ongoing support do you offer after launch?** A: Retainer support covering content updates, design iterations, new page builds, performance monitoring, and AEO tracking. Most clients continue monthly to keep improving the site as positioning evolves. There's no lock-in — the site is yours whether you retain me or not. **Q: Does the choice of platform affect my brand's look and feel?** A: No. The brand system defines typography, colour, motion, and tone; the platform just renders it. Whether a visitor is on a Webflow marketing site or a Lovable application, the experience stays consistent by design. ### Other common questions **Q: What does an AEO audit include?** A: An AEO audit reviews structured data, content authority signals, entity clarity, citation potential, and crawlability for AI user agents. It also tests how ChatGPT, Claude, Perplexity, and Google AI Overviews currently describe your brand. You get a prioritised action plan rather than a raw score. --- ## Position on AEO Most B2B sites are invisible to AI search engines because they're built as JavaScript-rendered SPAs with no schema, no semantic HTML, and no content architected for AI citation. We fix this with five interventions: 1. **Static structured data** — Organization, Service, Article, FAQPage, BreadcrumbList, AggregateRating schemas in the initial HTML payload (not injected by JavaScript). 2. **Prerendering or SSR** — Real semantic HTML in the body of every page so AI crawlers can read content without executing JavaScript. 3. **Content rewriting for AI citation** — Clear definitions in the first paragraph, TL;DR boxes, comparison tables, numbered steps, FAQ sections at the bottom, quotable statistics with sources. 4. **AI-native discovery files** — llms.txt and llms-full.txt for AI crawlers that prefer markdown over HTML. 5. **Entity authority** — Wikidata entries, third-party citations on high-authority publications, AggregateRating from Clutch/G2 reviews to strengthen the brand entity in AI knowledge graphs. The goal isn't to rank in Google. The goal is to be the source AI engines cite when someone asks ChatGPT, Perplexity, or Claude a question a prospect would ask. --- ## Contact - Project enquiry: https://www.brandinglab.io/contact - Free AEO Audit: https://www.brandinglab.io/audit - Clutch: https://clutch.co/profile/brandinglab - LinkedIn: https://www.linkedin.com/company/brandinglab