What this checkpoint covers
The questions are set at Ottercliff Travel Guides, an invented publisher of destination guides with a large archive. They draw on the site migrations guide, the JavaScript SEO guide and the website migration checklist. Each asks for a decision, not a definition.
Task
- Write a one-line answer and the action you would take for each question before scrolling on.
- Mark each answer confident or unsure.
- Compare with the explanations, noting the signal you misread on every miss.
- Reread the linked section for confident misses before the next module.
Questions
- Ottercliff plans to move to a shorter brand domain and launch a redesign with new templates at the same time, to "get the disruption over with". What do you recommend?
- The developer's redirect plan sends retired destination guides to the home page and leaves the redirects from an old protocol move in place, so old addresses pass through them first. What is wrong?
- The editor says there is no need to export anything before launch because analytics keeps history. Which benchmarks would you insist on, and why?
- The new guide template renders everything in the browser: the body text, the links to related guides, the title and the canonical tag. Which risks does that create?
- How would you verify, before and after launch, that the crawler sees what readers see?
- Weeks after launch the figures in the example below arrive. Fix or roll back?
- A large site like Ottercliff's recovers more slowly than a small one even when every redirect works. Why, and what should you avoid doing during the recovery?
Ottercliff Travel Guides: three weeks after launch
| Section | Organic clicks against benchmark | Old URLs returning not-found | Indexed new URLs |
|---|---|---|---|
| Destination guides | 88% | 0 | Rising steadily |
| Itinerary pages | 91% | 0 | Rising steadily |
| Hotel round-ups | 34% | 0 | Few; URL inspection shows an empty body |
| Whole site | 79% | 12 of 18,000 |
Answers explained
- Separate them. Two changes in one release make losses impossible to attribute. Keep URLs and change templates first, or move the domain with templates unchanged, then make the second change once the first has settled. The site migrations guide treats the number of simultaneous changes as the main risk.
- Both waste signals. Many unrelated pages redirected to the home page are treated as soft not-found, so their links stop counting; retired guides need the closest genuine equivalent or a deliberate gone status. Redirects chained through the old protocol rules slow crawling and dilute signals; resolve every old address to its final destination in one hop.
- Clicks and impressions by page and section, rankings for priority terms, indexed counts, the linked-URL list and a full crawl. Analytics history cannot tell you which URLs held links or ranked for what, and once the old site is gone the crawl cannot be taken. The "before" group of the website migration checklist exists for this.
- Content, links and signals that depend on execution. If rendering is delayed or a resource fails, pages index as empty, related-guide links are not followed, and a Canonical TagTells search engines the preferred URL. set by script may be missed or contradicted. Put content, links, titles and canonicals in the server response and keep interactivity on the client, as the JavaScript SEO guide recommends.
- Compare rendered HTML with expectations. Use the live URL test to view rendered HTML and failed resources, load the page with scripts disabled, check robots rules for every script and data host, and crawl with and without rendering to compare link counts. Repeat on production within hours of launch, per template.
- Fix, not roll back. The redirects work and most sections are recovering on schedule. The loss is concentrated in one template that renders empty, which points to a rendering fault such as a blocked data endpoint. Fix it, test that template live, then request recrawling. A rollback is for site-wide failure with no quick fix.
- Recrawling a big archive draws on Crawl BudgetHow much a search engine crawls a site.. The engine has to revisit every old URL and process every new one. Avoid adding new crawl demand: no new parameter URLs, no unnecessary sitemap churn, and no removal of redirects, which must stay for at least the documented period.
A learner with six or seven sound answers understands migration risk as part of SEOImproving visibility in unpaid search results. rather than a developer task. Fewer means rereading the guides behind the misses before moving on.
Where to go next
If questions two, three or six caught you out, redo the bathroom retailer redirect map exercise. Otherwise continue with the fabric shop filter indexing exercise, and use the intermediate SEO level to refresh crawling and indexing controls.
