Has anyone had issues with Yoast hitting IP for the schema markup instead of the

Has anyone had issues with Yoast hitting IP for the schema markup instead of the relative URL? It’s trying to hit one of our server’s EC2 instances (AWS) — which is a private IP that leads nowhere unless you’re on our VPN. Hence, schema isn’t actually working at all. Are there any fixes for this?


Source

2 comments

  1. This sounds like your site url is configured wrong… this should be set in your site’s settings, not be dependent on how you open a URL, which it looks like it is, at which point Yoast can save them wrong to the indexable table.

    I’d make sure that when you’re hitting the wrong URL, like the IP instead of the domain name, you’re always redirected to the correct URL. Once that’s fixed, install the Yoast Test Helper, and in its settings, hit the “Reset indexables” button. The site will then give you a notice to reindex, do that, and you should be good.

    Sorry, that’s a bit of work, but sounds like it’s necessary.

  2. Why? Haven’t you assigned an EIP to the EC2 instance with a public DNS?
    Are you using the Bitnami WordPress AMI from AWS marketplace or did you set up WP yourself?

Leave a comment

Your email address will not be published.