I’ve seen this with many WordPress initiatives (and shoppers) through the years so I assumed it was price a public thread. If you interlink a publish/web page that has embedding enabled, the iframe supply will affix /embed/ URL suffix:
<iframe class="wp-embedded-content" sandbox="allow-scripts" safety="restricted" fashion="place: absolute; clip: rect(1px, 1px, 1px, 1px);" title="Instance" src="https://instance.com/weblog/publish/embed#?secret=12345#?secret=12345" data-secret="12345" width="500" top="282" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
Nonetheless this tends to make Google GSC go a bit loopy as a result of their bots will attempt to crawl the iframes. WordPress does already embrace the noindex meta tag on these generated sub-pages:
<meta title="robots" content material="noindex, observe, max-image-preview:giant" />
WordPress additionally features a canonical tag:
<hyperlink rel="canonical" href="https://instance.com/weblog/publish" />
Nonetheless, for search engines like google and yahoo like Google they nonetheless assume you need the content material crawled due to the iframe present on a public web page… leading to tons of crawl errors in GSC. However as a result of the rel flag is not supported on iframes, there does not appear to be any straightforward option to keep away from this battle?
TLDR this appears to be extra of a Google downside than a WordPress downside, however I discover it unusual that the /embed/ web page has the very same content material because the canonical model… so what’s the objective of getting each?
