📌 Overview
Two questions come up often in support: why the schema markup in OTTO looks out of date, and why Atlas Agent credits can drop quickly when the Agent returns incorrect HTML. This article explains both issues and shows you what to do about them.
🔍 What Are FOUND Schemas?
OTTO groups schema markup (structured data) into two kinds:
- FOUND schemas: markup OTTO detected already on your live page the last time it scanned it.
- Suggested or generated schemas: markup OTTO recommends or creates for you.
FOUND schemas are a snapshot of what OTTO saw during its last scan. They are not a live view of your page, so they can fall behind if your site has changed since then.
🕰️ Why Your FOUND Schemas May Look Outdated
- The page changed after the last scan: prices, business details, authors, dates, or product info were updated on your site, but OTTO has not rescanned the page yet.
- Old markup is still on your site: a theme, plugin, or old template may still output the previous schema. OTTO reports it correctly, but the source is outdated.
- Caching: your website, CDN, or caching plugin may be serving an older version of the page to the scanner.
- Duplicate schemas: several plugins or templates may each add their own markup, so old and new versions appear together.
🔄 How to Refresh Outdated FOUND Schemas
- Open the page in your browser and confirm the information on the live page is correct and current.
- Update the schema at its source. This might be your CMS, an SEO or schema plugin, or your theme settings. If the old markup is still published on your site, OTTO will keep finding it.
- Clear your site cache, plugin cache, and CDN cache so the updated page is served.
- In OTTO, use Manual reprocess on the project (it recrawls the whole site, then refreshes OTTO, and can only be run again after 24 hours). You can also use Recrawl Site in Site Audit. Recrawl Page on a single page only re-fetches that page. It does not refresh FOUND schemas.
- Wait until the site recrawl and OTTO processing finish, then review the FOUND schemas again. They will match the markup from that crawl. A single-page Recrawl Page does not update them.
- Check the page with a public structured data testing tool to confirm that only one correct version of each schema type appears.
Tip: If you have many pages, start with your most important ones, such as your homepage, top service or product pages, and contact page.
✅ How to Keep Schemas Current
- Rescan key pages after any major change to business details, pricing, or page content.
- Use one source of schema markup per page. Disable overlapping plugins or templates that output the same data.
- Clear caches whenever you publish important updates.
- Review your schemas on a regular schedule, such as once a month.
⚡ Why Atlas Agent Credits Can Run Out Quickly
Atlas Agent uses credits whenever it processes a request. If the Agent returns HTML that is incorrect or unusable and you retry several times, each attempt can use credits. A few repeated retries can use up a large part of your balance.
Common causes of incorrect HTML output include:
- Broad or unclear requests that cover too many things at once.
- Missing context, such as the page URL, the exact section to change, or the format you need.
- Very large pages or complex layouts that are difficult to edit in one pass.
- Conflicting instructions across several retries in the same conversation.
🛡️ How to Protect Your Credits
- Work on one page or one section per request instead of asking for a full-site change.
- Be specific. State the page, the element to edit, the output you expect, and any limits, such as keeping existing classes or IDs.
- Review the first result before retrying. If it is wrong, change your instruction instead of sending the same request again.
- Stop after two failed attempts. Repeating the same request rarely fixes the problem and keeps using credits.
- Start a fresh request if a conversation has become long or confusing, so earlier mistakes do not carry over.
- Test generated HTML on a staging page or in a preview before publishing it.
📅 Understanding Credit Balances and Quota Resets
- Plan quota: the usage included with your subscription refreshes according to your billing cycle.
- Purchased credits: extra credits you buy are added to your balance and are used as you make requests.
You can check your current balance, plan details, and billing cycle date in your account and billing settings inside the platform. If your balance looks wrong after a purchase or a reset date, note the date and the approximate number of credits you expected.
💬 What to Do If Credits Were Used on Failed Results
If Atlas Agent repeatedly returned incorrect HTML and used most of your credits, our team can look into what happened. Have this information ready:
- The date and time of the affected requests.
- The page URL or project you were working on.
- A short description of what you asked for and what the Agent returned.
- Your credit balance before and after, if you know 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.
📝 Quick Summary
- FOUND schemas show what OTTO detected at its last scan, not a live view of your page.
- Fix outdated markup at its source, clear caches, then rescan.
- Use specific, single-page requests with Atlas Agent, and stop after two failed attempts.
- Check your billing settings for your balance and reset date, and use the chat widget if something looks wrong.