Crawled, Currently Not Indexed: What to Check Before Rewriting

“Crawled, currently not indexed” means Google fetched the page and decided not to index it for now. Before you rewrite anything, check three things in order: whether the crawl Google recorded is older than your current page, whether Google treats the page as a copy of another URL, and whether the content Google rendered matches what visitors see. Only when all three are clean is the page an editorial question.

Google’s Page Indexing report help, checked September 27, 2026, describes the status in two short sentences: “The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling.” Beyond the status itself, it does not say why a particular URL was left out. Anything you conclude about the cause is your own inference, so keep it labeled that way in your notes.

If you have not yet confirmed that the page returns 200, is allowed by robots.txt, and has no noindex, start with the indexing triage guide. This guide assumes those checks passed.

What the status does and does not tell you

The status tells you Google reached the page. That rules out several technical faults: the fetch did not fail, and robots.txt did not block it. It does not tell you the page is broken, penalized, or low quality. Google’s technical requirements, checked September 27, 2026, state that meeting the minimum requirements “doesn’t mean that a page will be indexed; indexing isn’t guaranteed.”

So the useful question is narrower than “why did Google reject this?” Ask instead: is there something specific about this URL, as Google saw it, that I can confirm and correct? If you cannot find one, a bounded editorial improvement or no action at all may be the right answer.

Confirm which crawl Google is reporting

Inspect the exact URL from the report in the URL Inspection tool. Compare Last crawl with the date you last changed the page. If the crawl came before your change, the status describes a page that no longer exists in that form.

Then check that the URL in the report is the one you care about. On WordPress, a sample of “Crawled, currently not indexed” URLs can include addresses that were never meant to rank. Check the sample for patterns like these:

If most of the sample is patterns like these, the report may be describing housekeeping rather than a problem with your articles. WP Visibility, if you use it, redirects attachment pages to the file and redirects ?replytocom addresses to the plain post URL by default; both toggles are in the Indexing section of its settings. If you use another SEO plugin, check its documentation for similar settings. For the archives you want out of search entirely, keep them out deliberately instead of leaving Google to sort them.

Google’s URL Inspection help, checked September 27, 2026, explains that the indexed view is not live. Run Test live URL as well, so you know whether Google can access the current page for indexing. The same help says a valid live test does not mean the page will be indexed, so a clean result does not clear this status.

Compare the page with its near duplicates

Look at Google-selected canonical in the inspection result. If it names a different URL from the one you inspected, Google is treating your page as a copy, and the repair belongs to canonical selection, not to a rewrite.

If the canonical field does not point elsewhere, look for similar pages on your own site that answer the same question. A WordPress site can end up with several routes to the same text:

• A category archive that shows full posts rather than excerpts repeats each post’s body.
• Two posts written years apart on the same topic, often with similar titles.
• A page and a post with the same content, created during a theme or builder change.
• A staging or development copy that is publicly reachable.

Google’s canonicalization documentation, checked September 27, 2026, lists “accidental variants,” such as a demo version of the site left accessible to crawlers, among the reasons a site may have duplicate content. Open each candidate and compare the main text. If two pages give the same answer, the decision to merge or keep both is editorial; make it deliberately and redirect the one you retire.

Check what Google rendered

In URL Inspection, run a live test and open View tested page. The URL Inspection help, checked September 27, 2026, says the indexed view’s View crawled page data is available only for URLs that are on Google, so for this status the live test is where you see what Google fetches from the current page. A successful live test includes a screenshot of the rendered page. Compare the HTML and the screenshot with what a visitor sees in a private window. You are looking for main content that Google did not receive:

• Text loaded by JavaScript that failed or timed out; check the JavaScript console output for errors.
• Page resources that did not load, listed under More info in the tested page panel. A robots.txt rule blocking /wp-content/ can stop Google from loading the theme and plugin styles and scripts stored there. Google’s robots.txt introduction, checked September 27, 2026, warns that blocking resources Google needs means it “won’t do a good job of analyzing pages that depend on those resources.”
• A cookie consent overlay, age gate, or membership prompt that replaces the content in the rendered page.
• A security challenge page from a firewall or CDN instead of your content.

If the rendered page is missing its main content, you have a technical fault with a clear owner: the theme, the plugin that loads the content, or the security layer. Fix that and retest. Rewriting the text would not help, because Google was not receiving it.

When the page checks out: a short editorial referral

If the crawl is current, no other URL is selected as canonical, and the rendered page is complete, the remaining question is whether the page gives a searcher something the rest of the web and the rest of your site do not. Google’s guidance on helpful content, checked September 27, 2026, offers self-assessment questions such as “Does the content provide original information, reporting, research, or analysis?” and “Does the content provide substantial value when compared to other pages in search results?”

Choose one bounded correction rather than a sitewide overhaul:

1. Merge it into a stronger page on the same topic and redirect the old URL. See 404, 410, or redirect for the response to use.
2. Improve it with the specific information a reader needs and cannot find elsewhere on your site.
3. Keep it out of search on purpose if it serves visitors but not searchers, such as a thank-you page.
4. Leave it alone if it already does its job and search traffic was never its purpose.

As an illustration, imagine the fictional garden.example has a 200-word tag archive and a 1,500-word pruning guide covering the same shears. Rewriting the tag archive would compete with the guide. Noindexing the tag archive, or linking it prominently to the guide, is the bounded change. This example is invented to show the reasoning; it is not an observed result.

Record a recheck

After a change, request indexing once for the URL. Google’s recrawl documentation, checked September 27, 2026, says there is a quota, that “requesting a recrawl multiple times for the same URL won’t get it crawled any faster,” and that crawling “can take anywhere from a few days to a few weeks.”

Keep a short log for each URL you work on:

• The date and the status as reported, with the last crawl date.
• Which of the three checks you ran and what each showed.
• The one change you made, if any, and why.
• The date you requested indexing, and the date you will look again.

If the status is unchanged after the recheck and every check still passes, the evidence does not identify a fault. Record that plainly and move on to pages where you can confirm a cause.