Why English? | Reading Google Sites Published-Site Visibility Before Releasing a Student Website

Google Sites publishing matters because editing a site, previewing it, publishing a version and deciding who can see the published site are four different actions.

For students, parents and educators asking how to publish a Google Site, strong English matters because draft, preview, Publish, published site, Public, Restricted, published viewer, web address and search-engine request describe separate states.

This guide uses Google’s current Sites Help documentation checked on 3 November 2026. It supports student website publishing without suggesting that a public setting creates copyright permission, that search opt-out guarantees invisibility, or that publication equals school endorsement.

Reading routes

• Separate draft, preview and published states
• Choose Public or Restricted visibility
• Prepare content and provenance
• Support students and parents
• Run the publication check

Chapter 1 of 19: The editor is not the published website

What this publishing state means

Google Sites lets collaborators build a draft in the editor while viewers see the latest published version. Changes can exist without being public yet.

The website language to distinguish

Use draft for editable work and published version for the release currently available at the web address.

For The editor is not the published website, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A student fixes a citation in the editor but confirms that the public site still shows the earlier version until Publish is selected.

Autosaved editing does not guarantee public update. Record the release step and verify the site afterward.

• Name the draft.
• Name the published version.
• List unpublished changes.
• Choose a release owner.
• Verify after publishing.

Describe the same page in draft and published states.

The reasoning in The editor is not the published website transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Next chapter

Chapter 2 of 19: Preview simulates layouts but does not publish

What this publishing state means

Google provides Preview and layout choices so the creator can inspect the site before release. Preview is a checking state, not a public publication action.

The website language to distinguish

The verb preview means inspect before release. It does not create a lasting audience or canonical web address.

For Preview simulates layouts but does not publish, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A student checks desktop, tablet and phone layouts before asking the teacher for a final review.

Preview cannot reveal every browser, accessibility or account issue. Perform an authorised viewer test after publication too.

• Preview every page.
• Switch layout sizes.
• Check navigation.
• Read text aloud.
• Return to edit when needed.

Make a ten-item preview checklist.

The reasoning in Preview simulates layouts but does not publish transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 3 of 19: Publish creates or updates the released version

What this publishing state means

Google’s Publish action releases the chosen draft changes to the site address. The release should follow a deliberate review, not an accidental click.

The website language to distinguish

The verb publish is stronger than save. It means make a version available to the selected published audience.

For Publish creates or updates the released version, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A project team records the release date, reviewer and major changes before publishing its final exhibition site.

Publication can expose mistakes instantly to the permitted audience. Keep a correction and withdrawal plan.

• Review changes.
• Confirm audience.
• Confirm web address.
• Publish once.
• Check the live result.

Write a release note with version, reviewer and date.

The reasoning in Publish creates or updates the released version transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 4 of 19: Pre-publish review compares draft with the current public version

What this publishing state means

Google Sites can show a side-by-side comparison: the draft on the left and current published version on the right, with annotations for unpublished changes.

The website language to distinguish

The adjective unpublished describes changes not yet released. It does not mean private if the old version remains public.

For Pre-publish review compares draft with the current public version, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A student notices that removing a paragraph from the draft will not remove a downloadable file linked elsewhere and checks that separately.

The review can be turned off for a site. If it is off, use an equivalent manual release checklist.

• Open the comparison.
• Visit changed pages.
• Read annotations.
• Check links and files.
• Return to edit if uncertain.

Explain one addition, one deletion and one unchanged public element.

The reasoning in Pre-publish review compares draft with the current public version transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 5 of 19: Editors must review changes is a process control

What this publishing state means

Google documents a setting requiring editors to review changes before publishing; it can be disabled for a site. The control helps teams pause at the release boundary.

The website language to distinguish

The word review should name criteria and authority. Looking at a screen is not the same as approving claims, privacy and attribution.

For Editors must review changes is a process control, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A project requires one peer content check and one teacher publication approval before release.

A checkbox cannot replace responsibility. Keep human criteria for facts, permissions and safeguarding.

• Define review criteria.
• Assign reviewers.
• Resolve comments.
• Record approval.
• Publish the agreed version.

Create a compact content, privacy and link review rubric.

The reasoning in Editors must review changes is a process control transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 6 of 19: Public visibility means anyone can view the published site

What this publishing state means

Google Sites allows a published site to be Public, meaning it can be viewed broadly according to the current service and account controls.

The website language to distinguish

The word Public should trigger a page-by-page review for names, faces, contact details, school work, licensed media and hidden downloads.

For Public visibility means anyone can view the published site, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A student portfolio uses approved public samples and removes classmates’ identifiable information.

A public site can be copied, indexed or shared beyond the intended conversation. Publish only material authorised for that audience.

• Inventory personal data.
• Check media rights.
• Remove draft notes.
• Test every page.
• Set a review date.

Classify site content as public-ready, restricted or remove.

The reasoning in Public visibility means anyone can view the published site transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 7 of 19: Restricted visibility needs named published viewers

What this publishing state means

Google says a Restricted published site can be shared with specific people or groups as Published viewers. This is separate from editing access.

The website language to distinguish

A Published viewer can view the released site; the label does not automatically grant editing of the draft.

For Restricted visibility needs named published viewers, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A class exhibition remains restricted to students, teachers and invited families through verified accounts.

Named viewers may lose access or use the wrong account. Provide a legitimate support route without sharing credentials.

• Choose viewers.
• Verify addresses or groups.
• Explain sign-in.
• Test one account.
• Remove stale viewers.

Write a restricted-view invitation with account and support instructions.

The reasoning in Restricted visibility needs named published viewers transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 8 of 19: Work or school accounts may show additional audience choices

What this publishing state means

Google notes that Sites used through work or school can provide other visibility options. These depend on organisational configuration.

The website language to distinguish

Do not assume “school only” means one class. Name the domain, organisation or group that the interface actually shows.

For Work or school accounts may show additional audience choices, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A school site uses an organisation audience for staff resources and a restricted list for a student feedback page.

Administrators can limit external publishing. Do not bypass that control with a personal account.

• Read the live audience label.
• Ask who belongs.
• Follow school policy.
• Use groups carefully.
• Document exceptions.

Translate an account-specific audience label into a plain-language sentence.

The reasoning in Work or school accounts may show additional audience choices transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 9 of 19: A web address is part of the public identity

What this publishing state means

Google asks for a web address when publishing. The address should be stable, clear and appropriate for the project.

The website language to distinguish

A web address identifies the route to the site; it is not the page title, search ranking or proof of authenticity.

For A web address is part of the public identity, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A science project uses a neutral address tied to the topic rather than a student’s full name or year of birth.

Previously used addresses can create conflicts. Google says a creator may need to change the address or permanently delete an old owned site.

• Choose a durable slug.
• Avoid personal data.
• Check spelling.
• Record the canonical address.
• Update old links.

Compare a privacy-safe address with one that exposes unnecessary identity.

The reasoning in A web address is part of the public identity transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 10 of 19: Changing the address creates a link-management task

What this publishing state means

When a published address changes, earlier bookmarks, QR codes, documents and messages may point to the old route.

The website language to distinguish

The adjective current should be attached to one verified address. “The site moved” needs a date and replacement route.

For Changing the address creates a link-management task, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A student updates presentation slides and competition materials after an authorised site-address change.

Redirect behaviour and account options vary. Test the old and new routes instead of promising an automatic redirect.

• Inventory old links.
• Publish the new address.
• Update key materials.
• Notify the intended audience.
• Test both routes.

Create a link-change notice that identifies the valid address.

The reasoning in Changing the address creates a link-management task transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 11 of 19: Search-engine opt-out is a request, not a guarantee

What this publishing state means

Google explicitly warns that opting a public site out of search engines is only a request and does not guarantee the site will not appear.

The website language to distinguish

The phrase request search engines not to display is weaker than “make private.” Use Restricted when the audience must be controlled.

For Search-engine opt-out is a request, not a guarantee, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A class project that should remain within families uses Restricted visibility rather than relying on search opt-out.

