---
title: "Thin pages after a site change: what to check first"
description: "Use the Page indexing report and URL Inspection to find affected URLs. Then improve, redirect, noindex or remove each page, based on its purpose."
url: "https://webleveling.com/blog/thin-pages-after-a-site-change/"
lang: "en"
published: "2026-10-28"
modified: "2026-10-28"
author: "Cal Hewitt"
tags: ["seo","website-maintenance","web-design"]
image: "https://webleveling.com/og/blog-thin-pages-after-a-site-change.jpg"
alternates:
  es: "https://webleveling.com/es/blog/paginas-delgadas-tras-un-cambio-de-sitio.md"
---

# Thin pages after a site change: what to check first

Use the Page indexing report and URL Inspection to find affected URLs. Then improve, redirect, noindex or remove each page, based on its purpose.

![A brass magnifying glass resting on a closed linen-covered notebook on a plain wooden desk.](https://webleveling.com/blog/thin-pages-after-a-site-change/thin-pages-featured.jpg)

Your traffic dropped after the redesign, and now you are wondering whether thin content after website redesign is the reason. Maybe the new site made tag pages nobody asked for, or a plugin started publishing a page for every uploaded photo. It is a fair worry, and you can check it this afternoon.

Open Search Console, find the Page indexing report, and write down the count for each reason Google lists. Then inspect a few URLs from the biggest groups. Every page you find gets one action based on what it is for: improve it, merge it with a permanent redirect, keep it out of search with noindex, or remove it.

Some of what you find will be harmless, and some may be the cause. You do not need to know which before you start counting.

**Key Takeaways**

**Start with counts, not rewrites**

Record the number of URLs under each Page indexing reason, then inspect three representative URLs for the Google-selected canonical, the last crawl and the visible content.

**A status is a clue, not a verdict**

"Crawled - currently not indexed" means Google crawled the URL and did not index it. That does not prove the page is thin.

**One page, one action**

Improve a page with a real purpose, merge true duplicates with a permanent redirect, noindex useful pages that should stay out of search, and remove pages with no purpose and no replacement.

**Noindex does not pick a canonical**

When two URLs overlap, name the preferred one with a canonical tag or a redirect, not a noindex on the other.

**Timing comes in ranges**

Google gives days for some changes, a few weeks for URL changes on small and medium sites, and months for broader reassessment. Recovery is not guaranteed.

## The Page indexing report shows you which pages to look at in ten minutes

Open Search Console, choose the correct property, then go to Indexing and Page indexing. Google's [Page indexing report](https://support.google.com/webmasters/answer/7440203) lists every reason a URL is not indexed, with a count beside each one. Write those counts down today, before you change anything, so you have a starting point to compare against later.

These are the reasons worth recording, because they are the ones most tied to thin, empty or duplicate pages:

- Crawled - currently not indexed
- Discovered - currently not indexed
- Duplicate without user-selected canonical, and Duplicate, Google chose different canonical than user
- Soft 404, and Page indexed without content
- Excluded by noindex tag, Blocked by robots.txt, and Page with redirect

Also note any server, redirect, access or sitemap errors. Counts alone do not prove a problem. A large number under one reason matters most when the pages in it are ones you want customers to find, or when the number jumped around the time of the site change.

![A small stack of blank index cards sorted into three neat piles on a plain wooden desk.](https://webleveling.com/blog/thin-pages-after-a-site-change/thin-sorted-index-cards.jpg)

Count the reasons first, then sort the pages.

Next, pick three representative URLs, one from each of your largest groups, and paste each into the [URL Inspection tool](https://support.google.com/webmasters/answer/9012289). Compare the canonical Google selected with the one you intended. Check when the page was last crawled. Run the live test and look at whether the page has meaningful visible content, not just a header and footer.

Those three inspections tell you more than a spreadsheet of a thousand rows. They show whether you are looking at a content problem, a canonical problem or a delivery problem.

## Each Search Console status points to a different kind of problem

The labels in the report sound alarming, and several of them overlap with thin pages only loosely. Read each one for what Google says it means, then choose a first move. Do not rewrite anything until the status and the page agree on what is wrong.

What each status means and where to look first

| Status | What Google means | First move |
| --- | --- | --- |
| Crawled - currently not indexed | Google crawled the URL and did not add it to the index | Inspect the page. Check its content, canonical and links before calling it thin |
| Discovered - currently not indexed | Google knows the URL but has not finished crawling it | Confirm the page has internal links and a sitemap entry |
| Duplicate without user-selected canonical | Google sees a duplicate and the site did not clearly name the preferred version | Add a canonical tag to the version you want shown, or redirect the duplicate |
| Duplicate, Google chose different canonical than user | Google picked another URL than the one you named | Use URL Inspection to compare the two, then decide which page deserves to win |
| Soft 404 | The page looks missing or nearly empty although it returns a success status | Add real content, or return a true 404 or 410 |
| Page indexed without content | Google indexed the URL but could not see content, which can point to a rendering, delivery or empty-content problem | Check the live page, templates and blocked files |

Two of these deserve extra care. "Crawled - currently not indexed" is a decision by Google, not a diagnosis. It can apply to a genuinely empty tag archive, and it can also apply to a decent page that Google simply has not chosen to index yet. "Discovered - currently not indexed" is even earlier in the process, because Google has not finished crawling the URL at all.

Google's [canonicalization documentation](https://developers.google.com/search/docs/crawling-indexing/canonicalization) explains that duplicate pages are grouped into a cluster, one representative URL is selected, and the others are generally crawled less often. Duplicates are not automatically a spam violation. They become a problem for you when the wrong version represents the cluster, or when so many similar URLs exist that your reports get hard to read.

## Every affected page gets one action, chosen by what the page is for

Once you know which URLs are affected, resist the urge to apply one fix everywhere. Deleting every low-traffic page, noindexing everything flagged, or redirecting everything to the homepage are all the same mistake in different clothes. Google's guidance asks whether a page offers original information and a substantial, complete description of its topic, so the question for each URL is what the page is for and whether anyone needs it.

There is no word count that makes a page thin. A short page that fully answers a real question is fine, and a long page that says nothing new is not. Four actions cover almost every page you will find.

### Improve a page that serves a real need

If customers search for this service, product or question, and the page says too little to help them, add what is missing. That means original details such as your process, your pricing logic, photos of your own work, and answers to the questions callers actually ask. Google's [helpful content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) says its systems prioritize helpful, reliable information created to benefit people. A page with a real purpose and thin content is an improvement job, not a deletion job.

### Merge true duplicates with a permanent redirect

When two URLs serve the same purpose and one page can cover both, keep the stronger page and send the other to it with a 301 or 308 redirect. Google's [redirect documentation](https://developers.google.com/search/docs/crawling-indexing/301-redirects) describes permanent redirects as the tool for replacing outdated URLs and removing a page in favor of a new one. Send the old URL to a page that truly replaces it. A redirect to an unrelated page, or to the homepage, can end up looking like a soft 404.

Near-identical service pages are a typical example. Our post on [updating, merging or deleting old pages](https://webleveling.com/blog/update-merge-or-delete-old-pages/) covers that choice in more detail, and the one on [duplicate content on a small business website](https://webleveling.com/blog/duplicate-content-on-a-small-business-website/) covers how overlapping pages compete.

### Use noindex for useful pages that should stay out of search

Some pages should exist for visitors but not appear in Google, such as internal utility pages. Google's [noindex documentation](https://developers.google.com/search/docs/crawling-indexing/block-indexing) describes noindex as a meta tag or HTTP header that stops supporting search engines from indexing a page. It is not the tool for picking between two duplicates. For that, point to the preferred version with a [canonical tag](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) or a redirect.

![Two matching cardboard boxes side by side on a shelf, one empty with its flaps open and one closed and taped.](https://webleveling.com/blog/thin-pages-after-a-site-change/thin-empty-and-sealed-boxes.jpg)

Keep what customers need, and take the rest out of the way on purpose.

### Remove a page that has no purpose and no replacement

An empty archive that nobody needs, with nothing to redirect it to, can simply go. Return a 404 or a 410. The HTTP standard, [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html), defines 404 as "Not Found" and says 410 is preferred when the resource is known to be permanently gone. On WordPress sites, image attachment pages can fall into this group, and our guide to [WordPress image attachment pages](https://webleveling.com/blog/wordpress-image-attachment-pages/) walks through the options.

## A redesign leaves a few usual fingerprints, so check them in order

When traffic falls right after a site change, the cause is not always thin pages. Google's [guidance on debugging traffic drops](https://developers.google.com/search/docs/monitor-debug/debugging-search-traffic-drops) starts by working out whether traffic really fell, which pages and queries lost clicks, and whether the change altered URLs. A missing redirect can look like a thin content problem in the reports, so rule these out as you go.

Work through them in this order, starting with the problems that can do the most damage fastest.

1.  **Old URLs without redirects.** Compare your pre-change URL list to the new one. Important old pages that changed address need a one-to-one permanent redirect to their equivalent.
2.  **Accidental noindex or robots changes.** A migration, plugin or SEO setting can add noindex or change robots directives. Check the page source and response headers of a few key pages.
3.  **Wrong canonicals.** Canonical tags that point to the homepage, an old URL or the wrong service page tell Google to ignore the page you care about.
4.  **Stale sitemaps and internal links.** If the sitemap and menus still reference obsolete URLs, Google keeps visiting pages that no longer matter.
5.  **Newly exposed empty pages.** Tag, category, author, attachment, filter and search-result pages may have become crawlable, and some service pages may share almost identical copy.

Also check for pages that return a success status but load blank or with only script-driven content, and for removed pages that were redirected somewhere unrelated. Google's [crawling troubleshooting guide](https://developers.google.com/search/docs/crawling-indexing/troubleshoot-crawling-errors) and its [site move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) cover these cases.

![A key ring with several unlabeled keys laid on a closed notebook next to a single open padlock.](https://webleveling.com/blog/thin-pages-after-a-site-change/thin-keys-and-padlock.jpg)

A redirect, a tag or a canonical that was switched, moved or left behind can look like thin content.

## Some excluded pages are correct, so leave them alone

A long list in the Page indexing report can feel like a failure notice. It usually is not. Google says it is acceptable for a URL to stay out of the index when the reason is expected, such as a noindex tag, a duplicate URL, or a removed page that returns 404. A page count that is larger than your indexed count is not automatically a quality problem.

Four things deserve less worry than they get:

- **A 404 for a removed page with no replacement.** Google's [404 help page](https://support.google.com/webmasters/answer/2445990) treats this as normal for pages that no longer exist, and it needs no repair.
- **A noindex page that should stay out of search.** If you put it there on purpose, it is working.
- **Duplicate URLs that Google has grouped.** Only the canonical version normally shows, and that is the system doing its job.
- **Pages with little traffic.** Low traffic alone is not a reason to delete a page that serves a purpose.

Focus on four things instead: important pages that are unexpectedly excluded, broken migration signals such as missing redirects, empty pages exposed at scale, and any measurable loss you can tie to specific URLs.

## Recovery takes days to months, and Google does not guarantee it

Fixing the pages is the first half. The second half is waiting, and Google gives ranges instead of a schedule. For URL changes on a small or medium-sized site, Google's [site move documentation](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) says it can take a few weeks for most pages to move, and longer for larger sites. Its guidance on traffic drops says some changes take effect in a few days, while broader reassessment of quality can take several months.

For canonical problems, Google's [canonicalization troubleshooting guide](https://developers.google.com/search/docs/crawling-indexing/canonicalization-troubleshooting) says pages can stay in a duplicate cluster for up to two weeks after content changes, and clearer differences between pages generally help them separate faster. None of this amounts to a promise. Fixing indexing problems makes your pages eligible to rank again, and it does not guarantee they will.

![A sand timer standing on a bare desk beside a small potted succulent.](https://webleveling.com/blog/thin-pages-after-a-site-change/thin-sand-timer.jpg)

Change one group of pages at a time, then give Google weeks before judging the result.

To keep the wait useful, change one group of pages at a time and write down what you did and when. Then compare clicks, impressions, indexed status and leads for just those URLs. If you change everything at once, you will never know which fix mattered.

## Paid help makes sense for specific situations, and a rewrite package is not one of them

You can complete the first diagnosis yourself with Search Console, URL Inspection, a list of your old and new URLs, and a look at a few page sources. That is enough to know which reasons are growing, which pages are affected and what each one is for. Nobody should sell you mass deletion, hundreds of rewrites or a guaranteed recovery period before those facts are known.

Paid help earns its place in a handful of situations: a large number of affected URLs, a complex migration, conflicting output from your CMS and plugins, server-rendering problems, several properties to reconcile, redirects lost from earlier site versions, or a need to connect technical changes to leads and revenue. In those cases the value is a defensible URL inventory, clear old-to-new mapping, the least destructive fix for each group, and monitoring afterward. It is reduced risk and clear accountability, not a secret recovery switch.

**Quiz: Which action fits the page?**

1. Search Console lists a tag archive with no posts in it under "Crawled - currently not indexed." What does that status prove?
   - The page is thin and Google has penalized the site
   - Google crawled the URL and did not index it, so you still need to inspect the page **(correct answer)**
   - The page must be redirected to the homepage
   - The page needs at least 300 more words
2. Two near-identical service pages both serve the same customer need. What is the cleanest fix?
   - Add noindex to one so Google picks the other
   - Keep the stronger page and send the other to it with a permanent redirect **(correct answer)**
   - Delete both and start over
   - Leave both and wait
3. A removed page has no replacement and no purpose. What should it return?
   - A 301 redirect to the homepage
   - A 200 status with a blank page
   - A 404 or 410 **(correct answer)**
   - A noindex tag on a live page

## Frequently Asked Questions About Thin Content After Website Redesign

**What is a thin page?**

A page with little useful, original information for the person it is meant to serve. There is no universal word count that defines it. Ask whether the page gives a substantial, complete answer to a real need.

**Does "Crawled - currently not indexed" mean my page is thin?**

No. It means Google crawled the URL and did not add it to the index. Inspect the page, its canonical and its internal links before deciding what to change.

**Should I delete duplicate pages?**

Only when a page has no separate purpose and needs no replacement. Otherwise merge it with a permanent redirect, set a canonical, or improve it so it stands on its own.

**When should I use noindex?**

Use it for pages that should stay available to visitors but should not appear in Google Search. Do not use it as your way of choosing between two duplicate pages.

**When should I use a 301 redirect?**

Use a permanent redirect when an old URL has a relevant replacement or has been merged into another page. Redirecting unrelated pages to the homepage can look like a soft 404.

**How long will recovery take?**

Google gives ranges: days for some changes, a few weeks for URL changes on small and medium sites, and months for broader reassessment. Recovery is not guaranteed, so judge each fix by its own URLs.

## Wrapping Up

After a redesign, plugin change or platform move, the Page indexing report and URL Inspection tell you which URLs Google skipped, doubled up or found empty. Each status points to a different cause, and none of them alone proves a page is thin. Give every affected page one action: improve it, merge it with a permanent redirect, noindex it, or remove it. Fix missing redirects, stray noindex tags and wrong canonicals first, since they can cause the most damage the fastest.

When you finish, you will hold a list of affected URLs, one action beside each, and an order for doing them. The pages that are excluded on purpose will be marked as fine, and you will stop treating them as emergencies. That is a calmer position than the one you started in, and a much cheaper one than a blanket cleanup.

If the list is long, the migration was complicated, or you want someone to trace the cause with you, [Web Leveling](https://webleveling.com/) can help. Our [search engine optimization](https://webleveling.com/services/search-engine-optimization/) work starts with the URL inventory and the Search Console reasons, and we will tell you if the fix is small enough to do yourself. We work with small and medium businesses across the country and overseas. [Send us your list of affected pages](https://webleveling.com/contact/), and we will help you sort out which ones to fix first.

## Terms

Words used in this post

Tap a term to see what it means.

**Page indexing report.** The Search Console report that lists which URLs are indexed and why others are not.

**Canonical URL.** The version of a page that Google treats as the representative one when several URLs show the same content.

**Noindex.** A meta tag or HTTP header that tells supporting search engines not to include a page in their index.

**Permanent redirect.** A 301 or 308 response that sends visitors and Google from an old URL to its replacement.

**Soft 404.** A page that looks missing or nearly empty to Google even though it returns a success status.

**410.** An HTTP status for a resource known to be permanently gone.

- [Old outbound link to a spam site: does it hurt SEO?](https://webleveling.com/blog/old-links-to-a-site-that-changed-hands/): Remove or replace an old link that now points to a spam site so visitors stop landing on it, then check the rest of your outbound links in one pass.
- [Keep a page out of Google search: noindex or a password](https://webleveling.com/blog/block-indexing-of-link-shared-content/): Shared quote or price sheet showing in Google? Check it with a site search, then use noindex if people need the link, or a password if it is confidential.
- [Search Console indexing report not updating: check pages first](https://webleveling.com/blog/search-console-page-indexing-report-stuck/): Google has given no cause or fix date for the Page indexing report. Check your key pages with URL Inspection and the Performance report while it catches up.