A WordPress website can look outdated without actually needing a complete rebuild. It can also look modern while hiding serious problems with speed, SEO, plugins, broken links, forms, security, or site structure.
That is why the best time to find website problems is before the redesign begins.
A pre-redesign audit helps you separate problems that require a new design from problems that can be fixed without rebuilding the website. It also gives your developer a clearer specification for the new site and reduces the risk of carrying old problems into the redesigned version.
Before changing layouts, colors, templates, or page builders, review the existing website across technical health, performance, SEO, UX, content, functionality and conversion paths. You can also use this WordPress website audit checklist to organize the review.
Why Audit a WordPress Website Before Redesigning?
A redesign changes much more than the appearance of a website.
Depending on how the project is handled, you may change:
- Page layouts
- Navigation
- URLs
- Templates
- Themes
- Plugins
- Content
- Internal links
- Images
- Forms
- Structured data
- Tracking
- Performance
- Mobile behavior
Some changes can improve the website. Others can accidentally remove functionality, rankings, traffic or useful content.
Google recommends thoroughly testing a new site before a site move and, when URLs change, preparing URL mappings and appropriate redirects.
The goal of a pre-redesign audit is therefore simple:
Understand what is wrong with the current website before deciding what the new website should look like.
1. Start With the Problems, Not the Design
Before opening a design tool or choosing a new WordPress theme, make a list of the problems users and the business are experiencing.
For example:
| Symptom | Possible underlying problem |
|---|---|
| Website feels slow | Heavy plugins, large images, poor hosting, inefficient code |
| Traffic is falling | SEO, content, technical or search-intent problems |
| Visitors leave quickly | UX, messaging, navigation or performance issues |
| Leads are low | Weak CTAs, forms, trust signals or page structure |
| Pages aren’t ranking | Technical SEO, content or relevance problems |
| Mobile experience is poor | Responsive design or layout issues |
| Developers keep fixing the same bugs | Theme, plugin or custom-code conflicts |
| Website is difficult to update | Poor CMS structure or excessive customization |
This distinction matters because a redesign is not automatically the solution to every website problem.
If the underlying issue is poor hosting, changing the homepage design may accomplish very little.
If the problem is thin or outdated content, a new color palette will not solve it.
If the problem is an overloaded plugin stack, installing another visual builder may make things worse.
2. Check WordPress Site Health
Start with WordPress’s built-in Site Health feature.
You can find it under:
WordPress Dashboard → Tools → Site Health
WordPress uses Site Health to identify critical issues and recommended improvements involving areas such as software versions, configuration and security.
Review:
- WordPress version
- PHP version
- Plugin updates
- Theme updates
- Security recommendations
- HTTPS configuration
- Background processes
- REST API status
- Scheduled events
- Database-related warnings
- Server configuration
- Persistent object cache, where relevant
Do not automatically treat every recommendation as a reason to rebuild the site.
Instead, classify each issue:
Fix now:
A serious issue affecting security, functionality, reliability or performance.
Fix during redesign:
An issue tied closely to the theme, templates, architecture or development approach.
Monitor:
A recommendation that does not currently create a meaningful problem.
This creates a more realistic redesign scope.
3. Audit Your Plugins
Plugins are one of the first areas to investigate when a WordPress website has accumulated problems over time.
Create a complete plugin inventory.
For every plugin, ask:
- What does it do?
- Is the functionality still required?
- Is another plugin already providing similar functionality?
- Is it actively maintained?
- Does the website depend on it?
- Does it affect frontend performance?
- Does it add unnecessary scripts or styles?
- Is it responsible for important forms, SEO or ecommerce functions?
- Can its functionality be replaced with simpler code?
Pay particular attention to plugin duplication.
For example, a website may have several plugins handling:
- SEO
- Caching
- Analytics
- Forms
- Redirects
- Security
- Image optimization
- Schema
- Social sharing
The goal is not to remove plugins simply because there are many of them.
The goal is to understand which plugins are necessary and what each one contributes.
4. Check the Theme and Custom Code
The theme can be responsible for problems that are not obvious from the frontend.
Review:
- Active theme
- Child theme
- Custom CSS
- Custom JavaScript
- Theme functions
- Template overrides
- Shortcodes
- Custom post types
- Custom fields
- Code snippets
- Third-party scripts
Ask whether the current theme is still appropriate for the website’s needs.
A redesign is often an opportunity to simplify the technical foundation rather than simply replacing the visual appearance.
If the existing website relies heavily on custom code, document what that code does before rebuilding anything.
Otherwise, useful functionality can disappear during the redesign because nobody realized where it came from.
5. Test Website Speed
Performance problems should be identified before the redesign because the new site should have a clear performance target.
Look for:
- Slow page loading
- Large images
- Unoptimized fonts
- Excessive JavaScript
- Unnecessary CSS
- Third-party scripts
- Large page builders
- Plugin-generated assets
- Poor caching
- Server response delays
- Oversized videos
- Excessive DOM complexity
Test important page types rather than checking only the homepage.
For example:
- Homepage
- Main service page
- Blog article
- Contact page
- Landing page
- Product page
- Category page
A website may have a fast homepage but a very slow blog template or ecommerce page.
Google recommends that websites be secure, fast, accessible and functional across devices.
For WordPress-specific performance work, review this WordPress speed optimization checklist for additional testing and improvement ideas.
6. Check Core Web Vitals
Performance should not be judged only by whether a page “feels fast.”
Review the site’s Core Web Vitals and other performance signals using appropriate testing and real-user data where available.
Look for problems involving:
- Loading performance
- Responsiveness
- Layout stability
- Large images
- Delayed interactions
- Layout shifts caused by media, fonts or dynamic elements
The important question is not simply:
“Can we make the website faster?”
Instead ask:
“Which templates, components and technical decisions are causing the performance problems?”
That answer can directly influence the redesign architecture.
7. Test the Website on Mobile
Open the website on actual mobile devices and test important journeys.
Do not only check whether the website technically fits on a smaller screen.
Test:
- Navigation
- Menus
- Buttons
- Forms
- Popups
- Text size
- Images
- Tables
- Embedded content
- Sticky elements
- Checkout, if applicable
- Contact actions
- Page scrolling
Pay particular attention to interactions that work on desktop but become frustrating on mobile.
A redesign should solve those specific problems rather than simply use a generic “mobile-friendly” template.
8. Find Broken Links and 404 Errors
Crawl the existing website and identify:
- Broken internal links
- Broken external links
- 404 pages
- Redirect chains
- Redirect loops
- Links pointing to outdated URLs
- Images returning errors
- Missing downloadable files
Then determine which URLs are important.
A 404 on an abandoned page may require little attention.
A 404 affecting an important service page, article or previously valuable URL deserves much more attention.
If URLs will change during the redesign, create an old-to-new URL mapping before launch. Google specifically recommends preparing URL mappings and redirects when site URLs change. For a broader review of these risks, see this WordPress redesign SEO audit.
9. Audit SEO Before Changing the Site
A redesign can accidentally remove SEO value that took years to build.
Before rebuilding, document important SEO assets.
Check:
- Organic traffic
- Ranking pages
- Search impressions
- Clicks
- Important queries
- Indexed URLs
- Canonical URLs
- XML sitemap
- Robots.txt
- Meta titles
- Meta descriptions
- Heading structure
- Internal links
- Image URLs
- Structured data
- Redirects
- Noindex directives
- Important backlinks
Google Search Console can help monitor indexing, crawling and search performance, while the URL Inspection tool can help investigate individual URLs.
For a more detailed technical review, use this technical SEO audit checklist and compare it with the WordPress technical SEO checklist for developers.
Do this before removing or rewriting pages.
Otherwise, you may not know which pages were actually contributing value.
10. Identify Your Most Valuable Pages
Not every page deserves the same treatment during a redesign.
Create a list of important URLs based on:
- Organic traffic
- Conversions
- Leads
- Revenue
- Backlinks
- Search impressions
- Rankings
- Business importance
- Internal-link importance
Then classify each page:
| Classification | Recommended action |
|---|---|
| High value, healthy | Preserve and improve |
| High value, problematic | Fix carefully |
| Low value, useful | Consider improving |
| Outdated | Update or consolidate |
| Duplicate | Consolidate where appropriate |
| No business/search value | Consider removing |
This prevents the common mistake of treating every page as equally disposable.
11. Review Website Structure and Navigation
A redesign is a good opportunity to fix confusing information architecture.
Review:
- Main navigation
- Dropdown menus
- Categories
- Parent/child pages
- Breadcrumbs
- Footer links
- Internal linking
- URL structure
- Important page depth
Ask:
Can a visitor quickly understand what this business offers and where to go next?
Then ask the same question from a search perspective:
Can search engines discover and understand the important pages through the site’s structure and links?
Google notes that links are an important way it discovers pages.
Do not redesign the navigation simply because the current menu looks old.
Redesign it because the existing structure makes important information difficult to find.
12. Review the Content Before Rebuilding It
One of the biggest redesign mistakes is moving every existing page into a new design without deciding whether the content is still useful.
Audit each important page for:
- Accuracy
- Search intent
- Originality
- Relevance
- Business value
- Organic performance
- Conversion performance
- Internal links
- Outdated information
- Duplicate content
- Thin content
Then choose:
Keep:
The page is still valuable.
Improve:
The topic is useful but the content needs work.
Merge:
Two or more pages overlap substantially.
Redirect:
The old page should be replaced by a more appropriate destination.
Remove:
The page has no meaningful purpose and should not be retained.
This is much better than blindly migrating the entire content library. If you need help planning the wider project, review this WordPress website redesign checklist.
13. Check Forms and Conversion Paths
A website can be technically healthy and still fail commercially.
Test every important conversion path.
For example:
- Contact forms
- Quote forms
- Newsletter forms
- Booking forms
- Phone links
- Email links
- WhatsApp buttons
- Download forms
- Ecommerce checkout
- Account creation
- Search functionality
Submit the forms yourself.
Check:
- Does submission work?
- Does the user see a confirmation?
- Does the business receive the lead?
- Is the correct email address used?
- Are tracking events firing?
- Does the form work on mobile?
- What happens when required fields are incomplete?
Do not assume that a form works because it visually appears on the page.
14. Review Analytics and Search Data
Analytics can reveal problems that a manual website review cannot.
Look for:
- Pages with high traffic but low conversions
- Pages losing organic traffic
- Landing pages with poor engagement
- High-exit pages
- Mobile versus desktop differences
- Conversion paths
- Search landing pages
- Traffic concentration on a small number of URLs
Search Console can provide another perspective through search queries, impressions, clicks and indexing information. Google recommends using Search Console when monitoring changes to a site and during migrations.
The purpose is not to chase every metric.
Use the data to identify where the website is failing users or the business.
15. Check Security and Maintenance Problems
Before redesigning, determine whether the existing website has maintenance or security problems that need attention.
Review:
- Outdated WordPress core
- Outdated plugins
- Outdated themes
- Unused plugins
- Unused themes
- Suspicious administrator accounts
- Weak access controls
- SSL/HTTPS
- Backup systems
- Security plugins or server-level protections
- PHP compatibility
WordPress considers keeping the software stack updated, maintained and secure part of maintaining a healthy website.
A redesign should not become an excuse to ignore an existing security issue.
16. Check Third-Party Integrations
Modern WordPress websites often depend on services outside WordPress itself.
Document integrations such as:
- Google Analytics
- Google Search Console
- CRM systems
- Email marketing platforms
- Payment gateways
- Booking systems
- Chat tools
- Advertising platforms
- Social platforms
- Maps
- Automation tools
Record how each integration works before rebuilding.
Otherwise, the redesigned site may look perfect while silently breaking lead tracking or another important business process.
17. Create a “Fix, Keep, Rebuild or Remove” List
Once the audit is complete, turn the findings into four categories.
Fix
Problems that can be solved without redesigning the website.
Examples:
- Broken links
- Missing redirects
- Plugin updates
- Image optimization
- Tracking errors
Keep
Elements that already work well.
Examples:
- High-performing landing pages
- Strong content
- Useful navigation
- Valuable URLs
- Working integrations
Rebuild
Problems that genuinely require structural or design changes.
Examples:
- Poor information architecture
- Outdated templates
- Difficult editing workflow
- Broken responsive layouts
- Inflexible page structure
Remove
Elements that add little or no value.
Examples:
- Unused plugins
- Duplicate pages
- Obsolete content
- Unnecessary scripts
- Redundant functionality
This framework makes the redesign much more deliberate.
What Should Be Fixed Before the Redesign Starts?
Some problems should be investigated or documented before development begins, even if the final fix happens during the redesign.
Prioritize:
- Critical security problems
- Important broken functionality
- High-value URLs and SEO assets
- Existing conversion paths
- Important redirects
- Analytics and tracking
- Content that must be preserved
- Plugin and theme dependencies
- Performance bottlenecks
- Third-party integrations
The goal is to establish a reliable baseline.
If you don’t know how the current website performs before the redesign, it becomes much harder to determine whether the new website actually improved anything.
WordPress Pre-Redesign Audit Checklist
Use this checklist before approving the redesign:
Technical
- WordPress version reviewed
- PHP/server environment reviewed
- Site Health checked
- Theme reviewed
- Plugins inventoried
- Custom code documented
- Security issues reviewed
- Backups confirmed
Performance
- Key templates tested
- Mobile performance tested
- Large images identified
- Heavy scripts identified
- Third-party scripts reviewed
- Core Web Vitals reviewed
SEO
- Organic traffic reviewed
- Important ranking pages identified
- Search Console reviewed
- Important URLs documented
- Titles and headings reviewed
- Canonicals checked
- Robots.txt checked
- Sitemap checked
- Internal links reviewed
- Redirects documented
- Noindex directives reviewed
UX
- Navigation tested
- Mobile experience tested
- Important user journeys tested
- Forms tested
- CTAs reviewed
- Accessibility issues identified
- Confusing pages documented
Content
- Valuable content identified
- Outdated content identified
- Duplicate pages identified
- Pages to consolidate identified
- Pages to remove identified
- New content requirements documented
Integrations
- Analytics checked
- Search Console checked
- CRM integrations documented
- Forms tested
- Payment systems tested
- Booking systems tested
- Third-party scripts documented
Common Mistakes When Auditing Before a WordPress Redesign
Mistake 1: Auditing only the homepage
The homepage may look excellent while important service pages, blog templates or conversion paths have serious problems.
Mistake 2: Assuming an old design is the main problem
A website can look outdated and still have a strong technical foundation.
Mistake 3: Replacing everything
A redesign does not mean every URL, plugin, page and piece of content needs to disappear.
Mistake 4: Ignoring SEO until launch
SEO should be considered before the new site is built, especially when URLs, navigation or content will change. This is why a website redesign SEO checklist should be part of the planning process.
Mistake 5: Forgetting old URLs
If URLs change, document the old and new destinations and implement appropriate redirects.
Mistake 6: Testing only desktop
Many website problems appear only on mobile devices.
Mistake 7: Measuring success only by appearance
A successful redesign should improve the website’s ability to serve users and meet business goals, not merely make it look newer.
Final Takeaway
The best WordPress redesigns start with an audit, not a mockup.
Before rebuilding the site, identify what is actually broken, what is performing well, what needs improvement, and what should be removed. Review technical health, plugins, performance, SEO, content, UX, conversions and integrations.
Most importantly, preserve the assets that already work.
A redesign should give you a better website, not simply a different website.
If the audit shows that the current site has problems that go beyond its visual design, the findings can become the foundation for a more focused redesign and development plan.
