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 glitchesGoogle Sites lets you create and publish a basic website without buying a separate website-builder subscription. On a computer, choose a blank site or template, add pages and content, preview the result, then publish it with a web address and a visibility setting. Your work saves as a draft automatically, but it does not become public until you publish it.
This guide follows Google’s current workflow and explains the account limits, page structure, accessibility checks, publishing choices, and fixes for the problems that most often make a new site appear incomplete.
As an Amazon Associate I earn from qualifying purchases.
What a free Google website actually is
Google Sites is a browser-based site builder for straightforward websites such as a personal information page, project hub, club site, event information site, classroom resource, or small organization presence. You create the site in Google Sites, and the new site is stored in Google Drive. The basic workflow does not require a separate website-builder subscription.
Outdated 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 matchWindows 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 reinstallA Google Site has two distinct states: an editable draft and a published version. Google Workspace Learning Center puts the distinction plainly: “Sites automatically saves every change you make, but your site isn’t public until you publish it.” Read the full getting-started instructions at Google’s Create your first site with Google Sites guide.
#1 Best Overall
That separation matters when you are working on a site with unfinished text, private information, or incomplete navigation. Saving protects your work; publishing is the action that makes the selected version available to the audience you choose.
Check access before you start
Google’s official getting-started instructions use a computer. Plan to do the initial setup, page organization, content editing, previewing, and publishing from a desktop or laptop. The material covered here does not establish that every editing task is available on every mobile device, so do not assume a phone can replace the computer-based workflow.
Use an account that can create Sites
Personal Google Accounts can be subject to the normal account settings, while work and school accounts may be governed by an administrator. Google says parent-managed Google Accounts cannot use Google Sites, although those users can see and edit existing sites. A workplace or school administrator may also restrict who can be added as an editor or how a site can be shared.
Recommended Free Tools
If a menu is missing, a create button is disabled, or sharing options are narrower than expected, confirm which account is active before changing your plan. Switch to an account permitted to use Sites, or ask the organization’s administrator whether Sites creation and editor sharing are allowed. Google’s account and access notes are collected in How to use Google Sites.
Prepare the material you want to publish
- Write a one-sentence purpose for the site. It should tell a visitor what the site contains and who it is for.
- Collect the text, images, links, contact details, dates, and documents that belong on the site.
- Separate material that is ready for public viewing from notes, drafts, or personal information.
- Decide whether visitors need one long page or several pages with a clear navigation structure.
- Choose a short site address that is easy to read aloud and type. Publishing will ask you to enter the web address.
Preparing these items first keeps the editor focused on structure rather than forcing you to invent navigation while a page is already public.
Plan the site before adding design
A useful small site usually has a clear home page and a limited set of supporting pages. Typical sections include About, Services or Projects, Resources, and Contact, but use labels that match your audience. A visitor should be able to predict what a page contains from its name alone.
Choose a page hierarchy
Use top-level pages for the main areas of the site. Use subpages when a group of related pages belongs under one subject, such as several project pages under Projects or several guides under Resources. Google’s Learning Center says subpages can be nested up to five levels, so keep the hierarchy shallower whenever a visitor can reach the information with fewer clicks.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Assign one job to each page
Give every page a primary purpose. A home page can orient a first-time visitor and link to the most important sections. A resource page can gather related links or files. A contact page can explain how to reach the organization without mixing those instructions into every other page. This approach makes the navigation easier to scan and reduces duplicated text.
Draft the navigation labels
Write the exact labels you expect to use before creating pages. Short, specific labels such as “Schedule,” “Application,” or “Project archive” are more useful than vague labels such as “Info.” If a label must be shortened in the navigation, put the fuller explanation in the page heading and introductory paragraph.
Create the site and set its identity
- Open Google Sites on a computer.
- Start with a blank site or select a template. A blank site gives you a clean structure; a template can provide an initial arrangement that you then replace with your own content.
- Name the site document so you can recognize it in Drive. This is the working file name and is useful when you manage more than one site.
- Enter a visible site title in the header. Use the name visitors should associate with the site, not an internal note or an unfinished working title.
- Check the header before moving on. Google’s Learning Center notes that the title appears in the published header and in the browser or mobile window title bar when the site has at least two pages.
The document name and the visible site title serve different purposes: one helps you find the file, while the other identifies the published experience. Set both deliberately so an internal label does not accidentally become the public identity.
Add pages and arrange them
Use the Pages panel to create the site’s navigation. Add a page for each major subject, then arrange the pages in the order a new visitor is most likely to need them. Reorder pages when the sequence does not match the visitor’s task, such as moving “Getting started” ahead of detailed reference material.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Create a page
- Open the Pages panel in the editor.
- Choose the control to add a new page.
- Give the page a concise, descriptive name.
- Place it at the appropriate level in the page list.
Turn related pages into subpages
When several pages belong to one subject, nest them beneath a parent page rather than putting every page at the top level. Review the resulting navigation as a visitor would: the parent should explain the group, and each subpage should answer a distinct question. Avoid deep nesting merely because the editor allows it; five levels is a maximum cited by Google, not a target for ordinary sites.
Review order before writing long pages
Open the page list and read it from top to bottom. Remove duplicate labels, identify pages that have no clear purpose, and move the most important destinations where they are easy to find. Fixing the structure early is faster than rewriting links after every page has been published.
Add text, headings, images, layouts, buttons, and links
Google Sites provides editing controls for text, images, section layouts, buttons, and links. Google’s detailed instructions are available in Add or edit text and images. Build each section around the information a visitor needs, rather than filling every available area.
Write scannable text
Start a page with a heading that states its subject. Follow it with a short explanation of what the visitor can do or learn there. Use smaller headings to divide distinct tasks, and keep paragraphs focused on one idea. Lists work well for requirements, steps, schedules, and grouped resources.
Do not use a decorative heading where an instructional one would be clearer. “Submit an application” tells a visitor what to do; “Welcome” does not. Keep terminology consistent across the navigation, headings, buttons, and links so the same destination is not given several names.
Use section layouts intentionally
Section layouts can place text and images in columns or other arrangements. Select a layout that matches the content: a single column for a detailed explanation, a side-by-side arrangement for a short comparison, or a compact group for related links. If a section becomes difficult to read on a narrow display, simplify it rather than adding more elements.
Add images with meaningful alternatives
Insert an image only when it communicates information or improves orientation. Give it meaningful alt text that describes its purpose. For example, an image showing the location of an event should have alt text that identifies the location or the map’s function, not a filename such as IMG_2048. If an image is purely decorative, do not use alt text to repeat nearby prose.
Rank #3
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Make links and buttons self-explanatory
Link text should tell visitors what will happen. “Download the registration form” is more useful than “Click here.” Use buttons for important actions such as opening an application, contacting the organization, or moving to a key section. Check every link after publishing; a well-designed button that leads to the wrong destination is still a broken user journey.
Keep embedded material understandable
When a page points to a document, spreadsheet, form, or external resource, explain what it is and what access a visitor needs. A link that works for the owner may still be inaccessible to the public. Test important resources while signed out or in a private browsing window when that is practical, and provide a plain-language alternative when a visitor cannot open the embedded item.
Make the layout readable before you publish
Design should help visitors find information, not compete with it. Use a consistent page title style, predictable spacing, and a small set of recurring patterns. Put the most important action or explanation near the start of a page, then provide supporting detail below it.
- Keep headings in a logical order instead of choosing sizes only for visual effect.
- Use strong contrast between text and its background.
- Break long instructions into numbered steps.
- Use bullets for unordered requirements or features.
- Keep button labels short enough to scan.
- Write image alt text and check that the page still makes sense without relying on pictures.
- Remove empty sections, placeholder text, and duplicate links before previewing.
These practices are content decisions rather than a substitute for Google’s editor controls. The editor can arrange elements, but it cannot decide whether a heading is meaningful or whether a visitor has enough context to complete a task.
Preview the site in different display layouts
Google recommends previewing before publication. Use the editor’s preview control to inspect how pages appear in the available display layouts. Look for clipped text, awkward line breaks, columns that become too narrow, images that dominate the page, and buttons that are difficult to identify.
- Save your current edits through the editor’s normal automatic-saving behavior.
- Open Preview.
- Switch among the available display layouts.
- Open each important page from the navigation, not only the home page.
- Follow every major button and link.
- Close Preview, correct problems, and preview again.
Preview is also a content check. Read the page as someone who knows nothing about the project. If a label, abbreviation, or image requires private background knowledge, add a short explanation before publishing.
Publish the site and choose who can see it
- When the draft is ready, select Publish.
- Enter the web address requested by the publishing dialog. Choose a concise address that matches the site’s purpose and is easy to share.
- Review the audience or visibility setting. Google’s publishing guidance says the creator decides who can see the site.
- Confirm the publication.
- Open the resulting address and inspect the live version, including navigation, images, buttons, and linked resources.
Publishing is the point at which the saved draft becomes a site that the selected audience can visit. If the site contains personal details, internal documents, or information intended only for a defined group, select a restricted audience rather than assuming the address itself provides privacy.
For the current controls and sharing terminology, use Google’s Publish and share your site help page. The exact options shown can depend on the account you are using and any administrator rules applied to it.
Understand draft, published, and updated states
| State | What visitors see | Your next action |
|---|---|---|
| Saved draft | The latest edits exist in the site file, but the site is not public merely because they were saved. | Continue editing or choose Publish when the content is ready. |
| Published site | Visitors with the permitted access can open the published version at its web address. | Check the live address and confirm the audience setting. |
| Edited after publication | The draft contains newer changes than the version visitors currently see. | Publish the changes again so the live site is updated. |
This distinction prevents a common mistake: checking the editor, seeing the new text, and assuming everyone else can see it. Always verify the published address after a significant change.
Update a published site safely
Open the site from Drive or Google Sites, make the edit, and review the affected page in Preview. When the change is ready, publish again. Google’s editing help repeats the publish step after edits because saving the draft alone does not update the live version.
For a scheduled announcement or event, publish early enough to test the public page, then return to the editor to correct errors. Keep a short record of which page changed when several people edit the same site, especially on a work or school account where editor permissions may be managed centrally.
Choose visibility with the audience in mind
Public information
Use the broadest audience setting only for information intended for anyone who receives the address. Remove private contact details, internal notes, and documents that should not be distributed widely. A public page should also explain unfamiliar acronyms and provide enough context for a first-time visitor.
Restricted or organization-only information
If the site is for a team, class, or community, use the available audience control that matches that group. Confirm that the people who need access can open both the site and any linked files. A site can be visible while a linked document remains restricted, creating a broken experience for readers.
Managed-account limits
Organization administrators can limit editor sharing or other access choices. If the expected audience option does not appear, ask the administrator what policy applies instead of repeatedly republishing. Parent-managed accounts cannot use Google Sites, according to Google’s help documentation, even though they can see and edit existing sites.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What Google’s help topics do and do not establish about advanced features
Google’s Sites Help index includes topics for custom domains, analytics, accessibility, and data export. Their presence confirms that Google documents these subjects, but the available guidance for this article does not establish the exact eligibility rules, connection steps, registrar requirements, pricing, or export format for each feature.
Custom domains
A custom-domain help topic exists for Google Sites, but do not assume that a branded address is included at no cost or that every account can connect one. Check Google’s current custom-domain documentation and your domain registrar’s terms before promising a particular address, fee, or setup path.
Analytics and data export
Analytics and export are separate topics from the basic create-and-publish workflow. If measurement or portability is essential to your project, review the relevant Google documentation first and confirm that the controls are available for your account and site type. Do not treat the existence of a help article as proof of a specific plan entitlement.
Free tools Windows power users keep installed
One-click scans. No signup required.
The central help index is available at Google Sites Help.
Troubleshoot the problems that stop a site from going live
The site looks complete in the editor but visitors see nothing
The most likely cause is that the draft has not been published. Automatic saving protects the draft; it does not make the site public. Select Publish, complete the web-address and visibility steps, then open the published address in a separate window.
Visitors see an older version
You changed the draft after the last publication. Review the page, open Preview, and publish the changes again. Then reload the public address and check the specific section that changed.
You cannot create a new site
Check the signed-in account. Parent-managed accounts cannot use Google Sites. On a work or school account, an administrator may restrict Sites creation or editor sharing. If the account is managed, contact the administrator before trying to build the project elsewhere.
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 →A collaborator cannot edit
The account may be subject to organization sharing rules, or the collaborator may be signed in with a different account than the one you invited. Verify the address used for sharing and ask the administrator whether editor access is limited. Keep the audience setting for visitors separate from editor permissions; they solve different problems.
A page is hard to find
Open the Pages panel and inspect its order and nesting. Move the page to a clearer position, rename it with a specific label, or place it beneath the correct parent page. Check the published navigation after republishing; a structure that seems obvious in the editor can be confusing when read as a visitor.
An image is confusing or inaccessible
Replace unclear imagery, add meaningful alt text, and place an explanatory caption or paragraph near the image when the visual alone is not enough. Preview the page in each available display layout to ensure the image does not push essential text out of view.
A linked file opens for you but not for visitors
The file’s permissions may be narrower than the site’s audience. Test the link from an account that represents the intended visitor, then adjust the file’s sharing or provide a different resource. Do not publish a link to a private document expecting the site’s visibility setting to override that document’s own access rules.
Recommended Free Tools
The address is difficult to share
Return to the publishing dialog and review the web address you chose. A short, readable address reduces typing errors and makes it easier to explain the site verbally. Avoid internal abbreviations that a first-time visitor will not recognize.
When Google Sites is a sensible choice
Google Sites fits projects that value quick setup, familiar Google account management, straightforward pages, and a simple publication workflow. It is especially practical when the people maintaining the site already use Google Drive and need a shared place for text, images, links, and organized resources.
Consider another publishing approach when your project depends on capabilities that have not been established here, such as a specific custom-domain arrangement, advanced analytics configuration, a particular export workflow, or highly specialized design behavior. Compare candidates on total cost, custom-domain control, design flexibility, ease of editing, and portability. Do not select a tool solely because it offers a template if it cannot meet the project’s access and maintenance requirements.
Quick Recap
Final launch checklist
- The site has a clear purpose and visible title.
- The document name is recognizable in Drive.
- Every page has a specific role and a useful navigation label.
- Related pages are nested logically, without unnecessary depth.
- Headings, paragraphs, lists, buttons, and links are readable and consistent.
- Images have meaningful alt text or are clearly decorative.
- Important links and files work for the intended audience.
- Preview has been checked in every available display layout.
- The web address is concise and appropriate for sharing.
- The visibility setting matches the information on the site.
- The published address has been opened and checked outside the editor.
- Later edits will be published again before you announce that the site is updated.
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:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →
