Case study
Seacoast Stories
They already had the hard parts. We made them work together.
Seacoast Stories had audience trust, a deep podcast archive, successful events, strong social reach, sponsors, local relationships and real community interest. The opportunity wasn't more activity. It was getting the pieces to work together.
The sign
People were asking for merch. There was nowhere to buy it. Audience demand had no path through the business.
The decision
Build one owned system connecting content, discovery, events, community, audience capture and partnership interest.
- 01
Existing assets
- 02
Disconnected paths
- 03
Connected system
- 04
Observable actions and commercial conversations
What Smithline uncovered and applied
The value existed. It needed a framework for discovery.
The archive, events and audience existed across separate places. The opportunity was not simply a better-looking website: it was a clearer structure connecting the brand, its stories, people and places, with useful next steps for visitors.
Smithline applied an integrated SEO, AEO and GEO framework across content architecture, metadata, internal linking and discovery paths. Individual episode pages and town-level organization made the archive easier to explore, while connected journeys led toward events, audience signup and partnership inquiries.
- SEO · Search engine optimization
- Make existing content easier to find through search. Episode pages, metadata, town-level organization and internal links gave the archive a clearer discovery structure.
- AEO · Answer engine optimization
- Make information easier to understand and use in answers. Clearer brand context and content organization were intended to help answer engines identify what a page is about and why it is relevant.
- GEO · Generative engine optimization
- Make the brand easier for generative search systems to interpret and potentially reference. The same connected content and metadata help describe the relationship between the brand, its stories and its local context.
These disciplines overlap. The distinction is what each is designed to support: being found in search, being understood as an answer, and being referenced in a generated response. Adding structure and tags is implementation evidence, not proof that an engine has used them.
The figures below measure post-launch site activity, not the isolated effect of any single intervention. They do not independently measure AI citations, answer-engine visibility or financial ROI.
How the different outcomes can be measured
SEO: Search Console can track indexed pages, search queries, impressions and clicks. This case study reports site-recorded Google referrals, a separate measure.
AEO: Dated examples can establish whether answer surfaces use the brand’s information accurately and attribute it to a source.
GEO: Repeated, dated checks of relevant questions can track brand mentions, citations and accuracy across selected generative search tools.
No historical answer-engine or AI-citation baseline is presented here. Those outcomes have not been quantified in this case study.
What changed
Make existing interest easier to act on.
The podcast archive, events, social audience, community interest and partner relationships existed across separate places. Visitors had limited clear ways to move from discovery to participation. On-site behavior and inquiries were harder to observe.
What we connected
Archive to discovery
A searchable site with individual episode pages turned the archive into something people could find and explore.
Listeners to an owned audience
Visitors could join an audience the business controls, not just follow on third-party feeds.
Interest to event signups
Dedicated event paths made interest and signups visible.
Fans to contributors
Contribution and nomination paths turned interest into recorded participation.
Sponsors to a front door
A clear inquiry route gave sponsors and partners an obvious way in.
Activity to evidence
Cookie-free, bot-filtered analytics made on-site behavior visible.
Evidence through September 15, 2026
What happened when the pieces connected.
Recorded site activity from July 16 through the September 15, 2026 snapshot, across 62 calendar days including the partial final day.
14,563
recorded pageviews
~235
recorded pageviews per day
1,326
Community pageviews
1,102
Events pageviews
831
site-reported Google Search referrals
826
pageviews on the best day
Before the connected site
Before the new site, Seacoast Stories averaged about 10 pageviews a day. The prior website recorded 1.9K pageviews over about 6.5 months. The new site's daily average covers 62 calendar days.
What the client reports
Regular sold-out events, podcast subscriber growth beyond natural growth, and more partnership inquiries.
Troy Farkas, Founder, Seacoast Stories. Reported September 4, 2026.
Source: September 15, 2026 site analytics export. Pre- and post-launch analytics use different systems, so the comparison is directional. Pageviews are not unique visitors, Google referrals are not Search Console clicks, and these figures do not establish sales or revenue.
From the founder
"Smithline came into our lives, and it completely changed the game."
What this could mean for your business
You may not need to start from scratch.
Your version may not be a podcast. It may be customer requests with no clear owner, a manual process holding the business together, an audience you reach but cannot bring closer, or valuable work you keep giving away.
The Opportunity Map identifies what is happening, what is worth pursuing, and what to do first. It is a paid, standalone engagement.
Three-page case study with the original website activity figures through September 15, 2026, including the partial final day.