Boxenstopp migration status, simplified.

Continuity is the default. We only call out changes when the structure or user experience improves.

The redirect file is the launch bridge between old WordPress paths and final Webflow paths.

These are not creative changes. They are continuity requirements for launch readiness.

The style guide was tightened without changing the subject matter of the site.

The count difference is visible and should be checked during content QA.

This gives reviewers more context and makes the migrated article pages easier to scan.

Filtered views support browsing but are not treated as duplicate index targets.

This is a prototype improvement for review clarity, not a claim that all terms were separately indexed before.

The team can review terms separately from editorial blog articles.

This gives search engines a clearer content type signal.

The live page sitemap is not one clean content type, so a lower static count is healthier than rebuilding every old path as a public page.

These are part of launch readiness and should remain easy to verify.

This preserves discoverability while reducing duplicated landing-page maintenance in Webflow.

This is the main reason the final static page set should be smaller than the raw page sitemap.

This gives Webflow or the final hosting layer a practical import list.

Permanent redirects are appropriate because this is a migration, not a temporary test.

This explains why static pages can be reduced without losing old entry points.

This should be repeated after the final Webflow import.

Authors and taxonomy can be imported first if Webflow reference fields are used.

This keeps the original content intact while still allowing template-level design polish.

These columns should map to Webflow SEO fields or a CMS SEO field group.

This makes the final file-source decision visible before Webflow launch.

This fixes the earlier issue where important menu links were not clickable in the prototype.

The footer now works as a navigation surface, not just a closing block.

This is especially visible on blog, resources and course pages.

This is demonstrated in the visual block and can be reviewed on the linked page.

This is demonstrated in the visual block and can be reviewed on the linked page.

This is demonstrated in the visual block and can be reviewed on the linked page.

This is demonstrated in the visual block and can be reviewed on the linked page.

This is demonstrated in the visual block and can be reviewed on the linked page.

This is demonstrated in the visual block and can be reviewed on the linked page.

This is demonstrated in the visual block and can be reviewed on the linked page.

This is demonstrated in the visual block and can be reviewed on the linked page.

This is demonstrated in the visual block and can be reviewed on the linked page.

This is demonstrated in the visual block and can be reviewed on the linked page.

This is demonstrated in the visual block and can be reviewed on the linked page.

This is demonstrated in the visual block and can be reviewed on the linked page.

This fixes duplicated CTA appearance in CMS card grids.

This improves SEO scanning and human scanning because each card has clearer content hierarchy.

The layout is more useful on client review screens and large monitors.

This is straightforward in Webflow because Blog, Lexicon and Resource templates can bind image fields directly.

Keep original format only where transparency, quality or file type requires it.

This is one of the simplest Webflow-friendly ways to improve perceived performance.

Image elements are easier to optimize, resize and lazy-load than decorative background images.

This is a low-risk publishing setting and should be checked after publish.

Per-page CSS matters because blog, lexicon, resources and legal pages do not need every style at once.

This should be tested with menu, forms, GTM, consent and search.

This is useful but not automatic. It needs a verification pass after publishing.

Most blog, lexicon and legal pages should not pay the HubSpot script cost unless a form is visible.

This supports performance, privacy and debugging at the same time.

This is especially relevant for courses, resources and consultation pages.

This can be part of the final Webflow handoff documentation.

This is easy to manage with Webflow collection lists and page structure.

This protects performance and keeps the reader focused on the next useful step.

This supports SEO cleanup while still helping users browse the content library.

This matches the prototype card cleanup and keeps cards fast to render.

This is an improvement plan, not a claim that the live site has no schema.

This anchors the site entity and connects Boxenstopp to Shiftmove and Vimcar signals.

This supports the new search experience and gives Google a clean site-search pattern.

This should be systematic across blog, lexicon, resources, courses and legal pages.