Redirects

Redirects let you redirect old URLs to new ones. Use them when you rename a post, restructure your content, or migrate from another platform.

This keeps your SEO intact and prevents broken links.

Why use redirects?

Renamed a post? Redirect the old URL to the new one so existing links still work.

Restructured your content? Keep visitors (and Google) from hitting 404 errors.

Migrated from Medium or Substack? Map your old URLs to your new Writizzy posts.

Find this in Settings → Redirects.

Creating a redirect

Click "Add Redirect" and fill in two fields:

• Source path: The old URL path (e.g., /old-article)
• Destination path: Where to redirect visitors (e.g., /new-article)

Both paths must start with /. Only internal redirects are supported—you can't redirect to external domains.

Smart destination autocomplete

When filling the destination field, the autocomplete helps you select the right page:

For posts: Start typing the post title or URL. You'll see:

• System pages (Home /, Archives /archives, About /about)
• Published posts with their titles

For tags: Type /tags/ and the autocomplete switches to tag mode. It suggests all your blog's tags. For example, type /tags/vue to find /tags/vuejs.

Editing and deleting redirects

Edit: Click the edit icon next to a redirect. Modify the source or destination and save.

Delete: Click the delete icon and confirm. The redirect stops working immediately.

Search: Use the search field to filter redirects by source or destination path.

Monitoring 404 errors

Switch to the "404 Errors" tab to see which URLs are returning 404 errors on your blog.

Each log shows:

• The broken path
• Number of hits (how many times it was accessed)
• Last referrer (where the visitor came from if available)
• Last occurrence date

Fixing broken links

Spotted a 404 that needs fixing? Click "Create Redirect" next to the log. The modal opens with the source path pre-filled—just select the destination and save.

Once fixed, delete the log by clicking the trash icon. The log can reappear if someone accesses the URL again, which is normal behavior.

Important notes

Source path must be unique. You can't create two redirects with the same source path. The system returns an error if you try.

Paths must start with /. Destination paths should exist.

Redirects are permanent (301). All redirects use HTTP 301 status codes, telling search engines the move is permanent.

Redirect loops aren't detected. Be careful not to create circular redirects (e.g., /a → /b and /b → /a).

That's it. Redirects are straightforward—map old URLs to new ones and keep your blog links healthy.