Positions 70 through 90, across the board. Eighty-five percent of Search Console showing some flavor of “not indexed.” New content published, old titles rewritten, sitemaps resubmitted — nothing moves. Somewhere in that stretch of silence, the question that feels inevitable arrives: is the domain just burned?

Almost never in the way that phrase implies. “Burned” suggests a permanent blacklist, and Google doesn’t work that way. What’s actually happening is one of two very different things — a specific, human-reviewed manual penalty, or a much more common algorithmic quality suppression with no notice and no appeal button — and confusing the two is why so many recovery attempts go nowhere. This guide is the fifteen-minute triage that tells you which one you’re facing, followed by the recovery framework for the algorithmic case, which is the one most teams actually have.

Step 1: Rule Out a Manual Action First

A manual action is a specific, documented thing: a human reviewer at Google found your site violating a spam policy — unnatural links, thin or auto-generated content deployed as spam, cloaking, structured data abuse — and applied a penalty by hand. Critically, manual actions are always visible. Open Search Console, go to Security & Manual Actions → Manual Actions, and you’ll see either “No issues detected” or a labeled violation with example URLs and a “Request review” button once you’ve genuinely fixed the cause.

This check takes under a minute and it should be the very first thing you do, because it completely changes your next move. If a real manual action exists: fix the specific violation, document exactly what changed, and submit reconsideration with specifics — don’t submit until the fix is thorough, since a half-fixed resubmission just burns a review cycle and extends your timeline. If it says “No issues detected” — and for the large majority of sites in the 70-to-90-position, mostly-unindexed scenario, it will — stop looking for a reconsideration button that doesn’t apply to you. Your problem is algorithmic, not punitive, and the rest of this guide is written for exactly that case.

Step 2: Understand What’s Actually Happening Instead

No manual action doesn’t mean “nothing is wrong.” It means Google’s automated systems have made an ongoing, unannounced judgment that large portions of your site aren’t worth ranking or indexing — and that judgment responds to evidence, not appeals.

The most common visible symptom is a large share of URLs sitting in “Crawled – currently not indexed” status — meaning Google fetched and rendered the page, then actively decided not to store it. This is a quality and prioritization verdict, not a technical bug, and Google’s own guidance and support threads consistently point toward fixing the underlying causes rather than repeatedly requesting reindexing. We’ve published a full diagnostic breakdown of the six specific causes behind this status — thin content, duplication, weak trust signals, crawl budget waste, internal linking gaps, and topical fragmentation — with the template-level remediation workflow for each; if you haven’t run that diagnosis yet, that’s the right next stop before continuing here.

What matters for this article is the bigger-picture framing: at scale, the pattern you’re seeing across positions and indexation is usually the aggregate of those same six causes, compounding site-wide. A site with thousands of thin, duplicated, or orphaned pages doesn’t just fail to index those pages individually — it depresses Google’s overall assessment of the domain’s trustworthiness and worth, which drags down ranking even on the pages that are indexed. That’s the mechanism behind the “stuck at 70–90 everywhere” feeling: it’s rarely one broken page. It’s an accumulated site-wide signal.

Step 3: The Trust-Recovery Framework

Once you’ve confirmed there’s no manual action, recovery is a sequencing problem: four layers of work, executed roughly in this order, because each one makes the next one more effective.

Content quality first. Score your URL clusters honestly against a simple rubric — uniqueness, intent match, depth, and demonstrated experience — and route anything that scores poorly into improve, merge, or remove. The target isn’t a word count; it’s genuine distinct value per URL. A hundred strategically improved pages consistently outperforms a thousand more pages that all look the same, and this is the highest-leverage layer because it addresses the root cause the other layers can’t fix around.

Duplication and canonical clarity second. Duplicate content rarely triggers a manual penalty on its own, but it dilutes indexing and ranking because Google has to choose which version of near-identical content to keep — and in scaled scenarios, duplication is very often the dominant pattern behind mass non-indexation. Pick one canonical URL per intent, enforce it with redirects or canonical tags depending on whether you need the alternates to stay accessible, noindex genuinely low-value archives, and make sure internal links point to the canonical version rather than accidentally splitting signal across variants.

Internal linking repair third. When rankings are stuck across the board, it’s frequently because Google can’t see a clear hierarchy of what matters on your site. Get your priority pages within a few clicks of the homepage, ensure every page you want indexed receives genuine contextual internal links rather than relying on pagination to surface it, and stop linking internally to non-canonical or noindexed URLs, which quietly bleeds signal you’re trying to concentrate. This is the fastest scalable lever available because it improves crawling, indexing, and ranking simultaneously without waiting on external validation.

Authority building last, and only after the leaks are fixed. Pouring earned links and reputation into a site still full of duplication and thin pages is pouring trust into a leaking bucket. Once the first three layers are addressed, build genuinely citable assets — original data, benchmarks, calculators — and identify which existing pages already attract organic links as a guide to where adjacent linkable content should go. Authority here means earned reputation and consistency, not synthetic link volume, which Google’s spam policies target explicitly.

Step 4: Should You Consider a Fresh Domain?

Almost never as a first move, and it’s worth being direct about why: a migration doesn’t erase quality problems, it moves them. If the underlying causes — thin templates, duplication, weak architecture — travel with the content to a new domain, Google evaluates the new domain against the same evidence and arrives at the same conclusion, except now you’ve also spent your accumulated brand equity and backlink history to get there.

