Maxxing Out your SEO in Webflow

How to Hide Unneeded CMS Pages

Overview
Introduction & Concepts
Terminology
000
High Value v. Low Value Traffic
002
Launching a New Site
The Site Launch SEO Checklist
051
Weblfow's SEO Features
051
Coming Soon Page
052
Developing Your Strategy
Mike's 4 Laws of SEO
100
Know Your Keyword Targets
101
RULE 1 - Make Your Site Easy to Find
Make Your Site Easy to Find
150
RULE 2 - Make Your Site Easy to Index
Domains, Page Titles, H1s, and Slugs
201
Page Titles
202
Page Descriptions
204
Add Basic OpenGraph Tags
210
RULE 3 - Make Your Site Relevant
Make Your Site Relevant
301
RULE 4 - Fine-Tune Your SEO
Fine-Tune Your SEO
380
Open Graph ( og: )
What is Open Graph?
400
How to Specify Global & Fallback og:images on Collection Pages
6:40
401
Debugging Open Graph
410
Debugging Open Graph Images
10:24
411
Fixing SEO Problems
Global Canonical URL Problems
2:27
851
TIP - How to Find Your Canonical URL
5:00
852
How to Hide Unneeded CMS Pages
6:29
853
Google Won't Index My Site
854
Google Search Console
855
Google Won't Display my META Description
4:47
855
Google SERPs Icon
856
Published
Updated
November 8, 2022
in lightbox

The Problem

You have a collection, but only some of the items need a Collection Page. The others are largely blank because those items don't have the content you want. Your goal is to;

  • Hide content on those pages so that they do not appear as blank content, if someone comes across them.
  • Suppress search engines from indexing those useless pages.
  • Filter your collection lists throughout the site, so that you don't navigate people to those blank pages.

Solution #1

Here's an easily implemented solution, which I've built a cloneable to demonstrate.

Basically you add a special field to your Collection, and a few tweaks to your Collection Pages so that search engines won't index the blank ones.

I recommend this approach if MOST OF your pages are used, and only a few of them need to be suppressed.

Solution #2

Separate out your "special" content into a separate collection.

For example, you might have a table of employees, some of whom also perform a recruiting function, and have a bio page for contacting them.

Here you could have two collections, C1 and C2.

  • C1 is Team Members in the company
  • C2 is Recruiters, which is a subset of the Team Members

Set it up so that C1 has all of the general employee information, and C2 has the recruiter-specific information. Add a single-ref link from C1 to C2.

This makes it easy to;

  • Identify which team members in C1 are recruiters and have a bio page in C2. You can easily display a button next to those collection list items and even pull C2 data ( like a linked-in URL ) into the collection lists displaying C1 content.
  • Avoid blank pages entirely.
  • Ensure that the sitemap.xml has only useful collection pages

One small downside here is that because C2 pages need to be able to display on their own, they may need some duplicate content ( like the team member's name ) with C1.

I recommend this approach when only a few of the C1 items need a page.

Tips

  • You can use the same slug in both C1 and C2, for consistency, but you'll have to maintain that if you ever change them.
  • It's possible to also have a single ref field from C2 to C1, so that you can link data in both directions... but this is somewhat ugly to administer in Webflow.

Resources

Videos
No items found.
Table of Contents
Comments
Did we just make your life better?
Passion drives our long hours and late nights supporting the Webflow community. Click the button to show your love.