-
How to write them.
Six steps, and the first one is the one everybody skips.
Give each page one job.
Write the title as ad copy.
Write a description that adds something.
Set a short, permanent slug.
Add a share image per page.
Publish, then read the live head.
-
The fiddly part, in detail
Do the writing outside the editor. A title and a description are advertising copy, and copy is far easier to write with every page listed together in one document than one page at a time inside a settings panel, where you cannot see that four of them open with the same six words.
Give yourself roughly 60 characters for the title and roughly 155 for the description. Neither is a rule. Search results are truncated by pixel width rather than character count, and Google rewrites descriptions whenever it prefers its own. Writing to those lengths simply keeps the half that matters visible.
The description does not rank the page. It sells the click, which is why a description that restates the title is a wasted line and one that answers what will I get if I open this is not.
Where each field sits in the editor is not something this page will guess at. Open the page settings in the app and use the labels you find there. That screen is the authoritative source and this one is not.
Then publish and check. Load the live URL, view source, and confirm the title, description and share-image tags are in the
<head>. If an edit is not showing, that is a publishing or caching question rather than an SEO one.
Set the SEO title, description and slug for every page
Every page you publish carries its own title, description, slug and share image. Here is how to write them so they earn a click, and an honest list of the SEO controls Siter.io does not document.
Start for free -> See the plans
The short answer.
The list is short — per-page title, description, slug and share image on paid plans. Each field belongs to the individual page rather than to the site, and alongside them sits one site-wide field for code in the document head. What about the free plan? No - the free plan builds and previews privately; publishing needs a paid plan, so there is no public URL for a crawler to look at in the first place.
-
Four fields, one page at a time
Title, description, slug and share image belong to the individual page, so each one can aim at the thing people actually type. That is the whole value of per-page control: the pricing page and the about page are found by different searches, and writing the same sentence twice wastes both.
-
One code field, for the whole site
Site-wide head code on paid plans, plus an on-canvas embed element; no per-page body scripts. Read that last clause twice before you plan anything around it. Verification tags and site-wide scripts fit comfortably; a snippet that should only run on one page does not.
Which plans include it.
One row, off on the free plan and on from the cheapest paid one. It is not the row that decides anything, though. The free plan does not publish at all, so it never reaches the point of needing a title tag.
| Feature | Start (free) | Solo $7 | Plus $12 | Pro $24 |
|---|---|---|---|---|
| SEO | No | Yes | Yes | Yes |
Read off the “View all features and options” table on siter.io/pricing on 2026-09-03.
Worth reading next to it: the webpage cap. 10 pages on Solo, 50 on Plus, unlimited on Pro. On a ten-page site every page has to earn its place, which is a healthier constraint for search than it sounds.
Four things that bite.
The last two are the ones a professional needs. A list of what a tool does is easy to find; what it does not do is the part that costs you a weekend.
-
The title is not the heading
The h1 on the page talks to somebody already reading it. The title tag talks to somebody scanning ten blue links and deciding which one to open. Repeating the heading throws away the only line of advertising copy you are given for free.
-
A slug is a promise
Short, lowercase, hyphenated, and about the page rather than the campaign that sent people to it. Change it later and every link to the old address breaks, which matters more here than elsewhere, because redirects and 404 handling are not documented by Siter.io. Assume no safety net and pick the slug once.
-
Head code is site-wide
A Search Console verification tag, or a script you genuinely want on every page, belongs in the head code field. Anything meant for one page only does not fit, and there are no per-page body scripts, so a tracker that must fire on a single thank-you page needs rethinking.
-
Assume nothing is automatic
Sitemap generation, robots.txt editing, structured data and canonical tags are not documented anywhere in Siter.io's own material. Neither is hreflang, which is moot while multi-language sites are not a feature. None of it is safe to assume is quietly handled for you.
Frequently asked.
How do I add SEO to my website?
Write a title and a description for each page, give the page a short slug, add a share image, then publish and confirm the tags are in the live head. What Siter.io gives you is exactly that list — per-page title, description, slug and share image on paid plans — with each field attached to the page it describes. Anything that belongs on every page goes in the site-wide head code field instead.
How long should a meta description be?
Roughly 155 characters for the description and roughly 60 for the title are the working numbers. Neither is enforced by Siter.io, and neither is a real limit, because search results are cut by pixel width and Google rewrites descriptions when it feels like it. Put the useful half first and treat the rest as a bonus that may never be seen.
Does Siter.io generate a sitemap or let me edit robots.txt?
Neither is documented. Siter.io’s own material describes per-page title, description, slug and share image plus a site-wide head code field, and stops there. Structured data and canonical tags are not mentioned either. Rather than assume a sitemap exists, verify your site in Google Search Console and submit the URLs directly, then check what is actually served before planning around it.
Can I add Google Analytics or a verification tag?
Yes. Google Analytics and Meta Pixel, built in — so the two most common tags do not need the code field at all. A Search Console or Bing verification tag, or any other third-party script, goes in the head code instead. Site-wide head code on paid plans, plus an on-canvas embed element; no per-page body scripts — the last clause is the limit that catches people out.
Can I redirect an old URL to a new one?
Not in any way Siter.io documents. Everything its own material has to say about redirects and custom 404 pages fits in two words. Not documented. That is the most expensive gap on this page if you are moving an existing site across, so ask support before you change a slug that already has links or rankings pointing at it, and keep the old address reachable if you possibly can.
Does the free plan have SEO settings?
No. The SEO row is off on the free plan, and switching it on would change nothing. No - the free plan builds and previews privately; publishing needs a paid plan, so there is no public page for anyone to index and no search result to write a title for. The fields, and publishing itself, start from $7/mo billed yearly on Solo, the cheapest plan that puts a site on a public URL.
What is the share image for?
It is the picture that appears when somebody pastes the page into Slack, iMessage, LinkedIn or X. It is not a ranking factor and it does not appear in a search result. It decides whether a shared link looks like a real site or like a broken preview, which is worth one image per page rather than one for the whole site.
Do Siter.io sites load fast enough for search?
Measure your own published page and decide from the number. Performance depends mostly on what you put on the page, and a design coming out of Figma tends to arrive with full-width images and several font weights attached. Run the live URL through Lighthouse or PageSpeed Insights after publishing rather than taking any platform’s word for it, ours included.
Can I change the SEO settings after publishing?
Titles and descriptions, yes, and rewriting a weak one is normal work. Slugs are the exception. Changing a slug changes the URL, every existing link to the old one breaks, and with no documented redirect handling there is nothing to catch the traffic. Treat the title as a draft and the slug as permanent.
More of what the editor does
-
Custom domains
Point a domain you own at the site, included in every paid plan at no extra cost.
-
Hosting and SSL
No separate host to buy, no certificate to renew. It is part of the plan.
-
HTML download
Take a copy of a page and host it elsewhere. On Pro, and honest about the limits.
-
Forms
Design a form on the canvas and get the answers in your inbox.
-
Custom fonts
Upload the font files the design was made with, on every plan including free.
-
Responsive design
Three fixed breakpoints, laid out by you rather than guessed by the tool.
-
Teams and roles
Editor and viewer roles on every plan, with seats included rather than billed per head.
Also useful: Siter.io pricing in full and the Figma to HTML plugin.
-
Design it, then make it findable.
Import the Figma frame, finish it on the canvas, and write the title and description before you publish anything. The free plan builds and previews as much as you like; the SEO fields, and publishing itself, arrive with the first paid plan.
Get the plugin -> -
Start for free with Siter.io
Start for free ->