Search · File

SEO launch checklist: what to check before and after go-live

34 checks before launch and 15 for the first month, each with the tool to open and what to look for. Status dropdown and progress counters included.

A spreadsheet to work through when a new website goes live or an old one is rebuilt. It covers launch readiness for search: can crawlers reach the pages, does each page have one address, do old URLs redirect, are titles and descriptions in place, does the phone version carry the full content, is analytics recording. Every row names the tool or report to open and what you should see there. It is written for site owners, freelancers and project managers who launch with a developer or a site builder, and it follows Google Search Central documentation read on 4 October 2026.

What is inside

  • How to use: the working order, what each status means and which rows to treat as launch blockers.
  • Before launch: 34 checks in eight areas (indexing, structure, pages, content, speed, mobile, analytics, legal basics).
  • For every check: the action to take, the report or tool to open, and one line on why it matters.
  • First month: 15 follow-up checks by week, from sitemap status to the first queries and real-user speed data.
  • A status dropdown in each row and progress counters at the bottom of both check sheets.
  • Rows marked “Relaunch only” for redirects, the old-site baseline and a change of domain.

How to use it

  1. Open the How to use sheet first: it explains the order and the four statuses.
  2. On Before launch go from top to bottom. Do the action in “How to check”, set the status and write what you found in the note.
  3. Close every row in Indexing and Structure before the site goes public. Mark rows that do not concern your site as Not applicable.
  4. On launch day switch to First month and follow the “When” column: launch day, week 1, week 2, weeks 3–4.
  5. Watch the Progress rows at the bottom of each sheet. They count the statuses for you, so do not type over them.
  6. Keep the file after the first month: it is your record of what was checked, when and by whom.

The order to work through it

The sheet runs from what blocks search engines outright to what only polishes the result. A site with a leftover crawl block or a broken redirect cannot be read at all, so those rows come first and should be closed before the public launch. Titles, alt text and speed matter too, but a gap there can be fixed in the first week without hiding the whole site.

Work with whoever has access to the server and the CMS. Many rows are quick if you can open the page source and the browser's developer tools. Several need Google Search Console, so set it up before launch day, not after.

AreaWhat you settleWhen to close it
IndexingCrawlers can reach the pages and no leftover block hides themBefore launch, no exceptions
StructureOne address per page, working redirects, a real 404Before launch, no exceptions
PagesTitles, descriptions, main headings, markup, faviconKey pages before launch, the rest in week 1
ContentNo placeholders or copies; images and links are describedBefore launch
SpeedA lab test of the main page typesStart before launch, continue after
MobileThe phone view works and carries the full contentBefore launch
AnalyticsVisits and enquiries are recorded from day oneBefore launch
Legal basicsRequired pages and contact details are publishedBefore launch

What the checklist does not replace

This is a readiness check, not an audit. It samples one page of each type and the main reports. A full technical audit crawls every URL, reads the server logs, tests how scripts render and looks for problems that only show up at scale.

It also says nothing about whether the content deserves to be found. Google's own starter guide puts useful, original content ahead of every technical suggestion, and no row here can judge that for you. A file with every row marked Done means search engines can find, read and show the site. Where it appears in results is a separate question.

  • A full technical audit of every URL, the server logs and script rendering.
  • A review of content quality, search demand and the offer on each page.
  • Legal advice on privacy, cookies and consumer rules in your country.
  • Ongoing monitoring: Google suggests looking at Search Console about once a month and after changes to the site.

New site or relaunch

For a brand-new domain, set the rows marked “Relaunch only” to Not applicable. Expect a quiet start: Google's help says it can take a week or so before a new site begins to be crawled and indexed, and a new site has no real-user speed data until enough people have visited it.

For a relaunch, the redirect rows carry most of the risk. Google recommends permanent server-side redirects from each old URL to its matching new page, advises against sending everything to the home page and suggests keeping redirects for at least a year. It also notes that visibility can fluctuate while the new addresses are processed, so compare with the saved baseline after a few weeks, not after a few days.

Questions

How long after launch should pages appear in Google?

There is no fixed term. Search Console help says it can take a week or so for a new site to start being crawled and indexed, and Google's page on recrawling says crawling can take from a few days to a few weeks. Submitting a sitemap and requesting indexing of the home page are the steps Google itself suggests. Neither makes indexing certain.

Do I need a sitemap if the site is small?

Google says a site of about 500 pages or fewer that is well linked internally may not need one. It also lists new sites with few external links among the cases where a sitemap helps, and adds that most sites benefit from having one. Most CMSs and site builders create it automatically, so the usual task is to confirm that it exists and lists the right URLs.

Does a fully ticked checklist mean the site will rank well?

No. The checks confirm that search engines can find, read and show your pages. Positions depend on how useful the content is for a query and on many other signals. Google's starter guide says plainly that there are no secrets that automatically put a site first.

Can I use it for a site made with a site builder?

Yes. Google's documentation notes that hosted platforms may manage robots.txt, the sitemap and redirects through their own settings pages, so you may not edit these files by hand. Run the check anyway by opening the live address, and look in the platform's help if something is wrong.

Sources

Related course

Website SEO

How to make a site legible to search engines and to people at the same time: the technical base, search intent, semantics, architecture, and a content system that can actually be maintained.

See the course ↗
Reviews

Was this useful?

Your review
Tap a star to rate
What stood out? Up to three

Have a VITON ID? Sign in