I personally don't think that Google handles this data exceptionally well:
https://d.pr/i/2Y562I.png (Keyword Revealer screenshot)
https://d.pr/i/El2skX.png (Ahrefs screenshot)
https://d.pr/i/Y3bQ3p.png (Google keyword planner screenshot)
... however, I do sometimes see such keywords returned from Google Search Console and / or Google Analytics under GSC's "Search Queries" (search terms) report. So it makes me wonder, if Google really has such trouble, why does it highlight and record such keywords, passing them to me for further analysis?
Maybe it's actually not a big deal, it's just that Google's keyword planner (in terms of full unicode support) is way, WAY out of date (something they should have patched and fixed 5-6 years ago IMO)
Regardless of this though, more people do seem to search by 'half' or '50%', people 'almost' never type "½" as it's so hard to type in a web browser, you almost always have to copy and paste the symbol unless you have some kind of rich-text field entry add-in / extension
Google can process the symbol as search entry text:
https://www.google.com/search?q=%C2%BD
Google often states that actually, using unicode characters (even in URLs, in UTF-8) is ok in modern times. This is a compromise they have had to make, as many foreign characters are packaged in various unicode character sets
This is the full list of UTF-8 symbols:
http://www.fileformat.info/info/charset/UTF-8/list.htm
If you Ctrl+F for '½', it is technically in that list. As early as 2008 Google was recorded indexing UTF-8 URLs:
https://www.seroundtable.com/archives/018137.html
Much more recently, the debate has been raised again:
https://searchengineland.com/google-using-non-english-urls-non-english-websites-fine-294758
"For domain names and top-level domains non-Latin characters are represented with Unicode encoding. This can look a little bit weird at first. For example, if you take Mueller, my last name, with the dots on the U, that would be represented slightly differently as a domain name. For browsers and for Google search, both versions of the domain name are equivalent; we treat them as one and the same. The rest of the URL can use unicode utf-8 encoding for non-Latin characters. You can use either the escape version or the unicode version within your website; they’re also equivalent to Google."
Obviously Google is talking about URLs here, but usually Google becomes capable of reading characters in markup (content, Page Titles etc) first and then accepts them for valid URL usage later. I would surmise that it probably is 'ok' to use them, but it probably would not be 'optimal' or 'the best idea'