## **🧭 Overview**

When you change a page's URL slug, both the old and new versions can sometimes appear in Google search results — even after setting up a redirect and clearing your cache. This happens because search engines may still hold a cached reference to the old URL. This article explains what typically causes duplicate URL issues after a slug change, and what information to have ready when contacting our support team for account-specific guidance.

## **⚠️ Why This Happens**

A duplicate URL issue after a slug change is typically caused by one or more of the following:

- **Google's crawl delay:** Search engines can take days or weeks to fully deindex the old URL, even after a redirect is in place.
- **Redirect not registered:** If the old slug still exists in your site's records, it may conflict with the new one.
- **Missing or incorrect canonical tag:** If the canonical tag on your new page still references the old URL, Google will treat both as valid versions.
- **Sitemap not updated:** An outdated sitemap can keep the old URL active in the index.

## **📋 What to Have Ready Before Contacting Support**

Because duplicate URL issues after slug changes can involve account-specific OTTO configurations, our support team will need the following details to investigate and resolve your situation:

- **Your project name** in OTTO where the slug change was made.
- **The old URL (before the slug change)** and the **new URL (after the slug change)** — exact full URLs, not just the slug segment.
- **When the slug change was made** — the approximate date and time.
- **A description of what you are currently seeing** — for example, both URLs appearing in search results, or the old URL still being indexed.
- **Any steps you have already taken** — such as clearing your cache or updating your sitemap — and what the outcome was.

Having these details ready will allow our team to review your specific OTTO configuration and provide targeted guidance as quickly as possible.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.