Our Search Console setup guide covers connecting your store. It also covers reading the Page indexing report for the first time. This post assumes you’ve already done both. Search Console has been running for a while now. You’re looking at a growing list of pages flagged Crawled – currently not indexed. Or pages sitting flat at zero clicks for months. The question now isn’t how to connect the tool. It’s what to do with the backlog it’s handed you.

Shopify content pruning isn’t noindex vs. redirect vs. merge vs. leave alone

The bottom line: those four actions aren’t peers on a menu. They answer two different questions. Mixing them up is why so much pruning advice contradicts itself.

Most guides list noindex, redirect, merge, and leave-alone as four interchangeable options. Pick whichever feels right, they say. That framing causes real damage. Google’s own documentation on consolidating duplicate URLs is specific about this. noindex is not a tool for choosing a winner between two similar pages. “The use of noindex… will completely block the page from Search,” the guidance states. It adds that rel="canonical" link annotations are “the preferred solution” for that job. Noindex doesn’t vote for a page. It removes one entirely.

So the real decision tree has two separate questions, asked in order:

Notice that “merge” and “dead weight” never share a fix. A near-duplicate gets a redirect. There’s a better page to send its traffic and link equity to. A genuinely thin, undemanded page doesn’t have a better page waiting. There’s nothing to consolidate into. So noindex or deletion is the honest answer there instead.

Branch 1: merge the near-duplicates, redirect the loser

The bottom line: if two pages target the same intent and one is clearly weaker, fold its content into the stronger page. 301 the weaker URL. Don’t noindex it.

This is the most common shape of a pruning backlog on Shopify. A collection page and a nearly identical filtered variant. Two blog posts written eight months apart on the same keyword. A legacy landing page that duplicates a newer one almost line for line. Google’s guidance ranks the signals by strength. A permanent redirect is “a strong signal that the target of the redirect should become canonical.” A rel="canonical" annotation is also a strong signal. Sitemap inclusion is only a weak one. In practice, that means this: if you’re retiring a page for good, redirect it. If both pages need to stay reachable at their own URLs, use canonical instead. Either way, take the better material from the weaker page first — a stat, a paragraph, an FAQ answer. Move it into the page you’re keeping before the old URL disappears. Our redirects and 404 guide covers the mechanics of building the redirect itself. Our canonical URL guide covers diagnosing which of two URLs Google already treats as canonical.

Branch 2: true dead weight — noindex or delete

The bottom line: a page with nothing unique to say, no search demand, and no equivalent page to merge it into isn’t worth indexing. Decide only between keeping it reachable (noindex) and removing it (delete/410).

This is where Crawled – currently not indexed in your Page indexing report usually lands. Google looked at the page and made a judgment call. It decided the page wasn’t worth adding to the index. Not because anything is broken. Because the content didn’t clear the bar. Say there’s no stronger page to fold it into. Say there’s no real reason to keep it public — a thin old blog post with zero organic entries and zero backlinks, for example. Then you’re choosing between two exits, not four.

Noindex vs. delete: which one

Google’s documentation on removing content is direct about the difference. Removing or updating the content is “the most secure way” to keep something out of search. A noindex tag “only blocks your page from showing up in Google search results.” The page itself is still reachable to users. So is any search engine that doesn’t respect the tag. Use noindex when the page still serves a navigation or customer-service purpose — an old policy page someone might still land on directly, say. Delete it, and let it 404, when nothing depends on the URL being reachable at all.

That result isn’t magic. Removing pages that were dragging down your site’s average quality lets the pages you want ranking get more of Google’s attention. It’s also why deleting everything in one pass is the wrong instinct. Work through the backlog in stages. Worst pages first. Watch what happens before you touch the next batch.

Branch 3: underperforming but salvageable — leave it, improve it

The bottom line: a page that’s unique and gets some real demand doesn’t belong in a pruning conversation at all. Rewrite it instead.

Not every page flagged low-traffic in Search Console is dead weight. Check three things first. Does it rank for anything beyond its own product name or title? Does it have any referring domains? Has it had any clicks or impressions in the last 12 months? Clear any one of those bars, and the page usually just needs better content. A thin description expanded. A missing H2 structure fixed. An outdated stat replaced. That’s an editing job, not a pruning one. It’s the one branch where Plug In SEO’s Scanner is directly useful, flagging missing tags, thin sections, and weak titles once you’ve decided a page is worth the rewrite. The Scanner doesn’t read your indexing status; that part stays in Search Console. But it tells you exactly what’s weak on the page you’ve chosen to keep.

A Shopify content pruning audit you can run in one sitting

The bottom line: you don’t need a full site crawl to start. You need the Page indexing report and a spreadsheet.

1. In Search Console, open the Page indexing report. Export everything flagged Crawled – currently not indexed, plus anything with zero clicks and zero impressions over the last 12 months in Performance.
2. For each URL, check whether a near-identical page already exists on your store — a duplicate collection path, an older version of the same post, a variant page. If yes, that’s a merge-and-redirect candidate.
3. For what’s left, check referring domains and whether the page ranks for anything broader than its own title. Zero on both, with no business reason to keep it public, is a noindex-or-delete candidate.
4. Anything that clears either bar goes back to “improve”, not “prune”. Note what’s weak on the page. That’s your rewrite list.
5. Work the delete/noindex batch in stages, not all at once. Re-check Performance after each stage before moving to the next.
6. Re-run the whole pass quarterly, or after any large content push that’s likely to have left thin pages behind.