You can place a Google Form directly inside a WordPress post or page by copying Google Forms’ generated embed HTML and pasting it into a WordPress Custom HTML block. The form must be published and its responder settings must allow the people you expect to use it; otherwise the iframe can appear correctly while visitors still receive an access error.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
The reliable workflow is: confirm access in Google Forms, choose More → Embed HTML, copy the complete markup, insert a Custom HTML block in WordPress, paste the markup, then test the published page on desktop and a narrow mobile viewport.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What you need before embedding
There are two separate gates: Google must allow the visitor to open the form, and WordPress must allow your editing account to save the iframe markup. Check both before diagnosing the page layout.
1. A published Google Form
Google’s guidance states that responders cannot access an unpublished form. Open the form’s publication controls and confirm it is published before copying or testing the embed.
2. Responder access that matches your audience
Publication alone does not make a form universally available. Google Forms can restrict responses to a domain, a trusted audience, a group, or people who have the link. Choose the setting that matches your visitors. A form intended for a public game-community page will fail for visitors if it is limited to an organisation’s domain or a private group.
3. A WordPress editor that can save the markup
You need access to the block editor and permission to insert a Custom HTML block. On WordPress 7.0, the official Custom HTML documentation says that users without the unfiltered_html capability can have disallowed markup, including <iframe>, removed when a post is saved or updated. Your role, site configuration and security controls therefore affect whether the embed survives.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches4. The correct form and page open at the same time
Open the intended Google Form in one browser tab and the correct WordPress post or page in another. This avoids copying an old form’s code into a new page, or editing a draft while testing a different published URL. The generated code is tied to the form you selected, so verify the form title before copying.
Is a plugin or paid service required?
The documented route uses Google Forms’ own generated HTML and WordPress’s built-in Custom HTML block. No plugin, theme feature, hosting plan or other product is specified as necessary for this workflow. If your site policy prevents iframe markup, contact the administrator rather than installing an unverified workaround.
Step 1: Confirm Google Forms publication and responder settings
- Open the Google Form you want to display.
- Review its publication status. If it is unpublished, publish it before testing the WordPress page.
- Review who is allowed to respond. Check whether responses are limited to a domain, trusted audience, group or people with the link.
- Decide which visitor identity the form requires. If visitors are not members of the permitted domain or group, change the responder setting or use a form configured for the audience you actually serve.
- Save the form settings, then open the form as a visitor where possible. This separates a Google access problem from a WordPress embedding problem.
Do this first because a correctly inserted iframe cannot bypass Google’s responder permissions. If the form reports that a responder lacks access, fix publication or audience settings before changing WordPress code.
Test access independently
Use a browser session that represents the intended visitor, such as a signed-out window when the form is meant to accept public responses. If the responder rules require a particular account, test with an account that meets that rule. An owner’s session can hide an access restriction that ordinary visitors will encounter.
Keep in mind that changing the form’s publication or responder settings changes what the existing embedded frame can do. You normally do not need to create a new WordPress block simply because the audience rule changed; retest the live page after saving the Google setting.
Step 2: Copy Google’s generated embed HTML
- With the form open, open the form’s More menu.
- Choose Embed HTML.
- In the dialog, select Copy to copy the HTML shown. Google’s documented instruction is: “Select Embed HTML. To copy the HTML that shows, click Copy.”
Copy the generated block as a unit. Do not copy only the form’s browser address and do not remove the iframe attributes before you have confirmed that the unmodified embed works. Google generates the markup intended for insertion into a website; using that output gives you the dimensions and document URL associated with the form at the time you copied it.
Keep the copied code available while you edit WordPress. If you switch between tabs, make sure you paste the complete markup rather than a shortened URL or a partial selection. If you accidentally overwrite the clipboard, return to the form and use More → Embed HTML → Copy again instead of reconstructing an iframe by hand.
Why use Google’s code instead of a responder link?
The responder link identifies the form, but it is not the same input as the generated embed HTML. Google’s documented website method supplies HTML intended to be placed in a page. WordPress’s generic Embed block, by contrast, starts with a URL and attempts to select a supported provider transformation. Using the generated code gives you one clearly documented handoff between the two products.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Step 3: Insert the code in a WordPress Custom HTML block
- Open the WordPress post or page where the form should appear.
- Place the cursor at the insertion point and open the block inserter with the + button.
- Search for and insert Custom HTML.
- Paste Google’s complete embed markup into the HTML field.
- Save the draft, or update the existing post. Publish when you are ready for visitors to use the form.
The Custom HTML block is the documented WordPress route for inserting raw HTML such as an iframe. Keep the code in that block rather than a paragraph or plain-text block; a paragraph block treats the markup as text instead of rendering it.
Where exactly do you paste the code?
Paste it into the large HTML field inside the Custom HTML block, at the location where the form should appear. Do not paste it into the page title, a paragraph block, the WordPress URL field, or a browser address bar. Text outside the block can introduce the form, explain who should respond, or provide instructions; the iframe markup itself belongs in Custom HTML.
What to expect in the editor
The editor may show an HTML editing area rather than the final form. Use the editor’s preview option and, more importantly, open the saved or published page. The live page is where you can verify the form’s loading behavior, available height and visitor permissions.
After saving, reopen the block and confirm that an iframe element or the original generated markup remains. If it has been replaced by ordinary text or disappeared, troubleshoot WordPress filtering before adjusting the frame’s size.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Step 4: Save, publish and test the live page
- Save or update the page after pasting the code.
- Open the page’s preview or published URL in a separate tab.
- Confirm that the form frame appears and that the first questions and controls are visible.
- Test the page at a normal desktop width.
- Test it again with a narrow mobile viewport or a phone. Check that visitors can scroll through the form and reach its submit control.
- If appropriate, submit a test response using the form owner’s normal testing process, then verify that Google receives it.
There is no universal iframe height that works for every form. A short one-question form and a multi-section questionnaire need different amounts of vertical space, and the surrounding theme can change how the frame looks. Judge the result on the actual published page rather than relying only on the block editor.
A practical desktop-and-mobile check
On desktop, look for clipping caused by a narrow column, a frame that leaves excessive blank space, or a submit control below the visible area. On a narrow viewport, check horizontal fit, scrolling and whether visitors can reach every question without controls being hidden. The available sources do not promise a universal responsive behavior, so the published page—not a presumed default—is the authority.
Repeat this check after moving the block into a column, changing the theme, changing the form’s questions or replacing the page template. Any of those changes can alter the space available to the iframe.
Custom HTML block versus the generic Embed block
These blocks accept different inputs and should not be treated as interchangeable.
| Characteristic | Custom HTML block | Generic Embed block |
|---|---|---|
| What you paste | Google’s generated embed HTML, normally containing an iframe and its attributes | A third-party URL |
| How WordPress handles it | Renders the HTML you provide, subject to the editor account’s filtering and capabilities | Attempts to transform the URL into a provider-specific embed when that provider is supported |
| Documented route for this task | Yes. Google instructs you to copy the Embed HTML and WordPress documents Custom HTML for inserting HTML | The reviewed WordPress documentation does not confirm that a Google Forms responder URL is supported |
| Best next step when it fails | Check publication, responder access and whether WordPress removed the iframe | Use Google’s generated HTML in a Custom HTML block instead of repeatedly pasting the same URL |
If you tried the URL-only route first and nothing appears, that does not prove the form or WordPress is broken. It may simply be a provider-support limitation of the generic Embed block. Switch to the generated HTML workflow.
Which method should you choose?
Choose Custom HTML when you have Google’s generated markup and want the documented route. Choose the generic Embed block only when you have confirmed that your WordPress installation supports the specific provider and URL format; the WordPress documentation reviewed here does not make that confirmation for Google Forms responder URLs. In either case, the editor must retain the resulting content and the live page must be tested.
How WordPress filtering can remove an iframe
After saving, inspect the Custom HTML block again. If the iframe has vanished or the markup has been reduced to ordinary text, the problem may be the editing account’s capabilities rather than Google Forms.
The unfiltered_html capability
WordPress.org’s Custom HTML documentation, updated June 15, 2026, describes WordPress 7.0 behavior: users who do not have unfiltered_html can have disallowed markup such as <iframe> stripped when the post is saved or updated. This means two editors on the same site can see different results when they paste identical code.
What to do
- Ask a site administrator to check the role and capability of the account that is editing the page.
- Have an authorised editor with the required capability paste and save the generated markup, if that matches your site’s security policy.
- Check whether the site has additional security, hosting or editor configuration that sanitises iframe HTML.
- After any change, save the post again and inspect the resulting block and the published page.
Do not assume that an iframe disappearing proves Google blocked the form. First determine whether WordPress retained the code. The official documentation establishes capability-based sanitising, but it does not diagnose the configuration of an individual site.
Do not try to defeat a site’s security controls by inserting the code into an unrelated field or repeatedly switching blocks. The administrator should decide whether the account can receive unfiltered_html or whether the site’s policy requires another approved publishing process.
Troubleshooting by symptom
The page says responders do not have access
Return to Google Forms and verify both publication and responder permissions. Confirm that the intended visitors fit the selected domain, trusted-audience, group or link-based rule. WordPress cannot override those settings.
The iframe disappears after saving
Check whether the account has the unfiltered_html capability and whether the site is running the documented WordPress 7.0 behavior. If the capability is missing, the editor may remove the iframe during save. A site administrator must decide whether to use an authorised role or another approved configuration.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The editor changes or rejects the markup
Compare the block before and after saving. If the code is altered, inspect site-specific security, hosting and editor settings. The official WordPress documentation explains the capability-based rule, but a particular site can impose additional filtering. Preserve the original Google-generated code so you can paste it again after the configuration issue is resolved.
Rank #4
The form is present but cut off
Open the published page, not just the editor, and check the entire form at desktop and mobile widths. The sources do not establish a universal responsive layout or a standard iframe height. Adjust the embed dimensions only after viewing the real page and only as much as your layout requires. A multi-question form may need substantially more vertical space than a short form.
The form is excessively tall
Review the page at the widths your visitors use. A large frame can create unnecessary empty space for a short form, while reducing it too far can make the visitor’s experience feel cramped. Choose dimensions based on the actual question count and page layout; there is no source-supported one-size-fits-all value.
The form works for you but not for visitors
Test outside the owner’s signed-in session. Your account may satisfy a domain, group or trusted-audience restriction that ordinary visitors do not. Recheck the responder rule and publication state, then test with the same kind of account or link access your audience will use.
A forum post says iframes are disabled
A WordPress.org forum reply has reported iframe insertion being disabled for security reasons in that particular context. Treat that as an anecdotal, site- or version-specific report, not as a universal WordPress rule. The current official documentation describes the more precise capability-based behavior, so check your account and configuration first.
Keeping the embed usable on game and community pages
Place the form where the visitor expects an action to occur—for example, below instructions for a tournament sign-up, bug report or event questionnaire—then leave enough surrounding context that the visitor knows what the form is for. Keep the explanatory copy outside the iframe so it remains readable even while the form is loading.
Use a clear location
Add a heading or short paragraph immediately before the Custom HTML block that identifies the purpose of the form. This is especially useful on long posts where visitors may arrive at an anchor link or on a phone.
Check both viewport types after edits
Theme CSS, column widths and the form’s generated dimensions can interact. Recheck the live page after changing the theme, moving the block into a column, or editing the form’s questions. A layout that looks comfortable on a wide monitor can require more scrolling on a phone.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRetest after changing Google settings
Changing publication or responder access in Google Forms affects the same embedded frame. If a previously working page begins showing an access message, verify the form settings before replacing the WordPress block.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A complete pre-publish checklist
- The Google Form is published.
- Responder access includes the visitors you intend to serve.
- You copied the code from More → Embed HTML using Google’s Copy control.
- The code is inside a WordPress Custom HTML block.
- The editing account can save iframe markup, or an authorised editor has completed the save.
- The saved block still contains the embed rather than stripped or plain-text content.
- The published page loads the form.
- The form is usable at desktop and narrow mobile widths.
- The frame provides enough height for the questions and submit control.
- A test visitor can open the form under the configured responder rules.
When to choose a different approach
Use the generated HTML method when your goal is to display the Google Form inside a WordPress page and your site permits the required iframe markup. If your organisation’s security policy forbids iframe HTML or your editing role cannot retain it, involve the site administrator rather than trying to bypass filtering. The generic Embed block is not documented here as a guaranteed alternative for Google Forms responder URLs, so a URL-only paste should not be treated as an equivalent fallback.
If an administrator cannot approve iframe markup, you can still publish a normal link to the responder page as a separate design decision, but that is a navigation link rather than an embedded form and is outside the documented embed workflow. Do not describe it as equivalent unless your site has separately verified the behavior you need.
The documented path remains straightforward: make the form available to its intended responders, copy Google’s own embed HTML, place it in Custom HTML, and validate the result on the published page at both desktop and mobile widths.
Recommended Free Tools
Frequently Asked Questions
Where do I paste Google Forms embed code in WordPress?
Insert a Custom HTML block at the location where the form should appear, then paste Google’s complete generated HTML into that block’s HTML field. Do not paste it into a paragraph block or the page URL field.
Can I paste the Google Form link into WordPress’s Embed block?
The generic Embed block accepts a URL and tries to use a supported provider transformation. The WordPress documentation reviewed here does not confirm Google Forms responder URLs as supported, so use Google’s generated Embed HTML in a Custom HTML block instead.
Why does my embedded form say that responders do not have access?
Check that the form is published and that its responder settings allow the visitor. Google Forms can limit responses to a domain, trusted audience, group or people with the link. An iframe cannot override those restrictions.
Why does the iframe disappear after I save the page?
On WordPress 7.0, users without the unfiltered_html capability can have disallowed markup such as <iframe> removed when a post is saved or updated. Ask an administrator to review the editing role and any additional site security or editor filtering.
Recommended Free Tools
What height should a Google Form iframe use?
There is no universal height established by the documented sources. Test the published page at desktop and narrow mobile widths, then adjust dimensions only as needed so visitors can see and reach the questions and submit control.
Do I need a plugin or paid WordPress service?
The documented method uses Google’s generated embed HTML and WordPress’s built-in Custom HTML block. No plugin or paid service is specified as necessary. If your site blocks iframe markup, follow your administrator’s approved process rather than bypassing the restriction.
The Bottom Line
Publish the Google Form, set responder access for your intended audience, copy More → Embed HTML, and paste the complete markup into a WordPress Custom HTML block. Confirm the iframe survives saving, then test the published page on desktop and mobile. If visitors lack access, fix Google’s settings; if the iframe disappears, investigate WordPress capabilities and site filtering.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →
