Hello,
We apologize for the issue you are facing with the Recipe schema not being visible until you manually edit and save the post. This can sometimes happen due to caching issues or conflicts with other plugins or themes that may be affecting how the schema is rendered on the front end.
Here are a few steps you can take to troubleshoot this issue:
-
Clear Cache: If you are using a caching plugin, try clearing the cache to see if that resolves the issue. Sometimes, cached versions of your pages may not reflect the latest changes.
-
Check for Conflicts: Deactivate other plugins temporarily to check if there is a conflict causing the schema not to display correctly. If the schema appears after deactivating a specific plugin, that plugin may be causing the issue.
-
Theme Compatibility: Ensure that your theme is compatible with Rank Math and does not have any customizations that might interfere with schema output.
-
Schema Settings: Double-check that the Schema Module is properly configured in Rank Math settings. You can do this by navigating to Rank Math > Dashboard in your WordPress admin area and ensuring that the Schema Module is enabled.
-
Manual Save: As a temporary workaround, you can continue to manually save the posts after editing the schema until a more permanent solution is found.
If these steps do not resolve the issue, please reply to this ticket with any additional details or error messages you may be encountering, and a human agent from our support team will assist you further. Thank you for bringing this concern to our attention!
I have enabled Troubleshoot so I only have RankMath active and the default theme, the schema still does not show by default.
Hello,
Unlike the article schema, the Recipe schema needs some fields to be added to its properties.
You should fill in those and validate it using this tool:
https://search.google.com/test/rich-results
Looking forward to helping you.
I understand, but at first the schema is not found, then I try to edit it BUT I DO NOT CHANGE/ADD ANYTHING, and save the Post and then the schema is found.
Hello,
Allow us to verify this behavior with our development team.
We should get back to you shortly with some advice.
Thank you.
Hello,
This is intended behavior. We use the default values from the Settings on the frontend only for the Article schema. For other schema types, those values serve as a fallback only when the user has configured the schema on the post. We consider the schema to be configured on a post when the user has saved schema data on that post.
Even if you don’t make any modifications to the data already available, when the default values are saved, it considers that the user reviewed the data, so it adds the data to the page.
The only automated Schema type is the Article Schema, which doesn’t require you to open the post/page to save the data.
Don’t hesitate to get in touch if you have any other questions.
It doesn’t make any sense that the defaults you set for schema types other than article don’t carry through to the front-end.
I’ve been troubleshooting the same type of issue where my post type metas and titles defaults are configured and I have set what the default headline should be, but the schema doesn’t make it to the front end without first editing the post, opening the schema area and hitting save. Not even editing the schema, just seeing that it’s selected the schema type I configured by default. That’s completely confusing because I’ve not had to change any details for it to work as expected.
It’s not a logical or predictable workflow, it’s not obvious to editors which posts are working and which aren’t.
Also new posts are showing as schema off for me, even though the default has been set.
Hello,
We understand the confusion. Currently, default schema settings (other than Article) act as a fallback and aren’t applied to the front end unless the schema is explicitly saved on the post at least once. This ensures the data is reviewed and confirmed by the user.
We agree the workflow could be more intuitive, and if this is something we can improve in the future, we will be sure to let you know.
For now, manually saving the schema once per post is necessary.
Hope that helps.
If this is “intended behaviour”, what’s the logic behind it? When the recipe schema is configured with the right placeholders, why don’t you automatically apply it in the same way you automatically apply the article schema? Why the need to double check an already preconfigured and therefor approved schema?
In my 20 years of web development, when I hear “This is intended behaviour” it’s because it hasn’t been thought through, but also there is no intention to make it better.
Too bad as this means I will have to manually open, edit and save 100+ posts!
It’s completely illogical; I can’t imagine anybody expects it to work this way.
I’m pretty sure the fact that new posts are showing as “Schema: Off” too for me has to be a bug?!
Hello,
Thanks for your feedback and we truly understand your frustration.
The reason only the Article schema is applied automatically is because it doesn’t have required fields beyond what’s available globally. Other schema types, like Recipe, often have required/recommended fields that can’t be set in the global defaults. If we applied them without user confirmation, it could result in invalid or incomplete schema output – giving a bad impression to Google.
That’s why saving the schema once per post is needed — it confirms the data is complete and intentionally used.
That said, if this workflow is something we can improve in the future, we will be sure to let you know.
Don’t hesitate to get in touch with us if you have any other questions.
“If we applied them without user confirmation” > if we just open the schema and save it without editing anything, aren’t we doing just that?
At least give us some bulk edit options then. Do you know how long it takes to edit 100+ posts? And even after saving, there is no visual confirmation in the post overview table that the Recipe schema has been activated.
Hello,
Opening and saving without making changes is essentially confirming the defaults, and we understand how tedious that can be with a large number of posts.
We’ve heard your feedback on bulk editing and clearer indicators, and if this is something we can improve, we’ll let you know
Thank you.
Hello,
Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.
If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.
Thank you.
