Short answer: "Crawled, currently not indexed" means Google fetched the page and chose not to add it to the index, at least for now. On a brand new WordPress site this is often normal and tends to fade over a few weeks as Google learns the domain. It becomes a real problem only when it is paired with a hidden technical block, thin pages, or pages Google cannot find through links. Rule out the technical causes first, then improve the pages, then wait.
What does the status actually tell you?
Search Console shows this status in the Page indexing report. It is not an error and, as far as we know, it is not a penalty. It says the page was crawled but not indexed. On repeated requests, Google's recrawl guide says that requesting a crawl multiple times for the same URL "won't get it crawled any faster", so resubmitting the same URL is not a fix (Ask Google to recrawl your URLs). A new domain has no history, so Google may be cautious about how much of it to store.
| Status in Search Console | What it usually means | What to do |
|---|---|---|
| Crawled, currently not indexed | Fetched, not stored yet | Check quality and links, then wait |
| Discovered, currently not indexed | Known URL, not fetched yet | Add internal links, check server speed |
| Excluded by noindex tag | The page tells Google not to index it | Remove the noindex, then request indexing |
Is something on the site telling Google to stay out?
Check this before anything else, because it is quick and it is the most embarrassing cause. WordPress has a setting under Settings, then Reading, called "Discourage search engines from indexing this site". Developers tick it on staging and forget to untick it at launch. WordPress's Reading screen documentation describes the setting and, as we read it, says it is up to search engines to honor the request (Settings Reading screen). In practice, when the box is ticked WordPress typically adds a noindex robots tag to pages. Google's noindex guide says a page with that rule can be dropped from search results (Block search indexing with noindex).
You can see the same kind of signal from a terminal. As a reproducible example, httpbin.org is a public test service that echoes query parameters back as response headers, so this command asks it to send a noindex header:
curl -sI "https://httpbin.org/response-headers?X-Robots-Tag=noindex" | grep -i "x-robots-tag"It should print a line like x-robots-tag: noindex. That is the exact line to look for on your own site. Now point the same two checks at the client's page:
curl -s https://example.com/ | grep -i "robots"
curl -sI https://example.com/ | grep -i "x-robots-tag"The first command shows any robots meta tag in the HTML. A line containing noindex means the page is blocked. The second shows the HTTP header version, which an SEO plugin, a caching layer or the host can set without touching the page source. If you prefer not to use a terminal, paste the address into the noindex checker, which looks at the tag, the header and robots.txt together. See httpbin's response-headers endpoint for how the test service works.
Also open /robots.txt and look for Disallow: /. Google's robots.txt introduction explains what these rules do (Introduction to robots.txt). Then confirm the XML sitemap loads and lists the URLs you want indexed. Cloudflare bot settings are worth a look too, since a challenge page served to Googlebot can look like an empty page.
If nothing is blocked, why does Google skip the page?
Once the technical checks are clean, the cause is often one of these. Google does not publish a per-page reason, so treat this list as likely suspects, not a diagnosis:
- Thin or templated pages. A page with a few lines of text, or ten near-identical service pages with only the town name swapped, gives Google little reason to store each one. Google's helpful content guidance asks whether a page provides substantial value (Creating helpful, reliable, people-first content).
- No internal links. A page that only appears in the sitemap and is linked from nowhere looks unimportant. Link it from the homepage or a main menu page.
- Default and filler content. Sample pages, "Hello world" posts and placeholder text dilute the site. Delete them.
- Duplicate or alternate URLs. Tag archives, author archives and attachment pages can crowd out the pages that matter.
- A very new domain. Google needs time and signals before it trusts a site with no history.
What are the exact fix steps?
- In Search Console, open the URL Inspection tool for one affected page and run the live test. Confirm it says the page is available to Google and indexing is allowed.
- Untick the Reading setting if it is on, and check your SEO plugin has no site-wide noindex option enabled.
- Fix robots.txt and any X-Robots-Tag header you found.
- Improve the weakest pages: add real, specific content that the client can stand behind, and merge pages that say the same thing.
- Add internal links from the homepage and menu to every page that should rank.
- Submit one clean sitemap, then use Request Indexing for the few most important pages only.
- Wait two to four weeks before judging, and check the same report again. This is a rule of thumb, not a Google promise.
What do you tell the client?
Keep it plain: "Google has visited the new pages but has not added all of them yet. This is common for new websites. We have checked that nothing on the site is blocking it, and we are strengthening the pages and links. We will recheck in two weeks." Do not promise a date for indexing, because nobody outside Google controls it. Do promise the check, and send the result.
How does quietwatch catch the blocking causes daily?
A site that was fine at launch can pick up a noindex tag, a robots.txt block or a bad header after a plugin update or a host change. what quietwatch checks every day covers those, plus sitemaps, certificates and Cloudflare settings, and it alerts you before the client notices. The free tool above is the place to start for a one-off look at a single site.
Sources
- Google Search Central: Ask Google to recrawl your URLs
- Google Search Central: Introduction to robots.txt
- Google Search Central: Block search indexing with noindex
- Google Search Central: Creating helpful, reliable, people-first content
- WordPress Documentation: Settings Reading screen
- httpbin: Response headers test endpoint