WordPress SEO · Business perspective
Website Redesign SEO: A Checklist Tested on Our Own August 2026 Rebuild
Every redesign checklist says “map your redirects.” This one says what happened when we did it on our own WordPress site: 32 pages retired, 78 redirect rules changed, 116 internal links moved, two AI crawlers found blocked by the host, and one problem the redesign could not fix.
What website redesign SEO is, and what a rebuild actually risks
Website redesign SEO is the work of changing a site’s structure, templates and pages without losing the rankings, the indexed pages and the AI-answer citations the old site had earned, and then using the rebuild to fix what the old site could not. AI Search Engine Optimization rebuilt its own WordPress site in August 2026 on a new child theme, retired 32 city landing pages that had been built in 2024 and 2025, and reorganized the rest around eight service pages; in the weeks that followed it changed 78 redirect rules (23 retargeted to the right page, 55 deleted because they pointed at addresses that no longer existed), moved 116 internal links across 77 pages in one verified pass, built a 404 page, published a list of retired addresses for the search engines, and found two AI crawlers being blocked by the host’s firewall while Google’s was let through. Every item in the checklist below was run on that site, and the results are stated, including the one the redesign did not fix.
What a rebuild risks is specific: addresses that change without a redirect, pages that are dropped with their links still pointing at them, templates that hide content the old ones showed, and crawlers, including the AI ones, that the new setup blocks without anyone noticing. None of those is design. They are plumbing, and a redesign that treats them as an afterthought loses in a week what the old site took a year to earn. The pages ranking for this question cover the plumbing well and the decision badly: none of the seven readable ones shows a rebuild the author actually ran, and only one asks whether a redesign was the right project in the first place. That question comes first.
Decide first: a redesign, or SEO on the site you have
A redesign is the right project when the constraint is the site’s structure or its ability to convert, and the wrong one when the constraint is what the pages say and whether Google trusts them, so AI Search Engine Optimization diagnoses the symptom before recommending either. Rankings that never arrived on pages Google has indexed point to content and authority, and a redesign leaves both untouched. Visitors who arrive and leave without inquiring point to the page’s presentation and the path to contact, which a redesign can fix. A site whose templates cannot carry structured data, whose navigation buries the money pages, or whose pages compete with each other for the same search points to structure, which is a rebuild. On this site the diagnosis in July 2026 was structure: 32 city pages competing with each other and with the service pages, a navigation built for a different set of services, and templates that could not carry the answer blocks and schema the AI platforms read. That is a redesign case. A site with clean structure and thin pages is not, and the same audit would send it to a content program instead.
- Pages indexed but not ranking: a content and authority problem; a redesign does not move it.
- Pages ranking but not converting: a presentation problem; a redesign or a conversion pass moves it.
- Pages competing with each other, templates that cannot carry schema, navigation that hides the money pages: a structure problem; this is the redesign case.
The checklist, with what each item produced on our rebuild
The checklist below is the one AI Search Engine Optimization runs on every WordPress rebuild it delivers through its WordPress SEO services, ordered by when each item happens, with the result each one produced on the August 2026 rebuild of this site. The items are the consensus of the field; the third column is what no checklist in the field carries.
| When | Item | What it produced on this site, August to September 2026 |
|---|---|---|
| Before | Crawl the old site and record every URL, title, ranking and inbound link | A full inventory; the redirect cleanup in September was run against it |
| Before | Decide which pages stay, merge, or retire, by demand and by inbound links | 32 city pages retired after each was checked for demand and for links pointing at it |
| Before | Map every retired or moved URL to one destination, one hop | The redirect map; later audited: 23 rules retargeted, 55 deleted |
| During | Keep URLs where the page survives; change only what the structure requires | Every surviving service and post URL kept; one post renamed and one merged later, each with a one-hop redirect |
| During | Build templates that carry structured data, answer blocks and one H1 | Service and insight templates with schema fields; a schema graph on every page |
| During | Keep any staging copy out of the index | The live site’s robots file and crawler-facing files confirmed after launch |
| Launch | Canonical host and protocol rules | www and http variants redirected to one canonical address in the server configuration |
| Launch | A real 404 page, and 410 for pages that are gone for good | 404 page built; retired addresses answer 410 or redirect, listed in a retired-URL sitemap for the engines |
| Launch | Internal links pointed at the surviving pages | 116 link changes across 77 pages in one afternoon, each read back live afterward |
| Launch | Tell the engines: sitemaps, IndexNow, Bing | 90 URLs submitted through IndexNow; Bing Webmaster Tools imported; retired-URL sitemap submitted |
| After | Probe every crawler, including the AI ones, with the identities they really use | Two AI crawlers found blocked by the host’s firewall while Google’s passed; a host ticket opened to allow them |
| After | Read the Crawl Stats and Indexing reports weekly | 49 crawl requests in a week, all refresh visits to known pages, none to new ones: the signal that led to the finding below |
| After | Regenerate the AI-crawler index file from the live site | llms.txt rebuilt from the live sitemap, 66 entries, every URL answering 200 |
| After | Re-measure rankings and AI citations against the pre-rebuild baseline | Weekly measurement running; the first post-rebuild AI reading is on the benchmark page |
Retired pages: redirect, 410, or keep, and how we decided for 32 of them
A retired page gets a redirect when a surviving page answers the same search, a 410 when nothing does, and it stays live when it still earns something, and AI Search Engine Optimization decided all three for the 32 city pages on this site by demand and by links rather than by sentiment. The city pages had been built for local searches the business no longer targets; the site is national, so most of them had no surviving equivalent, and a redirect to the homepage or to an unrelated service page would have been a soft 404 in Google’s eyes. Those answer 410. A handful matched a surviving service page and redirect to it in one hop. The redirect audit in September then found the residue every rebuild leaves: 55 old rules pointing at addresses that themselves no longer existed, and 23 pointing at the wrong survivor, which were fixed in one pass and checked as a search engine would check them, following each rule to its final answer. A redirect chain of two hops is a slow 301; a redirect to a page about something else is a 404 with extra steps.
- Redirect only where the destination answers the same search; otherwise 410.
- Audit the rules after launch as a crawler would: follow each to its final status code.
- Publish the retired addresses in a sitemap so the engines process them instead of rediscovering them for months.
The AI crawlers, and the firewall nobody checks
A rebuild changes the server as well as the site, and the change most checklists never test is whether the AI crawlers can still get in. AI Search Engine Optimization probes every rebuilt site with the crawler identities the AI platforms actually use, and on this site the probe found the host’s security layer blocking two of them while letting Google’s crawler through, silently, with no error anywhere in WordPress. The fix was a host ticket, not a plugin setting, and a page that no AI crawler can read cannot be cited whatever its content says. The same pass regenerated the site’s llms.txt from the live sitemap so the file the AI assistants read matched the pages that exist, and rewrote every page opener so the answer to the page’s question sits in its first paragraph, which is the part an AI answer lifts. The measurement that followed is on the AI answer benchmark page.
The problem the redesign could not fix
A redesign cannot make a thin page worth indexing, and this site proved it in September 2026. Two weeks after a batch of supporting posts went live on the new templates, 51 of the site’s 67 pages were still not in Google’s index, and the crawl log showed Google re-reading the pages it already held rather than fetching the new ones. The templates were clean, the redirects were right, the crawlers were allowed in, and none of it mattered, because the posts had been written to the same length and pattern with no first-party data, and Google’s indexing system declines pages that add nothing to what it already stores. The remedy was not structural; it was to rewrite each post around a dated measurement of its own, which is why this page carries the rebuild’s actual numbers rather than a generic checklist. The lesson for any redesign: budget for the content the new structure will carry, because a beautiful template around a page that says nothing new is a beautiful page Google will not keep.
After launch: what to watch, and for how long
The two weeks after launch are read in Search Console rather than in rankings, because rankings are the last thing to move. AI Search Engine Optimization watches three reports weekly on every rebuilt site. The Crawl Stats report shows whether Google is fetching the new pages or only refreshing the old ones; on this site it showed 49 requests in a week, all refresh visits, which was the first sign the new posts were not being read. The Indexing report shows which pages Google has stored and which it has looked at and declined, and it separates a page problem from a site problem. The redirect audit, repeated as a crawler would run it, shows whether every old address ends at a 200 or a 410 in one hop. A temporary dip in the first weeks is normal and is not what these reports are for; they are for telling the difference between a dip that is settling and a loss that is structural, and for finding it in week two rather than month three.
What a redesign should cost you, and what it should not
A redesign should cost the time to inventory, map and redirect properly, the templates that carry structured data and answer blocks, and the content the new structure needs, and it should not cost the rankings, the indexed pages or the citations the old site had earned. AI Search Engine Optimization scopes a rebuild in writing after the audit, because the price depends on how many pages survive, how many retire, and how much of the content has to be written to the standard the new templates deserve, and a scope that omits the content line is the one that ends with clean templates around empty pages. The pricing and proposals page explains how the scope is built; the number itself is written after the site is measured.
Questions about website redesign SEO
How do you redesign a website without losing SEO?
You redesign a website without losing SEO by inventorying every URL and its rankings first, keeping the addresses of pages that survive, mapping every moved or retired page to one destination in one hop, building templates that carry structured data, blocking the staging site, and then auditing the redirects, the crawlers and the indexing reports after launch. AI Search Engine Optimization ran that sequence on its own August 2026 rebuild: 32 pages retired, 78 redirect rules corrected, 116 internal links moved, and two blocked AI crawlers found by probing.
Should I do SEO before or after a website redesign?
SEO comes before a redesign as the audit that decides whether a redesign is the right project, and during it as the structure the new site is built on. AI Search Engine Optimization diagnoses the symptom first: pages indexed but not ranking need content and authority, which a redesign does not fix; pages competing with each other or templates that cannot carry schema need a rebuild. The August 2026 rebuild of this site was a structure case; a thin-content case would have been sent to a content program instead.
Do I need to keep the same URLs in a redesign?
Keep the same URL for every page that survives, and change only the addresses the new structure requires, each with a one-hop redirect. AI Search Engine Optimization kept every surviving service and post URL on its own rebuild and later renamed one post and merged another, each with a single redirect that was walked as a crawler would walk it to confirm it ended at a 200.
What happens to the pages I remove in a redesign?
A removed page redirects to a surviving page only if that page answers the same search; otherwise it should answer 410 and be listed in a retired-URL sitemap so the engines process it. AI Search Engine Optimization retired 32 city pages on its own site that way, then audited the old redirect rules and found 55 pointing at addresses that no longer existed and 23 pointing at the wrong survivor, all corrected in one pass.
How long does the traffic dip after a redesign last?
A settling dip lasts two to six weeks while Google re-reads the moved pages; a dip that is still there at month three is structural. AI Search Engine Optimization reads the Crawl Stats and Indexing reports weekly after launch rather than waiting for rankings, because those reports separate the two in week two; on its own rebuild they showed the new posts were not being fetched at all, which was a content problem the redesign could not fix.
Does a redesign help AI search visibility?
A redesign helps AI search visibility only if the new templates carry answer blocks and structured data, the AI crawlers can reach the site, and the pages say something the AI does not already hold. AI Search Engine Optimization found two AI crawlers blocked by its host’s firewall after its own rebuild and opened a ticket to allow them; a page no AI crawler can read is not cited whatever it says, and a page that adds nothing is not indexed at all.
How much should a website redesign cost?
A website redesign should cost the inventory and redirect work, templates that carry structured data, and the content the new structure needs, and it should never cost the rankings the old site had. AI Search Engine Optimization scopes a rebuild in writing after the audit, because the price depends on how many pages survive, how many retire, and how much content must be written to the standard the new templates deserve.
Continue your research
AI SEO Automation: What to Automate, and What Needs a Person: how the 116-link pass and the redirect audit were run and verified.
Keyword Mapping: One Search, One Page, No Exceptions: the map that decides which pages a rebuild keeps.
Discuss what this means for your business
If you have been quoted a redesign without an audit that says whether structure is actually the problem, you have been quoted a project, not a diagnosis. Owners who work with AI Search Engine Optimization describe the difference as being told what will be done and why, before anything is built. Owners who want their site measured first, and a rebuild scoped only if the measurement calls for one, start with the strategy call.
See how the WordPress work is delivered, including what a rebuild carries that a template does not.
Book a free strategy call before you commit to a redesign
30 minutes with Phil. Written scope and pricing before paid work begins.