How do I fix crawled, currently not indexed?

Fixing crawled, currently not indexed starts with the checks you can verify, and no change guarantees indexing. Check the canonical, duplicates on your site, the amount of real text, internal links and the sitemap entry. Resubmit after a real change and watch the URL Inspection history.

How do I fix page indexing issues?

Fixing page indexing issues starts with the reason Google gives for each URL. Server errors, 404s, robots.txt blocks and noindex directives have direct fixes, and the free indexability checker tests for them. Reasons like crawled, currently not indexed have no single documented cause, so you run checks and watch the result.

Can SearchAnalysis.io get my crawled page indexed?

SearchAnalysis.io cannot get a crawled page indexed, because Google decides what it crawls and indexes. It submits the URL, inspects it with Search Console URL Inspection on a schedule, and turns it green when Google confirms it.

Guide

Crawled, Currently Not Indexed

Crawled, currently not indexed is the Search Console reason Google gives for a page it fetched but did not add to its index. A page Google crawled but did not index shows a lastCrawlTime in URL Inspection and no index entry. The crawled not indexed status comes with no cause list from Google, so this guide covers checks you can verify yourself.

Check a page free Join the waitlist

Source: Google Search Console Help, Page indexing report

Definition

What Crawled, Currently Not Indexed Means

Crawled, currently not indexed is a reason in the Search Console Page indexing report that marks a URL Google has crawled and has not added to its index. Google's full description reads: "The page was crawled by Google but not indexed." The reason names a state, and

The reason sits in the Page indexing report next to Discovered, currently not indexed and Soft 404. For a single URL, the URL Inspection API returns the same state in coverageState, alongside verdict, googleCanonical and lastCrawlTime.

Google decides what it crawls and indexes, and nobody can guarantee indexing. Each check in this guide rules something out.

2,000inspections a day

URL Inspection quota per property

7days

Recheck interval after Indexed

10minutes

First inspection after submission

Comparison

Discovered, Currently Not Indexed Is an Earlier Stage

Both reasons sit in the same report and describe different points in Google's process. Discovered, currently not indexed means Google knows the URL exists and has not fetched it. Crawled, currently not indexed means the fetch already happened.

Attribute	Crawled, currently not indexed	Discovered, currently not indexed
Google's description	"The page was crawled by Google but not indexed."	"The page was found by Google, but not crawled yet."
Has Google fetched the page?	Yes	Not yet
`lastCrawlTime` in URL Inspection	Present	No crawl to report yet
Checks worth running first	The page itself: canonical, duplicates, content	The path to the page: sitemap, internal links, robots.txt
What the free checker verifies	Status, redirects, robots.txt, directives, canonical, word count	The same 6 checks, so the page is ready when Google fetches it

If your page shows Discovered, currently not indexed, Google has the URL and has not fetched it yet, so checks about reaching the page come first: the sitemap that lists it, the internal links that point to it, and a robots.txt that lets Googlebot crawl it. Run the free indexability checker in both states.

URL Inspection

URL Inspection Fields for a Crawled, Unindexed Page

The URL Inspection API answers for one URL at a time. For a page in this state it returns 3 signals you can read directly.

verdict is a value other than PASS. The field takes one of PASS, PARTIAL, FAIL or NEUTRAL, and SearchAnalysis.io treats PASS as indexed.
coverageState carries the reason in Google's wording, the same string you see in the report.
lastCrawlTime is present, because Google did crawl the page. Compare it with your last change to the page.

An inspection result for a page in this state has this shape (values are illustrative):

verdict:          anything other than PASS
coverageState:    "Crawled - currently not indexed"
lastCrawlTime:    2026-10-01T14:22:05Z
googleCanonical:  https://www.example.com/guide/
userCanonical:    https://www.example.com/guide/

The other fields help you rule things out. robotsTxtState and indexingState show whether robots.txt or a directive was in play, googleCanonical and userCanonical show whether Google agreed with your canonical, and sitemap and referringUrls list the sitemaps and pages where Google found the URL.

SearchAnalysis.io stores this snapshot with every inspection. Each inspection becomes a row in the URL's check history, marked NOT_INDEXED while the page stays in this state, and the Google index checker shows that history per URL.

Tracking

