I was going to enumerate two of these options. Currently, this can be solved with <meta> redirects, which are however very difficult to create in such a way that Frozen-Flask can collect them. Deploying for "real" would also solve this.
Well i was thinking we could teach Frozen-Flask to create those mate redirects when it sees a flask.redirect, but than again you would also need to feed it a route generator in order to be able to collect them. My opinion: Too much work, given the fact that we'll probably need to switch to dynamic website soon enough anyway.