Start here#

Google has fetched the URL but has not included it in the index at the reported time. Investigate what the page contributes before requesting another crawl.

  1. Compare the rendered page with an indexed page serving a similar purpose.
  2. Resolve thin content, unintended duplication and contradictory canonical signals.
  3. Strengthen useful internal links, then monitor after a meaningful change.

Treat the status as a starting point#

The cause may be technical, presentational, duplicate-related, site-wide, or simply temporal. Avoid turning the label into a universal “content quality” verdict before verifying what was fetched.

Verify the live page as Googlebot might receive it#

Run URL Inspection’s live test, then compare the final URL, HTTP response, rendered HTML, screenshot, robots directives, and canonical. Check for bot challenges, intermittent 5xx errors, soft 404 messages, empty JavaScript shells, and headers added outside WordPress.

If Detailed SEO or your browser sees a positive page while a remote tool sees a negative response, investigate firewall variation. The correct diagnostic state is unverified until the responses agree.

Review duplication, internal importance, and usefulness#

Compare the URL with pages already indexed on the site. Consolidate near-duplicates, strengthen the distinct purpose, and make the page answer the query more completely.

Then check whether important pages actually link to it and whether the sitemap lists the same canonical URL.

Large sets of tag, author, date, filtered, or paginated URLs often signal a template decision rather than hundreds of independent failures.

A measured recovery sequence#

  1. Capture the current inspection and report dates.
  2. Fix confirmed response, rendering, robots, or canonical defects.
  3. Improve or consolidate pages that duplicate an existing destination.
  4. Add relevant internal links and update the sitemap.
  5. Request indexing once after meaningful changes, then allow time for recrawl and evaluation.

Use the preflight checklist before the next request.

Sources and further reading#

Choose your next step#

Follow the guide that matches your next decision.

Questions, answered#

How long can this status last?

There is no fixed deadline. The next useful step depends on the live technical state, site crawl patterns, and the page’s distinct value.

Should I rewrite the whole page?

Only after verifying technical and duplicate signals. Rewrite when the page does not offer a distinct useful destination.

Why does the live test pass while the report says not indexed?

The report and live test can describe different fetches and dates. A live pass shows the current page is accessible, not that the report has updated.

Can a firewall cause this?

Yes. A crawler may receive a challenge or alternate response even when a logged-in browser sees the intended page.