Wholesale Portal SEO: What to Index and What to Hide
A roaster builds out a wholesale area, price lists, a login, an order form, a sample request page, and then faces a decision nobody explained clearly: should Google see any of this. Some owners answer by blocking the entire wholesale section from search, which quietly hides the one page that would actually win cafe buyers searching for a new bean supplier. Others leave everything open, including login and cart pages, which clutters search results with pages no stranger should ever land on. Both mistakes come from the same root cause: treating a wholesale section as one single thing rather than a handful of pages that each serve a different audience.
Short answer: a wholesale portal is not one thing to either fully expose or fully hide. It has three layers, a public landing page that should be indexed and found, account and order pages that should be kept out of search entirely, and price lists that sit in between and deserve their own decision. This post walks through each layer, and explains the real, documented difference between blocking a page in robots.txt and adding a noindex tag, since a blocked page can still show up in search results without either your product's content or your customer's information ever being safe.
None of this requires security expertise or a developer on staff. It requires understanding what each tool actually does, which turns out to be simpler than the confusing mix of advice floating around usually makes it sound. Once the three layers are clear, sorting a specific wholesale portal's actual pages into the right category is mostly a matter of going through them one at a time and asking who each page was written for and acting accordingly.
Rules
The public landing page is the one part of a wholesale portal that should actively want to be found. This is the page explaining that the roaster offers wholesale accounts, what that looks like, and how to start the conversation, and it should be indexed the same way any other important page on the site is, with a clear title, real descriptive content, and normal internal links pointing to it from elsewhere on the site. A cafe owner searching for a new bean supplier is exactly the person this page exists to reach, and hiding it from search defeats the entire point of having it.
It is worth being specific about how a small roaster's site map might sort into these layers, since the abstract version of this advice is easy to agree with and much harder to apply consistently once real pages are involved. Picture a roaster with a homepage, a retail shop section for individual bags, and a wholesale section underneath it. Within that wholesale section sits a landing page describing the program, a how to order page explaining the process, a sample request page for prospective buyers to try beans before committing, a login page, an account dashboard once logged in, an order form, an order confirmation page, and a price list. The landing page, the how to order page, and the sample request page all belong in the indexed, public group, since each one is written for a prospective buyer who has not yet started an account. The login, dashboard, order form, and confirmation pages all belong in the noindexed, hidden group, since none of them serve any purpose to a stranger arriving from a search result. The price list is the one page on this list that genuinely depends on what kind of price list it is.
Account and order pages sit at the opposite end, and it is worth making explicit why this matters beyond tidiness. None of these pages help a search engine understand what the roaster sells or offers, and their presence in results can crowd out the pages that would. A login screen, an actual account dashboard, an order form once someone is logged in, an order confirmation page, none of these should ever appear in search results. Nobody searching for a new coffee supplier benefits from landing on someone else's order confirmation, and a roaster gains nothing from that page being indexed either. This is where the difference between two related but distinct tools matters. A robots.txt disallow line tells search engine crawlers not to fetch a page's content at all. It does not, by itself, guarantee the page never appears in search results, since a page that is disallowed from crawling but still linked to from elsewhere on the web can still show up as a bare URL with no description, because the search engine never crawled it to know what to say about it. A noindex tag works differently: it lets the page be crawled, but instructs the search engine directly not to include it in search results at all, which is the actual, reliable way to keep a specific page out of search.
That distinction is the single most useful thing to understand from this whole post. If the actual goal is keeping a page out of search results, a noindex tag on that page is the tool that does that job. A robots.txt disallow line is a different tool, aimed at controlling crawler traffic and server load, not at guaranteeing a page's absence from search. Using the wrong one for the goal is the most common, avoidable mistake in this entire setup, and it explains why some owners are confused when they blocked a page in robots.txt and it still somehow appeared in a search result.
There is a related trap worth understanding too, since it trips up owners who otherwise did everything else right. If a page is disallowed in robots.txt and also carries a noindex tag, the two instructions can work against each other. Because a robots.txt disallow tells a crawler not to fetch the page at all, that crawler may never read the noindex tag sitting on the page, since reading that tag requires crawling the page in the first place. For any page where the real goal is exclusion from search results, a noindex tag on its own, without an accompanying robots.txt block, tends to be the more reliable choice. Reserve robots.txt disallow rules for a different purpose, controlling how much of a site's crawl budget gets spent on pages that genuinely do not need to be crawled at all, such as an internal search results page or a filtered product listing that generates near endless URL variations.
This confusion is common enough that it is worth naming directly rather than assuming it away. Robots.txt predates the noindex tag by years, and a lot of general advice about controlling what search engines see still treats robots.txt as the default answer to almost any exclusion question, simply because it was the first tool available. That history is part of why so many site owners reach for a robots.txt block first, even when a noindex tag is the tool built for the specific job of keeping a page out of search results.
Price lists sit between these two clear categories and deserve their own honest thought rather than a default answer. A general price list, one that gives a rough sense of wholesale pricing without requiring a login, can be a useful, indexable page for a cafe owner doing early research and comparing suppliers before ever reaching out. A detailed, account specific price list, one tied to a particular buyer's negotiated terms, belongs firmly in the same category as account and order pages, behind a login and marked noindex. The decision here is not about security so much as about who the page is written for. A page meant to inform a prospective buyer belongs in search. A page meant only for an existing account holder does not.
It is worth being direct about a point that gets confused often. Noindex is not a security tool and should never be treated as one. A noindex tag only tells a search engine to leave a page out of its results. It does nothing to stop someone who has the direct URL from opening that page, and it does nothing to encrypt, restrict, or otherwise protect any data that page contains. If a wholesale portal has sensitive information, negotiated pricing terms, account details, order history, that information needs an actual login requirement to be properly protected, not just an instruction telling Google to look away. Conflating these two things, keeping a page out of search results and keeping a page's contents private, is a mistake worth avoiding specifically because the consequences of getting it wrong are real.
On the platform side, the three major builders each handle this differently, and the exact click path is worth confirming against each platform's own current help documentation rather than relying on a fixed set of steps that could change. Broadly, each of the major site builders provides some setting, usually within a page's own settings panel or a broader SEO settings area, that lets an owner mark a specific page as hidden from search without needing to touch a robots.txt file directly. This is helpful for an owner without any technical background, since it turns what sounds like a developer level task into a checkbox or a toggle within a page's normal settings.
Before publishing any changes to a wholesale portal's indexing, it is worth checking the result using a structured testing tool built for exactly this purpose, which can confirm whether a specific page is set up the way it was intended, indexed pages showing as indexable and noindexed pages showing as excluded. Running this kind of check after making changes, rather than assuming the settings took effect correctly, catches the occasional mistake, a noindex tag left on the wrong page, a setting that did not save properly, before it causes a real problem either way, a landing page invisible to the buyers who should find it, or a private order page showing up somewhere it should not.
None of this decision making needs to happen all at once either. A roaster building out a wholesale section for the first time can reasonably start with the clearest cases, indexing the landing page and noindexing the login and order pages, and take a bit more time deciding on the price list once the rest of the structure is settled. Getting the two obvious categories right covers most of what matters, and the price list decision can follow later once there is a clearer sense of who the page is supposed to serve.
It is also worth revisiting this setup occasionally rather than treating it as a one time decision. A wholesale section tends to grow over time, a new sample request form, a new account tier, a new resource page for existing buyers, and each new page deserves the same sorting exercise the original pages went through. A portal that was set up correctly at launch can quietly drift out of that correct state simply because nobody thought to apply the same three layer thinking to a page added eighteen months later.
Related Reading
More from Hillcane on this topic, plus the pages on the site that sit next to the work.
Frequently Asked Questions
Should a wholesale landing page be indexed by Google?
Yes. A public wholesale landing page explaining what the roaster offers and how a cafe buyer can start a conversation is exactly the kind of page that should be found in search, since it is written for the prospective buyer this whole section exists to reach. Blocking or hiding this page from search defeats its purpose, and it should be treated with the same care as any other important page on the site.
What is the difference between robots.txt and a noindex tag?
A robots.txt disallow line tells crawlers not to fetch a page's content, but it does not reliably keep that page out of search results, since a disallowed page that is still linked from elsewhere can appear as a bare, undescribed result. A noindex tag lets the page be crawled but tells the search engine directly not to include it in results. If the actual goal is keeping a page out of search, a noindex tag is the correct tool, not a robots.txt disallow line.
Why would a blocked page still show up in a Google search?
This happens because robots.txt only controls crawling, not indexing. If a page is disallowed in robots.txt but other sites or pages link to it, a search engine can still be aware the page exists and may display it as a bare URL with no description, since it was never crawled to generate one. This confuses many owners who assumed a robots.txt block was the same as removing a page from search entirely. It is not.
Should a login page for a wholesale portal be indexed?
No. A login screen serves no purpose to a stranger arriving from a search result, and it should be kept out of search entirely using a noindex tag on that page. This is a straightforward case, unlike price lists, where there is little reason for a prospective buyer or a search engine to see the page before an account has even been created.
What about an order confirmation or cart page?
These should also be kept out of search results with a noindex tag. An order confirmation page or a cart in progress has no value to anyone arriving from search, and its presence in results only adds clutter that makes a roaster's actual useful pages harder to find. These pages belong in the same category as account and login pages, not the public landing page.
Should a general wholesale price list be public and indexed?
It depends on what the price list is. A general, rough pricing page aimed at helping a prospective cafe buyer compare suppliers during early research can reasonably be public and indexed, since it serves the same purpose as the landing page. A detailed, account specific price list tied to a particular buyer's negotiated terms should instead sit behind a login and be marked noindex, since it is not written for a general audience.
Does noindex protect private wholesale data from being seen?
No, and this is an important distinction. A noindex tag only tells a search engine not to include a page in search results. It does nothing to prevent someone with the direct link from viewing the page, and it is not a security or privacy control. Genuinely private or account specific information needs an actual login requirement, not just a noindex tag, to be properly protected.
Can a page be blocked in robots.txt and also marked noindex?
This combination is worth understanding carefully rather than applying by default. If a page is disallowed in robots.txt, a search engine may never crawl it and therefore may never see a noindex tag placed on that same page, since the tag itself has to be crawled to be read. For a page a roaster wants excluded from search, a noindex tag without a robots.txt block is generally the more reliable approach.
How do Wix, Squarespace and Shopify handle hiding a page from search?
Each platform provides a setting for this within its own page or SEO settings, typically allowing an owner to mark an individual page as hidden from search engines without needing to edit robots.txt directly. The exact click path differs by platform and can change over time, so an owner should check their specific builder's current help documentation for hiding a page from search rather than relying on a generic instruction that may be out of date.
What is the simplest way to think about a wholesale portal's three layers?
Picture three groups: a public landing page written for a prospective buyer, which should be indexed and found. Account, login, cart and order pages, written only for someone who already has an account, which should be noindexed and kept out of search. And a price list, which falls into one category or the other depending on whether it is general information for a prospective buyer or specific terms for an existing account. Sorting every wholesale page into one of these three groups covers the whole decision.
Work with Hillcane
A roaster builds a wholesale login, an order form, and a price list, then faces a question nobody explained clearly: should any of this show up on Google. The honest answer has three parts, not one.
If your roaster's wholesale portal needs its indexing sorted out properly, reach Hillcane at hillcane.co/contact or call (256) 384-2449.
Comments