tokyo.uk → node.uk redirect plan (DRAFT)

90 pages mirrored from tokyo.uk on 2026-05-22. This document proposes which
URLs should stay live on tokyo.uk vs. 301-redirect to existing node.uk
content. Reviews/edits welcome before we wire it up.

A. Keep on tokyo.uk (unique creative/agency content)

These have no real equivalent on node.uk — they're the tokyo agency
portfolio and the creative-agency service pages.

Portfolio (31 pages) — keep all

/                                 (home)
/about-us
/contact
/work + /work/*  (31 case studies: 4music, adidas-4dfwd, annabels, bbc,
                  burn, capcom, cisco, disney, emirates, fremantle,
                  fyre-festival, google-cds, harrods, house, merry-pixmas,
                  oakley, oetker-collection, pavia, peter-rabbit,
                  pinterest-presents, proxx, shire, sky-mobile, store-first,
                  turner, urban-splash, valentino, volkswagen, warehouse,
                  4talent, adidas-sportswear)
/sitemap

Creative services (15 pages) — keep all

These don't exist on node.uk (node is infra/AI/security-focused):

/what-we-do
/what-we-do/adaptive-machine-learning
/what-we-do/ai-ml-rag-chatbot
/what-we-do/cms-crm
/what-we-do/creative-design
/what-we-do/creative-marketing-agency
/what-we-do/ecommerce
/what-we-do/interactive-game
/what-we-do/interface-crafting
/what-we-do/mobile-app-development
/what-we-do/motion-design
/what-we-do/targeted-persona-development
/what-we-do/ui-ux-blueprinting
/what-we-do/user-experience-ux
/what-we-do/user-research-insight
/what-we-do/web-development

Landing pages (8 pages) — keep all

Vertical-specific agency landers — pure tokyo agency content:

/landing/entertainment-digital-agency
/landing/fashion-digital-agency
/landing/gamification-agency
/landing/hospitality-digital-agency
/landing/luxury-digital-agency
/landing/private-members-clubs
/landing/travel-digital-agency
/landing/virtual-events-agency

Articles unique to tokyo (2 pages) — keep

Not present in node.uk's /insights:

/articles/digital-strategy-making-your-online-business-effective
/articles/understanding-digital-strategy

Note: node.uk has redirects sending these slugs to /consulting/digital-strategy/ — confirm we want tokyo to keep its own copies.

B. Redirect tokyo.uk → node.uk (content already lives on node)

Two-way decision needed: do you want each of these to redirect from
tokyo to node, or do you want to keep a copy on tokyo and accept
duplicate-content risk? My recommendation is redirect — node already
has the indexed version, single canonical wins SEO.

Sectors (5) — exact slug match on both sites

/sectors                          → https://node.uk/sectors/
/sectors/business-corporate       → https://node.uk/sectors/business-corporate/
/sectors/luxury-fashion           → https://node.uk/sectors/luxury-fashion/
/sectors/media-entertainment      → https://node.uk/sectors/media-entertainment/
/sectors/pharmaceutical-healthcare → https://node.uk/sectors/pharmaceutical-healthcare/
/sectors/travel-hospitality       → https://node.uk/sectors/travel-hospitality/

Articles → Insights (8) — exact slug match

/articles/                        → https://node.uk/insights/
/articles/ai-browser-data         → https://node.uk/insights/ai-browser-data/
/articles/enhancing-user-experience-design → https://node.uk/insights/enhancing-user-experience-design/
/articles/fashion-ai              → https://node.uk/insights/fashion-ai/
/articles/healthcare-britain-ai   → https://node.uk/insights/healthcare-britain-ai/
/articles/hello-fresh-ai          → https://node.uk/insights/hello-fresh-ai/
/articles/immersive-experiences-for-brands → https://node.uk/insights/immersive-experiences-for-brands/
/articles/seo-importance-of-search-engine-optimisation → https://node.uk/insights/seo-importance-of-search-engine-optimisation/
/articles/website-usability-analysis → https://node.uk/insights/website-usability-analysis/
/insights                         → https://node.uk/insights/  (tokyo's index → node's)

Service pages with direct equivalents on node (10)

/what-we-do/ai-sentiment-analysis       → https://node.uk/ai/ai-sentiment-analysis/
/what-we-do/analytics-exploration       → https://node.uk/ai/analytics-exploration/
/what-we-do/usability-analysis          → https://node.uk/ai/usability-analysis/
/what-we-do/seo-and-user-analytics-data-science → https://node.uk/ai/seo-and-user-analytics-data-science/
/what-we-do/custom-software-development → https://node.uk/consulting/custom-software-development/
/what-we-do/digital-strategy            → https://node.uk/consulting/digital-strategy/
/what-we-do/qa-testing                  → https://node.uk/consulting/qa-testing/
/what-we-do/systems-security            → https://node.uk/security/systems-security/
/what-we-do/cloud-services              → https://node.uk/cloud/  (closest match)
/what-we-do/seamless-cloud-migration    → https://node.uk/cloud/cloud-native-modernisation/

Legal/policy (3) — exact slug match

/about-us/terms-and-conditions    → https://node.uk/about-us/terms-and-conditions/
/about-us/privacy-policy          → https://node.uk/about-us/privacy-policy/
/about-us/disclaimer              → https://node.uk/about-us/disclaimer/

Alternative: keep tokyo's own legal pages since they describe tokyo Ltd. specifically. Recommend keeping these on tokyo.

C. Open questions

  1. Domain ownership — is tokyo.uk staying as a separate brand domain
    long-term, or eventually being collapsed into node.uk? Affects whether
    we want canonical tags on overlapping pages instead of 301s.
  2. Legal pages — same Ltd. company or different? If same, redirecting
    to node.uk legals reduces maintenance.
  3. Articles — node.uk currently redirects the two "digital-strategy"
    articles to /consulting/digital-strategy/. Should we keep that on
    node, and on tokyo just link out, or republish on tokyo?
  4. /insights vs /articles — tokyo uses /articles/, node uses
    /insights/. Pick one for tokyo (keep /articles/?) so we don't
    need a tokyo-internal redirect too.