If you changed a slug (like /contact → /contact/contact-03) and now pages are broken, you need redirects. 301 redirects protect SEO, preserve trust, and keep Google crawling your site cleanly.
Pro rule: don’t redirect everything to the homepage — redirect to the closest matching page.
Google remembers your old URLs. If they become 404s, you lose ranking signals. 301 redirects pass most value to the new page.
When visitors land on a dead page, they bounce. Redirects keep the experience smooth and premium.
Broken internal links waste crawl budget and slow indexing. Redirects + link fixes solve it.
Want to restructure your site? You can — as long as you keep redirects.
If /contact was broken but /contact/contact-03 worked, adding a 301 redirect fixes it instantly.
Start with the obvious ones (nav links, footer links). Then check Google Search Console coverage errors if you have it.
Redirect to the most relevant page. If a “case studies” page changed, redirect to the new case studies—not the homepage.
Webflow → Project Settings → Hosting → 301 Redirects. Add paths only.
Old path: /contact
New path: /contact/contact-03Don’t include https:// in the redirect fields.
Publish the site, then test the old URL in an incognito window. If it still fails, you may have a cached version.
Redirects are a safety net. Your actual links should point to the new URL so you’re not chaining redirects.
This looks spammy and hurts relevance. Redirect to the closest matching page.
Multiple redirects slow crawling and can break SEO signals. Keep it one hop.
Redirects don’t fully apply until the site is published. Always publish after changes.
Even with redirects, you should update nav/footer links to point to the new URL.
If you want a site that stays clean while you add pages, we’ll handle redirects, internal links, speed, and search structure so traffic can compound.