Foundations
Part of Podcast SEO foundations explained for England marketers
Choosing a podcast SEO model by data access: retainer, audit, project or in-house
Compare the four podcast SEO business models by the data each needs: Search Console, Apple Podcasts Connect, Spotify for Creators and host analytics, how access is granted, and how to score the options.
A podcast SEO service can be bought as a monthly retainer, a one-off project, a productised audit or an in-house hire. Which one works depends on one practical question: what data can the person doing the work see? This guide is for show owners choosing an approach and for providers deciding what to sell.
Start with what each model needs to see
Podcast SEO work uses two kinds of data. Search and site data show how episodes appear in search results and how the website performs. Listening data shows downloads, plays and where listeners come from. The first is usually easy to share. The second sits in accounts that only the show owner controls.
The retainer covers continuing support; a project is a one-off audit or migration; a productised audit uses a repeatable report with a fixed scope; and in-house delivery places the work with salaried staff. Each needs different access, as the next section sets out.
Four Podcast SEO Business Models
Retainer
- Recurring revenue
- Highest
- Data burden
- Highest
- Scope
- Monthly work
- Cost per hour
- High
Project
- Recurring revenue
- Lumpy
- Data burden
- Lower
- Scope
- Defined audit
- Cost per hour
- Medium
Productised audit
- Recurring revenue
- Volume-based
- Data burden
- Templates
- Scope
- Standard report
- Cost per hour
- Low
In-house
- Recurring revenue
- Salary
- Data burden
- Tooling
- Scope
- Salaried delivery
- Cost per hour
- Cheapest at volume
A project has less even cash flow because it is paid for once. In-house work may cost less per hour at high volume, but the organisation carries its tooling and compliance costs.
The data sources behind podcast SEO, by name
| Data | Source | Who controls it | Used for |
|---|---|---|---|
| Search queries, clicks and indexing | Google Search Console | Site owner | Which episode pages appear for which searches |
| Site traffic and conversions | Google Analytics 4 | Site owner | Visits to show notes, sign-ups, referrals |
| Crawl health and page speed | A site crawler such as Screaming Frog, plus Search Console reports | Anyone, for a public site | Broken links, missing titles, slow pages |
| Downloads and listeners by episode | Your podcast host's dashboard, such as Acast, Libsyn, Buzzsprout or Podbean | Show owner | Whether search work lifts listening |
| Plays and follower data | Apple Podcasts Connect and Spotify for Creators | Show owner | Platform-level discovery and retention |
| UK audience context | RAJAR and Ofcom's Communications Market Reports | Public | Background on listening habits |
Search Console and crawl data can be inspected from outside. Downloads, plays and advertising delivery usually need access to the show owner's host or platform account. RAJAR and Ofcom data give context but not figures for one show.
How access is requested and agreed
Agree access in the contract before work begins. For site data, ask the owner to add the provider as a user in Search Console and GA4 with the lowest permission that does the job, such as a restricted user in Search Console or a viewer in GA4. Record the date and who can remove access.
For listening data, ask whether the host offers a team login or a read-only role. If not, agree a monthly export of downloads by episode and source, in the same format each time. Apple Podcasts Connect and Spotify for Creators show analytics to account holders, so exports or screenshots may be the only route.
At the end of the engagement, remove the provider's access and keep a copy of the reports in your own storage.
What the access check rules out
- Retainer.Needs search, site and listening data every month. Without listening data the provider cannot show whether the work helped, which makes renewal difficult.
- Productised audit.Can run on search and crawl data alone, with a before-and-after crawl as its evidence. It does not depend on monthly access to downloads.
- Project.Needs access for the length of the job, then ends. Define the scope so it cannot grow into unpriced support.
- In-house.The show owns every account, so access is simple, but the team needs time and skills to read the data.
If a provider promises growth in downloads but asks for no access to the host, ask how they will measure it. Compare any quote against the pricing models and the commercial contract terms before agreeing.
Score the options against your own situation
Score each model from one to five against weighted criteria, multiplying each score by its weight. The weights below are a starting point. Change them to match your priorities, and show the scores to whoever approves the budget.
| Criterion | Weight | What a high score requires |
|---|---|---|
| Recurring revenue | 3 | Multi-month commitments with clear renewal triggers |
| Data access | 3 | First-party analytics plus platform reporting |
| Compliance load | 2 | Consent, tracking notices and ad claim checks in place |
| Delivery cost | 2 | Templates, tooling and trained staff already available |
| Client education | 1 | Buyers who understand podcast discovery timelines |
| Scalability | 2 | Repeatable process that survives staff changes |
Scoring Rubric for Model Selection
- Recurring revenueweight 3
- Data accessweight 3
- Compliance loadweight 2
- Delivery costweight 2
- Client educationweight 1
- Scalabilityweight 2
For example, a show owner who cannot share host data would score a retainer low on data access and an audit higher. A provider with templates and no legal support would score the audit well on delivery cost and compliance load. A small difference between totals proves nothing, so treat the scores as a way to discuss the choice, not an answer.
Check claims and compliance before you sign
Any statement about results, such as download growth or ranking, needs evidence. Check the ASA AdviceOnline library for misleading advertising and the evidence behind objective claims.
Tracking on your site must meet the Privacy and Electronic Communications Regulations, and the ICO's guidance on online tracking applies where personal data is processed under the UK GDPR. If paid promotion is part of a promise about downloads, check budget pacing and measurement rather than treating ad spend as proof of an outcome.
For audience context, Ofcom's Communications Market Reports and RAJAR's MIDAS survey cover UK audio listening. Neither replaces account access for one show's downloads.
Rules to carry forward
Start with access, not with a model borrowed from another provider. Record what the show can share and which source supports each measure. Vendor source checks help trace figures to their origins, and public search tools support checks of search demand, crawl health and page speed.
Define the work before comparing income. Separate a one-off audit from ongoing support, and record what each includes. If renewal risk rises because progress cannot be shown, rethink the reporting promise. If tooling costs overtake salary savings, revisit the assumptions.
Keep the weights and assumptions visible, and rescore at least annually and when platform reporting or tracking rules change. See podcast SEO foundations for market context and the review methodology for how to test a provider's claims.