Tracking a Page Through Each Recheck

Google decides when a page leaves this state. SearchAnalysis.io inspects the page on a fixed schedule and keeps every result.

Connect the Search Console Property
Add the site, connect Google with OAuth and pick the matching domain or URL-prefix property.
Submit the Page After Your Change
Submit the final URL by single entry, bulk paste, CSV, sitemap import, the REST API or an MCP tool call.
Read the First Inspection
About 10 minutes later, URL Inspection records verdict, coverageState and lastCrawlTime. A page still in this state shows Processing on the Search Console row.
Follow the Ladder
Rechecks run at +15 minutes, +1 hour, +6 hours and every 24 hours, up to 6 checks, then daily. Each one adds a row to the check history.
Confirm Indexed, Then Keep Watching
If an inspection returns PASS, the URL turns Indexed and you get an "Indexed" email. From then on it is inspected every 7 days, and a later miss shows amber Not indexed.

Inspection schedule for one URLSearch Console URL Inspection

0 minSent to Indexing API and IndexNow

+10 minFirst URL Inspection

+15 minSecond inspection

+1 hThird inspection

+6 hFourth inspection

+24 hDaily, up to 6 checks

7 daysRecheck after Indexed

example.com/docs/webhookscheck history

Oct 06 14:20Not indexedCrawled, currently not indexedrecheck

Sep 29 14:18IndexedSubmitted and indexedrecheck

Sep 22 14:21IndexedSubmitted and indexedrecheck

Sep 15 20:02IndexedSubmitted and indexedinspection

Sep 15 14:02ProcessingDiscovered, currently not indexedinspection

Deindex eventIndexed on Sep 15. The recheck on Oct 06 found it not indexed.

First inspectionAbout 10 minutesAfter submission

Confirmation ladderAbout 3 daysUp to 6 checks: +15 minutes, +1 hour, +6 hours, then every 24 hours

Deindex watchEvery 7 daysFor each Indexed URL, while the site is connected

Checks

Checks to Run on a Crawled, Currently Not Indexed Page

Google publishes no single cause list for this reason. Each panel is a check you can verify on your own site, and the first badge says whether the signal comes from Google's documentation or is commonly reported by site owners. Change what you find, then let the inspection history show what Google does next.

(Select a check to read more)

Indexability Basics With the Free Checker

DOCUMENTEDFREE CHECKER

Start a crawled, currently not indexed review by confirming the page is indexable today. Google's report gives the common blockers their own reasons: Server error (5xx), Not found (404), URL blocked by robots.txt and URL marked 'noindex' each have a row. Since those blockers have rows of their own, this reason usually means the page cleared them at the last crawl. Pages change, though, so confirm the current state.

The free indexability checker fetches the page as SearchAnalysisBot/1.0 and runs 6 checks in one pass:

Check	Rule the checker applies
Page loads	A non-2xx final status fails
Redirects	Follows up to 5; Google indexes the destination
robots.txt	Googlebot group wins over `*`; the longest match decides; Allow wins a tie
Indexing directives	`noindex` or `none` in meta robots or X-Robots-Tag
Canonical	Self-reference passes; pointing elsewhere or missing warns
Content	Under about 100 words of visible text warns as thin

The canonical and content results lead into the next panels. The other 4 catch changes made since Google's crawl, like a deploy that added a noindex or a new redirect. If the checker reports a redirect, the URL Google crawled may differ from the one you are now looking at, so work on the destination.

The checker fetches as its own user agent and cannot see Google's index. A clean result tells you the page is eligible today, and URL Inspection remains the only source for whether Google added it.

Canonical Target of the Crawled Page

DOCUMENTEDCANONICAL

On a crawled, currently not indexed page, check where the canonical points. A canonical that names another URL asks Google to index that other URL. If the tag came from a template or was left over from a migration, the page you care about may be asking Google to skip it.

What to Compare

Read the rel=canonical in the page HTML. The indexability checker passes a self-reference and warns on any other target or a missing tag.
Open URL Inspection and compare userCanonical, the URL you declared, with googleCanonical, which Google defines as "The URL of the page that Google selected as canonical."
If the two differ, open the page Google picked. Check whether it is a near copy of yours and whether it is indexed.

