Webflow SEO tool for CMS and static pages

Why on-page SEO is slow to fix in Webflow

Webflow gives you clean HTML and good SEO controls. The catch is where those controls live. Static pages and CMS items are handled in different places, and every fix ends with a publish.

• Static pages, one at a time. Each static page has its own SEO title and meta description in Page settings. Updating 40 landing pages means opening Page settings 40 times.
• CMS template formulas. Collection template pages usually build their title and description from CMS fields. One formula covers every item, so all your blog posts may share the same pattern, and items with an empty field get a weak or empty description.
• Fields that were never added. If a collection has no meta description or SEO title field, adding one means editing the collection schema and then filling it in for every item.
• Headings are design choices. Designers often pick heading levels for looks. A page can end up with the H1 on a small label, or two H1s in different sections.
• Alt text per asset. Alt text is set on each image or asset. Images added to rich text and galleries are easy to miss.

How to add SEOAmazing to Webflow head code

Plan check first. Webflow only lets you use custom code on a site with a paid Site plan, or in a paid Workspace (Core, Growth, Agency or Freelancer). The free Starter plan does not support it.

Use site-wide head code, not Page settings. Page-level code only runs on one page. The pixel needs to be on every page.

1. Copy your snippet from the SEOAmazing dashboard.
2. Open your project's Site settings and select the Custom code tab.
3. Paste the snippet into the Head code box. Webflow places this code in the head of every page on the site.
4. Click Save.
5. Publish the site. Saved custom code does not go live until you publish, and scripts may not fully run in the Designer preview.
6. Open your published site, view the page source, and check the snippet is in the head.

<script defer src="…/pixel.js" data-site-id="YOUR_SITE_KEY"></script>

What SEOAmazing changes on Webflow pages

Add your site in the dashboard and SEOAmazing starts a crawl from your sitemap. Webflow can generate a sitemap for you, which makes discovery easy. If there is no sitemap, the crawl starts from your homepage.

The crawl snapshots titles, meta descriptions, headings, images missing alt text, structured data, internal links and Core Web Vitals. The AI then writes prioritized fixes, page by page. That is the key difference from a CMS formula: each collection item can get its own title and description, written for that item.

Each fix shows the current value, a proposed value you can edit, a severity and a one-line reason. Nothing changes until you click Approve.

• Title tags and meta descriptions, per static page and per CMS item.
• A single clear H1 where a page has none or several.
• JSON-LD schema.
• Image alt text.
• Internal-link anchor text.

What stays the same in your Webflow project

SEOAmazing does not edit your Webflow project. Your CMS items, collection fields, Page settings and Designer layouts stay as they are. You don't need to republish to apply an approved fix. The pixel applies it in the browser, and the ruleset is cached at the edge for about five minutes.

Changes are live only while the snippet is in your head code. Delete it and publish, and your pages go back to what Webflow serves. Writing changes back into the CMS is on our roadmap. It is not live today.

The pixel is under 8 KB gzipped, loads with defer and never blocks paint. It is wrapped so it can't throw errors into your page. If our CDN is unreachable, your site renders as normal.

How Google and AI crawlers read your Webflow site

Google renders JavaScript, so Googlebot can see the changes the pixel applies.

Many AI crawlers, such as GPTBot, ClaudeBot and PerplexityBot, don't run JavaScript. Our prerender service can serve them fully rendered HTML with your approved changes in it. On your domain this needs bot traffic routed to the prerender with a small edge rule, for example a Cloudflare Worker route. It is set up with our help, not automatic. seoamazing.com itself runs this way.

Next steps after you publish

Once the first crawl finishes, a simple order works well.

1. Review fixes for your CMS collection items first. They are usually the most pages with the weakest default titles.
2. Then review your main static pages: home, pricing, product and service pages.
3. Add target keywords to rank tracking. Check them any time with Check now, once an hour.
4. Connect Google Search Console (optional, read-only) to see clicks, impressions and question-style queries. Track any of them in one click.

Frequently asked questions