Crawled - Currently Not Indexed: How to Check One Page Before Changing Your Whole Site

Your new site has a handful of pages. The homepage is indexed, but Search Console lists an article as “Crawled – currently not indexed.” You can open the page yourself. Your sitemap was submitted. What should you do next?

Start with one representative URL, not every excluded page at once. Google’s Page indexing report says this status means Google crawled the page, but it is not indexed. The label does not identify a cause. The separate “Discovered - currently not indexed” status means Google found the URL but has not crawled it yet.

This guide walks through the evidence you can collect for one page, how to choose the next action, and when to stop changing things and wait for another observation. The examples below are illustrative; they are not results from a customer site.

First, inspect the exact URL

Open Search Console for the correct property. In Pages, open the “Crawled – currently not indexed” group and choose a page that you genuinely want searchers to find. Copy its full URL, including https, hostname, path and any trailing slash. Then paste that URL into URL Inspection.

Record the result and the last crawl date. Compare them with the date you last changed the page. Compare the report’s date with the inspection result and its last crawl date; the reports can reflect observations from different times. Google explains the difference between indexed data and live tests in its URL Inspection documentation.

If the inspected URL is already indexed, check whether you inspected the same address that appeared in the report. Then note the dates rather than making another change immediately. If it is still excluded, keep the inspection result as your baseline.

What a live test can and cannot tell you

The live test checks whether Google can currently access and process the URL for indexing. It is useful after a change, but a successful live test does not mean Google has indexed the page. The indexed result describes Google’s stored view; the live result is a fresh check of the URL. Keep both when you compare them.

Check whether this is the page you intend to keep

In URL Inspection, compare the user-declared canonical with the Google-selected canonical if those fields are available. A canonical is the preferred URL among duplicate or very similar pages; Google’s choice can differ from the one a site declares. See Google’s canonicalization guidance.

Imagine your article is available at both /guide and /guide?source=newsletter. If the tagged URL is excluded while the clean URL is selected and indexed, the next step may be to use the clean URL in internal links and your sitemap—not to create another copy. That is an example, not a claim about your own canonical settings.

If an important, substantially different page points to an unrelated canonical, investigate why. Check the page’s canonical element and redirects, and compare its main content with the selected page. Do not assume that changing a canonical tag alone forces Google to choose it.

Compare what people see with what Google can access

Open the page in a normal browser. Confirm that the main heading, answer and any essential content are actually present. Then use URL Inspection’s available crawl or rendered-page information to check what Google retrieved. Google describes the available screenshots and rendered HTML in the live test instructions.

Look for a specific mismatch. For example, if the visitor sees the article but the inspected HTML or screenshot shows only a sign-in screen, check the response and rendering path with the person responsible for the site. JavaScript by itself is not a diagnosis: Google can render JavaScript, but rendering and access still need to be checked for the page in question. See Google’s JavaScript SEO basics.

Also inspect the current response, redirects and any noindex directive if the live test points to an access or indexing restriction. The earlier “crawled” status is a historical observation; it does not guarantee that the current page has the same response today. A successful HTTP response alone is not proof that a page has been indexed.

Give the page a job that another page does not already do

Once the canonical and access checks make sense, read the page alongside your closest related page. Ask what a visitor can do or decide after reading this URL that they could not do as easily on the other one.

A short service-area page that changes only the city name might not give someone enough local detail to choose a service. A useful revision could add the actual area served, relevant constraints, a clear contact route and answers specific to that location—if those facts are true. A tutorial might need a missing step, an original example or a clearer explanation of when its instructions do not apply.

Do not add generic paragraphs merely to make the page longer. If two pages genuinely serve the same need, decide which should be the main page and handle the overlap deliberately. Google’s helpful content guidance asks creators to focus on content made for people; it does not provide an indexing guarantee for any particular edit.

Make the next step easy to discover

Find an existing page where the excluded URL would help a reader continue. Add a descriptive link in context if one is missing. For instance, a guide about comparing service quotes could link to a genuinely useful page explaining what a local quote includes. Avoid adding a sitewide link to every excluded page simply because it is excluded.

Keep your sitemap aligned with the canonical URLs you want discovered. A sitemap is a discovery signal, not a promise of indexing. Google’s sitemap documentation explains its role and limitations. If the page already has an appropriate internal link and is in the sitemap, record that and move on; submitting the same sitemap repeatedly does not establish that the page needs a different fix.

Make one meaningful change, then compare the same evidence

Write down the URL, the inspection status and crawl date, the issue you observed, and the change you made. After publishing your change, use the live test if you need to check whether the new version is accessible. You can request indexing for an important changed URL through Search Console, but a request does not guarantee indexing or immediate processing. See Google’s recrawl guidance.

On a later review, inspect the same canonical URL and compare the status and crawl date with your notes. If Google has not recrawled since the change, you do not yet have evidence of how it processed the revision. If it has recrawled and the page is still excluded, revisit the evidence; the status alone does not tell you which of several possible factors matters.

For a separate check of the homepage, a registered site owner can use SEOHabit’s website SEO checker; its first check has a limited homepage scope. It does not diagnose the indexing status of the inner page in this example. Site ownership and ongoing checks follow the product’s current workflow. Use Search Console for Google’s indexing information.

For now, pick one important URL and save its inspection result. That gives you a real baseline for the next decision, even if the answer today is simply that Google has not indexed it yet.