When Search Console reports “Discovered – currently not indexed” or “Crawled – currently not indexed”, the cause is usually a judgement about the page rather than a fault in the site. The first status means Google knows the address exists but has not yet fetched it; the second means it fetched the page and decided not to keep it. In both cases a search engine is weighing whether the page adds anything it does not already have, and resubmitting the address does not change the answer.
Rule out the mechanical causes first, quickly
There is a short list of genuine faults, and checking it takes minutes. Confirm that the page returns a normal success response, that it is not blocked by robots rules or marked noindex, that its canonical address points to itself, and that it is listed in the sitemap. Check that the content is present in the HTML a crawler receives and not only after scripts run.
If all of that is clean, which it usually is, stop looking for a bug. The remaining causes are about the page and the site, and no setting will fix them.
Does the page answer something no other page of yours does?
Thin pages and near-duplicates are the most common reason. A search engine has no use for a tenth page that says what nine others already say with a different city name or a swapped keyword. If a page could be deleted and nothing on the site would be missing, that is often what the status is telling you.
The remedy is a decision, not a technique: merge the page into the one that already covers the topic, give it a genuinely different purpose, or remove it. Publishing fewer pages that each earn their place is usually better than publishing many that do not.
Is anything linking to it?
A page that no other page links to looks unimportant, because the site itself behaves as though it is. Listing an address in a sitemap tells a crawler it exists, but it does not tell the crawler it matters. Links from pages that are themselves well placed, with anchor text that describes the destination, are how a site says which pages carry weight.
Look at how deep the page is and how many routes lead to it. If the answer is one route from a long list, that is a structural problem you can fix without touching the page.
Is the site generating addresses nobody asked for?
Filters, sort orders, tag archives, parameters and printable versions can multiply a few hundred useful pages into thousands of near-identical ones. A crawler that meets an endless supply of low-value addresses learns to spend less time on the site, including on the good pages. Where a large number of excluded addresses share a pattern, the pattern is the problem.
Decide which addresses should exist at all. The ones that should not can be kept out of the index with noindex or, better, never generated.
A decision this studio made on its own site
The portfolio on this site lists many projects, but only a subset has a page of its own. The rest appear in the portfolio index and nowhere else, and they are deliberately left out of the sitemap. A single published sentence about a client is not a case study, and forty pages built from one sentence each would be exactly the kind of near-empty addresses that end up in “Discovered” or “Crawled” with no index.
The rule is the same one a crawler applies: a page earns an address when it answers something no other page does. A page that cannot meet it is better folded into a list than published alone.
New sites wait, and resubmitting does not help
A new site with little history and few links is crawled cautiously, and pages can sit in these states for a while without anything being wrong. Patience, plus the structural work above, is the honest advice.
Resubmission tools have their place. Requesting indexing for a single page is reasonable after you have fixed it, and a protocol such as IndexNow tells participating search engines about changes faster. But IndexNow is not read by Google, and a notification is not an argument: if the page was not worth indexing before you sent it, it is not worth indexing after. Fix the reason, then ask.