Run this decision logic before pricing anything: Is there an active manual action? Fix and get reconsideration first — migrating with an unresolved violation can preserve the problem and create new ones. Is the indexing refusal mostly duplication or thin templates? Fix the architecture and content first; migration doesn’t cure a duplicated template, it just relocates it. Is there genuine domain-level toxicity — a history of real spam, a past hack, ongoing security issues flagged in Search Console? Address those specifically before considering anything structural. Does your current CMS genuinely prevent the fix — can it not enforce clean canonical logic, can’t support real hub architecture, generates infinite URL variants you structurally cannot control? That’s the one legitimate case for migration: moving to a platform that enables the architecture and index control your content strategy actually needs.

The distinction that matters: migration helps when it removes a genuine platform constraint you’ve confirmed is otherwise unfixable. It hurts when it’s really an attempt to “wipe the ledger” — the same content, freshly relocated, evaluated by the same systems, arriving at the same verdict.

Is Iriscale Right for Your Team?

The recovery layers that are content and architecture work — the quality audit, the duplication and canonicalization policy, the internal linking design, and the topical consolidation that prevents this pattern from recurring — are exactly what Content Architecture, Topic Strategy, and the Articles Hub run for you, with the Knowledge Base keeping the entity and voice consistency that weak-trust-signal pages typically lack. What stays explicitly outside that scope, honestly: manual action investigation and reconsideration submissions are a process only you can run in your own Search Console account, and crawl budget, server performance, and canonical implementation remain developer work.

The useful first step, whichever situation you’re in, is the same fifteen-minute check this guide opens with — confirm manual action status before anything else, because it changes every decision that follows.

Book a demo and see how Content Architecture prevents the site-wide pattern from recurring →

Frequently Asked Questions

How do I know for certain whether I have a manual action or an algorithmic issue?

Check Search Console’s Manual Actions report directly — it’s the single authoritative source, and it takes under a minute. Manual actions are always disclosed there with a labeled violation type and example URLs; there is no algorithmic equivalent that shows up in that report, because algorithmic demotions and indexing decisions are made by automated systems continuously, with no notification and no appeals process. If that report says “No issues detected,” you can rule out a manual penalty with confidence and redirect your entire recovery effort toward the algorithmic causes — content quality, duplication, architecture, and authority — rather than waiting for a reconsideration process that was never going to apply to your situation.

Can algorithmic suppression really affect a domain this severely without any penalty being applied?

Yes, and it’s the more common scenario by a wide margin for sites experiencing broad, sustained ranking suppression alongside mass non-indexation. Google’s automated quality and indexing systems evaluate content and site-wide trust continuously; a domain accumulating enough thin, duplicated, or poorly-linked pages can see its overall assessed trustworthiness depressed enough to suppress rankings across the board — including on pages that are individually fine — without any single violation ever triggering a human review. The absence of a formal “penalty” doesn’t mean the suppression is any less real or any less severe in its business impact; it just means the recovery path is systematic quality rebuilding rather than a specific fix-and-appeal process.

How long does algorithmic recovery typically take compared to a manual action reconsideration?

Manual action recovery has a defined process with a bounded, if variable, timeline — fix, submit, wait for review, typically resolved in weeks once a thorough fix is submitted. Algorithmic recovery has no defined timeline at all, because there’s no review to request; Google’s systems simply reassess your site continuously as new signals accumulate. In practice, sites executing a genuine, systematic fix across content quality, duplication, and architecture commonly begin seeing directional movement within a couple of months, with fuller recovery often taking two to three quarters depending on how deep the underlying problems were and how thoroughly they’ve actually been addressed — not partially patched. The discipline that matters most here: take a real baseline before you start remediation, because algorithmic recovery is gradual and trend-based, and without a baseline you won’t be able to distinguish real progress from noise for months.

Is it ever worth migrating to a new domain to escape accumulated quality problems?

Rarely as a first resort, and only under a narrow, specific condition: when your current platform genuinely cannot support the fix your content strategy requires — it can’t enforce clean canonical logic, can’t structure real topical hubs, or mechanically generates infinite low-value URL variants you cannot control at the CMS level. In that specific case, migrating to a platform that enables proper architecture, paired with real content pruning and correct redirects, can be a legitimate net positive. What migration will not do: erase a quality assessment built on thin or duplicated content. If the same problematic templates and content patterns move to the new domain, Google’s systems evaluate the new domain against the same evidence and typically arrive at a similar conclusion — except now you’ve also spent accumulated brand equity, backlink history, and direct traffic recognition to get there. Fix the content and architecture first; only consider migration if a genuine platform constraint remains after that work is done.

What’s the single highest-leverage fix if I only have time for one thing this month?

Internal linking repair, and specifically closing orphan pages and flattening click depth to your priority URLs — it’s the fastest lever precisely because it requires no new content creation and no external validation, only reorganizing links you already control. A site where important pages sit five or six clicks deep, reachable only through pagination, is quietly telling Google those pages don’t matter regardless of their actual quality; restructuring so priority pages sit within a few clicks of the homepage and receive genuine contextual links from your strongest existing content routinely produces the fastest visible movement in both crawl behavior and indexation status. It’s not usually sufficient on its own if content quality and duplication are also genuinely poor, but it’s the highest-leverage single move available in a resource-constrained month, and it makes every subsequent content-quality improvement more effective by ensuring Google actually finds and prioritizes the improved pages once they exist.

Related Reading

• Why “Crawled – Currently Not Indexed” Happens at Scale
• Build Topical Authority That Drives Revenue
• SEO Ranking Factors That Actually Matter in 2026
• What My Blog Traffic Dropped to Zero Diagnostic Checklist
• Grow Organic Traffic Without Publishing More Content

© 2026 Iriscale · iriscale.com · AI-Powered Growth Marketing for B2B SaaS