As a moderately heavy Discogs user, the ability to create a playlist from a Discogs wantlist would be a very welcome feature.

Your service works pretty well, but you should consider using SSL certificate.

I have hundreds of records with dance music that have one track on each side. Typically the Discogs title will be "Track A / Track B". Now, some labels chose to name the albums on Spotify like that as well, and there is a match in your search. However, many labels chose to name the Spotify album like the A side.
Just one just example each to make the point:

Match:
https://open.spotify.com/album/4N1xZdCPUPif2wYtfnTnnQ?si=REpoLLaAQe-fRg8IDPK_XA
https://www.discogs.com/501-Mind-Control-Hidden-Worlds/release/1716182

No Match:
https://open.spotify.com/album/70do9kzpwzySrARkWLFrbM?si=u18az7bnTH--nnbxaFdP0Q
https://www.discogs.com/Boxcutter-Allele-Other-People/release/2746044

I see two possible solutions:

1. regex the title for this format, use only the first part if it's a match. This would be a pragmatic solution. I tested the search with some releases. If the album is called "Track A / Track B" on Spotify, searching for "Track A" will find it as well.
2. be a bit more strict and only attempt this kind of search if the first search yields no result. this way might prevent some new ambiguities (say an artist has albums called "Foo / Volume x", "Foo / Volume y" etc), but on the other hand it adds new complexity (retry searches).

So I would prefer the first solution. If you agree, I can create a pull request. It's really a minor change that would create hundreds of new matches for my collection alone.

Artist name variations have become a part of discogs, and part of the API response for a release.
Take this release:
https://www.discogs.com/Distance-My-Demons/release/899691

The api will return artist information with a name key (value "DJ Distance") and an anv key (value "Distance").
Your search extracts artist information from the name field, and a search on Spotify yields no result. Had we searched using the anv field, we would have had a match: https://open.spotify.com/album/0OunwPdyQkPtategY8yonA?si=7_PH890fRXe9LIZU2KSD0A

There is a simple solution: always use the anv value if it exists. The only question is, could this mean we lose some matches on Spotify? I still think it would be a worthy change, from my collection it seems that ANV will typically be the currently agreed upon most common name. But of course my collection is only "anecdotal evidence".
A more complex solution would of course require changes in your datastructures, maybe retried searches with anvs, etc....