Site Maker
Students read web pages all day, and almost none of them have made one. Site Maker opens on a finished page about sea turtles. A student drags a picture to the other side and the words wrap round it, double-clicks a paragraph and types, and drops in a heading of their own. Beside the page is the real HTML and CSS it is made of, changing as they work. A box called Ready to publish? checks the page the way the web expects: words for people who cannot see a picture, colors that are easy to read, and no personal information. Then they publish it, and the page has its own link.
Using this with a class? Make a free class and add your students yourself: each gets a username and password, with no email or Google account needed. Or give them one join code. Using Google Classroom? Post the link there; with a free class, the link also puts each student in your class, so you see their work. mytekDev is also available from the Google Workspace Marketplace, so your school's Google admin can install it for everyone.A first lesson: Open See the code and give it to a partner. One student taps a part on the page; the other finds its lines in the code and reads them out. Then swap: one taps a line in the code, the other says which part of the page lit up and what the tag is called.
Set up a free class Share to Google ClassroomHomeschooling? A step-by-step kit uses Site Maker and ends with a certificate. See the kit
What a student actually does
They open the app on a finished one-page site about sea turtles, in a laptop frame: a big heading, a picture on the right with the words wrapping round it, a button that jumps to the fun facts, a line and a list. Six parts sit on the left: Heading, Words, Picture, Button, List and Line.
They drag a part onto the page and a green line shows where it lands, between two other parts. They drag a picture or a button to the left, the middle or the right of the page, and drag a picture's corner dot to make it small, medium or full width. A double-click on any words, or a second click, and they type straight onto the page, with Ctrl B for bold. Phone and Laptop show the same page at both widths: on a phone the picture moves to the middle, because the page's CSS says so.
See the code shows the page's HTML, with its CSS at the top. Tapping a part on the page lights its lines; tapping a line picks its part. Ready to publish? watches the page as they work: a red line for personal information or an empty part, which must be fixed, and an orange line for a picture with no alt text, colors that are hard to read, or a button that goes nowhere. Tapping a line says why it matters.
Publish puts the page on the web at its own link, with a square code to scan. The site builds the page itself from the saved project, checks it again, and asks search engines not to list it. Open in Code Editor carries the same page into the Code Editor, for a student ready to type the HTML themselves.
What they are learning while they play
Nothing here is presented as a lesson. This is what the activity is made of.
| What the student does | What it is |
|---|---|
| Taps a part on the page and finds its lines in the code | HTML elements and tags. Every part of a page is an element with a tag: h1 and h2 for headings, p for a paragraph, img for a picture, a for a link, ul and li for a list. The code pane lights the part's tag, so the student sees which words make which thing. |
| Drags a picture to the right and watches the words wrap | CSS and layout. The page's look is CSS: a few rules at the top of the code. A picture on the right is a float, and a rule further down undoes it on a narrow screen. Phone and Laptop show that one page fitting both. |
| Writes words for people who cannot see a picture | Alt text and accessibility. A screen reader reads a picture's alt text out loud. Without it, a person who cannot see the picture misses what it shows. Ready to publish? asks for it on every picture. |
| Picks a pale color for the words and sees an orange line | Readable contrast. Words need to stand out from the page: the web's rule for easy reading is a contrast of at least 4.5 to 1. The check measures it as the colors change. |
| Types a phone number and cannot publish | Public and private. A published page can be read by anyone with the link. A phone number, an email, a street address or a full name could lead a stranger to a real person, so those stop the page from going out. |
| Publishes and opens the link on a phone | How a page reaches a browser. The page is a file on a server, at an address. Any browser that asks for the address gets the same file, which is why the link opens on a parent's phone exactly as it looked in class. |
How to tell whether it landed
Ask, and let them show you. A student who has understood it can answer these without help.
- Point to the part of the code that makes your page's main heading. What is the tag called?
- Why does your picture move to the middle on a phone? Find the rule in the CSS that does it.
- What would a screen reader say about your picture? Where did those words come from?
- Why can't a page with a phone number on it be published, when a first name can?
- Who can open your page right now, and how would they find it?
Use it in your subject
Not a technology class? Then the app is how students show what they learned in your unit. More projects for every subject.
Computer science, grades 3 to 5
CSTA 2017 1B-AP-15: test and debug to make sure it runs as intended, in the Phone and Laptop views and the check; 1B-IC-19 and 1B-IC-21: accessibility, and using media with permission, in alt text and picture credits; 1B-NI-04: how a page travels to a browser, at the publish step. A page is not a program, so Site Maker claims the programming standards only through reading and testing the code, not the dragging.
Computer science, grades 6 to 8
CSTA 2017 2-IC-23: the tradeoffs between keeping information public and private, which is the Publish step and its personal information check; 2-IC-21: design that works for everyone, in alt text and contrast; 2-AP-17: test and refine. Open in Code Editor is the next step for a student ready to write HTML by hand.
English language arts
Common Core W.4.2.a and W.6.2.a ask for informational writing that uses headings and illustrations to aid comprehension, and W.4.6 and W.6.6 for using technology to publish writing. A one-page report site is both.
Digital citizenship
ISTE Standards for Students 1.2, Digital Citizen, and 1.6, Creative Communicator: what goes on a public page, who owns a picture, and making something others can read.
Practical notes
- AgesGrades 3 to 9. Younger students change the starter page's words and pictures and publish. Older ones read the code, fix every orange line, and carry the page into the Code Editor.
- TimeA minute to change the starter page. A first page of their own and a published link fit in one period of forty-five minutes. Reading the code and fixing the page for accessibility is a second.
- EquipmentA computer or Chromebook with a modern browser. Nothing to install. A phone helps for opening the published link.
- CostFree. The app has no paid tier.
- PrepNone to try it. To publish, students need a free account; the site's sharing rules apply, so a class set to share inside the class only cannot publish links.
- In a groupEveryone starts from the same sea turtle page, or one of the six starters. Pairs work well for the code-reading activity.
For co-ops, microschools, and classrooms
Make a class web: each student publishes a one-page report on a different animal, state or book, and the class collects the links on one page of their own made with Site Maker, with a button for each. Every page is checked for personal information before it goes out, and every published page has a Report link.
Common questions
Is Site Maker free?
Yes. It runs in your browser and there is no paid tier. A free account adds saving and publishing, but nothing on this page is behind a paywall.
Does my child need an account to try it?
No. The demo on this page is the whole app with the sea turtle page loaded. Publishing a page at its own link needs a free account.
Is the code real?
Yes. The page is real HTML with its CSS in the same file, and the code shown is exactly what is published. It has no script at all. Open in Code Editor carries it into the Code Editor, where it can be changed by hand.
Who can see a published page?
Anyone with the link. Search engines are asked not to list it, so it is found by its link, not by searching a name. A page with a phone number, an email, a street address, or the full name of the student or a classmate cannot be published. Every published page has a Report link, and taking the page down stops the link working.
Can students link to other websites or add videos?
Not yet. A button jumps to a heading on the same page. A page has no forms, no scripts and no embeds, so it cannot collect anything from the people who read it.
Where do the pictures come from?
Six drawings come with the app, and students can use their own pictures from their files on the site. A picture needs words for people who cannot see it, and a picture of their own asks who made it.
Still have a question? Ask us, and a person will write back.
Where to go next
Badge kits and learning kits
Step-by-step projects in Site Maker that end with a certificate: for a scout badge, or for homeschool families and classes.
- Make your first web page: Learning kit badge, or the learning kit for grades 3-8
Start with Site Maker
Trying it costs nothing and takes about five minutes. An account is what makes the work last.
Site Maker is one of the making apps on the platform. It is a place to make things, not a course, and it is not a substitute for a teacher: it is at its best when an adult asks the questions above and takes the answers seriously.
Page last reviewed November 2026.
Google, Google Classroom and Chromebook are trademarks of Google LLC.