Build search intent into the website before the pages are finished.

Give every page a job before designing its layout

Start a website project with the services the client wants to explain and the questions a customer needs answered. Map each proposed page to its audience, purpose, evidence and next action. Identify the person who supplies business facts, the person who writes or edits the content and the person who approves professional claims. A visually polished layout cannot resolve a missing service explanation or an unanswered pricing question by itself.

Review the current site before replacing it. Keep an inventory of existing URLs, useful content, titles, descriptions and important inquiry paths. Ask for appropriate access to search and analytics information so decisions are informed by evidence when it is available. Preserve useful pages and URLs unless there is a reason to change them. A redesign should make the customer's journey clearer without casually removing the material and addresses people already use.

Treat URL changes and launch settings as design dependencies

When addresses must change, prepare an old-to-new URL map and assign an appropriate destination for each affected page. Avoid sending unrelated old pages to the homepage as a blanket solution. Make the new internal links, canonical addresses and sitemap agree with the intended public URLs. Google provides specific site-move guidance; use it to plan implementation and monitoring rather than assuming a theme or SEO plugin handles every migration detail.

Check the rendered pages and their responses before launch. Confirm page-specific titles and descriptions, clear main headings, accessible content, working navigation and functioning contact routes. Review staging restrictions so the intended public pages can be indexed after release. Inspect important templates on mobile and test forms through to the actual destination. A successful build command or a green plugin score does not demonstrate that the live customer journey works.

Define a bounded handoff instead of an undefined SEO promise

A designer can deliver valuable SEO foundations without promising ongoing rankings. Define the scope in concrete terms: page-purpose mapping, content implementation, metadata, links, agreed URL redirects, launch verification and a documented handoff. Identify the work that needs a separate specialist or client decision. If the client has not supplied reviewed content or account access, record the dependency before the launch rather than silently substituting generic copy.

The handoff should identify account ownership, where important settings live, who maintains business facts and how issues are reported. Include the final URL map, remaining actions and the checks completed on the live site. Set a realistic post-launch review for indexing and inquiry behavior if that is within the engagement. Separate what was implemented from results that require later observation. This gives the client a reviewable deliverable and gives the designer a clear boundary around continuing marketing work.

Redirect a moved or consolidated page to its closest relevant replacement, normally with a permanent server-side redirect. If content is intentionally retired and has no suitable replacement, return a genuine 404 or 410 response instead of forcing an unrelated redirect. Record that decision in the URL inventory.