Anywhere you see user input is reflected in the response (not limited to what you see on the page, it could be in source code/HTTP response only), note the location/parameter down, that's a potential attack vector.
2οΈβ£ Testing encodings/unusual behavior
If at first your usual XSS payload doesn't work (99% times), don't let it go straight away, most times there will be a filter/WAF in place, which could be bypassed.
Firstly, figure out how they handle input, don't jump straight into XSS.
They might filter <script>, but how do they handle non-harmful HTML tags such as <u>?
If they encode <> ,what happens if you provide already encoded tags such as %3C or <
To help with identifying weird behavior, I've already put together a list of payloads:
Don't rely on these though, in most cases you have to craft your own payload based on the target/location which requires you to think a little, so put that π§ to work