--- title: "Discovered, currently not indexed: check every page" description: "Find every page Google knows about but has not crawled, with a live check of each one, and see whether the hold-up is the page, your server or your links." canonical: "https://seoskill.dev/features/discovered-currently-not-indexed" language: "en" --- # Discovered, currently not indexed See every page Google knows about but has not crawled yet. Your agent reads Google's reason for each one and checks what the page does now, so you can tell a broken or unwanted URL from a good page Google has not got to. Run it in a terminal, then sign in with Google. Or run it on your machine Installs the CLI, signs you in and adds the skill to your agents. Site crawls and Bing data run this way, on your own machine. A crawl fetches many pages, and Bing blocks our hosted server. ## What discovered, currently not indexed means Discovered, currently not indexed is a reason in Search Console's Page indexing report. Google found the URL, through a link or your sitemap, and has not crawled it yet. Google's [Page indexing report help](https://support.google.com/webmasters/answer/7440203) says that typically Google wanted to crawl the URL but expected it to overload the site, so it rescheduled the crawl. That is also why the last crawl date is empty. Google has not read the page, so rewriting its text is not the first thing to try. Check that the URL works, that you want it indexed, and that Google can reach it easily. ## Find every discovered, not indexed page on your site Search Console's report shows up to 1,000 example URLs for each reason. SEO Skill asks Google's URL Inspection about each page it knows from your Search Console and your sitemap, and sorts them by reason. 1. Connect the hosted MCP server and sign in with Google, or run `npm i -g seo` then `seo start`. Both are free. The site has to be a Search Console property your Google account can read. 2. Ask your agent: ``` Which pages on example.com are discovered but not indexed? Group them by folder and tell me which ones we want in Google. ``` Or run it in a terminal: ``` seo index --site example.com ``` Each run checks 100 pages, in a fixed order: pages that lost their clicks, pages by clicks and impressions, sitemap pages, then the rest. On your own machine, `--max-urls` takes it up to the 2,000 checks Google allows each property a day. The result always says how many pages it checked out of how many it knows. ## What you get for a page Google has not crawled Google has no crawl of these pages, so its side of the answer is mostly empty. The live check fills in the rest: the page's status, any redirect, its canonical and robots tags, and whether your sitemap lists it. A page that loads is labelled check. A missing page your sitemap still lists is labelled fix. Here is the kind of result to expect, for example.com: ``` URLs labelled fix or check, 1 to 3 of 3: reason | label | url | live | in_sitemap | last_crawl | why Discovered - currently not indexed | check | /guides/composting | 200 | yes | | Google knows the URL but has not crawled it yet. The sitemap lists it. It returns 200 now. Discovered - currently not indexed | check | /shop?colour=red&size=9 | 200 | no | | Google knows the URL but has not crawled it yet. It returns 200 now. Discovered - currently not indexed | fix | /guides/old-compost-bins | 404 | yes | | It returns 404 now, and the sitemap lists it. ``` Each of the three rows needs something different. The guide is a real page that Google has not crawled yet. The filter URL is one you probably never wanted in Google. The old guide is gone, and the sitemap still sends Google to it. ## Four things to check, in this order 1. Check the URL works. A page that returns 404, redirects or carries a noindex tag now will not be indexed when Google does crawl it. Fix the sitemap or the link that sends Google there instead. 2. Decide whether you want it indexed. Filter, sort and tracking URLs add to Google's crawl queue without adding a page anyone searches for. Take them out of your sitemap and stop linking to them. 3. Check your server answers quickly. Google puts off crawls it expects to overload the site. Search Console's [Crawl stats report](https://support.google.com/webmasters/answer/9679690) shows how fast your server answered Googlebot and any host problems. 4. Make sure your own pages link to it. A page that only your sitemap mentions is easy to put off. `seo internal-links --url https://example.com/guides/composting` crawls your site from your machine and returns up to eight pages that should link to it. Look at the pattern before the pages. Hundreds of discovered URLs in one folder usually trace back to that folder as a whole, such as a filter system or a batch you published at once. None of these checks makes Google crawl or index a page. They remove the reasons on your side that Google could have. ## See whether Google has crawled it since Check one URL on its own: ``` seo page --url https://example.com/guides/composting ``` Once Google crawls the page, URL Inspection shows a last crawl date and the reason changes. `seo` cannot submit URLs to Google. To ask for a crawl, use Request indexing in Search Console's [URL Inspection tool](https://support.google.com/webmasters/answer/9012289). A live index check searches Google itself for `site:` plus the URL and an exact phrase from the page, on desktop and mobile. It needs a DataForSEO key and costs about 2 to 4 cents a page: ``` seo research index_check --target https://example.com/guides/composting ``` ## No discovered pages on seoskill.dev on 11 November 2026 When we ran `seo index` on this site on 11 November 2026, none of its 272 known URLs had this reason, which is why the example above uses example.com. Three URLs were unknown to Google, a step before discovered: Google had no record of them at all. The [website not showing up on Google](https://seoskill.dev/features/website-not-showing-up-on-google) page covers that reason and the others. ## Discovered or crawled, currently not indexed Discovered means Google has the URL and has not fetched it. [Crawled, currently not indexed](https://seoskill.dev/features/crawled-currently-not-indexed) means Google fetched it and left it out, and URL Inspection shows when. A page can move from discovered to crawled, so watch for the reason changing. ## Daily index checks with alerts The [weekly site audit](https://seoskill.dev/docs/weekly-site-audit) ($50 a month per site) runs these checks every day on our servers, using each property's full 2,000 checks. Your agent's `seo index` then answers at once from the stored results, and you get an email when a page drops out of Google's index or comes back. [Alerts](https://seoskill.dev/docs/alerts) covers each email. ## Read the docs [ ### seo index Google's indexing reason for every known page, each checked live and labelled. seo index docs](https://seoskill.dev/docs/indexing)[ ### seo page One URL: what it serves now, its Google index status and its queries. seo page docs](https://seoskill.dev/docs/page)[ ### Crawled, currently not indexed Pages Google fetched and chose not to index. Crawled, not indexed](https://seoskill.dev/features/crawled-currently-not-indexed)[ ### Website not showing up on Google Every indexing reason across your site, and what to check for each. Website not on Google](https://seoskill.dev/features/website-not-showing-up-on-google)[ ### seo internal-links Find the pages on your site that should link to one page. seo internal-links docs](https://seoskill.dev/docs/internal-links)[ ### Weekly site audit Daily Google index checks and an email when a page drops out. Weekly site audit docs](https://seoskill.dev/docs/weekly-site-audit)