Google Forms redirect after submit: every method and its limits

No. After someone clicks Submit, Google shows a confirmation page on docs.google.com with your confirmation message, and that is the end of the flow. Google's help pages describe editing the message, showing a link to submit another response, and showing a results summary. None of them mention sending the respondent to another URL.

Two popular fixes don't work. Google Workspace Marketplace add-ons for Forms can't change the respondent's page, because Google's developer documentation says they "only extend the Forms editor itself" and can't extend the form shown to respondents. Apps Script form-submit triggers run on Google's servers after the response is saved. They can email someone or write to a sheet, but they can't control the respondent's browser. The one Apps Script route that once allowed redirects, a published web app, has also been closed. Digital Inspiration's documentation notes that Google dropped support for redirects in Apps Script web apps.

This is the classic forum answer. Embed the form in an iframe on your page and count the iframe's load events. The first load is the form. When the respondent submits, the frame loads Google's confirmation page, which fires a second load event, and your script sends the parent page to your thank-you URL.

The same-origin policy is the catch. Your page can see that the frame loaded something, but not what loaded, because the content comes from docs.google.com. So the script is guessing. The guess fails in three common cases. On a multi-section form, every Next click loads a new page, so the count is wrong unless you hard-code the number of sections. A load event only tells you that a page loaded, not which page, so an error page would trigger it too. And anyone who opens the direct form link or the forms.gle short link never runs your script at all.

Our view: it can work for a short single-section form that only ever appears embedded on your page, and only if you test it every time the form changes. It isn't suitable for anything you're tracking as a conversion, because a load event doesn't prove Google accepted a response.

Some tutorials build a custom HTML form that copies each Google question's hidden entry ID and posts answers to the form's response endpoint, then redirects with ordinary JavaScript. Answers land in the Google Form and its linked sheet, and the redirect is fully under your control.

It works until it doesn't. Google doesn't document this endpoint. Required-field checks, sections, file uploads, sign-in requirements and response validation all have to be rebuilt in your code or dropped. Editing a question can change the entry IDs and silently break submissions. At that point Google Forms is only acting as a database, and a form builder with a Google Sheets integration gives you the same spreadsheet without the upkeep.

Formfacade renders your Google Form's questions through its own page or embed code. Responses still go into Google Forms, and it adds features such as redirect on submit. Its redirect page says it can pass answers to the redirected page and send people to different pages based on their answers. It also says you must use the Formfacade share link or embed code, not the native Google Forms link.

When we checked, redirect was included on all three paid plans. The cheapest, Basic, was $8/month billed annually or $16 monthly, with 50 responses a month and 3 forms. That is a big step down from Google Forms' unlimited responses, so compare it against a form builder that includes redirects before you commit.

If the redirect is the point, a form builder that does it natively removes every caveat above. It works from the direct link, counts only real submissions, and needs no script. When checked, Tally included redirect on completion on its free plan, Typeform offered it on paid plans, Youform put it on Pro, and Zunoform includes it on every plan.

The trade is migration effort. Some builders, including Zunoform, can import an existing Google Form so you don't retype the questions. Existing responses stay in your Google sheet.

Four reasons come up again and again. Conversion tracking: ad platforms and analytics count a visit to your own thank-you page as a conversion, and a Google-hosted confirmation page can't carry your tracking code. Next steps: sending people straight to a calendar, a payment page or a download while they're still engaged. Personalization: showing a result or offer based on their answers. Continuity: people finish on your site instead of a docs.google.com page with Google's footer.

If you need only the second reason, the confirmation-message link probably does the job. The first and third need a real redirect, and the third needs one that can carry answers.

Zunoform has redirect after submit on every plan, including Free. Each ending screen has an Auto-redirect toggle, a redirect URL, and a delay you can set from 0 to 60 seconds, so people can read a short message before they move on. The URL can carry answers: pick answers from the token list under the redirect URL and they're inserted into the query string (for example ?plan= followed by the respondent's choice), URL-encoded, when the redirect fires. Number variables, such as a calculated total, can go in the same way. Only http and https targets are followed. Because each ending screen has its own redirect, an outcome quiz or branching form can send different people to different pages.

Where it doesn't fit: the Free plan is capped at 500 responses a month and shows a small "Powered by" badge, while Google Forms and Tally are unlimited on free. If a clickable link in the confirmation message is enough, stay on Google Forms and use Method 1.