WordPress SEO
WordPress SEO or a Website Redesign?
The short answer
Improve your existing WordPress site when it can support the customer experience and publishing work you need. Consider a redesign when the structure keeps getting in the way. Design age and traffic totals alone are not enough to decide.
On this page
Describe the constraint before choosing the project
“We need a new website” names a solution. “Buyers cannot tell which service applies to an existing installation” names an information problem. “Our team cannot change product conditions without breaking the page” names a publishing problem. Each needs a different investigation.
Separate four questions: is there relevant demand; does the offer answer it clearly; can the site present and maintain the answer; and can customers complete a sensible next step? Low inquiry volume does not identify which layer is responsible. Record actual questions, editing failures, page examples and available search records. Label anything you have not verified as a possible explanation.
Work through three possible paths
- Can the present website support the necessary page types, content and inquiry path? If yes, investigate improvements before assuming replacement. If the answer is unknown, test representative tasks.
- Is the obstacle confined to a specific template, page group or workflow? If so, compare a targeted change with a broader rebuild, including dependencies and checking.
- Are requirements substantially different across the site? If the business now needs a different information structure or functions the current system cannot reasonably support, investigate a redesign.
- Is there enough evidence to choose? If not, define the small investigation needed first. An uncertain decision does not become stronger because a proposal is detailed.
| Situation | Direction to investigate | Cost, risk and reversibility |
|---|---|---|
| A service company has usable editing and forms but unclear suitability information. | Retain the site; improve a priority service page using approved facts. | Narrower content scope and easier comparison with the previous version; it may not solve a separate demand problem. |
| A supplier’s product template cannot show an essential comparison, while the rest of the site works. | Assess one template change before a full rebuild. | Development still has dependencies; check related pages and whether the change can be reversed. |
| A company’s new product catalog and quotation requirements cannot fit its old brochure structure. | Compare restructuring and a broader build against written requirements. | More content and transition work; preserve useful resources and plan implementation risk. |
The same visual condition leads to three different recommendations. None establishes that a particular technology or redesign will improve rankings.
Decide what the new site must keep
Inventory pages, downloads, images, useful customer resources and current URLs. For each, record whether it will remain, be updated, be consolidated or require a separate retirement decision. Ask who uses a resource before removing it merely because it receives little search traffic.
A redesign need not change every URL. Where URLs do change, Google’s migration guidance calls for preparation, mapping, redirects and monitoring. Search fluctuation can occur. A promise of a risk-free reset is not a transition plan.
Use the migration planning guide for detailed responsibilities. Do not approve a blanket redirect of unrelated old pages to the homepage as a substitute for reviewing destinations.
Compare complete projects, not just design fees
A smaller project is not automatically cheaper once dependencies are included. Repeated fixes to an unsuitable system can consume more effort than a coherent rebuild; an unnecessary rebuild can also discard useful work and create avoidable transition tasks.
- Content: what can be retained, what needs factual correction and who supplies missing information?
- Implementation: which templates, integrations or publishing tasks need work?
- Transition: what pages, files and addresses need preservation and checking?
- Internal time: who reviews design, verifies claims and approves launch?
- After launch: what licensing, maintenance and ongoing content costs continue?
Request these items on the same basis for each option. A one-time build is not the same purchase as ongoing SEO, and a retain-existing-site recommendation does not imply an automatic discount.
Ask for the reasoning behind the recommendation
| Field | Example |
|---|---|
| Problem | Customers do not understand the service eligibility conditions. |
| Evidence | The service page omits them; the business team reports repeated questions. |
| Recommended first work | Approve the conditions and test them in the existing template. |
| Alternative considered | A rebuild; not yet justified because the required editing task has not been tested. |
| Unknown | Whether the long condition remains readable on mobile without template changes. |
| Next check | Use representative approved copy, inspect the layout and then confirm the implementation scope. |
A useful recommendation tells you what changes, why, what remains and which uncertainty could change the decision. For Stormy Increment, review the listed service options and confirm who will assess and implement the specific changes. The agency checklist helps compare who can carry out the recommendation, rather than simply sell its label.
For the surrounding design, content and implementation responsibilities, read our web design and SEO project guide.
Considering outside support? WordPress SEO Services: Scope and Fit explains the available scope and its limits.
Need help with your next step?
Tell us about your website and the question you are trying to work through.