If we didn’t put this logic in the plugin, we would have many more PowerPress users complaining that their podcasts do not appear in google search like other podcasts appear in google search. PowerPress in this situation is stuck between a rock and a hard place, either we do what Google requires or we don’t. Google’s basically decide that since no one is using this meta tag today they can now use it for their purpose for identifying a podcast homepage when crawling a website. When we spoke with Google engineers about this they asked us “what does our use of a tag that has otherwise not used by anyone in many years impact?”, we did not have an answer. When google first launched podcasting and released this documentation our tests lead us to have to do add the code in PowerPress to deal with this.
If you want to be found on Google podcasts and treated as a podcast in google search you have to have one feed link per page, and this indicates the “homepage” for your podcast. If you want to podcast, we assume you want to be found on Google Search and Google Podcasts. The solution we put in PowerPress is a compromise to decide what is best for what the goals a podcaster is trying to achieve. The homepage cannot have another element on it.
Keep in mind if you do not do this, Google will not associate your homepage with your podcast which can have negative consequences if you wanted your podcast in Google search results. If you read this thread, this has to do with Google, not what I want or think is acceptable. Why are you messing with site RSS feeds? The appropriate fix is for you to rewrite your code to not remove the feeds by default – not to make users add some random code to a config file, that may or may not work, and which is not documented anywhere in the official docs. I want the appropriate RSS feeds in the headers for each page type: which is what WordPress and every other CMS in the world does out of the box. I don’t want a podcast RSS feed anywhere on my site. The podcast is just one thing that runs through my site’s pages, and the feed is for the audio files, not the web pages. To be honest I’m really struggling to understand why you think it’s acceptable, let alone desirable, for your plugin to strip sites of RSS feed tags, and then provide an undocumented ‘solution’ via an addition to a config file where users are forced to opt out rather than opt in. That didn’t work, but defining it as a string did for some reason: define('POWERPRESS_NO_REMOVE_WP_HEAD', 'true')
0 kommentar(er)
