🧭 Overview
Two common questions come up together: your dashboard still shows a large issue count even after you have fixed and deployed everything, and only some of your pages appear in Google's index. This article walks you through both situations step by step so you can confirm your fixes are recorded correctly and understand why certain pages may not be indexed yet.
📊 Why Your Dashboard Still Shows Issues After Fixing Them
The issue count on your dashboard reflects the state of your site the last time Search Atlas crawled it. Deploying fixes to your live site does not automatically update the count — the platform needs to re-crawl your pages to detect the changes.
There are three common reasons the count stays high after you have made fixes:
- No re-crawl has run yet. Your fixes are live but Search Atlas has not crawled those pages since the changes were deployed.
- Fixes were saved in the editor but not published to your live site. Changes made inside Search Atlas do not push directly to your CMS or server unless you explicitly export or publish them.
- Some issues belong to pages or issue types you have not reviewed yet. The total count includes every open issue across all pages, not only the ones you worked on.
📍 How to Locate All 1,599 Open Issues
To see exactly where your remaining issues are and confirm which ones are resolved, follow these steps:
- Go to Home from the left-hand navigation bar.
- Locate the Site Audit or Issues section on your dashboard and click View All Issues.
- Use the filters at the top of the issue list to sort by issue type, priority, or page URL. This helps you identify patterns — for example, all missing meta descriptions or all broken internal links grouped together.
- Check the Status column. Issues marked Open have not yet been confirmed as fixed by a crawl. Issues marked Fixed were detected as resolved during the most recent crawl.
- If an issue you fixed still shows as Open, trigger a manual re-crawl by going to OTTO SEO → Site Audit → Overview (Website Overview) and clicking Recrawl Site. Once the crawl completes, the status will update automatically.
After the re-crawl finishes, return to the issue list. Any issues correctly resolved on your live site will move to a Fixed status and the total count will decrease accordingly.
🗂️ Where to Find Fixes Inside Content Optimizations
If you used the Content Optimizations tool to make on-page edits, your changes are stored inside that tool and must be exported or applied to your live site separately. To review them:
- Navigate to Content Optimizations from the main menu.
- Select the page you edited.
- Review the Recommendations panel to see which suggestions were accepted, which are still pending, and which were skipped.
- If you accepted changes but did not publish them, copy the optimized content and update your live page manually, or use the export option if your integration supports it.
Changes that exist only inside Content Optimizations and have not been applied to your live site will not reduce your dashboard issue count because the crawler reads your published pages, not your drafts inside the platform.
🌐 Why Only 23 of Your 33 Pages Are Indexed
Having fewer pages indexed than you expect is a separate issue from your dashboard issue count. Google decides independently which pages to include in its index. Search Atlas can surface data that helps you diagnose the cause, but the indexing decision itself belongs to Google.
Common reasons pages are not indexed include:
- Pages are too new. Google may not have crawled them yet. New pages can take days to several weeks to appear in the index.
- Crawl budget limitations. On smaller or newer sites, Google may not crawl every page on every visit.
- Noindex tags or directives. A
noindexmeta tag or anX-Robots-TagHTTP header tells Google explicitly not to index the page. - Blocked in robots.txt. If your
robots.txtfile disallows Googlebot from crawling certain paths, those pages will not be indexed. - Thin or duplicate content. Google may choose not to index pages it considers low-quality, near-duplicate, or lacking original value.
- Pages not included in your sitemap. If your XML sitemap is missing URLs, Google is less likely to discover them quickly.
🔧 Steps to Troubleshoot Missing Indexed Pages
- Check Google Search Console. Open GSC and go to Pages under the Indexing section. Look for the Not indexed tab. GSC will show you exactly why each page was excluded — for example, Crawled – currently not indexed, Excluded by noindex tag, or Blocked by robots.txt.
- Audit your noindex settings. In Search Atlas, run a crawl and filter your issue list for noindex tags. Confirm that the 10 missing pages do not have an accidental noindex directive applied.
- Review your robots.txt file. Check that the paths for your missing pages are not blocked. You can use Google's robots.txt Tester inside GSC to verify access for Googlebot.
- Submit your sitemap. In GSC, go to Sitemaps and confirm your XML sitemap is submitted and has no errors. Make sure all 33 pages are listed in the sitemap.
- Request indexing for specific pages. In GSC, use the URL Inspection tool, enter the page URL, and click Request Indexing. This signals to Google that the page is ready to be crawled and considered for inclusion.
- Improve page quality. If Google has crawled the page but chosen not to index it, review the content for thin text, duplicate sections, or missing structured information. Use Search Atlas Content Optimizations to strengthen the page before requesting re-indexing.
⏱️ How Long Does Re-Indexing Take?
After you request indexing through GSC, Google typically processes the request within a few days for most sites, though it can take up to a few weeks in some cases. There is no guaranteed timeline. Continue monitoring the Pages report in GSC weekly to track progress. Once a page is indexed, it will move from the Not indexed list to the All submitted pages or Indexed view.
💬 Need More Help?
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.