Why a podcast SEO quality checklist needs dated evidence

What to take away

The Google Search Central page Verify Googlebot (developers.google.com/crawling/docs/crawlers-fetchers/verifying-googlebot) is the check that separates real crawler traffic from spoofed hits in your logs.
Feed ownership sits with Apple Podcasts show claiming, so confirm who controls the show before anyone edits episode metadata.
Mobile page quality affects both discovery and paid landing pages, per the Google Ads Help page About mobile-friendly sites (support.google.com/google-ads/answer/7323900).
Review the checklist monthly and retire items that no longer map to a measurable outcome.

Start with evidence, not opinions

A quality checklist fails when it records opinions. Each line should name a source, an owner and the date it was checked. If a colleague says the feed was fixed, the checklist needs the date of the fix and the page or feed URL it applies to.

Vague vs Dated Checklist Entry

Vague entry

Wording: Improve metadata
Source: None named
Date: Not recorded
Sign-off: Cannot be closed

Dated evidence entry

Wording: Episode title checked
Source: Feed URL named
Date: Date checked recorded
Sign-off: Someone can sign off

A vague entry such as improve metadata can never be closed. Rewrite it as one episode title checked against the feed on a stated date, so someone can sign it off.

Copy this row format into your checklist.

Item	Source	Owner	Date checked	Sign-off
Episode 42 title matches feed title	Apple Podcasts show page	Show producer	4 March 2025	Producer initials

That discipline matters because podcast discovery spans several platforms, each with its own rules. A change that helps one directory can leave another untouched.

Confirm crawler traffic before you act

Server logs fill up with bots. Some are genuine, some are not. Before you change anything in response to a crawl spike, confirm the request came from Google using the verification steps on the Google Search Central page Verify Googlebot, at verifying Googlebot requests.

Verify Crawler Before Acting

Crawl spike in server logs?

Yes

Verify request came from Google

Exclude from diagnostics

Keep the raw log extract beside the finding, so a later reviewer can repeat the check without guessing.

A verified hit shows a Google IP and reverse DNS that forwards to Google. Example log line:

66.249.66.1 - - [04/Mar/2025:10:14:22 +0000] "GET /episode/42 HTTP/1.1" 200 512 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

Reverse DNS: crawl-66-249-66-1.googlebot.com.

A spoofed hit uses the same user agent from an IP that does not resolve to Google. Example:

203.0.113.45 - - [04/Mar/2025:10:15:01 +0000] "GET /episode/42 HTTP/1.1" 200 512 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

Reverse DNS: no Googlebot hostname.

Unverified traffic should be excluded from your diagnostics. Otherwise you risk rebuilding a page that was never the problem. Log the verification date next to the finding.

Checklist: ownership and access

Named owner for the podcast feed, the website and the analytics account.
Show claimed and controllable on Apple Podcasts through the claiming process for creators, with the date of the claim recorded.
Admin access held by at least two people, so a departure does not lock the team out.
Password and two-factor changes logged with dates.
Written handover note when ownership moves between people or agencies.
For UK distribution, list BBC Sounds and Global Player alongside Apple Podcasts and Spotify.

Record the date of each handover, not only the name of the new holder.

For UK shows, Ofcom's Broadcasting Code covers broadcast radio, so treat podcast-only episodes under platform rules instead.

Ownership gaps surface late, usually during a migration. Our podcast SEO team roles and data sources guide maps who should hold each account.

Checklist: pages and episode entries

Each episode page should carry a unique title, a short summary and a link to the audio file. Test how the page behaves on a phone, since mobile rendering shapes how listeners reach and read it, as set out in the Google Ads Help page About mobile-friendly sites, at mobile optimisation guidance.

Episode title matches the feed title exactly.
Show notes present and readable without JavaScript.
Publish date visible on the page.
Canonical tag points to the intended URL.
Internal link from the episode page to the show index.
For UK paid landing pages, the CAP Code requires ad claims to be substantiated, so keep the evidence beside the page.

Two episodes covering the same topic should not compete for the same phrase in the title tag. Separate them in the summary instead.

For example, a show with 120 episodes and no canonical tags will scatter signals across duplicate URLS. Fixing that is a checklist item, not a project.

Checklist: measurement and reporting

One agreed definition of a download or play, written down.
Dashboard refreshed on a fixed day each month.
Source of each metric named beside the number.
Any change in tracking tooling flagged in the report.
Report circulated to the owner named at the top of this checklist.

Name the tool behind each number, and the date the export was taken.

For the wider sequence of checks, fixes and reviews, see our podcast SEO operations and delivery guide.

Common questions

How often should the checklist be run?

Run the ownership and access items monthly, and the page items whenever an episode publishes. A full pass each quarter is enough for most shows.

Who should own the checklist?

A single named owner, with a deputy for cover. Shared ownership without a name is how items stay open for months.

What if a check cannot be verified?

Mark it unresolved and set a review date. An unverified item is more useful than a false pass, because it shows where evidence is missing.