Google Sites QR codes: link to the published page
Key Takeaway
Make a Google Sites QR for the published page. Check site and embedded-file access, anchors and updates, then create and test the URL in QRLynx.
Create a Google Sites QR from the published page address visitors should open, then paste it into QRLynx Website / Link. Review Published site access and test the destination on a phone before printing.
An editor preview, a published site and an embedded Drive file are separate surfaces. A working editor session does not establish that your audience can see the live page or every file inside it.
Publish the destination you intend to distribute
Google’s publishing guide separates Preview from Publish. Preview lets an editor inspect layout options; Publish makes the chosen version available at its web address. Visit that published address and navigate to the exact page the QR should open.
In sharing controls, review Published site. Google documents Restricted and Public choices, with other options possible in work or school accounts. Use the audience that fits the material. Restricted access is valid when the people scanning are intentionally authorized.
After editing the site, publish the intended changes and check the live page. Do not approve a poster by looking only at the editing canvas.
Three separate access checks
| Surface | Check as the intended visitor | What this avoids |
|---|---|---|
| Published page | The correct page loads for the approved audience | Distributing an editor or owner-only route |
| Embedded file | The intended document is visible to that audience | A public page containing a restricted resource |
| Page or heading target | The complete URL reaches the useful section | Landing on a changed or incorrect section |
Check embedded files independently
Google states that files with restricted sharing, including files on shared drives, remain visible only to people with access to those files. Someone can open the site and still be unable to read an embedded document.
Review the page and each important resource separately. If a file is intentionally restricted, test with an appropriate authorized account. Do not broaden its audience merely to remove an access message from a public page.
The Google Drive QR guide covers file-sharing permissions. Keep the site as the page owner when it supplies navigation and context for several resources.
How to create a published Google Sites QR with QRLynx
Check the live page and its resources before distributing the QR.
Prepare the visitor page
Finish the relevant page in Google Sites and use Preview to inspect the phone layout. Review the material and audience before publishing.
Publish and open the real address
Publish the site, visit its live web address and navigate to the page or supported heading anchor visitors should reach.
Check site and file audiences
Review Published site access, then open important embedded files as the intended visitor. Keep restricted access intentional.
Create the QRLynx link QR
Paste the complete published destination into Website / Link. Use static for a final direct address, or a saved dynamic URL QR when destination replacement or eligible scan activity matters.
Label and export the artwork
Use a task label such as Open the workshop resources. Preserve contrast and a clear QR border, and provide a readable alternative link where practical.
Test the final visitor journey
Scan the final printed or displayed proof on a phone. Check the landing page, section, navigation and important resources. Retest after site, address or access changes.
Use the approved visitor address
Create the QR for your published site page
Use the tested URL after reviewing the site audience and embedded resources.
Decide what changes require another check
Google Sites supports links to headings on a published site. Its documented control is Settings, Viewer tools, Show anchor links, followed by Publish. If you use an anchor, retain the complete address, including the # fragment, and verify the target after edits.
For a changed destination address, update and retest an authorized QRLynx dynamic destination or replace static artwork. When the URL stays the same but the page changes, keep the artwork only after checking the new live content and resources.
Google’s search-engine opt-out is separate from access control. Google describes it as a request and says exclusion is not guaranteed. Use audience settings for controlled access rather than relying on a search preference.
Sources and related guidance
Google documents publishing, audiences, search opt-out and anchors, plus embedded files and their access requirements. Continue with QRLynx Website / Link or the QR scanner.
Questions before distributing a Google Sites QR
Which Google Sites address belongs in the QR?
Use the published visitor address for the exact page you want to distribute. Open it outside the editing canvas and check the audience. A preview or editor route does not replace a live published-page check.
Why are my latest edits missing after someone scans?
Check whether the intended changes were published and whether the QR opens the page you updated. Google distinguishes editing and previewing from publishing. Verify the visitor address rather than assuming the editor and live page are identical.
Can the site remain restricted when I distribute its QR?
Yes, when scanners are the people intentionally authorized to view it. Review Published site access and test the appropriate authorized and unauthorized contexts. The QR carries a route; it does not grant a Google account access.
Does opting out of search engines make the site private?
No. Google describes search-engine exclusion as a request that does not guarantee exclusion. Audience controls are separate. Use the intended Published site access setting for restricted material.
Can the QR open a specific page or heading?
Use the published page address. Google Sites also supports heading anchors when the relevant viewer setting is enabled and published. Preserve the complete tested address, including any fragment, and retest after changing the target section.
Why can visitors see the site but not an embedded file?
Google says restricted or shared-drive files remain available only to people who can access those files. Check the item’s audience separately. Publishing the surrounding page does not establish that the document is available to every visitor.
Is Google Sites Preview enough for the phone check?
Preview helps inspect layout, but it is not the final audience test. Open the published address on a phone in the intended visitor context. Check navigation, headings and embedded resources as well as the first screen.
What happens if the published site address changes?
A static QR still contains its former address and needs replacement artwork for a different destination. An authorized owner can update a saved QRLynx dynamic URL QR and test the new page. Neither action changes Google’s audience settings.
What should I verify on the printed QR proof?
Check the decoded route, correct published page, intended access and useful phone layout. Follow the page or heading target and open important resources. A camera reading the symbol is only the start of that check.
