Q:

What close reason to use for "Debug my Website" questions

Hi!  Here's a link to my website.  Something in the HTML/CSS/Javascript isn't working.  Can you tell me what? 

This type of question is obviously not useful, as once a fix has been provided, the website will presumably be updated to incorporate it.  And then later it'll be completely redesigned.  And at some point it'll die and the domain will be taken over by squatters.  It happens. 
Such questions should, then, be edited to include actual code.  If you're feeling public-spirited, you should do it yourself.  Alternatively, you could close till the asker edits and asks for a reopen.  And, if the questions are old, and there's no way to access the original code, the question should be closed. 
Clear enough.  My question: What close reason applies to these questions?  We used to have an SSCCE close reason, but it's disappeared.  What applies now? 

A:

Leaving aside the case of old questions, for new questions where the question being a 'link-only' question is the sole or primary problem, I would always use a custom close reason now that the SSCCE reason is gone.  Here, I'll make one up in case anyone wants to copy and paste it:

Questions regarding a problem with code on your website should always include the relevant sections of code, not just link to a page on your site.  This ensures that your question will remain understandable to future readers once the problem has been fixed.  See http://meta.stackoverflow.com/questions/254428 for more information. 

The problem with Robert Harvey's approach is that while it may be technically valid to close these questions as "unclear what you're asking", it doesn't communicate to question asker - or anyone else who isn't already familiar with Stack Overflow's norms - what the specific problem with their question is.  Given that such communication is the entire purpose of close reasons, I think that this point matters. 

A:

Refer to https://meta.stackexchange.com/a/126000/

It will nearly always be unclear what you're asking: the problem exists only on one page, at one point in time.  It's unlikely anyone
  else will write the exact same code (even if they encounter the same
  underlying problem), and once a solution is devised and the page
  fixed, the link won't even serve to demonstrate the problem.