The SEO checklist for a brand-new website covers four areas in your first 30 days: technical setup (so Google and AI crawlers can find and read you), on-page basics (titles, structure, internal links), content foundations (answer-first pages targeting winnable keywords), and tracking (Search Console + a rank tracker). Do these in order and you'll avoid the mistakes that keep most new sites invisible for months. Here's the complete list.
("seo checklist for new website" sees ~260 searches/mo and the broader "seo checklist" ~880/mo, difficulty ~36 — live keyword data, May 2026, via our Keyword Research module.)
1. Technical setup (do first)
- Verify the site in Google Search Console and submit your
sitemap.xml. - Make sure
robots.txtisn't blocking important pages — and allow AI crawlers (GPTBot, OAI-SearchBot, PerplexityBot, Google-Extended). - HTTPS, mobile-friendly, fast load. Run a site audit (or a quick free SEO audit) to catch issues.
- Set up clean, logical URLs and a shallow structure.
2. On-page basics
- Unique title tag (under ~60 chars) and meta description (under ~155) per page.
- One clear H1 per page; descriptive H2/H3 structure.
- Internal links between related pages with descriptive anchors — see internal links.
- Add Organization and (where relevant) FAQ schema as JSON-LD.
3. Content foundations
- Use keyword research to find low-difficulty, winnable terms — don't start on head terms.
- Write answer-first pages so they rank AND get cited by AI search.
- Cover one topic thoroughly (a pillar + supporting posts) rather than scattering.
4. Tracking
- Watch impressions and positions in Search Console (see how to read GSC).
- Add target keywords to a rank tracker.
- Be patient and consistent — see how long SEO takes.
The new-site mistakes to avoid
Chasing high-difficulty head terms on day one, publishing thin content, ignoring AI crawlers, and giving up before month three. New sites that win pick winnable keywords, publish genuinely useful answer-first content, and stay consistent. Start free on the pricing page.