Webflow SEO checker: diagnose URLs and metadata

A Webflow SEO check should sample one static page and two Collection items. Use the custom domain serving real visitors, since staging can expose different content or publication settings.

Compare canonical output on subpages

Read the canonical on the static page and a CMS item. Two elements suggest custom code or an injected tag competing with Webflow's settings. An old hostname calls for reviewing the default domain and global canonical base. After correcting the configuration, publish and request the URL again. Saving a change inside the Designer does not establish that production now serves it.

Exercise Collection fallback values

Choose a complete item and another missing an SEO description. Record title, description, and H1 to expose patterns that produce empty or repetitive output. Correct the responsible field binding or fallback rather than replacing every item's metadata with one fixed string. Establish whether the item is published and indexable before attributing its absence from a sitemap to a platform defect.

Follow a legacy slug after release

Request an old address still used by an article or partner. Record redirect hops and verify that the destination has the same purpose. If the old route returns 404, add an appropriate redirect in the site's configuration. Review menu and Collection links too: a redirect is not a substitute for correcting internal references. Preserve before-and-after crawl results to show whether the fix changed editorial data, the shared template, or the global domain configuration.

A worked publishing scenario

Illustrative scenario: a static page has the correct canonical while a CMS item still names a previous domain. Compare global configuration with Collection-template metadata and custom code. Publish the targeted change and request a second item. A corrected static page does not prove that CMS output changed as well. Save the two item addresses and their returned canonical values so the release can be reviewed without access to the Designer session.

Run a check and interpret the evidence

Submit one representative public URL to the free SEO checker below. Record its status, title, description, and canonical alongside the exact address and time of the check. Group repeated issues by their responsible template or configuration so a single targeted fix can be retested on multiple pages. A missing field and an intentional exclusion need different decisions.

An HTTP/HTML audit observes public responses. It does not sign into the platform, inspect every administrative setting, reproduce every client-side rendering behavior, or prove that Google has indexed a page. For search-engine evidence, compare Search Console URL Inspection and subsequent crawl data. Recheck the original URL after publication and cache refresh instead of interpreting a changed score alone as proof that the underlying issue is resolved.

Tools and related guidance

• Read the Webflow configuration guide
• Check a public URL
• Inspect a redirect chain

Official references

• Webflow: canonical tags
• Webflow: default domain