<!-- On https://www.example.com/guide/ -->
<link rel="canonical" href="https://www.example.com/guide/">

Google has a separate reason for a disagreement, Duplicate, Google chose different canonical than user. Record any mismatch you find on a crawled page with its date, so you can tell later whether it lined up with a change in state.

SearchAnalysis.io keeps the Google-selected canonical in every inspection snapshot, and the Google index checker shows it next to the verdict. A canonical that changes between inspections is visible in the check history without a manual export. If Google keeps choosing a different URL after you fix the tag, look at the duplicates in the next panel.

Duplicate Content Within Your Site

COMMONLY REPORTEDDUPLICATES

Site owners commonly report crawled, currently not indexed pages that closely match other pages on the same site. Google keeps separate reasons for duplicates: Duplicate without user-selected canonical, Duplicate, Google chose different canonical than user, and Alternate page with proper canonical tag. The link between duplication and this reason comes from site owners' reports, and Google has not documented it.

Patterns Worth Checking

URL parameters for sorting, filtering or tracking that serve the same content
Tag, category and archive pages that list the same posts
Location or product pages built from one template with a few words swapped
HTTP and HTTPS, or www and non-www, versions that both answer 200
Printer-friendly copies of an article

To find them, export the URLs under this reason and sort them by path. Clusters of near-identical paths stand out fast. The page inventory in sitemap monitoring records every URL in your sitemaps with first seen and last seen dates, which helps you spot template pages that multiplied.

If you find a cluster, decide which page should represent it. Point the others' canonicals at that page, merge them into it, or make each one distinct enough to stand on its own. Then resubmit the page you kept, and leave the merged URLs to redirect. Run the indexability checker on each old URL to confirm its redirect lands on the page you kept.

Thin or JavaScript-Only Content

COMMONLY REPORTEDCONTENT

Thin pages come up often in site owners' reports about crawled, currently not indexed URLs. Google has not published a word count or a quality threshold for this reason, so treat the checks below as things you can measure, with no promised outcome.

Free checker thin content warningUnder about 100 wordsVisible text counted in the HTML the checker fetches.

Thin Text

Run the page through the indexability checker and read the content result. A warning means the fetched HTML holds under about 100 words of visible text. Then compare the page with what a searcher needs: a product page without a description, a location page with only an address, or a post that is mostly embeds will read as short to any reader.

Text That Only JavaScript Adds

If the count is far lower than what you see in the browser, your main text is likely added by scripts after the HTML arrives. Open View Source and search for a sentence from the body. If it is missing, the first response carries an empty shell. Rendering the main text on the server puts it in the HTML that every crawler receives first.

Google's report has a related warning, Page indexed without content, which applies to pages that are in the index. It is the closest documented name to this check, and it does not describe pages under this reason. After you add text, run the checker again and confirm the count rose in the fetched HTML, since that is the version a crawler receives first.

Internal Links Pointing to the Page

COMMONLY REPORTEDLINKS

A crawled, currently not indexed page with few internal links pointing to it is a pattern site owners report often. Google has not documented a link count for this reason. What you can verify is how your own site connects to the page and where Google says it found the URL.

What Google Shows You

URL Inspection returns referringUrls, a list of pages where Google found the URL, and sitemap, the sitemaps that list it. If referringUrls is empty, Google has reported no page linking to it.

What to Check on Your Site

Search your site or CMS for links to the exact final URL, with the same protocol, host and trailing slash.
Check that the links appear in the page HTML, in body text or navigation, since links built by scripts after load may be absent from the first response.
Add links from related pages that are already indexed, with anchor text that names the page's topic.
Fix links that point to a redirecting or non-canonical version of the URL.
Check that the page is reachable within a few clicks from the home page or a hub page, and not orphaned on a path nothing links to.

Once links are in place, the Google index checker shows each later inspection of the page, so you can see whether referringUrls and the verdict change.

Sitemap Presence and Lastmod Accuracy

DOCUMENTEDSITEMAPS

Check that a crawled, currently not indexed page appears in a sitemap Google knows about, and that its <lastmod> tells the truth. Google documents how it reads both.

