Both trailing-slash versions serve the same content
trailing_slash_variant_duplicate · Issue
Both slash forms answered 200 with matching main content. Choose the form your site uses consistently and permanently redirect the other form to it, or use a supported canonical between the checked addresses.
Severity: Medium. Both addresses serve the same recorded main content without supported consolidation; the audit does not establish that Google indexed both.
Why it matters
Google describes canonicalization as choosing a representative URL among duplicate pages. This finding records a duplicate response pair; it does not measure a ranking loss.
What to do
- Read the two requested addresses and their recorded status, main-text and canonical evidence.
- Choose a consistent slash form. Permanently redirect the other form to its checked counterpart, or use a canonical between them that meets the checked-pair conditions.
- Update internal links consistently and run a new full audit.
When to leave it as it is: Review before changing a route where the slash forms intentionally represent distinct views. Content that only differs after scripts run needs a browser check.
What we read
We compare an observed address with its opposite trailing-slash path form, preserving query spelling and percent-encoded bytes. The origin root has no distinct opposite form.
We compare the two recorded requested addresses. Both must return direct HTTP 200 with complete server HTML and one complete, unique, nonempty main, role=main or article region. Their main-text hashes must match exactly after the existing whitespace and letter-case normalization.
The pair is not reported when a qualified canonical from either member points to the matching checked peer, whose canonical is absent or points to itself. Ambiguous, invalid or third-target canonicals and noindex scope exits remain unknown.
Already captured peers are reused. Additional path variants use the existing governed, robots-aware request budget, with at most 20 selected variant reads per site. Missing responses, partial HTML and content that needs browser execution are not clean comparisons.
Example & evidence
Illustrative example, not a live audit.
/tea → 200, main text: Tea guide
/tea/ → 200, main text: Tea guide
No supported canonical consolidates the pair.Confirm & check again
Check for yourself: Open both recorded addresses, inspect their HTTP status and source canonicals, and compare their main content. Confirm the chosen redirect or canonical still lets visitors reach the intended page.
Check again: Full audit — Run a new full audit. The same two requested addresses must be checked. A qualified permanent 301 or 308 to the checked counterpart, a qualified 404 or 410 at one address with a checked peer, a supported canonical between the pair, or genuinely distinct complete main content can resolve the observation. Temporary redirects, missing peers, uncertain canonicals, noindex and insufficient coverage leave it unresolved.
Limits & sources
Only captured server responses are compared. Identical main text does not prove identical HTML, browser output, intended URL form or a Google indexing decision.
Confidence: High The response pair and exact normalized main-text equality are recorded; choosing the preferred address remains a site decision.
Sources
- Google, How to specify a canonical URL — Describes redirects and canonical annotations as canonicalization signals. Our exact pair comparison does not predict which address Google chooses. Checked 13 October 2026.
Editorial review: 2 November 2026