After the website relaunch
The relaunch is online. Now it turns out whether everything fits together.
New URLs and templates often only have an effect during ongoing operation. Compare the condition before and after the change and keep an eye on open technical points.
Regular website crawls · daily from business · keyword rankings weekly.
Prepare before the change
Without a basis for comparison, any change remains an assumption.
After a relaunch, not only the design is new. Often URLs, templates, navigation and content change at the same time. If fewer pages are subsequently recorded or a score falls, you need the state before the change to classify the observation.
Therefore, secure an audit stand and a list of important URLs in advance. Add which old addresses should redirect to where, which pages should be omitted and which are deliberately treated differently. The URL mapping remains its own working document; the suite does not create an automatic migration release from it.
Three lists that will help later
- Important introductions: Pages with requests, sales, external links or important searches.
- Expected changes: new target URLs, aggregated content, and deliberately removed areas.
- Unchanged requirements: For example, reachable contact paths and indexable performance pages.
After publication:
Find the first error before evaluating the history.
Immediately after publication, check the most important ways of doing business. Old URLs should lead to the intended new content. New landing pages must be accessible and provide the desired SEO information. This direct exam will complement you regardless of the next planned suite crawl.
| Observation | Next test step |
|---|---|
| An old product URL leads to the start page. | In the URL mapping, see if there is a more suitable new landing page. Check the forwarding technically, instead of evaluating its status code alone. |
| The crawl contains significantly fewer URLs. | Compare navigation, sitemap, accessibility and quota. First clarify whether content is deliberately eliminated or no longer found. |
| Important new sites carry noindex. | Control staging settings in the CMS, template and HTTP header. Then check the correction on the delivered pages. |
| Old and new URLs are simultaneously linked internally. | Examine menus, editorial links and reused content modules for old references. |
For URL moves, Google recommends permanent server-side redirects and as direct destinations as possible. Google's Notes on Website Moves Also explain the follow-up in the Search Console.
The weeks after the relaunch
Evaluate technical stability and visibility separately.
What the Suite Continues to Watch
Recurring audits show the respective recorded website status. In addition, you can monitor important landing pages for indexability and changes to SEO information. Daily sitemap checking helps detect new or removed entries and eye-catching HTTP responses.
A fixed result is then reliable if the affected URL has been successfully checked again. Therefore, always compare measurement time and scope. A missing reading is not a successful follow-up audit.
What else do you evaluate?
Use your Search Console for indexing, impressions and clicks. Watch selected search terms in Rank Tracker. Fluctuations after a move can have several causes; a technical fix and a change in ranking on the same day do not yet prove a causal connection.
Make your changes with Date in your own log. If several people rework, otherwise it quickly becomes unclear which stand belongs to which measurement.
Select the test sequence appropriately
Daily crawls for intensive follow-up care.
Business or agency
Business offers daily website crawls for up to 10 projects, starting with 79 € net per month with monthly payment. Agency also crawls daily. The URL quotas apply to the account together for each round, not again for each website.
Keyword rankings remain weekly. The suite is not a release switch and does not automatically trigger a full special check when released.
Smaller projects or external audit
Starter and Pro check the website weekly; Sitemap and HTTPS can already be monitored daily from starter. Based on the risk and size of your website, decide whether this rhythm is sufficient for follow-up care.
For a professionally accompanied examination of the move, there are the Relaunch test as a separate performance. Automated monitoring does not replace this project review. All suite prices are plus VAT.
Good to know
Questions about the follow-up of a relaunch
Does the monitoring replace the release before the relaunch?
No. A project release includes technical requirements, URL mapping, central user channels and other individual criteria. The suite provides technical findings and recurring examinations, but does not decide on publication.
Should I start with the suite before moving?
A detected initial state facilitates later comparisons. Secure an audit status before the change, as well as your important URLs and the planned mapping. Non-existing historical measurements cannot be generated subsequently.
Does a deployment automatically trigger a new crawl?
The suite is not connected to your deployment here. Website crawls follow the intended test sequence and the tariff limits. An immediate control of important URLs after publication should be carried out separately.
Does an error-free crawl guarantee stable rankings?
No. A crawl assesses the recorded technical state. Visibility depends on other factors and can vary after a move. Add technical data to your Search Console and the history of selected keywords.
Appropriate next steps
Targeted deepening of follow-up care
- Relaunch checklist
Look up preparation and operational checkpoints.
- Monitor indexability
Check important new landing pages for Noindex and Canonical changes.
- Sitemap monitoring
Observe the generated URL inventory after the move.
- Rank Tracker
Classify the development of selected search terms.