You fixed the problem in your store, but Site Health still lists it. Annoying, but there's nearly always a simple explanation. Work through these in order.
1. You haven't rescanned yet
Your report shows what we found in your last scan. It doesn't update by itself when you change your store. Click Re-crawl in Site Health, or Rescan on the Projects page. A Quick scan is enough to check a handful of fixes.
2. The change isn't live
Some platforms keep your edit as a draft until you click Publish, and some theme editors save changes to a preview theme. Open the page in a private browser window and make sure you can actually see the change.
3. Your store is showing an older copy
Caching plugins and services like Cloudflare can keep serving the old version of a page for a while. Clear the cache, then rescan.
4. You fixed some pages, not all of them
Most issues sit on lots of pages at once. Fixing alt text on one product doesn't fix it on the other 200. Open the full issues list to see exactly which pages still have the problem.
Quick tips remind you what a good fix looks like for that type of issue.
Each row is one page that still has the problem, with the issue named at the top and the page's title and address underneath.
Fix opens the tool that can write the fix for that page. Use CSV to download the whole list and work through it in a spreadsheet.
5. Your theme or an app is adding it back
Some problems don't live in your products at all. Two main headings on every page, a noindex tag from an SEO app, or scripts from apps you stopped using all come from your theme or an app's settings. Fixing one product won't help, because the theme puts the problem back on every page. Fix it once at the source and it clears everywhere.
6. You're comparing different scan types
A Full scan reads more pages and runs extra checks than a Quick scan, so it can find issues the Quick scan never saw. When you compare progress, compare scans of the same type. How to compare scans shows where to find them.
Still there after all six? Send us a message with the page address and the name of the issue, and we'll check it for you.
