Why do new CMS items share the same title?
Audit the published domain, a static service and at least two CMS items. This distinguishes template problems from missing values on a particular item.
What to do step by step
A practical example
One CMS item has a description while another leaves it empty. Test both to see whether the template supplies a useful fallback or missing metadata.
A common mistake
The editor preview is not the production response. Custom head code can duplicate tags already managed by the platform.
Try the report before checking your site.
Explore the sample report, then enter your own URL to see findings, HTML evidence and a repair plan for your page.
Run your audit
fukamo.com/skSeptember 16, 2026
59/ 100
HTML response size · Fukamo 200 kB budget
- Evidence
- 314476 bytes of decoded HTML; this is not the transferred compressed size.
- Repair
- Reduce unnecessary HTML and inline data. The 200 kB threshold is a Fukamo budget, not a Google limit or compressed transfer size.
Inline JS size · Fukamo 64 KiB budget
- Evidence
- 4 blocks; 179621 bytes before transfer compression.
- Repair
- Reduce inline data exceeding the Fukamo 64 KiB budget. Compare an external cacheable file and measure the impact.
ImageObject · basic data
- Evidence
- 1 entity. Missing data ImageObject #1: contentUrl.
- Repair
- Check appropriate properties for this type. Checking a selected set does not replace complete validation or establish rich-result eligibility.
Illustrations have the context they need
- Evidence
- 1 of 1 figure element has no text figcaption.
- Repair
- Add a caption where the image needs explanation. Figcaption is optional and does not replace alt.
Which fields should a Webflow CMS template include?
A portfolio needs more than a gallery. Give editors fields for the brief, constraints and actual contribution so projects do not become interchangeable pages.
- Compare two projects with different purposes.
- Separate missing data from an unconnected CMS field.
- Choose a sharing image that represents the project.
How to test dynamic SEO titles with missing CMS fields
Webflow Collection pages support shared SEO title and description patterns. Test the resulting sentence, not only whether a field binding exists.
- Check a short name and a long name.
- Leave an optional location empty.
- Look for repeated separators or unsupported promises.
Check heading semantics and content revealed by animation
A large label is not necessarily an H1. Inspect actual heading elements and confirm that important text stays available when an animation does not run.
- Read the outline without relying on font size.
- Check reused contact blocks in context.
- Try keyboard, mobile and reduced-motion navigation.
How to verify Webflow SEO after publishing
The editor preview and published domain can differ. Check canonical, links and social images after publishing the intended version.
- Record the exact public URL.
- Inspect custom head code for duplicate declarations.
- Test old project paths after a CMS migration.
How to verify the result
Publish to the public domain and inspect two CMS items with different field completeness. Verify heading structure, metadata and the keyboard path through any interaction that reveals important content.
Primary documentation help.webflow.com ↗
Frequently asked questions
Why do new CMS items share the same title?
A template may use static text or an empty dynamic field with a shared fallback. Check field bindings and test both a complete item and one missing an optional field. Editing a single item does not fix shared template logic.
When the task is complete
Two distinct published items have accurate, distinct titles and descriptions. Missing fields do not create incomplete promises or duplicate defaults, and the production domain shows the change.
Related SEO guides
Check a specific page.
Fukamo shows findings, evidence and the next step.
836 rules + SEO, AI readability, performance and accessibility measurements for free.