This article explains why OTTO flags null values in your Page-Level Schema Markup, why fixing Review and Aggregate Rating warnings can feel like a loop, and how to clear internal link warnings tied to redirected URLs.
⚠️ Why OTTO Flags Null Review and Aggregate Rating Schema Fields
OTTO scans each page for content patterns that match known schema types. When it detects a star-rating element on the page, it interprets that element as review-related content and suggests Review and Aggregate Rating schema properties.
The warning appears when OTTO has no underlying data to populate those properties. If the page has no actual product reviews, rating values, or review counts, OTTO cannot fill the Review and Aggregate Rating fields, so they remain null and trigger the schema warning.
Why the fix loops and how to break it
The fix appears to loop because the warning is not caused by a broken setting you can toggle off. OTTO keeps detecting the star-rating element and keeps suggesting the same Review and Aggregate Rating properties, but there is no review data on the page to satisfy them. Re-running the fix re-detects the same element and re-creates the same null fields.
Here's what to do: instead of re-running the fix, choose the path below that matches your page.
How to resolve the null schema warnings
Choose the option that matches your page:
- If the page has no reviews: the null Review and Aggregate Rating values are expected. You can safely dismiss this warning or manually populate the Review and Aggregate Rating fields. The star-rating element triggers the suggestion, but with no review data available, these fields cannot be populated automatically.
- If the page should display reviews: add genuine review content to the page, such as customer reviews, a numeric rating value, and a review count. Make sure that review data is visible on the page so OTTO can detect it. Once that data exists on the page, OTTO can populate the Review and Aggregate Rating fields instead of leaving them null.
After you confirm which case applies and update the page accordingly, OTTO can resolve the Review and Aggregate Rating fields on the next crawl rather than re-flagging empty values.
Note: Other schema fields can trigger a similar Review Required state. For example, numeric fields such as an ImageObject's width and height that are flagged as strings can keep a page stuck in Review. This is a known issue tracked separately (OTTO-2193); if you encounter it, reach out to support so it can be confirmed against that fix.
🔗 Why OTTO Warns About Internal Links Pointing to Redirected URLs
OTTO flags internal links when they point to a URL that redirects to another URL. In this case, internal links still point to /collections/halloween-collection, which redirects to /collections/halloween. Relying on that redirect is what triggers the internal link warning.
How to fix the redirected internal link warnings
- Find every internal link that points to the redirecting URL,
/collections/halloween-collection. - Update each of those links to point directly to the final destination,
/collections/halloween, so they no longer rely on the redirect. - Save your changes and allow OTTO to recrawl the site.
Once the internal links point directly to /collections/halloween and OTTO recrawls the site, these internal link warnings should clear.
🎯 You now know that null Review and Aggregate Rating warnings come from a star-rating element with no review data behind it, and that internal link warnings clear once you point links directly to the final URL instead of a redirect. Update the relevant pages and links, then let OTTO recrawl to confirm the issues resolve.