How Do You Run Campaign Pages in Webflow Without Making a Mess?

How Do You Run Campaign Pages in Webflow Without Making a Mess?

Decide how a page dies before you build it. Every campaign page needs an owner, an end date, and a decision about what happens at that date: redirect, keep and update, or remove. Without that third decision, a site accumulates dead pages nobody will take responsibility for deleting.

We see this on almost every site we inherit. Somewhere in the page list there are twelve landing pages for events that happened two years ago, still indexed, still linked from an old email, still showing a registration form that goes nowhere.

Here is the approach we use to keep campaign work fast without leaving that behind.

Should Campaign Pages Live in the CMS or as Static Pages?

In the CMS if there will be more than about three of them, as static pages if each one is genuinely bespoke. The deciding factor is whether the pages share a shape. A webinar page and another webinar page share a shape. A product launch microsite does not.

The CMS route pays off immediately on lifecycle. Webflow's CMS items carry isDraft and isArchived flags, which means a campaign page can exist before it is live and be retired without being destroyed. Those two booleans are most of a lifecycle system, and you get them for free.

The static route is right when the design is the point. If the page has a custom layout that will never be reused, forcing it into a collection template costs more than it saves. We covered the general version of this call in our piece on Webflow CMS versus static pages.

What Belongs in the Collection Structure?

Fields that drive behaviour, not just fields that display text. A start date, an end date, a state, and an after field that says where traffic should go once the campaign closes. Those four turn a content collection into something you can actually operate.

The end date is the one that changes everything. A campaign page with an end date can be found by a filter, which means the monthly question "what has expired" takes ten seconds instead of a manual audit. Without it, expiry is something somebody has to remember.

Keep the rest lean. Every field you add is a field somebody has to fill in under time pressure on launch day, and optional fields that are always left blank are worse than no field. We went into structure properly in our piece on content modelling for a CMS.

How Do You Stage a Campaign Before It Goes Live?

Use draft items rather than an unpublished page. A CMS item created with isDraft set to true exists in the collection without appearing on the site, so marketing can write and review well ahead of launch without anybody worrying about an accidental publish.

Be careful about what publishing means here, though. Webflow documents that publishing from staging to production "publishes all staged changes", so a campaign that is ready cannot be held back by not publishing. It is held back by being a draft. Those are different mechanisms and confusing them is how things go live early.

If the campaign involves a code change as well as content, separate the two. Ship the template and the styles in one publish, then flip the draft flag on launch day. A launch that requires a design change and a content change at the same moment is a launch with two ways to go wrong.

What Happens When the Campaign Ends?

One of three things, decided in advance. Redirect the page to the closest permanent equivalent, keep it and rewrite it into evergreen content, or remove it properly. Doing nothing is the fourth option and it is the one that creates the mess.

Redirecting is right when the page earned links or is still in circulation. A redirect keeps those signals attached to something useful and keeps the visitor's journey intact. Webflow handles this in site settings, and we walked through the specifics in our piece on 301 redirects in Webflow.

Keeping is right more often than people expect. A webinar page with a good recording and a real summary is a content asset. Deleting it because the event is over throws away work that is still answering a question somebody types.

How Do You Remove a Page Properly?

Remove the content, not just the link to it. Google's guidance is direct: the most secure way to keep something out of search is to "remove or update the content on your page", and a noindex tag "only blocks your page from showing up in Google search results", while "users and other search engines that don't support noindex can still access your page."

Google is equally clear about one common mistake: "don't use robots.txt as a way to block your page." Blocking a crawler from a page it already knows about does not remove it from results, and it removes your ability to signal anything about it.

The Removals tool in Search Console is for emergencies, not for lifecycle. Google states that "requests made in the Removals tool last for about 6 months", so it buys you time while you fix the underlying page rather than being the fix itself.

Who Owns a Campaign Page After Launch?

Whoever asked for it, by name, recorded on the item. Campaign pages are built under deadline by people who move straight on to the next campaign, and ownership evaporates the moment the launch email goes out.

An owner field costs nothing and changes the conversation months later. "Whose page is this" is unanswerable on most sites we audit, and the honest consequence is that nobody deletes anything because nobody is sure what it was for.

Pair the owner with the end date and you have a monthly review that takes fifteen minutes. Filter for items past their end date, read the owner, send three messages. That is the entire governance process.

Does Automation Help, and Where Does It Bite?

It helps for creating and updating in bulk, and it bites on publishing. Webflow's Data API rate limits are tied to the site plan: 60 requests per minute on Starter and Basic, 120 on CMS, eCommerce and Business, and custom on Enterprise, with an HTTP 429 and a Retry-After header when you exceed them.

The publish limit is the tighter one. Webflow documents that Site Publish operations "are limited to one successful publish per minute", so a script that updates thirty campaign items and publishes after each one will stall. Update everything, then publish once.

Our rule for campaign automation is that it should create and update, and a person should publish. Bulk creation from a spreadsheet is a genuine time saver. Automated publishing of marketing pages is a small saving with a large downside.

What About Pages That Come Back Every Year?

Reuse the URL rather than dating it. A page at a stable address that you update each year accumulates links and ranking history, while a new dated URL every year starts from nothing and leaves last year's page competing with it.

Keep the year inside the page content where it belongs, and use the old content by moving it to an archive item rather than leaving it live at its own address. One strong URL beats five weak ones every time.

The exception is when each year is genuinely a different thing that people search for separately. An annual report is like that. A recurring webinar series usually is not.

What Should You Do With the Dead Pages You Already Have?

List them, decide once, and execute in a single afternoon. Export your page list and your CMS items, sort by last updated, and put everything untouched for a year into one of the three buckets: redirect, rewrite, remove.

Do not try to be clever about it. The value is in having made a decision on every page, not in making the perfect decision on each one. A redirect to a sensible parent page is almost never wrong, and it is reversible.

If you are looking at a Webflow site with years of campaign residue in it and want help clearing it without losing the pages that are still working, we are happy to go through it with you. Find us at phoenix.studio.