Skip to content
Free Indian Tools

SEO · Free tool

Trailing Slash Converter

Normalise a URL list to consistently include or strip trailing slashes. Files with extensions are left alone.

Normalised URLs

https://www.example.com/page
https://www.example.com/about
https://www.example.com/contact

Pick one and stick with it

Google treats /page and /page/ as different URLs by default. Without consistent canonicalisation, links and shares split between the two versions and your authority fragments. The right answer is whichever form matches your framework default — match it everywhere.

Server-side redirect is the long-term fix

This tool helps normalise existing URL lists (sitemaps, internal-link audits, ad URL sets). The permanent fix is a server-side redirect rule via .htaccess or nginx, plus a self-referential canonical tag on every page. The full discussion is in trailing slash — pick one.

Framework defaults

  • WordPress, Hugo, Next.js (default): trailing slash.
  • Most static-site generators in headless mode: no trailing slash.
  • Files with extensions (/file.pdf): never add a trailing slash.
  • Homepage /: always one slash.

FAQ

Does trailing slash matter for SEO?

Pick one and stick with it. Google treats /page and /page/ as different URLs by default. Without consistent canonicalisation, links and shares split between the two versions, fragmenting authority.

Which version should I pick?

Either works - what matters is consistency. WordPress and Next.js default to trailing slash. Static sites and many headless setups default to no slash. Match your framework default to minimise redirect overhead.

What if my server does not redirect between the two?

You need either a server-side redirect rule (.htaccess / nginx) or a self-referential canonical on every page. Without one of these, Google indexes both variants and your link equity splits.