How to Design Website Structure for SEO at Scale

How to Design Website Structure for SEO at Scale

WordPress won’t warn you about the old links when you change a page’s address. The new URL loads, and everything looks fine in the editor. Meanwhile, an older article may send people to the wrong service, or describe an offer the business stopped selling. A working redirect doesn’t fix what that article says.

We ran into this while cleaning up CMX’s old Discord material. The support service and its pricing page were retired, yet published articles still invited readers to hire us for that work. Taking the pages out of navigation wouldn’t have fixed those promises. We had to review the articles and correct the links without wiping out the history of what CMX built.

Know Which Page Is Responsible for the Answer

Before approving another page, find the one currently answering that question. It sounds obvious, but busy sites often distribute the same subject across a service page, a blog post and an older landing page. Each may have been useful when it was published. Together, they can leave visitors unsure which advice still applies.

CMX’s website development page helps somebody decide whether to hire us. A migration guide can get into redirect maps, launch checks and what to do when something breaks. The reader coming to each page needs different information. Another article that mostly repeats our service description would only make the choice harder.

Keep a working inventory that tells editors which page covers each major topic, which team owns it and when it was last reviewed. Add the current URL and any old addresses that redirect to it. A spreadsheet is fine, provided people check it before publishing and update it after making changes.

Keyword research should inform that decision. Search demand for a phrase doesn’t automatically require a new URL. Review what the existing page already answers, how people find it and whether a substantial new question deserves its own guide. Then assign the topic to a page instead of letting the content calendar decide.

Make Your Internal Links Reflect the Website You Operate Today

A tidy menu can conceal a messy archive. Older articles may recommend services that no longer exist. A footer might promote an offer that was replaced. An otherwise useful tutorial can point to a landing page whose message changed years ago.

Start with the pages visitors use most, then work through content that links to current services. Check the links in the body of each article, not only its navigation. When a service changes, search your content for its former name and URL. A proper retirement review should include those references.

Internal links also help readers discover a page without needing to search for it. Google’s guidance on crawlable links recommends linking important pages from elsewhere on the site. An XML sitemap is useful for discovery, but it won’t explain to a visitor why two pages belong together.

Compare a crawl with the full WordPress page inventory from time to time. That helps uncover orphan pages, meaning published URLs that no other crawlable page links to. A crawler cannot reliably find an isolated page by following links, which is why the inventory matters. Check links on a phone too. Visitors should be able to reach useful content through an ordinary, readable link.

Changing a URL Means Taking Care of Its Old Readers

Some URLs genuinely need to move. A business might merge two competing articles or rename a service. But a prettier address alone rarely justifies changing a working page. First check where people reach it from and whether other websites have linked to it.

For a permanent move, map the old address to the most relevant replacement. A 301 or 308 redirect can tell browsers and search engines the move is permanent. Google’s site move guidance covers the technical details. Update your own links to use the new address directly, and check that the canonical and sitemap point where you intend.

Then open the old URL yourself. Does it land on the page someone would expect? Does it pass through several redirects before arriving? A permanent redirect to an unrelated homepage may keep a visitor off an error screen while leaving their original question unanswered.

Sometimes there is no suitable replacement. An old announcement or discontinued service might need a clear explanation, an archived page or a normal missing-page response. Choose based on what the original page was for. Hiding every retired URL behind the homepage makes the website harder to understand.

Be Careful With Templates That Produce Hundreds of Pages

Templates save time when the content genuinely belongs on separate pages. Clinics with real locations, for instance, may need distinct addresses and appointment details. The location page should tell a patient something specific about that clinic. Swapping only the town name across dozens of otherwise identical articles doesn’t give readers much value.

Check the first few generated pages on mobile before publishing the rest. Do the contact links lead to the correct location? Are the hours and services accurate? Can someone tell why that particular page exists? One mistaken template field can spread across the whole set.

Service area coverage is a separate decision. If a business travels to several neighborhoods from one base, a clear service area page may be more useful than a large collection of near-identical neighborhood pages. Build pages around differences people need to know.

A Publishing Checklist That Someone Will Actually Use

Give a person responsibility for the final check. Automated tools help find errors, but they won’t know that a discontinued package is still being advertised in a perfectly functioning article.

  1. Check the topic. Which existing page already answers this question? Explain why the new one deserves to exist.
  2. Check the route in. Link from a relevant page using ordinary HTML, and make sure the link works on mobile.
  3. Check the route out. Open the page’s service links and calls to action. Confirm those offers are still current.
  4. Check any move. Test the old URL and its intended replacement. Update internal links and review redirects for unnecessary chains.
  5. Record the decision. Note who approved the change, who owns the page and what somebody should review next time.

When an editor joins the team, the record should tell them which pages are current and which redirects are deliberate. They shouldn’t have to guess why an old service URL still exists or revive a discontinued offer by following an outdated article.

Start With the Last Page You Retired

Find a service or article your organization stopped offering. Search the rest of the website for mentions of its name and old address. Read the surrounding sentences, because a link can be technically valid and still promise something the business no longer does.

Fix those references first. You’ll learn more about the real state of your site’s architecture from that exercise than from reorganizing the menu for the third time. CMX’s website structure guide covers the basics for smaller sites. Our website development services include migrations and the technical work behind them.