Reducing Thin Content on a Cannabis Website

What thin looks like on a cannabis site

The usual suspects repeat across the industry. Strain pages generated from one template with a swapped name and nothing else. Blog posts written to a keyword in 200 words and never touched again. Tag and archive pages a CMS mints automatically. City pages that exist for the city name alone, with no store, no inventory, and no local detail behind them. None of these fail because they are short; they fail because a searcher who lands on one learns nothing they could not get from the title.

Build the inventory before touching anything

Two data sources find nearly all of it. A Screaming Frog crawl exports every URL with its word count and title, which surfaces the template-generated bulk. Search Console's page-level report shows which URLs earned zero clicks over the past twelve months, and the overlap between low word count and zero clicks is your working list. Put it in a sheet with one column for the verdict. Deciding page by page sounds slow and is actually fast; most verdicts take seconds once the page is in front of you.

The three verdicts

Expand when the topic deserves its own page and the content just never got written — a strain page for something you actually sell, covering lineage, terpenes, and tested potency, is worth the effort. Merge when several weak pages circle the same intent: combine them into the strongest URL and 301 the others to it. Remove when nothing on the page is worth saving; delete it, return a 404 or 410, and redirect only if the URL has external links or steady impressions worth preserving.

Merging deserves the extra word, because it usually beats deleting. Three thin posts about storing flower, storing edibles, and storing concentrates split what should be one ranking across three URLs, and each cannibalizes the others. Merged into one substantial storage guide with 301s from the old URLs, their signals consolidate — links, history, and the modest authority each page collected now push a single page that can compete. Deletion throws that accumulation away. Reserve it for pages that never earned anything to preserve.

A worked example

A client's blog held roughly 90 strain posts, each 150-250 words from the same template, and Search Console showed all but a handful with zero clicks for the year. We grouped them by lineage family and merged them into twelve substantial guides, each covering related crosses with real detail on genetics, terpene profiles, and what the client actually stocked. Every retired URL got a 301 to its guide. The twelve pages began ranking within weeks for terms the ninety never touched, and crawl stats showed Googlebot spending its visits on pages that now deserved them.

Frequently asked questions

Is there a word count that stops a page being thin?

No. Thin describes value, not length — a 120-word page that fully answers its query is fine, and 900 words of padding around no answer is still thin. The test is whether the page tells a searcher something the title alone does not.

Will removing pages cost me traffic?

Pages with zero clicks for a year have no traffic to lose, which is exactly what the audit confirms before anything is removed. Redirect the exceptions: any URL holding external links or steady impressions keeps its value through a 301.

Can thin pages drag down the rest of the site?

Yes. Google has said its helpful-content signals are evaluated sitewide, so a large mass of weak pages colors how the strong ones are judged, and crawl time spent on stubs is not spent on the pages that earn revenue.