Publishing a blog post makes it available on your website. It does not guarantee that Google will discover it, index it, or show it for the search you have in mind. Those are separate steps, and separating them makes troubleshooting much easier.
On the old Webflow forum, I explained both sides of this problem: Collection SEO settings belong in the Collection page template, and useful content still needs to earn its place in search. Here is a practical way to check the technical setup before rewriting every article or installing another tool.
Start with one exact URL
Choose a single published article and open its custom-domain URL in a private browser window. Check that it works without a login, displays the full article, and has not been redirected to the home page or a general archive.
Use this exact address in Google Search Console's URL Inspection tool. Record the reported status and, where available, the last crawl and Google's chosen canonical. A general search for your title is less useful as a diagnostic because results vary and an indexed page may not appear for that query.
If the URL is not indexed, investigate the reason shown. If it is indexed but receives few impressions, the next question is relevance and demand, rather than whether Webflow has published the page at all.
Set metadata on the Collection template
Open the blog Collection page from the Pages panel, then open its page settings and SEO settings. Use Add field to connect the title and description to appropriate CMS fields. This creates a reusable pattern while allowing each item to provide its own content.
For example, a title pattern might use the article's SEO title followed by the site name. A description field should describe that particular article rather than repeating a generic introduction to the business. Check several items, including older records where a newly added SEO field may be empty.
Publish the changes to the domain you want indexed, then inspect the published page. The settings saved in the Designer and the HTML currently available on the public domain may differ until publication. Webflow's metadata guide documents the dynamic field controls.
Metadata helps describe the page. It is not a guarantee of indexing, ranking, or the exact snippet Google will display.
Check access and indexing instructions
Review the published HTML and response for a noindex instruction, unexpected canonical URL, or access restriction. Inspect robots.txt as well. A page can be publicly reachable in your browser while still sending instructions that discourage crawling or indexing.
Be careful with the relationship between these controls. Blocking crawling in robots.txt is not a reliable substitute for a page-level noindex instruction, because a crawler needs access to read that instruction. Use Google's inspection reports to understand what it can actually fetch.
If you recently changed domains or slugs, inspect the old address too. A relevant redirect should lead directly to the replacement article. Sending every old article to one general page loses the specific destination a visitor expected.
Give the article a route into the site
Make sure published posts appear in appropriate internal links and your sitemap. A useful category page, a topic guide, and links between closely related articles help both readers and crawlers find deeper content.
For a large archive, try reaching a representative older article from the home page without using search. If it is effectively stranded, improve the navigation. A sitemap is useful discovery support, but it does not replace a content structure that people can follow.
Also distinguish Google from Webflow's internal site search. They are different systems. A problem with one search box does not establish a problem with the other index.
Improve the page's reason to exist
Once access and metadata are correct, review what the article actually contributes. Does it answer a specific question? Does it include the steps, limitations, or example the reader needs? Is it substantially different from other pages on your own site?
Strengthen thin or overlapping articles rather than creating more copies of the same answer. Keep instructions current, explain the result of each important step, and link to supporting material when it helps the reader continue.
Do not treat a Google Analytics installation or a particular bounce-rate number as a prerequisite for indexing. Use analytics to understand your visitors, and use Search Console to investigate search visibility. Avoid turning a diagnostic metric into a promise about Google's ranking system.
Recheck after a meaningful change
After fixing a concrete issue, republish, test the live URL, and use Search Console's available inspection and indexing tools. Keep notes so you can distinguish a new crawl from an old report. Repeatedly editing the title every day makes the result harder to evaluate.
Google explicitly says that crawling, indexing, and serving a page are not guaranteed. A sound setup removes avoidable obstacles; useful, distinctive content gives the page a stronger reason to be found.
Where this guide started
This article expands Jeff Selser's webdev replies from January 16 and 18, 2019 in “SEO in blog posts help.” It retains the advice about Collection template metadata and useful content while replacing older speculation about engagement metrics with a clearer diagnostic process.