Other links, screenshots and caches can persist. Do not publish sensitive material publicly and hope it remains undiscovered.

• Choose visibility first.
• Treat opt-out as supplementary.
• Remove sensitive data.
• Check search appearance.
• Close public access when done.

Rewrite “hidden from Google” as an accurate statement.

The reasoning in Search-engine opt-out is a request, not a guarantee transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 12 of 19: Every page and subpage needs a publication check

What this publishing state means

A multi-page site can contain forgotten pages, duplicate navigation, old downloads or unfinished subpages. The release scope is larger than the home page.

The website language to distinguish

Use a page inventory with status words: publish, revise, restrict or remove.

For Every page and subpage needs a publication check, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A team discovers an old interview-transcript subpage and removes it before public release.

Hidden-from-navigation does not necessarily mean inaccessible by direct link. Verify the actual published behaviour.

• List all pages.
• Check navigation.
• Open direct links.
• Review files.
• Confirm release status.

Build a site map and assign one decision to every page.

The reasoning in Every page and subpage needs a publication check transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 13 of 19: Images, quotations and downloads need provenance

What this publishing state means

A student site may combine original work, licensed media, quotations, data and shared files. Each item needs a legitimate source and permitted use.

The website language to distinguish

Use verbs such as photographed, adapted, quoted and used under licence.

For Images, quotations and downloads need provenance, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A history site credits archive images and links to source records while distinguishing student interpretation.

Attribution alone cannot cure a licence violation or private-data exposure. Confirm permission and context.

• Keep a source log.
• Credit creators.
• Check licences.
• Remove unauthorised media.
• Review downloads.

Write two image captions that include provenance without clutter.

The reasoning in Images, quotations and downloads need provenance transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 14 of 19: Forms, embeds and external files have their own access rules

What this publishing state means

A Google Site can link or embed other resources whose permissions may differ from the site audience. A public page can still contain an inaccessible file, or expose an over-broad one.

The website language to distinguish

The prepositions on the site and accessible through the site are not identical. Test each embedded object separately.

For Forms, embeds and external files have their own access rules, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A public project embeds a viewable chart but keeps raw survey responses restricted.

External services and accounts can change. Record owners and review permissions after publication.

• List embeds.
• Test signed-out access.
• Protect raw data.
• Name owners.
• Remove obsolete objects.

Create an embed audit with object, owner, audience and result.

The reasoning in Forms, embeds and external files have their own access rules transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 15 of 19: Parents can ask who can see which version

What this publishing state means

Parents can help a young publisher separate draft editors, published viewers and public visitors. The key is to ask for the actual audience and live address.

The website language to distinguish

Use specific questions: “Is this the draft or published version?” “Is the published site Public or Restricted?”

For Parents can ask who can see which version, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A parent notices a full name on a public page and helps the child use the school’s correction route before sharing wider.

Parents should not override school publishing rules or post a child’s work under a personal account without approval.

• Ask for the live address.
• Ask who can view.
• Check identifying details.
• Let the student correct.
• Use school support.

Role-play a calm pre-publication family review.

The reasoning in Parents can ask who can see which version transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 16 of 19: Students can write for the real audience

What this publishing state means

A website needs orientation, headings, concise paragraphs, descriptive links and honest limitations so a visitor can understand it without the creator standing beside them.

The website language to distinguish

Replace vague link text such as “click here” with the destination and purpose. Distinguish fact, evidence and interpretation.

For Students can write for the real audience, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A student science site explains the method, sample limits and what the results cannot establish.

Clear writing does not guarantee a high grade or ranking. It makes the work more usable and reviewable.

• Name the audience.
• Lead with purpose.
• Use descriptive headings.
• Link evidence.
• State limits.

Revise one page so a first-time visitor can act without explanation.

The reasoning in Students can write for the real audience transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 17 of 19: Career and further-study portfolios need selective evidence

What this publishing state means

A published site can present projects, reflections and skills when the learner is authorised to show the material and can explain their contribution.

The website language to distinguish

Use evidence verbs: designed, analysed, revised and collaborated.

