http://www.domain.com/folder newfolder/file name.htm is incorrect.
http://www.domain.com/folder-newfolder/file-name.htm is suitable:
Many developers prefer to use underscores (_) to separate words in file names rather than hyphens (-). Because the hyphen is reserved in some computer languages, such as the subtraction infix operator, they are educated to employ this behavior.
Because Google was created by geeks for geeks, the search engine interprets underscores as joiners or concatenation, and therefore technical terminology like FTP BINARY will appear on search results pages.
If you are starting a new website, hyphens are recommended.
Alter the current URLs to hyphens and 301 redirected URLs to the new URLs if you have a tiny website with few inbound links.
If you have an initiative site that utilizes underscores, keep the CMS rules and previous URLs, but change the naming resolution for any new files to hyphens instead of underscores.
With a little thought, you can keep the number of hyphens and words down to a manageable level. For the subjects level pages or the name of the category, I recommend using one or two hyphens. You'll have a lot of leeway when naming the files for the articles; don't attempt to pack keywords or go to town with them.

Choose a domain that concisely and effectively defines your brand or business without the use of dashes.
You may learn how to buy expired domains by reading this post.
There's no need to be concerned about keywords. Though I'm not aware of any technical reasons why dashes should not be used in domain names, they appear compromised and cheap in practice. When you are out of credentials and connections, this may raise an attention ensign.
The ability to include keywords is one of the primary reasons why people select hyphenated domains. Last year, Google changed its algorithms to minimize the precise match domain benefit. Though, for a long time, the success of a large number of brand name domains, many of which bordered on the absurd, demonstrated that a keyword-rich domain is not required to be successful.

Both Bing and Google excel at providing challenging URLs that are non-standard and contain dashes or encoded characters. And the issue arises when other websites attempt to link to your papers. If the special characters are not encoded, the special characters may be encoded by the content management systems of other websites that are connected to your publications.
For example, spaces become 20%. If the character sets used by those websites differ from the character sets used by your website, your special characters may not be translated correctly. The best method to keep things simple is to use hyphens, alphabets from a to z, and characters for 0 to 9. According to technical standards, URLs are case sensitive. Many content management systems handle mixed case addresses by rewriting them in lower case, but you should double-check yours and don't take chances.
Also, certain SEO tools and analytics are case sensitive, so various variations of the same URL will be reported separately. The safest route is to make sure that all of your internal links are in lower case, and to make this the norm of style for all coders and copywriters.

It is common practice for search engines to consider subdomains similarly to different websites. Today, they are unequally distributed. Actually, it has happened multiple times in the same way. It is also beneficial since many third-party apps, such as shopping carts, are required to be housed on subdomains.
Search engines are extremely capable at determining whether or not subdomains are linked. WordPress.com, Tumblr, and Blogspot, for example, are not connected subdomains, although store.domain.com and www.domain.com are.
Don't disconnect subdomains if you're utilizing them. Make sure your subdomains and domains' navigation links are effectively connected. I've seen applications within subdomains that only connect to the main website's homepage or utilize no follow links.

Take Care When Using Parameters
The parameters are variables in URLs. The conventional method of generating parameters is to end the address with a question mark, followed by a list of parameter names and values.
For instance, http://www.domain.com/category=billiards&game=nineball&article=how-to-rack-the-balls?category=billiards&game=nineball&article=how-to-rack-the-balls
http://www.domain.com/billiards/nineball/how-to-rack-the-balls/ Your content management system may rewrite this into an SEO-friendly and user-friendly style.
Both of the URLs shown above are valid. The second example is my personal favorite since it is simple to read and eliminates needless letters and phrases.
You'll almost certainly want to disregard non-standard or missing delimiters.
http://www.domain.com/nineball/nineball/nineball/nineball/nineball/n (no limitations)
http://www.domain.com/billiards/nineball/nineball/nineball/nineball/nineball/nineball/n (unusual restrictions)
I've also come across a few more amusing delimiter systems.
Be cautious of user identifying parameters such as uid=1432567, and each visitor will get a number or tracking parameters such as source=abc, where abc is distinct for each page displayed. It will result in content difficulties as a result of the replacement.
You have two options: get rid of them or use cookies to replace them.
To notify the search engine which URL to index and credit with certificates and links, use the rel=”canonical” element.
Indicate to search engines that you want to avoid the criteria that are being used by webmaster tools, such as Bing and Google.
Another method is to place the parameters by the page's content, which will not be affected by a #. After the # character in URLs, almost everything is disregarded by search engines, with the exception of the AJAX hash bang.

Despite the fact that search engines promote their capacity to crawl Flash and other rich media, they nevertheless perform a poor job of it. When inserting multimedia into an HTML page, such as a presentation, video, sound file, or animation, Flash is a preferable alternative.
Don't utilize full Silverlight or Flash on your website. Photographers, painters, and musicians are particularly fond to Flash sites, which is unfortunate because these are the folks who may benefit from organic search. Remember that Apple's iDevices do not support Flash, therefore its popularity is waning.

Google doesn't care if you use https: or http: or if you don't use it at all!
Even though Google accepts both https: and http:, choose one and switch to it on a URL-by-URL basis. Allow us the opportunity to inform you that if you have a shopping cart, it is protected by https: checkout. If you have a crawler-friendly collection of sites that resolve to both versions https: and http:, you might be in a lot of trouble.
I've seen webpages where all offsite links point to http: addresses, which Google crawls. Then, for no apparent reason, the addresses in the Google index change to https:, and the website's rating vanishes.
The use of conical tags that mandate https: or http: each is the version you wish to get indexed is an easy method to get around this.

When the text in the HTML markup does not match what consumers view, it is referred to as cloaking by search engines. Cloaking can happen inadvertently. An example I've seen is in a shopping cart, where all of the links to all of the product categories and subcategories are included in the markup of each page. Visitors can only see links to the subcategories of the category they're looking at. CSS is used by the content management system to conceal the other subcategory links.
I'm not going to fight about white hat vs. black hat cloaking here, partly since Google engineers tend to loathe discussing specific cloaking techniques. Perhaps they don't want to offer folks any ideas. Allocating distinct contents based on user agents and using CSS for placing text off the screen are the two exceptions, one of which they utilize for demonstrative reasons (-999).
They are always quick to claim that there are no legitimate grounds for cloaking and that they have specific recognition of algorithms that sound the red alarm phone. The eventual consequence of these twists is to prevent cloaking by mistake.

Long winding road, long – winding road, long — winding road, and long | winding road are all terms that can be used to describe a winding road. It's worth noting that Google ignores the dashes but not the vertical bars. Not just aesthetically, but also in the Google algorithm, that bar distinguishes between long and curved. If your website has a vertical bar, try replacing it with a dash and see what happens.
It's excellent for you if you understand all nine of my SEO twists. It's difficult to stay up with everything there is to know about Bing and Google SEO. If you have any SEO twists, please share them in the comments.