# SEO-friendly URLs: choosing a stable address

> Choose readable, stable URLs, understand parameters and fragments, and avoid moving existing pages for appearance alone.


**An SEO-friendly URL helps someone anticipate a page’s content by reading its address.** A path such as `/workshops/beginner-pottery/` communicates more than opaque parameters. When creating one, choose an understandable name that remains accurate as minor details of the offer change.

Google recommends a [simple, descriptive URL structure](https://developers.google.com/search/docs/crawling-indexing/url-structure), using the audience’s language and hyphens between words. Those recommendations help organize a site; an unattractive address does not automatically require an urgent migration.

## The class changes its schedule but keeps its page

Suppose a studio is preparing a recurring beginner pottery class. Its page is not published yet. The first proposed path is `/best-pottery-class-saturday-november-2026/`. It contains an unsupported judgment and details that may soon stop describing the offer.

The team chooses `/workshops/beginner-pottery/`. The next schedule and booking date belong in the content. If it later creates a dated edition with its own terms and archive, it can assess whether that edition needs a separate page.

| Situation | Decision | Reason |
| --- | --- | --- |
| Recurring class not yet published | Create `/workshops/beginner-pottery/` | Describes the level without tying it to an incidental date |
| Existing `/class?id=42` page with links and accurate content | Keep it while assessing a substantive reason to change | URL appearance alone does not justify a move |
| Catalog sorted by price | Keep a parameter with a clear purpose | Sorting does not need to masquerade as a new category |
| Dated edition with its own tickets and conditions | Assess a dedicated page | May serve a different need from the recurring class |

Do not promise traffic gains from shortening an address. The example avoids a name that becomes outdated quickly, without claiming a ranking improvement.

## Parameters, capitalization and fragments

Parameters can be necessary. An address containing `?page=2` may identify a different catalog page; removing every parameter could break that navigation. Remove unnecessary ones only after understanding what each one changes.

Google handles URLs as case-sensitive. If your server supplies the same content for upper- and lowercase variants, agree on a consistent form and check how the others resolve. Editing capitalization in a document does not configure server responses.

A fragment such as `#materials` can identify a section within a page. Do not use it as the only mechanism for presenting different catalog pages you expect Google to discover separately. Its guidance notes crawling limitations for content identified only through fragments.

## When the address is already published

Before renaming it, identify its internal links, external references and current use. If a move has a substantive purpose, prepare equivalents, redirects and link updates. The [301 redirect article](/en/guides/301-redirect/) develops those checks.

For the recurring class, consider one final condition: if the studio replaces it with an advanced course, the chosen address no longer represents the same offer. Stability requires a match between address and content, rather than preserving a page at any cost after its purpose changes.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
