![\"\"](\"https:\/\/ten30media.com\/sapnew\/wp-content\/uploads\/2022\/03\/Clean-URL.jpg\")
<\/p>\n<\/p>\n
\u00a0<\/strong><\/p>\n Clean URLs<\/strong>, also sometimes referred to as\u00a0RESTful URLs<\/strong>,\u00a0user-friendly URLs<\/strong>,\u00a0pretty URLs<\/strong>\u00a0or\u00a0search engine-friendly URLs<\/strong>, are\u00a0URLs<\/u>\u00a0intended to improve the\u00a0usability\u00a0and\u00a0accessibility\u00a0of a\u00a0website\u00a0or\u00a0web service\u00a0by being immediately and intuitively meaningful to non-expert\u00a0users. Such URL schemes tend to reflect the conceptual structure of a collection of information and\u00a0decouple\u00a0the\u00a0user interface\u00a0from a server’s internal representation of information. Other reasons for using clean URLs include\u00a0search engine optimization\u00a0(SEO),[<\/sup>\u00a0conforming to the\u00a0representational state transfer\u00a0(REST) style of software architecture, and ensuring that individual\u00a0web resources\u00a0remain consistently at the same URL. This makes the\u00a0World Wide Web\u00a0a more stable and useful system, and allows more durable and reliable\u00a0bookmarking\u00a0of web resources.<\/p>\n 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\u00a0server-side script, such as\u00a0example.php,\u00a0example.asp\u00a0or\u00a0cgi-bin. 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\u00a0broken links, both internally and from external sites, the latter of which can lead to removal from\u00a0search engine\u00a0listings. The use of clean URLs presents a consistent location for resources to\u00a0user-agents\u00a0regardless 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\u00a0security\u00a0of a system.<\/p>\n Table of Contents<\/p>\n <\/p>\n Structure<\/strong><\/p>\n A URL will often comprise a\u00a0path, script name, and\u00a0query string. The query string parameters dictate the content to show on the page, and frequently include information opaque or irrelevant to users\u2014such as internal numeric\u00a0identifiers\u00a0for values in a\u00a0database, illegibly\u00a0encoded\u00a0data,\u00a0session IDs, 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.<\/p>\n\n