Launch readiness
When a new site replaces an old one, every URL Google sends visitors to on the old site has to keep working — as the same page on the new site, or as a redirect to its new home. Launch readiness checks that before the switch, while the new site still runs on staging.
Setting it up
Section titled “Setting it up”- Add the new site (e.g.
staging.example.dev) to Overwatch with the SEO app installed. - In the site’s Settings → Site, set Replaces to the live site’s
hostname (e.g.
www.example.com). - Connect Search Console on the new site and choose the live site’s
property (e.g.
sc-domain:example.com). This is intended: the live site’s search traffic is what the check compares against. Google’s own view of the new site starts after launch.
A Launch readiness page then appears in the site’s menu.
What is checked
Section titled “What is checked”After each crawl of the new site, Overwatch takes the live site’s pages and requests each path on the new site, following redirects (up to five hops). The pages come from two sources:
- Search traffic: the pages that earned clicks or impressions in the last 28 days (Search Console, up to the top 500 by clicks).
- The live sitemap: every other page the live site’s sitemap lists
(found via its
robots.txtor at/sitemap.xml). These pages are indexed and may have links pointing at them even without recent clicks. The sitemap is read again weekly and on every re-check. This source works without Search Console.
Up to 1,000 paths are checked in all. Each path is one of:
| Result | Meaning |
|---|---|
| Same path | The new site answers 200 on the same path. |
| Redirected | A redirect on the new site leads to a working page. |
| Broken | The new site answers 404 (or another error) — visitors from Google would land on a broken page. |
| Redirect chain | A redirect on the new site ends on an error, loops, or takes more than five hops. |
| Removed (410) | The new site answers 410 Gone: the page was removed on purpose. Counted, but never blocks. |
A new site behind a password or bot wall (401/403) is reported as not checkable rather than broken. Checking starts as soon as Replaces is saved and usually finishes within a minute; whatever is left is finished within 15 minutes. The checks run again after each crawl, since the new site may have changed.
To check again without waiting for a crawl — say, right after adding redirects — use Re-check now on the checklist. It re-reads the live sitemap and requests every path again, which takes up to about a minute. It needs the same permission as triggering a crawl, and can run once a minute.
For each broken page, the report suggests the closest page on the new site by the words in its path. It’s information for whoever sets up the redirects — Overwatch doesn’t change or export redirects itself.
The launch checklist
Section titled “The launch checklist”| Check | Blocks launch when |
|---|---|
| Every page with search traffic still resolves | Any page is broken. |
| Every page in the live sitemap still resolves | Any page is broken. Left out when the live site has no sitemap. |
| Redirects land on a working page | Any redirect chain ends on an error or loops. |
| The new site is open to search engines | Never — noindex is right on staging, so it’s an At launch reminder: it must come off at the switch, or the whole site drops out of Google. |
| The sitemap lists the new site’s pages | Never — a warning when under 90% of crawled pages are in the sitemap. |
| Search Console is ready for the switch | Never — a warning when the connected property doesn’t cover the live host. |
The verdict is Not ready to launch while any check blocks, Ready — with launch-day steps when only reminders remain, and Ready to launch when everything passes. Breaking pages are grouped by site section, so a section that moved wholesale reads as one decision.
After launch
Section titled “After launch”A relaunch goes live by changing the site’s root URL in Settings →
Site to the live address (e.g. https://www.example.com/). Overwatch stamps
the launch date, and the page (now Launch in the menu) switches to the
after-launch view:
- The old URLs keep being checked after every crawl, against the live site. The live sitemap read before launch is kept, since the old site’s sitemap is gone. If an old page with search traffic worked and then breaks (a redirect removed, a page unpublished), a search alert goes out — see Notifications.
- Google’s side, from Search Console: whether Google has read a sitemap for the site (submitted, read, no errors), and how many of the inspected pages are in Google’s index. New URLs usually take a few weeks, so for 28 days after launch slow indexing is shown as waiting, not as a problem. The SEO report’s “Google hasn’t crawled the page yet” finding waits the same four weeks.
- Your steps — what only a person can do, with guidance. Tick each off as
done, or mark it as not applying:
- Ask Google to index the most important pages. Up to ten pages, ranked by the old site’s search clicks that now land on them, each with Google’s current verdict and a link straight into Search Console’s URL Inspection. Pages Google has indexed drop off the list; the step completes by itself when they all are.
- Add the site to Bing Webmaster Tools (it also feeds DuckDuckGo and ChatGPT search), importing it from Search Console.
- Check the website link in the Google Business Profile.
| After-launch check | Needs attention when |
|---|---|
| Old pages with search traffic still resolve | Any old page is broken. |
| Pages from the old sitemap still resolve | Any old page is broken. |
| Redirects land on a working page | Any redirect chain ends on an error or loops. |
| The site is open to search engines | Some pages carry noindex (a warning); every page does (fails). |
| The sitemap lists the site’s pages | Under 90% of crawled pages are in the sitemap. |
| Google has read the sitemap | No sitemap for the host is submitted, or Search Console reports errors. |
| Google is indexing the new pages | Under 80% of inspected pages are indexed four weeks after launch. |
| Search Console covers the site | The connected property doesn’t cover the live host. |
The verdict reads needs attention, Google is catching up (checks still waiting) or settled.
Finishing the launch
Section titled “Finishing the launch”A launch closes by itself 90 days after going live, unless a check still fails then (a broken old page or redirect, a site-wide noindex) — that keeps it open until it’s fixed. Warnings don’t hold it open; slow indexing and the like stay visible in the SEO report. An owner or admin can also close it early with Finish launch.
Finishing turns the site back into a regular site: Replaces is cleared, the Launch page leaves the menu, and the old URLs are no longer checked. Keep the redirects in place for at least a year — Google keeps following them that long.
In the stakeholder report
Section titled “In the stakeholder report”For a site with Replaces set, the stakeholder report opens with a Launch readiness section, right after the summary: the verdict, the share of search clicks that land on a working page, the checklist and the ten costliest pages that will break, with what the new site answers for each. It holds findings only; the closest-page suggestions stay in the app.
For CMS integrations, the same data is at GET /v1/sites/:id/launch-readiness
(verdict, checklist, totals and the breaking pages with suggestions; each
page’s source is search or sitemap). It returns 404 unless the site has
Replaces set and the SEO app installed. POST /v1/sites/:id/launch-readiness/recheck runs a re-check and answers with the
fresh report (429 within a minute of the last check).
After launch the report has phase: "launched", launchedAt, and steps:
the after-launch steps with their state (todo, done or skipped),
guidance and links, and for request-indexing the pages to ask for with
each page’s inspectUrl. PUT /v1/sites/:id/launch-readiness/steps/:step
with { "state": "done" | "skipped" | "todo" } ticks a step and answers with
the fresh report. finishesAt is when the launch closes by itself; POST /v1/sites/:id/launch-readiness/finish closes it now (owners and admins).