You generated schema for every page, then ran a new crawl and OTTO is suggesting schema for many pages again. This is a common question, and in most cases you are not repeating work. This article explains why it happens, how to confirm nothing is duplicated, and how to build a before-and-after comparison of your crawls.
🤔 Why Schema Suggestions Can Reappear
Each crawl is a fresh scan of your site. OTTO compares what it finds on your live pages against its recommendations. Suggestions can come back for several reasons:
- Schema was generated but not deployed. Generating schema creates the markup, but it only counts once it is live on the page. If it was not published or deployed, the crawl will not find it.
- The crawl did not detect the deployed markup. Caching, a CDN, or a page builder plugin can delay updated code from reaching the crawler.
- New or changed URLs. New pages, redirected pages, or URLs with different parameters or trailing slashes may be treated as new pages that need schema.
- Different schema types. OTTO may suggest an additional type, such as FAQ, Breadcrumb, or Product, on a page that already has a basic type like Article or Organization.
- Page content changed. If a page changed significantly, the earlier schema may no longer match its content, so a new suggestion appears.
- Site-wide changes. A theme update, migration, or plugin change can remove or override schema that was previously live.
✅ How to Confirm You Are Not Duplicating Work
Spot-check a few pages from the new suggestion list before generating anything again.
- Pick 3 to 5 pages that OTTO is suggesting schema for again.
- Open each page in your browser, right-click, and choose View Page Source. Search for application/ld+json. If you see your schema, it is live.
- Paste the page URL into Google's Rich Results Test or the Schema Markup Validator. This shows exactly which schema types the page currently exposes.
- Compare the result with OTTO's suggestion. If the same schema type is already live, the suggestion may be out of date and you can wait for the next crawl to refresh.
- If the schema is missing, it was likely not deployed, or something on your site removed it. Re-deploy it rather than generating a new version.
Tip: Avoid adding a second copy of the same schema type to a page. Duplicate markup can cause validation warnings.
📊 Building a Before and After Crawl Inventory
A simple inventory shows what changed between crawls and confirms which suggestions are new. If you can export your OTTO schema or page lists from the platform, use that. If not, a manual snapshot works well.
Before your next crawl:
- Record the date of your last crawl.
- Make a list of all pages where you generated and deployed schema. Include the URL, schema type, and deployment date.
- Note the total number of pages with schema suggestions at that time.
After the crawl finishes:
- Make a second list of pages OTTO now flags for schema, with the URL and suggested type.
- Put both lists in a spreadsheet and use a filter or lookup to find URLs that appear in both.
- Sort the results into three groups: Already handled (same URL, same type, already live), Needs re-deployment (schema not found on the live page), and Genuinely new (new URLs or new schema types).
Only the second and third groups need action. This usually shrinks a long suggestion list to a short to-do list.
🛠️ Steps to Take When Suggestions Look Wrong
- Wait for caching to clear. If you deployed recently, allow time for your site cache or CDN to refresh, then run another crawl.
- Clear your cache. Purge your site, plugin, and CDN caches so the crawler sees your latest code.
- Check your URLs. Make sure the URLs OTTO crawls match the ones you deployed to, including the www or non-www version, HTTP or HTTPS, and trailing slashes.
- Look for conflicts. Some SEO plugins or themes add their own schema. Check that nothing overrides or removes the markup.
- Re-deploy if needed. If schema is missing from the live page, deploy it again, then re-crawl to confirm.
💡 Best Practices to Prevent Confusion
- Keep a simple log of when schema was generated and deployed for each page.
- Verify a few pages with a validator after each deployment.
- Run a new crawl after major site changes, not before them.
- Review suggestions by page group, such as blog posts, product pages, and service pages, instead of all at once.
- Take a snapshot of your suggestion counts before each crawl so you can compare.
💬 Need More Help?
If suggestions still look wrong after these checks, such as schema that is confirmed live but still flagged, send us a few example URLs so we can look into it.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.