Recent projects · Media & entertainment
Build or Break

Build or Break

SEO and GEO inside a finished Webflow site

From other people's shows to the first result for its host's podcast

We made a finished Webflow site readable to search and gave every episode a transcript page, which Perplexity quoted in a check on October 1.

118%

site-wide rise in citations inside AI answers after launch

As of Sep 17, 2026 · Google Search Console

Last updated

The numbers

What changed for Build or Break

5 of 6

episode pages are the first Google result for their guest's name with “build or break”

As of Oct 1, 2026 · Checked on Google

3.8

average Google position of the show's hub page

As of Sep 17, 2026 · Google Search Console

17 days from Aug 29, 12 after launch

11.0%

of the people who see the hub click it, against 1.7% across the rest of the site

As of Sep 17, 2026 · Google Search Console

17 days from Aug 29, 12 after launch

5.9

average Google position of the episode pages, up from 8.1

As of Sep 22, 2026 · Google Search Console

Aug 28–Sep 9 against Sep 10–Sep 22, 2026

Where it started

The problem

Searching for the host's podcast used to return other people's shows.

Build or Break is a weekly interview podcast that launched on September 3, 2026 with three episodes. We were hired in late August to make it findable. The site was already built in Webflow, the design was finished and the launch date was fixed, so the job was everything search needs that a finished design does not give you.

At our audit on August 29 the show's name appeared zero times as text on its own page. It existed in the logo and in images, all with empty alt text. The page title was “Podcast Episodes”. There was no sitemap, no canonical tags, no share image and no structured data, and 42 article URLs from an old WordPress site returned errors.

A search for the host's podcast mostly returned other shows he had guested on. A page that never states its own subject in text gives a search engine nothing to match.

Before and after

What it looked like, and what it looks like now

The hub's title on Google

Before

Podcast Episodes

At the audit, August 29, 2026.

After

Build or Break | A Podcast Hosted By Daniel Lubetzky

Live on October 1, 2026.

A search for “daniel lubetzky podcast”

Before

Other people's shows

August 29, 2026, with Build or Break nowhere on the page.

After

The show's own hub, first

October 1, 2026, above Spotify and Apple Podcasts.

SEO and GEO inside a finished Webflow site

What we did

01 · Inside the finished design

  • The name in real text

    The show's name and the host in text a crawler can read, the logo labelled, and a title that says what the page is.

  • Titles, canonicals and a sitemap

    A title and description written for each page, self-referencing canonicals, share tags and a live sitemap, without touching the design.

  • The brand domains

    buildorbreak.com, www.buildorbreak.com and buildorbreakpod.com all 301 to the show's hub.

02 · A page per episode

  • Transcript pages

    A Webflow template with the guest's name in the title, a summary, 14 to 25 timestamped chapters, the guest's bio, the trailer, every platform link and the full transcript: 11,000 to 16,000 words of searchable text a page. Six are live.

  • Chapter titles written to be quoted

    Each chapter title names the idea discussed, so an answer engine can cite the exact moment, and ChatGPT did.

03 · A weekly pipeline

  • Built from the transcript

    From episode four on, each page is built from the transcript the team drops into a shared tracker, with its platform links fetched for it, and staged through Webflow's API as a draft.

  • Checked on every drop

    Publishing touches the one episode, never the whole site, and then checks the title, description, sitemap and hub. On September 15 it caught a dead video button about an hour after the page went up.

  • Reports to the team

    Search reports at week one and week three, and a ChatGPT citation sweep on September 9.

Timeline

  1. Audit: the name nowhere in text, no sitemap, 42 dead URLs.

  2. Launch, with three episode pages.

  3. ChatGPT cites an episode page by the chapter title we wrote.

  4. The weekly pipeline's first live run catches a dead video button.

  5. Search Console results published.

  6. Six episode pages live. Checked on Google and in AI answers.

Results

The results

Every result carries the date it was true and where it came from, so you can check it.

  • Site-wide, citations inside AI answers rose 118% after launch. The podcast pages drew roughly a quarter of all the times Google's AI answers cited the site, from four pages out of thirty-two.

    Sep 17, 2026 · Google Search Console

  • The hub page we reworked sits at an average Google position of 3.8, and 11.0% of the people who see it click through, against 1.7% across the rest of the site.

    Sep 17, 2026 · Google Search Console

  • On the show's own name the hub is the first result, at position 1.1, and more than a third of the people who see it click it.

    Sep 17, 2026 · Google Search Console

  • The hub takes 49% of every click the site receives, 54% counting the three launch episode pages.

    Sep 17, 2026 · Google Search Console

  • The episode pages moved from an average position of 8.1 to 5.9, and their clicks rose 38%, comparing Aug 28–Sep 9 with Sep 10–Sep 22.

    Sep 22, 2026 · Google Search Console

  • “build or break podcast” returns the hub as the first result, above YouTube, Facebook and Bloomberg.

    Oct 1, 2026 · Checked on Google

  • “daniel lubetzky podcast” returns the hub first, above Spotify and Apple Podcasts. On Aug 29 the same search returned other people's shows.

    Oct 1, 2026 · Checked on Google

  • Five of the six episode pages are the first result for their guest's name with “build or break”: Kevin O'Leary, Chris Paul, Kendra Scott, Andrew Yang and Steven Bartlett, whose page got there about two days after it went live.

    Oct 1, 2026 · Checked on Google

Seen in AI answers

When people ask AI about Build or Break

Each of these is one run on one date. Answers vary between runs, so we call them checks, not rankings.

PerplexitySingle run · Oct 1, 2026

Asked

“On the Build or Break podcast, what did Kevin O'Leary say about the valley of death?”

Answered from the episode and cited the Kevin O'Leary page for all three paragraphs, quoting the transcript word for word.

“You're going to go down into the valley of death”

Google AI ModeSingle run · Oct 1, 2026

Asked

“On the Build or Break podcast, what did Kevin O'Leary say about the valley of death?”

Answered from the episode itself and cited two sources, both pages we worked on: the Kevin O'Leary episode page and the show's hub.

Google AI OverviewSingle run · Oct 1, 2026

Asked

“build or break podcast”

Walked through the first five episodes with the show's own site as the source, in wording that follows the episode titles we wrote.

“from a failed hat company to a billion-dollar brand”

ChatGPTSingle run · Sep 9, 2026

Asked about

What a guest had said about a specific idea

Cited the Kevin O'Leary page by the chapter title we wrote, and named the chapter and its timestamp. That title exists in one place on the internet.

“Every startup's valley of death and Steve Jobs' signal-vs-noise rule”

On screen

The site, at desktop and phone width

Captured from the live site on October 1, 2026.

The Build or Break podcast hub on daniellubetzky.com, the page 6AI set up for search, at desktop width
The Build or Break podcast hub on daniellubetzky.com, the page 6AI set up for search, on a phone
The show's hub on daniellubetzky.com, the page that comes first for its name.
The Build or Break Kevin O'Leary episode page that 6AI built, at desktop width
The Build or Break Kevin O'Leary episode page that 6AI built, on a phone
The Kevin O'Leary episode page, the one Perplexity and Google's AI mode answered from on October 1.
What's next

The work from here

  • The structured data for the series, the host and every episode is written and validated. It goes live when the client's team publishes it.
  • The redirect map for the old WordPress URLs is written too. Some of those dead addresses are still cited in Google's AI answers, so importing it turns that attention into visits.
  • A new episode page every week, built the same way.

Related

Want results like this?

Tell us what you sell and where, and we will show you how you come up on Google and in ChatGPT today.