PodView, a podcast website builder, sent out a marketing email pushing their platform as an alternative to self-hosting on WordPress. Fair enough, that’s a normal pitch. But buried in their site is a free tool called the Podcast Discoverability Report, which promises to score your show “across SEO, AI-readiness, structured data, and RSS quality” and tell you exactly what’s stopping ChatGPT, Claude, and Perplexity from citing you.
We ran it. The RSS half of the report worked exactly as advertised. The website half did not, and what it did instead is worth a closer look.
The RSS Feed Section: This Part Actually Works
We run our own SEO and AI-visibility tracking already, built specifically around how our shows actually get cited and found, so a generic third-party scorecard isn’t something we need to make decisions. But when a vendor’s marketing email lands in your inbox pushing their platform as better than what you’ve already built, it’s worth checking their own tools before dismissing the pitch. So we did.
We pointed the tool at our RSS feed and it came back with a real, itemized 10/10:
- Show title, description, cover art, category, language, author all present
- Stable show GUID
- Every episode has audio, a GUID, a duration
- Enclosures declare a media type
- Feed loads in 123ms, served over HTTPS, reasonable size
- Social links detected: Facebook, Instagram, Threads, X, YouTube
That’s a legitimate feed audit. No complaints here, and it’s genuinely useful if you’ve never validated your feed against podcasting best practices before.
The Website Section: This Part Doesn’t
Here’s where it gets interesting. The report also tries to crawl your show’s website and score it on SEO tags, structured data, AI visibility, social presence, and infrastructure.
Our first run pointed at an old domain we’d recently migrated away from. Every subsection came back the same way: “Couldn’t inspect the linked website,” “Couldn’t reach the website to check its meta tags,” “Couldn’t reach the show’s website to check structured data,” and so on down the list. Reasonable, actually. We’d forgotten to update our RSS.com custom website field after a domain migration, so the crawler was hitting a stale URL. Fair miss on our part, and it explained the failure.
We fixed the RSS.com field, pointed it at our current domain, a site we knew for a fact was live and working, and ran the report again.
This time, every website subsection displayed a green “Looks good” badge: Website, SEO & sharing tags, Structured data, AI visibility, Social presence, Infrastructure & DNS. All six. Overall score, 10.0/10.
We looked closer. The notes underneath each of those “Looks good” badges were identical, word for word, to the first run: “Couldn’t inspect the linked website to assess branding.” “Couldn’t reach the website to check its meta tags.” “Couldn’t reach the show’s website to check structured data.” “Couldn’t reach the show’s website to check AI visibility.” “No website to check for social links.” Every check had still failed to reach our site. The only thing that changed between runs was that this time the tool displayed a green passing badge over each failure instead of leaving it unstyled.
And sitting above all of it, exactly as before, was the same summary label: “Generic / unbranded.”
Green Badges Over Failed Checks
Here’s the part that actually matters. This wasn’t a case of the tool having an honest excuse on one run and an unexplained warning on the next. On both runs, across both domains, every single website check failed to reach our site. The only difference is that on the second run, PodView’s own report displayed those six failures as “Looks good,” with the same green success icon it uses for a check that actually passed.
A tool that tells you “Couldn’t reach the website to check structured data” and then marks Structured Data as “Looks good” isn’t reporting a result, it’s papering over a failure. Anyone glancing at the summary, six green badges and a 10/10, would reasonably assume their site got a clean bill of health. It didn’t get checked at all.
Sitting on top of that is the “Generic / unbranded” badge, unexplained on either run. So we opened dev tools and looked at the markup rendering it:
<span class="inline-flex items-center gap-1 rounded-full bg-pw-warning/10 px-2.5 py-0.5 text-xs font-medium text-pw-warning">Generic / unbranded</span>
bg-pw-warning. A warning-state style class, the same one you’d expect on any other caution badge in the app. Nothing about that class name or its placement suggests it was generated from an actual analysis of our site’s design, copy, or branding, because the notes directly beneath it say plainly that no such analysis happened.
Underneath the whole website section, still claiming a 10/10 built on checks that never ran, sits this line:
“Your website’s in great shape. Host it with PodView for a fast, discoverable home, built to be found by search and AI, so you can keep growing your community.”
Which is a strange thing to say about a site the tool never actually reached.
Why This Matters Beyond Us
We’re not writing this because a free tool got our branding wrong. We’re writing this because a report that marks six failed checks as “Looks good” and then tacks on an unexplained “Generic / unbranded” warning is actively misleading, not just incomplete. A podcaster who’s put real work into their brand could see six green checkmarks, a 10/10 score, and a “generic/unbranded” tag all on the same screen and reasonably assume the tool found something specific. It didn’t find anything. It never reached the site.
That’s the actual issue. Not that a crawler sometimes fails (that happens), but that the failure gets dressed up as a pass, and a warning label gets tacked on regardless of what the crawl actually returned.
The Takeaway
If you run your show through a free “grading” tool from a company that also sells you the fix, don’t trust a green badge at face value, read the note underneath it. A “Looks good” over a “Couldn’t reach the website” isn’t a finding, it’s a UI choice that makes a broken check look like a passed one.
In our case, the RSS audit was solid and we’d genuinely recommend it for a quick feed health check. The website section never once completed a real check on either domain we tried, marked every one of those failures “Looks good” anyway, and topped it off with an unexplained warning tag calling our brand generic.
We reached out to PodView on August 27, 2026 for a response and will update accordingly below if we receive a response.
