320:
Slugs are typically generated automatically from a page title but can also be entered or altered manually, so that while the page title remains designed for display and human readability, its slug may be optimized for brevity or for consumption by search engines, as well as providing recipients of a
108:
Clean URLs also do not contain implementation details of the underlying web application. This carries the benefit of reducing the difficulty of changing the implementation of the resource at a later date. For example, many URLs include the filename of a
125:. If the underlying implementation of a resource is changed, such URLs would need to change along with it. Likewise, when URLs are not "clean", if the site database is moved or restructured it has the potential to cause
173:, implementation details, and so on. Clean URLs, by contrast, contain only the path of a resource, in a hierarchy that reflects some logical structure that users can easily interpret and manipulate.
264:
For search engine optimization purposes, web developers often take this opportunity to include relevant keywords in the URL and remove irrelevant words. Common words that are removed include
137:
regardless of internal structure. A further potential benefit to the use of clean URLs is that the concealment of internal server or application information can improve the
471:
157:. The query string parameters dictate the content to show on the page, and frequently include information opaque or irrelevant to users—such as internal numeric
359:
Another benefit of URL slugs is the facilitated ability to find a desired page out of a long list of URLs without page titles, such as a minimal list of opened
321:
shared bare URL with a rough idea of the page's topic. Long page titles may also be truncated to keep the final URL to a reasonable length.
615:
644:
419:
90:
78:
475:
572:
261:
techniques. As this usually takes place on the server side, the clean URL is often the only form seen by the user.
86:
102:
409:
300:
296:
50:
445:
386:
272:, while descriptive keywords are added to increase user-friendliness and improve search engine rankings.
345:
292:
269:
110:
279:
can be included at the end of a clean URL for references within a page, and need not be user-readable.
329:
620:
276:
85:
from a server's internal representation of information. Other reasons for using clean URLs include
590:
77:. Such URL schemes tend to reflect the conceptual structure of a collection of information and
425:
364:
313:
265:
138:
560:
344:. Punctuation marks are generally removed, and some also remove short, common words such as
341:
166:
74:
374:
Should a tool to save web pages locally use the string after the last slash as the default
629:
430:
360:
257:
The implementation of clean URLs involves URL mapping via pattern matching or transparent
66:
129:, both internally and from external sites, the latter of which can lead to removal from
549:
435:
324:
Slugs may be entirely lowercase, with accented characters replaced by letters from the
98:
82:
367:, and the ability to preview the approximate title of a target page in the browser if
638:
258:
130:
58:
649:
440:
325:
154:
150:
94:
317:
in the news media to indicate a short name given to an article for internal use.
133:
listings. The use of clean URLs presents a consistent location for resources to
70:
611:
337:
170:
158:
134:
498:
414:
390:
375:
368:
303:
part), which can be interpreted as the name of the resource, similar to the
54:
17:
308:
304:
162:
126:
625:
62:
101:
a more stable and useful system, and allows more durable and reliable
524:
333:
295:
keywords. It is usually the end part of the URL (specifically of the
93:(REST) style of software architecture, and ensuring that individual
311:
or the title of a page. The name is based on the use of the word
379:
73:
by being immediately and intuitively meaningful to non-expert
591:"16 Best Instagram Tricks And Hidden Features You Must Know"
243:
236:
97:
remain consistently at the same URL. This makes the
525:"Uniform Resource Identifier (URI): Generic Syntax"
382:does, a slug makes the file name more descriptive.
353:
228:
223:
216:
211:
204:
199:
192:
187:
27:URL intended to improve the usability of a website
291:as the part of a URL that identifies a page in
237:http://en.wikipedia.org/search/?title=Clean_URL
224:http://example.com/kb/index.php?cat=1&id=23
350:This, That, and the Other! An Outré Collection
472:"Clean URLs for better search engine ranking"
8:
385:Websites that make use of slugs include
175:
457:
212:http://example.com/index.php?page=name
465:
463:
461:
389:with question title after slash, and
7:
474:. Content with Style. Archived from
573:"Question URL slugs based on title"
441:HTTP referer § Referrer hiding
420:Persistent uniform resource locator
470:Opitz, Pascal (28 February 2006).
25:
531:. Internet Engineering Task Force
244:http://en.wikipedia.org/Clean_URL
503:Style Guide for online hypertext
354:this-that-other-outre-collection
200:http://example.com/user.php?id=1
352:could have a generated slug of
91:representational state transfer
53:(URLs) intended to improve the
550:Slug in the WordPress glossary
1:
188:http://example.com/about.html
149:A URL will often comprise a
561:Slug in the Django glossary
43:search engine-friendly URLs
666:
645:Search engine optimization
621:The User Interface of URLs
229:http://example.com/kb/1/23
87:search engine optimization
497:Berners-Lee, Tim (1998).
348:. For example, the title
205:http://example.com/user/1
89:(SEO), conforming to the
499:"Cool URIs don't change"
410:Information architecture
193:http://example.com/about
51:Uniform Resource Locator
217:http://example.com/name
49:) are web addresses or
626:Cool URIs don't change
446:Canonical link element
387:Stack Exchange Network
287:Some systems define a
330:whitespace characters
577:Meta Stack Exchange
371:to without title.
277:fragment identifier
153:, script name, and
111:server-side script
105:of web resources.
35:user-friendly URLs
478:on 6 January 2012
426:URL normalization
365:browser extension
363:exported using a
250:
249:
16:(Redirected from
657:
599:
598:
587:
581:
580:
569:
563:
558:
552:
547:
541:
540:
538:
536:
521:
515:
514:
512:
510:
494:
488:
487:
485:
483:
467:
399:
355:
246:
239:
230:
225:
218:
213:
206:
201:
194:
189:
176:
161:for values in a
124:
120:
116:
21:
665:
664:
660:
659:
658:
656:
655:
654:
635:
634:
630:Tim Berners-Lee
608:
603:
602:
589:
588:
584:
571:
570:
566:
559:
555:
548:
544:
534:
532:
523:
522:
518:
508:
506:
496:
495:
491:
481:
479:
469:
468:
459:
454:
431:URL redirection
406:
400:URL parameter.
394:
340:to avoid being
285:
255:
242:
235:
147:
122:
118:
114:
67:web application
33:(also known as
28:
23:
22:
15:
12:
11:
5:
663:
661:
653:
652:
647:
637:
636:
633:
632:
623:
618:
607:
606:External links
604:
601:
600:
582:
564:
553:
542:
516:
489:
456:
455:
453:
450:
449:
448:
443:
438:
436:URL shortening
433:
428:
423:
417:
412:
405:
402:
332:replaced by a
293:human-readable
284:
281:
254:
253:Implementation
251:
248:
247:
240:
232:
231:
226:
220:
219:
214:
208:
207:
202:
196:
195:
190:
184:
183:
180:
146:
143:
99:World Wide Web
83:user interface
26:
24:
14:
13:
10:
9:
6:
4:
3:
2:
662:
651:
648:
646:
643:
642:
640:
631:
627:
624:
622:
619:
617:
616:Jakob Nielsen
613:
610:
609:
605:
597:. 2017-08-04.
596:
592:
586:
583:
579:. 2011-10-10.
578:
574:
568:
565:
562:
557:
554:
551:
546:
543:
530:
526:
520:
517:
504:
500:
493:
490:
477:
473:
466:
464:
462:
458:
451:
447:
444:
442:
439:
437:
434:
432:
429:
427:
424:
421:
418:
416:
413:
411:
408:
407:
403:
401:
398:
392:
388:
383:
381:
377:
372:
370:
366:
362:
357:
351:
347:
343:
339:
335:
331:
327:
322:
318:
316:
315:
310:
306:
302:
298:
294:
290:
282:
280:
278:
273:
271:
267:
262:
260:
252:
245:
241:
238:
234:
233:
227:
222:
221:
215:
210:
209:
203:
198:
197:
191:
186:
185:
181:
178:
177:
174:
172:
168:
164:
160:
156:
152:
144:
142:
141:of a system.
140:
136:
132:
131:search engine
128:
112:
106:
104:
100:
96:
95:web resources
92:
88:
84:
80:
76:
72:
68:
64:
60:
59:accessibility
56:
52:
48:
44:
40:
36:
32:
19:
594:
585:
576:
567:
556:
545:
533:. Retrieved
528:
519:
507:. Retrieved
502:
492:
480:. Retrieved
476:the original
396:
384:
373:
358:
349:
346:conjunctions
326:Latin script
323:
319:
312:
288:
286:
274:
270:conjunctions
263:
256:
179:Original URL
165:, illegibly
155:query string
148:
127:broken links
107:
47:RESTful URLs
46:
42:
38:
34:
30:
29:
18:Semantic URL
482:9 September
369:hyperlinked
171:session IDs
159:identifiers
135:user-agents
119:example.asp
115:example.php
103:bookmarking
71:web service
39:pretty URLs
639:Categories
452:References
395:?taken-by=
338:underscore
182:Clean URL
113:, such as
31:Clean URLs
612:URL as UI
595:Fossbytes
415:Permalink
391:Instagram
376:file name
259:rewriting
145:Structure
55:usability
529:RFC 3986
404:See also
397:username
309:filename
305:basename
301:pathinfo
266:articles
163:database
139:security
79:decouple
509:6 March
378:, like
342:encoded
167:encoded
123:cgi-bin
63:website
422:(PURL)
336:or an
334:hyphen
169:data,
628:, by
614:, by
535:2 May
505:. W3C
393:with
307:in a
75:users
69:, or
61:of a
537:2014
511:2011
484:2010
380:wget
361:tabs
328:and
314:slug
297:path
289:slug
283:Slug
268:and
151:path
81:the
57:and
650:URL
121:or
45:or
641::
593:.
575:.
527:.
501:.
460:^
356:.
299:/
275:A
117:,
65:,
41:,
37:,
539:.
513:.
486:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.