Theme does not control RSS feeds, these are part of WordPress.
RSS validation tools are unable to validate
A) SRCSET tags
B) https enclosures, as it doesn’t know what https is (really dumb), and only validates if http, since stuck in 20th century
C) Weird crap invented by WordPress but not part of the normal Web standards
addons from Jetpack may generate this error, try disabling Jetpack features if using that which add to the RSS
<site xmlns="com-wordpress:feed-additions:1">116197527</site>
If using YOAST SEO, disable the feature which adds extra text to the feeds.
(( UNRELATED Note that posts/pages should ideally be built by a user and not by ‘admin’ as you should not have an ‘admin’ named user for WordPress. ))
Probably. Looks like an ‘ad blocker’ in place in your browser.
ERR_BLOCKED_BY_CLIENT will be from security/privacy software on your PC blocking optional, third-party features on the website
403 error can be from your site or IP being blocked by the ad network from loading anything … or some element on your site not being allowed to load …
A web server may return an HTTP 403 Forbidden status in response to a request from a client for a web page or it may indicate that the server can be reached and process the request but refuses to take any further action. HTTP status code 403 responses are the result of the web server being configured to deny access to the requested resource by the client.
Yes, I am well aware having managed our own servers since 1996. However *most* web hosts are requiring https for http/2 as a standard with the ‘https everywhere’ movement.
Much like Google will be warning site visitors about “site not safe” for any website with an insecure form in October. Everybody *should* be moving to https. Period. We moved all our sites to https in 2004, not just the ecom systems on sites.
Obviously anybody who can read up on the topic knows that.
My point was that somebody trying to switch on http/2 on their server as a hosting client, where the server policy is to enforce https for http/2 will have errors and perhaps generate ‘port’ errors since there will be mis-match on secure/insecure ports, much like with mod_pagespeed couple years back (2013? wow time flies!) with mixed content.
server certificate does NOT include an ID which matches the server name
For example on a Plesk/ONYX server, “Make sure that SSL support is enabled for the web site in the Hosting Settings section of the domain. HTTP/2 is supported for SSL sites only, so non-SSL sites will continue to work under HTTP /1.x. That is a restriction of nginx web server and web browsers.”
My comment was intended for the OP who might not understand what he/she is actually doing with this process.
Cheers.
You can use geo targeting with an ad management module/plugin (not part of theme); however be aware with the shortage of IPV4 IPs, the actual country/locale may be totally wrong (e.g., here in Calif when Frontier took over FIOS from Verizon, all our IP blocks were originally from Canada, so I’d go to Newegg and they would redirect me to their Canadian site every time … so the geo sniffer totally failed there … ) …. until IPv6 comes into full adoption, there will still be a lot of false locales with the wind down on IPv4.
Food for thought anyway 🙂
