When a page gets no traffic, or a site suddenly loses impressions, it is easy to jump to one scary conclusion: Google penalized me.
Usually, that is not the first explanation to test.
Google Search Console can show four very different situations that often get mixed together: a page is indexed but unseen, crawled but not indexed, discovered but not crawled, or losing traffic after it once ranked. Each needs a different response.
This guide gives you a simple way to read those signals. It is not a shortcut for diagnosing every ranking problem. It is a way to stop making the wrong fix first.
Important: Search Console indexing statuses are not a penalty meter. A real manual action or security issue is the first thing to rule out.
Start here: check for a real manual action or security issue
Before reviewing any chart, open Security & Manual Actions in Search Console.
If Google has applied a manual action, it will be reported there. This is the closest thing to a confirmed Google penalty. Security issues, such as hacked content or harmful downloads, are also shown separately.
If both reports are clear, do not assume everything is perfect. It simply means you should move on to normal diagnosis: indexing, relevance, technical health, and search demand.
That distinction matters. A page can be absent from search without any punishment at all.
Signal 1: the page is indexed, but it gets almost no impressions
An indexed page is eligible to appear in Google Search. It does not mean Google has found a good reason to show it often.
This is common when a page answers a question that few people search for, targets a broad term already dominated by stronger pages, has a title that does not clearly match the reader’s intent, gives a thin answer, or has no internal links that explain why the page matters.
What to check
Open URL Inspection and confirm that the page is indexed. Then open Performance, filter by that page, and look at impressions over the last 28 days.
If impressions are near zero, the first job is not to rewrite every sentence. First ask: What exact search should this page deserve to appear for?
Read the title, H1, opening paragraph, and subheadings together. A reader should be able to tell the page’s promise in a few seconds. If the promise is vague, Google may have the same problem.
A useful next move
- Write a specific title that names the problem or outcome.
- Add the missing steps, example, comparison, or answer that a reader would expect.
- Link to the page from one or two genuinely related pages on your site.
- Give Google time to recrawl. Do not judge the change the next morning.
Signal 2: “Crawled – currently not indexed”
This status means Google fetched the page, but chose not to include it in its index at that time.
It can feel like a rejection, but it is not proof of a penalty. Google may reconsider later. The status is often a sign that the page is too similar to another page, too light for the query it targets, unclear in purpose, or simply not a priority yet.
Do not start by deleting everything
A common reaction is to remove all pages with this status. That can create a bigger mess. First separate the pages into three groups:
| Page type | Better response |
|---|---|
| A valuable page with a clear but incomplete answer | Improve and keep it. |
| Two pages covering almost the same intent | Merge the stronger ideas into one page; redirect only if there is a clear replacement. |
| A page you no longer want readers or search engines to find | Remove it deliberately; do not create a replacement just for the status report. |
What to improve before requesting another crawl
Look for a real quality gap. For example, an article may promise a tool comparison but list only features. A better version could include who each tool suits, cost limits, setup notes, and a simple decision table.
Also check the basics:
- Is the page indexable and self-canonical?
- Does it return a normal
200status for visitors? - Is the content substantially different from nearby pages?
- Does at least one relevant internal link point to it?
- Does the page answer a distinct question?
Request indexing only after the page has materially improved. Repeated requests without a better page rarely change the underlying decision.
Signal 3: “Discovered – currently not indexed”
This status means Google knows the URL exists but has not crawled it yet.
For a new or small site, a few URLs in this state are normal. The useful question is whether it is a small delay or a pattern across important pages.
If many valuable pages stay here for weeks, look at crawl priority rather than treating every URL as an emergency.
Give Google a clear path to the page
- Add the page to your XML sitemap.
- Link to it from a relevant published page, not only from a tag archive or a menu.
- Make sure the server responds reliably and reasonably fast.
- Avoid publishing many near-duplicate URLs at once.
- Keep pagination, filters, and parameter URLs under control.
Submitting a sitemap is helpful, but it is not a command to crawl every URL immediately. Internal links and useful content help Google decide which pages deserve attention first.
For a young site, this is one reason to publish focused articles and connect them naturally, rather than creating dozens of weak pages in one batch.
Signal 4: a page used to get impressions, then drops sharply
This is the signal worth treating most carefully. It does not automatically mean a penalty, but it can point to a real change.
Start by comparing two meaningful periods, such as the last 28 days against the previous 28 days. If the topic is seasonal, compare the same period last year when enough data exists.
Work through the likely causes in order
- Technical change — Did the URL redirect, become blocked, change its canonical tag, lose important text, or return an error?
- Indexing change — Does URL Inspection still say the live URL is indexed?
- Search demand change — Are related queries down as well? Some topics simply cool off.
- Search-result change — Did Google add more videos, product results, forums, or AI features that push ordinary pages lower?
- Competition or freshness — Did stronger pages publish a better, newer answer?
Check both the page and the queries that lost impressions. A drop in one query may be a content-match issue. A drop across many pages may point to a technical or site-wide change.
Do not make five changes at once. Fix the clearest issue, note the date, and then watch the trend.
The 20-minute diagnosis path
| Minute | Check | What the result tells you |
|---|---|---|
| 1–3 | Manual Actions and Security Issues | Whether there is a confirmed Google enforcement or security problem. |
| 4–7 | URL Inspection | Whether the specific live URL can be indexed and is known to Google. |
| 8–12 | Pages report | Whether the issue is crawling, indexing, duplication, or something else. |
| 13–20 | Performance by page and query | Whether the problem is low visibility, a traffic decline, or weak intent match. |
This sequence will not solve every SEO problem. It does prevent a common mistake: treating a relevance problem, a crawl-priority problem, and a real manual action as if they were the same thing.
What not to do
- Do not call every indexing status a penalty.
- Do not delete pages in bulk just to make a report look cleaner.
- Do not buy links or use link schemes to force a recovery.
- Do not refresh the report several times a day and expect a useful answer.
- Do not rely on one
site:search as proof that a page is healthy or broken.
Search Console is most useful when you use it to form a small, testable hypothesis: this page has unclear intent, these URLs are too similar, or this section is not getting enough internal links. Then make one meaningful change.
A quick checklist before you blame Google
| Check | Done? |
|---|---|
| Manual Actions and Security Issues are clear | ☐ |
| The live URL can be indexed and has the right canonical | ☐ |
| The page has a distinct purpose and a useful answer | ☐ |
| The page has at least one relevant internal link | ☐ |
| You compared a meaningful date range, not one bad day | ☐ |
| You chose one clear improvement before requesting another crawl | ☐ |
The goal is not to make every Search Console report turn green. The goal is to understand what Google is telling you, make the next sensible change, and give that change enough time to work.