Home πŸ” Site Audit & Technical SEO

πŸ” Site Audit & Technical SEO

Camilo Aponte
By Camilo Aponte
β€’ 4 articles

πŸ” Diagnosing Crawled Not Indexed Pages

πŸ“Œ What "Crawled – Not Indexed" Means When a page is crawled but not indexed, Google has visited the page but decided not to add it to its search results. The page is not blocked and Google can reach it. Google simply did not consider it worth storing yet. This status is common, especially on new sites, large sites, and sites with many similar pages. It does not always mean something is broken, but it is a signal that the page can be improved. ❓ Is There a One-Click Tool for a Single URL? Customers often ask whether they can give Search Atlas a URL and get back a list of exactly what to fix. There is no single tool that does this, because Google does not tell anyone the exact reason a page was left out of its index. Instead, you can combine two tools to find the most likely causes: - Site Audit checks the technical side: tags, redirects, links, speed, and crawl settings. - Content Genius checks the content side: depth, relevance, and how your page compares with pages that already rank. Used together, they cover the two main reasons pages stay out of the index: technical signals and content quality. βœ… Step 1: Confirm the Page Status Before you change anything, confirm the page is really crawled but not indexed. 1. Open Google Search Console and go to the URL Inspection tool. 2. Paste the full URL of the page. 3. Check the status. Look for wording such as "Crawled – currently not indexed." 4. Make sure you are testing the exact version of the URL you want indexed (with or without www, http or https, trailing slash). If the status says something different, such as "Discovered – currently not indexed" or "Excluded by noindex tag," the fix will be different. The steps below still help with most cases. πŸ› οΈ Step 2: Check Technical Issues with Site Audit Run a Site Audit on the domain, or open your most recent audit if you already have one. Then look for issues that affect the affected URLs. - Noindex tags: a noindex directive tells Google to leave the page out. Remove it if the page should be indexed. - Canonical tags: if the canonical points to a different URL, Google may treat your page as a duplicate and skip it. - Robots.txt rules: make sure the page and its important resources are not blocked. - Status codes and redirects: pages should return a normal 200 status. Redirect chains, 404s, and soft errors can cause problems. - Duplicate or missing titles and meta descriptions: many pages with the same titles look like duplicates. - Orphan or weakly linked pages: pages with few or no internal links look unimportant to Google. - Page speed and loading problems: very slow pages or pages that fail to load content can be skipped. - Sitemap issues: confirm the page is listed in your XML sitemap and the sitemap has no errors. Fix the issues that apply to your page first. These are usually the quickest wins. ✍️ Step 3: Improve Content Quality with Content Genius If Site Audit shows no technical problems, content quality is the most likely cause. Google often skips pages that are thin, repetitive, or similar to pages already in its index. 1. Open Content Genius and enter the main keyword or topic the page targets. 2. Compare your page with the top-ranking results for that topic. 3. Look for gaps such as missing subtopics, short sections, or questions that you do not answer. 4. Expand the page with useful, original information. Add examples, data, images, or clear step-by-step guidance where it makes sense. 5. Improve headings so the structure is easy to scan. 6. Avoid copying text from other pages, including your own. Each page should have a clear, unique purpose. Aim for a page that gives readers something they cannot get from the other pages on your site or from the top results. πŸ”— Step 4: Strengthen Internal Links Internal links tell Google which pages matter. For each page that is not indexed: - Add links to it from related, already indexed pages. - Use clear, descriptive link text instead of "click here." - Link from high-traffic pages, such as your homepage, category pages, or popular articles, when it is relevant. - Make sure the page is not more than a few clicks from your homepage. πŸš€ Step 5: Request Indexing and Wait 1. After you make your fixes, go back to URL Inspection in Google Search Console. 2. Click Request Indexing for the updated page. 3. Run a new Site Audit to confirm the technical issues are resolved. 4. Wait one to four weeks, then check the status again. Requesting indexing does not guarantee results. Google decides based on the quality and value of the page, so the improvements in Steps 2 to 4 matter most. πŸ’‘ Common Causes at a Glance - Thin content: use Content Genius to add depth and unique value. - Duplicate or near-duplicate pages: merge them or set the correct canonical tag. - Noindex or wrong canonical: find it in Site Audit and correct it. - Weak internal linking: add links from relevant pages. - New site or low authority: keep publishing quality content and be patient. - Too many low-value pages: remove or consolidate pages that do not serve a purpose. πŸ™‹ Frequently Asked Questions Can I hand Search Atlas a URL and get a full fix list? Not in a single step. Use Site Audit to find technical issues and Content Genius to improve content. Together they point you to the most likely fixes. How long does indexing take after I fix a page? It can take from a few days to several weeks. Larger or newer sites often wait longer. Should I delete pages that stay unindexed? Only if they have no real purpose. Otherwise, improve them, add internal links, or combine them with a stronger page. Does a crawled-not-indexed page hurt my whole site? A few of them are normal. A large share of low-quality pages can reduce how Google views your site overall, so it is worth cleaning them up. πŸ’¬ 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 instantly connected with a member of our team.

