Choose and maintain page URLs

A page URL should help people recognise its topic. Choose a short, descriptive slug before publication, then keep the public address stable while the page continues to serve the same purpose.

Understand the parts

In https://www.example.com/services/career-coaching, the domain identifies the website and /services/career-coaching identifies the page path. A folder can organise related paths in the editor.

Pineapple may normalise an index page to its parent address. For example, /docs/topic/index can be served publicly as /docs/topic. Use the public address when sharing links or checking search results.

Choose a slug when creating a page

Use words that describe the page, with hyphens where helpful. For example, career-coaching is clearer than page-3.

Keep the slug readable, avoid unnecessary words and check that it matches the topic. There is no need to add every possible keyword or chase an arbitrary character count. Check the actual path shown before saving the new page.

Keep different purposes on different pages

A service description and a detailed preparation guide can have separate URLs because they answer different needs. Two pages with nearly identical content are harder for readers to distinguish.

Before creating a new page, check whether an existing page already covers the topic. Improve or combine the content when that gives readers a clearer answer.

Before changing a public URL

Identify where the existing address is used: navigation, buttons, related articles, shared links and search results. Record the old URL and the intended replacement.

Do not assume a rename automatically redirects the old address. Confirm how the old URL will be handled before changing it. If there is no verified redirect plan, keeping the existing URL is usually the safer way to update the content.

Check the result

After a planned change, publish the intended content and open both the old and new addresses. Check the destination, navigation and internal links. Review the sitemap and canonical URL for the public page.

If the old address returns an error, changing links inside your own website does not fix links that other people already shared. Resolve the old address as part of the migration.

For ordinary content updates, edit and republish the existing page without changing its URL. See sitemap checks and SEO settings.