Hi Anna,
Currently if you check the SEO feature setting in the Store Admin module, the meta tag are modified on the fly depending on the context. On the Store Catalog page, if no category is selected the Store name is injected in the page title, Store keywords and description are used for the corresponding meta tags. If a category is selected, the category name with the Store name is used for the title, same for keywords and description. If a product detail page is displayed, then this time it's a combination of the Product name and Store name, keywords and description. This allow a good ranking because each time the category or product page change the search crowler receive a different title, keywords and description. All this combinations can be changed using the DNN language editor and tokens.
I could add the product name in the url in a future version, BUT it's NOT so simple! Because you think localy while I think globaly! I work for every one in the world, not only English speaking users! :-) As a sample, imagine a French Store (I'm French) with a product named: Vélo d'appartement (home bike in English). To avoid problem and bad looking encoding like %## in the url (for the characters "é" and '), the product name should be normalized as: velo-d-appartement. It work perfectly for a French reader, but it's not always valid to simply remove accents and replace some predefined characters by a -. Because for some languages like Swedish or Korean and many others, removing an accent can change the meaning of a word! And I do not talk about Chineese, Arabic or Jewish languages! This time you have to Romanize the product name not translate it!. They are several ISO recommendations about each language. Believe me, that's a larger subject than simply remove accents like some do. Do a simple search of "normalization" and "romanization" with Google, you should found zillon pages about his subject. :-) At least, using CategoryID and ProductID works whatever the used language! :-)
Concerning to remove the CategoryID, again it's not a so good idea. First because if you have a list of link from your catalog, they will be ordered by category. :-) Moreover, the Store module REQUIRE the category id to return to the right category page from the product detail page. I know than most of time it's the same page, but again it's perfectly correct to use two different pages if you need two different skins for the catalog page and the product detail page. Second, I could retrieve the categoryID from the product info, but I will have to add it to the url to allow the Store Menu module to display the right category your customer want to return to. I could use the DNN Inter Module Communication API to transmit the category id, but it works ONLY if both modules are on the SAME page. This is why it's required, the Store module nor me have a crystal ball. :-) Finally, simply changing an url system of an existing website IS NEVER a good idea and REQUIRE to have a redirection system from the old url to the new one. Because a search crowler like Google will discover two differents url with THE SAME content and Google DO NOT LIKE this and can decrease your ranking as a punishment.
Gilles-who-is-NOT-a-magician