How to use the URL Slug Generator.
A slug should be readable and stable. Avoid inserting a year or promotional claim unless the page's identity genuinely depends on it.
Make the workflow fit your task.
Choose a short phrase that identifies the page's stable subject or task. Remove decorative words and temporary claims, then check that the resulting path remains distinct from existing destinations.
- What you provide
- Page title and content context.
- What you get
- Readable normalized URL path.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Title: How to Compare Supplier Catalogs in Minutes!
Completed example
supplier-catalog-comparison
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a slug change whenever the title changes?
Usually preserve a stable URL when the page's identity remains the same. Treat a path change as a separate migration decision.
Why does the generated slug collide with another page?
Compare the two page purposes. Use a meaningful distinction if both are needed, rather than adding an arbitrary suffix without resolving overlap.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