For Career and further-study portfolios need selective evidence, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A student portfolio links a cleaned project and explains one challenge, decision and learning outcome.

Admissions and employers use varied processes. A website does not promise an offer, and public visibility may not suit every project.

• Select representative work.
• Protect client or school data.
• Credit collaborators.
• Explain decisions.
• Review annually.

Turn a gallery caption into an evidence-based project note.

The reasoning in Career and further-study portfolios need selective evidence transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 18 of 19: Unpublishing and restriction are different responses

What this publishing state means

A creator may need to stop public access, change visibility or correct a released version. These actions have different consequences.

The website language to distinguish

Use precise verbs: unpublish, restrict, republish and delete. Do not use “take it down” for every case.

For Unpublishing and restriction are different responses, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A team changes a public exhibition to Restricted while it reviews a privacy concern, then republishes an approved version.

Search caches and copied content may persist. Serious exposure requires the school’s incident process.

• Identify the problem.
• Choose the right action.
• Preserve required evidence.
• Notify the authorised adult.
• Verify the final state.

Write a factual correction update without promising total erasure.

The reasoning in Unpublishing and restriction are different responses transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Next chapter

Chapter 19 of 19: A handover should include draft, published and linked assets

What this publishing state means

The next owner needs the editor access list, published audience, current address, page inventory, embeds, source log and update schedule.

The website language to distinguish

A handover should say what is live now, what remains draft and who is authorised to publish next.

For A handover should include draft, published and linked assets, complete a release record: current draft, changes since last publication, intended published audience, exact web address, pages included and authorised reviewer. Then inspect the public or restricted viewer experience rather than relying on the editor screen.

A student-site example, limitation and next action

A graduating project leader transfers the site record to the teacher and next cohort without sharing passwords.

Account ownership and domain controls may require administrator help. Follow the institution’s process.

• Confirm owners.
• Record current address.
• List live pages.
• Audit embeds.
• Set next review.

Create a handover table with state, owner, audience and action.

The reasoning in A handover should include draft, published and linked assets transfers to portfolios, class blogs, documentation and workplace websites: separate authoring, preview, release, visibility, search discovery and withdrawal so that every public claim has an owner and evidence.

Back to reading routes · Previous chapter · Continue to the FAQ

A practical Google Sites publication check

Treat the site as a real publication with an audience, address, version and owner.

• Preview every page at several layout sizes.
• Use pre-publish review to compare draft and published versions.
• Inventory pages, embeds, links and downloads.
• Confirm provenance, privacy and school approval.
• Choose Public or Restricted deliberately.
• Set and record the current web address.
• Publish, then test as the intended viewer.
• Keep a correction, restriction and handover plan.

For parents: ask whether you are looking at the draft or published version, whether the published site is Public or Restricted, and whether names, images and downloads are authorised.

For students: preview is not publish, and public is not private because a search opt-out box is selected. Review every page, credit sources, test the viewer route and keep one current address.

Frequently asked questions

What is the difference between preview and publish?

Preview helps inspect the site before release; Publish creates or updates the version available to the selected published audience.

Can I restrict a published Google Site?

Yes. Google documents Restricted visibility with specific people or groups added as Published viewers.

Does search opt-out guarantee that a public site will not appear in search?

No. Google explicitly says it is a request and not a guarantee.

Do work or school accounts have other audience options?

They may, depending on organisational settings.

Why should I check embeds separately?

Embedded forms, files and media can have permission settings different from the site itself.

Useful next reading

• Google Sites Help: publish and share your site
• Google Sites Help: review changes before publishing
• Why English? Google Drive ownership transfer
• Why English? Group projects and useful feedback
• Why English? Explaining scientific evidence
• English Learning Hub: Primary to adult English
• How English works when reading instructions
• How English works in explanation
• Study skills for Secondary School English
• Why English remains important in twenty-first-century Singapore
• MOE EdTech Masterplan
• IMDA Digital Skills for Life framework

English matters because a student website exists in states: draft, previewed, published, public, restricted, discoverable, corrected and withdrawn. Precise labels help learners publish confidently without confusing visibility with permission or quality.