What Should You Check on a Webflow CMS Post Before You Publish?

What should you check on a Webflow CMS post before you publish?

Six things, in ten minutes. The slug, the first forty words, every internal link, snippet eligibility, the excerpt as a standalone sentence, and one action in Search Console afterwards. This is the check I run on a finished post that is sitting in the CMS with the publish button waiting.

I am writing this for one specific situation, because generic launch checklists do not help here. Your site is already live. Your template already works. You have written one article and you are about to add it to a collection that already has other articles in it. That is a narrow, repeatable job, and it deserves a narrow, repeatable check.

Across more than 350 published articles the thing I have learned is that the expensive mistakes are all made in the last two minutes, by someone who is finished and wants to be done.

Step one: does the slug read like the thing it is?

Read the slug out loud without the title. If a stranger could guess the topic from it, keep it. If it contains a word you added for search reasons that a human would never say, remove it. Then check it against the posts you already have, because near duplicate slugs are how archives become unnavigable.

The reason this is step one rather than step five is that the slug is the only field on this list you cannot cheaply change later. Everything else on a CMS post can be edited in place forever. Change a slug after publication and you have broken every link anyone made to it, including your own internal links from other posts.

My rule is that a slug should survive a rewrite of the article. If I might substantially change the angle in a year and the slug would then be wrong, the slug is too specific. Name the problem, not the take.

Step two: is the answer in the first forty words?

Open the post and read only the first paragraph after the first heading. If it sets up the question without answering it, rewrite it. The opening should state the answer plainly, then the rest of the piece earns it. This is the single highest leverage edit on the list.

The reason is mechanical rather than stylistic. Retrieval systems and readers both sample the top of a page before committing to it, and a paragraph that spends its first sentences clearing its throat gives neither one anything to hold. A direct opening also makes the rest of the article easier to write, because you now have a claim to defend.

The test I use is whether the opening paragraph would work as the entire answer if someone read nothing else. If it would, the article has a spine. If it would not, I am usually still deciding what I think.

Step three: do the internal links actually resolve?

Click every internal link in the post. Not hover, click. On a CMS blog the most common silent error is a link to a slug that was renamed, never published, or typed from memory, and the post looks perfect in the editor while the link is dead on the live site.

This is also the moment to check the direction of your links. A new post should point to older posts that give it context, and after publishing, at least one older post should point back. One way linking is how good articles end up orphaned. If your site has grown past the point where you can hold the structure in your head, controlling what goes into your sitemap is the companion discipline.

I check link targets against the list of slugs that are actually published, not against what I remember writing. Memory is the least reliable tool in this entire process.

Step four: is the page snippet eligible?

Confirm the post is not inheriting a directive that suppresses its preview. Google's documentation states that nosnippet will also prevent the content from being used as a direct input for AI Overviews and AI Mode, and that max-snippet set to zero is equivalent to nosnippet.

That matters more than it used to, because Google's AI features documentation says a page must be indexed and eligible to be shown in Google Search with a snippet in order to be eligible as a supporting link in AI Overviews or AI Mode. Snippet eligibility is not a cosmetic setting. It is the gate.

On a CMS blog this is almost always a template level problem rather than a per post one, which is why it is worth checking once properly and then trusting. Check where your head code and SEO fields are set for the collection template, and confirm what a published post actually emits. Webflow's own documentation is the right reference for where those settings live on your plan.

Step five: does the excerpt work as a standalone sentence?

Read the excerpt with the title hidden. If it only makes sense as a continuation of the headline, rewrite it. The excerpt travels without its title constantly, into listing pages, previews, feeds, and shared links, and an excerpt that depends on context it does not carry simply fails in all of those places.

Keep it under the limit your template respects and make it a complete thought with a verb. The common failure is a fragment that describes the category rather than the article, something like a note on pricing strategy, which tells a reader nothing they did not already know from the title.

I write the excerpt last, deliberately, because by then I know what the article actually argued rather than what I intended it to argue. Those are different more often than I would like.

Step six: what do you do in Search Console after publishing?

Inspect the URL once, and then stop. Google's documentation describes the URL Inspection tool as providing information about Google's indexed version of a specific page and letting you test whether a URL might be indexable, with a live test that fetches and examines the URL in real time.

Know which view you are reading. Google says the indexed inspection reflects the most recently indexed version of a page, not the live version on the web, which is exactly why a fresh post shows as not indexed while looking perfectly healthy in the live test. Those are two different questions and people routinely panic at the wrong one.

You can request that a URL be crawled, but manage your expectations honestly. Google's own documentation says indexing typically takes only a day or so but can take much longer in some cases, that submitting a request does not guarantee the page will appear in the index, and that there is a daily limit to how many index requests you can submit, with a sitemap preferred for multiple pages. Notably, the documentation says nothing about whether repeated requests help, so I do not repeat them and I would not tell you they hurt either. Set up Search Console properly once and let the sitemap do the routine work.

How long should this whole check take?

Ten minutes on a normal post, and it should get faster. Steps four and six are mostly template level and become a glance once you have verified them on your collection template. Steps one, two, three, and five are per post and are where the real time goes, with the link check usually the longest.

If a check routinely takes you longer than that, the problem is upstream. Slugs taking five minutes means you are deciding the angle too late. Link checks taking ten means your internal linking is being improvised rather than planned. The checklist is diagnostic as well as preventive.

I would also resist the urge to grow this list. Every checklist I have seen die was killed by additions, each of which was individually reasonable. Six items get run. Twenty items get skipped, and a checklist you skip is worse than none, because it gives you the feeling of having checked.

What should you do next?

Take your most recent published post and run all six steps on it now, after the fact. You will find something, and whatever you find is the item worth putting first on your own version of this list. Then run it on the next post before you publish rather than after.

If you publish on a schedule, put the template level items on a monthly review instead of a per post one, and verify against the live site rather than the Designer. Staging and published output can differ in ways that only show up when you view the real page.

And if you have a blog that has grown faster than its process and you would like someone to look at what your template is actually emitting, reach out. It is usually a short job with a clear answer.