"Trailing slash versus no trailing slash is a ranking decision."

"Trailing slash versus no trailing slash is a ranking decision."

No. It's a consistency decision wearing a ranking costume.

Google treats /page and /page/ as different URLs but does not prefer either. There is no slash bonus. What there is: a duplication risk if both resolve 200, and a split-signal mess if half your internal links use one and half use the other.

So the real comparison isn't slash vs no-slash. It's pick-one-and-redirect vs let-both-live. The first costs you one redirect rule and a find-replace in your link templates. The second costs you canonical confusion forever.

Files get no slash. Directories conventionally get one. Past that, the winning move is whichever your platform defaults to — then enforce it with a 301 on the other variant and never think about it again.

(If you're migrating slash conventions to "boost" anything, stop. You're spending redirect equity to fix a problem you invented.)