Google Thinks Your Multi-Step Form Is Thin Content
On this page
A multi-step form that mints a fresh URL for each step is quietly manufacturing thin pages. Step two of a quote wizard, step four of an application, the confirmation screen: each is a URL with input fields and next to no text, nothing that maps to a search query. They can land in Search Console as “Crawled – currently not indexed” or sit in the index as pages nobody searches for. Noindex the step and confirmation URLs while keeping the real content-bearing landing page indexable, or rebuild the wizard on a single URL with client-side step navigation so the thin URLs never exist.
Why per-step URLs read as thin
No one searches for “insurance quote step 4 of 6.” There is no query intent that a form-step page satisfies, and there is little content on the page to match against a query even if one existed. For search, these URLs are interface state, not documents. That is the core of the diagnosis: a page can be functional, fast and valid, and still be thin because it carries no search value.
The setup can survive on an old idea: “more pages means more chances to rank.” Indexed page count is not an asset in itself. Google’s ranking systems guide says its systems work on the page level and also use site-wide signals, and the helpful content system became part of the core ranking systems in March 2024. Interface URLs add nothing to either side of that: no page a searcher wants, and no reason for the site as a whole to look more useful.
The targeted noindex
Be precise rather than sweeping. Noindex the step URLs and the confirmation or thank-you URL, and leave the landing page indexable if and only if it has real service content: an explanation of what the form does, who it serves, what the offering is. The landing page is the thing a query can match; the steps are not.
Use a robots noindex rule on the step and confirmation templates. Internal links pointing at noindexed steps are fine; you don’t need to nofollow the “Next” button or hide the funnel from your own navigation. noindex governs whether the URL appears in search, not whether it can be linked or crawled within the flow.
One trap: don’t also block the step URLs in robots.txt. Google’s guide to blocking indexing with noindex says the page must not be blocked by robots.txt for the rule to work. If the crawler can’t fetch the page, it never sees the noindex, and the page can still appear in results if other pages link to it.
The cleaner architecture: one URL, client-side steps
The more durable answer is to remove the thin URLs entirely by moving the wizard to a single URL with client-side step navigation. The user advances through steps without the address changing, so there are no /step-2/ and /step-3/ pages to index in the first place. You are not hiding thin pages; you are not creating them.
Analytics raises an objection: a team may worry about losing funnel tracking if each step is no longer its own pageview. It doesn’t have to. Fire virtual pageviews or step events as the user advances, so the funnel reporting (start, step completion, drop-off, submit) stays intact in your analytics, decoupled from real indexable URLs. You keep the measurement and shed the thin URLs.
Sitemap hygiene
When you noindex the step and confirmation URLs, remove them from the XML sitemap. Google’s guide to building a sitemap says to include the URLs you want to see in Google’s search results. A sitemap that lists noindexed steps contradicts the pages themselves. The sitemap should list only the URLs you want indexed: the landing page stays in, the steps come out.
To be explicit about the asymmetry: keep internal links to the noindexed steps (the funnel needs them), but pull those URLs from the sitemap (the index shouldn’t advertise them).
Don’t pad the steps with text
The wrong fix is to add paragraphs of filler to each form step so it no longer “looks thin.” This treats the symptom and creates two new problems. It doesn’t make the page satisfy any search intent, because the underlying truth (no one queries for a form step) is unchanged, so the padded page is still low-value. And it degrades the experience: filler text on an input screen can slow the user, bury the fields and cost completions. You would be trading a clean fix for a worse form and gaining nothing.
Treat a form step as thin, not as a soft 404
Keep two failure modes separate, because they call for different fixes. A multi-step form’s interface pages are thin: they return 200, they are working pages, they simply carry no search value. That is not the same as a soft 404, which is a URL returning 200 while its content suggests an error or an empty page, such as a removed product with a placeholder or an empty results page. The distinction is the relationship between the status code and the content. A form step is an honest 200 for a page that exists and does its job; it just isn’t a search destination, so the correct treatment is noindex, not a 404 or 410. Search Console may still report a near-empty step as a soft 404: Google’s documentation on HTTP status codes says it shows that error when the content suggests an empty page. The treatment stays the same.
If you reflexively reach for a 404 on a form step, you break the form: a step that returns 404 is a step the funnel can’t complete. The right tool for “this page works but shouldn’t be indexed” is noindex; the right tool for “this URL represents nothing and should signal gone” is 404 or 410. Form wizards are squarely the first case. Diagnosing it correctly keeps you from applying a status-code fix to a content-value problem.
The right end state in Search Console
Reframe what success looks like in the Page indexing report. Before the fix, the step URLs may show up in “Crawled – currently not indexed” or as indexed pages with no search value. After you apply noindex, the report should list them under its noindex reason. That is the correct destination, not a regression: you told Google not to index a page that shouldn’t be indexed, and Google complied. The noindex guide itself points to the Page indexing report as the place to monitor pages where Googlebot found a noindex rule. A falling indexed-page count here reflects a deliberate choice, not a loss.
Frequently asked questions
Will noindexing my form steps lose me traffic?
It shouldn’t cost search traffic that mattered. Those URLs carry no search intent, and the page that can earn traffic, the landing page, stays indexable.
Is it better to noindex the steps or rebuild on one URL?
Rebuilding the wizard on a single URL with client-side steps is cleaner, because the thin URLs never exist, so there is nothing to noindex or keep out of the sitemap. Noindexing is the right fix when a rebuild isn’t practical right now.
Should I block the step URLs in robots.txt instead?
No. A robots.txt block stops Google from fetching the page, so it can’t see a noindex, and a blocked URL can still appear in results if other pages link to it. Use noindex and let Google crawl the steps.