Sitemap fact	What Google says
`<lastmod>`	Used "if it's consistently and verifiably accurate"
`<priority>` and `<changefreq>`	"Google ignores `<priority>` and `<changefreq>` values."
Size limit	50MB uncompressed or 50,000 URLs per sitemap
Ping endpoint	Retired, announced June 2023
How to submit	Search Console, the Search Console API, or a reference in robots.txt

A <lastmod> that changes on every build, with no change to the page, fails Google's test of consistent, verifiable accuracy. Set it when the main content changes.

URL Inspection's sitemap field lists the sitemaps where Google saw the URL. If it is empty for a page you meant to list, open the sitemap itself and confirm the exact final URL is in it. Sitemaps are submitted in Search Console, through the Search Console API, or referenced in robots.txt, so check that the file you edited is the one Google reads.

List the final URL, after redirects, with the same protocol and host as the canonical.
Remove URLs that redirect, return errors or carry a noindex.
Split a sitemap that passes 50,000 URLs or 50MB into several files under a sitemap index.

Sitemap monitoring scans your sitemaps every 6 hours, follows sitemap index files to their child sitemaps, and records each URL as Discovered, Submitted, Indexed or Removed. Automatic resubmission when a sitemap lastmod changes is PLANNED: it will resubmit a page when its lastmod moves.

Resubmitting After a Real Change

COMMONLY REPORTEDMONITORING

Resubmit a crawled, currently not indexed page after you change something Google can see: new text, a corrected canonical, new internal links. Resubmitting an unchanged page asks Google to look at the same thing again. Reports that resubmission helps come from site owners, and Google decides what it crawls and indexes.

How SearchAnalysis.io Tracks the Page

Submit the final URL. SearchAnalysis.io sends it to Google and to Bing through IndexNow, and queues a Search Console inspection.
The first URL Inspection runs about 10 minutes after submission.
If the page is not indexed, rechecks follow at +15 minutes, +1 hour, +6 hours and then every 24 hours, up to 6 checks.
After the ladder, a daily fallback keeps inspecting the unconfirmed URL.
Each inspection adds a row to the check history with the time, the state and the coverage state.

Confirmation ladder6 checks over about 3 daysThen a daily fallback for unconfirmed URLs.

Two details matter here. A URL already tracked on your account in the last 30 days is skipped and reported, and the daily fallback keeps inspecting it anyway. The Indexing API row shows Processing when Google accepts the notification, and only the URL Inspection row turns a URL green. Watch the Google index checker history for the day coverageState changes, and compare lastCrawlTime with the date of your change to see whether Google has crawled the new version yet.

FAQ

Common Questions About This Search Console Reason

What the Reason Means

What does crawled, currently not indexed mean?

Crawled, currently not indexed means Google crawled the page and did not add it to its index. Google describes it only as "The page was crawled by Google but not indexed."

What is the difference between crawled and discovered currently not indexed?

The difference between crawled and discovered, currently not indexed is whether Google has fetched the page. Crawled means Google fetched it and did not index it. Discovered means Google found the URL and has not crawled it yet.

What are page indexing issues?

Page indexing issues are the reasons Google lists in the Search Console Page indexing report for URLs it did not index. They include Server error (5xx), Not found (404), URL marked 'noindex', URL blocked by robots.txt and Crawled, currently not indexed. Each reason names a different state.

Waitlist

Join the Waitlist for Verified Index Tracking

The checks above are yours to run. SearchAnalysis.io handles the repeat work: inspecting each page on a schedule and keeping the history. Access is invite-only, through the waitlist.

Picture opening a page's history after your next fix and reading each inspection in order, with the date its coverageState changed if Google indexes it.

Waitlist members getwritten commitments

An Invite Before Public Launch

Waitlist members get access before the product opens to everyone.

Launch Pricing Locked

Your launch price stays locked for as long as you stay subscribed. The price is announced at launch.

An Extended Free Trial

Waitlist members get a longer free trial. Its length is announced at launch.

Included in SearchAnalysis.ioshipped

An Inspection Ladder per URL

The first inspection runs about 10 minutes after submission, then at +15 minutes, +1 hour, +6 hours and every 24 hours.

Full Check History

Every inspection is stored with its time, state and coverage state.

A Google Index Card per Site

Pages verified indexed, a 30-day trend and coverage printed with its denominator.