Last updated on Oct 29, 2026

πŸ” Site Audit REST API Contract and Quotas

πŸ“Œ What this article covers This guide explains the Site Audit REST API for authenticated Search Atlas accounts: starting a crawl, how crawl_budget is applied, where to read status, settings, and URL issues, and how to recrawl a domain without changing settings or creating an OTTO project. It also covers permissions, quota, archive slots, rate limits, response fields, and subdomains. πŸš€ Start an audit Use POST /api/v2/site-audit/ with your account API credentials. Send the domain you manage and the crawl settings for that run, including crawl_budget. The call creates or updates the Site Audit record only. It does not create an OTTO project, and you should not send OTTO project fields. A successful response returns the audit identifier, the domain, the accepted crawl budget, and a status such as queued or running. Save the identifier. You need it for later reads and for a recrawl. πŸ“Š Crawl budget on a new domain Yes. If you send crawl_budget: 25 for a new domain, that audit is capped at 25 URLs. The crawler does not expand to the whole site. A higher plan allowance does not override the value you sent. - The cap applies only when 25 is within your remaining crawl quota. - If fewer than 25 URLs of quota remain, the crawl stops when quota runs out. - Pages that cannot be fetched still count toward the attempt limit for that run. - Changing the budget later requires a new request. It does not rewrite a crawl already in progress. βš™οΈ Read status, settings, and issues After POST returns an audit id, use the authenticated GET reads for that same audit. The current paths are listed in the in-product API reference so you always call the version tied to your account. Use three separate reads: - Status returns state, progress, URLs crawled, and whether the run is queued, running, complete, or failed. - Settings returns the saved domain settings, including the crawl budget used for the latest run. - URL issues returns the issue list for crawled URLs, including severity and the affected URL. Do not poll a different domain or another account's audit id. Empty issues usually mean the crawl has not finished or no issues were found. πŸ› οΈ Recrawl without changing settings To recrawl an existing domain, call POST /api/v2/site-audit/ again for that same domain and audit. Omit settings you do not want to change, and do not send any OTTO project payload. Saved settings, including the existing crawl budget, stay as they are. 1. Confirm the domain already has a Site Audit id. 2. Send the recrawl request with that domain and audit id only. 3. Do not include new settings or an OTTO project. 4. Poll the status read until the run completes, then refresh URL issues. A recrawl replaces the previous run's results for that domain. It does not merge two crawls and it does not create a second project. πŸ’‘ Permissions, quotas, slots, and rate limits The API is for authenticated use by your Search Atlas account. It is not an open public endpoint. You may audit domains you add to your own account. Do not share tokens or audit a site you do not manage. - Quota: each URL attempted in a crawl counts toward your Site Audit crawl quota. Quota is consumed when the crawl runs, not when you merely save settings. - Archive and slots: a finished audit uses an active slot until you archive it. Archiving frees the slot. It does not refund URLs already crawled and it does not erase saved settings used for a later recrawl. - Rate limits: keep one active crawl per domain. Parallel crawls of the same domain can be rejected. If a call is throttled or quota is exhausted, wait and retry later instead of launching another crawl. πŸ” Response fields and subdomain isolation Create and status responses include the audit id, domain, status, accepted crawl budget, and URLs crawled. The settings read returns the stored settings. The issues read returns one entry per affected URL with the issue type and severity. Extra fields may appear as the API evolves. Ignore fields you do not use. A root domain and its subdomains are isolated. An audit of example.com does not crawl blog.example.com unless that host is included in the crawl scope or audited as its own domain. Each host has its own status, settings, issues, and quota usage. Archiving one host does not archive the other. πŸ’¬ If you still need help 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.

Last updated on Oct 29, 2026

πŸ—ΊοΈ Fix Sitemap Indexing Stuck at Zero

