How do URLs and duplicate pages affect search?

Keep page addresses clear and stable, and send visitors to the right page when an address changes.

A URL is a page’s web address. The same content can sometimes be opened at several addresses. Give customers a clear, stable main address where possible.

The basics to remember

Website structure describes how pages are organized. Service directories, navigation and related links should make important pages easy to find.
A canonical tag tells Google which main URL you prefer for duplicate or very similar pages. It is a signal, not an absolute instruction.
A redirect automatically sends visitors from an old address to a new one. A 301 means a permanent move; permanently changed pages should lead to corresponding new content.

See Google: Consolidating duplicate URLs and Google: Redirects .

Keep established addresses stable and check duplicates individually

Improve content and entries first during a redesign. You do not need to move every address to add new keywords. If a name, domain or path genuinely needs changing, map old pages to new ones. After migration, check bookmarks, external links, internal links and sitemaps. Do not redirect all pages without a matching replacement to the homepage.

The canonical URL should match the current content. A repair page with sharing-tracking parameters can point to its main address, but a booking explanation is not a duplicate of the repair homepage. Making every detail page canonical to the homepage expresses the wrong relationship. Choose a consistent production version for duplicate entries such as www versus non-www and HTTP versus HTTPS. See Google: Consolidating duplicate URLs .

Use short, clear topic wording in URLs rather than entire user inputs or prompts. A subdirectory is a grouping path after the domain; a subdomain adds a name before the main domain. Choose based on business relationships and maintenance needs, not a promise that one necessarily ranks better. Support stable addresses and clear navigation.

When a business changes its name, a clear update page can state the old name, new name, effective date and any service changes, linked from the homepage. Existing customers can confirm it is the same business. List old pages with visits or citations before migration, then check old-name queries, new-name queries and corresponding pages afterwards. A 301 does not guarantee immediate preservation of rankings. See Google: Site moves with URL changes .

Give language versions stable addresses and complete information

Use stable URLs for each language. Where possible, language switching should reach the same page’s translation; otherwise offer a clearly identified alternative. Check body content, titles, descriptions and navigation, not just the menu or body alone. Let customers switch rather than automatically sending them elsewhere based only on a guessed location.

hreflang is a marker telling Google about a page’s language or regional alternatives to help select the suitable version. It cannot replace a translation or repair broken links. Preserve working entries when changing an established site; adding a language does not justify casually changing domains. See Google: Multi-regional and multilingual sites .

Walk through an example

Check	Before (hypothetical)	After or appropriate action
Live service page	/old-service	Use a stable new address
Old-page visit	Not found	Redirect to the corresponding new page
Duplicate versions	Main address unclear	Use consistent canonical signals

Suppose a repair page moves. The developer sets a permanent redirect and updates its link in the service directory. Customers using an old bookmark still reach the same service.

Common misunderstandings