Project plan for a website relaunch
A website relaunch involves marketing, sales, HR and IT — and without a clean SEO migration it puts years of search visibility at risk. This plan shows the relaunch of a bilingual corporate website with product catalogue, careers section and accessibility.
No sign-up · opens instantly · 20 Weeks · 10 Phases · 61 Tasks · Budget approx. €230,500
This is how the plan looks in PathHub — click through the tabs or tick off tasks.
Corporate Website Relaunch for Industrial Supplier
Relaunch the corporate website of an industrial supplier in German and English with a new CMS, integrated product catalogue from the PIM, and a dedicated careers section. The project must preserve SEO value during URL migration, meet WCAG 2.1 AA accessibility requirements, and operate on EU-based hosting infrastructure. It also requires coordinated content migration, localization, and governance across marketing, product, HR, IT, legal, and external implementation partners. The outcome should be a modern, compliant, and maintainable platform that supports customer discovery, recruiting, and corporate communications.
Phases
Phase 1: Discovery, Governance and Requirements
Establish the project framework, confirm business and technical requirements, and align all departments on scope, decision rights, and success criteria. This creates a controlled foundation for the CMS, PIM, content, compliance, and migration workstreams.
Phase 2: Information Architecture and Content Model
Define how corporate, product, careers, service, contact, and download content will be organized and maintained in German and English. The phase establishes the navigation, taxonomy, metadata, URL principles, and CMS/PIM content relationships required for design and implementation.
Phase 3: UX and Visual Design
Translate the approved structure into accessible, responsive user journeys and visual patterns. Designs will cover the most important corporate, product, careers, contact, form, search, and download experiences before development begins.
Phase 4: Technical Architecture and Hosting Setup
Establish the technical foundation for the new platform, including CMS architecture, environments, EU hosting, security, deployment, monitoring, and integration principles. Decisions made here reduce implementation and operational risks later in the project.
Phase 5: CMS Implementation and Core Integrations
Configure and develop the CMS foundation, reusable frontend components, editorial workflows, search, forms, consent handling, and core corporate website functionality. The implementation will follow the approved design system and content model.
Phase 6: PIM Product Catalogue Integration
Connect the PIM to the CMS or catalogue presentation layer and implement the product browsing experience. Product data, technical attributes, documents, assets, units, and German-English relationships will be validated before publication.
Phase 7: Careers, Content Migration and Localization
Implement the careers area and migrate approved corporate content into the new CMS while completing German-English localization. Content ownership, quality, legal review, and PIM-related product content gaps will be resolved before final QA.
Phase 8: Accessibility, SEO and Quality Assurance
Verify that the complete website meets the agreed WCAG 2.1 AA target, preserves organic search value, performs reliably, and complies with security, privacy, browser, and analytics requirements. Defects will be prioritized and remediated before acceptance testing.
Phase 9: User Acceptance, Training and Launch Readiness
Obtain formal business acceptance from the departments that own the website, train editors and administrators, and confirm that all operational and launch prerequisites are complete. No production release will proceed without documented approval and rollback readiness.
Phase 10: Launch and Stabilization
Execute the controlled production cutover, validate the live website, monitor search and business-critical functionality, and resolve launch defects. Ownership will then transfer to the operational teams with documented support and monitoring procedures.
Timeline
Budget
| Item | Qty | Unit price | Total |
|---|---|---|---|
| Solution Architect | 8 Person days | €1,200 | €9,600 |
| Senior CMS Developer | 28 Person days | €900 | €25,200 |
| Frontend Component Developer | 18 Person days | €800 | €14,400 |
| PIM Integration Engineer | 25 Person days | €950 | €23,750 |
| DevOps and Security Engineer | 8 Person days | €950 | €7,600 |
| Item | Qty | Unit price | Total |
|---|---|---|---|
| Senior Project Manager | 14 Person days | €900 | €12,600 |
| Business Analyst / Requirements Consultant | 10 Person days | €950 | €9,500 |
| Information Architect / Content Modeler | 8 Person days | €900 | €7,200 |
| UX/UI Designer | 14 Person days | €850 | €11,900 |
| Accessibility UX Reviewer | 3 Person days | €900 | €2,700 |
| Item | Qty | Unit price | Total |
|---|---|---|---|
| QA Lead | 14 Person days | €850 | €11,900 |
| Browser, Device and Regression Testers | 12 Person days | €600 | €7,200 |
| WCAG 2.1 AA Accessibility Specialist | 8 Person days | €1,000 | €8,000 |
| SEO Migration Consultant | 10 Person days | €950 | €9,500 |
| GDPR and Security Test Consultant | 5 Person days | €1,100 | €5,500 |
| Item | Qty | Unit price | Total |
|---|---|---|---|
| Content Migration Specialist | 15 Person days | €750 | €11,250 |
| German-English Localization Editor | 24 Person days | €600 | €14,400 |
| Product Data Quality Coordinator | 10 Person days | €750 | €7,500 |
| Careers and Recruitment Integration Specialist | 10 Person days | €850 | €8,500 |
| Item | Qty | Unit price | Total |
|---|---|---|---|
| EU Hosting Environment Setup and Hardening | 1 Flat rate | €6,500 | €6,500 |
| Deployment, Monitoring and Backup Configuration | 1 Flat rate | €4,500 | €4,500 |
| CMS Editor and Administrator Training | 3 Person days | €850 | €2,550 |
| Launch and Cutover Support | 8 Person days | €850 | €6,800 |
| Operational Handover Documentation | 1 Flat rate | €1,950 | €1,950 |
Risks
Product Data Quality and Regulatory Attribute Gaps
If more than 5% of sampled products have missing technical attributes, inconsistent units, incorrect classifications, outdated documents, or incomplete German-English data during Weeks 11–14, the catalogue may display inaccurate information and delay launch.
CMS and PIM Integration Failure
If the PIM API specification, ownership model, or synchronization rules are not approved by Week 8, or if two consecutive integration test cycles fail during Weeks 11–13, product pages, assets, filters, or availability information may not render reliably.
SEO Visibility Loss During URL Migration
If the URL inventory and redirect map are incomplete, or redirect, canonical, sitemap, and indexation tests show less than 99% coverage by Week 16, the launch may cause ranking losses, broken links, and reduced organic traffic.
WCAG 2.1 AA and Accessible Document Non-Compliance
If automated and manual testing identifies unresolved Level A or serious Level AA issues in navigation, forms, search, product filters, PDFs, careers workflows, or third-party components during Weeks 14–16, redesign and legal or reputational exposure may delay launch.
GDPR, Consent and EU Hosting Misconfiguration
If data flows, processor agreements, sub-processors, retention rules, consent settings, or hosting access locations remain unapproved by Week 16, contact forms, careers applications, analytics, or cookies may process personal data unlawfully.
Security, Backup and Operational Readiness Gaps
If penetration testing identifies unresolved high-severity vulnerabilities, or if backup restoration, monitoring, deployment, rollback, and incident-response rehearsals fail by Week 18, launch defects could cause downtime or loss of editorial and product data.
Bilingual Content and Terminology Inconsistency
If priority German and English pages, product attributes, legal text, or careers content are not fully translated and reviewed by Week 15, users may receive contradictory technical, commercial, or employment information.
Careers and Recruitment Integration Dependency
If the careers feed, ATS interface, application links, consent wording, or tracking integration has not passed HR and technical testing by Week 13, vacancies may be missing, duplicated, outdated, or forced into a manual process at launch.
Stakeholder Approval and Content Ownership Delays
If product, sales, HR, legal, country, or language reviewers miss the agreed three-business-day review window during Weeks 12–17, conflicting feedback or unowned pages may prevent formal acceptance and compress launch testing.
Scope Growth and Budget or Timeline Compression
If new product templates, integrations, languages, content volumes, accessibility remediation, or stakeholder requests increase approved scope by more than 10% after Week 5, the 12% reserve may be consumed before QA and launch readiness.
Stakeholders
Executive Sponsor / Managing Director
Owns business outcomes, budget, scope escalation, and final go-live approval
Marketing and Corporate Communications
Owns corporate messaging, brand consistency, campaign priorities, and editorial governance
Product Management and Product Data Owners
Define product taxonomy, catalogue requirements, technical attributes, and data quality standards
Sales and Customer Service
Validate customer journeys, product discovery, enquiries, downloads, and regional requirements
Human Resources and Recruiting
Owns careers content, vacancies, application journeys, and employer-brand requirements
IT and Enterprise Architecture
Approves CMS integration, identity and access, environments, security, support model, and technical operations
Data Protection, Legal and Compliance
Reviews GDPR, cookies, forms, tracking, hosting arrangements, legal notices, and accessibility obligations
SEO and Analytics Owner
Defines migration rules, measurement requirements, redirects, search visibility controls, and reporting
Content Editors and Country or Language Representatives
Produce, review, translate, and maintain German and English content
External CMS/PIM Implementation Partner
Delivers architecture, development, integration, migration support, and technical remediation
EU Hosting, Security and Operations Provider
Implements hosting, monitoring, backups, deployment, incident response, and operational handover
Compliance
Complete a GDPR processing inventory covering contact forms, analytics, cookies, careers applications, hosting, PIM/CMS integrations, recipients, retention periods, data-subject rights, and processor agreements; complete DPIA screening where required.
Implement ePrivacy-compliant consent management for non-essential cookies, analytics, advertising tags, and similar technologies, including prior consent where required, an equally prominent refusal option, consent records, and withdrawal functionality.
Protect applicant and employee-related data in the careers section through lawful-basis and privacy notices, role-based access, restricted data collection, retention and deletion rules, secure transmission, and approved ATS processors.
Meet the project’s WCAG 2.1 AA target and assess alignment with EN 301 549 and applicable European or national accessibility obligations, including accessible templates, forms, navigation, multimedia, PDFs, product documents, and third-party components.
Publish accurate German and English legal disclosures, including provider identification/imprint, privacy information, cookie information, contact details, and applicable terms or disclaimers for digital services.
Host production and backup environments in approved EU regions, document subprocessors and support access locations, enforce encryption, least-privilege access, logging, vulnerability management, backups, restoration testing, and incident-response procedures.
Apply internal security and operational standards, including OWASP-based application testing, browser and device compatibility testing, release approvals, accessibility and SEO evidence, analytics validation, monitoring, rollback procedures, and formal go-live sign-off.
Milestones
- Week 2
Approved requirements baseline, governance model, scope, success criteria, and delivery plan
Depends on: Discovery, governance, and stakeholder alignment - Week 5
Approved sitemap, content model, product taxonomy, bilingual content rules, search requirements, and URL principles
Depends on: Requirements baseline and content governance - Week 8
Approved accessible design system, responsive templates, and validated user journeys for all priority content types
Depends on: Information architecture and content model - Week 8
Approved technical architecture with operational EU environments, security controls, integration specifications, and compliance decisions
Depends on: Architecture and hosting setup - Week 12
CMS-enabled corporate website foundation with tested templates, workflows, search, forms, consent management, and analytics instrumentation
Depends on: Technical architecture and CMS implementation - Week 14
Validated PIM-to-website integration with approved product taxonomy, representative catalogue data, bilingual product content, and tested product journeys
Depends on: CMS foundation and product data readiness - Week 15
Careers functionality operational and all priority German-English content migrated, reviewed, assigned to owners, and ready for formal QA
Depends on: PIM integration and content localization - Week 16
Signed QA report showing resolved critical defects, WCAG remediation status, tested SEO migration controls, and approved security and compliance results
Depends on: Content migration and implemented functionality - Week 18
Signed business acceptance, trained operational users, approved launch checklist, and formal go-live authorization
Depends on: QA completion and launch readiness - Week 20
Website live in German and English with validated redirects, integrations, monitoring, operational handover, and stabilization sign-off
Depends on: Go-live authorization and launch execution
How this plan was created
This plan was created by PathHub AI from a single description: “Relaunch the corporate website of an industrial supplier with 300 employees in German and English: new CMS, product catalogue from the PIM, careers section, accessibility to WCAG 2.1 AA, SEO migration of existing URLs and hosting in the EU.” — without company context. With your departments, approval processes and compliance requirements it becomes much more precise.
Obligations with lead time: what many think of too late
These obligations are typically triggered by a website relaunch (example: Germany). PathHub AI schedules them with lead time, warns when the schedule is too tight and shows the rule with its criteria under “Rule & evidence”, which you tick off and back with evidence. Not legal advice.
Rule & evidence
Why: Every website with analytics, maps, video or marketing services processes personal data.
Legal basis: Sec. 25 TDDDG: consent before setting non-essential cookies and trackers; GDPR Art. 13 information from the first visit.
- Cookie consent banner for all non-essential cookies and trackers
- Active opt-in without pre-ticked boxes
- Rejecting as easy as accepting
- Consent withdrawal available at any time
If breached: TDDDG fines up to €300,000. GDPR fines up to €20m or 4% apply in parallel.
Rule & evidence
Why: Accessibility has been mandatory for online shops serving consumers since June 2025.
Applies: if consumers can conclude contracts online (e.g. shop, booking); micro-enterprises with fewer than 10 employees and at most EUR 2m turnover or balance sheet are exempt for services
Legal basis: The BFSG has applied since 28 June 2025 to e-commerce services for consumers.
- Accessibility of certain products and services (e.g. e-commerce, banking, e-books) since 28 June 2025
- Compliance with accessibility requirements (perceivability, operability, understandability, robustness)
- Provision of accessibility information for consumers
- Micro-enterprise exemption for services (fewer than 10 employees and at most €2m turnover)
If breached: Fine up to €100,000 per violation. Sales ban until remediated.
Rule & evidence
Why: Distance-selling errors are a frequent reason for warning letters and extend withdrawal periods.
Applies: when selling to consumers
- Pre-contractual information obligations for distance contracts (Art. 246a EGBGB)
- Proper cancellation policy and provision of the model withdrawal form
- 14-day right of withdrawal for consumers
- Clearly designed ordering process with the "button solution" (order with obligation to pay)
- Transparent information on total price, delivery/shipping costs and contract term
If breached: Warnings and injunctions by competitors/consumer associations. Fines up to €250,000.
Rule & evidence
Why: Without registration, selling is prohibited.
Applies: if packaged goods are shipped to private end consumers
Legal basis: Packaging Act: registration in the LUCID register and system participation before first placing on the market.
- Registration in the LUCID packaging register before placing on the market
- System participation (licensing) of sales packaging subject to participation with a dual system
- Identical volume reporting to LUCID and the dual system
- Declaration of completeness when statutory volume thresholds are exceeded
- Observance of take-back and deposit obligations (e.g. one-way deposit)
If breached: Sales and distribution ban for non-registration. Fines up to €200,000.
Frequently asked questions
More project plan examples
Adapt this plan to your company
Open the plan in PathHub — no sign-up. Or describe your own initiative and get a complete plan in minutes.
Open plan →