πŸ“Œ Why the indexed count stays at zero A healthy sitemap and a clean robots.txt only tell Google which pages exist and that crawling is allowed. They do not guarantee that pages are indexed. The indexed number in Google Search Console can stay at zero while Google is still discovering URLs, or when pages are crawled but excluded. Search Atlas cannot force Google to index a site. You can confirm the setup, resubmit the sitemap, and request indexing for important URLs. Google decides what to crawl and when. βœ… Check the basics first - Confirm the sitemap URL returns a valid XML file and lists the live page URLs you expect, including https and the correct domain. - Open robots.txt and confirm it does not block those URLs or the sitemap itself. - Spot-check a few listed URLs. Each should return a normal page, not a redirect loop, login wall, or error. - On those pages, confirm there is no noindex tag and that the canonical URL matches the URL in the sitemap. - In Search Atlas, open the correct site project and confirm Google Search Console is connected to the same property that owns the sitemap. A domain property and a URL-prefix property can show different data. πŸ”„ Resubmit the sitemap in Search Console 1. In Google Search Console, select the property that matches the live site. 2. Open Sitemaps in the left menu. 3. If the sitemap is already listed, note the status. Success with zero indexed pages is common on new or recently changed sites. 4. Enter the sitemap path, such as sitemap.xml, in the add field and choose Submit. Submitting again asks Google to read the file again. It is not an instant recrawl of every URL. 5. Return to Search Atlas and refresh or re-sync Search Console data for that project so the platform shows the latest status. πŸš€ Request indexing for key pages 1. In Google Search Console, open URL inspection at the top of the page. 2. Paste one important URL from the sitemap, such as the homepage or a priority service page, and press Enter. 3. Review the result. Look for blocked by robots.txt, excluded by noindex, duplicate or alternate page, or crawled but not indexed. 4. If the URL is eligible and the Request indexing button is available, select it. Use this for a small set of priority URLs, not every URL in the sitemap. 5. Repeat for a few representative URLs. If those are excluded, fix the reported reason before requesting more. πŸ› οΈ Use Search Atlas to find blockers - Run or open the latest Site Audit for the project and filter for indexability issues, blocked pages, canonical conflicts, and redirect or status-code problems. - Compare audit URLs with the sitemap. Pages missing from the audit, or listed with errors, will not move the indexed count. - If OTTO recommendations are waiting, review indexation and technical items and apply only the fixes you intend to publish. - After fixes go live, resubmit the sitemap and request indexing again for the corrected URLs. ⏳ What to expect after a recrawl request Google may take days or longer to recrawl and update the indexed count. Zero does not always mean the sitemap was rejected. Check the Pages or indexing report for discovered, crawled, and excluded URLs. A rising discovered count with a low indexed count usually means quality, duplication, or canonical selection, not a broken sitemap. If the sitemap status is an error, the property is wrong, or URL inspection shows a sitewide block after you have corrected the pages, 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.

Last updated on Oct 29, 2026

πŸ” OTTO Slots Versus Site Auditor Quota

πŸ“Œ Why slots and quota are different Search Atlas uses more than one limit. Team seats control how many people can log in. OTTO slots control how many websites can use OTTO. Site Auditor quota controls how many websites you can add to Site Auditor. Unused seats or OTTO slots do not raise your Site Auditor quota. πŸ” Why an 11th site is blocked If you have 13 seats or OTTO slots but only 10 sites in the list, that extra capacity is not Site Auditor room. The message that you do not have quota is checking the Site Auditor project limit, not your seat count. A plan can allow 13 people or 13 OTTO sites while Site Auditor still stops at 10 projects. The visible list can also be shorter than the quota already in use: - Archived, paused, or removed projects may still count until they are fully deleted. - A site that did not finish setup can still hold a project. - A search box or status filter may hide some items. - Projects owned in the same plan by another workspace or teammate still count. βš™οΈ How to check each limit 1. Open your plan or usage area and note three numbers separately: team seats, OTTO website slots, and Site Auditor projects. 2. Open Site Auditor and clear search or status filters so hidden projects appear. 3. Count every project, including paused or incomplete ones. 4. Open OTTO and count only sites with OTTO turned on. That count uses OTTO slots, not auditor quota. 5. Compare the Site Auditor count with the Site Auditor limit before you add another website. πŸš€ How to free a Site Auditor spot 1. In Site Auditor, open a project you no longer need. 2. Delete the project completely. Pausing it may not free quota. 3. Refresh the project list and confirm the count dropped. 4. Add the new website again. To keep more than your current Site Auditor limit, upgrade the Site Auditor or plan quota. Adding seats or OTTO slots alone will not remove this error. πŸ’‘ If the numbers still do not match Note the three limits you see and how many projects remain after filters are cleared. 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.

Last updated on Oct 29, 2026